0.1.9-beta5

Killing a parent loop now takes its spawned children with it.

Stopping a coordinator left the workers it fanned out running headless — still spending, against a plan nobody owned anymore. The graph couldn't even express the cascade: parentage lived only in the already-fired edge drawn at creation, indistinguishable from any hand-drawn handoff.

Loops now record which loop created them, and stop/delete walk that custody chain transitively:

• Stop a parent → every unresolved spawned descendant stops with it: session terminated, its memory log told which parent took it down, downstream edges fired as failure. Children that already finished keep the ending they earned.
• Delete a parent → the whole fan-out tree goes: nodes, edges, sessions, memory.
• Drawn edges are not custody — stopping one side of a maker→critic pair you drew leaves the other side exactly as it was.

Custody is recorded from this version on: children created by earlier betas are grandfathered as independent loops.

Everything in beta4 (backend inheritance, the report-back route in each child's memory, staged delivery to non-live targets, node delete, metric-as-method, plateau in the edge editor) is unchanged.