werkrevisor 0.6.0: four verdict colours, and only deterministic rules block hard.
🟠 ORANGE: findings of the LLM and of the classifier Jev. No bot review; a developer approval after checking the findings unlocks the merge (assessment status warning, exit 15 where codes are distinguished, 0 in approval mode).
🔴 RED: only deterministic rules. First rule: open questions in a changed PR document ([ ], bullet or paragraph without checkbox under "Open Questions"/"Offene Fragen").
Fixes from the comparison on hsadmin-ng: no FIXME.review markers in findings, secret scan ignores src/test/** except real key formats, documentation files trigger no hard-YELLOW path rules.
Reason: the repository admin on dev.hostsharing.net is an operator, so an admin merge override is no way out of a false RED; model and classifier findings are often wrong (3 of 8 Sonnet findings in the comparison).
222 unit tests green in the pinned PR-Agent image.
Open: whether Gitea ignores a stale bot REQUEST_CHANGES after a later ORANGE/YELLOW head; tested on werkprobe after the rollout.
werkrevisor 0.6.0: four verdict colours, and only deterministic rules block hard.
- 🟠 ORANGE: findings of the LLM and of the classifier Jev. No bot review; a developer approval after checking the findings unlocks the merge (assessment status `warning`, exit 15 where codes are distinguished, 0 in approval mode).
- 🔴 RED: only deterministic rules. First rule: open questions in a changed PR document (`[ ]`, bullet or paragraph without checkbox under "Open Questions"/"Offene Fragen").
- Fixes from the comparison on hsadmin-ng: no `FIXME.review` markers in findings, secret scan ignores `src/test/**` except real key formats, documentation files trigger no hard-YELLOW path rules.
Reason: the repository admin on dev.hostsharing.net is an operator, so an admin merge override is no way out of a false RED; model and classifier findings are often wrong (3 of 8 Sonnet findings in the comparison).
222 unit tests green in the pinned PR-Agent image.
Open: whether Gitea ignores a stale bot REQUEST_CHANGES after a later ORANGE/YELLOW head; tested on werkprobe after the rollout.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
RED now comes only from deterministic rules.
ORANGE (exit 15) sits between YELLOW and RED; in approval mode it requests a human review,
submits no bot review and sets the assessment status to warning.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A new required section [pr_doc] names the PR-document globs and the headings of the open-questions section.
Only items checked with [x], blank lines, comments and continuation lines of a done item are allowed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- The operator instructions say that the AGENTS.md code-review procedure does not apply;
a leading FIXME.review line is stripped from a finding.
- secret_scan_exclude skips the generic patterns in test data;
private keys, AWS key ids and full hsak_/sk-or-v1- keys stay flagged everywhere.
- Files in the docs category never match the hard-YELLOW paths.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The guides state why model and classifier findings are only ORANGE:
the repository administrator on dev.hostsharing.net is an operator, so an admin merge override is no way out of a false RED.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
werkrevisor 0.6.0: four verdict colours, and only deterministic rules block hard.
warning, exit 15 where codes are distinguished, 0 in approval mode).[ ], bullet or paragraph without checkbox under "Open Questions"/"Offene Fragen").FIXME.reviewmarkers in findings, secret scan ignoressrc/test/**except real key formats, documentation files trigger no hard-YELLOW path rules.Reason: the repository admin on dev.hostsharing.net is an operator, so an admin merge override is no way out of a false RED; model and classifier findings are often wrong (3 of 8 Sonnet findings in the comparison).
222 unit tests green in the pinned PR-Agent image.
Open: whether Gitea ignores a stale bot REQUEST_CHANGES after a later ORANGE/YELLOW head; tested on werkprobe after the rollout.
🤖 Generated with Claude Code