Development record
Three build-plumbing comments still describe the pre-push gate and CI by an older, smaller shape. Same class as iss-37 (claims must match reality), in living files its re-scope does not cover, and no ledger entry records them until now. The fix direction is the same bar: state what actually runs, verified against the recipe or workflow beside the comment.
issueresolvedminoriss-182
Three build-plumbing comments still describe the pre-push gate and CI by an older, smaller shape. Same class as iss-37 (claims must match reality), in living files its re-scope does not cover, and no ledger entry records them until now. The fix direction is the same bar: state what actually runs, verified against the recipe or workflow beside the comment.
Makefile:58-61, thepreflightrecipe comment — "Pre-push gate (invoked by.githooks/pre-push): the same steps CI's check job runs — build, vet, test, and race-enabled internal tests — natively, plus the reviews-charter discipline." Two claims fail. CI's check job also runs agofmt -l .format gate, whichpreflightdoes not, so the step sets are not the same; and the recipe's own prerequisite line readspreflight: lint-reviews record-lint docs-lint, of which the comment names only the reviews-charter one. It also now contradictsCONTRIBUTING.md, which describes the real suite..githooks/pre-push:12-14— "The CI check-job trio (build/vet/test + internal race) must pass natively before a push leaves this machine. Secret-scan and workflow-audit lanes stay in Actions." The hook invokesmake preflight, which runs three lint gates ahead of those four Go steps, so the "trio" undercounts what the hook enforces; and the Actions-only list omits the reviews-charter job and the smoke job..github/workflows/ci.yml:3-4, the file header comment — "Lightweight checks on every push and pull request: build, vet, and test on macOS and Linux, plus full-history secret scanning and a workflow audit." It omits the check job'sgofmt, record-lint and docs-lint steps (all three gated to the ubuntu leg) and the reviews-charter and smoke jobs.
Scope note: comment-only corrections in all three files. No recipe, hook logic, workflow step, or gate behaviour changes.
Frontmatter
| id | iss-182 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-182-build-plumbing-comments-describe-an.md
open on GitHub ↗ · commit history ↗
mentions5
- dcn-26081900000000032026-08-19 — bughunt round 1 (branch bughunt-b/round-1): captured iss-291..iss-304 and fixed
- iss-37Phantom enforcement claims: developer docs describe gates that do not run as described. Re-scoped by the 2026-08-03 maintainer disposition to three doc-claim instances, each a claim about the local pre-push gate or CI:
- iss-318AGENTS.md and the ci.yml header enumerate CI separate jobs as a closed list that omits dependency-review and govulncheck
- iss-2608211142146585The release-gate runbook (.abcd/development/release-gate/README.md) misdescribes release.yml's verify job in two present-tense claims a maintainer reads at tag time. (1) It says the verify job runs the nine gates 'on macOS + Linux', but release.yml's verify job is runs-on: ubuntu-latest with no matrix — Linux only; the macOS coverage is ci.yml's check job. The gate_lockstep record-lint rule mirrors only the verify STEP NAMES, never runs-on, so the platform claim is outside its reach. (2) 'The verify job gates the merge' is false: verify runs post-merge on the tag/workflow_call; ci.yml's required checks gate the merge. Doc-accuracy family of resolved iss-182.
- iss-2608261133095909the pre-push hook restates a three-gate preflight roster while the recipe has five, and the preflight-gates drift detector omits the hook from its surface list, so the iss-182 drift recurred on the one unwatched surface