voyage/commands
Kjell Tore Guttormsen 22e792ce19
fix(review): a review with a control that did not run stops a merge
Operator decision 2026-10-06. Before, a WARN that existed only because a
reviewer or engine never reported (e.g. /security-review without an origin
remote) mapped to verdict-gate exit 0, so a review nobody performed in full
was green. Now `missing-reviewer:` / `unattributable-payload` in the JSON
block's allow_blocked_by is exit 2 (could not decide, never green); a WARN
for a MAJOR or a set-aside finding still passes with its reasons. A 1.1
review must carry allow_blocked_by.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-06 20:06:29 +02:00
..
trekbrief.md fix(docs): the order fields stand on all five surfaces (green) 2026-10-04 19:55:17 +02:00
trekcontinue.md feat(commands): drop orchestrator model pins - inherit session model 2026-07-02 17:09:49 +02:00
trekendsession.md fix(trekendsession): release v5.9.1 - eager-exec blocks crashed command load 2026-07-03 01:11:02 +02:00
trekexecute.md fix(execute): the Phase 8 payload goes on stdin; /trekreview findings closed 2026-10-05 18:16:46 +02:00
trekplan.md fix(docs): the alias targets and effort defaults match the docs today (green) 2026-10-02 21:44:00 +02:00
trekresearch.md fix(commands): the VOYAGE_ROOT fallback writes $(0), not $0 2026-10-02 16:02:13 +02:00
trekreview.md fix(review): a review with a control that did not run stops a merge 2026-10-06 20:06:29 +02:00