Reconcile headless control plane into GitHub history

[hudsonaikins]

Summary

• preserve the local-only headless remote control-plane commit in GitHub
• reconcile the one-commit gap between the former Forgejo main and GitHub main
• restore GitHub pull requests as the canonical review and merge path

Why

After GitHub PR #15, development continued against Forgejo and local main advanced from aa19d20 to 76b6e77. Publishing that commit on a branch prevents history loss while the GitHub-first edge is completed.

Draft boundary

This PR is intentionally draft. Current configuration still reports Forgejo as the canonical remote and includes Forgejo/AWS deployment material. Do not merge until the GitHub-first provider/configuration adjustment lands and private workflow-ledger placement is verified.

Impact

• GitHub main remains unchanged until review and merge
• no Entire checkpoints, review refs, validation refs, deployments, or infrastructure changes are published
• merged historical branch heads were removed separately from GitHub

Validation

• npm run check
• 80 tests passed
• local commit 76b6e77 has GitHub main commit aa19d20 as its direct parent

[hudsonaikins]

Superseded by #17, which establishes GitHub as the sole hosted Git and review surface while keeping private control refs in the private GitHub control repository. Closing this reconciliation path without merge.