[WAIFUS Phase 1] Freeze and back up the legacy repository

[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

Freeze the exact legacy source state, approve every open-work disposition, and create independently readable Git and GitHub metadata backups before migration.

Gates and dependencies

• Blocked by: Phase 0
• Gate coverage: Phase 0; FR-23 repository inventory; FR-49 ref dispositions; sourceFreezeSha.
• Exit gate: Two independently readable Git backups exist; ref and release hash inventories match the source-freeze repository, and every tracked GitHub object has an approved disposition.

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

• Approved disposition manifest for every issue, PR, draft release, branch, tag, workflow, integration, and inventory class.
• sourceFreezeSha, ref/object-ID inventory, settings/integration inventory, and contribution-freeze record.
• Verified mirror clone, Git bundle, hashed retained assets/artifacts, and exported GitHub metadata stored outside both repositories.

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. Finish every approved merge_before_freeze PR before sourceFreezeSha. Do not stack ordinary work across the freeze.

goal.md

Phase 1 — Freeze and back up the legacy repository

Objective

Freeze the exact legacy source state, approve every open-work disposition, and create independently readable Git and GitHub metadata backups before migration.

Source of truth

• Plan path: docs/plans/waifus-rebrand-and-repository-independence.md
• Approved SHA-256: B3D07F514F3E7D90C3EC4A8C586CD34E145D1673ED661B8D76D52F278AEC336A
• Owner: slashdevcorpse
• Applicable gate coverage: Phase 0; FR-23 repository inventory; FR-49 ref dispositions; sourceFreezeSha.
• 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

• Obtain explicit approval for any paid handle reservation, then reserve only
  the approved package/handle targets. The repository slug is claimed only
  by creating the public canonical repository in Phase 3; no private repository
  is created for staging or reservation.
• Produce a user-approved disposition manifest covering every open issue,
  every open pull request regardless of author, every draft release, every
  branch, every tag, and every additional FR-23 inventory class. Allowed issue
  dispositions are recreate_in_waifus,
  archive_open, or close_with_reason; allowed PR dispositions are
  merge_before_freeze, recreate_in_waifus, or archive; branches use the
  FR-49 parity-then-cleanup dispositions, and tags are mirrored as immutable
  historical provenance.
• Execute the approved pre-freeze PR and draft-release dispositions.
• Announce a short contribution freeze and record the source-freeze SHA
  that will become canonical WAIFUS history.
• Record the source-freeze timestamp, all branch/tag object IDs, repository
  settings, rulesets, environments, app installations, secret/variable names,
  issue/PR/review metadata, Actions state, and release metadata.
• Create and verify a mirror clone and Git bundle.
• Download release assets, logs/artifacts that must be preserved, and their
  hashes.
• Export issue, PR, review, label, milestone, release, and settings metadata.
• Store backups outside both repositories with access appropriate to any
  sensitive content.

The source freeze blocks ordinary code changes. Later legacy-issue forward-link
comments and the single legacy archival-banner commit are authorized migration
mutations and MUST be recorded separately. They do not change the source-freeze
SHA used for canonical ref-parity checks.

Required outputs

• Approved disposition manifest for every issue, PR, draft release, branch, tag, workflow, integration, and inventory class.
• sourceFreezeSha, ref/object-ID inventory, settings/integration inventory, and contribution-freeze record.
• Verified mirror clone, Git bundle, hashed retained assets/artifacts, and exported GitHub metadata stored outside both repositories.

Verification

• Both Git backups restore independently.
• Every branch/tag object ID and retained release/asset hash matches the frozen source.
• No private canonical or staging repository exists.

Exit criteria

Two independently readable Git backups exist; ref and release hash inventories match the source-freeze repository, and every tracked GitHub object has an approved disposition.

Non-goals

• Creating or detaching the canonical repository.
• Rewriting legacy history.
• Implementing branding, publication, or tracker migration.

STOP conditions

• Any tracked object lacks an approved disposition.
• A backup, ref, release hash, or metadata class cannot be verified.
• Ordinary development continues after sourceFreezeSha without a renewed freeze.
• 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.