v0.17.1 — project resume fix

Patch — chimera project resume fix

Found by a live test of the new chimera project orchestrator on a production VPS.

Fixed

• Resume after project start --yes no longer re-asks for plan approval. start --yes
  auto-approved the plan for that one invocation but never persisted it, so a later
  project approve <id> --card <c> (a fresh orchestrator that recomputes the requirement from the
  durable state) bounced back to "approve the initial plan" instead of running the just-approved
  high-risk card. The orchestrator now persists the plan approval the moment a run proceeds past the
  plan gate, so any resume — including right after approving a high-risk (deploy/migration/delete)
  card — continues correctly.

The full human-approval cycle (pause at a risk: high card → approve → the risky step runs → done)
is now verified end-to-end live. Regression test included.

pip install -U chimera-agent