fix: close the gaps the review of the trial-5 fixes found

- park-attempt-files: parks in the git dir (outside the work tree, so Sub-step C.2 never registers a parked file again), reads a path with a space, names a new file under a header it cannot read, parks a symlink, never overwrites a parked file, and exits 1 while a file the attempt made is still in the tree; the upward diff is saved in one form whatever the git config.

- brief-validator: BRIEF_SC_NOT_RUNNABLE only when a later backticked span is a command; a criterion that only names a flag or a path stays prose (Handover 1 says so now).

- review ids: counted over the final list (runContract), as fill-finding-ids counts review.md; trimmed_count matches rows by id; engine-findings and fidelity-diff use computeFindingIds; the --workflow dedup keeps one source's different findings apart, the decision-23 put-back stays one copy per triplet.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

commands/trekexecute.md

@@ -1527,13 +1527,16 @@ the earlier attempt's new files, which the revert left on disk untracked, so a
 stale file can never pass the revised step's checks (voyage-lekerepo trial 5,
 finding 4):
 ```bash
-node ${CLAUDE_PLUGIN_ROOT}/lib/util/park-attempt-files.mjs --diff {report dir}/step-{N}-upward.diff --to {report dir}/step-{N}-attempt-{attempts}
+node ${CLAUDE_PLUGIN_ROOT}/lib/util/park-attempt-files.mjs --diff {report dir}/step-{N}-upward.diff --step {N} --attempt {attempts}
 ```
-It moves every file the attempt created that is still untracked into that
-directory under its own path: moved, never deleted. Name the `parked` paths
-and every `kept` path with its reason in the step report; exit 2 is a stop
-(the tree was not checked). Then launch a fresh `build` helper for the
-revised step.
+It moves every file the attempt created that is still untracked to the git
+dir (`voyage/parked/step-{N}-attempt-{attempts}/`, outside the work tree, so
+Sub-step C.2 never registers it again): moved, never deleted, never over a file
+already parked. Name the `parked` paths and every `kept` path with its reason
+in the step report. Exit 1 means a file the attempt made is still in the tree
+(a header it could not read, a move that failed): stop and name it; exit 2 is
+a stop too (the tree was not checked). Then launch a fresh `build` helper for
+the revised step.
 
 - **Never pass the Agent tool's `name` parameter.** A named spawn becomes an
   `in_process_teammate`: it does the work, but its result never reaches this
@@ -1849,7 +1852,7 @@ session's effort, Sub-step E).
 | 4 | the plan | **After three failed fix rounds the question is the architecture, not a fourth fix.** The step goes back to planning (below). Sub-step B sends three answers here directly, with no fix round: a `"not-run"` caused by the `Verify:` command, a second `plan-unreadable` (the executor's own call still wrong after one correction), and a `not-red-at-base` with `tests_only: true` (a step of only tests). Stop class 4 |
 | 5 | the operator | A step already sent to the plan (`fix_rounds` 4) that fails its control again after re-planning goes to the operator. The executor never builds this step again: on a later `--resume` it only runs the checks (B, D1, D2, D3, D4, E) on whatever the operator changed. If they fail again the step stays at 5 — there is no sixth round, `fix_rounds` never exceeds 5 — and the run stops again. Stop class 4 |
 
-**Back to planning** (`fix_rounds = 4`): save `git diff {start_sha}` to
+**Back to planning** (`fix_rounds = 4`): save `git diff --no-ext-diff --no-renames --src-prefix=a/ --dst-prefix=b/ {start_sha}` (one form whatever the user's git config) to
 `{report dir}/step-{N}-upward.diff` and write `{report dir}/step-{N}-upward.md`:
 the step verbatim, every round's findings and verdicts, and the question for
 the planner — which assumption in the step (its Changes, its Interface, its
@@ -1873,7 +1876,7 @@ directly (Sub-step B), and so does a second `plan-unreadable` after one correcte
   ```
   The new files stay on disk, untracked, and `step-{N}-upward.md` names them —
   nothing the step made is deleted, and none of it is left registered. A
-  `--resume` after re-planning parks them in the report dir before the fresh
+  `--resume` after re-planning parks them in the git dir before the fresh
   build (Sub-step C).
   When the guard refuses the restore (it is destructive git: in the permission
   mode that shows no prompts the guard refuses it, exit 2, "no one to ask"), or