Co-owned org rows are still filed under the completetech family (latent leak) #40

Status: Verified during the Pick Your AI rollout (reproduced, or read directly in the code).

Part of epic: Epic: Keep brand families isolated (no CompleteTech text in other orgs).

Summary

Jevelopers-neatHack-2026 (display name TicketStub, tier T3) is still family: completetech, the same mistake that produced CompleteTech branding on Pick Your AI.

Evidence

• references/brand.yaml org row for Jevelopers-neatHack-2026.
• Eyebrow, palette, badge colours and License wording come from the family.

Impact

Its first rendered output would carry CompleteTech branding.

Proposed fix

Give each non-CompleteTech org its own family (or fail loudly), and add a generic leak test.

Acceptance criteria

• No org row whose display name is not a CompleteTech brand resolves to the completetech family.
• A test renders every org row and fails on completetech|CompleteDotTech|005ADD outside CompleteTech orgs.

Tasks

Each task below is a sub-issue.

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.