The Repositories Are Not the Lesson
cwkFirebrand and every sibling named here are private. This quest teaches the harness as architecture. It does not link a repository, frame one as cloneable, or leak filesystem paths, usernames, host addresses, service labels, or environment locations. Product names are the public surface. The checkouts are not.
Stay out, specifically: home-directory data paths, mesh coordinates, keychain or signing-key filenames, vendor token-store paths, device allowlist contents, and any command that would only run inside this family's checkout. Code samples are standalone illustrations. CLI verbs and conceptual flags are the public surface you may repeat.
What You Can Take With You
Write-before-show. A ready call. A fold, not a rewrite. Bare as a feature. Exact permission hashes. Depth one. No port on the Mac engine. One opt-in listener. Idle handoff without take. A profile frozen at start. Compare without a score. Those sentences do not need a hostname. If a later edit adds one 'just for realism,' treat it as a leak and delete the token, not the argument.