godpowers 0.15.10 → 0.15.12

package/CHANGELOG.md

@@ -5,6 +5,34 @@ All notable changes to Godpowers will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.15.12] - 2026-05-11
+
+Shipping closure release. Prevents `/god-mode --yolo` from stopping with broad
+staging/provider checklists.
+
+### Changed
+- Added a Shipping Closure Protocol for deploy, observe, harden, and launch:
+  verify a real environment when reachable, otherwise create local or
+  CI-verifiable automation, then pause only for one exact external access
+  bundle.
+- Deploy, observability, and launch agents now treat missing provider access as
+  `waiting-for-external-access` with a concrete artifact instead of a generic
+  next-step checklist.
+- Full-arc workflow metadata now records closure behavior for missing external
+  access.
+
+## [0.15.11] - 2026-05-11
+
+God Mode resume release. Fixes `/god-mode --yolo` prompting for a project
+description when durable Godpowers state already exists.
+
+### Changed
+- `/god-mode` now treats existing `.godpowers` state as a resume signal and
+  rehydrates intent from checkpoint, state, progress, intent, prep, and tier
+  artifacts before asking the user anything.
+- The orchestrator now documents that asking "what do you want to build?" in a
+  brownfield repo with existing Godpowers artifacts is a routing bug.
+
 ## [0.15.10] - 2026-05-11
 
 God Mode continuity release. Makes red verification output repair work inside

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-0.15.10-blue)](CHANGELOG.md)
+[![Version](https://img.shields.io/badge/version-0.15.12-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.**
@@ -153,6 +153,9 @@ going through build, verification, repair, launch, and final sync. Red tests,
 typecheck, lint, build, or check output enter the repair loop instead of being
 reported as the final result.
 
+If `.godpowers` state already exists, `/god-mode --yolo` resumes from disk
+instead of asking for the project description again.
+
 ## Architecture
 
 ### Slash Command + Specialist Agent Pattern

package/agents/god-deploy-engineer.md

@@ -20,7 +20,13 @@ Build is complete. All tests pass. `.godpowers/build/STATE.md` shows green.
 
 1. Read ARCH for deployment topology
 2. Read stack DECISION for hosting/CI choices
-3. Configure pipeline:
+3. Detect what can be verified now:
+   - real staging or production URL and credentials
+   - local staging harness or mock provider harness
+   - CI provider and deploy scripts
+   - provider CLIs, env files, Docker files, reverse proxy config, database,
+     backup, and restore scripts
+4. Configure pipeline:
 
 ### Same-Artifact Promotion
 - Build the artifact ONCE (Docker image, binary, bundle)
@@ -49,6 +55,18 @@ Build is complete. All tests pass. `.godpowers/build/STATE.md` shows green.
 - Post-deploy smoke test that hits real endpoints
 - Fails the deploy if smoke test fails (auto-rollback)
 
+### External Access Closure
+- If real staging is reachable, run the real smoke and rollback checks.
+- If real staging is not reachable, build the closest local staging harness and
+  run the same smoke command against it.
+- If provider credentials, DNS, TLS, dashboard access, or production secrets are
+  missing, write `.godpowers/deploy/WAITING-FOR-EXTERNAL-ACCESS.md`.
+- That file must contain one smallest access bundle, exact env var names,
+  exact dashboard/provider links or placeholders, and the command Godpowers will
+  run after access exists.
+- Do not return a broad checklist as the final answer. Either return tested
+  deploy readiness or the one access bundle.
+
 ## Output
 
 Write `.godpowers/deploy/STATE.md`:
@@ -85,3 +103,5 @@ Write `.godpowers/deploy/STATE.md`:
 - Health check is TCP-only
 - No smoke tests
 - Paper canary (label without traffic split)
+- Broad provider checklist with no scripts or exact access bundle
+- Marks deploy done when the only verified target is missing

package/agents/god-launch-strategist.md

@@ -65,6 +65,18 @@ For each channel:
 - D+1 to D+3: respond to all comments, gather feedback
 - D+7: post-launch retrospective
 
+### 6. Shipping Closure
+- Read `.godpowers/deploy/STATE.md`,
+  `.godpowers/deploy/WAITING-FOR-EXTERNAL-ACCESS.md` if present, and
+  `.godpowers/observe/STATE.md`.
+- If deploy or observe is waiting on external access, do not create a broad
+  dashboard checklist. Reference the single waiting access bundle and write
+  launch state as `waiting-for-external-access`.
+- If a staging or production URL is available, run or specify the exact smoke
+  command and record the result.
+- If only local staging is available, run local launch-readiness checks and
+  clearly label scope as local readiness, not live launch.
+
 ## Output
 
 Write `.godpowers/launch/STATE.md` with all artifacts.
@@ -78,6 +90,8 @@ Write `.godpowers/launch/STATE.md` with all artifacts.
 - Launch with no source attribution
 - No D+1 to D+7 follow-up plan
 - "We'll figure out marketing later"
+- Broad provider checklist instead of one exact external access bundle
+- Declares live launch without a verified live target
 
 ## Pause Conditions
 

package/agents/god-observability-engineer.md

@@ -15,7 +15,9 @@ Wire observability.
 
 ## Gate Check
 
-`.godpowers/deploy/STATE.md` exists. App is deployed and reachable.
+`.godpowers/deploy/STATE.md` exists. App is deployed and reachable, or deploy
+state documents a tested local staging harness plus a single external access
+bundle.
 
 ## Process
 
@@ -57,6 +59,16 @@ For each PRD success metric, define an SLO:
 - No "vanity metrics" dashboards
 - Top-level dashboard shows SLO status at a glance
 
+### 7. External Access Closure
+- If the observability provider is reachable, create or verify the real alerts,
+  dashboards, and runbooks.
+- If the provider is not reachable, create provider-neutral dashboard and alert
+  definitions as code when possible.
+- If dashboard/API credentials are missing, append them to the single waiting
+  access bundle instead of returning a broad checklist.
+- Under `/god-mode --yolo`, continue through every local or CI-verifiable
+  observability check before pausing for external access.
+
 ## Output
 
 Write `.godpowers/observe/STATE.md` with:
@@ -74,3 +86,5 @@ Write `.godpowers/observe/STATE.md` with:
 - Dashboard not tied to an SLO
 - Sensitive data in log output
 - Alert with no runbook
+- Broad dashboard checklist instead of definitions as code or one exact access
+  bundle

package/agents/god-orchestrator.md

@@ -324,6 +324,37 @@ after tests pass. If a git remote exists and the user passed an explicit push
 flag or the project intent says pushing is allowed, push after the green commit
 and then continue the arc. Pushing is not a terminal state.
 
+## Shipping Closure Protocol
+
+The shipping tier must not end by listing a broad provider checklist. God Mode
+either ships, creates the automation needed to ship, or pauses on one precise
+external access bundle.
+
+For deploy, observe, harden, and launch:
+1. Detect the target environment from deploy config, org context, env files,
+   CI config, README, existing scripts, and provider CLIs.
+2. If a real staging or production target is reachable, run the real smoke,
+   rollback, health, observability, and launch checks against it.
+3. If no real target is reachable but the stack can run locally, create or
+   update a local staging harness that exercises the same routes, health
+   checks, smoke checks, and launch gates. Run it.
+4. If provider credentials, DNS, TLS, dashboards, or production secrets are
+   missing, create the missing automation and documentation first:
+   - scripts for deploy, smoke, rollback, health, backup, and restore
+   - env var manifest with exact variable names
+   - CI jobs or documented commands that call those scripts
+   - `.godpowers/deploy/WAITING-FOR-EXTERNAL-ACCESS.md` with the smallest
+     access bundle needed
+5. Under `--yolo`, auto-pick safe defaults for provider-neutral choices and
+   continue through every local and CI-verifiable gate.
+6. Only pause when real external access is required and absent. The pause must
+   ask for one concrete thing, such as "provide STAGING_URL and these 5 secrets"
+   or "confirm production DNS host and token." Do not output a long checklist
+   as the stopping condition.
+7. Do not say "Suggested next" for a blocked shipping tier. Say either
+   `Arc complete` or `PAUSE: external access required`, with the exact artifact
+   that lists the required bundle.
+
 ## YOLO Behavior with Design + Linkage
 
 | Concern | Default | --yolo |
@@ -567,10 +598,19 @@ Default: If you say "go", I'll pick [X] because [Y].
 ## Resume Protocol
 
 On every invocation:
-1. Read PROGRESS.md from disk (NEVER trust conversation memory)
-2. Scan ALL artifact paths to verify what actually exists
-3. If PROGRESS.md and disk disagree: disk wins. Repair PROGRESS.md.
-4. Continue from the first non-done sub-step
+1. Read `.godpowers/CHECKPOINT.md`, `.godpowers/state.json`,
+   `.godpowers/PROGRESS.md`, and `.godpowers/intent.yaml` from disk. NEVER
+   trust conversation memory.
+2. Scan ALL artifact paths to verify what actually exists.
+3. If durable state exists, do not ask the user to describe the project again.
+   Reconstruct intent from disk and continue.
+4. If PROGRESS.md and disk disagree: disk wins. Repair PROGRESS.md.
+5. Continue from the first non-done sub-step or the first red verification
+   step.
+
+Only ask "what do you want to build?" when no `.godpowers` state, no intent,
+no checkpoint, and no completed artifact exists. In a brownfield repo with
+existing Godpowers artifacts, asking that question is a routing bug.
 
 ## Mode Detection (Tier 0 setup)
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "godpowers",
-  "version": "0.15.10",
+  "version": "0.15.12",
   "description": "AI-powered development system: 104 slash commands and 38 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.",
   "bin": {
     "godpowers": "./bin/install.js"

package/skills/god-deploy.md

@@ -23,7 +23,15 @@ Spawn the **god-deploy-engineer** agent in a fresh context via Task tool.
 After god-deploy-engineer returns:
 1. Verify STATE.md exists on disk
 2. Verify rollback procedure has been tested (not paper-only)
-3. Update `.godpowers/PROGRESS.md`: Deploy status = done
+3. Verify the deploy path is one of:
+   - real staging or production target tested
+   - local staging harness tested with equivalent health, smoke, and rollback
+     commands
+   - paused on `.godpowers/deploy/WAITING-FOR-EXTERNAL-ACCESS.md` with one
+     exact missing access bundle
+4. Update `.godpowers/PROGRESS.md`: Deploy status = done only for a tested real
+   target or tested local staging harness. If external access is missing, mark
+   Deploy = waiting-for-external-access, not done.
 
 ## On Completion
 
@@ -33,6 +41,12 @@ Deploy pipeline complete: .godpowers/deploy/STATE.md
 Suggested next: /god-observe (wire SLOs, alerts, runbooks)
 ```
 
+Under `/god-mode --yolo`, do not stop with a provider checklist. Create or
+update the deploy scripts, smoke command, rollback command, health endpoints,
+env manifest, and local staging harness first. If real external access is still
+required, pause on the single access bundle in
+`.godpowers/deploy/WAITING-FOR-EXTERNAL-ACCESS.md`.
+
 
 ## Re-invocation contract
 

package/skills/god-launch.md

@@ -25,7 +25,13 @@ After god-launch-strategist returns:
 1. Verify STATE.md exists on disk
 2. Verify landing copy passes substitution test
 3. Verify OG cards rendered (not just meta tags)
-4. Update `.godpowers/PROGRESS.md`: Launch status = done
+4. Verify one of:
+   - launch target is live and smoke checked
+   - local launch-readiness harness passed and external access bundle is the
+     only missing item
+5. Update `.godpowers/PROGRESS.md`: Launch status = done only when live launch
+   or explicit local launch-readiness scope is complete. If external access is
+   missing, mark Launch = waiting-for-external-access.
 
 ## Pause Conditions
 
@@ -43,6 +49,11 @@ Suggested next: /god-audit (score all artifacts retrospectively)
 Or: /god-status (see the final state)
 ```
 
+Under `/god-mode --yolo`, do not stop by listing provider dashboards. Create
+the launch runbook, smoke command, source attribution plan, and local
+launch-readiness checks. If real launch is blocked by missing external access,
+pause on the single access bundle from deploy or launch state.
+
 
 ## Re-invocation contract
 

package/skills/god-mode.md

@@ -16,7 +16,15 @@ You are receiving a /god-mode invocation. Your job is to spawn the
 
 ## Process
 
-1. Greet the user briefly: "God Mode engaged. Describe what you want to build."
+1. Resolve whether this is a new arc or a resume:
+   - If `.godpowers/state.json`, `.godpowers/PROGRESS.md`, or
+     `.godpowers/CHECKPOINT.md` exists, this is a resume. Do not ask the user
+     to describe the project again. Rehydrate intent from disk and continue.
+   - If no durable Godpowers state exists and no project description was
+     supplied in the invocation, greet briefly: "God Mode engaged. Describe
+     what you want to build."
+   - If no durable state exists and the invocation includes a description, use
+     that description immediately.
 
 2. **Auto-detect project type in background** (no jargon to user):
    - Scan working directory for code presence (package.json, src/, etc.)
@@ -25,7 +33,22 @@ You are receiving a /god-mode invocation. Your job is to spawn the
    - Announce in plain English what was detected (see god-orchestrator
      "How to announce" section)
 
-3. Wait for the user's project description (any format).
+3. Load durable resume context before asking anything:
+   - `.godpowers/CHECKPOINT.md` first, when present
+   - `.godpowers/state.json`
+   - `.godpowers/PROGRESS.md`
+   - `.godpowers/intent.yaml`, when present
+   - `.godpowers/prep/INITIAL-FINDINGS.md`, when present
+   - `.godpowers/prep/IMPORTED-CONTEXT.md`, when present
+   - Existing tier artifacts on disk
+
+   If these files contain enough information to identify the project and next
+   unfinished or red step, continue automatically. If the only missing data is
+   a nice-to-have description, use a `[HYPOTHESIS]` from existing artifacts and
+   keep moving.
+
+   Ask for a description only when there is no durable intent, no completed
+   artifact, and no resumable state.
 
 4. Parse flags from the invocation:
    - `--yolo` (skip pauses, pick defaults)
@@ -43,9 +66,10 @@ You are receiving a /god-mode invocation. Your job is to spawn the
    - `--greenfield` (force greenfield, skip archaeology even if code exists)
 
 5. Spawn the **god-orchestrator** agent via Task tool with:
-   - The user's project description
+   - The user's project description, or durable intent recovered from disk
    - The detected mode (A/B/C/E)
    - The active flags
+   - Instruction that existing `.godpowers` state means resume, not prompt
    - Instruction to read `.godpowers/PROGRESS.md` from disk if it exists
    - Instruction to read `.godpowers/prep/INITIAL-FINDINGS.md` and
      `.godpowers/prep/IMPORTED-CONTEXT.md` if present before choosing the
@@ -57,6 +81,10 @@ You are receiving a /god-mode invocation. Your job is to spawn the
      not a completed arc. It must enter the autonomous repair loop and continue
      the same `/god-mode` run until green, except for Critical security or a
      genuine human-only decision.
+   - Instruction that deploy, observe, harden, and launch must follow the
+     Shipping Closure Protocol: verify a real environment when available,
+     otherwise create local/CI-verifiable deploy automation and pause only for
+     one exact external access bundle.
 
 6. Orchestrator runs the appropriate workflow:
    - Greenfield -> full-arc

package/skills/god-observe.md

@@ -23,7 +23,14 @@ After god-observability-engineer returns:
 1. Verify STATE.md exists on disk
 2. Verify each SLO has an error budget policy
 3. Verify each alert has a runbook
-4. Update `.godpowers/PROGRESS.md`: Observe status = done
+4. Verify provider work is one of:
+   - real provider alerts and dashboards verified
+   - provider-neutral definitions as code created and locally checked
+   - missing dashboard/API credentials appended to the single external access
+     bundle
+5. Update `.godpowers/PROGRESS.md`: Observe status = done only for verified
+   real provider config or local definitions as code. If external access is
+   missing, mark Observe = waiting-for-external-access.
 
 ## On Completion
 
@@ -33,6 +40,11 @@ Observability complete: .godpowers/observe/STATE.md
 Suggested next: /god-harden (adversarial security review, gates Launch)
 ```
 
+Under `/god-mode --yolo`, do not stop with a dashboard checklist. Create or
+update alert definitions, dashboard definitions, runbooks, and local checks
+first. If real provider access is still required, append the exact missing
+credentials to `.godpowers/deploy/WAITING-FOR-EXTERNAL-ACCESS.md`.
+
 
 ## Re-invocation contract
 

package/workflows/full-arc.yaml

@@ -66,6 +66,9 @@ jobs:
     tier: 3
     needs: build
     uses: god-deploy-engineer@^1.0.0
+    closure:
+      on-missing-external-access: create-waiting-access-bundle
+      local-verification-required: true
 
   observe:
     tier: 3
@@ -85,3 +88,6 @@ jobs:
     uses: god-launch-strategist@^1.0.0
     with:
       template: HARDEN-FINDINGS.md
+    closure:
+      no-broad-checklists: true
+      on-missing-external-access: pause-with-single-access-bundle