Development record
docs says the release workflow runs the lint's release-gate mode while the scaffolded release template never names the verb; launch says abcd's own release workflows are regenerated byte-exact from those templates
docs says the release workflow runs the lint's release-gate mode while the scaffolded release template never names the verb; launch says abcd's own release workflows are regenerated byte-exact from those templates
A premise contradiction (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/brief/04-surfaces/10-docs.md:131— "The release workflow's docs-currency step runs the lint in its release-gate mode; CI's step and thedocs-lintmake target each run the lint in its plain mode, the scaffolded release template names the verb nowhere" - End B:
.abcd/development/brief/04-surfaces/04-launch.md:216— "The workflows ship from embedded templates, one per file, that abcd's own release workflows are regenerated from, proved byte-exact by a test, so a scaffolded repo and this one cannot drift."
10-docs.md says the release workflow's docs-currency step runs the lint in its release-gate mode, and that the scaffolded release template names the verb nowhere. 04-launch.md says abcd's own release workflows are regenerated from the embedded templates and a test proves them byte-exact, so a scaffolded repo and abcd cannot drift. If abcd's workflow is byte-exact with the template, the template carries the release-gate step and names the verb. If the template names no such step, abcd's workflow is not byte-exact or does not carry it.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 279.
Grounds
- declined: Closed in the 2026-10-27 triage (dcn-2610271112330536): the two ends do not conflict when read in full. internal/core/launch/scaffold/substitutions.go defines abcdExtraGates (including lint docs --release-gate) apart from the template, which only ranges over ExtraGates; docsreleasegate_workflow_test.go renders the template with abcd's substitutions.
Frontmatter
| id | iss-2610262032317368 |
|---|---|
| type | issue |
| lifecycle | wontfix |
| severity | minor |
.abcd/work/issues/wontfix/iss-2610262032317368-docs-says-the-release-workflow-runs-the.md
open on GitHub ↗ · commit history ↗
mentions2
- dcn-26102711123305362026-10-27 — The product thinker accepted on 2026-10-27 the triage of the 1301 records the 2026-10-26 consistency pass filed. The duplicates, the records a later record already settles, the ones that are no contradiction and the one already fixed are closed with each reader's reason. Every other record gets its fix as its remedy, the rulings' accepted answers included, so a drain can take it. The 45 major records left open are deferred past v0.15.1, because the brief's single-home rewrite rewrites or removes most of the passages they quote. The person ruled the major rulings one at a time; the minor rulings take their recommended answers.
- iss-2610262036512603itd-93 says abcd's release workflows are generated from the one scaffold template, so abcd runs exactly what a managed repo gets; the docs chapter says abcd's release workflow has a docs-currency step that the scaffolded template never names