Development record
2026-07-24 — Next-run queue reshaped by the grill: the small consequences
decisiondcn-2607240000000005
2026-07-24 — Next-run queue reshaped by the grill: the small consequences fold into Track 1 (resolve iss-35; implement iss-122 pinning; amend + promote itd-93 — promotion only, implementation later as its own focused run); the spine stays friction fixes → itd-94 → walk fixes → itd-88. itd-28 implements in the following run against the adapter decision. Queue: plans/2026-07-24-next-run-queue.md (supersedes the 2026-07-18 queue file's pick-up role).
Frontmatter
| id | dcn-2607240000000005 |
|---|---|
| type | decision |
| date | 2026-07-24 |
.abcd/work/decisions/dcn-2607240000000005-next-run-queue-reshaped-by-the-grill-the.md
open on GitHub ↗ · commit history ↗
mentions6
- iss-35brief-vs-shipped-surface reconciliation: 05-internals/08-skills.md claims abcd ships zero user-facing skills and six top-level commands while 04-surfaces/README.md itself tables nine and /abcd:consult and /abcd:ingest are shipped; the shipped skills violate the brief criterion that any artefact mutation is a command, not a skill; the skills/ layout described (abcd-ahoy, commit-attribution, secrets-and-pii) is fictional vs the real consult/ and ingest/; the implemented, user-reachable abcd docs lint and abcd history verbs have no home in 04-surfaces at all; the operator-internal paragraph contradicts the commands/ directory that exists. Detector (per spec-moves-with-the-surface): a record-lint cross-check that every entry under commands/ and skills/ resolves to a brief surface row, and every brief surface row resolves to a shipped or explicitly staged surface. Acceptance corpus: each falsified claim above — the check fails on all of them today. Fix amends the criterion or the surface in one change, never silently.
- iss-122The iss35 crosscheck's scope and depth are unpinned, so the gate is not reproducible: v0.3.0's receipt records zero findings four days ago while a full-depth run (17 brief docs, both directions, 22 checkers) returns 102 discrepancies, and the receipt's own promptHash field is the literal 'no-pinned-prompt' admission. The maintainer choosing briefDocs per run means two honest runs of the same gate can disagree by two orders of magnitude; the gate needs a pinned input manifest and depth so a PROMOTE means the same thing every release.
- itd-28Spec-Tied Reviews Live Next To The Spec They Reviewed
- itd-88Know What a Repo Can and Cannot Tell You — Before You Trust the Lifeboat
- itd-93abcd Scaffolds a Release Gate That Works on the First Try
- itd-94An intent that is not planned cannot be implemented: abcd gains a machine-checkable implement-readiness gate that refuses with a remedy and offers the planning interview