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

Merged

bosun merged 3 commits from rigger/1119-1111-dead-script-anchors into main 2026-09-05 04:05:24 +02:00

Conversation 4 Commits 3 Files changed 9 +405 -119

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

Owner

Copy link

Refs frankenbit/release-toolkit#1119 and frankenbit/release-toolkit#1111.

Coordinate decision (#1119)

• The 96/274 current-main measurement was run against 468710a0baa0917e102010130c6784b04c3da9e6 on 2026-09-05, as recorded in docs/dead-script-namespace.md. Main later advanced to descendant 11d0745349de3404ffb87934f26d56dc7439c6c0, which was the branch base used for editing/rebasing, not a second source for that measurement. The classification boundary remains frozen source tree a9563b4263de0ae97661304661efee44143953a8 from 2026-08-26.
• The complete frozen ledger is 274 outer records: H=233, P=27, L=14. The current-main recheck before editing landed 96/274 and missed 178: H=78/233, P=13/27, L=5/14.
• The reported 268/99/169 measurement is retained as historical evidence. The six-record difference is the L shorthand that the earlier parse did not reach; it is not silently substituted.
• Decision: live line numbers do not remain. Each entry uses the frozen path, nearest section heading, and quoted frozen text; line numbers in L entries remain explicitly historical navigation citations. The re-verification cost and method are recorded in the ledger.
• The unchanged-file control was AGENTS.md: git diff --quiet a9563b4263de0ae97661304661efee44143953a8 returned exit 0 before this PR, frozen/current SHA-256 was f2bbac162fe2c3a9daabdb0d079354eee4529c564b0c3a8741492833998b91d2, and its control population was 24/24 with zero misses.

Remediation register (#1111)

• The register covers all 16 grouped path entries across 13 names and 27 line occurrences. Current P claims are updated in AGENTS.md, the changelog/fragment/Forgejo/property contract docs, and the consumer hook example in docs/integration.md.
• The Arc42 changelog and conventional-commits entries were already reconciled by #917 and remain current; they are recorded as such rather than changed here.
• Current Go sources are named for composition, fragment kinds, register patterns, semver tests, typed Forgejo responses, bootstrap, and RC cleanup. The consumer post-bump examples are explicitly consumer-owned generic executable paths.
• The 123 H provenance records and 14 L deleted-file citations remain historical; the frozen 32-name population remains a bounded NAME-SPACE, not a 32-item work-list. The existing operations.md correction is preserved and not duplicated.

Changed files

AGENTS.md, changelog.d/1119-dead-script-namespace.fixed.md, docs/dead-script-namespace.md, docs/architecture/contracts/changelog-format.md, docs/architecture/contracts/cli-surface.md, docs/architecture/contracts/forgejo-responses.md, docs/architecture/contracts/fragment-format.md, docs/architecture/contracts/property-invariants.md, docs/integration.md.

Verification

• go test -count=1 ./... — pass.
• go vet ./... and go build ./... — pass.
• golangci-lint run --timeout=5m --max-issues-per-linter=0 --max-same-issues=0 — 0 issues.
• bats --print-output-on-failure tests/ — 152/152 pass.
• Full scripts shellcheck — pass.
• scripts/contract-paths-check.sh docs/architecture/contracts — pass: 5 authority paths resolve, 6 historical provenance paths existed, 1 glob classified.
• python3 scripts/dated-examples-check.py — pass: 4 example blocks checked.
• Workflow schema — pass: PARSED=27 TOTAL=27; fixture controls: 4 fatal rejected and 3 safe accepted.
• rt register-check — pass: 0 register-drift hits.
• Fragment coverage/content gate — pass: legitimate fragment present and 5 fragments pass density checks.
• Ledger controls — pass: 32 unique names and 274 records (H=233, P=27, L=14).
• Local binary-size-check could not grade because no FORGEJO_TOKEN was available; it measured 9,781,432 B without a baseline comparison.

No code, #851 corpus, #862, #876, or operator-decision scope was changed. No review was requested and no merge was performed.

Refs frankenbit/release-toolkit#1119 and frankenbit/release-toolkit#1111. ## Coordinate decision (#1119) - The 96/274 current-main measurement was run against `468710a0baa0917e102010130c6784b04c3da9e6` on 2026-09-05, as recorded in `docs/dead-script-namespace.md`. Main later advanced to descendant `11d0745349de3404ffb87934f26d56dc7439c6c0`, which was the branch base used for editing/rebasing, not a second source for that measurement. The classification boundary remains frozen source tree `a9563b4263de0ae97661304661efee44143953a8` from 2026-08-26. - The complete frozen ledger is 274 outer records: H=233, P=27, L=14. The current-main recheck before editing landed 96/274 and missed 178: H=78/233, P=13/27, L=5/14. - The reported `268/99/169` measurement is retained as historical evidence. The six-record difference is the L shorthand that the earlier parse did not reach; it is not silently substituted. - Decision: live line numbers do not remain. Each entry uses the frozen path, nearest section heading, and quoted frozen text; line numbers in L entries remain explicitly historical navigation citations. The re-verification cost and method are recorded in the ledger. - The unchanged-file control was `AGENTS.md`: `git diff --quiet a9563b4263de0ae97661304661efee44143953a8` returned exit 0 before this PR, frozen/current SHA-256 was `f2bbac162fe2c3a9daabdb0d079354eee4529c564b0c3a8741492833998b91d2`, and its control population was 24/24 with zero misses. ## Remediation register (#1111) - The register covers all 16 grouped path entries across 13 names and 27 line occurrences. Current P claims are updated in `AGENTS.md`, the changelog/fragment/Forgejo/property contract docs, and the consumer hook example in `docs/integration.md`. - The Arc42 `changelog` and `conventional-commits` entries were already reconciled by #917 and remain current; they are recorded as such rather than changed here. - Current Go sources are named for composition, fragment kinds, register patterns, semver tests, typed Forgejo responses, bootstrap, and RC cleanup. The consumer post-bump examples are explicitly consumer-owned generic executable paths. - The 123 H provenance records and 14 L deleted-file citations remain historical; the frozen 32-name population remains a bounded NAME-SPACE, not a 32-item work-list. The existing `operations.md` correction is preserved and not duplicated. ## Changed files `AGENTS.md`, `changelog.d/1119-dead-script-namespace.fixed.md`, `docs/dead-script-namespace.md`, `docs/architecture/contracts/changelog-format.md`, `docs/architecture/contracts/cli-surface.md`, `docs/architecture/contracts/forgejo-responses.md`, `docs/architecture/contracts/fragment-format.md`, `docs/architecture/contracts/property-invariants.md`, `docs/integration.md`. ## Verification - `go test -count=1 ./...` — pass. - `go vet ./...` and `go build ./...` — pass. - `golangci-lint run --timeout=5m --max-issues-per-linter=0 --max-same-issues=0` — 0 issues. - `bats --print-output-on-failure tests/` — 152/152 pass. - Full scripts shellcheck — pass. - `scripts/contract-paths-check.sh docs/architecture/contracts` — pass: 5 authority paths resolve, 6 historical provenance paths existed, 1 glob classified. - `python3 scripts/dated-examples-check.py` — pass: 4 example blocks checked. - Workflow schema — pass: `PARSED=27 TOTAL=27`; fixture controls: 4 fatal rejected and 3 safe accepted. - `rt register-check` — pass: 0 register-drift hits. - Fragment coverage/content gate — pass: legitimate fragment present and 5 fragments pass density checks. - Ledger controls — pass: 32 unique names and 274 records (H=233, P=27, L=14). - Local `binary-size-check` could not grade because no `FORGEJO_TOKEN` was available; it measured 9,781,432 B without a baseline comparison. No code, #851 corpus, #862, #876, or operator-decision scope was changed. No review was requested and no merge was performed.

rigger added 1 commit 2026-09-05 03:29:52 +02:00

docs: anchor dead-script ledger and remediate claims 1091ef9c8a

sentry requested changes 2026-09-05 03:42:50 +02:00

Dismissed

sentry left a comment

Copy link

Exact-head review at 1091ef9c8a: REQUEST_CHANGES.

The nine-file docs and ledger scope is otherwise coherent: the frozen a9563b4 source boundary, 275 literal matches versus 274 outer records, the historical 268/99/169 measurement, the six-record L shorthand difference, stable path and heading anchors, the 16-entry remediation register, and the H/L provenance separation are all stated consistently. The exact-tree Go tests, vet, build, Bats 152/152, contract-path, dated-example, and diff checks pass. The disclosed binary-size check remains cannot-grade without FORGEJO_TOKEN.

Blocker: docs/dead-script-namespace.md:77 presents git log --all --diff-filter=D --format= --name-only -- scripts | sort -u as a reproducible query returning 28 deleted script paths. Running that exact command against this PR history returns 30: the two post-freeze deletions scripts/fork-pr-approval-notice.sh and scripts/release-assets.sh are included. The frozen-anchored form git log a9563b4263de0ae97661304661efee44143953a8 --diff-filter=D --format= --name-only -- scripts | sort -u returns the claimed 28. Pin the query to the frozen commit, or label and preserve the historical query explicitly, so the ledger remains reproducible and the 28-path list stays unambiguous.

The sole red server context, gitea-twin-check, is inherited rather than caused by this PR: an exact-base checkout at 11d0745349 reports the same seven stale twins, the current main at 1ab4364a4f passes the twin check, and this PR changes no .forgejo or .gitea files.

Exact-head review at 1091ef9c8ac4baac756d3c2e1a5559e25e1451fd: REQUEST_CHANGES. The nine-file docs and ledger scope is otherwise coherent: the frozen a9563b4 source boundary, 275 literal matches versus 274 outer records, the historical 268/99/169 measurement, the six-record L shorthand difference, stable path and heading anchors, the 16-entry remediation register, and the H/L provenance separation are all stated consistently. The exact-tree Go tests, vet, build, Bats 152/152, contract-path, dated-example, and diff checks pass. The disclosed binary-size check remains cannot-grade without FORGEJO_TOKEN. Blocker: docs/dead-script-namespace.md:77 presents `git log --all --diff-filter=D --format= --name-only -- scripts | sort -u` as a reproducible query returning 28 deleted script paths. Running that exact command against this PR history returns 30: the two post-freeze deletions `scripts/fork-pr-approval-notice.sh` and `scripts/release-assets.sh` are included. The frozen-anchored form `git log a9563b4263de0ae97661304661efee44143953a8 --diff-filter=D --format= --name-only -- scripts | sort -u` returns the claimed 28. Pin the query to the frozen commit, or label and preserve the historical query explicitly, so the ledger remains reproducible and the 28-path list stays unambiguous. The sole red server context, gitea-twin-check, is inherited rather than caused by this PR: an exact-base checkout at 11d0745349de3404ffb87934f26d56dc7439c6c0 reports the same seven stale twins, the current main at 1ab4364a4f89534cc82e8592ccceff859aa7f5c4 passes the twin check, and this PR changes no .forgejo or .gitea files.

rigger added 1 commit 2026-09-05 03:45:13 +02:00

docs: pin dead-script history query to frozen tree aec02cb41d

rigger force-pushed rigger/1119-1111-dead-script-anchors from aec02cb41d to 2cf646dad6 2026-09-05 03:49:43 +02:00 Compare

sentry requested changes 2026-09-05 03:53:23 +02:00

sentry left a comment

Copy link

Exact-head follow-up review at 2cf646dad6 (base fb1bd9c2ca): REQUEST_CHANGES.

The previous blocker is corrected: the frozen-tree history query is now pinned to a9563b4263, and it returns 28 deleted paths. I independently confirmed the ledger counts (274 outer records: H=233, P=27, L=14), diff cleanliness, and the exact tree tests/gates; Forgejo CI is 27/27 success.

Blocker: the PR body and the artifact disagree about the same pre-edit current-main measurement. The body says the read was 11d0745349, while docs/dead-script-namespace.md:65-66 says it was 468710a0ba. These are different commits, and the statement supports the current-main recheck/96-of-274 measurement, so a reader cannot know which source tree produced the ledger evidence. Reconcile the SHA (or explicitly label them as separate measurements with their respective purposes) and keep the date/claim aligned. The code/docs scope otherwise reads coherently; no merge action taken.

Exact-head follow-up review at 2cf646dad6c154f255bc86df10ef5910ef85c7bb (base fb1bd9c2cacbf9b484d6e0ff52590541a3d314e9): REQUEST_CHANGES. The previous blocker is corrected: the frozen-tree history query is now pinned to a9563b4263de0ae97661304661efee44143953a8, and it returns 28 deleted paths. I independently confirmed the ledger counts (274 outer records: H=233, P=27, L=14), diff cleanliness, and the exact tree tests/gates; Forgejo CI is 27/27 success. Blocker: the PR body and the artifact disagree about the same pre-edit current-main measurement. The body says the read was 11d0745349de3404ffb87934f26d56dc7439c6c0, while docs/dead-script-namespace.md:65-66 says it was 468710a0baa0917e102010130c6784b04c3da9e6. These are different commits, and the statement supports the current-main recheck/96-of-274 measurement, so a reader cannot know which source tree produced the ledger evidence. Reconcile the SHA (or explicitly label them as separate measurements with their respective purposes) and keep the date/claim aligned. The code/docs scope otherwise reads coherently; no merge action taken.

rigger added 1 commit 2026-09-05 03:56:04 +02:00

docs: distinguish ledger measurement and rebase base 3def64ef76

sentry approved these changes 2026-09-05 03:58:41 +02:00

sentry left a comment

Copy link

Exact-head follow-up review at 3def64ef76 (base fb1bd9c2ca): APPROVE.

The prior artifact blocker is resolved. The PR body and docs/dead-script-namespace.md now agree that the 96/274 current-main measurement was run against 468710a0ba, while 11d0745 was the later branch base used for editing/rebasing. The frozen history query is pinned to a9563b4263 and independently returns 28 deleted paths; the ledger independently counts 274 outer records (H=233, P=27, L=14).

The nine-file docs/AGENTS/fragment scope is unchanged by the rebase and contains no twin repair. Exact-tree diff check and gitea-twin pass, and Forgejo CI is terminal 27/27 success. The documented coordinate decision and remediation register are now internally consistent. No merge action taken.

Exact-head follow-up review at 3def64ef7661b9b22dabfd048224433f37bd2aba (base fb1bd9c2cacbf9b484d6e0ff52590541a3d314e9): APPROVE. The prior artifact blocker is resolved. The PR body and docs/dead-script-namespace.md now agree that the 96/274 current-main measurement was run against 468710a0baa0917e102010130c6784b04c3da9e6, while 11d0745 was the later branch base used for editing/rebasing. The frozen history query is pinned to a9563b4263de0ae97661304661efee44143953a8 and independently returns 28 deleted paths; the ledger independently counts 274 outer records (H=233, P=27, L=14). The nine-file docs/AGENTS/fragment scope is unchanged by the rebase and contains no twin repair. Exact-tree diff check and gitea-twin pass, and Forgejo CI is terminal 27/27 success. The documented coordinate decision and remediation register are now internally consistent. No merge action taken.

sentry approved these changes 2026-09-05 04:02:32 +02:00

sentry left a comment

Copy link

Exact-head follow-up review at 3def64ef76 (base fb1bd9c2ca): APPROVE.

The prior artifact blocker is resolved. The PR body and docs/dead-script-namespace.md now agree that the 96/274 current-main measurement was run against 468710a0ba, while 11d0745 was the later branch base used for editing/rebasing. The frozen history query is pinned to a9563b4263 and independently returns 28 deleted paths; the ledger independently counts 274 outer records (H=233, P=27, L=14).

The nine-file docs/AGENTS/fragment scope is unchanged by the rebase and contains no twin repair. Exact-tree diff check and gitea-twin pass, and Forgejo CI is terminal 27/27 success. The documented coordinate decision and remediation register are now internally consistent. No merge action taken.

Exact-head follow-up review at 3def64ef7661b9b22dabfd048224433f37bd2aba (base fb1bd9c2cacbf9b484d6e0ff52590541a3d314e9): APPROVE. The prior artifact blocker is resolved. The PR body and docs/dead-script-namespace.md now agree that the 96/274 current-main measurement was run against 468710a0baa0917e102010130c6784b04c3da9e6, while 11d0745 was the later branch base used for editing/rebasing. The frozen history query is pinned to a9563b4263de0ae97661304661efee44143953a8 and independently returns 28 deleted paths; the ledger independently counts 274 outer records (H=233, P=27, L=14). The nine-file docs/AGENTS/fragment scope is unchanged by the rebase and contains no twin repair. Exact-tree diff check and gitea-twin pass, and Forgejo CI is terminal 27/27 success. The documented coordinate decision and remediation register are now internally consistent. No merge action taken.

bosun merged commit 3def64ef76 into main 2026-09-05 04:05:24 +02:00

bosun deleted branch rigger/1119-1111-dead-script-anchors 2026-09-05 04:05:24 +02:00

bosun referenced this pull request 2026-09-05 04:12:01 +02:00

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

bosun referenced this pull request from a commit 2026-09-05 04:16:25 +02:00

fix(prep): regenerate and stage the .gitea twins after the bake

bosun referenced this pull request from a commit 2026-09-05 04:19:03 +02:00

fix(prep): regenerate and stage the .gitea twins after the bake

bosun referenced this pull request from a commit 2026-09-05 04:21:36 +02:00

fix(prep): regenerate and stage the .gitea twins after the bake

Sign in to join this conversation.

Reviewers

No reviewers

sentry

Labels

Clear labels   

bump

major

Override the cut bump to MAJOR (release-toolkit#107)

  

bump

minor

Override the cut bump to MINOR (release-toolkit#107)

  

bump

patch

Override the cut bump to PATCH (release-toolkit#107)

  

kind/bug

Something is broken

  

kind/chore

Maintenance, tooling, refactor

  

kind/docs

Documentation work

  

kind/feature

New feature or capability

  

priority/critical

Critical: must be addressed immediately

  

priority/high

Important, should be addressed soon

  

priority/low

Low priority, address when convenient

  

priority/medium

Normal priority

  

size/L

Large: significant feature, ~6-16h

  

size/M

Medium: moderate feature, ~2-6h

  

size/S

Small: simple change, ~1-2h

  

size/XL

Extra large: major feature or refactor, 16h+

No labels

bump

major

bump

minor

bump

patch

kind/bug

kind/chore

kind/docs

kind/feature

priority/critical

priority/high

priority/low

priority/medium

size/L

size/M

size/S

size/XL

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

2 participants

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

frankenbit/release-toolkit!1169

No description provided.