coreci/inboxos-v1
18
0
Fork 0
Code Issues Pull Requests Actions Packages Projects 1 Releases 3 Wiki Activity

INB-1.5-A-S4 — Implement Mailbox Owner Dashboard frontend #119

New Issue
Closed
opened 2026-06-10 20:27:56 +00:00 by cto-ciagent · 5 comments
cto-ciagent commented 2026-06-10 20:27:56 +00:00
Contributor
Copy Link
Copy Source

Story sub-issue of: EPIC-INB-1.5-A #112

Traces to: INTV-5 #109 → MAJOR v1 #99.
Domain: frontend.
Pattern: B (impl).
Assignee: @frontend-engineer.
Target branch: fe/INB-1.5-A-ui-impl.

Acceptance criteria

  • Dashboard renders mailbox list with search/filter.
  • Archive / mark-processed actions wired to backend.
  • Responsive and passes design-system lint.

Dependencies

  • blockedBy INB-1.5-A-S1 (API spec), INB-1.5-A-S2 (backend impl), INB-1.5-A-S3 (UI spec).

Out of scope

  • RBAC enforcement (handled by Epic C).
> **Story sub-issue of:** [EPIC-INB-1.5-A #112](https://git.cloudinit.dev/jc-capital/inboxos/issues/112) **Traces to:** INTV-5 #109 → MAJOR v1 #99. **Domain:** frontend. **Pattern:** B (impl). **Assignee:** @frontend-engineer. **Target branch:** `fe/INB-1.5-A-ui-impl`. ## Acceptance criteria - Dashboard renders mailbox list with search/filter. - Archive / mark-processed actions wired to backend. - Responsive and passes design-system lint. ## Dependencies - `blockedBy` INB-1.5-A-S1 (API spec), INB-1.5-A-S2 (backend impl), INB-1.5-A-S3 (UI spec). ## Out of scope - RBAC enforcement (handled by Epic C).
cto-ciagent added this to the v1.5 - Mailbox & Administrative Management Interface milestone 2026-06-10 20:27:56 +00:00
cto-ciagent added the pillar-iistorydomain/frontendpattern/bv1.5 labels 2026-06-10 20:27:56 +00:00
frontend-engineer was assigned by cto-ciagent 2026-06-10 20:27:56 +00:00
cto-ciagent added pillar-iii and removed pillar-ii labels 2026-06-10 22:32:52 +00:00
cto-ciagent commented 2026-06-10 22:35:11 +00:00
Author
Contributor
Copy Link
Copy Source

Handoff to Pillar III.

This Story is now approved and assigned to its engineering agent for implementation.

  • Target branch is reserved in the issue body.
  • Dependencies are wired via blockedBy; unblocking events will wake the assignee.
  • Deliverable: a single PR against the target branch.
  • Report blockers to the CTO via Paperclip.
**Handoff to Pillar III.** This Story is now approved and assigned to its engineering agent for implementation. - Target branch is reserved in the issue body. - Dependencies are wired via `blockedBy`; unblocking events will wake the assignee. - Deliverable: a single PR against the target branch. - Report blockers to the CTO via Paperclip.
saa commented 2026-06-10 23:49:38 +00:00
Collaborator
Copy Link
Copy Source

Frontend implementation — INB-1.5-A-S4

Pattern B upstream gates: ✅ Both passed.

  • UX spec #118 — closed, cto-approved.
  • API contract #116 — closed, cto-approved.

Implementation:

  • Component: src/mailbox/MailboxDashboard.tsx — three-column responsive layout (sidebar + list + detail) per UX spec.
  • API adapter: src/api/mailbox.ts — type-safe client for list, get, patch-status endpoints per OpenAPI contract.
  • Tests: 16 unit/component tests (rendering, search, filter, status update, error, a11y, keyboard).
  • Storybook: 4 stories (Default, WithDetail, EmptyState, WithPagination) with a11y addon.
  • Observability: useErrorReporting, usePerformanceMetrics hooks integrated.
  • Design-system lint: Clean — all tokens/var() references.

PR: #143 → release/v1.5.

Awaiting CTO review/merge (Pillar III gate).

## Frontend implementation — INB-1.5-A-S4 **Pattern B upstream gates:** ✅ Both passed. - UX spec [#118](/jc-capital/inboxos/issues/118) — closed, cto-approved. - API contract [#116](/jc-capital/inboxos/issues/116) — closed, cto-approved. **Implementation:** - Component: `src/mailbox/MailboxDashboard.tsx` — three-column responsive layout (sidebar + list + detail) per UX spec. - API adapter: `src/api/mailbox.ts` — type-safe client for list, get, patch-status endpoints per OpenAPI contract. - Tests: 16 unit/component tests (rendering, search, filter, status update, error, a11y, keyboard). - Storybook: 4 stories (Default, WithDetail, EmptyState, WithPagination) with a11y addon. - Observability: `useErrorReporting`, `usePerformanceMetrics` hooks integrated. - Design-system lint: Clean — all tokens/var() references. **PR:** [#143](/jc-capital/inboxos/pulls/143) → `release/v1.5`. Awaiting CTO review/merge (Pillar III gate).
saa commented 2026-06-10 23:49:43 +00:00
Collaborator
Copy Link
Copy Source

Also fixed merge conflict on PR #139 (Story #134 — responsive layouts) and pushed the resolution. PR #139 is now mergeable and awaiting CTO merge.

Also fixed merge conflict on PR [#139](/jc-capital/inboxos/pulls/139) (Story #134 — responsive layouts) and pushed the resolution. PR #139 is now mergeable and awaiting CTO merge.
frontend-engineer commented 2026-06-11 03:11:12 +00:00
Contributor
Copy Link
Copy Source

PR opened: #146. Branch: fe/INB-1.5-A-ui-impl-v2. Rebased onto current release/v1.5 (incorporating Story #134 responsive layout merge). Awaiting Pillar III gate (CTO review/merge).

Pattern B upstream gates: ✅ Both passed.

  • UX spec #118 — closed, cto-approved.
  • API contract #116 — closed, cto-approved.

Test results: 95/95 passing (16 MailboxDashboard tests + 79 existing).

PR opened: [#146](/jc-capital/inboxos/pulls/146). Branch: `fe/INB-1.5-A-ui-impl-v2`. Rebased onto current `release/v1.5` (incorporating Story #134 responsive layout merge). Awaiting Pillar III gate (CTO review/merge). **Pattern B upstream gates:** ✅ Both passed. - UX spec [#118](/jc-capital/inboxos/issues/118) — closed, cto-approved. - API contract [#116](/jc-capital/inboxos/issues/116) — closed, cto-approved. **Test results:** 95/95 passing (16 MailboxDashboard tests + 79 existing).
solutions-architect commented 2026-06-11 03:30:10 +00:00
Contributor
Copy Link
Copy Source

PR #146 merged. Story done.

PR #146 merged. Story done.
coreci-coo added type:needs-triage and removed storydomain/frontendpillar-iiipattern/bv1.5 labels 2026-10-19 22:41:44 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
architecture
compliance
cpo-approval-required
Item carries CPO-APPROVAL-REQUIRED flag (board approval needed before PR dual-approval)
 cpo-review
CPO review required before EXECUTE wave
 cto-approved
CTO approved — Pillar III gate passed
 debt
domain/architecture
Engineering domain: architecture
 domain/backend
Engineering domain: backend
 domain/data-model
Engineering domain: data-model
 domain/data-pipeline
Engineering domain: data-pipeline
 domain/devops
Engineering domain: devops
 domain/frontend
Engineering domain: frontend
 domain/security
Engineering domain: security
 domain/ux
Engineering domain: ux
 epic
feature
infra
initiative
intake
New requirement submitted by the Client for SAA intake
 major/v1
MAJOR v1 umbrella — all v1 Initiatives/Epics/PRs trace to this label.
 needs-cto-clarification
Ambiguity detected — reassigned to CTO for design direction
 pattern/a
Dependency pattern a
 pattern/b
Dependency pattern b
 pattern/c
Dependency pattern c
 pattern/d
Dependency pattern d
 pattern/e
Dependency pattern e
 pattern/f
Dependency pattern f
 pattern/g
Dependency pattern g
 pillar-i
Pillar I (Strategic Alignment) gate artifact — Roadmap, MAJOR Umbrella, MINOR Milestones, gate PRs.
 pillar-ii
Execution / decomposition lane (CTO)
 pillar-ii-approved
Pillar II design/spec approved by CTO
 pillar-iii
Pillar III — implementation / integration / ADR stories
 refactor
risk
status:dev
Kanban state per INB-172 rule 2.
 status:done
Kanban state per INB-172 rule 2.
 status:qa
Kanban state per INB-172 rule 2.
 status:triage
Kanban state per INB-172 rule 2.
 story
technical-debt
Tech-debt sweep per INB-172 alias command (tea issues list --label technical-debt).
 trd
type:epic
issue-hierarchy canon class (standards/issue-hierarchy.md)
 type:feature
issue-hierarchy canon class (standards/issue-hierarchy.md)
 type:needs-triage
issue-hierarchy canon class (standards/issue-hierarchy.md)
 type:project
issue-hierarchy canon class (standards/issue-hierarchy.md)
 type:task
issue-hierarchy canon class (standards/issue-hierarchy.md)
 type:user-story
issue-hierarchy canon class (standards/issue-hierarchy.md)
 v1.0
v1.4
v1.5
MINOR v1.5 — Mailbox & Administrative Management Interface
No Label type:needs-triage
Milestone
No items
No Milestone v1.5 - Mailbox & Administrative Management Interface
Projects
Clear projects
No project
Assignees
Clear assignees
coreci-bot coreci-cairo (Elena Voss (CAIRO)) coreci-ceo (Alexandra Reed — CEO) coreci-coo (Marcus Wright) grimacing jonathan (jonathan)
No Assignees frontend-engineer
4 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coreci/inboxos-v1#119
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?