[WAIFUS Phase 2] Validate cutover and rollback manifests

[slashdevcorpse]

Current control issue in slashdevcorpse/synara. During Phase 6, recreate any still-open phase tracker in slashdevcorpse/waifus and preserve this URL in the cutover map.

Owner: slashdevcorpse
Source plan: docs/plans/waifus-rebrand-and-repository-independence.md
Approved plan SHA-256: B3D07F514F3E7D90C3EC4A8C586CD34E145D1673ED661B8D76D52F278AEC336A

Goal

Restore both backups, validate every cutover and rollback record, and reconfirm the standalone-public-repository plus archived-ledger architecture before repository creation.

Gates and dependencies

• Blocked by: Phase 1
• Gate coverage: Phase 1; D-3/D-4; schema-valid cutover map and public-reference inventory.
• Exit gate: Backups restore, every manifest entry is classified, rollback is documented, and no detachment has occurred.

Tracking

• Dependency and gate inputs are verified.
• Every requirement in the collapsed goal.md is complete.
• Required evidence is linked in this issue.
• STOP conditions are clear.
• Exit gate is independently verified.

Outputs

• Independent restore and SHA/ref/release comparison reports.
• Validated migration evidence with every FR-23 class classified.
• Executable rollback runbook and recorded D-3/D-4 reconfirmation.

PR structure

GitHub native Stacked PRs is private preview and is not a dependency. Do not combine this phase with an adjacent phase and do not use an atomic multi-PR stack merge. No bootstrap or implementation PR begins until this issue exits.

goal.md

Phase 2 — Validate cutover and rollback manifests

Objective

Restore both backups, validate every cutover and rollback record, and reconfirm the standalone-public-repository plus archived-ledger architecture before repository creation.

Source of truth

• Plan path: docs/plans/waifus-rebrand-and-repository-independence.md
• Approved SHA-256: B3D07F514F3E7D90C3EC4A8C586CD34E145D1673ED661B8D76D52F278AEC336A
• Owner: slashdevcorpse
• Applicable gate coverage: Phase 1; D-3/D-4; schema-valid cutover map and public-reference inventory.
• If this embedded goal conflicts with the approved plan, stop and resolve the conflict before mutation.

Prerequisites

• The native blocked-by dependency above is complete.
• Applicable provisioning, identity, governance, release, and migration gates are verified at the exact current state.
• Required mutation authority exists before any external write.
• No later phase is pulled forward.

Requirements

• Restore a sample from both Git backups and compare the source-freeze SHA,
  branches, tags, and release hashes.
• Review every FR-23 inventory class and both versioned migration evidence
  files for unclassified or schema-invalid entries.
• Verify the rollback procedure can restore legacy repository visibility,
  homepage/support routing, historical domain disposition, and release
  withholding without deleting history. No new WAIFUS DNS is provisioned.
• Reconfirm D-3 and D-4: create a new standalone repository and preserve the
  legacy fork as an archive. GitHub's self-service detachment MUST NOT be used.

Any later GitHub Support proposal for an in-place architecture change reopens
D-3 and D-4 and requires a revised, re-approved plan before any action.

Required outputs

• Independent restore and SHA/ref/release comparison reports.
• Validated migration evidence with every FR-23 class classified.
• Executable rollback runbook and recorded D-3/D-4 reconfirmation.

Verification

• Both backups restore and all frozen object IDs/hashes match.
• Both migration evidence files are schema-valid with zero unclassified entries.
• No fork detachment or WAIFUS DNS provisioning occurred.

Exit criteria

Backups restore, every manifest entry is classified, rollback is documented, and no detachment has occurred.

Non-goals

• Creating or pushing the canonical repository.
• Detaching or deleting the legacy repository.
• Implementing branding, publication, DNS, or tracker migration.

STOP conditions

• Either backup or rollback cannot be proven.
• Any manifest entry is invalid or unclassified.
• Detachment, history rewrite, or custom-domain scope is introduced without a revised approval.
• The exact current PR head, base, checks, review, DCO, provenance, or owner authorization is stale or incomplete where a PR is required.
• Work would expand beyond this phase or contradict the approved plan.