godpowers 3.0.1 → 3.11.0

package/CHANGELOG.md

@@ -7,6 +7,259 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [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
+- Added `/god-first-run`, `/god-demo`, and `/god-surface` as concierge
+  entry points for onboarding, sandbox proof, and post-install surface control.
+- Added the `try-safely` recipe for users who want a proof path before
+  touching their current project.
+- Added `godpowers demo` and `godpowers surface` CLI helpers, including
+  dry-run and apply flows for runtime profile changes.
+
+### Changed
+- Changed default command guidance from catalog-first and dashboard-first
+  output to compact recommendations with `Next commands:` blocks.
+- Updated `/god-help`, `/god`, `/god-next`, `/god-status`, and shared
+  dashboard contracts so full catalogs and full dashboards are opt-in.
+- Updated README, roadmap, reference, release notes, architecture, and Pillar
+  context counts for the 120-command and 43-recipe public surface.
+
+### Fixed
+- Added package, routing, installer-profile, command-family, quick-proof, and
+  surface-profile tests for the new concierge surface.
+- Refreshed repo documentation sync and repo surface sync evidence after the
+  new surface landed.
+
 ## [3.0.1] - 2026-06-11
 
 ### Changed
@@ -42,7 +295,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Routed `/god-observe` through the `ship` verb boundary based on Phase 2 host
   proof evidence.
 - Updated public docs, profile tests, command-family tests, and Phase 5
-  surface evidence for the 117-command surface.
+  surface evidence for the 120-command surface.
 
 ### Deprecated
 - Deprecated `/god-locate` in favor of `/god-status --locate`.
@@ -254,7 +507,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   Proof goal labels resolve through shipped `/god` recipes and routes.
 
 ### Changed
-- Updated public surface counts to 112 slash commands and 42 intent recipes
+- Updated public surface counts to 120 slash commands and 43 intent recipes
   across release notes, reference docs, architecture maps, package metadata,
   and project Pillars.
 - Tightened public front-door recipe matching for starter phrases including

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.1-blue)](CHANGELOG.md)
+[![Version](https://img.shields.io/badge/version-3.11.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,12 +30,19 @@ 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.1 is a release-surface cleanup patch on top of the 3.0.0 surface
-contraction release. The current 3.x line keeps the omitted installer profile
-on `core`, 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.11.0 adds the optional one-time `.mythify/` ledger importer (`npx
+godpowers import-ledger`), the final piece of the native fusion of Mythify's
+evidence engine and quarterback into Godpowers. The fusion is now complete end
+to end: 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, the read-only MCP tools, and now a path to bring
+existing Mythify ledgers along. 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
@@ -124,6 +131,13 @@ npx godpowers --codex --local --profile=builder
 npx godpowers --all --profile=maintainer
 ```
 
+After install, switch or preview the visible surface without starting over:
+
+```bash
+npx godpowers surface --profile=builder --codex --global --dry-run
+npx godpowers surface --profile=builder --codex --global --apply
+```
+
 Profiles are `core`, `builder`, `maintainer`, `suite`, and `full`. `core`
 installs the front door, status, verb dispatchers, and `/god-mode`
 compatibility. `full` preserves the complete command surface, while the smaller
@@ -217,13 +231,13 @@ same thing when you open a new session in a Godpowers project.
 If the full command surface feels large, begin with one of these paths and only
 learn the next command when Godpowers recommends it.
 
-`/god-help` presents command families first: start, continue, build, verify,
-operate, maintain, capture, recover, extend, collaborate, and configure. Leaf
-commands remain direct shortcuts.
+`/god-help` presents a short state-aware view by default. `/god-help all`
+shows the complete catalog. Leaf commands remain direct shortcuts.
 
 | Goal | Starter path |
 |---|---|
-| Start a product | `/god-init`, `/god-plan`, `/god-build` |
+| Start a product | `/god-first-run`, `/god-init`, `/god-plan`, `/god-build` |
+| Try safely | `/god-demo`, `/god-first-run`, `/god-init` |
 | Add a feature | `/god-reconcile`, `/god-feature`, `/god-sync`, `/god-review` |
 | Fix production | `/god-fix`, `/god-postmortem`, `/god-status` |
 | Audit an existing repo | `/god-preflight`, `/god-archaeology`, `/god-reconstruct`, `/god-audit`, `/god-tech-debt` |
@@ -253,7 +267,10 @@ runtime that can execute Node:
 ```bash
 npx godpowers status --project=.
 npx godpowers next --project=.
+npx godpowers demo --project=.
+npx godpowers surface --profile=core --codex --global --dry-run
 npx godpowers status --project=. --brief
+npx godpowers status --project=. --full
 npx godpowers status --project=. --json
 npx godpowers quick-proof --project=.
 npx godpowers state advance --step=prd --status=done --project=.
@@ -304,14 +321,14 @@ dependency to the main `godpowers` package:
 
 ```bash
 npx godpowers mcp-info --project=.
-npx -y -p godpowers@3.0.1 -p @godpowers/mcp@3.0.1 godpowers-mcp serve --project=.
+npx -y -p godpowers@3.11.0 -p @godpowers/mcp@3.11.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.1 -p @godpowers/mcp@3.0.1 godpowers-mcp setup --host=codex --project=. --write
+npx -y -p godpowers@3.11.0 -p @godpowers/mcp@3.11.0 godpowers-mcp setup --host=codex --project=. --write
 ```
 
 See [MCP Companion](docs/mcp.md) for package boundaries and setup details.
@@ -592,7 +609,7 @@ Pi. T3 Code inherits from the underlying agent (Codex / Claude / OpenCode).
 - [Quick Proof](docs/quick-proof.md)
 - [First 10 Minute Proof Case Study](docs/case-studies/first-10-minute-proof.md)
 - [Concepts](docs/concepts.md)
-- [Command reference (all 117 skills + 40 agents)](docs/reference.md)
+- [Command reference (all 120 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)

package/RELEASE.md

@@ -1,53 +1,41 @@
-# Godpowers 3.0.1 Release
+# Godpowers 3.11.0 Release
 
-> Status: Published
-> Date: 2026-06-11
+> Status: Prepared
+> Date: 2026-06-15
 
-[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.
+[DECISION] Godpowers 3.11.0 adds the optional one-time `.mythify/` ledger importer, the final item in the fusion design. With it, the native fusion of Mythify's evidence engine and quarterback into Godpowers (Phases 0-3 plus the optional importer) is complete.
+[DECISION] The importer is optional, one-time, and additive: it appends imported records to the Godpowers ledger and does not roll up into `state.json` or emit gate events. No existing command behavior changes.
+[DECISION] This release keeps `core` as the omitted installer profile, keeps `--profile=full` as the complete compatibility surface, and keeps the 3.1.0-3.10.0 evidence, close-gate, quarterback, work-report, reflections, memory, lessons, outcome, and MCP surface.
 
 ## 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`.
+- [DECISION] New `lib/evidence-import.js` and `npx godpowers import-ledger [--from <path>]`.
+- [DECISION] It copies an existing Mythify `.mythify/` ledger into `.godpowers/ledger/`: verifications (rebinding plan/step_id/step_title/step_status to arc/substep/substep_status), reflections, memory (merged by key), lessons (lessons/*.json to lessons.jsonl), and outcomes (goal.json + iterations.jsonl per slug).
+- [DECISION] Records are appended; the import does not roll up into `state.json` or emit gate events.
+- [DECISION] 120 slash commands, 40 specialist agents, 13 executable workflows, 43 intent recipes, and the 3.1.0-3.10.0 evidence, close-gate, quarterback, work-report, reflections, memory, lessons, outcome, and eight-tool MCP surface remain available.
 
 ## 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.
+- [DECISION] `package.json`, `package-lock.json`, and `packages/mcp/package.json` now publish the 3.11.0 minor version.
+- [DECISION] CHANGELOG, RELEASE notes, README, roadmap, reference, architecture, and the SECURITY supported-version series now describe the 3.11.0 importer and the completed fusion.
 
 ## 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] `node scripts/test-evidence-import.js` passed with 4 importer tests, including the plan/step to arc/substep rebind.
+- [DECISION] `node scripts/test-cli-dispatch.js` passed with 48 CLI dispatch tests, including the new `import-ledger` tests.
+- [DECISION] `npm run release:check` passed `coverage:lib` above the 90 percent line floor for `lib/**/*.js` (evidence-import.js at 97 percent lines).
 - [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.
+- [DECISION] `npm run release:check` passed public surface docs for version 3.11.0 with 120 skills, 40 agents, 13 workflows, and 43 recipes.
+- [DECISION] `npm run release:check` passed root and `@godpowers/mcp` package contents.
 
 ## 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.
+- [DECISION] Use `npm install -g godpowers@3.11.0` or `npx godpowers@3.11.0`.
+- [DECISION] No migration is required. The importer is optional and additive; no other behavior changed.
 
 ## 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 publish targets are npm `godpowers@3.11.0`, npm `@godpowers/mcp@3.11.0`, and GitHub release `https://github.com/aihxp/godpowers/releases/tag/v3.11.0`.
 - [DECISION] The tag-triggered GitHub publish workflow remains the preferred npm path because it publishes with provenance.
+- [DECISION] This is the final planned release of the fusion design. Every phase (0-3) and the optional importer are implemented and shipped to main across 3.1.0-3.11.0.