Epic: Onboarding other organizations and registry-free operation #105

Goal

The skill assumes the CompleteTech estate. Adding one organization required hand-editing five files, and several checks need a private registry.

Exit criteria

• A new org can be added with one command.
• Leak checks run without the private registry.
• doctor separates skill-complete from owner-pending.

Scope

• E6.1: Provide a supported way to onboard a non-CompleteTech organization
• E6.2: lint public-leak and org actions need the private registry; provide a registry-free mode
• E6.3: Checkouts whose origin was renamed are rejected as a different repository
• E6.4: doctor cannot distinguish "skill work complete" from "owner decisions pending"

Progress is tracked through this issue's sub-issues.

Prior work

Prior work: open PR #20 (opt-in --allow-t3 and the Pick Your AI family), open #7 and PR #13 (variant J badges), merged PRs #14 to #19 (icon art-direction path, UTF-8 output, registry-free org health and label planning, Windows test portability, footer URL repair) and closed issues #8 to #12. Nothing here duplicates those; where an item is already handled it is linked, not refiled.

Fresh VM verification: not run. Findings were verified on a Windows host; hosted CI is separate evidence.