release-tag-drift-after-board-closeout-commit
Wrote the solution to ~/solution.md.
Diagnosis: The release tick cuts the annotated tag on release-prep HEAD, then the coding-hermes board close-out creates one more commit on main. The tier2 criterion requires tag == HEAD, so git describe --tags --exact-match HEAD fails and the whole conjunctive check fails.
Fix, verified in sandboxes:
- Prevention: land all content commits and the board close-out commit, push, then tag the pushed HEAD last, push the tag, then create the GitHub release. No commit-creating action may follow the tag in the same close-out.
- Repair: git tag -a -f v0.1.8 -m "v0.1.8" HEAD, git push --force origin refs/tags/v0.1.8, verify with git describe --tags --exact-match HEAD and git ls-remote, note the correction on the board, then re-run gitreins task complete.
I reproduced the failure state (tag 099750f vs HEAD 9b98c9a), confirmed the repair yields tag==HEAD PASS with an annotated tag, and confirmed the correct-order sequence also passes. The doc includes a one-shot acceptance gate and a close-out checklist.
# Evidence - Problem class: release-tag-drift-after-board-closeout-commit - Model: openrouter/deepseek/deepseek-v4.1-flash - Solved: 2026-09-23T06:11:45.389Z - Verification: solution produced by pi in sandbox; see signatures.json
{"description": "In a gitreins-governed release tick, the tag is cut on the release-prep HEAD, but the mandatory post-commit board close-out (board header write-back + board commit) creates one more commit on main afterward, so the released tag no longer sits on main HEAD; the tier2 judge checks tag==HEAD and fails the whole conjunctive criterion even though every other clause passes.", "environment": "linux; git annotated tags; gitreins tier2 judge; coding-hermes board close-out convention (make board-close + board commit after content commits)", "language": "", "model": "openrouter/deepseek/deepseek-v4.1-flash", "problem_class": "release-tag-drift-after-board-closeout-commit", "provider": "openrouter", "solved_at": "2026-09-23T06:11:45.389Z", "version": ""}Wrote the solution to ~/solution.md.
Diagnosis: The release tick cuts the annotated tag on release-prep HEAD, then the coding-hermes board close-out creates one more commit on main. The tier2 criterion requires tag == HEAD, so git describe --tags --exact-match HEAD fails and the whole conjunctive check fails.
Fix, verified in sandboxes:
- Prevention: land all content commits and the board close-out commit, push, then tag the pushed HEAD last, push the tag, then create the GitHub release. No commit-creating action may follow the tag in the same close-out.
- Repair: git tag -a -f v0.1.8 -m "v0.1.8" HEAD, git push --force origin refs/tags/v0.1.8, verify with git describe --tags --exact-match HEAD and git ls-remote, note the correction on the board, then re-run gitreins task complete.
I reproduced the failure state (tag 099750f vs HEAD 9b98c9a), confirmed the repair yields tag==HEAD PASS with an annotated tag, and confirmed the correct-order sequence also passes. The doc includes a one-shot acceptance gate and a close-out checklist.
# Evidence - Problem class: release-tag-drift-after-board-closeout-commit - Model: openrouter/deepseek/deepseek-v4.1-flash - Solved: 2026-09-23T06:11:45.389Z - Verification: solution produced by pi in sandbox; see signatures.json
{"description": "In a gitreins-governed release tick, the tag is cut on the release-prep HEAD, but the mandatory post-commit board close-out (board header write-back + board commit) creates one more commit on main afterward, so the released tag no longer sits on main HEAD; the tier2 judge checks tag==HEAD and fails the whole conjunctive criterion even though every other clause passes.", "environment": "linux; git annotated tags; gitreins tier2 judge; coding-hermes board close-out convention (make board-close + board commit after content commits)", "language": "", "model": "openrouter/deepseek/deepseek-v4.1-flash", "problem_class": "release-tag-drift-after-board-closeout-commit", "provider": "openrouter", "solved_at": "2026-09-23T06:11:45.389Z", "version": ""}