# Prepared continuation

No paid execution is enabled by this document. Pending requested approval is a
US$125 cumulative inference cap and a US$59.08 one-time payment for US$50 credits.
The old US$100 cap remains authoritative until approved.

## Coverage
128 completed stages; 72 stages lack completed outputs across43run identities.
One is a legitimate16-turn initial limit (SolT03R1); preserve it as an observed
result, not a retry chosen for a better score. AstraT03R1revision hit the earlier
request-byte cap; keep that original result and label any continuation separately.
All infrastructure interruptions and unattempted stages are in missing-runs.csv.
Missing initial:30 (29 infrastructure/unattempted plus1legitimate limit).
Missing revision:42. Several revisions need their initial stage completed first.

## Resume rules
- Preserve every existing directory and ledger. Use completion-attempt IDs.
- For infrastructure-interrupted initials, start a clean identical input workspace;
  for missing revisions after a completed initial, restore the initial workspace
  and replay the original conversation, then send the unchanged revision prompt.
- For a revision interrupted by transport, resume only after matching any returned
  generation or recording the uncertain charge; no blind tool-call replays.
- Do not give models answer keys, grades, competitor outputs or evaluator feedback.
- Share one synchronized cost ceiling across tasks. Charge known historical receipt
  costs once, retain0.16833unassigned as a separate provisional shared-key amount,
  and preserve historical per-call reserves in the audit record. Aggregate delta is
  not proof that each individual failed request cost zero.
- Before dispatch, use a fresh catalog/route check, exact-ID setting and a credit
  balance check. Do not switch providers or reasoning for a cheaper result.
- Save request IDs, generation IDs, timestamps, status codes and redacted error
  bodies as early as available. A402stops all new dispatch; don't keep retrying it.
- One transport retry per new stage, with backoff, same prompt/settings and separate
  attempt ID. More infrastructure failures should be exposed and reported, not
  quietly converted into model failures or repeated forever.
- Preserve the16-turn stage cap and original time/output caps for comparability.
  Document the800000-byte expanded cap when used; the early220000cap stays recorded.

## Completion
Run independent verification against the fixed keys; identify AI reviews as AI,
not human review. Inspect websites and validate artifacts. Rebuild every table,
workbook, raw-output index and archive. Keep all failed attempts linked alongside
completed attempts. Validate actual relative links. Deliver the complete guide;
do not publish to WordPress without a publication request.

## Budget
Observed-cost estimate:US$40.4427817additional usage; not a quote or guarantee.
API-key baseline-adjusted usage:US$67.5263644; estimated totalUS$107.9691461.
RecommendedUS$125ceiling leaves approximatelyUS$17headroom above that estimate.
Account-wide balances omitted from public copy.