The first-login page shows each app with the crew member working on it, in one plain line #10753

Intent: what a client sees first is apps with agents working on them (docs/VISION.md, pillar 3 of #334).

• [x] On the page a new forge's first login lands on, each app is one line: its name, the crew member on it and what they are doing now in plain words ("Mason is adding sign-in"), or "nobody is on it yet".
• [x] Read first: if the page already does this, tick the box with a note naming the code and add only the missing test.
• [x] A test renders the page with an app that has a run in flight and one that has none and asserts both lines; the page stays under its time budget.
• [ ] bun scripts/design-lint.ts passes; before/after screenshots.

Files: src/web/pages/next-steps.ts (or the first-login home), a test. Risks: no polling; server-render it. Stay out of the wording #10712's replacement covers. Suggested: mason.

Reviewed pull #10819 at its head: ticked On the page a new forge's first login lands on, each app is one line: its name, the crew member on it and what they are doing now in plain words ("Mason is adding sign-in"), or "nobody is on it yet".; Read first: if the page already does this, tick the box with a note naming the code and add only the missing test.; A test renders the page with an app that has a run in flight and one that has none and asserts both lines; the page stays under its time budget.. left open: bun scripts/design-lint.ts passes; before/after screenshots. — Lint passed earlier, but no before/after screenshots are attached and lint was not rerun on this head..

Left open after pull #10819 landed: 1 unticked item remains (bun scripts/design-lint.ts passes; before/after screenshots.). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.

Closed by the planner: the page shipped; a run only for design-lint and screenshots of it is not wanted now.