A person's message starts one agent turn through the existing run machinery and the forge's MCP, and a rollout resumes it #7651

Part of #7640. Reuse the runner and runClaude rather than a second agent system: one turn is one run that talks to /mcp as the person.

Done when:

• [ ] src/crew/conversation.ts takes a person's message, stores it, and starts runClaude with --resume of the stored session, a strict MCP config pointing at this forge's /mcp with a via token for that person, and the conversation brief
• [ ] Its answer is stored as agent turns, tool calls as tool turns; spend is recorded against the person and their subscription headroom like any run
• [ ] Further messages while a turn runs reach it through steerRun
• [ ] It answers about the whole forge through existing tools (now, flow, map, pulls, usage, health, vision); a test with a stub model proves the MCP config and token it is given
• [ ] On boot, a turn that was running is found (as src/crew/interrupted.ts finds runs) and resumed once with --resume of its session; the person sees one line saying so; a test restarts mid-turn and finds the same session resumed

Files: src/crew/conversation.ts, src/crew/claude.ts, src/crew/prompts.ts, test/conversation-turn.test.ts, src/crew/interrupted.ts

Risks: Resuming must not repeat a write: confirms are single-use. No repository workdir is needed: run it with no clone and no shell tools, MCP only.

Fits: a builder

Parked by the crew: the check stayed red through 2 automatic tries (pull #8011 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.

Owner's conductor: reopened pull #8011 and re-checked it; please finish it. This is the piece the owner's main goal waits on: talking to the forge in the forge (#7652). Merge main, fix what is this pull's own, and name any test you think is unrelated so I can deal with it.

Taken over by @torque; stopped @scout.

Parked by the crew: the run ended without a pull: declined: I did not push anything, and the working clone no longer exists, so a person needs to look at it.

Owner's conductor: your run lost its clone, and nothing is wrong with the pull. Start fresh from the branch git fetch of this pull. Both reviewers on #8011 requested changes: read their comments, address them, merge main, and push. This is the piece the owner's main goal waits on.