CalvinBackup/gstack
1
0
Fork 0
mirror of https://github.com/garrytan/gstack.git synced 2026-09-09 14:38:59 +02:00
Code Issues Packages Projects Releases Wiki Activity

fix(review): advisory findings count in per-specialist stats

Browse Source 
Without this, simplification (all-advisory by construction) would log
findings:0 every run and auto-gate itself into permanent silence after 10
dispatches. The advisory carve-out governs score and header only.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Garry Tan
2026-08-29 05:18:34 +00:00
co-authored by Claude Fable 5
parent 385ca73283
commit ce7e3bff93
3 changed files with 15 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
scripts/resolvers/review-army.ts
+5
View File
@@ -213,6 +213,11 @@ For each specialist (testing, maintainability, security, performance, data-migra
- If skipped by gating: \`{"dispatched": false, "reason": "gated"}\`
- If not applicable (e.g., red-team not activated): omit from the object
Advisory findings COUNT in the stats \`findings\` field — the advisory
carve-out governs the quality score and the findings-count header only.
Logging simplification's advisories as \`findings: 0\` would auto-gate the
lens into permanent silence after 10 dispatches.
Include the Design specialist even though it uses \`design-checklist.md\` instead of the specialist schema files.
Remember these stats — you will need them for the review-log entry in Step 5.8.`;
}