Cut over existing Forge-managed projects

[Futuri-Risk]

Parent

#1

What to build

Move existing projects from the bespoke Forge/Project Conductor runtime onto the new FirstMate operating model while preserving the durable project state that matters.

Existing Gitea issues, labels, branches, commits, pull requests, and unresolved work must carry forward. Each project should be onboarded into its persistent Secondmate. Old Forge runtime/session identities should not become new FirstMate execution state. Preserve the old Forge implementation intact as rollback/reference material.

Cloud implementation requirement: Complete all implementation, repository changes, tests, fixtures, static/contract verification, and integration analysis possible from the GitHub/chat environment. Do not defer implementation merely because final production binaries or private services are unavailable. Clearly identify only the minimal runtime observations that require later local certification.

Acceptance criteria

• Existing project repositories can be onboarded without rewriting or discarding their Git history.
• Existing open Gitea work is visible to the new project Secondmate after cutover.
• Existing semantic labels remain present and can be normalized/backfilled by the new metadata extension without losing unrelated labels.
• Existing unresolved branches/commits/work remain preserved and are not silently reset or deleted.
• Obsolete Forge runtime/session identifiers are not imported as active FirstMate task/session identities.
• Legacy manually created coding sessions may continue independently without requiring general session-adoption machinery.
• The old Forge/Project Conductor code and state needed for rollback/reference remain preserved, while FirstMate becomes the active orchestration authority.
• Migration tests/fixtures demonstrate preservation of representative open issues, labels, branches, commits, and unresolved work.

Blocked by

• Add living Gitea semantic labels #4 Add living Gitea semantic labels
• Recover interrupted ZCode work without losing changes #5 Recover interrupted ZCode work without losing changes
• Ship validated ZCode work through Gitea #8 Ship validated ZCode work through Gitea