The terminal's issues list opens the repository's plan with `m`: working, ready now, waiting on what, and parked twice, as MCP `map` reads it #7472

Intent: the owner reads where the plan stands in the terminal, in one screen. No terminal screen calls repoGraph or pillarView today. Only the web map and MCP map do.

Done:

• [ ] m on the issues list (src/tui/screens/issues.ts) pushes a new src/tui/screens/plan.ts. It has four groups, each headed with its count. Working: #N title — agent. Ready now: #N title — pillar. Waiting: #N title — waits on #A, #B, with a hold's sentence (mapHeldFor) when one stands. Parked twice: #N title — why.
• [ ] It uses the same reads as MCP map (src/http/mcp/tools/map.ts): repoGraph with the caller's sealedScope, pillarView, mapHeldFor and listActiveRuns. A sealed issue the reader may not see is left out, as there.
• [ ] Enter on a row opens that issue's screen, and r reads again.
• [ ] The issues list's key hints add m plan.
• [ ] A test (e.g. test/tui-plan.test.ts) makes a small graph (one ready issue, one waiting on it, one with a run in flight), opens the screen and checks the groups and Enter. A sealed issue is not shown to a reader.

Files: src/tui/screens/issues.ts, src/tui/screens/plan.ts (new), a new test.