A client's first screen speaks plain words: their apps, each in a sentence, and whether its agents are working or waiting #1607

Split from #1115 (a person's ask). Done: a person signed in through a child forge's claim link first sees their apps, each with a one-line description in plain words and its agents working or waiting; no map, no board, no settings until asked. A test asserts none of "pull", "branch", "commit", "merge", "CI", "repository" appears on that screen.

Before pushing, run bun test test/asks.test.ts test/asks-expiry.test.ts test/check-list.test.ts with your own tests: earlier tries at this work went red on exactly those home and asks tests. A test that goes red in this pull is fixed in this pull. Name any new test file in GATE in scripts/gate.ts.

Parked by the crew: the check failed ("a spawned child's apps > after claiming, the home shows the app, and says the crew has no model key and where to add one") and the decider saw no point in another try (pull #1735 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.

Parked by the crew: the check failed ("a spawned child's own keys and domain > the child's address is <name>--<parent's host>, recorded and shown on its home") and the decider saw no point in another try (pull #1738 closed).

Parked twice since a person last spoke here, so it is the planner's now. Every reason:

1. the check failed ("a spawned child's apps > after claiming, the home shows the app, and says the crew has no model key and where to add one") and the decider saw no point in another try (pull #1735 closed)
2. the check failed ("a spawned child's own keys and domain > the child's address is <name>--<parent's host>, recorded and shown on its home") and the decider saw no point in another try (pull #1738 closed)

The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.

Deferred behind the Later gate (#595). The owner's direction of 2026-10-15 puts the check pipeline first, before any new feature: #1792, #1793, #1794, #1795, #1796, #1797, #1798, #1799, then #1789. Both tries red on the spawned-child suites; new client home copy waits for the pipeline work and the test split (#1798).

replaced by #1812. Correction to my note above: the Later gate refused it as a cycle (the gate waits on this pillar), so it is replaced instead, by an issue that waits for the owner's check-pipeline work it was failing on and that keeps its pillar.