Godpowers 3.14.0

Godpowers 3.14.0 Release

Status: Published
Date: 2026-06-17

[DECISION] Godpowers 3.14.0 is a UX-audit remediation release that drives the Godpowers UX audit (uxaudit.md, 11 weighted experience lenses) to zero: all 20 findings across usability, content, information architecture, interaction, process, journeys, and trust.
[DECISION] The changes are backward compatible and add no new commands. They tighten the install and dashboard surfaces, broaden the free-text router, restructure --help, add a docs index, and rewrite the front-door documentation. This is a minor bump because it adds backward-compatible user-facing functionality.
[DECISION] No new skill, agent, workflow, or recipe surface is added or removed. Surface counts are unchanged: 120 slash commands, 40 specialist agents, 13 workflows, 44 recipes. The lib module count is unchanged at 91.

What's in this release

• [DECISION] Install and surface validation (USE-001, USE-002, USE-003): a typo'd bare subcommand errors instead of silently starting a global install; an unknown --profile is a clean one-line error before any filesystem write; surface --runtime=<bad> is rejected instead of planning an apply to a nonexistent runtime.
• [DECISION] Dashboard and report display honesty (USE-004, CNT-005, CNT-006, IXD-001): status --full shows Phase/Step: not initialized instead of Complete on an uninitialized project; the readiness headline reads no blockers instead of the overloaded ready; the empty report names the commands that populate the ledger; next no longer prints the recommended command a third time.
• [DECISION] Free-text router accuracy (IA-001, IA-002): broadened intent-keywords so common verbs match a topical recipe (fix a bug, ship it, deploy, release, check progress); classifyWorkSize returns null when no small-task signal is present instead of mis-sizing an unrelated intent as /god-quick.
• [DECISION] Process and journey honesty (PROC-001, JRN-002): can-close output, its docstring, and the orchestrator runbook now state that can-close is the advisory freshness check and npx godpowers gate is the enforced boundary; the dashboard progress line annotates skipped steps so a skipped-tier run no longer shows an inflated percent.
• [DECISION] Help and docs prioritization (CNT-004, IA-004): --help leads with a 6-item "Start here" group above two labelled advanced groups; a new docs/README.md indexes user-facing docs under "Start here" and separates internal/maintainer docs.
• [DECISION] Front-door content, vocabulary, and trust (CNT-001, CNT-002, CNT-003, IA-003, JRN-001, TRU-001, TRU-002): the README top fold leads with a runnable Quick start and an inline glossary, version archaeology moved to a CHANGELOG/RELEASE pointer; the worst command descriptions lead with the user-intent verb and the /god-reconcile vs /god-sync overlap is disambiguated; the README clarifies that plain /god-mode resumes from disk; SECURITY.md softens its SLA to best-effort; the runtime headline no longer implies 15-way parity.

Changes

• [DECISION] package.json, package-lock.json, and packages/mcp/package.json now publish the 3.14.0 version.
• [DECISION] No new runtime module (lib module count unchanged at 91). No public command/agent/workflow/recipe surface change.
• [DECISION] CHANGELOG, RELEASE notes, README, roadmap, reference, architecture, the architecture map, and agents/context.md now reflect 3.14.0. The SECURITY supported-version table now carries the 3.14.x row.

Validation

• [DECISION] npm test passed all command groups.
• [DECISION] npm run release:check passed coverage:lib above the 90 percent line floor and the 75 percent branch floor, and the per-file floor (>= 70 percent lines across the lib modules).
• [DECISION] npm run release:check passed npm audit --omit=dev with 0 vulnerabilities and git diff --check.
• [DECISION] npm run release:check passed public surface docs for version 3.14.0 with 120 skills, 40 agents, 13 workflows, and 44 recipes.
• [DECISION] npm run release:check passed root and @godpowers/mcp package contents.

Upgrade

• [DECISION] Use npm install -g godpowers@3.14.0 or npx godpowers@3.14.0.
• [DECISION] No migration is required. The changes are install-surface validation, dashboard/router honesty, and documentation improvements with no breaking surface change.

Notes

• [DECISION] The publish targets are npm godpowers@3.14.0, npm @godpowers/mcp@3.14.0, and GitHub release https://github.com/aihxp/godpowers/releases/tag/v3.14.0.
• [DECISION] Tagged v3.14.0 and published to npm with provenance via the tag-triggered GitHub publish workflow (.github/workflows/publish.yml): godpowers@3.14.0 and @godpowers/mcp@3.14.0 are live as the latest dist-tag.

Godpowers 3.13.2

Godpowers 3.13.2 Release

Status: Published
Date: 2026-06-17

[DECISION] Godpowers 3.13.2 is a maintenance release that drives a third self-audit (codeaudit.md, codeauditor-grade, nine weighted dimensions) to zero. It fixes one Medium finding and twelve Low findings across de-duplication, error handling, security hardening, the test gate, and documentation.
[DECISION] No new skill, agent, workflow, or recipe surface is added or removed. Surface counts are unchanged from 3.13.1: 120 slash commands, 40 specialist agents, 13 workflows, 44 recipes. The lib module count rises from 90 to 91 (lib/sync-check.js).
[DECISION] This release keeps core as the omitted installer profile, keeps --profile=full as the complete compatibility surface, and keeps the full 3.1.0-3.13.1 surface.

What's in this release

• [DECISION] De-duplication (ARC-001, QUAL-001/002/003): the four *-sync modules share lib/sync-check.js (addCheck/makeAddCheck/listFiles) instead of copy-pasting them; removed dead helpers (two unused rel(), an unused sha); added sync-fs.readTextOrNull adopted by requirements.js, which now sources PRD/ROADMAP paths from artifact-map; fixed a boolean/string status wart in repo-surface-sync.
• [DECISION] Test gate (TEST-001, TEST-002): coverage:lib now emits a json-summary and scripts/check-per-file-coverage.js (in release:check) fails any lib module below 70% lines, excluding the two environment-bound browser drivers, so a single file can no longer rot while the aggregate stays green; the run()/appendLog() write path of the three sync siblings is now tested for the no-banned-dash invariant.
• [DECISION] Error handling (ERR-001): reverse-sync writes state before the ledger and surfaces a caught error as requirementsError instead of silently nulling it.
• [DECISION] Security hardening (SEC-001, SEC-002): the MCP requireRuntime rejects any module name that is not a plain lib basename; intent.cleanArrays caps recursion depth so a pathologically deep YAML cannot overflow the stack.
• [DECISION] Performance and docs (PERF-001/002, DOC-001, ARC-002): have-nots findPositions compiles its regex once per call; the bounded whole-ledger read is documented with an opt-in prune noted; the README's docs/* links are now absolute GitHub URLs (docs are deliberately excluded from the package); and pillars.js is delineated into its model and artifact-sync halves (a full split was deferred because the halves share public-API construction functions).

Changes

• [DECISION] package.json, package-lock.json, and packages/mcp/package.json now publish the 3.13.2 version.
• [DECISION] New runtime module lib/sync-check.js (lib module count 90 -> 91). No public command/agent/workflow/recipe surface change.
• [DECISION] CHANGELOG, RELEASE notes, README, roadmap, reference, architecture, and the architecture map now reflect 3.13.2. The SECURITY supported-version table already carries the 3.13.x row.

Validation

• [DECISION] npm test passed all command groups.
• [DECISION] npm run release:check passed coverage:lib above the 90 percent line floor and the 75 percent branch floor, and the new per-file floor (>= 70 percent lines across 88 lib modules).
• [DECISION] npm run release:check passed npm audit --omit=dev with 0 vulnerabilities and git diff --check.
• [DECISION] npm run release:check passed public surface docs for version 3.13.2 with 120 skills, 40 agents, 13 workflows, and 44 recipes.
• [DECISION] npm run release:check passed root and @godpowers/mcp package contents.

Upgrade

• [DECISION] Use npm install -g godpowers@3.13.2 or npx godpowers@3.13.2.
• [DECISION] No migration is required. The changes are internal de-duplication, error-visibility, security, test-gate, and documentation improvements with no surface change.

Notes

• [DECISION] The publish targets are npm godpowers@3.13.2, npm @godpowers/mcp@3.13.2, and GitHub release https://github.com/aihxp/godpowers/releases/tag/v3.13.2.
• [DECISION] Tagged v3.13.2 and published to npm with provenance via the tag-triggered GitHub publish workflow (.github/workflows/publish.yml): godpowers@3.13.2 and @godpowers/mcp@3.13.2 are live as the latest dist-tag.

Godpowers 3.13.1

Godpowers 3.13.1 Release

Status: Published
Date: 2026-06-16

[DECISION] Godpowers 3.13.1 is a maintenance release that drives a full self-audit (codeaudit.md, codeauditor-grade, nine weighted dimensions) to zero. It fixes one High finding plus the Medium and Low findings across runtime correctness, security hardening, the test gate, documentation, and de-duplication.
[DECISION] No new skill, agent, workflow, or recipe surface is added or removed. Surface counts are unchanged from 3.13.0: 120 slash commands, 40 specialist agents, 13 workflows, 44 recipes.
[DECISION] This release keeps core as the omitted installer profile, keeps --profile=full as the complete compatibility surface, and keeps the full 3.1.0-3.13.0 surface (fusion + codeauditor-grade audit + remediation loop + audited/documented greenfield arc).

What's in this release

• [DECISION] Runtime correctness: lib/evidence.js appendJsonlAtomic now appends with fs.appendFileSync (O_APPEND) instead of a read-modify-write, so concurrent verify/outcome check processes no longer lose ledger records and the append is no longer O(n) (ERR-001). A maxBuffer overflow is surfaced distinctly instead of as a plain failure (ERR-003).
• [DECISION] Security hardening: the pre-tool-use hook is reframed as a best-effort advisory typo guard and matches more destructive-command variants (SEC-001); outcome check announces a disk-sourced verifier before running it (SEC-002); the LEDGER-LOG.md command echo masks obvious secret shapes and SECURITY.md documents the ledger and Codex-sandbox trust boundaries (SEC-003, SEC-004); SECURITY.md replaces the non-existent npm install --verify with npm audit signatures (DOC-002).
• [DECISION] Test gate: coverage:lib now enforces --branches 75 (TEST-001); a new scripts/test-runtime-audit.js raises lib/runtime-audit.js line coverage from 68.8% to 77.8% (TEST-002); scripts/test-router.js no longer shares cumulative state across tests and cleans up its temp dirs (TEST-003); new scripts/test-hooks.js, scripts/test-cli-log.js, and scripts/test-text-util.js cover the new code.
• [DECISION] De-duplication: the five *-sync modules share lib/sync-fs.js; the ANSI logger moves to lib/cli-log.js and slugify to lib/text-util.js; installer-args.parseArgs is now table-driven (ARC-001, QUAL-001, QUAL-002).
• [DECISION] Documentation: ARCHITECTURE-MAP.md counts are regenerated and now machine-guarded by scripts/test-doc-surface-counts.js; state.STATE_FILE is the canonical state-file constant and artifact-map.js's scope is documented accurately (DOC-001, DOC-003, ARC-002).
• [DECISION] Re-audit follow-ups: a fresh self-audit confirmed no regressions and closed the residual gaps it found - installer-core.js imports the shared logger (QUAL-003); dashboard.js/planning-systems.js consume sync-fs (ARC-003); the lib/README module catalog is complete and now guarded by a completeness check (DOC-004); the ledger-append comment is corrected (DOC-005); the corrupt-state error is typed rather than message-matched (ERR-004); and the hook tests assert each warning's text (TEST-005).

Changes

• [DECISION] package.json, package-lock.json, and packages/mcp/package.json now publish the 3.13.1 version.
• [DECISION] New runtime modules lib/sync-fs.js, lib/cli-log.js, and lib/text-util.js (lib module count 87 -> 90). No public command/agent/workflow/recipe surface change.
• [DECISION] CHANGELOG, RELEASE notes, README, roadmap, reference, architecture, and the architecture map now reflect 3.13.1. The SECURITY supported-version table already carries the 3.13.x row.

Validation

• [DECISION] npm test passed all command groups.
• [DECISION] npm run release:check passed coverage:lib above the 90 percent line floor and the new 75 percent branch floor for lib/**/*.js.
• [DECISION] npm run release:check passed npm audit --omit=dev with 0 vulnerabilities and git diff --check.
• [DECISION] npm run release:check passed public surface docs for version 3.13.1 with 120 skills, 40 agents, 13 workflows, and 44 recipes.
• [DECISION] npm run release:check passed root and @godpowers/mcp package contents.

Upgrade

• [DECISION] Use npm install -g godpowers@3.13.1 or npx godpowers@3.13.1.
• [DECISION] No migration is required. Existing projects are unaffected; the changes are internal correctness, security, test-gate, and maintainability fixes with no surface change.

Notes

• [DECISION] The publish targets are npm godpowers@3.13.1, npm @godpowers/mcp@3.13.1, and GitHub release https://github.com/aihxp/godpowers/releases/tag/v3.13.1.
• [DECISION] Tagged v3.13.1 and published to npm with provenance via the tag-triggered GitHub publish workflow (.github/workflows/publish.yml): godpowers@3.13.1 and @godpowers/mcp@3.13.1 are live as the latest dist-tag.

Godpowers 3.0.2

Godpowers 3.0.2 Release

Status: Published
Date: 2026-06-11

[DECISION] Godpowers 3.0.2 is a concierge surface patch on top of the 3.0.0 surface contraction release and the 3.0.1 release-surface cleanup.
[DECISION] This release keeps core as the omitted installer profile, keeps --profile=full as the complete compatibility surface, and adds first-run, demo, and surface-control entry points for safer onboarding.
[DECISION] This release changes default guidance from catalog-first and dashboard-first output to compact recommendations with Next commands: blocks.
[DECISION] This release keeps @godpowers/mcp as the optional read-only companion package.

What's in this release

• [DECISION] 120 slash commands.
• [DECISION] 40 specialist agents.
• [DECISION] 13 executable workflows.
• [DECISION] 43 intent recipes.
• [DECISION] Three concierge entry points are now shipped: /god-first-run, /god-demo, and /god-surface.
• [DECISION] Five thin verb dispatch commands remain shipped: /god-plan, /god-fix, /god-ship, /god-capture, and /god-extend.
• [DECISION] Five read-only MCP tools remain available in @godpowers/mcp: status, next, gate_check, lint_artifact, and trace_requirement.

Changes

• [DECISION] package.json, package-lock.json, and packages/mcp/package.json now publish the 3.0.2 patch version.
• [DECISION] /god-help now starts with contextual next moves, while /god-help all remains the full installed catalog.
• [DECISION] /god, /god-next, /god-status, and the shared dashboard contract now prefer concise action briefs and explicit Next commands: blocks.
• [DECISION] godpowers demo exposes the shipped sandbox proof from the CLI without modifying the current project.
• [DECISION] godpowers surface --profile=<name> --dry-run previews runtime profile changes, and --apply writes the selected installed surface.
• [DECISION] README, roadmap, reference, architecture, release notes, and Pillar context now describe the 3.0.2 concierge surface.

Validation

• [DECISION] npm run test:quick-proof passed with 22 tests.
• [DECISION] npm run lint passed with 29 static checks.
• [DECISION] npm run release:check passed with coverage:lib at 92.69 percent line coverage.
• [DECISION] npm run release:check passed npm audit --omit=dev with 0 vulnerabilities.
• [DECISION] npm run release:check passed public surface docs for version 3.0.2 with 120 skills, 40 agents, 13 workflows, and 43 recipes.
• [DECISION] npm run release:check passed root package contents with 556 files.
• [DECISION] npm run release:check passed @godpowers/mcp package contents with 8 files.
• [DECISION] npm pack --pack-destination /tmp/godpowers-release-3.0.2 produced godpowers-3.0.2.tgz with 556 files.
• [DECISION] npm pack --workspace @godpowers/mcp --pack-destination /tmp/godpowers-release-3.0.2 produced godpowers-mcp-3.0.2.tgz with 8 files.

Upgrade

• [DECISION] Use npm install -g godpowers@3.0.2 or npx godpowers@3.0.2.
• [DECISION] Use npx godpowers --profile=full when the complete pre-3.0 command surface should be installed.
• [DECISION] Use npx godpowers --profile=core or omit --profile for the contracted default surface.
• [DECISION] Use optional MCP package install npm install -g godpowers @godpowers/mcp when the host can register MCP servers.
• [DECISION] Re-run /god-context in each project to refresh installed runtime metadata.

Notes

• [DECISION] The publish targets are npm godpowers@3.0.2, npm @godpowers/mcp@3.0.2, and GitHub release https://github.com/aihxp/godpowers/releases/tag/v3.0.2.
• [DECISION] The tag-triggered GitHub publish workflow remains the preferred npm path because it publishes with provenance.

Godpowers 3.0.1

Godpowers 3.0.1 Release

Status: Published
Date: 2026-06-11

[DECISION] Godpowers 3.0.1 is a documentation and release-surface cleanup patch on top of the 3.0.0 surface contraction release.
[DECISION] This release preserves the 3.0.0 runtime behavior: core remains the omitted installer profile, --profile=full remains the complete compatibility surface, verb dispatchers continue routing to existing leaves, and @godpowers/mcp remains the optional read-only companion package.
[DECISION] This release removes the completed migration planning document from the public documentation tree.
[DECISION] This release updates stale README, roadmap, architecture, reference, MCP, release checklist, package metadata, and package version surfaces.

What's in this release

• [DECISION] 117 slash commands.
• [DECISION] 40 specialist agents.
• [DECISION] 13 executable workflows.
• [DECISION] 42 intent recipes.
• [DECISION] Five thin verb dispatch commands remain shipped: /god-plan, /god-fix, /god-ship, /god-capture, and /god-extend.
• [DECISION] Five read-only MCP tools remain available in @godpowers/mcp: status, next, gate_check, lint_artifact, and trace_requirement.

Changes

• [DECISION] package.json, package-lock.json, and packages/mcp/package.json now publish the 3.0.1 patch version.
• [DECISION] README current-release prose now points at the 3.x release line instead of foregrounding older 2.x patch details.
• [DECISION] docs/ROADMAP.md now reports the 3.x public adoption window and the v3.0.1 current surface.
• [DECISION] docs/RELEASE-CHECKLIST.md now describes npm run lint as a separate static release-sensitive gate instead of claiming it runs inside npm run release:check.
• [DECISION] Architecture extension compatibility examples now match the shipped first-party pack range >=2.0.0 <4.0.0.
• [DECISION] MCP setup examples now pin godpowers@3.0.1 and @godpowers/mcp@3.0.1.
• [DECISION] The quick proof regression test now guards adoption canary and release verification documentation links.

Validation

• [DECISION] npm run test:quick-proof passed with 22 tests.
• [DECISION] npm run lint passed with 29 static checks.
• [DECISION] npm run release:check passed with coverage:lib at 92.82 percent line coverage.
• [DECISION] npm run release:check passed npm audit --omit=dev with 0 vulnerabilities.
• [DECISION] npm run release:check passed public surface docs for version 3.0.1 with 117 skills, 40 agents, 13 workflows, and 42 recipes.
• [DECISION] npm run release:check passed root package contents with 548 files.
• [DECISION] npm run release:check passed @godpowers/mcp package contents with 8 files.
• [DECISION] npm pack --pack-destination /tmp/godpowers-release-3.0.1 produced godpowers-3.0.1.tgz with 548 files.
• [DECISION] npm pack --workspace @godpowers/mcp --pack-destination /tmp/godpowers-release-3.0.1 produced godpowers-mcp-3.0.1.tgz with 8 files.

Upgrade

• [DECISION] Use npm install -g godpowers@3.0.1 or npx godpowers@3.0.1.
• [DECISION] Use npx godpowers --profile=full when the complete pre-3.0 command surface should be installed.
• [DECISION] Use npx godpowers --profile=core or omit --profile for the contracted default surface.
• [DECISION] Use optional MCP package install npm install -g godpowers @godpowers/mcp when the host can register MCP servers.
• [DECISION] Re-run /god-context in each project to refresh installed runtime metadata.

Notes

• [DECISION] The publish targets are npm godpowers@3.0.1, npm @godpowers/mcp@3.0.1, and GitHub release https://github.com/aihxp/godpowers/releases/tag/v3.0.1.
• [DECISION] The tag-triggered GitHub publish workflow remains the preferred npm path because it publishes with provenance.

Godpowers 3.0.0

[DECISION] Godpowers 3.0.0 is the Phase 5 surface contraction release.
[DECISION] The omitted installer profile now resolves to core, while --profile=full preserves all 117 shipped commands.
[DECISION] The release adds /god-plan, /god-fix, /god-ship, /god-capture, and /god-extend as thin verb dispatch skills.
[DECISION] The release deprecates /god-locate and /god-lifecycle in favor of /god-status --locate and /god-status --lifecycle.
[DECISION] npm latest is now godpowers@3.0.0 and @godpowers/mcp@3.0.0.
[DECISION] Publish workflow https://github.com/aihxp/godpowers/actions/runs/27308383323 passed and published both packages with provenance.
[DECISION] Published install verification passed with npm run verify:published-install.
[DECISION] Published MCP CLI verification passed with npm exec --package @godpowers/mcp@3.0.0 -- godpowers-mcp --help.

Godpowers v2.7.0

Godpowers 2.7.0

[DECISION] Godpowers 2.7.0 is the Phase 4 one-directional state release.
[DECISION] This release makes .godpowers/state.json the authority for Godpowers state decisions and treats .godpowers/PROGRESS.md plus Godpowers-owned per-tier STATE.md files as generated human views.
[DECISION] The release preserves the optional @godpowers/mcp companion boundary and keeps the main godpowers package dependency-free.

Highlights

• [DECISION] godpowers state advance --step=<step> --status=<status> --project=. updates state through the lock and regenerates managed views.
• [DECISION] Route prerequisites, executable gates, workflow handoffs, command prompts, and specialist agent contracts now use .godpowers/state.json for Godpowers state decisions.
• [DECISION] Generated markdown state views carry checksums, preserve prose outside managed fences, and replace tampered fences on the next state mutation.
• [DECISION] Deploy, observe, and launch handoffs now use structured state evidence fields.

Verification

• [DECISION] PR #40 passed Test (Node 18), Test (Node 20), Test (Node 22), and Package check.
• [DECISION] Main CI run 27303847386 passed on merge commit 026f7f609548278a823ab14ff6a76cc291bdb5d4.
• [DECISION] Tag publish workflow 27304053692 passed and published godpowers@2.7.0 plus @godpowers/mcp@2.7.0 with provenance.
• [DECISION] npm run verify:published-install passed after publish and resolved godpowers@latest to 2.7.0.
• [DECISION] npm exec --package @godpowers/mcp@2.7.0 -- godpowers-mcp --help passed after publish.

Packages

• [DECISION] npm package godpowers@2.7.0 is published at latest.
• [DECISION] npm package @godpowers/mcp@2.7.0 is published at latest and remains public.

Godpowers v2.6.0

Godpowers 2.6.0 ships the Phase 3 MCP companion package release.

Highlights:

• Added the optional @godpowers/mcp package with read-only status, next, gate_check, lint_artifact, and trace_requirement tools.
• Added godpowers mcp-info as a main-package setup helper without adding production dependencies to godpowers.
• Published both godpowers@2.6.0 and @godpowers/mcp@2.6.0 through the tag-triggered provenance workflow.

Verification:

• npm run release:check passed at merge commit 84f5ae1.
• GitHub publish workflow 27291159615 passed.
• npm run verify:published-install passed against godpowers@latest.
• npm exec --package @godpowers/mcp@2.6.0 -- godpowers-mcp --help passed.

Godpowers 2.5.2

Phase 2 blocker patch. Fixes installed runtime gate command access and build gate false-pass handling. npm publish and published install verification passed.

Godpowers 2.5.1

Godpowers 2.5.1 Release

Status: Published
Date: 2026-06-10

Godpowers 2.5.1 ships the Phase 2 host proof campaign as a docs patch release.
It keeps the 2.5.0 executable tier gates intact while adding Codex host-run
evidence for a CLI package, a browser app, and a TODO-backed React component
project.

What's in this release

• 112 slash commands
• 40 specialist agents
• 13 executable workflows
• 42 intent recipes
• 8 installer CLI helpers

Highlights

• Run A completed a Codex host proof on slugify-cli with 13 of 13 workflow steps
  complete, 16 of 16 requirements done, passing tests, passing production
  audit, passing pack dry run, and no tracked source diff.
• Run B completed a Codex host proof on Countdown with local browser evidence,
  6 of 7 requirements done, dependency audit repair, and deployed-origin proof
  deferred pending a staging URL.
• Run C completed a documented failed Codex host proof on
  react-github-readme-button, with local tests, lint, build, browser smoke, and
  production audit passing before the run blocked on Critical dev-tooling audit
  findings.
• The host proof campaign captured command usage, gate failures, repairs,
  blocker files, cost availability, and proof limits in docs/case-studies/.

Validation

• npm run test:e2e passed.
• node scripts/test-runtime-verification.js passed.
• node scripts/test-agent-browser.js passed.
• npm run release:check passed before publish.

Upgrade

• npm install -g godpowers@2.5.1 or npx godpowers@2.5.1
• Re-run /god-context in each project to refresh installed runtime metadata.
• Existing .godpowers/ state remains compatible.

Notes

• GitHub release created for v2.5.1.
• The tag matches the npm package version.
• The v2.5.1 tag points to the release commit that matches the npm
  godpowers@2.5.1 package.