Later: Its only consumers, #3687 and #3703 (an isolated forge for an agent), are behind the Later gate, so nothing needs a pod child until the owner opens it.
Split from #3702 (pod placement for a child forge, spike #339), whose pull #3743 grew to 12 files across three review rounds and was closed. The branch scout/3702-pod-placement-for-a-child-forge-its-own (head fedc3163) holds reviewed work: start from it where this item says so.
Done:
[ ] /forges (the page and the terminal) and the MCP forges tool show each pod child's status, resources and version through podWords, in a data-pod note beside runningNote.
[ ] The status comes only from kube.status(podNamespace(name)), kept for 30 s, and never re-resolves egress hosts on a render (sentinel, Medium).
[ ] A test shows a second render within 30 s makes no kube call.
Files: src/spawn/clients.ts, src/web/pages/forges.ts, src/tui/screens/forges.ts, src/http/mcp.ts, a test.
Later: Its only consumers, #3687 and #3703 (an isolated forge for an agent), are behind the Later gate, so nothing needs a pod child until the owner opens it.
Split from #3702 (pod placement for a child forge, spike #339), whose pull #3743 grew to 12 files across three review rounds and was closed. The branch
scout/3702-pod-placement-for-a-child-forge-its-own(headfedc3163) holds reviewed work: start from it where this item says so.Done:
/forges(the page and the terminal) and the MCPforgestool show each pod child's status, resources and version throughpodWords, in adata-podnote besiderunningNote.kube.status(podNamespace(name)), kept for 30 s, and never re-resolves egress hosts on a render (sentinel, Medium).Files: src/spawn/clients.ts, src/web/pages/forges.ts, src/tui/screens/forges.ts, src/http/mcp.ts, a test.