fix: pre-landing review fixes (pass 2)

Standing approvals: the newest row about autoplan recommendations decides, so a later refusal
blocks older grants; rows whose id or date is not the recorded shape are never cited; the
project is fixed at init from the plan's physical path (run.json project_root) so a symlinked
plans folder or a checkpoint restore cannot borrow another repository's record. Gate cost:
recReopens counts every phase revise can keep or add and prices answers already recorded at
the gate; run --json emits one payload; the Captain brief's ### Cost sits above the relaying
trailer.

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

docs/troubleshooting.md

@@ -1713,8 +1713,12 @@ import again. Imports are idempotent, so a retry never records an answer twice.
 **Meaning.** `answer --owner-standing rec` looked for a standing approval covering autoplan
 recommendations (a `gstack-approvals` row with outcome `standing`, scope or ask naming
 `autoplan`, words or scope naming `rec` or the recommendations) in this project's records,
-local and mirror, every branch, and found none. The gate stays pending; nothing was applied.
-Exit 3.
+local and mirror, every branch, and found none that applies: either no such row exists, the
+newest row about autoplan recommendations refuses them (`never take the recommendations`, a
+scope that carves autoplan out; the line quotes it, and a later grant supersedes it), or the
+run's plan is not inside a git repository, so no project record can be named (the project is
+the repository the plan's physical path was in at init). A row whose id or date is not the
+recorded shape is never cited. The gate stays pending; nothing was applied. Exit 3.
 
 **Fix.** Relay the gate to the owner (or Captain) and answer with their reply through
 `--reply` and `--owner-reply`. For the next gate, the Captain records the owner's standing