germination isolation: one per host, and no fixed MCP port #256
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!256
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "germination-isolation"
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?
The gauntlet’s first night ran concurrently with the reseed gate and exposed a real class:
mcp_pfbound a FIXED local port (3200), so the gate’s front door reached the gauntlet daughter’s MCP — foreign PAT, “unauthorized” (run 848 / mitosis#255’s failure). Three fixes:MCP_PORTderives from the already-uniqueFJ_PORT;bin/uptakes a host-wide flock so germinations serialize as a SYSTEM invariant (loud wait, bounded, not politeness between workflows); the anon-surface scenario sets its probe variables in the calling shell (run 846:ANON_CODEunbound — set inside a command substitution). #255 is superseded by the reseed this merge triggers.