fix(governance): repair canonical repository identity and runbook truth

[eimyroot]

Purpose

PR-01 prerequisite for VOODOO ONE Operating System v2. Repairs canonical repository identity and operational truth without changing product runtime or security behavior.

Exact scope

• canonical GitHub repository identity: eimyroot/Voodoo-One
• governance baseline and verifier fixtures/tests bound to the current repository identity
• review-branch publisher targets only https://github.com/eimyroot/Voodoo-One.git
• prior repository URLs retained only as explicit fetch-only legacy aliases
• operations runbook uses the current GitHub repository and artifact-derived migration/schema truth
• current G0 state is UNKNOWN pending a fresh exact-main post-rename G0 run; historical VERIFIED G0 evidence remains historical
• regression tests prevent repository-identity, publication-target, runbook-schema, and G0-current-state drift

Boundary / non-scope

No changes to:

• voodoo_product/* runtime
• database migrations or schema
• auth / RBAC
• provider authority, Runner or Verifier semantics
• production effects
• GitHub ruleset settings
• required verify check
• release-promotion semantics
• deployment

Base / candidate

• base main: 66df8669dcfe5b2955d71fa02987f26c95bcf750
• candidate branch: review/os-v2-pr01-repo-identity-runbook
• candidate head at PR creation: 639bcda974a2879dbf9a87fd88d863c6e05dfa8b

Verification

Required before merge:

• exact-head canonical CI verify = green
• targeted governance/publication/documentation regression tests = green
• full pytest / readiness / dependency audit / image smoke remain green

After merge, a fresh manual g0-governance-verify must run on the exact new main SHA before current GitHub governance may return from UNKNOWN to VERIFIED.

Rollback

Revert this PR if the canonical identity repair introduces an unexpected tooling regression. Do not restore current G0 to PASS unless fresh exact-main live evidence independently supports it.