The terminal's Family card says, per sent forge, how many of its apps run and which one does not #1898

Replaces #1584. The terminal has no forges screen; the sent forges reach it through the Family card (src/tui/screens/family.ts), whose lines come from src/spawn/family.ts. Once #1384 gives the parent each hosted child's app state, add it to those lines so the terminal and /family say the same thing.

Done looks like:

• [ ] src/spawn/family.ts gives, for each child an admin sees, N of M apps running, or names the app that is not and its one-word reason (asleep, failing, not deployed), read from the same state #1384 shows on /forges; a child given no apps says nothing about apps.
• [ ] The terminal Family card and /family render that line from the same view; a guest still sees only the parent (the gate stays in spawn/family.ts).
• [ ] A test in test/ builds a family with one child given two apps, one running and one asleep, and asserts the line reads 1 of 2 apps running — <app> asleep in both the view and the rendered card; it fails without the change.

Files: src/spawn/family.ts, src/tui/screens/family.ts, the /family page, a test. Risk: do not invent app state; if #1384's state is not reachable from the family view, expose it there rather than recomputing it.

Parked by the crew: the check failed ("migrations are additive across a roll > the release record is newest first and never ahead of the schema") and the decider saw no point in another try (pull #1939 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.