germinate: daughters fork their parent's mitosis — repo-migrate, 3 tiers (#70) #72
No reviewers
Labels
No labels
bug
discussion
duplicate
enhancement
goal
help wanted
horizon:backlog
horizon:governance
horizon:mvp
invalid
operator-decision
question
roadmap
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
open-platform/mitosis!72
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/fork-on-germinate"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Implements #70 per the design contract on the issue: after the postgres-backed Forgejo is healthy, the daughter's mitosis repo is created by Forgejo repo-migrate (full parent history + forge-recorded source = genealogy) instead of the squashed bundle push. THREE tiers, never aborting germination: (1) seed manifest createdFrom (the parent), (2) MITOSIS_FORK_ROOT default git.open-platform.sh/plat/mitosis (removed-parent case), (3) the existing bundle push (air-gapped seeds unchanged). One-time migrate — downstream maintainer edits are never clobbered. ORIGIN lineage still appends; public flag + metadata replay preserved.
Validation: the coldstart gate (merged via #71) runs automatically on this PR (bin/** path filter) and proves tier-flow germination end-to-end; tier-specific assertions (parent-history depth, migration metadata, forced tier-3) follow as a gate extension before merge.
🤖 Generated with Claude Code
e6f7d9117eto13e278106bWorkspaces are scrubbed post-run and this Forgejo's job-log API 404s, so a red gate run was undebuggable — tee the germination and gate output to ~/ci-gate-logs/run<N>-{up,gate}.log on the runner host. germinate now logs ONE definitive 'mitosis fork RESULT: tier-N' line (attempt lines also fire on failed tiers), and the workflow exports FORK_TIER from it so A7 asserts strictly: log-said-migrate must match repo-records-migration. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>