Problem
PR #263 (closed #259) reconciled docs/reproducibility.md + docs/notes/reproducibility.md against the post-#258 inline-shell package job. But three more docs outside #263's scope still describe the release pipeline as goreleaser-driven, and those refs are now stale post-merge of PR #258 (.goreleaser.yaml deleted on main).
Where
docs/getting-started.md:102 — "+ attested per the goreleaser pipeline (see docs/reproducibility.md)." This is an operator-facing first-touch doc; a new user clicking through gets a contradiction (the README they just landed on does not mention goreleaser).docs/STRATEGY.md:140 — ".github/workflows/release.yml - goreleaser + slsa-github-generator + cosign-installer + sbom-action integration glue." Stale — the actual integration glue is now inline shell + the same SLSA / cosign / sbom-action stack.docs/notes/ci.md:15 — ".github/workflows/release.yml is rewritten on top of the goreleaser + slsa-github-generator + cosign-installer + sbom-action stack (RFC-0013 §Migration PR-C)." Reads as current-state for the v0.1.0 row of a release-pipeline history block.
Fix prescription
For each line, drop the bare "goreleaser" mention and reframe around release.yml + the still-applicable SLSA / cosign / sbom-action stack. The docs/getting-started.md line can simply read "signed + attested via the release pipeline (see docs/reproducibility.md)". docs/notes/ci.md v0.1.0 row should describe the current release.yml shape and mention the goreleaser → inline-shell migration as a 2026-05-31 footnote so the doc still reads as a historical timeline.
Acceptance
grep -rn 'goreleaser' docs/ returns only historical-record mentions (RFC-0013 + FOLLOWUPS.md M-row + docs/migration/v0.1-to-v0.2.md table + docs/research/ + RFC-0008 archived refs).- No operator-facing doc still describes the pipeline as goreleaser-driven.
bash scripts/doc-check.sh stays green.
Related: #258 (goreleaser removal), #259 (already-fixed repro doc sweep), #263 (already-merged repro doc sweep).
Problem
PR #263 (closed #259) reconciled
docs/reproducibility.md+docs/notes/reproducibility.mdagainst the post-#258 inline-shellpackagejob. But three more docs outside #263's scope still describe the release pipeline as goreleaser-driven, and those refs are now stale post-merge of PR #258 (.goreleaser.yamldeleted on main).Where
docs/getting-started.md:102— "+ attested per the goreleaser pipeline (seedocs/reproducibility.md)." This is an operator-facing first-touch doc; a new user clicking through gets a contradiction (the README they just landed on does not mention goreleaser).docs/STRATEGY.md:140— ".github/workflows/release.yml- goreleaser + slsa-github-generator + cosign-installer + sbom-action integration glue." Stale — the actual integration glue is now inline shell + the same SLSA / cosign / sbom-action stack.docs/notes/ci.md:15— ".github/workflows/release.ymlis rewritten on top of the goreleaser +slsa-github-generator+cosign-installer+sbom-actionstack (RFC-0013 §Migration PR-C)." Reads as current-state for the v0.1.0 row of a release-pipeline history block.Fix prescription
For each line, drop the bare "goreleaser" mention and reframe around
release.yml+ the still-applicable SLSA / cosign / sbom-action stack. Thedocs/getting-started.mdline can simply read "signed + attested via the release pipeline (seedocs/reproducibility.md)".docs/notes/ci.mdv0.1.0 row should describe the current release.yml shape and mention the goreleaser → inline-shell migration as a 2026-05-31 footnote so the doc still reads as a historical timeline.Acceptance
grep -rn 'goreleaser' docs/returns only historical-record mentions (RFC-0013 + FOLLOWUPS.md M-row +docs/migration/v0.1-to-v0.2.mdtable +docs/research/+ RFC-0008 archived refs).bash scripts/doc-check.shstays green.Related: #258 (goreleaser removal), #259 (already-fixed repro doc sweep), #263 (already-merged repro doc sweep).