Eight components under apps/app/src/components-v2/shared/ plus a
severity-map utility, seeded from amended spec §8 and enforced via the
bidirectional Vitest consistency test required by §8.X.
Carries forward two Plan 2-deviation cleanup tasks from spec-amend
commit ae0bd2da:
- (a) migrate 6 centralized stories from src/stories/v2/ to co-located
- (b) refactor AppTopbar to wrap PrimeVue Menubar per RFC AD-3
Also deletes the X.vue boundary-test stub and repoints
boundaries-v2.spec.ts at a real shared component.
Plan format follows Plan 1 precedent (REQUIRED SUB-SKILL header,
- [ ] task syntax, Definition of Done, Plans 4-5 outline). Execution
will happen in a fresh Claude Code session via
superpowers:subagent-driven-development.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
- §8 severity table now covers all 21 values of the 5 mirrored enums
(ShiftAssignment/ArtistEngagement/Payment/Person/MatchStatus); drops
3 phantom rows (active/inactive/expired, in no enum). Closes the
silent grey-fallback gap for 11 production values found in the
Plan 3 brainstorm self-audit.
- §6 stories-placement reworded: custom/wrapper components (incl.
PrimeVue wrappers) co-locate; only the ~80 PrimeVue catalog +
Foundations centralize. Plan 2 misread this.
- New §8.X: bidirectional Vitest consistency test
(apps/app/tests/unit/utils/statusSeverity.consistency.spec.ts),
added in Plan 3 — fails on any unmapped enum value OR orphan key.
Plan 3 cleanup tasks (tracked in the Plan 3 plan doc, not here):
(a) migrate Plan 2's 6 centralized stories to co-located.
(b) refactor AppTopbar to wrap PrimeVue Menubar per RFC AD-3.
Background: discovered during Plan 3 (Tier-1 primitives) brainstorm
self-audit. Fixes spec-vs-reality drift and two Plan 2 deviations
from binding spec/RFC text; prevents recurrence for future enums.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
All corrections audited against the codebase:
- §7.4 useWorkspaceStore ghost removed (computed over auth/org stores)
- §12 portal /portal/* verified in repo; observability is meta-based,
/api/v1/p/* is separate backend layer — no cross-doc conflict
- §3 getRouteName v2- name-prefix convention (route-name collision)
- §4 theme parallel-mode AD + useRightDrawer in useShellUiStore
- §8/§9 DraggableBlock is foundation, not Tier-4
- §3 single ESLint enforcement for definePage meta-key
- §8 StatusTag severity map; §14 brace-glob fallback; §13 CT/Storybook
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Brainstorming outcome: pivot the PrimeVue redesign to use crewli-starter
as the design source of truth, parallel /v2/ routes, PrimeVue-first
fidelity, page-by-page cutover. Supersedes F4a-F4d of
RFC-WS-FRONTEND-PRIMEVUE.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
