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

[story #119] Frontend: Mailbox Owner Dashboard (INB-1.5-A-S4) #143

Closed
saa wants to merge 1 commits from fe/INB-1.5-A-ui-impl into release/v1.5
pull from: fe/INB-1.5-A-ui-impl
merge into: coreci:release/v1.5
Conversation 1 Commits 1 Files Changed 31
+3557
saa commented 2026-06-10 23:49:32 +00:00
Collaborator
Copy Link
Copy Source

Story #119 — Implement Mailbox Owner Dashboard frontend

Pattern: B (impl). Domain: frontend. Assignee: @frontend-engineer.

Design bundle ref: #118 (closed, cto-approved).
API contract ref: #116 (closed, cto-approved).
A11y level: WCAG 2.2 Level AA.

Acceptance criteria

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

Deliverables

  • UI component: MailboxDashboard — three-column layout (sidebar + list + detail) per UX spec.
  • API adapter: Type-safe client for /api/v1/mailbox/messages endpoints (list, get, patch status).
  • Tests: 16 unit/component tests (rendering, search, filter, status update, error, a11y, keyboard).
  • Storybook stories: 4 stories (Default, WithDetail, EmptyState, WithPagination) with a11y addon.
  • Observability: useErrorReporting and usePerformanceMetrics hooks integrated.
  • Design-system lint: Clean — all colors/spacing/typography use token vars.

Component reuse

  • AppShell, SidebarNav, ResponsiveGrid (from D-S3 #134)
  • StatusBadge, Loading, EmptyState (from D-S3 #134)
  • Design-system tokens (tokens.css, tokens.ts)

Co-Authored-By: Paperclip noreply@paperclip.ing

## Story #119 — Implement Mailbox Owner Dashboard frontend **Pattern:** B (impl). **Domain:** frontend. **Assignee:** @frontend-engineer. **Design bundle ref:** [#118](/jc-capital/inboxos/issues/118) (closed, cto-approved). **API contract ref:** [#116](/jc-capital/inboxos/issues/116) (closed, cto-approved). **A11y level:** WCAG 2.2 Level AA. ### Acceptance criteria - [x] Dashboard renders mailbox list with search/filter. - [x] Archive / mark-processed actions wired to backend API contract. - [x] Responsive and passes design-system lint. ### Deliverables - **UI component:** `MailboxDashboard` — three-column layout (sidebar + list + detail) per UX spec. - **API adapter:** Type-safe client for `/api/v1/mailbox/messages` endpoints (list, get, patch status). - **Tests:** 16 unit/component tests (rendering, search, filter, status update, error, a11y, keyboard). - **Storybook stories:** 4 stories (Default, WithDetail, EmptyState, WithPagination) with a11y addon. - **Observability:** `useErrorReporting` and `usePerformanceMetrics` hooks integrated. - **Design-system lint:** Clean — all colors/spacing/typography use token vars. ### Component reuse - `AppShell`, `SidebarNav`, `ResponsiveGrid` (from D-S3 #134) - `StatusBadge`, `Loading`, `EmptyState` (from D-S3 #134) - Design-system tokens (`tokens.css`, `tokens.ts`) Co-Authored-By: Paperclip <noreply@paperclip.ing>
saa added 1 commit 2026-06-10 23:49:33 +00:00
[story #119] Frontend: Mailbox Owner Dashboard component (INB-1.5-A-S4) fa946fbc2e 
- MailboxDashboard component with email list, search/filter, detail view
- Type-safe API adapter for mailbox endpoints (listMessages, getMessage, patchStatus)
- MailboxApiError class for structured error handling
- Client-side observability hooks (useErrorReporting, usePerformanceMetrics)
- 16 unit tests covering rendering, interactions, accessibility, error states
- Storybook stories with a11y addon enabled (4 stories: Default, WithDetail, EmptyState, WithPagination)
- Conforms to UX spec (#118) and API contract (#116)
- Reuses design-system tokens, AppShell, SidebarNav, StatusBadge components
- WCAG 2.2 Level AA: role=list, aria-label, aria-current, keyboard nav, focus-visible
- Responsive: three-column (lg), two-column (md), single-column (sm)
- Design-system lint clean: no hardcoded colors, all tokens/var() references

Co-Authored-By: Paperclip <noreply@paperclip.ing>
saa closed this pull request 2026-06-11 01:07:54 +00:00
saa commented 2026-06-11 01:07:55 +00:00
Author
Collaborator
Copy Link
Copy Source

Duplicate of #119. Closing to eliminate half-filled mirror. Original story carries full metadata.

Duplicate of #119. Closing to eliminate half-filled mirror. Original story carries full metadata.

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No Reviewers
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
Milestone
No items
No Milestone
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
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coreci/inboxos-v1#143
Delete Branch "fe/INB-1.5-A-ui-impl"

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?