The keyboard navigation change proposal still describes a gap that is already closed

[rubenvdlinde]

What happens

openspec/changes/kanban-task-detail-keyboard-navigation/proposal.md says a task card has "no interaction path to task detail at all, mouse or keyboard". That is no longer true. Anyone who reads the change, or its tracking issue #346, concludes the board is still inaccessible, and may pick the work up again.

Why

Read at development 6fa5ef5.

• src/views/ProjectBoard.vue:125-165 renders each card with role="button", tabindex="0", an aria-label, and @click, @keydown.enter and @keydown.space calling navigateToTask(task). A per-card "Move task to another column" menu is the keyboard equivalent of drag and drop.
• All 8 tasks in the change's tasks.md are checked. None is open.
• openspec/specs/kanban-board.md:155 already has "Board is keyboard-navigable (WCAG AA)" checked.
• The change was never archived, and [OpenSpec] kanban-task-detail-keyboard-navigation #346 is still open.
• The proposal's line citations (ProjectBoard.vue:88-97, :290-360, src/store/projects.js:697) point at code that has since moved.

Fix direction

1. Run /opsx-verify on the change, then /opsx-archive it, syncing its delta spec into openspec/specs/kanban-board.md.
2. Close [OpenSpec] kanban-task-detail-keyboard-navigation #346.

Live check

1. Open a project board. Press Tab until a card is focused, then Enter. Expected: the task detail page opens.
2. Focus a card's action menu and move the task to another column with the keyboard only.

Matrix rows

brd-keyboard-move in openspec/parity/capabilities.json (PR #645), rated yes for Planninq.

[github-actions]

Thank you for opening this issue! It has been assigned to @rubenvdlinde for review.

What happens next:

1. A maintainer will review this issue and determine the appropriate action
2. If accepted, it may be converted into an OpenSpec change for structured development
3. You will be notified of any status changes

Triage labels:

• triage:accept-feature — accepted as a new feature
• triage:accept-bugfix — accepted as a bug fix
• triage:needs-info — more information needed
• triage:wontfix — will not be addressed
• triage:duplicate — duplicate of another issue