godpowers 3.11.0 → 3.13.1

package/lib/state.js

@@ -53,10 +53,26 @@ const SUBSTEP_LABELS = {
  * @property {number} ordinal One-based step position.
  */
 
+// Canonical project-relative location of the state file. Other modules that
+// need to name state.json (gates, dispatch findings, audits) import this rather
+// than re-typing the literal (ARC-002).
+const STATE_FILE = '.godpowers/state.json';
+
 function statePath(projectRoot) {
   return path.join(projectRoot, '.godpowers', 'state.json');
 }
 
+// A typed error so callers (e.g. the CLI dispatcher) can detect corrupt state
+// by `err.code === 'CORRUPT_STATE'` instead of matching the message prose.
+function corruptStateError(file, cause) {
+  const err = new Error(
+    `Corrupt state file at ${file}: ${cause.message}. ` +
+    `Fix the JSON or remove the file to let Godpowers reinitialize it.`
+  );
+  err.code = 'CORRUPT_STATE';
+  return err;
+}
+
 function tierNumber(tierKey) {
   const match = String(tierKey).match(/^tier-(\d+)$/);
   return match ? Number(match[1]) : Number.MAX_SAFE_INTEGER;
@@ -88,10 +104,7 @@ function read(projectRoot) {
   try {
     return JSON.parse(raw);
   } catch (e) {
-    throw new Error(
-      `Corrupt state file at ${file}: ${e.message}. ` +
-      `Fix the JSON or remove the file to let Godpowers reinitialize it.`
-    );
+    throw corruptStateError(file, e);
   }
 }
 
@@ -144,10 +157,7 @@ async function readAsync(projectRoot) {
   try {
     return JSON.parse(raw);
   } catch (e) {
-    throw new Error(
-      `Corrupt state file at ${file}: ${e.message}. ` +
-      `Fix the JSON or remove the file to let Godpowers reinitialize it.`
-    );
+    throw corruptStateError(file, e);
   }
 }
 
@@ -421,6 +431,7 @@ module.exports = {
   updateSubStepAsync,
   hashFile,
   detectDrift,
+  STATE_FILE,
   statePath,
   isInitialized,
   isInitializedState,

package/lib/sync-fs.js

@@ -0,0 +1,37 @@
+/**
+ * Shared filesystem helpers for the lib/*-sync.js family.
+ *
+ * Every sync module used to redefine its own byte-identical read/write/exists/
+ * readJson against a project root (ARC-001). They now share these so a change
+ * to path handling or read semantics lives in one place. Module-specific log
+ * writers (appendLog) stay per-module because their headers and formats differ.
+ */
+
+const fs = require('fs');
+const path = require('path');
+
+function read(projectRoot, relPath) {
+  const file = path.join(projectRoot, relPath);
+  if (!fs.existsSync(file)) return '';
+  return fs.readFileSync(file, 'utf8');
+}
+
+function write(projectRoot, relPath, content) {
+  const file = path.join(projectRoot, relPath);
+  fs.mkdirSync(path.dirname(file), { recursive: true });
+  fs.writeFileSync(file, content);
+}
+
+function exists(projectRoot, relPath) {
+  return fs.existsSync(path.join(projectRoot, relPath));
+}
+
+function readJson(projectRoot, relPath) {
+  try {
+    return JSON.parse(read(projectRoot, relPath));
+  } catch (err) {
+    return null;
+  }
+}
+
+module.exports = { read, write, exists, readJson };

package/lib/text-util.js

@@ -0,0 +1,19 @@
+/**
+ * Small shared string helpers (QUAL-002).
+ *
+ * slugify is the canonical home for the "lowercase, collapse non-alphanumerics
+ * to '-', strip edge '-', truncate to 40 chars" contract. lib/evidence.js keeps
+ * its own copy on purpose: that module is vendored from the upstream engine and
+ * its helpers are provenance-tracked, so it must not import first-party code.
+ */
+
+function slugify(text, fallback = '') {
+  const slug = String(text == null ? '' : text)
+    .toLowerCase()
+    .replace(/[^a-z0-9]+/g, '-')
+    .replace(/^-+|-+$/g, '')
+    .slice(0, 40);
+  return slug || fallback;
+}
+
+module.exports = { slugify };

package/lib/workflow-helper-groups.js

@@ -6,6 +6,10 @@
  */
 
 const HELPER_GROUPS = {
+  'context-bootstrap': [
+    'pillars-detect',
+    'pillars-init'
+  ],
   'standard-closeout': [
     'repo-doc-sync',
     'repo-surface-sync',

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "godpowers",
-  "version": "3.11.0",
+  "version": "3.13.1",
   "description": "AI-powered development system: 120 slash commands and 40 specialist agents that take a project from raw idea to hardened production. Runs inside Claude Code, Codex, Cursor, Windsurf, Gemini, and 10+ other AI coding tools.",
   "bin": {
     "godpowers": "./bin/install.js"
@@ -24,7 +24,7 @@
     "test:e2e": "node tests/integration/full-arc.test.js",
     "test:mcp": "npm --workspace @godpowers/mcp test",
     "coverage": "c8 --reporter=text --reporter=lcov node scripts/run-tests.js",
-    "coverage:lib": "c8 --include=lib/**/*.js --check-coverage --lines 90 --reporter=text node scripts/run-tests.js",
+    "coverage:lib": "c8 --include=lib/**/*.js --check-coverage --lines 90 --branches 75 --reporter=text node scripts/run-tests.js",
     "test:audit": "npm audit --omit=dev && git diff --check && npm run test:surface",
     "pack:check": "node scripts/check-package-contents.js",
     "pack:mcp:check": "npm --workspace @godpowers/mcp run pack:check",

package/references/orchestration/GOD-ORCHESTRATOR-RUNBOOK.md

@@ -115,6 +115,13 @@ This converts existing Godpowers artifacts into managed source references in
 the relevant pillar files, so old projects are Pillar-ized as part of being
 Godpower-ized.
 
+In the greenfield `full-arc` workflow this start-of-arc step is surfaced as the
+tier-0 `context` job, whose `context-bootstrap` helper group expands to
+`pillars-detect` (`lib/pillars.detect`) and `pillars-init` (`lib/pillars.init`).
+The job uses `god-orchestrator` as a local runtime call, not a `god-context-writer`
+spawn, so it changes nothing about the behavior described above; it only makes the
+init visible in `/god-mode --plan` alongside the closeout `pillars-sync-plan`.
+
 Before each major command, compute the task-specific Pillars load set with
 `lib/pillars.computeLoadSet(projectRoot, taskText)`. Load `agents/context.md`
 and `agents/repo.md` first, then the routed primary pillars and their direct
@@ -367,6 +374,46 @@ after tests pass. If a git remote exists and the user passed an explicit push
 flag or the project intent says pushing is allowed, push after the green commit
 and then continue the project run. Pushing is not a terminal state.
 
+## Audit-Remediation Loop
+
+Run a bounded audit-then-remediate loop in three cases: the `full-arc`
+**`code-audit` step** (it runs `god-debt-assessor` after build and before the
+shipping tier, because AI-generated code can miss things a per-slice review and
+the security gate do not); intent like "audit and fix until clean" (the
+`audit-remediate` recipe); and any standalone `/god-tech-debt` follow-up. In
+`full-arc` the loop must drive Confirmed Critical and High findings to closure
+(or pause them as blockers) before `deploy`, `harden`, and `launch` proceed. The
+maker that fixes is never the checker that grades.
+
+1. **Audit (read-only).** Spawn `god-debt-assessor` in a fresh context. It writes
+   the scored, self-contained report to `.godpowers/tech-debt/REPORT.md` with
+   stable finding IDs (SEC-001, etc.), each carrying Severity, Confidence, Effort,
+   `file:line`, and a "Verify the fix" step.
+2. **Select.** Take the "What to fix first" list: Confirmed Critical and High,
+   worst-first, root causes (systemic patterns) before leaves. Re-verify any
+   Suspected finding against the cited code before touching it; never act on an
+   unconfirmed claim.
+3. **Drive each finding to closure** with an outcome loop so the loop is bounded
+   and self-arresting:
+   - `npx godpowers outcome start fix-<ID> --verify "<the finding's verify command>" --substep <tier.substep> --project=.`
+   - Spawn `god-debugger` (or the owning specialist) in a fresh context with only
+     that finding's evidence and touched files to draft the fix.
+   - Spawn an **independent** reviewer (`god-quality-reviewer`, or
+     `god-harden-auditor` for a SEC finding) in a fresh context to verify the fix
+     against the cited evidence and the project's tests. The maker does not grade
+     its own work.
+   - `npx godpowers outcome check fix-<ID> --project=.` runs the finding's verify
+     command and records the iteration. Repeat until the outcome succeeds or the
+     budget is exhausted.
+   - Never mark a finding resolved while `can-close` for its substep is red.
+4. **Re-audit.** Re-run `god-debt-assessor` and confirm findings are resolved,
+   not relocated, and that no Strength regressed. The loop is done when no
+   Confirmed Critical or High remains (or the agreed bucket is empty).
+5. **Pause, do not fake.** Anything that cannot be fixed within budget, or that
+   is `human-only` (scope, credentials, vendor/legal/Critical-security
+   acceptance), lands as a precise paused blocker with the finding ID, not a
+   silent skip. "Clean" is an evidence-backed re-audit, never a claim.
+
 ## Shipping Closure Protocol
 
 The shipping tier must not end by listing a broad provider checklist. God Mode

package/routing/recipes/audit-remediate.yaml

@@ -0,0 +1,30 @@
+apiVersion: godpowers/v1
+kind: Recipe
+metadata:
+  name: audit-remediate
+  category: maintaining
+  description: "Audit the codebase, then drive the findings to zero"
+
+triggers:
+  intent-keywords:
+    - "audit and fix"
+    - "fix all the audit findings"
+    - "drive the audit to clean"
+    - "remediate tech debt"
+    - "fix the codebase until clean"
+    - "pay down tech debt"
+    - "address all the findings"
+    - "code audit and fix"
+
+sequences:
+  default:
+    description: "Audit the codebase, then drive the findings to zero"
+    steps:
+      - command: "/god-tech-debt"
+        why: "Score the codebase and write the prioritized, self-contained audit report (god-debt-assessor)"
+      - command: "/god-debug"
+        why: "Fix each Confirmed Critical/High finding worst-first; an independent reviewer verifies each fix against the cited evidence"
+      - command: "/god-tech-debt"
+        why: "Re-audit to confirm findings are resolved not relocated and no strength regressed; the orchestrator loops this under an outcome budget until clean"
+
+default-sequence: default

package/skills/god-version.md

@@ -16,7 +16,7 @@ Print version and a short capability summary.
 ```
 Godpowers v2.3.1
 Install: /Users/.../.claude/  (matches package.json)
-Surface: 120 skills, 40 agents, 13 workflows, 43 recipes
+Surface: 120 skills, 40 agents, 13 workflows, 44 recipes
 Schema: intent.v1, state.v1, events.v1, workflow.v1, routing.v1, recipe.v1
 External integrations available: impeccable, agent-browser (others lazy)
 Feature awareness: planning-system migration, source-system sync-back, context refresh, dashboard status labels, repo documentation sync, repo surface sync, quick proof, request trace, release hardening, maintenance hardening

package/workflows/full-arc.yaml

@@ -3,6 +3,15 @@
 # the agents in the order this file specifies. To preview without running,
 # use `/god-mode --workflow=<name> --plan`.
 #
+# Native Pillars context (AGENTS.md + agents/context.md + agents/repo.md) is
+# woven through this arc by the orchestrator's local runtime, not a specialist
+# agent. It is now visible at both ends: the tier-0 `context` preamble runs
+# context-bootstrap (lib/pillars.detect then lib/pillars.init) so a greenfield
+# project is Pillar-ized before planning, and the `final-sync` standard-closeout
+# runs pillars-sync-plan (lib/pillars.planArtifactSync) so the pillars reflect
+# the artifacts the arc produced. Both are local runtime calls; see
+# references/orchestration/GOD-ORCHESTRATOR-RUNBOOK.md "Native Pillars context".
+#
 apiVersion: godpowers/v1
 kind: Workflow
 metadata:
@@ -15,8 +24,17 @@ metadata:
 on: [/god-mode]
 
 jobs:
+  context:
+    tier: 0
+    uses: god-orchestrator@^1.0.0
+    local-helper-groups:
+      - context-bootstrap
+    with:
+      action: pillars-bootstrap
+
   prd:
     tier: 1
+    needs: context
     uses: god-pm@^1.0.0
     with:
       template: PRD.md
@@ -62,9 +80,16 @@ jobs:
     verification:
       required: [test, lint, typecheck-or-check]
 
+  code-audit:
+    tier: 2
+    needs: build
+    uses: god-debt-assessor@^1.0.0
+    with:
+      mode: post-build-audit
+
   deploy:
     tier: 3
-    needs: build
+    needs: code-audit
     uses: god-deploy-engineer@^1.0.0
     closure:
       on-missing-external-access: create-waiting-access-bundle
@@ -84,14 +109,21 @@ jobs:
 
   harden:
     tier: 3
-    needs: build
+    needs: code-audit
     uses: god-harden-auditor@^1.0.0
     blocks-on:
       - critical-finding: pause
 
-  launch:
+  docs:
     tier: 3
     needs: harden
+    uses: god-docs-writer@^1.0.0
+    with:
+      mode: product-docs-verify
+
+  launch:
+    tier: 3
+    needs: docs
     uses: god-launch-strategist@^1.0.0
     with:
       template: HARDEN-FINDINGS.md