docs(cold-read): extract Cold-Read Prompt to in-repo doc + scrub docs.saratow.net references from all files #326
Labels
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
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
frankenbit/release-toolkit#326
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Motivation
Operator surfaced 2026-07-03 that the Cold-Read Prompt currently lives externally at
docs.saratow.net/books/tmux-tell/page/cold-read-prompt*(BookStack, operator's personal domain). Public Codeberg mirror + adopter clones expose thesaratow.netURL, which leaks the operator's surname into a public project — a discrete privacy concern separate from Lookout's earlier "BookStack references confuse adopters" register issue (already scoped under release-toolkit#315).Operator ratified the ideal variant: extract Cold-Read Prompt content into the repo as an in-repo doc, drop all external references.
Semantic upside: Cold-Read becomes a first-class project asset — human-side discipline complementing the mechanical
changelog-body-check.ymllinter. Adopters can see + adopt the discipline themselves.Scope
Herald prose-craft surface
docs.saratow.net/books/tmux-tell/page/cold-read-prompt-changelog-verifier) and companioncold-read-promptpage. Herald has access.docs/cold-read-prompt.md— adopter-facing prose, aligned register (no BookStack references, no operator-name leaks, no internal jargon).docs/conventions.md:262— replace saratow.net link withdocs/cold-read-prompt.mdchangelog.d/.template.md:27— replace saratow.net link with in-repo referencedocs/integration.md:228— coordinate with release-toolkit#315 (Herald's existing scrub scope), since both touch the same lineQM mechanical surface
.forgejo/workflows/reusable-changelog-body-check.yml:8— comment currently reads# Read discipline catches (BookStack page 208 anchor).— update to reference the in-repo doc:# Read discipline catches (see docs/cold-read-prompt.md).Empirical baseline (from
grep -rIn 'saratow\.net')Plus
.forgejo/workflows/reusable-changelog-body-check.yml:8"BookStack page 208 anchor" comment (no saratow.net URL but internal BookStack reference).Verification AC
grep -rIn 'saratow\.net' .returns zero hits post-mergegrep -rIn 'BookStack' .returns zero adopter-facing hits (docs/internal/ maintainer-scoped references acceptable)docs/cold-read-prompt.mdrenders cleanly on Codeberg mirror + Forgejo web viewdocs/cold-read-prompt.mdor in-repo equivalentSet J context
Must land before v1.0.0 cut. Coordinates with release-toolkit#315 (Herald's existing integration.md scrub scope) — both touch integration.md line 228; Herald handles both in one PR to avoid conflicts. Herald prose-craft primary; QM mechanical assist on workflow comment (single line change).
Landed in PR #328 (merged to
mainat2b07ddf, fast-forward). Cold-Read Prompt extracted from BookStack into in-repodocs/cold-read-prompt.md(titled Changelog Cold-Read Prompt to distinguish from the #312 maintainer README cold-read framework), generalized to a project-neutral placeholder. All in-repo refs repointed (integration.md, conventions.md, changelog.d/.template.md, reusable-changelog-body-check.yml). Two-fixes-one-pass: the old BookStack link was both a dead link (slug renamed) AND asaratow.netprivacy surface on the public mirror. Verifiedsaratow.net=0 /docs.saratow=0 /bookstack=0 repo-wide.