godpowers 2.5.0 → 2.5.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -7,6 +7,19 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
7
7
 
8
8
  ## [Unreleased]
9
9
 
10
+ ## [2.5.1] - 2026-06-10
11
+
12
+ ### Added
13
+ - Added three Codex host-run proof case studies for slugify-cli, Countdown, and
14
+ react-github-readme-button.
15
+ - Added Phase 2 proof evidence for successful CLI and web app runs plus one
16
+ blocked harden run with Critical dev-tooling findings preserved as a public
17
+ blocker.
18
+
19
+ ### Changed
20
+ - Updated USERS, README, roadmap, reference, architecture, release notes, and
21
+ bridge-plan status for the Phase 2 host proof campaign.
22
+
10
23
  ## [2.5.0] - 2026-06-10
11
24
 
12
25
  ### Added
package/README.md CHANGED
@@ -2,7 +2,7 @@
2
2
 
3
3
  [![CI](https://github.com/aihxp/godpowers/actions/workflows/ci.yml/badge.svg)](https://github.com/aihxp/godpowers/actions/workflows/ci.yml)
4
4
  [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
5
- [![Version](https://img.shields.io/badge/version-2.5.0-blue)](CHANGELOG.md)
5
+ [![Version](https://img.shields.io/badge/version-2.5.1-blue)](CHANGELOG.md)
6
6
  [![npm](https://img.shields.io/npm/v/godpowers.svg)](https://www.npmjs.com/package/godpowers)
7
7
 
8
8
  **Ship fast. Ship right. Ship everything. Ship accountably.**
@@ -21,15 +21,19 @@ CLI-verifiable canaries now cover [sindresorhus/is](docs/case-studies/sindresorh
21
21
  [expressjs/cors](docs/case-studies/expressjs-cors-adoption-canary.md), and
22
22
  [tinyhttp/tinyhttp](docs/case-studies/tinyhttp-adoption-canary.md), with host
23
23
  slash-command gaps called out rather than hidden.
24
+ Host-run proof studies now cover [slugify-cli](docs/case-studies/run-a.md),
25
+ [Countdown](docs/case-studies/run-b.md), and
26
+ [react-github-readme-button](docs/case-studies/run-c.md), including one
27
+ blocked harden run recorded as evidence instead of hidden as success.
24
28
 
25
29
  Godpowers makes AI coding accountable: every serious run should leave disk
26
30
  state, artifacts, validation gates, host guarantees, and a next action. Code is
27
31
  only one output. The project memory and proof trail matter too.
28
32
 
29
- Version 2.5.0 adds executable tier gates through `npx godpowers gate` while
30
- keeping the 2.4 command-family UX, external CLI canary evidence, prompt-size
31
- guardrails, legacy command quarantine, lib coverage gating, and package
32
- verification before publish.
33
+ Version 2.5.1 adds three Codex host-run proof studies on top of the 2.5.0
34
+ executable tier gates, while keeping the 2.4 command-family UX, external CLI
35
+ canary evidence, prompt-size guardrails, legacy command quarantine, lib
36
+ coverage gating, and package verification before publish.
33
37
 
34
38
  Maintainer hardening continues on the 2.x line with small, audited public
35
39
  surface updates when they close real workflow gaps. The 2.1.0 patch closes a command-injection vector in the
package/RELEASE.md CHANGED
@@ -1,12 +1,12 @@
1
- # Godpowers 2.5.0 Release
1
+ # Godpowers 2.5.1 Release
2
2
 
3
- > Status: Ready for package verification
3
+ > Status: Release candidate
4
4
  > Date: 2026-06-10
5
5
 
6
- Godpowers 2.5.0 ships executable tier gates for the code-first kernel
7
- migration. It keeps the slash-command workflow intact while giving command
8
- capable hosts a stable JSON gate contract and non-zero exit codes for blocked
9
- tier transitions.
6
+ Godpowers 2.5.1 ships the Phase 2 host proof campaign as a docs patch release.
7
+ It keeps the 2.5.0 executable tier gates intact while adding Codex host-run
8
+ evidence for a CLI package, a browser app, and a TODO-backed React component
9
+ project.
10
10
 
11
11
  ## What's in this release
12
12
 
@@ -18,35 +18,35 @@ tier transitions.
18
18
 
19
19
  ## Highlights
20
20
 
21
- - `npx godpowers gate --tier=<tier> --project=.` checks PRD, design,
22
- architecture, roadmap, stack, repo, build, and harden artifacts.
23
- - Gate JSON returns `{tier, verdict, artifacts, checks, findings, summary}` for
24
- host-visible evidence.
25
- - Build gates require `.godpowers/build/STATE.md` to record exact verification
26
- commands that passed.
27
- - Harden gates fail unresolved Critical findings and blocked launch gates.
28
- - `/god-mode` now runs executable gates between tier transitions.
29
- - Tier routes declare `standards.gate-command`, and static checks enforce the
30
- skill and route metadata.
31
- - CLI command dispatch now lives in `lib/cli-dispatch.js`, keeping
32
- `bin/install.js` thin.
21
+ - Run A completed a Codex host proof on slugify-cli with 13 of 13 workflow steps
22
+ complete, 16 of 16 requirements done, passing tests, passing production
23
+ audit, passing pack dry run, and no tracked source diff.
24
+ - Run B completed a Codex host proof on Countdown with local browser evidence,
25
+ 6 of 7 requirements done, dependency audit repair, and deployed-origin proof
26
+ deferred pending a staging URL.
27
+ - Run C completed a documented failed Codex host proof on
28
+ react-github-readme-button, with local tests, lint, build, browser smoke, and
29
+ production audit passing before the run blocked on Critical dev-tooling audit
30
+ findings.
31
+ - The host proof campaign captured command usage, gate failures, repairs,
32
+ blocker files, cost availability, and proof limits in `docs/case-studies/`.
33
33
 
34
34
  ## Validation
35
35
 
36
- - `node scripts/test-gate.js` green
37
- - `node scripts/test-cli-dispatch.js` green
38
- - `node scripts/static-check.js` green
39
- - `npm run release:check` required before publish
36
+ - `npm run test:e2e` passed.
37
+ - `node scripts/test-runtime-verification.js` passed.
38
+ - `node scripts/test-agent-browser.js` passed.
39
+ - `npm run release:check` passed before publish.
40
40
 
41
41
  ## Upgrade
42
42
 
43
- - `npm install -g godpowers@2.5.0` or `npx godpowers@2.5.0`
43
+ - `npm install -g godpowers@2.5.1` or `npx godpowers@2.5.1`
44
44
  - Re-run `/god-context` in each project to refresh installed runtime metadata.
45
45
  - Existing `.godpowers/` state remains compatible.
46
46
 
47
47
  ## Notes
48
48
 
49
- - GitHub release creation for `v2.5.0`.
50
- - The tag should match the npm package version.
51
- - The `v2.5.0` tag should point to the release commit that matches the npm
52
- `godpowers@2.5.0` package.
49
+ - GitHub release created for `v2.5.1`.
50
+ - The tag matches the npm package version.
51
+ - The `v2.5.1` tag points to the release commit that matches the npm
52
+ `godpowers@2.5.1` package.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "godpowers",
3
- "version": "2.5.0",
3
+ "version": "2.5.1",
4
4
  "description": "AI-powered development system: 112 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.",
5
5
  "bin": {
6
6
  "godpowers": "./bin/install.js"