docs: fix stale Vitest note in FRONTEND-TOOLING + update RFC-WS-FRONTEND-PRIMEVUE §13 Storybook entry

dev-docs/FRONTEND-TOOLING.md

@@ -62,9 +62,9 @@ backstop.
 
 ## Vitest
 
-Runs against `apps/portal/`. `apps/app/` has no test suite yet —
-build + typecheck are its only automated gates. Bringing Vitest
-coverage to `apps/app` is a separate backlog item.
+Runs against `apps/portal/` and `apps/app/`. `apps/app/` has a
+Vitest test suite (402 tests as of May 2026); run with `pnpm test`
+from `apps/app/`.
 
 ## Storybook
 

dev-docs/RFC-WS-FRONTEND-PRIMEVUE.md

@@ -409,7 +409,7 @@ To prevent ambiguity, decisions deliberately deferred:
 - **Sakai or other PrimeVue admin templates.** None will be adopted; layout shells are hand-rolled to avoid template lock-in.
 - **CSS-in-JS migration (e.g., Pinceau, Vanilla Extract).** Out of scope; Aura tokens + Tailwind utilities cover all cases.
 - **State machine for form wizards** (e.g., XState). Out of scope; existing `useFormSteps.ts` remains.
-- **Storybook or component playground.** Useful but out of scope; revisit post-launch.
+- ~~**Storybook or component playground.**~~ **Landed post-RFC** (Storybook 10, commit ebb8e3bc). See `dev-docs/FRONTEND-TOOLING.md` § Storybook.
 
 ---