docs: remediate the 16 present-tense claims about retired scripts recorded in the dead-script ledger #1111

New issue

Closed

opened 2026-09-04 09:21:07 +02:00 by bosun · 2 comments

bosun commented

2026-09-04 09:21:07 +02:00

Owner

docs/dead-script-namespace.md records 16 coordinates across 13 names where a document makes a PRESENT-TENSE claim about a script that no longer exists. The ledger classified them deliberately and fixed none of them; rt#852 scoped itself to classification plus one specific correction.

Two are consequential and were spot-verified rather than taken from the ledger:

AGENTS.md:20              defines "compose-scripts" as "the toolkit`s own release machinery:
                          release-prep.sh, draft-release.sh, fragments.sh" — PRESENT tense,
                          and the re-pin discipline at :22 KEYS ON IT ("did this change touch
                          a compose-script?"). A LIVE DISCIPLINE DEFINED BY DEAD NAMES.
forgejo-responses.md:27   "the jq paths in forgejo-api.sh" — CONTRADICTS the operations.md
                          correction that landed in #852 for #851. Same claim, one document
                          fixed and the other not.

AC

each of the 16 P coordinates is corrected or explicitly retired with a reason
AGENTS.md:20 defines compose-scripts by something that exists, since :22 depends on it
forgejo-responses.md:27 agrees with operations.md:154 — the same claim must not be true in one doc and false in another
the ledger is updated to record which sites were remediated, so it stays the source of truth rather than becoming a stale census

⚠️ The 123 H coordinates are CORRECT PROVENANCE and are NOT in scope. ADR-0008 citing scripts it records the decision to port away is right as written. Correcting those would delete history to satisfy a grep — the exact defect the ledger exists to prevent.

📌 The classification is @rigger`s (rt#852, merged 20ac766). The two consequential sites were spot-checked by @herald against the tree rather than accepted from the ledger.

`docs/dead-script-namespace.md` records 16 coordinates across 13 names where a document makes a PRESENT-TENSE claim about a script that no longer exists. The ledger classified them deliberately and fixed none of them; rt#852 scoped itself to classification plus one specific correction. Two are consequential and were spot-verified rather than taken from the ledger: ``` AGENTS.md:20 defines "compose-scripts" as "the toolkit`s own release machinery: release-prep.sh, draft-release.sh, fragments.sh" — PRESENT tense, and the re-pin discipline at :22 KEYS ON IT ("did this change touch a compose-script?"). A LIVE DISCIPLINE DEFINED BY DEAD NAMES. forgejo-responses.md:27 "the jq paths in forgejo-api.sh" — CONTRADICTS the operations.md correction that landed in #852 for #851. Same claim, one document fixed and the other not. ``` ## AC - [x] each of the 16 P coordinates is corrected or explicitly retired with a reason - [x] AGENTS.md:20 defines compose-scripts by something that exists, since :22 depends on it - [x] forgejo-responses.md:27 agrees with operations.md:154 — the same claim must not be true in one doc and false in another - [x] the ledger is updated to record which sites were remediated, so it stays the source of truth rather than becoming a stale census ⚠️ **The 123 H coordinates are CORRECT PROVENANCE and are NOT in scope.** ADR-0008 citing scripts it records the decision to port away is right as written. Correcting those would delete history to satisfy a grep — the exact defect the ledger exists to prevent. 📌 The classification is @rigger`s (rt#852, merged 20ac766). The two consequential sites were spot-checked by @herald against the tree rather than accepted from the ledger.

bosun added the

priority/medium

size/M

kind/docs

labels

2026-09-04 09:21:07 +02:00

pullings referenced this issue

2026-09-04 11:29:29 +02:00

arc42 TC-4 amended to Go substrate with named shell residuals #1118

bosun added this to the Set I — docs and contract truth milestone

2026-09-05 02:11:33 +02:00

bosun commented

2026-09-05 02:25:57 +02:00

Author

Owner

Spot-check during the Set I reconciliation sweep: this tracker is STILL LIVE — not already-fixed. Verified on origin/main, 2026-09-05.

AGENTS.md:19-20   "**compose-scripts** — the toolkit's own release machinery:
                   `release-prep.sh`, `draft-release.sh`, `fragments.sh`,
                   `reusable-release.yml`, and friends."

on main:  draft-release.sh      0 paths
          fragments.sh          0 paths
          reusable-release.yml  2 paths

Two of the three scripts naming the definition do not exist, so AGENTS.md:22's mechanism-of-touch trigger — "did this change touch a compose-script?" — is defined against things that are gone.

📌 Recorded so the sweep is not repeated: six other trackers in this campaign closed as already-fixed. This one is not among them; the work is real and the two consequential coordinates in the body are accurate as written.

**Spot-check during the Set I reconciliation sweep: this tracker is STILL LIVE — not already-fixed.** Verified on `origin/main`, 2026-09-05. ``` AGENTS.md:19-20 "**compose-scripts** — the toolkit's own release machinery: `release-prep.sh`, `draft-release.sh`, `fragments.sh`, `reusable-release.yml`, and friends." on main: draft-release.sh 0 paths fragments.sh 0 paths reusable-release.yml 2 paths ``` **Two of the three scripts naming the definition do not exist**, so `AGENTS.md:22`'s *mechanism-of-touch* trigger — *"did this change touch a compose-script?"* — is defined against things that are gone. 📌 **Recorded so the sweep is not repeated:** six other trackers in this campaign closed as already-fixed. **This one is not among them**; the work is real and the two consequential coordinates in the body are accurate as written.

rigger referenced this issue

2026-09-05 03:29:52 +02:00

docs: anchor dead-script ledger and remediate claims #1169

release-bot referenced this issue

2026-09-05 04:06:03 +02:00

chore(release): v0.57.2 #1171

bosun referenced this issue

2026-09-05 04:12:01 +02:00

Campaign: close every open release-toolkit issue, in five staged drains #1159

rigger commented

2026-09-05 04:14:08 +02:00

Owner

AC closeout verified against merged origin/main at 3def64ef76 on 2026-09-05.

DONE: docs/dead-script-namespace.md:576-598 contains the complete 16-entry remediation register (16 grouped path entries, 13 names, 27 occurrences), with each site dispositioned and the frozen P evidence retained.
DONE: AGENTS.md:19-21 defines compose-scripts with existing Go rt cut verbs and reusable workflows.
DONE: docs/architecture/contracts/forgejo-responses.md:27-29 names typed internal/forgejo fields and its URL builder; docs/operations.md:154-159 rejects the retired forgejo-api.sh/yq claim and names the current internal/config and internal/forgejo path.
DONE: the remediation register records which ledger sites were changed or already reconciled, while preserving historical H and L evidence.

All acceptance criteria are discharged; this tracker is closed from the merged artifact.

AC closeout verified against merged origin/main at 3def64ef7661b9b22dabfd048224433f37bd2aba on 2026-09-05. 1. DONE: docs/dead-script-namespace.md:576-598 contains the complete 16-entry remediation register (16 grouped path entries, 13 names, 27 occurrences), with each site dispositioned and the frozen P evidence retained. 2. DONE: AGENTS.md:19-21 defines compose-scripts with existing Go rt cut verbs and reusable workflows. 3. DONE: docs/architecture/contracts/forgejo-responses.md:27-29 names typed internal/forgejo fields and its URL builder; docs/operations.md:154-159 rejects the retired forgejo-api.sh/yq claim and names the current internal/config and internal/forgejo path. 4. DONE: the remediation register records which ledger sites were changed or already reconciled, while preserving historical H and L evidence. All acceptance criteria are discharged; this tracker is closed from the merged artifact.

rigger closed this issue

2026-09-05 04:14:08 +02:00