Public: anyone can read this; nobody can change it.

germinate: daughters fork their parent's mitosis — repo-migrate, 3 tiers (#70) #72

Merged opened this view on origin

Check · Review · Land done · Live — Landed; nothing deploys from this branch, so this is the end of its path.

Merged

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/mi…

shipped merged

opened this view on origin

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

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs