Split tollbooth and remediation concerns between reconstruct-best-practices and pre-publish-privacy-review

[krisrowe]

Problem

The reconstruct-best-practices and pre-publish-privacy-review skills have overlapping concerns around content safety when documenting research and design decisions. Currently:

• reconstruct-best-practices contains detailed tollbooth checks, leak remediation guidance, and audience-per-piece evaluation as part of its documentation workflow
• pre-publish-privacy-review focuses on scanning for PII patterns but doesn't cover the broader content placement and remediation concerns

This creates duplication and unclear ownership of these responsibilities.

Proposed responsibility split

Concern	reconstruct-best-practices	pre-publish-privacy-review
"Who does this content serve?" audience routing	Primary — about where to put documentation	No — pre-publish assumes target is already chosen
Tollbooths before commits/pushes/issues	Referenced briefly	Primary — the actual checklist
Leak remediation (amend, force-push, delete)	Referenced briefly	Primary — the recovery playbook
Personal narrative vs. abstract documentation split	Primary — about documentation quality	Mentioned as a category of concern
Reviewing context piece-by-piece against artifacts	Primary — for completeness	Primary — for safety
"If the user walked away this minute" exposure test	Referenced	Primary — this is the core safety heuristic

Work breakdown

• Add tollbooth checklist to pre-publish-privacy-review — the list of critical moments (commit, push, issue create, shared doc write) where content must be re-evaluated
• Add the "walked away" exposure test to pre-publish-privacy-review — "if the user stopped right now, could this content reach unintended audiences through normal subsequent actions?"
• Add leak remediation playbook to pre-publish-privacy-review — amend/rebase for local commits, force-push for pushed commits, delete-and-recreate for issues/comments, delete releases not just assets
• Add "shared or eventually-shared resources" as a category in pre-publish-privacy-review — Google Docs with edit history, draft releases, etc.
• Slim down the corresponding sections in reconstruct-best-practices to brief references that point to pre-publish-privacy-review for the detailed guidance, keeping only what's needed for the documentation placement workflow
• Ensure both skills reference each other where appropriate without duplicating content