godpowers 1.6.23 → 2.0.0

package/CHANGELOG.md

@@ -7,6 +7,80 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [2.0.0] - 2026-05-16
+
+Executable proof release.
+
+### Added
+- Added `npx godpowers quick-proof --project=.` as a read-only CLI helper that
+  renders a shipped fixture with real `.godpowers/state.json`, computed next
+  action, missing-artifact visibility, and current host guarantees.
+- Added `lib/quick-proof.js` and `fixtures/quick-proof/` so the first-user
+  proof loop is packaged, deterministic, and testable.
+- Added `docs/quick-proof.md`, `docs/proof-transcript.md`, and
+  `docs/adoption-canary.md` so onboarding, proof evidence, and real-world
+  canary work share one connected story.
+- Added `scripts/run-adoption-canary.js` to clone an external repository and
+  capture CLI-verifiable trust signals: quick proof, dashboard status, and next
+  route output.
+- Added `scripts/verify-published-install.js` to verify the published npm
+  artifact after release, including quick proof, dashboard status, Claude
+  install, and Codex metadata install.
+
+### Changed
+- README now leads with executable proof, starter command paths, runtime
+  expectations, and the accountable AI development thesis.
+- Release checklist now includes published install verification through the
+  registry artifact instead of only the local checkout.
+- Package contents checks now require `lib/quick-proof.js` and the shipped
+  quick-proof fixture state.
+- Context and quality pillars now treat quick proof, adoption canary, and
+  published-install verification as durable repository truth.
+
+### Guardrails
+- `npm run test:quick-proof` verifies README links, quick proof docs,
+  transcript evidence, release checklist wiring, adoption canary wiring, local
+  links, and forbidden character rules.
+- `npm run release:check` includes the quick-proof test and package payload
+  verification.
+- The adoption canary harness does not replace host slash-command execution.
+  It captures CLI-verifiable signals and clearly leaves `/god-preflight`,
+  `/god-audit`, and `/god-reconstruct` to the AI coding host.
+
+## [1.6.24] - 2026-05-16
+
+Strict background release readiness.
+
+### Added
+- Added the `strict-release-readiness` automation template so delegated or
+  scheduled release checks fail closed when any required release surface is
+  unchecked, stale, missing, untested, or inconsistent with the intended
+  version.
+- Added a required release-surface manifest for root docs, docs, agents,
+  skills, routing, workflows, schema, templates, references, hooks, lib,
+  scripts, tests, fixtures, GitHub workflows, package metadata, npm latest,
+  git tag state, GitHub release state, CI, publish workflow, and local install
+  state.
+
+### Changed
+- `/god-automation-setup` now recommends `strict-release-readiness` for
+  background release checks and keeps the narrower `release-readiness`
+  template reserved for quick manual checks.
+- The release maintenance recipe now routes background-release setup through
+  `/god-automation-setup` with an explicit no-publish guardrail.
+- Auto-invoke visibility docs now classify strict release readiness as a
+  read-only, fail-closed Level 2 automation candidate.
+- The release checklist now names every folder and published surface that must
+  be checked before packaging, tagging, pushing, releasing, or publishing.
+
+### Guardrails
+- Added behavioral coverage that verifies the strict release readiness
+  template exists, is fail-closed, refuses file mutation, and names every
+  required release surface.
+- The strict readiness template may report blockers and exact next commands,
+  but it must not modify files, stage, commit, tag, push, create a GitHub
+  release, publish to npm, delete files, clear caches, or change installs.
+
 ## [1.6.23] - 2026-05-16
 
 Full repository audit, release gate hardening, and documentation repair.

package/README.md

@@ -2,7 +2,7 @@
 
 [![CI](https://github.com/aihxp/godpowers/actions/workflows/ci.yml/badge.svg)](https://github.com/aihxp/godpowers/actions/workflows/ci.yml)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
-[![Version](https://img.shields.io/badge/version-1.6.23-blue)](CHANGELOG.md)
+[![Version](https://img.shields.io/badge/version-2.0.0-blue)](CHANGELOG.md)
 [![npm](https://img.shields.io/npm/v/godpowers.svg)](https://www.npmjs.com/package/godpowers)
 
 **Ship fast. Ship right. Ship everything. Ship accountably.**
@@ -12,10 +12,26 @@ idea to hardened production. It runs as **slash commands inside your AI coding
 tool** (Claude Code, Codex, Cursor, etc.) that orchestrate **specialist agents**
 in fresh contexts to do the work.
 
-Version 1.6.23 hardens the release surface after a full file-by-file audit.
-Godpowers now keeps repo documentation, release gates, feature awareness,
-host guarantees, source-system sync-back, and repository surface checks aligned
-from reconciliation through final sync.
+Want the short proof first? Start with [Quick Proof](docs/quick-proof.md) to
+run `npx godpowers quick-proof --project=.`, see transcript excerpts, pick a
+starter command set, and understand runtime expectations before reading the
+full reference.
+
+Godpowers makes AI coding accountable: every serious run should leave disk
+state, artifacts, validation gates, host guarantees, and a next action. Code is
+only one output. The project memory and proof trail matter too.
+
+Version 2.0.0 makes the proof loop executable. `npx godpowers quick-proof
+--project=.` now renders a shipped fixture with real `.godpowers/state.json`,
+computed next action, missing-artifact visibility, and host guarantees. The
+release also ships a proof transcript, adoption canary harness, published npm
+install verifier, and package checks that require the proof fixture to ship.
+
+Strict release readiness remains fail-closed. Godpowers requires delegated
+release checks to cover root docs, docs, agents, skills, routing, workflows,
+schema, templates, references, hooks, lib, scripts, tests, fixtures, GitHub
+workflows, package metadata, npm, GitHub release, CI, publish workflow, and
+local install state before a human-approved release executor can run.
 
 The dashboard now starts with an action brief and a host guarantee line: the
 next command, why it is recommended, whether the project is ready, the first
@@ -38,6 +54,17 @@ It fuses four disciplines into one unified workflow:
 - **Team intelligence** - scale-adaptive complexity, specialized agent personas
   (PM, Architect, Executor, Reviewer, Harden Auditor, etc.).
 
+## What Godpowers Proves
+
+Godpowers is designed to prove more than "the model wrote files." A useful run
+should prove:
+
+- The current state is on disk, not trapped in chat memory.
+- The next action is derived from repository state.
+- Planning artifacts, code changes, reviews, and launch checks can be inspected.
+- Host guarantees are explicit, including degraded or simulated agent behavior.
+- Release confidence covers tests, package contents, install surfaces, and docs.
+
 ## Install
 
 ```bash
@@ -62,6 +89,18 @@ mechanism against the installed `agents/god-*.md` files. If a host cannot
 provide a true fresh-context spawn, Godpowers must report that limitation
 instead of pretending a background agent ran.
 
+### Runtime Expectations
+
+| Runtime class | What to expect |
+|---|---|
+| Claude Code | Strong reference path when native agent spawning is available. |
+| Codex | Strong installed support through `agents/*.toml` metadata backed by the same Markdown agent contracts. |
+| Other install targets | Skills and agent contracts install, while host-native spawning depends on the tool. |
+| Degraded hosts | Godpowers must report local-only or simulated agent behavior instead of hiding the limitation. |
+
+See [Host capabilities](docs/host-capabilities.md) for the detailed guarantee
+model.
+
 ## Usage
 
 Open your AI coding tool in any project directory and type:
@@ -114,6 +153,21 @@ This reads `.godpowers/PROGRESS.md`, scans disk, reconciles any drift, and
 suggests the next logical command with a compact action brief. The SessionStart
 hook does the same thing when you open a new session in a Godpowers project.
 
+### Start With A Path
+
+If the full command surface feels large, begin with one of these paths and only
+learn the next command when Godpowers recommends it.
+
+| Goal | Starter path |
+|---|---|
+| Start a product | `/god-init`, `/god-prd`, `/god-design`, `/god-arch`, `/god-roadmap`, `/god-stack`, `/god-build` |
+| Add a feature | `/god-feature`, `/god-reconcile`, `/god-build`, `/god-review`, `/god-sync` |
+| Fix production | `/god-hotfix`, `/god-debug`, `/god-harden`, `/god-postmortem` |
+| Audit an existing repo | `/god-preflight`, `/god-audit`, `/god-archaeology`, `/god-tech-debt` |
+| Ship a release | `/god-status`, `/god-harden`, `/god-launch`, `npm run release:check` |
+| Maintain project health | `/god-hygiene`, `/god-update-deps`, `/god-docs`, `/god-check-todos` |
+| Extend Godpowers | `/god-extension-add`, `/god-extension-list`, `npx godpowers extension-scaffold --name=@godpowers/my-pack --output=.` |
+
 The same status engine is available from the installer CLI for humans, CI,
 Codex, Claude, Cursor, Gemini, OpenCode, Windsurf, Antigravity, and any host
 runtime that can execute Node:
@@ -123,6 +177,7 @@ npx godpowers status --project=.
 npx godpowers next --project=.
 npx godpowers status --project=. --brief
 npx godpowers status --project=. --json
+npx godpowers quick-proof --project=.
 npx godpowers dogfood
 npx godpowers extension-scaffold --name=@godpowers/my-pack --output=.
 ```
@@ -377,9 +432,11 @@ Pi. T3 Code inherits from the underlying agent (Codex / Claude / OpenCode).
 ## Full reference
 
 - [Getting Started](docs/getting-started.md)
+- [Quick Proof](docs/quick-proof.md)
 - [Concepts](docs/concepts.md)
 - [Command reference (all 110 skills + 40 agents)](docs/reference.md)
 - [Feature awareness](docs/feature-awareness.md)
+- [Adoption Canary](docs/adoption-canary.md)
 - [Repository documentation sync](docs/repo-doc-sync.md)
 - [Repository surface sync](docs/repo-surface-sync.md)
 - [Roadmap](docs/ROADMAP.md)

package/RELEASE.md

@@ -1,11 +1,12 @@
-# Godpowers 1.6.23 Release
+# Godpowers 2.0.0 Release
 
 Date: 2026-05-16
 
-Godpowers 1.6.23 hardens the repository after a full file-by-file audit. It
-aligns release gates, documentation sync, repository surface sync, feature
-awareness, source-system sync-back, host guarantees, dashboard closeouts, and
-package publishing into one verified release surface.
+Godpowers 2.0.0 is the executable proof release. It turns the first-user trust
+loop from documentation into a packaged command: `npx godpowers quick-proof
+--project=.`. The command renders a shipped fixture with real
+`.godpowers/state.json`, computed next action, missing-artifact visibility, and
+host guarantees from the caller's environment.
 
 ## What is stable
 
@@ -19,18 +20,14 @@ package publishing into one verified release surface.
 - Shared runtime bundle at `<runtime>/godpowers-runtime`
 - Native Pillars project context through `AGENTS.md` and `agents/*.md`
 - `.godpowers/` workflow state and artifact layout
-- Safe-sync routing before deploy, observe, harden, launch, or god-mode work
-- Critical harden finding gate before launch
+- Dashboard action briefs for next-step compression
+- Dashboard host guarantees for full, degraded, and unknown runtime capability
+- `godpowers status --project .` and `godpowers next --project .`
+- `godpowers quick-proof --project .`
 - Planning-system migration for GSD, BMAD, and Superpowers
-- Managed sync-back companion files for imported source systems
-- Feature awareness for existing Godpowers projects
 - Repository documentation sync checks
 - Repository surface sync checks
 - Route quality, recipe coverage, and release surface sync checks
-- Dashboard action briefs for next-step compression
-- Dashboard host guarantees for full, degraded, and unknown runtime capability
-- Agent-spawn trace event guardrails
-- Mode D suite readiness checks
 - Messy-repo dogfood scenarios
 - Extension authoring scaffold helper
 - Mode D suite release dry-run planner
@@ -38,56 +35,43 @@ package publishing into one verified release surface.
 
 ## What is new
 
-- Added `.planning/2026-05-16-surface-sync-status.md` to record the current
-  `.github/workflows`, `.planning`, and `agents` sync status without rewriting
-  historical planning evidence.
-- Expanded `god-reconciler` so feature reconciliation includes repository
-  documentation, repository surface, runtime feature awareness, source-system
-  sync-back, and host capability checks.
-- Expanded `god-updater` so closeout reports repo-doc sync, repo-surface sync,
-  feature awareness, source-system sync-back, host capability, dashboard
-  refresh, checkpoint sync, Pillars sync, and context refresh.
-- Updated workflow release jobs so root and first-party pack publishing run
-  the complete release gate first.
-- Updated `prepublishOnly` so local npm publish attempts also run the complete
-  release gate.
+- Added `lib/quick-proof.js` and the packaged `fixtures/quick-proof/` project.
+- Added the `quick-proof` CLI command as the first executable proof path.
+- Added `docs/quick-proof.md` to make the first 10 minutes concrete.
+- Added `docs/proof-transcript.md` with captured command output.
+- Added `docs/adoption-canary.md` with pass/fail criteria and feedback routing.
+- Added `scripts/run-adoption-canary.js` to clone an external repo and capture
+  quick proof, dashboard status, and next-route output.
+- Added `scripts/verify-published-install.js` to verify the npm registry
+  artifact after publish.
+- Updated README, getting started, reference, release checklist, and Pillars
+  context so executable proof is part of the product surface.
 
-## Repairs
+## Guardrails
 
-- Repaired stale current-version claims in README, architecture, roadmap,
-  reference docs, `/god-version`, and agent context.
-- Repaired stale `/god-reconcile` docs so the command and specialist agent
-  describe the same expanded sync surfaces.
-- Repaired final sync docs so `/god-mode`, `god-orchestrator`, and agent specs
-  all describe core artifacts plus local runtime and repository sync surfaces.
-- Removed literal forbidden dash and emoji characters from primary source files
-  while keeping validator tests intact through Unicode escape sequences.
-- Repaired release documentation drift around package contents, route quality,
-  recipe coverage, release-surface checks, dogfood, host guarantees, extension
-  authoring, and Mode D suite release dry-runs.
+- Quick proof is read-only and deterministic.
+- Quick proof reports the user's current host guarantees separately from the
+  shipped fixture state.
+- Package contents checks require the quick-proof module and fixture state.
+- Published install verification checks quick proof, status, next, Claude
+  install, and Codex metadata install against the registry artifact.
+- The adoption canary harness captures CLI-verifiable signals only. Host slash
+  commands such as `/god-preflight`, `/god-audit`, and `/god-reconstruct` still
+  require an AI coding host.
 
 ## Validation
 
 Release validation includes:
 
-- source audit over 639 tracked plus untracked source files
-- `node scripts/validate-skills.js`
-- `bash scripts/smoke.sh`
-- `node scripts/test-agent-validator.js`
-- `node scripts/test-artifact-linter.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-feature-awareness.js`
-- `node scripts/test-host-capabilities.js`
-- `node scripts/test-dogfood-runner.js`
-- `node scripts/test-extension-authoring.js`
-- `node scripts/test-mode-d.js`
-- `node scripts/test-extensions-publish.js`
-- `node scripts/test-install-smoke.js`
-- `npm audit --omit=dev`
-- `git diff --check`
+- `npm run test:quick-proof`
+- `node scripts/run-adoption-canary.js <repo> --output=<report>`
 - `npm run release:check`
+- `npm pack --json`
+- local uninstall of previous runtime installs
+- local reinstall from the generated tarball
+- npm publish with provenance when available
+- `node scripts/verify-published-install.js godpowers@latest`
+- GitHub release creation for `v2.0.0`
 
-The `v1.6.23` tag should point to the release commit that matches the npm
-`godpowers@1.6.23` package.
+The `v2.0.0` tag should point to the release commit that matches the npm
+`godpowers@2.0.0` package.

package/bin/install.js

@@ -322,6 +322,7 @@ function parseArgs(argv) {
     switch (arg) {
       case 'status':
       case 'next':
+      case 'quick-proof':
       case 'automation-status':
       case 'automation-setup':
       case 'dogfood':
@@ -594,15 +595,16 @@ function showHelp() {
   log('Commands:');
   log('  status               Show the Godpowers Dashboard for a project');
   log('  next                 Show the dashboard and recommended next command');
+  log('  quick-proof          Show a runnable proof from the shipped fixture');
   log('  automation-status    Show host automation provider support');
   log('  automation-setup     Show an opt-in automation setup plan');
   log('  dogfood              Run built-in messy-repo dogfood scenarios');
   log('  extension-scaffold   Create a publishable extension pack skeleton');
   log('');
   log('Options:');
-  log('  --project=<path>     Project root for status, next, or automation commands');
-  log('  --json               Emit JSON for status, next, or automation commands');
-  log('  --brief              Render a compact dashboard for status or next');
+  log('  --project=<path>     Project root for status, next, proof, or automation commands');
+  log('  --json               Emit JSON for status, next, proof, or automation commands');
+  log('  --brief              Render compact output for status, next, or proof');
   log('  --name=<scope/name>  Extension package name for extension-scaffold');
   log('  --output=<path>      Extension output root for extension-scaffold');
   log('  --skill=<name>       Extension skill name for extension-scaffold');
@@ -632,6 +634,7 @@ function showHelp() {
   log('Examples:');
   log('  npx godpowers status --project=.');
   log('  npx godpowers next --project=.');
+  log('  npx godpowers quick-proof --project=.');
   log('  npx godpowers automation-status --project=.');
   log('  npx godpowers automation-setup --project=.');
   log('  npx godpowers dogfood');
@@ -681,6 +684,16 @@ function runDogfoodCommand(opts) {
   if (result.status !== 'pass') process.exit(1);
 }
 
+function runQuickProofCommand(opts) {
+  const quickProof = require('../lib/quick-proof');
+  const result = quickProof.compute(opts.project);
+  if (opts.json) {
+    console.log(JSON.stringify(result, null, 2));
+  } else {
+    console.log(quickProof.render(result, { brief: opts.brief }));
+  }
+}
+
 function runExtensionScaffoldCommand(opts) {
   const authoring = require('../lib/extension-authoring');
   if (!opts.extensionName) {
@@ -726,6 +739,11 @@ function main() {
     return;
   }
 
+  if (opts.command === 'quick-proof') {
+    runQuickProofCommand(opts);
+    return;
+  }
+
   if (opts.command === 'automation-status' || opts.command === 'automation-setup') {
     runAutomationCommand(opts);
     return;

package/extensions/data-pack/manifest.yaml

@@ -9,7 +9,7 @@ metadata:
     without SLOs, ETL without idempotency.
 
 engines:
-  godpowers: ">=0.14.0 <2.0.0"
+  godpowers: ">=2.0.0 <3.0.0"
 
 provides:
   agents:

package/extensions/data-pack/package.json

@@ -37,6 +37,6 @@
     "README.md"
   ],
   "peerDependencies": {
-    "godpowers": ">=0.14.0 <2.0.0"
+    "godpowers": ">=2.0.0 <3.0.0"
   }
 }

package/extensions/launch-pack/manifest.yaml

@@ -9,7 +9,7 @@ metadata:
     god-launch-strategist with channel expertise.
 
 engines:
-  godpowers: ">=0.14.0 <2.0.0"
+  godpowers: ">=2.0.0 <3.0.0"
 
 provides:
   agents:

package/extensions/launch-pack/package.json

@@ -36,6 +36,6 @@
     "README.md"
   ],
   "peerDependencies": {
-    "godpowers": ">=0.14.0 <2.0.0"
+    "godpowers": ">=2.0.0 <3.0.0"
   }
 }

package/extensions/security-pack/manifest.yaml

@@ -8,7 +8,7 @@ metadata:
     Layers on top of god-harden-auditor with regulation-specific checks.
 
 engines:
-  godpowers: ">=0.14.0 <2.0.0"
+  godpowers: ">=2.0.0 <3.0.0"
 
 provides:
   agents:

package/extensions/security-pack/package.json

@@ -37,6 +37,6 @@
     "README.md"
   ],
   "peerDependencies": {
-    "godpowers": ">=0.14.0 <2.0.0"
+    "godpowers": ">=2.0.0 <3.0.0"
   }
 }

package/fixtures/quick-proof/manifest.json

@@ -0,0 +1,19 @@
+{
+  "name": "quick-proof",
+  "description": "Deterministic fixture for the Godpowers quick proof CLI command.",
+  "project": "quick-proof-saas",
+  "proves": [
+    "state on disk",
+    "missing artifacts",
+    "next command",
+    "host guarantees"
+  ],
+  "expected": {
+    "state": "in progress",
+    "next": "/god-prd",
+    "missing": [
+      ".godpowers/prd/PRD.md",
+      ".godpowers/roadmap/ROADMAP.md"
+    ]
+  }
+}

package/fixtures/quick-proof/project/.godpowers/prep/INITIAL-FINDINGS.md

@@ -0,0 +1,5 @@
+# Initial Findings
+
+- [DECISION] This quick-proof fixture represents a project that has been initialized but does not have a PRD yet.
+- [DECISION] The expected next command is `/god-prd`.
+- [HYPOTHESIS] A first-time user can understand the Godpowers proof loop by seeing state, missing artifacts, host guarantees, and a next action together.

package/fixtures/quick-proof/project/.godpowers/state.json

@@ -0,0 +1,69 @@
+{
+  "$schema": "https://godpowers.dev/schema/state.v1.json",
+  "version": "1.0.0",
+  "project": {
+    "name": "quick-proof-saas",
+    "started": "2026-05-16T00:00:00.000Z"
+  },
+  "active-workstream": "main",
+  "tiers": {
+    "tier-0": {
+      "orchestration": {
+        "status": "done",
+        "updated": "2026-05-16T00:00:00.000Z"
+      }
+    },
+    "tier-1": {
+      "prd": {
+        "status": "pending"
+      },
+      "arch": {
+        "status": "pending"
+      },
+      "roadmap": {
+        "status": "pending"
+      },
+      "stack": {
+        "status": "pending"
+      },
+      "design": {
+        "status": "not-required",
+        "reason": "Fixture is focused on state and routing proof."
+      },
+      "product": {
+        "status": "not-required",
+        "reason": "Fixture is focused on state and routing proof."
+      }
+    },
+    "tier-2": {
+      "repo": {
+        "status": "pending"
+      },
+      "build": {
+        "status": "pending"
+      }
+    },
+    "tier-3": {
+      "deploy": {
+        "status": "pending"
+      },
+      "observe": {
+        "status": "pending"
+      },
+      "launch": {
+        "status": "pending"
+      },
+      "harden": {
+        "status": "pending"
+      }
+    }
+  },
+  "lifecycle-phase": "in-arc",
+  "linkage": {
+    "coverage-pct": 0,
+    "orphan-count": 0,
+    "drift-count": 0,
+    "review-required-items": 0
+  },
+  "yolo-decisions": []
+}

package/fixtures/quick-proof/project/README.md

@@ -0,0 +1,5 @@
+# Quick Proof Fixture
+
+This fixture is intentionally small. It has Godpowers state on disk, but it
+does not include completed PRD or roadmap artifacts. The expected next command
+is `/god-prd`.

package/fixtures/quick-proof/project/package.json

@@ -0,0 +1,6 @@
+{
+  "name": "quick-proof-saas",
+  "version": "0.0.0",
+  "private": true,
+  "description": "Tiny project fixture used by godpowers quick-proof."
+}

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/feature-awareness.js

@@ -83,6 +83,12 @@ const FEATURES = [
     commands: ['/god-status', '/god-next'],
     description: 'Report full, degraded, or unknown host guarantees in dashboard output.'
   },
+  {
+    id: 'quick-proof',
+    since: '2.0.0',
+    commands: ['godpowers quick-proof'],
+    description: 'Render a shipped proof fixture with computed next action and host guarantees.'
+  },
   {
     id: 'extension-authoring',
     since: '1.6.22',

package/lib/quick-proof.js

@@ -0,0 +1,153 @@
+/**
+ * Quick proof runner.
+ *
+ * Renders a deterministic proof from a shipped fixture while detecting host
+ * guarantees from the caller's actual project and environment.
+ */
+
+const fs = require('fs');
+const path = require('path');
+
+const dashboard = require('./dashboard');
+const hostCapabilities = require('./host-capabilities');
+
+const FIXTURE_ROOT = path.join(__dirname, '..', 'fixtures', 'quick-proof', 'project');
+const MANIFEST_PATH = path.join(__dirname, '..', 'fixtures', 'quick-proof', 'manifest.json');
+
+function readJson(filePath) {
+  return JSON.parse(fs.readFileSync(filePath, 'utf8'));
+}
+
+function relFixturePath(absPath) {
+  return path.relative(path.join(__dirname, '..'), absPath).split(path.sep).join('/');
+}
+
+function compute(projectRoot = process.cwd(), opts = {}) {
+  const fixtureRoot = opts.fixtureRoot || FIXTURE_ROOT;
+  const manifestPath = opts.manifestPath || MANIFEST_PATH;
+  const manifest = readJson(manifestPath);
+  const fixtureDashboard = dashboard.compute(fixtureRoot, { git: false });
+  const host = opts.hostReport || hostCapabilities.detect(projectRoot, opts.hostOptions || {});
+  const focusedActionBrief = {
+    recommended: fixtureDashboard.next && fixtureDashboard.next.command
+      ? fixtureDashboard.next.command
+      : 'describe the next intent',
+    reason: fixtureDashboard.next && fixtureDashboard.next.reason
+      ? fixtureDashboard.next.reason
+      : 'No route was computed.',
+    confidence: host.level === 'unknown' ? 'needs attention' : 'ready',
+    blockers: host.gaps && host.gaps.length > 0 ? [`Host: ${host.gaps[0]}`] : [],
+    overflow: host.gaps && host.gaps.length > 1 ? host.gaps.length - 1 : 0
+  };
+
+  const proof = {
+    source: 'quick-proof fixture',
+    manifest,
+    projectRoot: path.resolve(projectRoot),
+    fixtureRoot,
+    fixturePath: relFixturePath(fixtureRoot),
+    statePath: relFixturePath(path.join(fixtureRoot, '.godpowers', 'state.json')),
+    dashboard: {
+      state: fixtureDashboard.state,
+      progress: fixtureDashboard.progress,
+      planning: fixtureDashboard.planning,
+      next: fixtureDashboard.next,
+      actionBrief: focusedActionBrief
+    },
+    host,
+    commands: [
+      `npx godpowers quick-proof --project=${projectRoot}`,
+      `npx godpowers status --project=${fixtureRoot} --brief`,
+      `npx godpowers next --project=${fixtureRoot} --brief`,
+      `npx godpowers status --project=${projectRoot} --brief`
+    ],
+    evidence: [
+      {
+        label: 'State on disk',
+        value: relFixturePath(path.join(fixtureRoot, '.godpowers', 'state.json'))
+      },
+      {
+        label: 'Next action',
+        value: fixtureDashboard.next && fixtureDashboard.next.command
+          ? fixtureDashboard.next.command
+          : 'describe the next intent'
+      },
+      {
+        label: 'Missing artifact',
+        value: fixtureDashboard.planning.prd.status === 'missing'
+          ? '.godpowers/prd/PRD.md'
+          : 'none'
+      },
+      {
+        label: 'Host guarantees',
+        value: hostCapabilities.summary(host)
+      }
+    ]
+  };
+
+  return proof;
+}
+
+function render(proof, opts = {}) {
+  const brief = proof.dashboard.actionBrief || {};
+  const next = proof.dashboard.next || {};
+  const progress = proof.dashboard.progress || {};
+  const planning = proof.dashboard.planning || {};
+
+  if (opts.brief) {
+    return [
+      'Godpowers Quick Proof',
+      '',
+      'Action brief:',
+      `  Next: ${brief.recommended || next.command || 'describe the next intent'}`,
+      `  Why: ${brief.reason || next.reason || 'No route was computed.'}`,
+      `  Readiness: ${brief.confidence || 'unknown'}`,
+      `  Host guarantees: ${hostCapabilities.summary(proof.host)}`,
+      '',
+      'Evidence:',
+      `  State on disk: ${proof.statePath}`,
+      `  Fixture: ${proof.fixturePath}`,
+      `  PRD: ${planning.prd ? planning.prd.status : 'unknown'}`,
+      `  Roadmap: ${planning.roadmap ? planning.roadmap.status : 'unknown'}`
+    ].join('\n');
+  }
+
+  return [
+    'Godpowers Quick Proof',
+    '',
+    `Source: shipped fixture (${proof.fixturePath})`,
+    '',
+    'What this proves:',
+    '  1. Godpowers can read project state from disk.',
+    '  2. Godpowers can name missing artifacts instead of inventing completion.',
+    '  3. Godpowers can recommend the next command from state.',
+    '  4. Godpowers can report host guarantees separately from fixture state.',
+    '',
+    'Dashboard proof:',
+    `  State: ${proof.dashboard.state}`,
+    `  Progress: ${progress.percent || 0}% (${progress.completed || 0} of ${progress.total || 0} tracked steps complete)`,
+    `  PRD: ${planning.prd ? planning.prd.status : 'unknown'}`,
+    `  Roadmap: ${planning.roadmap ? planning.roadmap.status : 'unknown'}`,
+    `  Next: ${next.command || 'describe the next intent'}`,
+    `  Why: ${next.reason || 'No route was computed.'}`,
+    `  Host guarantees: ${hostCapabilities.summary(proof.host)}`,
+    '',
+    'Evidence:',
+    ...proof.evidence.map((item, index) => `  ${index + 1}. ${item.label}: ${item.value}`),
+    '',
+    'Try it on the fixture:',
+    `  npx godpowers status --project=${proof.fixtureRoot} --brief`,
+    `  npx godpowers next --project=${proof.fixtureRoot} --brief`,
+    '',
+    'Try it on your project:',
+    `  npx godpowers status --project=${proof.projectRoot} --brief`,
+    `  npx godpowers next --project=${proof.projectRoot} --brief`
+  ].join('\n');
+}
+
+module.exports = {
+  compute,
+  render,
+  FIXTURE_ROOT,
+  MANIFEST_PATH
+};

package/package.json

@@ -1,15 +1,18 @@
 {
   "name": "godpowers",
-  "version": "1.6.23",
+  "version": "2.0.0",
   "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",
+    "test": "node scripts/validate-skills.js && node scripts/test-doc-surface-counts.js && node scripts/test-quick-proof.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 run release:check",
     "validate-skills": "node scripts/validate-skills.js",
     "test:surface": "node scripts/test-doc-surface-counts.js",
+    "test:quick-proof": "node scripts/test-quick-proof.js",
+    "canary:adoption": "node scripts/run-adoption-canary.js",
+    "verify:published-install": "node scripts/verify-published-install.js",
     "smoke": "bash scripts/smoke.sh",
     "test:runtime": "node scripts/test-runtime.js",
     "test:router": "node scripts/test-router.js",

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/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-extension-info.md

@@ -31,7 +31,7 @@ Description:
   specific checks.
 
 Engines:
-  godpowers: >=0.14.0 <2.0.0  (compatible with running v1.0.0? YES)
+  godpowers: >=2.0.0 <3.0.0  (compatible with running v2.0.0? YES)
 
 Provides:
   Agents (3):

package/skills/god-test-extension.md

@@ -49,7 +49,7 @@ Manifest: ./extensions/security-pack/manifest.yaml  [OK]
 apiVersion: godpowers/v1                            [OK]
 metadata.name: @godpowers/security-pack             [OK]
 metadata.version: 1.0.0                             [OK]
-engines.godpowers: >=0.14.0 <2.0.0                  [OK]
+engines.godpowers: >=2.0.0 <3.0.0                  [OK]
 
 Provided surface:
   agents/god-soc2-auditor.md   [OK]

package/skills/god-version.md

@@ -14,7 +14,7 @@ Print version and a short capability summary.
 ## Output
 
 ```
-Godpowers v1.6.23
+Godpowers v2.0.0
 Install: /Users/.../.claude/  (matches package.json)
 Surface: 110 skills, 40 agents, 13 workflows, 40 recipes
 Schema: intent.v1, state.v1, events.v1, workflow.v1, routing.v1, recipe.v1