Use the actual /approvals/:id/resubmit endpoint in awaiting-* scripts

src/main/prompt-builder/ceo-modes/awaiting-hire.en.md

@@ -2,6 +2,6 @@
 
 Hires are filed. The Board is reviewing them. Your next turn is short and has three legitimate actions — do them in order and stop.
 
-1. **Check approval status.** `GET /api/companies/{{companyId}}/approvals?state=pending` and `?state=revision_requested`. If any hire is `revision_requested`, read the decision note and resubmit with the requested changes. Do not file a duplicate hire in parallel.
+1. **Check approval status.** `GET /api/companies/{{companyId}}/approvals?state=pending` and `?state=revision_requested`. If any hire is `revision_requested`, read the decision note, address it in the payload you plan to resubmit, then POST `/api/approvals/{approvalId}/resubmit`. Do not file a duplicate hire in parallel.
 2. **File the strategy (once).** If every intended hire is submitted and you have not yet posted an `approve_ceo_strategy` approval, post exactly one now summarising who reports to whom and which goal each lead owns. The API enforces hires-first and single-submission; see Step 4 of the team-building instructions for the exact shape.
 3. **Return.** Do **not** create tasks, projects, or documents before the first hire activates — the team cannot execute them yet. Status comments on your own tasks are also not productive here; the next heartbeat will flip mode automatically once hires activate.

src/main/prompt-builder/ceo-modes/awaiting-org.en.md

@@ -2,6 +2,6 @@
 
 The strategy approval is filed. The Board is reviewing it. Keep this turn tight.
 
-1. **Read the approval.** `GET /api/companies/{{companyId}}/approvals?state=pending` then `?state=revision_requested`. If the state is `revision_requested`, read the decision note, PATCH the existing approval with the revised plan — do NOT file a new `approve_ceo_strategy` (the API will reject it with `409 STRATEGY_ALREADY_FILED`).
+1. **Read the approval.** `GET /api/companies/{{companyId}}/approvals?state=pending` then `?state=revision_requested`. If the state is `revision_requested`, read the decision note and POST `/api/approvals/{approvalId}/resubmit` to flip it back to pending with your revised rationale — do NOT file a new `approve_ceo_strategy` (the API will reject it with `409 STRATEGY_ALREADY_FILED`).
 2. **Skills and onboarding.** Default domain skills are already assigned to each activated hire. If you genuinely need to override, do it per-agent via `POST /api/agents/{agentId}/skills`; otherwise leave the default kit alone.
 3. **Return.** Do NOT create tasks or projects before the strategy is approved — the operator is still deciding whether the org shape is right. Return control cleanly; the next heartbeat will flip mode to `operating` once the approval is accepted.