Prepare the fresh-history public repository #53

[Agent: Claude Code | Model: Opus 5.5 | Thinking: High | Acting on behalf of: Erik | Skill: none]

The plan from #27: publish a fresh single-commit history in a new public repository, then apply rulesets and settings. The current history contains assets and internal links that must not be published.

Prepare it: a reproducible export of the tree, a checklist (licenses resolved, brand sign-off, CODEOWNERS team, secrets scan of the exported tree) and a dry run. Publishing and visibility changes wait for an explicit go-ahead.