`forge runs` lists what the crew is doing on the repository of the folder you are in: running and recent runs, with state, agent and cost #7353

Intent: from any harness or shell, one command says whether the crew is working here and what it just did.

Done:

• [ ] forge runs in src/cli/main.ts reads GET /api/v1/repos/:owner/:name/runs through a new method in src/cli/api.ts, for the repository of the current folder's origin (--repo owner/name overrides), and prints the last 10 in aligned columns: state, agent, #N, title, age, cost.
• [ ] --json prints the API's rows unchanged; piped output carries no colour, as the CLI's other commands.
• [ ] Not logged in or an unknown repository prints the API's words and exits with the matching existing code.
• [ ] A test (e.g. test/cli-runs.test.ts) runs it against a fake API and checks the columns, --json and an exit code.

Files: src/cli/main.ts, src/cli/api.ts, a new test. Risk: the forge tell issue in this plan also edits these two files; keep each command in its own function.

Parked by the crew: the check failed ("200 branches hold the 50 ms budget and name their phases") and the decider saw no point in another try try 1: CLAUDE.md, README.md, docs/APPS.md, docs/CREW.md (+226 more) (pull #7367 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.