Driver

The privacy-gate wording introduced in PR #144 (and unchanged in PR #147) attributes the fork-publication to the framework rather than the adopter:

the standard fork-and-commit setup will silently publish your private project names on a public GitHub repo

This is factually wrong. ApexYard never pushes anything without explicit operator approval — the publication happens only when the adopter themselves runs git push, intentionally or accidentally. The current wording reads like the framework auto-publishes, which is misleading and undermines trust in the rest of the framework's safety claims.

Scope

Two prose-only edits, no code, no behavior change.

1. .claude/skills/setup/SKILL.md — Step 2a privacy-gate question

Replace will silently publish your private project names on a public GitHub repo with adopter-action language: you might accidentally publish your private project names on a public GitHub repo (a stray git push after registering them).

2. docs/multi-project.md — trip-wire callout

Replace silently publish their portfolio names the moment they push with adopter-action language: risk accidentally publishing their portfolio names with a stray push.

Acceptance Criteria

• .claude/skills/setup/SKILL.md Step 2a no longer contains the phrase "silently publish"; replaced with adopter-action language ("you might accidentally publish ...")
• docs/multi-project.md trip-wire callout no longer contains "silently publish"; replaced with adopter-action language ("risk accidentally publishing ...")
• No code changes — prose only
• grep returns zero hits across the framework: grep -r "silently publish" .claude/skills/ docs/

Risks / Dependencies

None. Pure prose correction. Targets dev per release-cut model.