feat(ui): share one token-backed status notice

[seonghobae]

Outcome

• adds shared StatusNotice (success / unavailable / retry) as current-main ADR 0214, superseding closed-branch ADR 0134 for protected main only
• migrates Calendar's Naruon fail-closed path so missing projection copy and the next action sit in one named region
• keeps retry on role="alert" with Retry; success and unavailable stay a named region so App live-region uniqueness (getByRole("status")) holds
• distinguishes kinds by label and glyph, not color alone (ADR 0099 tokens); never interpolates provider payloads (ADR 0123)

Independent of open stacks #579, #629, #631, #632, #636, #639, #640. Tracks #611; the issue stays open until remaining 0133/0135/0136/0137 slices ship on current main.

Verification

• corepack pnpm lint (0 warnings, 0 errors)
• corepack pnpm test (388 passed)
• corepack pnpm exec vitest run src/App.test.tsx -t "fails closed on the calendar" (passed)
• corepack pnpm build
• uv run --extra dev pytest -q tests/test_documentation_hygiene.py (5 passed)

Synthetic fixtures only. No keyword, heuristic, arbitrary threshold, or local measurement weight is introduced.

---

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

[coderabbitai]

Warning

Review limit reached

Next included review available in 59 minutes.

View limit details

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: fbfd56fe-589f-4de7-9c58-d97371b78b34

📥 Commits

Reviewing files that changed from the base of the PR and between fe17057 and 2956a21.

📒 Files selected for processing (16)

• AGENTS.md
• CHANGELOG.d/2.19.0-status-notice.md
• CLAUDE.md
• backend/tests/test_api.py
• docs/adr/0220-token-backed-status-notice.md
• docs/storybook-inventory.md
• frontend/src/App.css
• frontend/src/App.test.tsx
• frontend/src/components/StatusNotice.stories.tsx
• frontend/src/components/StatusNotice.test.tsx
• frontend/src/components/StatusNotice.tsx
• frontend/src/components/WorkspaceCalendar.stories.tsx
• frontend/src/components/WorkspaceCalendar.test.tsx
• frontend/src/components/WorkspaceCalendar.tsx
• frontend/src/i18n.ts
• lineageweave/naruon_calendar_workspace.py

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[seonghobae]

Exact-head UI audit: 041ec13b passed StatusNotice and WorkspaceCalendar component tests (8), lint, and Storybook build. The Unavailable scene was rendered and visually inspected at 1200×600 and 390×600: named state, message, and next action remain readable without horizontal overflow; the glyph plus visible label keeps state distinguishable without color alone. Screenshots used synthetic content and remain local, not committed.

[seonghobae]

Verified current head 041ec13 against ADR 0203: the unavailable branch intentionally renders the fail-closed notice before any event list, and the API contract returns events=[] when naruon_available=false. No actionable defect found in Devin note. Local Vitest: 9 targeted tests passed (StatusNotice, WorkspaceCalendar, Calendar App paths). Protected approval and hosted gates remain required.

[seonghobae]

Merged current protected-main base and retained both the StatusNotice and semantic-unit changelog entries. New exact head: 7fb4d18c69e18700229dbacb0690a891fb7b41ea. Hosted checks and independent review remain required.

[seonghobae]

Exact-head customer-copy audit at 8767de1b:

• Preserved the original shared StatusNotice intent, token-backed styling, fail-closed calendar evidence, named-region semantics, and retry alert contract.
• Corrected the calendar recovery contract at its source. The API and rendered notice no longer tell a customer to connect Naruon or a projection; they direct the customer to ask the workspace administrator to enable calendar access and to open an available commitment meanwhile.
• ADR 0220 now explicitly forbids customer-facing provider, model, transport, environment-variable, and projection names. Component, integration, Storybook, and API assertions pin that boundary.

Verification:

• tests/test_naruon_calendar_workspace.py: 9 passed.
• Focused StatusNotice, WorkspaceCalendar, App calendar, and i18n suite: 9 passed, 158 deselected.
• Frontend lint, production build, Storybook build, and git diff --check: passed.
• The live API integration test module was collected but stopped after 191 seconds because its stack-bound collection did not reach execution; no result is claimed for that test.
• Synthetic Storybook Workspace/WorkspaceCalendar/NaruonUnavailable was captured and directly inspected at 1280x720 and 390x844. The notice and commitment remained readable without clipping or horizontal overflow, the next action remained visible, and no provider/model/transport/environment/projection term appeared.
• The prior Strix failure was STRIX_PROVIDER_UNAVAILABLE, not a source-code finding; the new exact head will receive fresh protected checks normally.

Fresh hosted checks and independent current-head approval remain required.