Column mutations lack board-visit and operation-order ownership

[Chris0Jeky]

Summary

columnStore has the same selected-board asynchronous ownership gaps now fixed for labels/comments/cards, but its writes also share the board's ordered column set:

• create/update/delete/reorder responses authorize local commits using only the current board id, so A→B→A can reuse an old visit;
• overlapping reorders and column writes execute concurrently even though the API exposes no revision/If-Match precondition, allowing server commit order and client settlement order to diverge;
• a queued pre-logout intent would start with whichever authentication token exists when its transport eventually runs if serialization is added without a session gate;
• deleteColumn filters currentBoardCards after every successful response, even when another board/session now owns that collection;
• an already-started old-visit write that succeeds while the same board is reopened currently has no bounded authoritative reconciliation rule.

Expected contract

• One per-board mutation lane serializes create/update/delete/reorder in user-intent order; unrelated boards remain independent.
• The first intent starts transport immediately. A genuinely queued intent rechecks the initiating board-visit generation before invoking the API, so logout/login or A→B→A cannot run old intent under a later session.
• Post-await state, toast, error and loading writes are scoped to the initiating visit.
• A successful already-started write from an older visit performs a bounded getColumns reconciliation only when that same board is currently reopened; it never patches another board.
• Same-board detail refreshes during a write remain compatible: create deduplicates stable ids, update patches the current array, delete removes only current-board state, and reorder installs its confirmed result.
• A newer same-board mutation prevents an older reconciliation read from overwriting it.

Acceptance

• Deferred-promise regressions for reverse-settling reorders, queued mutation after navigation/logout, late delete after navigation, same-board refresh during write, and A→B→A post-write reconciliation.
• No production API/DTO/schema change.
• Frontend lint, typecheck, build, focused/full tests and exact-head hosted CI pass.

Audit provenance

Found during the 2026-09-20 selected-board asynchronous integrity pass after #3302, #3304 and #3312. Kept in columnStore.ts to avoid overlap with the shared loading/session-epoch follow-ups #3305 and #3306.

[Chris0Jeky]

[Codex lane claim v2]

• lane: alpha-product-trust
• base: 307c3b8b50bec1cb0bfaea3e570a942bcb1d4451
• owned paths: frontend/taskdeck-web/src/store/board/columnStore.ts plus one focused column-mutation ordering spec
• shared-path leases: none
• parallel-safe work: avoids card, label, comment, assignment-registry, capture and shared loading/session files already active in fix(labels): bind async commits to their board #3302/fix(comments): order shared cache settlements #3304/fix(capture): require write access for board attachment #3310/fix(board): serialize per-card move and delete settlements #3312/fix(board): own assignment saves beyond lane lifetime #3313
• status: add deferred-promise negative controls first, then one per-board mutation lane with board-visit gating and bounded stale-visit reconciliation

[Chris0Jeky]

[Codex lane claim v2]

• lane: alpha-product-trust, coordinator continuation of the existing PR fix(board): preserve column and assignment save ownership #3315
• base: a62d1ec; existing source head a1264ab
• owned paths: columnStore.ts and its focused tests; bounded boardState/boardCrudStore/boardStore route-visit invalidation wiring, BoardView.vue and direct lifecycle tests
• shared-path leases: this coordinator owns the new route-visit signal; card/comment/label/assignment mutation implementations remain outside this repair. The broader In-flight board mutations can repopulate cleared state after logout #3306 session-epoch acceptance remains open.
• ownership reconciliation: prior claim and remote head show no activity since 2026-09-20. Continue the existing commits in a new isolated checkout; preserve the old worktree. Any unexpected remote-head advance stops this continuation rather than overwriting another writer.
• parallel-safe work: integration fix(trust): integrate session and MCP ownership protections #3355 owns the session/MCP/quota wave and lands first; this repair follows that integration. Only the coordinator updates its bounded STATUS section.
• status: reproduce real BoardView departure with retained board payload, fix queued/settled column ownership, and correct the three raw-array/proxy identity assertions without weakening their unchanged-state checks. One blocker-only repair round, then focused/full frontend and exact-head CI.

[Chris0Jeky]

Claim released after #3315 merged at 346b3c7. This issue is verified closed and its Project item is Done. Source history and exact-head proof were retained; owned worktree evidence is archived under .runtime-codex/2026-09-22-hard-impact/board-integrated/. No human decision was inferred.