Spec History Archive — 2026-03-09
Purpose
Historical archive index created before compacting the main workspace Spec. The active Spec should stay operational and lightweight; deeper historical context belongs here and in the referenced task notes.
Source
- Workspace note:
Spec Archive 2026-03-09 - Note ID:
3e14a7ba-cdb8-49ed-b789-14395d92eb0a - Intent: preserve pre-compaction history in repository-friendly markdown
Latest verified state as of 2026-03-09
- Corrected rich-stem live-critical flow passed in Chromium, Firefox, and WebKit on the then-current live stack.
- Verified command at archive time:
op run --env-file env.1password -- bash -lc 'cd frontend && npm run test:e2e:critical-live -- --project=critical-live-chromium --project=critical-live-firefox --project=critical-live-webkit tests/e2e/live-critical/questions-rich-stem.live.spec.ts'
- Question-page Bits/shared accessible primitives migration was complete for the intended scope.
- MCQ choices/options remained plain-text inputs by decision.
- Earlier WebKit blocker narratives were superseded by the corrected editor-readiness targeting and updated toolbar contract.
Historical investigation index
Question authoring / live-critical rich-text chain
86592860-1772-44f8-a11c-8561bb8b127f— Implement global Playwright guardrails for live critical flowsb26faba9-ef93-41d5-ac78-a134b3b30f03— Fix/questionslive accessibility violation surfaced by new axe guardrails17627e2d-7420-40fe-a2c3-027bfce845ce— Fix live rich-text toolbar keyboard/focus path under critical Playwright guardrails1a47371d-fada-4015-8e1e-143bc2e0f253— Fix WebKit toolbar Tab focus in live-critical rich-text flow76d912ab-debe-4ec2-949c-baec2e077cbd— Create minimal reproduction and upstream investigation for WebKit Tab handling in live-critical rich-text flow2aaee77d-3b8d-4d10-ba08-56928cd0b87b— Refresh live frontend runtime and rerun corrected WebKit live-critical specd2dee3ac-2776-4f16-922a-2177d5b562b3— Fix preview-drawer focus restoration after close in live-critical question flow
Question-page accessibility / Bits migration
383df97b-3546-4855-a10a-62b34116964c— Audit and migrate the question creation page onto correct Bits/shared accessible primitives79f369a6-6973-4197-9ba3-977dd57d0dd0— Audit/questionsdetail-route scope and Bits UI applicability8256ca24-c069-4998-bd6a-853a12c4f68c— Harden/questions/[id]authoring flow and shared accessibility primitives
Broader workspace operational history
30e99b2b-9f65-4551-8b57-cedde448d6b4— Recover current workspace API reachability980b9266-d1c3-468d-b5fd-1ac2fa47cce7— Verify local and tunneled API recoveryba53b912-d72b-45d4-b9ab-b636f038f20f— Audit frontend hydration failure on current workspace stackc23e7ad1-5ae9-4ac0-bd60-c6344df1cf66— Fix frontend shell/layout hydration regression891ce201-0d7c-44da-a823-ece06b24a88f— Verify frontend hydration recovery on current workspace stack
Preserved open-work index after compaction
The compact active Spec can stay concise while this archive preserves the related open-work references that existed at compaction time:
0dd9b8a5-453e-4dc5-822c-020fca2f8b96— Audit mocked Playwright specs for promotion into live-critical real-API coverage914f2b45-789e-4197-ab8c-98766ced48e1— Extend shared rich editor to question choice text0809bdd6-c732-4678-9c49-ab83e5058a24— Harden shared rich-authoring platform for cross-surface reuse1f82b08a-09f5-4d60-bbdc-8d29a26ad094— Frontend local-first new-question route and browser draft lifecycle73d8be2c-8642-41d1-8693-25900b0afeb3— Atomic first-save question API03a3371b-32ae-4bbd-90a8-028e90103920— Retire the hidden-parent fallback and clean up legacy orphan rows1644ce31-6726-49d8-be4c-9c46889d107a— Reconfigure dev workflow for tunnel-always-on with HMR opt-in9bd7978e-149f-402b-a7c9-9e47361f609a— Verify tunnel-always-on and HMR-default-off workflowb1da91b0-6e32-43fc-b3b7-426a09c3e75a— Apply non-destructive database migrations to the active local stack
Archive policy
- The main Spec remains the operational working document.
- Detailed attempt logs, superseded hypotheses, and long verification histories should live in task notes and archive records, not in the active Spec.
- When deeper historical context is needed, start with the task IDs and titles captured above.