Use GitHub noreply email on public-marketplace commits

Problem

Commits to this public marketplace repo currently carry my real email in the git author header. A GitHub noreply address (<id>+TimZander@users.noreply.github.com) would reduce email-scraping surface without breaking attribution.

The team .commit-email-rules convention in standards/CLAUDE.md handles internal repos via per-repo domain enforcement. The equivalent for public-marketplace personal repos is a noreply email author.

Surfaced during deep-review of the Claude Code usage tooling work: file content was sanitized but the commit author header still carries my personal email.

Acceptance criteria

• Identify the noreply address from github.com/settings/emails (and enable "Keep my email addresses private" if not already on)
• Configure git so commits to public personal repos author as the noreply address. Two viable approaches:
  • Structural (recommended): add an [includeIf "hasconfig:remote.*.url:..."] block in ~/.gitconfig so any repo with a github.com/TimZander/... remote auto-uses the noreply email. Doesn't affect BGV/internal repos.
  • Per-repo: git config user.email <noreply> in each public repo. Simpler but easy to forget on new clones.
• Add a .commit-email-rules file in this repo enforcing domain=users.noreply.github.com so the existing pre-commit hook catches accidental real-email commits going forward.
• Document the public-repo noreply pattern in standards/CLAUDE.md (sibling section to the existing internal-repo guidance).
• Verify on next commit that the author header shows the noreply address.

Important note

GitHub does not retroactively obfuscate existing commits — only new ones. Past commits in this repo and other public personal repos will retain the real email. The only retroactive fix is git filter-branch + force-push, which conflicts with the no-force-push policy. Accept prior exposure; fix going forward.

Start with the existing .commit-email-rules convention and standards/CLAUDE.md, then review the repository's current pre-commit hook behavior. Check github.com/settings/emails and the ~/.gitconfig includeIf approach before choosing the configuration path. Done means new public-repository commits use the GitHub noreply address, the rules file enforces the domain, and the public-repo pattern is documented.