godpowers 1.6.22 → 1.6.24

package/hooks/pre-tool-use.sh

@@ -1,7 +1,8 @@
 #!/usr/bin/env bash
 # Godpowers PreToolUse Safety Hook
 # Runs before destructive tool calls in a Godpowers project.
-# Warns on: rm -rf, git reset --hard, force push to main, deleting .godpowers/
+# Warns on: rm -rf, git reset --hard, force push to main, deleting .godpowers/,
+# and irreversible public release actions.
 
 set -euo pipefail
 
@@ -31,6 +32,17 @@ case "$TOOL_INPUT" in
     echo "destroy collaborators' work."
     exit 1
     ;;
+  *"npm publish"*)
+    echo "WARNING: npm publish is a public release action."
+    echo "Confirm release checklist, repo-doc-sync, repo-surface-sync,"
+    echo "release-surface-sync, package contents, and installer smoke first."
+    exit 1
+    ;;
+  *"gh release create"*)
+    echo "WARNING: gh release create publishes public release notes."
+    echo "Confirm README, badges, CHANGELOG, RELEASE, package, tag, and npm version agree."
+    exit 1
+    ;;
   *"rm -rf node_modules"*)
     # Allowed: this is just cache
     exit 0

package/hooks/session-start.sh

@@ -30,6 +30,17 @@ cat <<'EOF'
 A Godpowers project is active in this directory.
 EOF
 
+# Prefer the shared dashboard action brief when the installed CLI is available.
+# This keeps hook orientation aligned with /god-status and /god-next.
+if command -v godpowers >/dev/null 2>&1; then
+  BRIEF="$(godpowers status --project . --brief 2>/dev/null | head -30 || true)"
+  if [ -n "$BRIEF" ]; then
+    echo ""
+    echo "$BRIEF"
+    echo ""
+  fi
+fi
+
 # Prefer CHECKPOINT.md (the orient-a-new-session pin) when present
 if [ -f "$CHECKPOINT_FILE" ]; then
   echo ""
@@ -69,6 +80,7 @@ Next step: run /god-next  (it inspects disk state and proposes the next command)
 Or:       /god-mode for the full autonomous project run
 Or:       /god-help to see the catalog
 Or:       /god-status for the full project snapshot
+Or:       /god-context refresh after installing a newer Godpowers runtime
 
 Disk state is authoritative. Conversation memory is not.
 EOF

package/lib/automation-providers.js

@@ -14,6 +14,24 @@ const os = require('os');
 
 const CONFIG_PATH = '.godpowers/automations.json';
 
+const STRICT_RELEASE_SURFACES = [
+  'root docs: README.md, CHANGELOG.md, RELEASE.md, CONTRIBUTING.md, SUPPORT.md, USERS.md, ARCHITECTURE.md, ARCHITECTURE-MAP.md, AGENTS.md, SKILL.md',
+  'docs/: release checklist, roadmap, reference, validation, concepts, getting started, feature awareness, auto-invoke visibility, repo sync docs',
+  'agents/: pillar files and specialist agent contracts',
+  'skills/: command skills and release-visible examples',
+  'routing/: command routes and high-frequency recipes',
+  'workflows/: full arc, feature, hotfix, refactor, migration, docs, deps, hygiene, suite, and audit workflows',
+  'schema/: events, intent, routing, recipe, state, workflow, and extension schemas',
+  'templates/: generated artifact templates and update logs',
+  'references/: have-nots, orchestration, planning, building, design, and shared references',
+  'hooks/: session-start and pre-tool-use runtime hooks',
+  'lib/: sync detectors, release guardrails, host capabilities, automation providers, and runtime helpers',
+  'scripts/: release gate, smoke, package, and sync tests',
+  'tests/ and fixtures/: integration, dogfood, and golden fixtures',
+  '.github/workflows/: CI, publish, and pack publish gates',
+  'package surface: package.json, package-lock.json, npm files list, pack contents, npm latest, git tag, and release notes'
+];
+
 const SAFE_TEMPLATES = [
   {
     id: 'daily-status',
@@ -43,6 +61,20 @@ const SAFE_TEMPLATES = [
     risk: 'read-only',
     prompt: 'Run a read-only hygiene summary for docs drift, dependency signals, checkpoint age, and pending reviews.'
   },
+  {
+    id: 'strict-release-readiness',
+    title: 'Strict release readiness report',
+    cadence: 'Manual, before release, or weekly before planned releases',
+    risk: 'read-only, fail-closed',
+    surfaces: STRICT_RELEASE_SURFACES.slice(),
+    prompt: [
+      'Run strict release readiness for every required Godpowers release surface.',
+      'Check root docs, docs/, agents/, skills/, routing/, workflows/, schema/, templates/, references/, hooks/, lib/, scripts/, tests/, fixtures/, .github/workflows/, package metadata, git tag state, GitHub release state, npm latest, and local install state.',
+      'Run or report the status of repo documentation sync, repo surface sync, route quality sync, recipe coverage sync, release surface sync, automation surface sync, package content checks, release gate status, CI status, publish workflow status, forbidden character scan, stale version scan, and unstaged work.',
+      'Fail closed when any required surface is unchecked, stale, missing from the package manifest, not covered by tests, or inconsistent with the intended version.',
+      'Summarize blockers and exact next commands only. Do not modify files, stage, commit, tag, push, create a GitHub release, publish to npm, delete files, or clear caches.'
+    ].join(' ')
+  },
   {
     id: 'release-readiness',
     title: 'Release readiness report',

package/lib/events.js

@@ -20,6 +20,12 @@ const VALID_EVENT_NAMES = new Set([
   'gate.fail', 'gate.pass',
   'tier.skip',
   'state.repair', 'state.rollback',
+  'local-helper.run', 'local-helper.complete',
+  'dashboard.render',
+  'host-capabilities.detect',
+  'dogfood.run',
+  'source-system.import', 'source-system.sync-back',
+  'repo-doc-sync.detect', 'repo-surface-sync.detect',
   'extension.install', 'extension.activate',
   // Cost / cache / budget (v0.14 token cost saver)
   'cost.recorded', 'cache.hit', 'cache.miss', 'budget.exceeded',

package/lib/feature-awareness.js

@@ -71,6 +71,12 @@ const FEATURES = [
     commands: ['/god-dogfood'],
     description: 'Run messy-repo fixtures for migration, host guarantee, extension authoring, and suite release readiness.'
   },
+  {
+    id: 'dashboard-action-brief',
+    since: '1.6.22',
+    commands: ['/god-status', '/god-next', '/god-mode'],
+    description: 'Render compressed action brief, readiness, attention, and host guarantee lines from disk state.'
+  },
   {
     id: 'host-capabilities',
     since: '1.6.22',
@@ -82,6 +88,12 @@ const FEATURES = [
     since: '1.6.22',
     commands: ['/god-extension-add', '/god-test-extension'],
     description: 'Scaffold and validate publishable Godpowers extension packs.'
+  },
+  {
+    id: 'suite-release-dry-run',
+    since: '1.6.22',
+    commands: ['/god-suite-release'],
+    description: 'Plan Mode D suite releases with impacted dependents and planned writes before mutation.'
   }
 ];
 

package/lib/have-nots-validator.js

@@ -1,7 +1,7 @@
 /**
  * Have-Nots Validator
  *
- * Registry of mechanical checks against the 99 named have-nots from
+ * Registry of mechanical checks against the 156 named have-nots from
  * references/HAVE-NOTS.md. Each check returns structured findings:
  *
  *   { code, severity: 'error'|'warning'|'info', line, column, message, suggestion }
@@ -70,7 +70,7 @@ function findPositions(content, regex) {
 /** U-08: em or en dash present */
 function checkEmEnDash(content) {
   const findings = [];
-  const positions = findPositions(content, /[–—]/g);
+  const positions = findPositions(content, /[\u2013\u2014]/g);
   for (const p of positions) {
     findings.push({
       code: 'U-08',

package/lib/workflow-runner.js

@@ -111,6 +111,7 @@ function plan(workflow, ctx = {}) {
         review: job.review || null,
         'on-pass': job['on-pass'] || null,
         'on-fail': job['on-fail'] || null,
+        localHelpers: job['local-helpers'] || [],
         with: job.with || null
       });
     }
@@ -191,6 +192,9 @@ function serializePlan(p) {
       if (step.tier) lines.push(`        tier: ${step.tier}`);
       if (step.agent) lines.push(`        agent: ${step.agent}`);
       if (step.uses)  lines.push(`        uses: ${step.uses}`);
+      if (step.localHelpers && step.localHelpers.length) {
+        lines.push(`        local-helpers: [${step.localHelpers.join(', ')}]`);
+      }
       if (step.needs && step.needs.length) {
         lines.push(`        needs: [${step.needs.join(', ')}]`);
       }

package/package.json

@@ -1,13 +1,13 @@
 {
   "name": "godpowers",
-  "version": "1.6.22",
+  "version": "1.6.24",
   "description": "AI-powered development system: 110 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"
   },
   "scripts": {
     "test": "node scripts/validate-skills.js && node scripts/test-doc-surface-counts.js && bash scripts/smoke.sh && node scripts/test-runtime.js && node scripts/test-router.js && node scripts/test-recipes.js && node scripts/test-context-writer.js && node scripts/test-pillars.js && node scripts/test-artifact-linter.js && node scripts/test-artifact-diff.js && node scripts/test-design-foundation.js && node scripts/test-linkage.js && node scripts/test-impact.js && node scripts/test-reverse-sync.js && node scripts/test-planning-systems.js && node scripts/test-feature-awareness.js && node scripts/test-repo-doc-sync.js && node scripts/test-repo-surface-sync.js && node scripts/test-automation-surface-sync.js && node scripts/test-host-capabilities.js && node scripts/test-extension-authoring.js && node scripts/test-dogfood-runner.js && node scripts/test-integration.js && node scripts/test-cross-artifact.js && node scripts/test-awesome-design.js && node scripts/test-skillui-bridge.js && node scripts/test-runtime-verification.js && node scripts/test-agent-browser.js && node scripts/test-mode-d.js && node scripts/test-runtime-heuristics.js && node scripts/test-agent-validator.js && node scripts/test-story-validator.js && node scripts/test-state.js && node scripts/test-dashboard.js && node scripts/test-automation-providers.js && node scripts/test-intent.js && node scripts/test-events.js && node scripts/test-golden-artifacts.js && node scripts/test-install-smoke.js && node scripts/test-checkpoint.js && node scripts/test-extensions.js && node scripts/test-event-reader.js && node scripts/test-state-lock.js && node scripts/test-cost-saver.js && node scripts/test-budget-onoff.js && node scripts/test-workflow-runner.js && npm run test:e2e && node scripts/test-otel-exporter.js && node scripts/test-extensions-publish.js",
-    "prepublishOnly": "npm test",
+    "prepublishOnly": "npm run release:check",
     "validate-skills": "node scripts/validate-skills.js",
     "test:surface": "node scripts/test-doc-surface-counts.js",
     "smoke": "bash scripts/smoke.sh",

package/references/HAVE-NOTS.md

@@ -78,6 +78,22 @@ the Decisions Log. Fail.
 ### O-06 YOLO decisions silent
 --yolo flag was used but no YOLO-DECISIONS log was emitted. Fail.
 
+### O-07 Invisible auto-invoke
+Automatic local helper or specialist work ran without reporting the trigger,
+agent status, helper result, changed artifacts, and next route. Fail.
+
+### O-08 Stale dashboard closeout
+A command completed without a disk-derived dashboard, action brief, or
+recommended next command. Fail.
+
+### O-09 Sync-back ambiguity
+Imported GSD, BMAD, or Superpowers context exists but the project does not say
+whether managed sync-back is enabled, disabled, or not applicable. Fail.
+
+### O-10 Host guarantees hidden
+The workflow relies on shell, git, npm, release tooling, or fresh-context
+agent spawning without reporting host guarantee level. Fail.
+
 ---
 
 ## Tier 1: Planning Have-Nots

package/references/orchestration/MODE-DETECTION.md

@@ -1,6 +1,7 @@
 # Mode Detection
 
-> How god-orchestrator decides which mode (A/B/C/D) to use.
+> How god-orchestrator decides which mode (A/B/C/E) to use, and when Mode D
+> suite coordination also applies.
 
 ## Mode A: Greenfield (default)
 
@@ -17,6 +18,8 @@
 - Some `.godpowers/<tier>/<artifact>` files already exist
 - OR existing codebase signals: package.json, Dockerfile, .github/workflows
 - User describes an existing project they want to add Godpowers to
+- GSD, BMAD, or Superpowers planning context is detected and should be imported
+  into Godpowers preparation artifacts
 
 **Behavior**:
 1. For each canonical artifact path: check existence on disk
@@ -30,6 +33,8 @@ Codebase signals (for inferring partial completion):
 - `.github/workflows/` or `.gitlab-ci.yml` exists -> CI present
 - `tests/` or `*.test.*` files exist -> Build tier in progress
 - `Dockerfile` + deploy config -> Deploy tier may be done
+- `.planning/`, `.gsd/`, `_bmad-output/`, `.bmad/`, or Superpowers specs ->
+  source-system import and managed sync-back may be needed
 
 ## Mode C: Audit
 
@@ -39,14 +44,34 @@ Codebase signals (for inferring partial completion):
 
 **Behavior**: run god-auditor on all existing artifacts. Build nothing.
 
-## Mode D: Multi-repo (FUTURE WORK)
+## Mode E: Bluefield
+
+**Signals**:
+- User is starting new code inside an existing organization or platform.
+- Parent or sibling directories contain org standards, shared packages,
+  deployment conventions, or platform contracts.
+- User names shared constraints such as approved infrastructure, design system,
+  compliance baseline, or internal libraries.
+
+**Behavior**:
+1. Load org context with `/god-org-context`.
+2. Run `/god-preflight` against the surrounding environment.
+3. Run a greenfield simulation audit against the org constraints.
+4. Use `god-greenfieldifier` to plan approved artifact updates.
+5. Continue the normal arc with the org constraints respected.
+
+## Mode D: Multi-repo suite membership
 
 **Signals**:
 - Working directory contains workspace config (pnpm-workspace.yaml, nx.json, lerna.json, turbo.json)
 - OR multiple sub-repos with their own `.git/`
 - User describes a system spanning multiple repos
+- `.godpowers/suite/` exists or sibling repos share byte-identical managed files
 
-**Status**: documented but not implemented in v0.4. Falls back to Mode A or B for the current repo.
+**Behavior**: Mode D is not a replacement for A/B/C/E. It is suite membership
+managed by `god-coordinator` as a Tier-0 peer. Each repo still runs one of
+A/B/C/E underneath, while `/god-suite-*` commands handle cross-repo status,
+sync, patch, and release planning.
 
 ## Worked example
 
@@ -72,3 +97,11 @@ Reports to user:
 > Setting Mode B (gap-fill). I'll work backward to fill missing artifacts.
 > First: I need to understand what this codebase does. Let me start with
 > /god-explore or you can describe it briefly."
+
+## Existing Godpowers projects after upgrades
+
+When `.godpowers/state.json` already exists, mode detection should also run
+feature awareness. The safe local helper records the installed Godpowers
+feature set, refreshes managed AI-tool context fences, and reports missing
+planning-system import or sync-back opportunities. It does not overwrite
+product artifacts.

package/references/orchestration/README.md

@@ -5,14 +5,17 @@ god-orchestrator and related agents.
 
 ## Files
 
-- (empty for now; content to be added in future releases)
+- [MODE-DETECTION.md](MODE-DETECTION.md): Mode A/B/C/E detection, plus Mode D
+  suite membership.
+- [SCALE-DETECTION.md](SCALE-DETECTION.md): scale rubric and calibration.
 
 ## Contribution Welcome
 
 This directory is the natural home for:
-- Mode A/B/C/D detection heuristics with worked examples
+- More Mode A/B/C/E and Mode D suite detection examples
 - Scale detection rubric with calibration cases
 - Pause vs no-pause decision tree examples
 - YOLO default rationale documents
+- Auto-invoke visibility examples for local helpers and specialist spawns
 
 If you'd like to contribute, see [CONTRIBUTING.md](../../CONTRIBUTING.md).

package/references/planning/ROADMAP-ANTIPATTERNS.md

@@ -4,7 +4,7 @@
 
 ## 1. The Date-Hopeful Roadmap
 
-**Sample**: "M-1: Auth — early Q3"
+**Sample**: "M-1: Auth, early Q3"
 
 **Why it fails**: "Early Q3" is not a gate, not a date, not a measurable
 state. The team treats it as soft, slippage compounds, and by mid-Q3 the

package/references/shared/ORCHESTRATORS.md

@@ -42,18 +42,47 @@ codebase mappers, story trackers). The rules below let them coexist.
 ## Migration into Godpowers
 
 If you arrive at Godpowers carrying artifacts from another system,
-`/god-init` Mode B (gap-fill) reads what exists and maps it forward:
-
-- Existing PRD-like documents -> `.godpowers/prd/PRD.md` (after
-  substitution-test rewrite if needed)
+`/god-init` Mode B (gap-fill) and `/god-migrate` read what exists and map it
+forward:
+
+- GSD `.planning/` or `.gsd/` context -> `.godpowers/prep/IMPORTED-CONTEXT.md`
+  and optional native seed artifacts
+- BMAD `_bmad-output/` or `.bmad/` context -> imported preparation context and
+  open questions for PRD, architecture, roadmap, and stack
+- Superpowers specs or plans -> imported preparation context and native
+  Godpowers seed artifacts when confidence is high
+- Existing PRD-like documents -> `.godpowers/prd/PRD.md` after
+  substitution-test rewrite if needed
 - Existing ADRs -> `.godpowers/arch/adr/`
-- Existing roadmap / milestones -> `.godpowers/roadmap/ROADMAP.md`
-- Existing story / ticket files -> `.godpowers/stories/STORY-*.md`
-  (via `/god-story`)
+- Existing roadmap or milestones -> `.godpowers/roadmap/ROADMAP.md`
+- Existing story or ticket files -> `.godpowers/stories/STORY-*.md` through
+  `/god-story`
+
+Mode B does not delete the source files. It produces Godpowers artifacts
+alongside them. Once parity is reached, you can retire the older system at
+your own pace.
+
+## Managed sync-back
+
+Godpowers can keep a source system informed without making that source system
+authoritative. `/god-sync` writes managed companion files such as:
+
+- `.planning/GODPOWERS-SYNC.md`
+- `_bmad-output/GODPOWERS-SYNC.md`
+- `docs/superpowers/GODPOWERS-SYNC.md`
+
+The sync-back file is a bridge, not a second source of truth. It should contain
+the current Godpowers status, imported-context mapping, open conflicts, and the
+next safe route back into either system. It must be fenced or companion-owned
+so Godpowers does not overwrite arbitrary GSD, BMAD, or Superpowers artifacts.
+
+## Existing Godpowers projects after upgrades
 
-Mode B does not delete the source files. It produces Godpowers
-artifacts alongside them. Once parity is reached, you can retire the
-older system at your own pace.
+Feature awareness is the upgrade path for projects that are already
+Godpowers-native. `/god-context refresh`, `/god-sync`, `/god-doctor --fix`, and
+God Mode resume can record the current runtime feature set, refresh managed AI
+tool fences, and point out missing migration, sync-back, dogfood, host
+capability, extension-authoring, or suite-release readiness.
 
 ## Migration out of Godpowers
 
@@ -64,7 +93,9 @@ frontmatter. There's no proprietary binary state. To leave:
 2. Strip the fenced "Implementation Linkage" footers if the target
    system doesn't understand them (they're recoverable from code
    annotations).
-3. Delete `.godpowers/`.
+3. Use the most recent managed sync-back file as the return-path summary if the
+   target system is GSD, BMAD, or Superpowers.
+4. Delete `.godpowers/`.
 
 ## What Godpowers does not try to be
 

package/references/shared/README.md

@@ -4,11 +4,11 @@ Cross-tier reference content used by multiple agents.
 
 ## Files
 
-- [HAVE-NOTS.md](../HAVE-NOTS.md) (canonical failure-mode catalog, 115 entries)
+- [HAVE-NOTS.md](../HAVE-NOTS.md) (canonical failure-mode catalog)
+- [ORCHESTRATORS.md](ORCHESTRATORS.md): composition patterns with other AI
+  coding workflow systems, including migration and managed sync-back.
+- [GLOSSARY.md](GLOSSARY.md): standardized vocabulary across tiers.
 
 ## Planned content
 
-- ORCHESTRATORS.md: composition patterns with other AI coding workflow systems
 - RESEARCH.md: dated research notes informing agent design decisions
-- GLOSSARY.md: standardized vocabulary across tiers (substitution test,
-  three-label test, flip point, have-not, paper artifact, theater, AI-slop)

package/routing/recipes/release-maintenance.yaml

@@ -23,5 +23,7 @@ sequences:
         why: "Verify README, release notes, badges, and public docs against code"
       - command: "/god-version"
         why: "Confirm installed runtime and package version visibility"
+      - command: "/god-automation-setup"
+        why: "Use strict-release-readiness for any background release check; do not publish without explicit user approval"
 
 default-sequence: default

package/schema/events.v1.json

@@ -48,6 +48,15 @@
         "tier.skip",
         "state.repair",
         "state.rollback",
+        "local-helper.run",
+        "local-helper.complete",
+        "dashboard.render",
+        "host-capabilities.detect",
+        "dogfood.run",
+        "source-system.import",
+        "source-system.sync-back",
+        "repo-doc-sync.detect",
+        "repo-surface-sync.detect",
         "extension.install",
         "extension.activate",
         "error",

package/schema/intent.v1.yaml.json

@@ -108,7 +108,11 @@
       "properties": {
         "yolo": { "type": "boolean", "default": false },
         "conservative": { "type": "boolean", "default": false },
-        "trash-retention-days": { "type": "integer", "minimum": 0, "default": 30 }
+        "trash-retention-days": { "type": "integer", "minimum": 0, "default": 30 },
+        "repo-doc-sync": { "type": "boolean", "default": true },
+        "repo-surface-sync": { "type": "boolean", "default": true },
+        "source-sync-back": { "type": "boolean", "default": true },
+        "dashboard-brief": { "type": "boolean", "default": true }
       }
     }
   },

package/schema/recipe.v1.json

@@ -27,7 +27,8 @@
           "enum": [
             "starting", "planning", "building", "shipping",
             "production", "maintaining", "recovering", "collaborating",
-            "knowledge", "feature-addition", "configuration", "meta"
+            "knowledge", "feature-addition", "configuration", "meta",
+            "migration", "release", "extension", "suite", "dogfood"
           ]
         },
         "description": { "type": "string" }

package/schema/routing.v1.json

@@ -65,6 +65,26 @@
           "type": "array",
           "items": { "type": "string" },
           "description": "Agents spawned by primary agent (e.g., reviewers)"
+        },
+        "local-helpers": {
+          "type": "array",
+          "description": "Visible local runtime helpers this command may run without spawning a specialist agent.",
+          "items": {
+            "type": "string",
+            "enum": [
+              "checkpoint-sync",
+              "feature-awareness",
+              "host-capabilities",
+              "repo-doc-sync",
+              "repo-surface-sync",
+              "route-quality-sync",
+              "recipe-coverage-sync",
+              "release-surface-sync",
+              "dogfood-runner",
+              "source-sync-back",
+              "pillars-sync-plan"
+            ]
+          }
         }
       }
     },

package/schema/state.v1.json

@@ -157,6 +157,57 @@
       },
       "additionalProperties": false
     },
+    "host-capabilities": {
+      "type": "object",
+      "description": "Most recent host guarantee report used by dashboard and release readiness surfaces.",
+      "properties": {
+        "host": { "type": "string" },
+        "level": {
+          "type": "string",
+          "enum": ["full", "degraded", "unknown"]
+        },
+        "gaps": {
+          "type": "array",
+          "items": { "type": "string" }
+        },
+        "checked-at": {
+          "type": "string",
+          "format": "date-time"
+        }
+      },
+      "additionalProperties": true
+    },
+    "dashboard": {
+      "type": "object",
+      "description": "Optional cached dashboard summary. Runtime recomputes from disk when present data is stale.",
+      "properties": {
+        "last-rendered-at": { "type": "string", "format": "date-time" },
+        "action-brief": {
+          "type": "object",
+          "properties": {
+            "next": { "type": "string" },
+            "why": { "type": "string" },
+            "readiness": { "type": "string", "enum": ["ready", "needs attention"] },
+            "attention": { "type": "array", "items": { "type": "string" } },
+            "host-guarantees": { "type": "string" }
+          },
+          "additionalProperties": false
+        }
+      },
+      "additionalProperties": false
+    },
+    "dogfood": {
+      "type": "object",
+      "description": "Most recent deterministic messy-repo fixture run summary.",
+      "properties": {
+        "status": { "type": "string", "enum": ["not-run", "pass", "fail"] },
+        "total": { "type": "integer", "minimum": 0 },
+        "passed": { "type": "integer", "minimum": 0 },
+        "failed": { "type": "integer", "minimum": 0 },
+        "last-run-at": { "type": "string", "format": "date-time" }
+      },
+      "additionalProperties": false
+    },
     "yolo-decisions": {
       "type": "array",
       "description": "Auto-decisions made under --yolo. Mirrored to YOLO-DECISIONS.md.",

package/schema/workflow.v1.json

@@ -27,7 +27,7 @@
       "type": "array",
       "items": {
         "type": "string",
-        "pattern": "^/god-[a-z-]+$"
+        "pattern": "^/god-[a-z-]+(\\s.*)?$"
       }
     },
     "jobs": {
@@ -86,10 +86,39 @@
             "additionalProperties": true
           }
         },
+        "local-helpers": {
+          "type": "array",
+          "description": "Visible local runtime helpers that run in this job without specialist-agent judgment.",
+          "items": {
+            "type": "string",
+            "enum": [
+              "checkpoint-sync",
+              "feature-awareness",
+              "host-capabilities",
+              "repo-doc-sync",
+              "repo-surface-sync",
+              "route-quality-sync",
+              "recipe-coverage-sync",
+              "release-surface-sync",
+              "dogfood-runner",
+              "source-sync-back",
+              "pillars-sync-plan"
+            ]
+          }
+        },
         "per": { "type": "string", "enum": ["slice", "wave"] },
         "parallel-by": { "type": "string", "enum": ["slice", "wave"] },
         "on-pass": { "type": "string" },
-        "skip-when": { "type": "string" }
+        "on-fail": { "type": "string" },
+        "skip-when": { "type": "string" },
+        "verification": {
+          "type": "object",
+          "additionalProperties": true
+        },
+        "closure": {
+          "type": "object",
+          "additionalProperties": true
+        }
       }
     }
   }

package/skills/god-automation-setup.md

@@ -83,8 +83,13 @@ for that exact write-capable automation:
 - `stale-checkpoint`: inspect checkpoint freshness and suggest `/god-sync` or `/god-resume-work`
 - `review-queue`: report unresolved review items without clearing them
 - `weekly-hygiene`: report docs, dependencies, checkpoint, reviews, and hygiene signals
+- `strict-release-readiness`: fail-closed release readiness across root docs, docs, agents, skills, routing, workflows, schema, templates, references, hooks, lib, scripts, tests, fixtures, GitHub workflows, package metadata, git tag state, GitHub release state, npm latest, and local install state
 - `release-readiness`: report release readiness without publishing
 
+Use `strict-release-readiness` for any background release automation. Use
+`release-readiness` only for quick manual checks where the user explicitly
+accepts a narrower report.
+
 ## Provider Guidance
 
 - Codex App: use native Codex automations when the host exposes them.

package/skills/god-mode.md

@@ -286,10 +286,13 @@ Default. Skip the hygiene pass. Use when iterating quickly.
 ## Mandatory final sync
 
 Regardless of flags, `/god-mode` always runs `/god-sync` before declaring
-complete. This ensures all 14 artifact categories are in a consistent state:
+complete. This ensures all 14 core artifact categories and local sync surfaces
+are in a consistent state:
 
 - 10 Tier 0-3 artifacts validated (have-nots passing)
 - 4 capture artifacts noted as `not-yet-created` (graceful handling)
+- repo-doc, repo-surface, feature awareness, source sync-back, host capability,
+  checkpoint, Pillars, and context refresh statuses reported
 - SYNC-LOG.md updated with project-run completion entry
 - state.json reflects final tier statuses