Scaffolded repos should identify the author by GitHub handle, never a real name

[PBNZ]

Desired outcome

A repo scaffolded by RepoKit should never end up carrying a maintainer's real/legal personal name — not in file contents, not in package/module metadata, and not in the git commit identity it configures. The GitHub account or org handle should be what identifies the author by default, everywhere an author/owner/copyright value gets written. A real name should appear only when the user explicitly asks for it.

This needs to hold for the private-now/public-later path RepoKit is built around: by the time visibility flips, there should be nothing personal left to scrub — including in history, which is the expensive case.

Why

RepoKit already treats the commit email as something to keep anonymous by default. The same reasoning should apply to the name. Once a repo is public — or its history is merely pushed — a personal name is effectively permanent: removing it means rewriting history and force-pushing, not editing a file.

What "done" looks like

• Scaffolding a repo at any tier/type produces no real personal name anywhere in the resulting tree, nor in the commit identity that gets configured.
• The handle-over-real-name expectation is a stated convention, discoverable alongside the other identity/privacy conventions — not just an implicit default someone has to notice.
• If a real name is introduced later, something catches it rather than relying on a human spotting it in review.
• The existing email-anonymisation behaviour stays as-is; this extends the same principle to names.

Notes

• Please treat the above as the goal, not a change list — the current defaults and guidance should be re-derived from the repo, since the gaps may be broader than assumed here.
• No names or current values are quoted deliberately: this repo is public.