Trello: TOOL-12 https://trello.com/c/6af3cdffa4cedf98a5c97517
Source: owner 2026-11-11, after the SAFETY-135 dev (Opus) sat overnight waiting for a router verdict that never came. Same on SAFETY-126 (2026-10-31, 8 h idle).
What happens: the router verifies only dev agents that ran below Opus. For an Opus-run dev it posts nothing, so silence means both "still verifying" and "will never verify". Also seen: for SAFETY-126 a verdict arrived ~11 h late, labelled "sonnet", although that dev transcript was all Opus, so the router may misread which model ran.
Wanted: on every dev hand-back, one line:
[model-router] T<n> verifying on Opus..., or
[model-router] T<n> no verification: dev ran on Opus. Go straight to review.
The model is taken from what actually ran, not only from the routing choice.
Acceptance (tests):
Opus-routed dev: skip message at hand-back, and no later verdict.
Sonnet-routed dev: "verifying" message, then the verdict.
Dev routed Sonnet but run on Opus (or the reverse): reported by the model that ran.
Then install in ~/projects/goodwe/tools/model-router and /reload-plugins.
Priority P2, size S.
Trello: TOOL-12 https://trello.com/c/6af3cdffa4cedf98a5c97517
Source: owner 2026-11-11, after the SAFETY-135 dev (Opus) sat overnight waiting for a router verdict that never came. Same on SAFETY-126 (2026-10-31, 8 h idle).
**What happens:** the router verifies only dev agents that ran below Opus. For an Opus-run dev it posts nothing, so silence means both "still verifying" and "will never verify". Also seen: for SAFETY-126 a verdict arrived ~11 h late, labelled "sonnet", although that dev transcript was all Opus, so the router may misread which model ran.
**Wanted:** on every dev hand-back, one line:
- `[model-router] T<n> verifying on Opus...`, or
- `[model-router] T<n> no verification: dev ran on Opus. Go straight to review.`
The model is taken from what actually ran, not only from the routing choice.
**Acceptance (tests):**
1. Opus-routed dev: skip message at hand-back, and no later verdict.
2. Sonnet-routed dev: "verifying" message, then the verdict.
3. Dev routed Sonnet but run on Opus (or the reverse): reported by the model that ran.
Then install in ~/projects/goodwe/tools/model-router and /reload-plugins.
Priority P2, size S.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Trello: TOOL-12 https://trello.com/c/6af3cdffa4cedf98a5c97517
Source: owner 2026-11-11, after the SAFETY-135 dev (Opus) sat overnight waiting for a router verdict that never came. Same on SAFETY-126 (2026-10-31, 8 h idle).
What happens: the router verifies only dev agents that ran below Opus. For an Opus-run dev it posts nothing, so silence means both "still verifying" and "will never verify". Also seen: for SAFETY-126 a verdict arrived ~11 h late, labelled "sonnet", although that dev transcript was all Opus, so the router may misread which model ran.
Wanted: on every dev hand-back, one line:
[model-router] T<n> verifying on Opus..., or[model-router] T<n> no verification: dev ran on Opus. Go straight to review.The model is taken from what actually ran, not only from the routing choice.
Acceptance (tests):
Then install in ~/projects/goodwe/tools/model-router and /reload-plugins.
Priority P2, size S.