feat(#599): expose pendingQuestion in get_status and REST endpoint

[OneStepAt4time]

Summary

Closes #599 (intervention 1 of 3).

When a session enters ask_question state, get_status (MCP) and GET /v1/sessions/:id (REST) now include a pendingQuestion payload:

{
  "status": "ask_question",
  "pendingQuestion": {
    "toolUseId": "toolu_abc123",
    "content": "Which strategy? 1) Clean up 2) Auto-restart 3) Both",
    "options": ["Clean up", "Auto-restart", "Both"],
    "since": 1774906529600
  }
}

This closes the feedback loop for MCP callers that previously had no visibility into CC questions — the root cause of duplicate session spawns.

Changes (3 files, +71/-6)

File	Change
src/session.ts	Add timestamp to PendingQuestion, expose in getPendingQuestionInfo()
src/server.ts	Extend addActionHints() with pendingQuestion payload + extractQuestionOptions() helper
src/__tests__/mcp-server.test.ts	Add test verifying pendingQuestion flows through get_status

Verification

• ✅ tsc --noEmit — exit 0
• ✅ npm run build — exit 0
• ✅ npm test — 75 files, 1734 tests passed, 0 failed

What is NOT in this PR

Interventions 2 and 3 from #599 (waitForStable on create_session and idempotency key) will be separate PRs.

[OneStepAt4time]

👁️ Argus Code Review

feat(#599): expose pendingQuestion in get_status and REST endpoint

Verdict: ✅ Approved — code is solid

What it does

Exposes pendingQuestion data (toolUseId, content, options, timestamp) in REST GET /sessions/:id and MCP get_status when a session is in ask_question state.

Checklist

• ✅ Root cause addressed — data was missing from responses
• ✅ New test covers the ask_question → pendingQuestion path
• ✅ Optional sessions param — no breaking change
• ✅ extractQuestionOptions with regex + max 4 cap — defensive
• ✅ Follows existing patterns (Feature: Support PreToolUse hook updatedInput for headless question answering #336, Performance: Unbounded maps and memory leaks across modules #357)
• ✅ CI green
• ⚠️ Branch not up to date with main — needs rebase before merge

Notes

• extractQuestionOptions only handles numbered options (1. Foo, 2. Bar). If question format changes, returns null gracefully — fine for now.
• The timestamp addition to PendingQuestion is clean and minimal.

Ready to merge after rebase.

[OneStepAt4time]

ok

[OneStepAt4time]

ok