docs(autoplan): how run settles a failed api call; changelog scopes it to the native voice

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

changelog.d/gsta232-autoplan-wave.md

@@ -7,7 +7,7 @@
 - **A spend cap binds on any unattended host.** With `--spend-cap` set and no `--estimate-usd`, each host-subagent attempt reserves the default $5 per voice, on Capy or off it. `next --estimate-usd <n>` sets the reservation for the rest of the run. `run` reserves each API call's priced worst case (prompt size plus the output limit) and settles it at its real token cost, so `--spend-cap 0` refuses before any call.
 - **`gstack-autoplan run` with `--native-runner api --runner api` reaches the gate.** Results are checked as autoplan results, so they bind. A response cut off at the output limit is named `truncated` and interrupts the run instead of binding a partial review. The default output limit is 16384 tokens for both providers (OpenAI counts reasoning tokens toward it), `--max-tokens <n>` sets it, and an outside result refused at submit leaves the run native-only instead of aborting it.
 - **An earlier item-by-item answer carries forward when nothing changed.** When every item on the new gate is carried by origin, the owner's `p1` choice is replayed and their tokens are recorded verbatim as the basis. Any new or changed item still goes to the owner.
-- **A spend cap stays closed when a call fails.** A call cut off at its output limit is settled at what it cost, and a retry with a larger `--max-tokens` is admitted against the cap afresh. A call that timed out or dropped after it was sent is charged its full reservation, because the provider may have billed it. A call refused before anything was sent (no API key, for example) charges nothing, and the rerun reuses its reservation.
+- **A spend cap stays closed when a call fails.** For the native voice, a call cut off at its output limit is settled at what it cost, and a retry with a larger `--max-tokens` is admitted against the cap afresh. A call that timed out or dropped after it was sent is charged its full reservation, because the provider may have billed it. A call refused before anything was sent (no API key, for example) charges nothing, and the rerun reuses its reservation. A failed outside call is still counted at its full reservation while the phase continues native-only.
 - **A finding you chose to fix stays open until the revised plan is reviewed.** If the reviewer raises it again after a revise that missed it, it comes back to the gate instead of being treated as settled. A withdrawn fix leaves its finding open.
 - **Two findings that only sit near each other are no longer merged.** A user challenge one line away from an unrelated Critical no longer hides the Critical. Findings are merged only when their titles match or the parent says they are the same problem.
 - **A plan gate answered in an agent's own words is not owner approval.** `gstack-ship-receipt` rejects a plan-sha approval citation whose gate was answered with `--words-by agent:<id>`.

docs/unattended.md

@@ -458,7 +458,12 @@ spend is `unknown` and counted in `worst_case`. Under a cap (or on Capy) each
 unattended host-subagent attempt reserves the default per voice unless
 `next --estimate-usd <n>` sets the reservation, which the run keeps for later
 phases (`run` reserves an api attempt's priced worst case, prompt bytes / 3
-input tokens plus the output limit, and settles it at its token usage); `submit
+input tokens plus the output limit, and settles it at its token usage; a native
+call that fails after it was sent settles at its usage, or at its full
+reservation when the usage is unknown, while one refused before anything was
+sent, such as with no API key, keeps its attempt open for the rerun, and a
+failed outside call leaves the phase native-only and stays counted at its
+reservation); `submit
 --usage-usd <n>` settles an attempt at its real cost. `--deadline <min>` makes the
 `run` subcommand cancel the children it started and marks the run
 `interrupted`.