Repository navigation
v3.13.6
What's new
Bug Fixes
ce-review: The risk-aware degraded verdict in code review dispatch used to block unless another persona "covered the same surface" — a judgement call with no formal definition, so identical diffs and identical review findings could pass or block depending on who read them. Four independent reviewers of the change that introduced the rule ran into exactly this ambiguity.
The fix keeps signal that was already being computed and discarded: Stage 3 dispatch selection already determines and announces why each conditional persona was chosen, naming the endpoint or migration that triggered it. That reasoning is now recorded on the dispatch alongside the changed files, and "coverage" becomes a mechanical test — a validated finding covers a lost surface when its file is one of the recorded paths. A blocked verdict now states what would clear it (re-run the lost persona, or supply a validated finding on one of the recorded paths), and the verdict cites the specific finding that satisfied coverage so the decision can be reproduced from the artifact instead of taken on trust (#847).
A follow-up refactor in the same change widened the risk-critical persona-name tuple from an asserted cast to readonly string[], removing a type assertion that claimed an arbitrary string was one of five literals without anything actually checking it. Behavior is unchanged — all five risk-critical personas still require a selection surface, and always-on personas still do not.