great-cto 3.75.0 → 3.75.1

package/board/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "great-cto",
   "description": "You already have the agent. This is everything around it. great_cto runs Claude Code as a pipeline of 72 specialist agents \u2014 an independent model checks each stage before the next builds on it, spending caps refuse rather than warn, and three decisions stay yours: what gets built, how, and whether it ships.",
-  "version": "3.75.0",
+  "version": "3.75.1",
   "author": {
     "name": "Alexander Velikiy",
     "url": "https://hashnode.com/@Greatcto"

package/board/agents/code-reviewer.md

@@ -96,6 +96,16 @@ snapshots, binaries) are excluded, because their size is not review effort.
    passes if the function under test does nothing, so it asserts nothing), comments
    that lie, an abstraction that hides a bug. Match the surrounding code's idiom.
 
+   **Stub pass over new tests — do it for every test the diff adds.** Picture the
+   function under test replaced by a stub that returns nothing and does nothing, and
+   run each new test against it in your head. Assertions that something did *not*
+   happen (`not.toHaveBeenCalled`, `not.toThrow`, `resolves`, "is defined") pass
+   against that stub. A test made only of them asserts nothing, however correct the
+   code beside it: that is a **Finding (P2)**, not an Observation — the evidence is the
+   test line itself. Cite each such line, say it passes for a do-nothing function,
+   and name the positive assertion that is missing (the call that must happen, the
+   value that must come back). Judge the test, not your guess about the implementation.
+
 ## Calibration — apply `shared/agent-fragments/argument-quality.md`
 
 Every finding carries **severity + concrete evidence (file:line or a metric)**.

package/board/agents/project-auditor.md

@@ -225,7 +225,7 @@ bash scripts/auditor-architectural-debt-scan.sh
 
 Runs all of Phase 4 (sections labeled in stdout):
 - **4A.0** intersects the top-20 largest source files with the top-20 most-git-churned files
-  (last 6 months), writing scratch files to `/tmp/audit-{largest,churn,hotspots}.txt`. Every
+  (last 6 months), writing scratch files to ``$AUDIT_TMP/audit-{largest,churn,hotspots}.txt` (default `/tmp`). Every
   file in the intersection MUST receive concrete file:line citations in the findings table —
   these are the most expensive places to leave debt unaddressed. A hotspot with no test
   beside it gets "characterize before change" in its Recommendation: the first edit there

package/board/agents/qa-engineer.md

@@ -613,7 +613,7 @@ suite **catches**. A surviving mutant is a fault your tests would have shipped.
 
 Small tasks skip the run, not the question: the cheap form is the empty-implementation
 check — stub the function under test to do nothing; a test that still passes asserts
-nothing. senior-dev runs it at RED and code-reviewer flags it; if you see such a test
+nothing. senior-dev runs it before GREEN and code-reviewer flags it; if you see such a test
 in a small task, report it.
 
 Run it on the **changed files only** — a full-repo mutation run is minutes-to-hours

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "great-cto",
-  "version": "3.75.0",
+  "version": "3.75.1",
   "description": "One command install for the great_cto Claude Code plugin. Auto-detects your stack, picks the right archetype, bootstraps PROJECT.md.",
   "keywords": [
     "claude-code",