Skip to content

chore(board): mark v2.rev.0020 + v2.release.0002-0006 done#141

Merged
SUaDtL merged 1 commit into
mainfrom
chore/board-mark-done
Jun 26, 2026
Merged

chore(board): mark v2.rev.0020 + v2.release.0002-0006 done#141
SUaDtL merged 1 commit into
mainfrom
chore/board-mark-done

Conversation

@SUaDtL

@SUaDtL SUaDtL commented Jun 26, 2026

Copy link
Copy Markdown
Collaborator

Board hygiene. Flips six tasks to done (2026-06-26):

Docs/state only (.codearbiter/open-tasks.md); no code, no payload change. Resolves the known board drift in one pass.

v2.rev.0020 (farm.ts god-module split) landed via #140. The five
release-skill hardening tasks v2.release.0002-0006 landed via #138 but the
board was never updated in that PR. Flip all six to done (2026-06-26).

Claude-Session: https://claude.ai/code/session_0123LEtLuVCEzLMhWdktP7aC
@SUaDtL
SUaDtL merged commit 3dbfd14 into main Jun 26, 2026
17 checks passed
@SUaDtL
SUaDtL deleted the chore/board-mark-done branch June 26, 2026 16:52
SUaDtL added a commit that referenced this pull request Jun 26, 2026
)

A task isn't done until its PR merges, but open-tasks.md is itself versioned,
so a board flip only goes live when its own change merges to main. That created
a trap with no good side: flips drifted into lagging chore(board) PRs or
post-commit edits that depended on cross-session memory, and silently fell off
(#138 never marked v2.release.0002-0006 done; #140 needed the separate #141).

ADR-0008 makes commit-gate the single board-sync chokepoint, co-locating the
flip with the work commit: it is invisible on main until merge, lands atomically
when the work does, and an abandoned PR abandons the flip with it -- so the
"don't mark done before merge" and "don't lose the board update" rules become
the same, self-correcting rule. No task-to-commit inference is introduced; the
human still declares the transition via /ca:task.

Mechanism: a new pure _taskboardlib.classify_board_diff recognizes a clean
done/start/add transition vs an arbitrary board edit; commit-gate Phase 6 retains
a classified transition instead of flagging it as scope creep; Phase 7 stages it
by explicit path; the raise-new harvest moved to Phase 7 (pre-commit) so a
discovered follow-up rides the work commit (contingent default -- a must-survive
follow-up is filed as a GitHub issue). A read-only /ca:standup advisory sweep
(hooks/boardsync.py reconcile, best-effort) surfaces any merged-but-not-flipped
task; the fix still routes through /ca:task. Conflict-hierarchy level:
maintainability/reliability (SMARTS, per ADR-0008).

Folds into the unreleased 2.6.0 (payload already ahead of tag v2.5.2; no
over-bump). All 10 plan tasks shipped test-first; full tech-stack suite green;
security review PASS (one LOW hardened).

CHANGELOG: commit-gate now lands task-board done/start/add transitions in the
same commit as the work (no separate chore(board) PR); /ca:standup gains a
read-only drift sweep for any merged-but-not-flipped task.
Closes #142
Ref: ADR-0008
Claude-Session: https://claude.ai/code/session_018n3e8e2RWU7hLzzJjEAscb

Co-authored-by: SUaDtL <SUaDtL@users.noreply.github.com>
SUaDtL added a commit that referenced this pull request Jun 27, 2026
)

A task isn't done until its PR merges, but open-tasks.md is itself versioned,
so a board flip only goes live when its own change merges to main. That created
a trap with no good side: flips drifted into lagging chore(board) PRs or
post-commit edits that depended on cross-session memory, and silently fell off
(#138 never marked v2.release.0002-0006 done; #140 needed the separate #141).

ADR-0008 makes commit-gate the single board-sync chokepoint, co-locating the
flip with the work commit: it is invisible on main until merge, lands atomically
when the work does, and an abandoned PR abandons the flip with it -- so the
"don't mark done before merge" and "don't lose the board update" rules become
the same, self-correcting rule. No task-to-commit inference is introduced; the
human still declares the transition via /ca:task.

Mechanism: a new pure _taskboardlib.classify_board_diff recognizes a clean
done/start/add transition vs an arbitrary board edit; commit-gate Phase 6 retains
a classified transition instead of flagging it as scope creep; Phase 7 stages it
by explicit path; the raise-new harvest moved to Phase 7 (pre-commit) so a
discovered follow-up rides the work commit (contingent default -- a must-survive
follow-up is filed as a GitHub issue). A read-only /ca:standup advisory sweep
(hooks/boardsync.py reconcile, best-effort) surfaces any merged-but-not-flipped
task; the fix still routes through /ca:task. Conflict-hierarchy level:
maintainability/reliability (SMARTS, per ADR-0008).

Folds into the unreleased 2.6.0 (payload already ahead of tag v2.5.2; no
over-bump). All 10 plan tasks shipped test-first; full tech-stack suite green;
security review PASS (one LOW hardened).

CHANGELOG: commit-gate now lands task-board done/start/add transitions in the
same commit as the work (no separate chore(board) PR); /ca:standup gains a
read-only drift sweep for any merged-but-not-flipped task.
Closes #142
Ref: ADR-0008
Claude-Session: https://claude.ai/code/session_018n3e8e2RWU7hLzzJjEAscb

Co-authored-by: SUaDtL <SUaDtL@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant