docs: scrub remaining tmux-tell internal-refs from integration.md (out-of-scope leak from #210) #214

New issue

Closed

opened 2026-06-27 17:35:53 +02:00 by quartermaster · 0 comments

quartermaster commented

2026-06-27 17:35:53 +02:00

Owner

Why

Herald's #212 audit of #210 surfaced 4 remaining tmux-tell internal-refs in integration.md (in the relocated section_format / tag-is-version content). Same external-leak family as previous README scrubs — internal-project references that don't belong in adopter-facing docs for release-toolkit (a generic reusable-workflow toolkit).

The #210 scope was structural-polish (M2-M8 + L1); scrubbing internal-refs is a separate concern. Filing as follow-up so the scope-leak doesn't silently propagate.

Scope

Grep docs/integration.md for tmux-tell / tmux-msg references
For each: either remove (if just example-leakage) or generalize (if substantive — replace with a generic project reference or remove the example entirely)
Same check on README.md, AGENTS.md, ADRs as a sweep — there may be other internal-refs hiding

Composition

Sister of Herald's #212 (PR closing #210 main scope; this is the out-of-scope leak)
Empirical: Herald observed M5's trim incidentally scrubbed one cellblock ref; pattern suggests similar leaks elsewhere
Lightweight: a sed-grep sweep + judgment call per match. No structural docs rework needed.

What this PR will NOT do

Will NOT touch the structural polish from #210 (already shipped/being-shipped via #212)
Will NOT renumber sections or restructure (pure replace/remove operations)

Refs

Herald 3c5a (the surfacing)
#210 (the sibling that surfaced this during its polish pass)
#212 (Herald's PR closing #210's main scope)

priority/low · size/S

## Why Herald's #212 audit of #210 surfaced 4 remaining `tmux-tell` internal-refs in integration.md (in the relocated section_format / tag-is-version content). Same external-leak family as previous README scrubs — internal-project references that don't belong in adopter-facing docs for release-toolkit (a generic reusable-workflow toolkit). The #210 scope was structural-polish (M2-M8 + L1); scrubbing internal-refs is a separate concern. Filing as follow-up so the scope-leak doesn't silently propagate. ## Scope 1. Grep `docs/integration.md` for `tmux-tell` / `tmux-msg` references 2. For each: either remove (if just example-leakage) or generalize (if substantive — replace with a generic project reference or remove the example entirely) 3. Same check on `README.md`, `AGENTS.md`, ADRs as a sweep — there may be other internal-refs hiding ## Composition - Sister of Herald's #212 (PR closing #210 main scope; this is the out-of-scope leak) - Empirical: Herald observed M5's trim incidentally scrubbed one cellblock ref; pattern suggests similar leaks elsewhere - Lightweight: a sed-grep sweep + judgment call per match. No structural docs rework needed. ## What this PR will NOT do - Will NOT touch the structural polish from #210 (already shipped/being-shipped via #212) - Will NOT renumber sections or restructure (pure replace/remove operations) ## Refs - Herald 3c5a (the surfacing) - #210 (the sibling that surfaced this during its polish pass) - #212 (Herald's PR closing #210's main scope) priority/low · size/S

quartermaster referenced this issue

2026-06-28 10:29:42 +02:00

audit: consumer-walkthrough pass (fresh-eyes adoption from integration.md to first cut) #157

quartermaster referenced this issue

2026-06-28 13:22:07 +02:00

[MED] docs: integration.md adoption-surface polish (structure, step-completeness, token clarity) — #157 bundle #199