godpowers 2.2.0 → 2.3.0

package/CHANGELOG.md

@@ -7,6 +7,43 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [2.3.0] - 2026-05-30
+
+### Added
+- Added source-grounded planning helpers so build plans can name existing files,
+  existing symbols, planned new artifacts, and unchecked references before
+  execution begins.
+- Added package legitimacy checks for package-backed stack and dependency
+  replacement decisions, covering npm existence, typo risk, staleness, and
+  repository metadata.
+- Added role-based installer profiles (`core`, `builder`, `maintainer`,
+  `suite`, and `full`) plus `--minimal` as a compact alias for the core
+  surface.
+- Added atomic file-write helpers and wired them into state, checkpoint,
+  requirements, linkage, source-sync, reverse-sync, and async filesystem
+  persistence paths.
+- Added executor repair classification for retry, decomposition, pruning, and
+  escalation so failed implementation attempts leave clearer next actions.
+
+### Changed
+- Debranded legacy planning-system wording across public docs, runtime
+  detection, fixtures, tests, and sync-back surfaces to keep Godpowers distinct
+  from external workflow products.
+- Build, executor, planner, spec-reviewer, stack-selector, and dependency
+  auditor contracts now require source grounding or package legitimacy evidence
+  where those checks apply.
+
+## [2.2.1] - 2026-05-30
+
+### Fixed
+- Made `.godpowers/REQUIREMENTS.md` stable on no-op regenerations by ignoring
+  generated timestamp-only changes and removing the extra blank line at EOF.
+- Persisted reverse-sync deliverable summaries into `state.json.deliverables`,
+  matching the documented `/god-sync` and reverse-sync behavior.
+- Reconciled the Godpowers self-ledger so the shipped deliverable-progress
+  feature is marked done in `.godpowers/roadmap/ROADMAP.md`,
+  `.godpowers/REQUIREMENTS.md`, and `.godpowers/state.json`.
+
 ## [2.2.0] - 2026-05-30
 
 ### Added
@@ -312,7 +349,7 @@ Dogfooding, host guarantees, extension authoring, and suite release dry-runs.
 ### Added
 - Added `lib/dogfood-runner.js`, `/god-dogfood`, and `npx godpowers dogfood`
   for deterministic messy-repo dogfood scenarios.
-- Added `fixtures/dogfood/` scenarios for half-migrated GSD import,
+- Added `fixtures/dogfood/` scenarios for half-migrated legacy planning import,
   degraded and full host guarantees, extension scaffolding, and Mode D suite
   release dry-run planning.
 - Added `lib/host-capabilities.js` and dashboard host guarantee reporting for
@@ -488,7 +525,7 @@ Feature awareness for existing Godpowers projects.
 Planning-system migration and sync-back.
 
 ### Added
-- Added `lib/planning-systems.js` to detect GSD, BMAD, and Superpowers
+- Added `lib/planning-systems.js` to detect legacy planning, BMAD, and Superpowers
   planning context and convert useful signals into Godpowers prep and seed
   artifacts.
 - Added `lib/source-sync.js` to write current Godpowers progress back into
@@ -498,11 +535,11 @@ Planning-system migration and sync-back.
   ambiguous.
 - Added `docs/planning-system-migration.md` with detection signals, import
   mapping, sync-back destinations, conflict rules, and return-path guidance.
-- Added behavioral tests for GSD, BMAD, Superpowers, imported seed artifacts,
+- Added behavioral tests for legacy planning, BMAD, Superpowers, imported seed artifacts,
   state recording, and idempotent sync-back.
 
 ### Changed
-- `/god-init` now auto-invokes planning-system import when GSD, BMAD, or
+- `/god-init` now auto-invokes planning-system import when legacy planning, BMAD, or
   Superpowers evidence is detected.
 - `/god-sync` now auto-invokes source-system sync-back when `state.json`
   records enabled source systems.
@@ -697,7 +734,7 @@ of leaving the user to infer the next action.
   `/god-roadmap-check`.
 
 ### Changed
-- Proposal-style outputs now mirror the clearer GSD pattern: implement a small
+- Proposal-style outputs now mirror the clearer legacy planning pattern: implement a small
   slice, implement the full route, discuss more, inspect status, or run
   `/god-mode` only when that is safe.
 - `/god-next` and `/god-status` now explicitly distinguish partial progress,
@@ -1223,7 +1260,7 @@ routing, or the full autonomous arc starts.
 ### Documented
 - The full recent init preparation flow is now documented together:
   automatic AI-tool context for explicit `god init`, quiet context writes,
-  GSD / Superpowers / BMAD import into `IMPORTED-CONTEXT.md`, and direct
+  legacy planning / Superpowers / BMAD import into `IMPORTED-CONTEXT.md`, and direct
   Godpowers repo findings in `INITIAL-FINDINGS.md`.
 
 ## [0.15.7] - 2026-05-11
@@ -1232,7 +1269,7 @@ Planning import release. Lets `/god-init` preserve useful context from nearby
 planning systems without making those systems authoritative.
 
 ### Added
-- `/god-init` now detects GSD, Superpowers, BMAD, and similar planning context
+- `/god-init` now detects legacy planning, Superpowers, BMAD, and similar planning context
   during project preparation.
 - Added `.godpowers/prep/IMPORTED-CONTEXT.md` as a non-authoritative
   preparation artifact for imported product, delivery, architecture, and stack

package/INSPIRATION.md

@@ -7,7 +7,9 @@
 Godpowers was shaped by ideas from several existing AI coding workflow
 systems. The four direct ancestors were:
 
-- **GSD** by Hanns Princivil ([github.com/aihxp/gsd](https://github.com/aihxp/gsd)) - pure-skill model, slash commands inside AI tools, TDD enforcement, critical-finding gate with autonomous-mode carve-out
+- **Prior internal planning-system experiments** - pure-skill model, slash
+  commands inside AI tools, TDD enforcement, critical-finding gate with
+  autonomous-mode carve-out
 - **Superpowers** by Anthropic ([github.com/anthropics/skills](https://github.com/anthropics/skills)) - subagent specialization with strict hand-off contracts, fresh-context isolation, two-stage review pipelines
 - **BMAD-METHOD** ([github.com/bmad-code-org/BMAD-METHOD](https://github.com/bmad-code-org/BMAD-METHOD)) - story-file workflow for incremental delivery, multi-phase methodology
 - **arc-ready / arc-anything** - artifact-quality discipline (substitution test, three-label test, named have-nots catalog)
@@ -35,7 +37,7 @@ Beyond what was inherited, godpowers added:
   AGENTS.md / CLAUDE.md / GEMINI.md and 11 other tool-specific paths
 - **Feature awareness and host guarantee reporting** so existing projects and
   AI coding hosts can state what Godpowers capabilities are actually available
-- **Messy-repo dogfood fixtures** for GSD migration, sync-back, extension
+- **Messy-repo dogfood fixtures** for legacy planning migration, sync-back, extension
   authoring, host capability, and Mode D suite release dry-run behavior
 - **Autonomous repo documentation and surface sync** for badges, route
   metadata, recipes, package payloads, release gates, and extension packs

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-2.2.0-blue)](CHANGELOG.md)
+[![Version](https://img.shields.io/badge/version-2.3.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.**
@@ -21,14 +21,12 @@ 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.2.0 keeps 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
-2.0 line also ships a proof transcript, adoption canary harness, published npm
-install verifier, package checks that require the proof fixture to ship, and
-request-trace review guardrails for narrower implementation diffs. The 2.0.2
-release also hardens the dependency-free YAML subset, route file checks,
-installer file copying, and maintainer release gates.
+Version 2.3.0 keeps the proof loop executable and adds accountability
+hardening. Build plans can now be checked against real repository files and
+symbols before execution, package-backed stack choices can be screened for
+legitimacy, core ledger writes use atomic persistence, installer profiles let
+teams choose a smaller command surface, and failed executor attempts leave a
+clear repair classification.
 
 Maintainer hardening continues on the 2.x line without expanding the public
 command surface. The 2.1.0 patch closes a command-injection vector in the
@@ -78,6 +76,8 @@ should prove:
 - 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.
+- Build plans cite real files and symbols before execution starts.
+- New dependencies have registry and legitimacy evidence before they enter the stack.
 
 ## Install
 
@@ -96,6 +96,19 @@ The installer copies:
 - Codex agent metadata to `<runtime>/agents/*.toml`
 - SessionStart hook (Claude Code only) to `<runtime>/hooks/`
 
+Installer profiles keep the visible command surface calm:
+
+```bash
+npx godpowers --claude --global --profile=core
+npx godpowers --codex --local --profile=builder
+npx godpowers --all --profile=maintainer
+```
+
+Profiles are `core`, `builder`, `maintainer`, `suite`, and `full`. `full`
+preserves the complete command surface, while the smaller profiles install the
+commands most relevant to the role. `--minimal` is an alias for
+`--profile=core`.
+
 Agent spawning is host-native. Claude uses its native agent/task interface,
 Codex uses installed `agents/*.toml` metadata backed by the same Markdown agent
 contracts, and the other runtimes use their supported agent or subagent
@@ -240,7 +253,7 @@ extension files, with parser coverage in `scripts/test-yaml-parser.js`.
 | `/god-automation-status` | Show host automation provider support | (built-in) |
 | `/god-automation-setup` | Prepare opt-in automation setup | (built-in) |
 | `/god-dogfood` | Run messy-repo dogfood scenarios for release and autonomy readiness | (built-in) |
-| `/god-migrate` | Detect GSD, BMAD, and Superpowers context; import and sync back | god-greenfieldifier when needed |
+| `/god-migrate` | Detect legacy planning, BMAD, and Superpowers context; import and sync back | god-greenfieldifier when needed |
 | `/god-preflight` | Read-only intake audit before project-run readiness and pillars | god-auditor |
 | `/god-audit` | Score artifacts against have-nots | god-auditor |
 | `/god-debug` | 4-phase systematic debug | god-debugger |
@@ -327,7 +340,7 @@ Godpowers can dogfood itself against shipped messy-repo fixtures:
 npx godpowers dogfood
 ```
 
-The dogfood suite covers a half-migrated GSD project, full and degraded host
+The dogfood suite covers a half-migrated legacy planning project, full and degraded host
 guarantee detection, extension scaffold validation, and a Mode D suite release
 dry-run. `/god-dogfood` reports failures with scoped specialist ownership
 rather than treating fixture checks as silent background work.
@@ -343,7 +356,7 @@ Godpowers can migrate from adjacent planning systems:
 /god-migrate
 ```
 
-This detects GSD `.planning/` or `.gsd/`, BMAD `_bmad-output/` or `.bmad/`,
+This detects legacy planning `.planning/` or `.legacy-planning/`, BMAD `_bmad-output/` or `.bmad/`,
 and Superpowers specs or plans. It writes
 `.godpowers/prep/IMPORTED-CONTEXT.md`, optional imported seed artifacts, and
 managed sync-back files such as `.planning/GODPOWERS-SYNC.md`,

package/RELEASE.md

@@ -1,11 +1,12 @@
-# Godpowers 2.2.0 Release
+# Godpowers 2.3.0 Release
 
 > Status: Ready for release
 > Date: 2026-05-30
 
-Godpowers 2.2.0 adds deliverable progress tracking on top of the 2.1.1
-documentation and off-switch safety patch. It keeps the public slash-command
-surface stable and backward compatible.
+Godpowers 2.3.0 is an accountability-hardening release for the 2.x line. It
+keeps the public slash-command surface stable while strengthening planning
+grounding, package legitimacy, install profiles, atomic persistence, and
+executor recovery.
 
 ## What's in this release
 
@@ -16,23 +17,18 @@ surface stable and backward compatible.
 
 ## Highlights
 
-- Deliverable progress tracking: the new `/god-progress` command and the
-  `.godpowers/REQUIREMENTS.md` ledger report which PRD requirements and roadmap
-  increments are done, in progress, or not started. Status is derived from the
-  linkage map by `lib/requirements.js`, so it cannot drift from the code that is
-  actually implemented.
-- Stable requirement and increment ids: PRD requirements carry
-  `P-MUST-NN`/`P-SHOULD-NN`/`P-COULD-NN`, and ROADMAP increments carry `M-slug`
-  ids with a per-increment `Status` and member requirement ids.
-- The build chain populates the ledger during real runs: `god-planner` names the
-  requirement ids each slice delivers, `god-executor` stamps `// Implements: P-...`
-  annotations, and the spec and quality reviewers verify them.
-- The dashboard (`/god-status`, `/god-next`, `/god-mode` closeout) gains a
-  `Deliverable progress` section, and a `whats-done` recipe routes natural
-  language like "how far along are we" to `/god-progress`.
-- Documentation reconciled with the shipped surface and version: accurate
-  counts and `/god-progress`/`REQUIREMENTS.md` awareness across README,
-  ARCHITECTURE, reference, linkage, recipes, and the artifact inventories.
+- Source-grounded planning records existing files, existing symbols, planned new
+  artifacts, and unchecked references before build execution.
+- Package legitimacy checks give stack and dependency decisions a concrete npm
+  evidence gate before recommending package-backed choices.
+- Installer profiles let users install a smaller role-based command surface
+  with `--profile=<name>` or `--minimal`.
+- Atomic write helpers now protect core state and ledger writes from partial
+  file updates.
+- Executor repair classification names whether a failed attempt should retry,
+  decompose, prune, or escalate.
+- Public migration language now uses neutral legacy-planning terminology so
+  Godpowers is not confused with external workflow products.
 
 ## Validation
 
@@ -42,14 +38,14 @@ surface stable and backward compatible.
 
 ## Upgrade
 
-- `npm install -g godpowers@2.2.0` or `npx godpowers@2.2.0`
+- `npm install -g godpowers@2.3.0` or `npx godpowers@2.3.0`
 - Re-run `/god-context` in each project to refresh installed runtime metadata
-- No breaking changes; existing `.godpowers/` state is compatible. Projects gain
-  a `REQUIREMENTS.md` ledger the next time `/god-progress` or `/god-sync` runs.
+- No breaking changes; existing `.godpowers/` state is compatible. Users who
+  want a compact install can run `npx godpowers --profile=core`.
 
 ## Notes
 
-- GitHub release creation for `v2.2.0`
+- GitHub release creation for `v2.3.0`
 - The tag should match the npm package version
-- The `v2.2.0` tag should point to the release commit that matches the npm
-  `godpowers@2.2.0` package.
+- The `v2.3.0` tag should point to the release commit that matches the npm
+  `godpowers@2.3.0` package.

package/SKILL.md

@@ -297,7 +297,7 @@ Run these local runtime helpers automatically when their trigger is present:
   `PROGRESS.md` mutation.
 - Lightweight reverse-sync or linkage scan after code or artifact edits.
 - Pillars sync planning after durable artifact truth changes.
-- `lib/planning-systems.importPlanningContext` when GSD, BMAD, or
+- `lib/planning-systems.importPlanningContext` when legacy planning, BMAD, or
   Superpowers planning context is detected during `/god-init` or
   `/god-migrate`.
 - `lib/source-sync.run` when `state.json` records enabled `source-systems`
@@ -351,7 +351,7 @@ Spawn these agents only when the trigger is direct and scope is bounded:
 - `god-automation-engineer` after the user approves provider, template,
   cadence, and scope for multi-template, write-capable, background-agent,
   scriptable-scheduler, or provider-uncertain automation setup.
-- `god-greenfieldifier` when imported GSD, BMAD, or Superpowers context has
+- `god-greenfieldifier` when imported legacy planning, BMAD, or Superpowers context has
   low confidence, conflicting systems, or missing canonical Godpowers seed
   artifacts after local import.
 - `god-greenfieldifier` when feature-awareness detects unimported or imported

package/agents/god-auditor.md

@@ -250,7 +250,7 @@ Mode: [brownfield | bluefield]
 - This audit does not rewrite artifacts.
 - This audit must be followed by `god-greenfieldifier` in brownfield and
   bluefield workflows when the user wants the audit acted on.
-- This audit does not treat imported GSD, Superpowers, BMAD, or org context as
+- This audit does not treat imported legacy planning, Superpowers, BMAD, or org context as
   source of truth.
 - This audit does not block the project run unless it finds a Critical security or
   impossible planning contradiction.

package/agents/god-deps-auditor.md

@@ -31,6 +31,15 @@ For each dependency, classify:
 - **Minor behind**: only minor/patch updates available
 - **Up to date**: no action needed
 
+For each new replacement candidate, run the package legitimacy gate before
+recommending it:
+- Registry existence
+- Package age and recent publish signal
+- Repository URL
+- Maintainer or ownership signal when visible
+- Typo-squat similarity to better-known packages
+- Known vulnerability status where available
+
 ### 2. Triage
 
 Priority order:
@@ -109,3 +118,5 @@ Deps audit FAILS if:
 - Changelog not consulted (so breaking changes unknown)
 - Lockfile not committed alongside package.json
 - Bulk update without per-package commits (loses bisect-ability)
+- Replacement package recommended without legitimacy evidence or accepted-risk
+  note

package/agents/god-executor.md

@@ -22,6 +22,8 @@ You receive:
 - The slice's dependencies (what must already exist)
 - Optional repair payload: failing command, error counts, focused diagnostics,
   and files implicated by a previous verification run
+- Optional source-grounding report: pass/fail status for existing files and
+  symbols cited by the slice plan
 
 ## TDD Sequence (mandatory)
 
@@ -73,6 +75,14 @@ requirement as "not started" even after you ship it.
 - **Unrelated cleanup**: VIOLATION. Do not reformat, rename, refactor, or
   delete adjacent code that is not required for this slice. Mention it as a
   follow-up instead.
+- **Ungrounded existing references**: VIOLATION. Do not implement against a
+  file, symbol, route, or API that the source-grounding preflight failed to
+  locate unless the plan explicitly declares it as a new artifact or the user
+  accepted it as unchecked risk.
+- **Unverified new dependency**: VIOLATION. Before installing or adding a new
+  third-party package, run the package legitimacy gate from
+  `lib/package-legitimacy.js` or record why network verification was unavailable
+  and who accepted the risk.
 
 ## Request Trace Discipline
 
@@ -122,8 +132,15 @@ happen.
 
 ## Repair Mode
 
-If invoked with a repair payload, stay narrowly focused on the failing command.
-Do not reopen PRD, ARCH, roadmap, or stack unless the diagnostic proves the
-artifact is stale. Fix code, config, imports, tests, generated types, or
-tooling until the command passes. If the same root failure survives 3 focused
-attempts, return the smallest human-only question needed to continue.
+If invoked with a repair payload, classify the failure before editing:
+
+| Strategy | Use when | Action |
+|---|---|---|
+| retry | The approach is right but a command, import, path, dependency, timeout, or environment failed | Make one focused adjustment and rerun the exact verification |
+| decompose | The task is too broad or the done criteria combines multiple outcomes | Split into at most 3 smaller verified steps for this run |
+| prune | A task is infeasible in this slice because a prerequisite is missing or out of scope | Skip only with a recorded reason and a downstream review marker |
+| escalate | The repair budget is exhausted or the fix changes architecture, product behavior, or user intent | Stop and return the smallest human-only decision needed |
+
+Log every repair decision in the slice closeout as
+`[Executor Repair - STRATEGY] task: reason`. Do not reopen PRD, ARCH, roadmap,
+or stack unless the diagnostic proves the artifact is stale.

package/agents/god-greenfieldifier.md

@@ -137,7 +137,7 @@ After approved rewrites:
 
 ## Rules
 
-- Imported GSD, Superpowers, BMAD, org context, and reconstructed artifacts are
+- Imported legacy planning, Superpowers, BMAD, org context, and reconstructed artifacts are
   evidence, not source of truth.
 - Never erase existing specific evidence to replace it with a generic
   greenfield default.

package/agents/god-orchestrator.md

@@ -161,7 +161,7 @@ Before each tier, check whether this repo is part of a registered suite:
 
 ## Planning-system context import
 
-During `/god-init`, scan for adjacent methodology artifacts from GSD,
+During `/god-init`, scan for adjacent methodology artifacts from legacy planning,
 Superpowers, BMAD, and similar systems. Treat them as preparation context,
 not as source of truth.
 
@@ -210,7 +210,7 @@ conflicts with user intent, state.json, PROGRESS.md, or completed Godpowers
 artifacts, the Godpowers artifact wins.
 
 Detection signals:
-- GSD: `.gsd/`, `.planning/`, `GSD.md`, `gsd*.md`
+- legacy planning: `.legacy-planning/`, `.planning/`, `LEGACY-PLANNING.md`, `legacy-planning*.md`
 - Superpowers: `.superpowers/`, `superpowers/`, `SUPERPOWERS.md`,
   `.claude/skills/`, `.codex/skills/`
 - BMAD: `.bmad-core/`, `bmad-core/`, `.bmad/`, `BMAD.md`,

package/agents/god-planner.md

@@ -35,6 +35,12 @@ Plan the build.
    - **Slice name**: user-visible behavior
    - **Requirements**: the PRD requirement ids this slice delivers (so the
      executor can annotate the code and the deliverable ledger can trace it)
+   - **Source grounding**:
+     - Existing files this slice depends on
+     - Existing symbols, functions, classes, routes, commands, or APIs this
+       slice depends on
+     - New artifacts this slice will create
+     - Unchecked references that need human acceptance before execution
    - **Files to create/modify**: exact paths
    - **Tests to write FIRST**: with expected behavior
    - **Implementation steps**: ordered
@@ -55,6 +61,11 @@ Write `.godpowers/build/PLAN.md`:
 ## Wave 1 (parallel)
 ### Slice 1.1: User can create an account
 - Requirements: P-MUST-01
+- Source grounding:
+  - Existing files: src/auth/index.ts
+  - Existing symbols: createSession
+  - New artifacts: src/auth/signup.ts, src/auth/signup.test.ts
+  - Unchecked references: none
 - Files: src/auth/signup.ts, src/auth/signup.test.ts, src/db/users.ts
 - Tests first:
   - signup_creates_user_record
@@ -76,6 +87,9 @@ Write `.godpowers/build/PLAN.md`:
 - `.godpowers/build/PLAN.md` exists
 - Every slice has tests-first sequence
 - Every slice names the PRD requirement ids it delivers
+- Every slice separates existing references from new artifacts
+- Every existing reference is grounded by `lib/source-grounding.js` before
+  execution
 - Every member requirement id of the increment is covered by at least one slice
 - Every slice has verification criteria
 - Dependencies are explicit

package/agents/god-pm.md

@@ -62,7 +62,7 @@ reflects what Godpowers observed during init: codebase shape, tests, docs,
 risks, and methodology systems detected.
 
 If `.godpowers/prep/IMPORTED-CONTEXT.md` exists, read it before drafting the
-PRD. Use product signals from GSD, Superpowers, BMAD, or similar systems as
+PRD. Use product signals from legacy planning, Superpowers, BMAD, or similar systems as
 hypothesis-level input only.
 
 If `.godpowers/domain/GLOSSARY.md` exists, read it before drafting the PRD.

package/agents/god-reconciler.md

@@ -144,7 +144,7 @@ For each artifact below, check (in parallel where possible):
 - If imported planning systems have low confidence or conflicts: recommend
   `god-greenfieldifier`.
 
-#### SOURCE SYSTEM SYNC-BACK (GSD, BMAD, Superpowers)
+#### SOURCE SYSTEM SYNC-BACK (legacy planning, BMAD, Superpowers)
 - Did migrated source-system summaries need managed sync-back?
 - Verdict: not-applicable / fresh / needs-sync-back / blocked-by-conflict
 - If conflicts exist: recommend greenfieldifier review before writes.

package/agents/god-roadmapper.md

@@ -36,7 +36,7 @@ If `.godpowers/prep/INITIAL-FINDINGS.md` exists, read it first for repo risks,
 existing tests, docs, CI, deploy, and suggested sequencing implications.
 
 If `.godpowers/prep/IMPORTED-CONTEXT.md` exists, read its delivery signals
-before sequencing work. Use imported GSD, Superpowers, BMAD, or similar
+before sequencing work. Use imported legacy planning, Superpowers, BMAD, or similar
 stories and plans as hypothesis-level input only. Convert imported terminology
 into Godpowers vocabulary. Do not preserve imported methodology terminology in
 Godpowers artifacts unless the user explicitly asked for it.

package/agents/god-spec-reviewer.md

@@ -57,6 +57,14 @@ Answer each with EVIDENCE from the code:
    - A planned requirement id with no annotation is a finding, because the
      deliverable ledger derives requirement status from those annotations.
 
+7. **Did the implementation honor source grounding and package legitimacy?**
+   - Did every existing file or symbol cited by the slice plan exist before
+     execution?
+   - Did new files appear only under the plan's new artifacts or expected file
+     list?
+   - If the slice added a dependency, is there package legitimacy evidence or
+     an explicit accepted-risk note?
+
 ## Output
 
 Return verdict to orchestrator:
@@ -83,6 +91,8 @@ Return verdict to orchestrator:
 - Every touched file has request-trace evidence
 - No speculative flexibility or unrelated cleanup entered the diff
 - Every planned requirement id carries its `// Implements: P-...` annotation
+- Source-grounding failures are resolved or explicitly accepted
+- New dependencies have legitimacy evidence or accepted-risk notes
 
 If FAIL: orchestrator returns the slice to god-executor with the failures.
 If PASS: orchestrator spawns god-quality-reviewer next.

package/agents/god-stack-selector.md

@@ -65,6 +65,9 @@ Rules:
 3. For each category:
    - List 2-3 viable candidates
    - Score on: fit-for-requirements, maturity, ecosystem health, team familiarity, total cost
+   - For package-backed choices, run or request the package legitimacy gate:
+     registry existence, package age, repository signal, maintainer signal,
+     typo-squat risk, and known vulnerability status where available
    - Document the **flip point**: condition under which you'd reverse this choice
    - Document the **lock-in cost**: how hard is it to switch (Low/Medium/High)
 4. Verify pairing compatibility (e.g., chosen ORM works with chosen DB)
@@ -103,6 +106,7 @@ Stack DECISION FAILS if:
 - High lock-in choice with likely flip point in <6 months
 - Pairing incompatibility (chosen ORM doesn't support chosen DB, etc.)
 - "Best practice" rationale without specific rationale tied to ARCH
+- Package-backed choice without legitimacy evidence or an accepted-risk note
 
 ## Pause Conditions
 

package/agents/god-updater.md

@@ -174,7 +174,7 @@ After feature work, every artifact that was impacted needs to reflect reality.
 
 ### Source-system sync-back
 - Call `lib/source-sync.run(projectRoot)` when `.godpowers/state.json`
-  declares GSD, BMAD, Superpowers, or other source-system records.
+  declares legacy planning, BMAD, Superpowers, or other source-system records.
 - Write only managed Godpowers summary sections back to source systems.
 - Preserve user-authored source-system content outside managed sections.
 - If source-system confidence is low or conflicts are present, recommend

package/bin/install.js

@@ -17,8 +17,10 @@ const {
   uninstallForRuntime,
   countInstalledSurface
 } = require('../lib/installer-core');
+const { describeProfiles } = require('../lib/install-profiles');
+const identity = require('../lib/package-identity');
 
-const VERSION = require('../package.json').version;
+const VERSION = identity.PACKAGE_VERSION;
 
 const BANNER = `
   GODPOWERS v${VERSION}
@@ -80,6 +82,8 @@ function showHelp() {
   log('  --codebuddy          Install for CodeBuddy');
   log('  --pi                 Install for Pi');
   log('  --all                Install for all 15 runtimes');
+  log('  --profile=<name>     Install profile: core, builder, maintainer, suite, or full');
+  log('  --minimal            Alias for --profile=core');
   log('  -u, --uninstall      Uninstall Godpowers');
   log('  -h, --help           Show this help message');
   log('');
@@ -92,6 +96,7 @@ function showHelp() {
   log('  npx godpowers dogfood');
   log('  npx godpowers extension-scaffold --name=@godpowers/my-pack --output=.');
   log('  npx godpowers --claude --global');
+  log('  npx godpowers --claude --global --profile=core');
   log('  npx godpowers --all');
   log('  npx godpowers --codex --cursor');
 }
@@ -243,10 +248,11 @@ function runInstall(opts, srcDir) {
     process.exit(1);
   }
 
-  const surface = countInstalledSurface(srcDir);
+  const surface = countInstalledSurface(srcDir, opts);
   log('');
   log(`\x1b[32mDone!\x1b[0m Installed Godpowers v${VERSION} for ${installed} runtime(s).`);
   log('');
+  log(`\x1b[36mProfile:\x1b[0m ${describeProfiles(opts.profile)}`);
   log(`\x1b[36mInstalled:\x1b[0m`);
   log(`  ${surface.skills} slash commands (try: /god-mode, /god-next, /god-status, /god-progress)`);
   log(`  ${surface.agents} specialist agents`);
@@ -258,7 +264,7 @@ function runInstall(opts, srcDir) {
   log(`     Or:   \x1b[36m/god-next\x1b[0m to see what to run next`);
   log(`     Or:   \x1b[36m/god-init\x1b[0m to start a new project`);
   log('');
-  log(`\x1b[36mDocs:\x1b[0m https://github.com/godpowers/godpowers`);
+  log(`\x1b[36mDocs:\x1b[0m ${identity.HOMEPAGE_URL}`);
   log('');
 }
 

package/fixtures/dogfood/{half-migrated-gsd → half-migrated-planning}/manifest.json

@@ -1,12 +1,12 @@
 {
-  "name": "Half migrated GSD project",
+  "name": "Half migrated planning project",
   "kind": "planning-migration",
   "actions": [
     "import-planning-context",
     "sync-back"
   ],
   "expectedSystems": [
-    "gsd"
+    "legacy-planning"
   ],
   "expectedFiles": [
     ".godpowers/prep/IMPORTED-CONTEXT.md",