Normalize pre-0.2 Git author metadata

[hizyyo]

Purpose

Correct the accidental OpenCode <opencode@localhost> identity on the 36 pre-0.2 commits authored by hizyyo <kapolol2266@gmail.com>.

This rewrite changes commit metadata only. File trees, commit messages, author dates, and committer dates are unchanged. The existing v0.1.5, v0.1.6, and v0.1.7 tags retain their original objects and SHA values.

Important: do not merge this PR

GitHub cannot apply an existing-history identity rewrite through a normal PR merge. This draft is the review and change-control record for the prepared replacement history.

To apply it, a repository administrator must temporarily allow force-pushes to main. Once that setting is enabled, hizyyo can replace main with commit 00af079729515c173a58477842381450560ebec1 using an explicit lease against the current tip 9394ed6f4be6b2f04153a14474d69e3bfa346a6a. Branch protection should be restored immediately afterward.

Verification

• Erroneous identity before: 36 commits
• Erroneous identity after: 0 commits
• hizyyo <kapolol2266@gmail.com> after: 36 commits
• Source trees: identical across all 54 commits
• Commit messages: identical across all 54 commits
• Author and committer dates: identical across all 54 commits
• npm run typecheck: passed
• npm run build: passed
• npm test: 55 files and 343 tests passed
• GitHub Actions: 16 of 16 checks passed

Operational impact

• main changes from 9394ed6f4be6b2f04153a14474d69e3bfa346a6a to 00af079729515c173a58477842381450560ebec1.
• SHA values change for the 36 corrected commits and the 12 later commits that descend from them.
• Existing clones and forks must fetch the rewritten branch and reset or clone again.
• Historical signatures and status checks on rewritten commits do not carry over.
• Published npm 0.1.x artifacts remain immutable and may retain their original gitHead metadata.

Release note

Normalized pre-0.2 Git author metadata after correcting a cofounder's local Git configuration. No source behavior changed.

[ecc-tools]

ECC bundle files are already tracked in this repository. Skipping generation of another bundle PR.

[github-actions]

GhostAPI PR safety

Result: success

The status check and sanitized evidence artifact are the source of truth. This comment is updated in place and contains no request traffic or secrets.

[yiaany]

Applied on September 1, 2026 by replacing the protected main reference with validated commit 00af079 using an explicit --force-with-lease against 9394ed6. Branch protection was restored immediately. No GitHub UI merge or merge commit was used. GitHub automatically marked this PR as merged after its head became identical to main.