feat(trekexecute): every MAJOR answered before merge, fixed runs the fix loop

docs/architecture.md

@@ -9,7 +9,7 @@ Imported from `CLAUDE.md` via pointer.
 - `lib/util/{frontmatter,result,atomic-write,autonomy-gate}.mjs` — shared YAML-frontmatter parser + Result helpers + `atomicWriteJson(path, obj)` for tmp+rename writes + autonomy-gate state machine (v3.4.0)
 - `lib/parsers/{plan-schema,manifest-yaml,project-discovery,arg-parser,bash-normalize,jaccard,finding-id}.mjs` — pure parsers (no I/O), unit-tested. `manifest-yaml` extended in v3.4.0 with additive `skip_commit_check` + `memory_write` flags (forward-compat: unknown keys ignored)
 - `lib/review/{rule-catalogue,plan-review-dedup}.mjs` — version-pinned rule catalogue (17 keys) + Phase 9 inline dedup helpers (v3.4.0)
-- `lib/review/{verdict-gate,engine-findings,recurrence}.mjs` — the review gate (K7: 0 ALLOW/WARN · 1 BLOCK · 2 never green), Claude Code `/code-review` + `/security-review` findings → reviewer payload, recurring finding classes → operator-approved project-memory lines (review_version 1.2); `lib/review/fill-finding-ids.mjs` computes the coordinator's `@@ID_<n>@@` placeholders over `(file, line, rule_key)`; `lib/validators/brief-review-stamp.mjs` lets `/trekplan` skip a brief review `/trekbrief` already ran on the same text
+- `lib/review/{verdict-gate,engine-findings,recurrence}.mjs` — the review gate (K7: 0 ALLOW, or WARN with every counting MAJOR answered · 1 BLOCK · 2 never green), Claude Code `/code-review` + `/security-review` findings → reviewer payload, recurring finding classes → operator-approved project-memory lines (review_version 1.2); `lib/review/fill-finding-ids.mjs` computes the coordinator's `@@ID_<n>@@` placeholders over `(file, line, rule_key)`; `lib/validators/brief-review-stamp.mjs` lets `/trekplan` skip a brief review `/trekbrief` already ran on the same text
 - `lib/stats/event-emit.mjs` — single-source stats event emitter for autonomy-gate transitions and main-merge-gate (v3.4.0)
 - `lib/validators/{brief,research,plan,progress,session-state}-validator.mjs` — schema validators with CLI shims (`node lib/validators/X.mjs --json <path>`)
 - `lib/validators/architecture-discovery.mjs` — drift-WARN external-contract discovery for `architecture/overview.md`

docs/command-modes.md

@@ -89,10 +89,11 @@ Every mode that executes refuses a plan whose approval in the approval log does
 
 | Flag | Behavior |
 |------|----------|
-| _(default)_ | Claude Code `/code-review` + `/security-review` (engine, via the Skill tool, never `--fix`), then brief-conformance + code-correctness reviewers in parallel, coordinator dedup + verdict, write `{project_dir}/review.md` with the required `verdict:`, decide with `lib/review/verdict-gate.mjs` (0 ALLOW/WARN · 1 BLOCK · 2 never green), propose recurring finding classes as project memory (operator approves each line) |
+| _(default)_ | Claude Code `/code-review` + `/security-review` (engine, via the Skill tool, never `--fix`), then brief-conformance + code-correctness reviewers in parallel, coordinator dedup + verdict, write `{project_dir}/review.md` with the required `verdict:`, decide with `lib/review/verdict-gate.mjs` (0 ALLOW, or WARN with every counting MAJOR answered · 1 BLOCK · 2 never green), the operator answers each counting MAJOR (Phase 8.8), propose recurring finding classes as project memory (operator approves each line) |
 | `--project <dir>` | **Required.** Path to trekplan project folder containing `brief.md`. Review is written to `{dir}/review.md` |
 | `--since <ref>` | Override "before" SHA for the diff range. Validated via `git rev-parse --verify` |
 | `--quick` | `/code-review` + code-correctness reviewer only; skip brief-conformance reviewer, `/security-review` and the coordinator's reasonableness filter except the brief-conflict rule — fast correctness-only pass |
+| `--answers` | Only the operator's answers to the counting MAJORs (Phase 8.8) on the existing `{dir}/review.md`, then the verdict gate. No reviewer and no write of findings: it opens no new round and counts nothing against the cap |
 | `--validate` | Schema-only check on existing `{dir}/review.md` plus the verdict gate. No LLM calls. A 1.0 review without `verdict:` fails here (it still seeds a plan in soft mode) |
 | `--dry-run` | Print discovered scope + triage map; skip writes |
 | `--fg` | No-op alias (foreground is default) |

docs/release-runbook.md

@@ -66,7 +66,8 @@ do. `scripts/release-check.mjs` refuses a release whose section has no
    node lib/review/verdict-gate.mjs <review.md>
    ```
 
-   0 = ALLOW or WARN, 1 = BLOCK, 2 = could not decide. Only 0 goes on.
+   0 = ALLOW, or WARN with every counting MAJOR answered, 1 = BLOCK, 2 = could
+   not decide. Only 0 goes on.
 4. **The release commit.** It changes only the version and the release notes:
    `.claude-plugin/plugin.json`, `package.json`, `package-lock.json` (both
    `version` fields), the README version badge, and a new CHANGELOG section
@@ -90,6 +91,17 @@ do. `scripts/release-check.mjs` refuses a release whose section has no
    Voyage's own artifacts under `.claude/projects/` and `.claude/voyage/`, such
    as the review itself and the approval log), and the door type is set. 0 = ready, 1 = not ready (each failure listed), 2 = could
    not run — never green.
+
+   A review with an unanswered MAJOR reads NOT_READY (exit 1), also one
+   written before `review_version` 1.2, such as a review written by the
+   installed 6.5.0 plugin (this delivery's own review included). Answer each
+   counting MAJOR from this repo before the release check, the `/trekreview`
+   Phase 8.8 path: list them with
+   `node lib/review/review-answers.mjs pending --review <review.md> --repo .`,
+   then record each answer with `node lib/review/review-answers.mjs record`
+   (the reason on stdin; see its header for the flags). An answer "fixed"
+   needs its `### Step R<n>` in the review first, and stays open until a later
+   review round no longer finds the finding.
 6. **The operator's yes, logged.** The operator reads the release section and
    says yes (an answer like "sounds good" is not a yes). The check prints the
    command that logs it (K2):