docs(plan): advance to application workspace

2026-08-10 11:17:14 +02:00
parent 4e5ce0c447
commit a54b70960c
6 changed files with 68 additions and 21 deletions
@@ -629,3 +629,13 @@
 - **Consequences:** UX-003 becomes the only in-progress package. JOBS remains explicitly incomplete rather than `DONE`; its live gates stay visible.
 - **User approval required:** No; this is tracking and safe local sequencing within the approved programme.
 - **Reversible:** Yes; JOBS can resume when live NAV or production verification becomes available.
+
+## DEC-064 — Use one accessible Kanban move state model
+
+- **Date:** 2026-08-10
+- **Decision:** Drive pointer and keyboard moves from the same picked-up job and active-column state. Use live theme variables for every surface/tone, Space to pick up/cancel, Enter or Space on a focused valid column to drop, and update local state only after the API succeeds.
+- **Reason/evidence:** the prior static light palette caused confirmed white columns in dark mode, while native drag alone exposed no target or keyboard semantics and rejected moves became unhandled promises. Shared state makes valid/active/invalid/selected/failure states consistent without replacing the precise status menu.
+- **Alternatives considered:** isolated dark hex colours; CSS-only drop feedback; optimistic moves with rollback; a second keyboard-only status implementation; replacing drag with a new library. These duplicate policy, risk stale UI or add unnecessary dependency/complexity.
+- **Consequences:** pointer and keyboard users receive the same server-confirmed behavior and announcements; custom `Other` remains visibly invalid. The existing exact-stage menu stays available and now has an accessible name.
+- **User approval required:** No; this is approved local UX/accessibility work with mocked browser APIs.
+- **Reversible:** Revert `fb6f17e` and `4e5ce0c`; no schema/data change is involved.