Onboard a Gitea project into a persistent Secondmate

[Futuri-Risk]

Parent

#1

What to build

Make one complete project-onboarding path work: a Gitea repository can be registered with FirstMate, sourced from the synchronized local mirror when current, reconciled with its existing open issue backlog, and automatically provisioned with its own persistent OpenCode Secondmate using the normal tmux-backed FirstMate runtime.

The finished behavior should establish the one-project/one-Secondmate convention without introducing a new orchestration framework or replacing upstream FirstMate lifecycle machinery.

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

• Registering a project creates or reuses the correct FirstMate project record without losing the upstream repository identity.
• A current local/self-hosted mirror is preferred for source inspection and cloning; stale or failed synchronization is visible rather than silently treated as current.
• Every registered project provisions exactly one persistent Secondmate by default, with no small-project exception.
• The Secondmate uses its own persistent FirstMate home and project state and initially runs through the supported OpenCode supervision path.
• Existing open Gitea issues are discoverable to the project onboarding flow without converting closed historical issues into active work.
• Direct conversation with the Secondmate does not corrupt its supervisor state or prevent normal parent-channel reporting.
• The solution keeps tmux as the selected runtime backend and does not introduce Herdr, ACPx-as-backend, or another terminal backend.
• Tests prove onboarding behavior at the project-lifecycle seam using the repository's existing test runner and conventions.

Blocked by

• None (can start immediately).