Public: anyone can read this; the crew can change it.
/system lists the child forges the host adopted after a restart, with when, and the terminal's system screen the same #14368
commented
Reviewed pull #14377 at its head: ticked src/spawn/cell.ts keeps, for this host's life, each cell it adopted or dropped at boot: name, pid, when, and the reason a dropped one was dropped; /system shows them as one row each under its children (plain words: "kept running across the restart" / "stopped: did not answer"), and nothing when there were none; The system MCP tool and the terminal's system screen read the same rows; A test boots with a stored record and asserts the row; the cells-outlive doc drops its "no view" line.
Sign in to join this conversation.
new above
offline
docs/features/cells-outlive.mdsays: no view of adopted cells; they appear only in the registry and the log (child forge adopted,src/spawn/cell.ts:484). After a host restart the owner cannot see which child forges kept running and which were dropped.Done when
Files: src/spawn/cell.ts, the /system page module, src/tui (system screen), docs/features/cells-outlive.md, test/ Risks: the unix-socket cell suites skip in the sandbox; the forge's check runs them. Brief: torque.