godpowers 3.0.2 → 3.13.0

package/CHANGELOG.md

@@ -7,6 +7,289 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [3.13.0] - 2026-06-16
+
+### Changed
+- The default greenfield workflow (`full-arc`, run by `/god-mode`) now runs two
+  more steps so the one-shot product ships audited and documented. A `code-audit`
+  job (`god-debt-assessor`) runs after the build and before deploy/harden, giving
+  the whole AI-generated codebase a scored audit that catches what the per-slice
+  reviews could not see across files. A `docs` job (`god-docs-writer`) runs after
+  harden and before launch, writing the project documentation and verifying every
+  claim against the code (drift detected) before the product ships. `deploy` and
+  `harden` now need `code-audit`; `launch` now needs `docs`. The plan goes from
+  11 to 13 steps. No new skill, agent, workflow, or recipe surface: both jobs
+  reuse agents that already exist.
+- `GOD-ORCHESTRATOR-RUNBOOK` documents the new audit and docs positions in the
+  greenfield arc.
+
+## [3.12.1] - 2026-06-16
+
+### Changed
+- De-duplicated the audit lanes in `god-debt-assessor`. Its Security dimension
+  now defers to `god-harden-auditor`: when `.godpowers/harden/FINDINGS.md`
+  exists, score Security from harden's verdict and cite its finding IDs instead
+  of re-running the OWASP walkthrough, recording a security finding only for
+  something harden did not cover. Its Code Quality dimension is explicitly the
+  whole-repo point-in-time read that complements, not duplicates,
+  `god-quality-reviewer`'s per-slice diff review.
+
+## [3.12.0] - 2026-06-16
+
+### Changed
+- Upgraded `god-debt-assessor` (`/god-tech-debt`) to a codeauditor-grade,
+  read-only source-code audit: nine weighted dimensions scored 0-100 with grade
+  bands and risk-capping, per-finding Severity/Confidence/Effort, adversarial
+  verification with Suspected marking, paper-construct/theater hunting,
+  root-not-leaves systemic clustering, a strengths-to-preserve section,
+  calibration to maturity, a file:line + substitution evidence gate, and a
+  self-contained "how to use this report" protocol for an acting agent. Keeps
+  Godpowers' broader operational/knowledge debt categories as extra lenses.
+  Output stays `.godpowers/tech-debt/REPORT.md`.
+
+### Added
+- Added the audit-remediation loop: a new `audit-remediate` recipe routes
+  "audit and fix until clean" intent, and a `GOD-ORCHESTRATOR-RUNBOOK` section
+  defines the bounded drive-to-zero loop (audit, select worst-first, fix with
+  `god-debugger`, verify with an independent reviewer, bound the retries with
+  `evidence.outcome`, re-audit until no Confirmed Critical/High remains). The
+  can't-fake-done gate makes "clean" an evidence-backed re-audit; un-fixable
+  findings pause as precise blockers instead of silent skips.
+
+### Notes
+- No new skill or agent (god-debt-assessor enhanced in place). Recipe surface
+  count moves 43 to 44. The audit-remediation loop is opt-in (intent/recipe or
+  an end-of-arc pass); it is not wired into the default greenfield `full-arc`.
+
+## [3.11.0] - 2026-06-15
+
+### Added
+- Added `lib/evidence-import.js` and the `npx godpowers import-ledger [--from
+  <path>]` CLI: a one-time, best-effort importer that copies an existing Mythify
+  `.mythify/` ledger into `.godpowers/ledger/` (verifications rebinding
+  plan/step to arc/substep, reflections, memory merged by key, lessons, and
+  outcomes). Records are appended; no state rollup and no gate events.
+- Exported `readJsonl` and `appendJsonlAtomic` from `lib/evidence.js` for reuse.
+
+### Notes
+- This is the final item in `docs/FUSION-ARCHITECTURE.md`. With it, the native
+  fusion of Mythify's evidence engine and quarterback into Godpowers (Phases 0-3
+  plus the optional importer) is complete.
+
+## [3.10.0] - 2026-06-15
+
+### Added
+- Added three read-only MCP tools to `@godpowers/mcp` (Phase 3, the final fusion
+  slice): `work_report` (wraps `lib/work-report.js`, forced peek so it never
+  advances the cursor), `route` (wraps `lib/quarterback.js`, never mutates
+  state), and `verification_history` (wraps `lib/evidence.js` history). All
+  carry `readOnlyHint:true` via the same `requireRuntime` bridge. The companion
+  now exposes eight read-only tools.
+
+### Notes
+- This release completes the native fusion of Mythify's evidence engine and
+  quarterback into Godpowers across Phases 0-3 (`docs/FUSION-ARCHITECTURE.md`):
+  the evidence producer, enforced close-on-evidence on the build and harden
+  gates, the quarterback entry router, the work report, reflections, memory,
+  lessons, outcome loops, and now the MCP read tools. Mutating verification stays
+  on the CLI and orchestrator path.
+
+## [3.9.0] - 2026-06-15
+
+### Added
+- Added `evidence.outcome.start/check/stop/status` (Phase 3), rebound from
+  Mythify's `outcomes/<slug>/` store: a bounded retry loop with `goal.json` and
+  `iterations.jsonl` at `.godpowers/ledger/outcomes/<slug>/`. `check` runs the
+  verifier through `evidence.verify` (so the executed verdict is also written to
+  the main verifications ledger and rolled up), appends an iteration, and marks
+  the outcome succeeded, failed when the budget is exhausted, or still active.
+- Added the `npx godpowers outcome start|check|stop|status <name> [--goal ...]
+  [--verify "<cmd>"] [--budget N] [--substep <id>] [--reason ...]` CLI subcommand.
+
+### Notes
+- Outcome state lives under the ledger; `check` is the only path that mutates
+  shared state, and it does so through the existing `evidence.verify` rollup. No
+  existing command behavior changed.
+
+## [3.8.0] - 2026-06-15
+
+### Added
+- Added `evidence.lesson.add/list` (Phase 3), rebound from Mythify's lessons
+  store: append tagged lessons with project or global scope to
+  `.godpowers/ledger/lessons.jsonl` (or `~/.godpowers/lessons.jsonl` for global).
+- Added the `npx godpowers lesson add|list "<lesson>" [--tags a,b] [--scope
+  project|global]` CLI subcommand.
+
+### Changed
+- `evidence.reflect()` now auto-records a project lesson tagged `auto-reflected`
+  when a reflection carries a lesson, matching the upstream reflect tool. The
+  reflection record itself is unchanged.
+
+### Notes
+- The lessons store is isolated: it never touches `state.json`, the
+  verifications ledger, or the event stream.
+
+## [3.7.0] - 2026-06-15
+
+### Added
+- Added `evidence.memory.set/get/list/clear` (Phase 3), rebound from Mythify's
+  memory.json: a durable key/value store with categories fact, decision,
+  discovery, and state at `.godpowers/ledger/memory.json`. `set` upserts by key
+  and defaults the category to fact; `clear` removes one key or all entries;
+  writes go through `lib/atomic-write.js`.
+- Added the `npx godpowers memory set|get|list|clear [<key>] [<value>]
+  [--category ...]` CLI subcommand.
+
+### Notes
+- The memory store is isolated: it never touches `state.json`, the verifications
+  ledger, or the event stream. No existing command behavior changed.
+
+## [3.6.0] - 2026-06-15
+
+### Added
+- Added `evidence.reflect()` and `evidence.reflections()` (Phase 3), rebound from
+  Mythify's reflect tool: record action, outcome (success/partial/failure),
+  observation, root cause, next action, and an optional lesson to
+  `.godpowers/ledger/reflections.jsonl` with substep context.
+- Added the `npx godpowers reflect --action "<...>" --outcome <...> --next "<...>"`
+  CLI subcommand (`--observation`, `--root-cause`, `--lesson`, `--substep`
+  optional).
+
+### Changed
+- Generalized the ledger jsonl append/read into shared `appendJsonlAtomic` and
+  `readJsonl` helpers in `lib/evidence.js` so verifications and reflections share
+  one atomic path. No change to the verifications record shape or behavior.
+
+### Notes
+- `reflect` is isolated: it never touches `state.json`, the verifications ledger,
+  or the event stream. No existing command behavior changed.
+
+## [3.5.0] - 2026-06-15
+
+### Added
+- Added `lib/work-report.js`, the chat play-by-play (Phase 3) rebound from
+  Mythify's build_work_report. It reads the evidence ledger, surfaces an
+  Attention section for unverified records, summarizes passed/failed/attested,
+  and advances a report cursor at `.godpowers/ledger/reports/cursor.json` so a
+  fresh session emits only what is new.
+- Added the read-only `npx godpowers report --since last` CLI subcommand
+  (`--since all` for full history, `--peek` to show without advancing the
+  cursor).
+
+### Notes
+- `report` is read-only beyond the report cursor and never mutates `state.json`;
+  no existing command behavior changed. This is the first Phase 3 slice; outcome
+  loops, memory, lessons, reflections, and MCP read tools remain to come.
+
+## [3.4.0] - 2026-06-15
+
+### Added
+- Added `lib/quarterback.js`, the entry-level two-layer router (Phase 2 of the
+  fusion design). It composes `router.suggestNext` and `recipes.matchIntent` and
+  adds the two genes Godpowers lacked at entry: refuse-on-red (never start new
+  work when the latest executed verdict is red or harden findings carry an
+  unresolved Critical) and proportional ceremony (a one-line fix routes to
+  `/god-fast`, not an arc). The priority ladder is recover, resume, recovery,
+  brownfield, research, review, full, feature, trivial; first match wins.
+- Added the read-only `npx godpowers route "<prompt>"` CLI subcommand, which
+  returns the chosen play with its next command, ceremony level, verification
+  strategy, and an evidence block (classification, latest verdict, active arc,
+  open findings). `route` never mutates state.
+
+### Notes
+- `route` is read-only and additive; no existing command behavior changed. The
+  quarterback reads the evidence ledger and harden findings to decide refuse-on-red.
+
+## [3.3.0] - 2026-06-15
+
+### Added
+- Added the `npx godpowers can-close --substep <id>` CLI subcommand, a read-only
+  face over `evidence.canClose`. It exits zero only when the substep has the
+  evidence to close (executable-gated tiers need a passing executed record since
+  they went in-flight; other tiers accept an attested record), so skills and the
+  orchestrator can shell into the strict close gate the way they already shell
+  `gate` and `state advance`.
+
+### Changed
+- Wired the `GOD-ORCHESTRATOR-RUNBOOK` close loop to record executed evidence and
+  confirm `can-close` is green before advancing an executable-gated sub-step to
+  done. This completes the orchestrator side of the Phase 1 close-on-evidence
+  path (`docs/FUSION-ARCHITECTURE.md`). No existing command behavior changed; the
+  CLI addition is additive and the runbook change is prompt-level guidance.
+
+## [3.2.0] - 2026-06-15
+
+### Changed
+- BEHAVIOR CHANGE: the `harden` gate now requires executed verification
+  evidence. `lib/gate.js`'s build-only executed-evidence requirement is
+  generalized to every executable-gated tier, driven by
+  `evidence.EXECUTED_REQUIRED_SUBSTEPS` (`build`, `deploy`, `harden`). The
+  harden gate now requires at least one passed and zero failed verification
+  commands in `state.json` `verification.commands[]`, in addition to its
+  no-Critical-findings check. A security tier can no longer close "done" without
+  an exit-code-backed passing record. Finding ids are tier-prefixed, so the
+  build tier keeps its `build-verification-*` contract and harden gains
+  `harden-verification-*`.
+- Updated the `god-harden` skill to record the executed security check
+  (for example `npx godpowers verify "npm audit --omit=dev" --substep
+  tier-3.harden`) before running the harden gate.
+
+### Added
+- Added the `tier-3.harden` state-step mapping in `lib/artifact-map.js` so the
+  harden gate reads structured state evidence (matching `build`).
+
+### Notes
+- This is the first enforced close-on-evidence behavior change from the Phase 1
+  fusion design (`docs/FUSION-ARCHITECTURE.md`). Projects that closed a harden
+  step without a verification record must now run `godpowers verify` (or record
+  an attested record where no executable check applies) before the harden gate
+  passes. The build gate behavior is unchanged.
+
+## [3.1.1] - 2026-06-15
+
+### Added
+- Added `evidence.canClose(substep)` to `lib/evidence.js`, the read-only strict
+  close-gate primitive rebound from Mythify's completion rule: a substep may
+  close only when evidence bound to it since it went in-flight supports the
+  close. Tier-appropriate per `docs/FUSION-ARCHITECTURE.md` section 4.2:
+  `build`/`deploy`/`harden` require the latest executed record to be
+  `verified:true`; other substeps accept an executed pass or an attested record,
+  and a failed executed record always blocks.
+
+### Notes
+- `canClose` is additive and read-only. It does not mutate state and is not yet
+  wired into `gate.js` or the close path; wiring it in (the deliberate
+  behavior change) is the remaining Phase 1 work tracked in
+  `docs/FUSION-ARCHITECTURE.md`. No existing behavior changed in this release.
+
+## [3.1.0] - 2026-06-15
+
+### Added
+- Added the evidence producer in `lib/evidence.js`, vendored from the Mythify
+  Node engine (`mythify-mcp@3.6.3`, `verify_run`/`verify_claim`). `evidence.verify()`
+  executes a command, appends an exit-code-backed record to the new append-only
+  `.godpowers/ledger/verifications.jsonl`, rolls the latest verdict per command
+  into `state.json` `verification.commands[]` through `lib/state.js`, and emits
+  `gate.pass`/`gate.fail` to the hash-chained `runs/<id>/events.jsonl` stream.
+  `evidence.verifyClaim()` records a second-class attested record that never
+  rolls up.
+- Added the `npx godpowers verify "<cmd>" --substep <id> --claim "<text>"` CLI
+  subcommand (with `--timeout`, and `--attest`/`--evidence` for attestations),
+  wired through `lib/cli-dispatch.js`.
+- Added `lib/evidence/.provenance.json` recording the vendored engine's source,
+  version, commit, and adaptations, plus `scripts/sync-evidence-engine.js` to
+  re-pull the upstream engine, re-state the adaptations, and flag any upstream
+  record-shape drift for review.
+- Added `docs/FUSION-ARCHITECTURE.md`, the canonical design for transplanting
+  Mythify's evidence engine and quarterback into Godpowers (Phases 0-3; this
+  release lands Phase 0).
+
+### Changed
+- `state.json` `verification.commands[]` is now reliably populated by the
+  evidence producer (previously specified in the schema but never written).
+  This is additive: the build gate reads the same shape, no gate behavior or
+  close-on-evidence logic changed (that is Phase 1).
+
 ## [3.0.2] - 2026-06-11
 
 ### Added

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-3.0.2-blue)](CHANGELOG.md)
+[![Version](https://img.shields.io/badge/version-3.13.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.**
@@ -30,13 +30,27 @@ 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 3.0.2 is a concierge surface patch on top of the 3.0.0 surface
-contraction release. The current 3.x line keeps the omitted installer profile
-on `core`, adds first-run, demo, and surface-control entry points, preserves
-`--profile=full` for compatibility, keeps locate and lifecycle views under
-`/god-status`, ships the optional `@godpowers/mcp` companion package, and
-verifies docs, package contents, npm metadata, GitHub release state, and
-published install behavior before public release.
+Version 3.13.0 makes the default greenfield arc (`/god-mode`) miss less. The
+one-shot `full-arc` workflow now runs a whole-codebase code audit after the
+build (so it catches what the per-slice reviews missed in AI-generated code) and
+a documentation pass after harden (so the shipped product has docs verified
+against the code, not vibes). The arc goes build, code-audit, deploy, observe,
+harden, docs, launch, final-sync: per-slice review, whole-codebase audit plus
+remediation, a security gate, and verified docs before launch. This builds on
+3.12.x, which made that code audit codeauditor-grade: `god-debt-assessor`
+(`/god-tech-debt`) produces a scored, prioritized, self-contained source-code
+audit across nine weighted dimensions, and the `audit-remediate` recipe drives
+the findings to zero (audit, fix worst-first with an independent reviewer,
+re-audit, bounded by an outcome budget, with the can't-fake-done gate ensuring
+"clean" is evidence-backed). It all sits on top of the completed Mythify fusion
+(the evidence producer, enforced close-on-evidence, the quarterback, work report,
+reflections, memory, lessons, outcome loops, MCP read tools, and ledger importer). The current 3.x line keeps
+the omitted installer profile on `core`, keeps first-run, demo, and
+surface-control entry points, preserves `--profile=full` for compatibility,
+keeps locate and lifecycle views under `/god-status`, ships the optional
+`@godpowers/mcp` companion package, and verifies docs, package contents, npm
+metadata, GitHub release state, and published install behavior before public
+release.
 
 Maintainer hardening continues on the 3.x line with small, audited public
 surface updates when they close real workflow gaps. Historical release details
@@ -315,14 +329,14 @@ dependency to the main `godpowers` package:
 
 ```bash
 npx godpowers mcp-info --project=.
-npx -y -p godpowers@3.0.2 -p @godpowers/mcp@3.0.2 godpowers-mcp serve --project=.
+npx -y -p godpowers@3.13.0 -p @godpowers/mcp@3.13.0 godpowers-mcp serve --project=.
 ```
 
 The companion exposes `status`, `next`, `gate_check`, `lint_artifact`, and
 `trace_requirement`. Host registration is opt-in:
 
 ```bash
-npx -y -p godpowers@3.0.2 -p @godpowers/mcp@3.0.2 godpowers-mcp setup --host=codex --project=. --write
+npx -y -p godpowers@3.13.0 -p @godpowers/mcp@3.13.0 godpowers-mcp setup --host=codex --project=. --write
 ```
 
 See [MCP Companion](docs/mcp.md) for package boundaries and setup details.

package/RELEASE.md

@@ -1,53 +1,41 @@
-# Godpowers 3.0.2 Release
+# Godpowers 3.13.0 Release
 
-> Status: Published
-> Date: 2026-06-11
+> Status: Prepared
+> Date: 2026-06-16
 
-[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.
+[DECISION] Godpowers 3.13.0 is a minor release that hardens the default greenfield arc. The one-shot `full-arc` workflow run by `/god-mode` now audits the whole codebase after the build and writes verified documentation after harden, so a long-running idea-to-production run ships audited and documented without a separate manual pass.
+[DECISION] No new skill, agent, workflow, or recipe surface is added: both new steps reuse existing agents (`god-debt-assessor`, `god-docs-writer`). Surface counts are unchanged from 3.12.1.
+[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.12.1 surface (fusion + codeauditor-grade audit + remediation loop).
 
 ## 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`.
+- [DECISION] `full-arc` gains a `code-audit` job (`god-debt-assessor`, `mode: post-build-audit`) that runs after `build` and before `deploy`/`harden`. It gives the whole AI-generated codebase a scored, prioritized audit that catches issues the per-slice `god-spec-reviewer` + `god-quality-reviewer` reviews cannot see across files.
+- [DECISION] `full-arc` gains a `docs` job (`god-docs-writer`, `mode: product-docs-verify`) that runs after `harden` and before `launch`. It writes the project documentation and verifies every claim against the code (drift detected) before the product ships.
+- [DECISION] Dependencies were rewired: `deploy` and `harden` now `need` `code-audit`; `launch` now `needs` `docs`. The greenfield arc is build, code-audit, deploy, observe, harden, docs, launch, final-sync. The `full-arc` plan goes from 11 to 13 steps.
+- [DECISION] `GOD-ORCHESTRATOR-RUNBOOK` documents the audit and docs positions in the greenfield arc.
+- [DECISION] 120 slash commands, 40 specialist agents, 13 executable workflows, 44 intent recipes, and the full fusion + audit surface remain available.
 
 ## 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.
+- [DECISION] `package.json`, `package-lock.json`, and `packages/mcp/package.json` now publish the 3.13.0 version.
+- [DECISION] `workflows/full-arc.yaml` adds the `code-audit` and `docs` jobs and rewires `deploy`/`harden`/`launch` dependencies. No lib change.
+- [DECISION] CHANGELOG, RELEASE notes, README, roadmap, reference, architecture, and the MCP docs now reflect 3.13.0. SECURITY supported-version table adds the `3.13.x` row and moves `3.12.x` to security fixes only.
 
 ## 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 lint` passed with 29 static checks (agent contract + size + refs intact).
+- [DECISION] `node tests/integration/full-arc.test.js`, `node scripts/test-workflow-runner.js`, and `node scripts/test-agent-refs.js` passed: `full-arc` plans to 13 steps with a valid DAG and both `god-debt-assessor` and `god-docs-writer` are real agents.
+- [DECISION] `npm run release:check` passed `coverage:lib` above the 90 percent line floor for `lib/**/*.js`.
 - [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.
+- [DECISION] `npm run release:check` passed public surface docs for version 3.13.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.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.
+- [DECISION] Use `npm install -g godpowers@3.13.0` or `npx godpowers@3.13.0`.
+- [DECISION] No migration is required. Existing projects are unaffected; the change only adds steps to the greenfield one-shot arc, which now takes longer in exchange for an audited and documented product.
 
 ## 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.
+- [DECISION] The publish targets are npm `godpowers@3.13.0`, npm `@godpowers/mcp@3.13.0`, and GitHub release `https://github.com/aihxp/godpowers/releases/tag/v3.13.0`.
+- [DECISION] The tag-triggered GitHub publish workflow remains the preferred npm path because it publishes with provenance. This release has not been tagged or published to npm yet.