roles.sh had been red for a while, hiding everything behind whatever failed first: - planner.md was bumped to 4.2.0 (board-triggered split mode) without updating the test's hardcoded 4.1.0 expectations. - reviewer.md had drifted two minor versions ahead of its catalog.json entry (1.6.0 registered vs. 1.8.0 actual) across two prior commits that never touched the catalog; catalog.json now matches. - researcher.json's generic Bash(*) grant is an intentional, already deployed capability (docs/intent/research-pipeline-researcher-shell.md) that the blanket "no self-close settings file may hold Bash(*)" loop didn't know about; researcher.json is now a documented exception with its own check that the required deny-prefix list stays in place. - fixer.md's Inspector/Fixer split reworded "erfolgreichen Review" to "erfolgreichem Review"; the substring assertion didn't follow. - the operator.json permission check had a jq and/or precedence bug (missing parens around length == N clauses) that made it error out rather than actually check anything. agents/tests/roles.sh, agents/tests/fixer-role.sh and agents/tests/inspector-role.sh all pass end to end now. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01T7UVrKsttMP9a6FiGFna9b |
||
|---|---|---|
| .. | ||
| fixer-role.sh | ||
| inspector-role.sh | ||
| roles.sh | ||