great-cto 2.86.0 → 2.87.1

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

@@ -2,7 +2,7 @@
   "name": "great_cto",
   "id": "great_cto",
   "description": "Engineering process for solo founders and teams up to 50 engineers. Agents do architecture, code review, QA, and security. You make two decisions per feature.",
-  "version": "2.86.0",
+  "version": "2.87.1",
   "author": {
     "name": "Great CTO",
     "url": "https://github.com/avelikiy/great_cto"
@@ -152,6 +152,12 @@
             "command": "PLUGIN_DIR=$(ls -d ~/.claude/plugins/cache/local/great_cto/*/ 2>/dev/null | sort -V | tail -1 | sed 's|/$||'); node \"${PLUGIN_DIR}/scripts/hooks/frozen-gates-guard.mjs\" 2>&1; EXIT=$?; if [ $EXIT -eq 2 ]; then exit 2; fi; exit 0",
             "timeout": 5,
             "statusMessage": "Checking frozen gates..."
+          },
+          {
+            "type": "command",
+            "command": "PLUGIN_DIR=$(ls -d ~/.claude/plugins/cache/local/great_cto/*/ 2>/dev/null | sort -V | tail -1 | sed 's|/$||'); node \"${PLUGIN_DIR}/scripts/hooks/edit-scope-guard.mjs\" 2>&1; EXIT=$?; if [ $EXIT -eq 2 ]; then exit 2; fi; exit 0",
+            "timeout": 5,
+            "statusMessage": "Checking edit scope..."
           }
         ]
       }

package/board/packages/board/lib/metrics.mjs

@@ -5,6 +5,25 @@ import { sseClients, bdCache } from './state.mjs';
 import { getTasks } from './beads.mjs';
 import { readVerdicts, readPlanCosts, readQAStats, readSecStats } from './verdicts.mjs';
 
+// Acceptance-oriented metrics (the "verified acceptance" shift): measure the cost
+// of a change that a gate actually APPROVED — not throughput — and how often work
+// was sent back before it landed. Both derive from verdict logs already on disk;
+// no new capture. cost_per_accepted is null when nothing was accepted in the
+// window: dividing a real cost by zero approvals would invent a number, and "no
+// accepted change yet" is the honest reading (same discipline as the null-score
+// oracle). Only two of the five metrics the literature lists are built here on
+// purpose — a solo project's denominator is tiny and the other three would be noise.
+function acceptanceMetrics(verdicts = [], windowCostUsd = null) {
+  const isAccepted = (v) => /^APPROVED$/i.test(v.verdict || '');
+  const isRework = (v) => /^(CHANGES(_REQUESTED)?|REJECT(ED)?|FAIL(ED)?|BLOCKED)$/i.test(v.verdict || '');
+  const accepted = verdicts.filter(isAccepted).length;
+  const rework_rounds = verdicts.filter(isRework).length;
+  const cost_per_accepted = (accepted > 0 && windowCostUsd != null)
+    ? Math.round((windowCostUsd / accepted) * 100) / 100
+    : null;
+  return { accepted, cost_per_accepted, rework_rounds };
+}
+
 // ── Metrics ────────────────────────────────────────────────────────────────────
 function getMetrics(cwd = process.cwd(), days = 30) {
   // `days` controls the window for cost/agents_cost and for "shipped in window".
@@ -245,8 +264,14 @@ function getMetrics(cwd = process.cwd(), days = 30) {
   // Count tasks completed in selected window (for period-scoped reports)
   const doneInWindow = done.filter(t => t.closed_at && (now - new Date(t.closed_at).getTime()) <= costWindowMs);
 
+  // Acceptance metrics over the same window as cost, so cost_per_accepted lines
+  // up with the cost tile.
+  const verdictsInWindow = verdicts.filter(v => v.ts && (now - new Date(v.ts).getTime()) <= costWindowMs);
+  const acceptance = acceptanceMetrics(verdictsInWindow, cost.llm_usd);
+
   return {
     window_days: days,
+    acceptance,
     tasks: {
       total: tasks.length,
       done: done.length,
@@ -304,4 +329,5 @@ function getCanonicalAgents() {
   return set;
 }
 
-export { getMetrics, getCanonicalAgents };
+export {
+  acceptanceMetrics, getMetrics, getCanonicalAgents };

package/board/packages/board/public/index.html

@@ -4174,9 +4174,15 @@ function renderDashboard(m) {
       <div class="metric-trend">${s.trend}</div>
     </div>`).join('');
 
+  const acc = m.acceptance || {};
   const secondary = [
     { v: avgMin ? `${avgMin}` : '—', sub: avgMin ? 'm' : '', label: cycleStat },
     { v: m.qa?.pass_rate != null ? m.qa.pass_rate : '—', sub: m.qa?.pass_rate != null ? '%' : '', label: m.qa?.pass_rate != null ? 'QA pass rate' : 'QA — run /qa', cls: 'green' },
+    // Verified-acceptance metrics: cost of a change a gate actually APPROVED, and
+    // how often work bounced. '—' when nothing was accepted in the window — an
+    // honest gap, not a zero.
+    { v: acc.cost_per_accepted != null ? `$${acc.cost_per_accepted.toFixed(2)}` : '—', sub: '', label: acc.accepted ? `Cost / accepted (${acc.accepted})` : 'Cost / accepted' },
+    { v: acc.rework_rounds ?? 0, sub: '', label: 'Rework rounds', cls: acc.rework_rounds ? 'amber' : 'green' },
     { v: m.security?.blocked ?? 0, sub: '', label: 'Open security blocks', cls: m.security?.blocked ? 'red' : 'green' },
     { v: m.tasks?.in_progress ?? 0, sub: '', label: 'In progress', cls: 'amber' },
   ];

package/dist/adapt.js

@@ -541,6 +541,34 @@ export async function runAdapt(args) {
         if (!meta.aiTools.includes("cursor") && !meta.aiTools.includes("copilot") && !meta.aiTools.includes("windsurf")) {
             console.log(`  Tip: add other AI tools to ai_tools: [] in PROJECT.md to generate .cursorrules, copilot-instructions.md, etc.`);
         }
+        for (const line of nextStepsAfterAdapt(meta.aiTools))
+            console.log(line);
     }
     return 0;
 }
+/**
+ * What to do AFTER the configs exist.
+ *
+ * Telemetry showed `adapt` at 69 of 100 recorded runs against 2 for `board`:
+ * people run it, come back, run it again. Both of this command's closing lines
+ * used to point back at itself ("re-run after editing…", "add more tools…") and
+ * nothing pointed forward, so the command taught its own loop.
+ *
+ * The pointer is tool-aware on purpose. `adapt` is the one command that serves
+ * non-Claude-Code users (Cursor / Copilot / Windsurf / Aider), and the agent
+ * pipeline is Claude-Code-only — telling a Cursor user to run `/audit` would be
+ * a dead end, which is worse than saying nothing. So: pipeline steps only where
+ * the pipeline exists; otherwise say plainly what they have and what it would
+ * take to get the rest.
+ */
+export function nextStepsAfterAdapt(aiTools = []) {
+    const hasClaude = aiTools.includes("claude-code");
+    const out = ["", "Next:"];
+    if (hasClaude) {
+        out.push("  1. Restart Claude Code so it picks up the regenerated CLAUDE.md.", "  2. /audit    — full analysis of this codebase (existing project)", "     /start    — scope and build a new feature (greenfield)", "     /inbox    — what needs your decision right now", "  3. great-cto board — Kanban + CTO dashboard at localhost:3141");
+    }
+    else {
+        out.push(`  Your ${aiTools.join(" / ")} config is live — reload the tool to pick it up.`, "  The agent pipeline (architecture review, QA, security gates) runs inside", "  Claude Code. To use it here: add claude-code to ai_tools in PROJECT.md,", "  then `npx great-cto install`.");
+    }
+    return out;
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "great-cto",
-  "version": "2.86.0",
+  "version": "2.87.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",