godpowers 2.0.0 → 2.1.1

package/skills/god-mode.md

@@ -161,272 +161,16 @@ workflow.
     create a new handoff file, then re-spawn god-orchestrator with only the
     display-safe pointer.
 
-## User-Visible Transcript Contract
+## Runbook Contracts
 
-The God Mode transcript is an operator console, not a prompt debugger.
+Detailed operator transcript rules, step cards, pause format, flag behavior, mandatory final sync, and completion templates live in `references/orchestration/GOD-MODE-RUNBOOK.md`.
 
-Show:
-- detected resume or project mode in plain language
-- a compact "Next step" card before each visible phase or tier sub-step
-- a compact "Step result" card after each visible phase or tier sub-step
-- every auto-invoked command, agent, and local runtime helper using an
-  `Auto-invoked:` or `Sync status:` card
-- plain-language workflow names. Say "project run" or "workflow" instead of
-  unexplained "arc" in visible output
-- PRD and roadmap visibility in status and closeout blocks when artifacts
-  exist or are expected
-- short progress updates for phases, commands, validations, and file edits
-- concise validation summaries instead of full command noise when possible
-- final changed paths, validation results, and completion or pause status
-- final Godpowers Dashboard from disk, including phase, tier, step, progress,
-  planning visibility, proactive checks, open items, worktree/index state, and
-  recommended next action
+When spawning `god-orchestrator`, include the runbook path in the private handoff file and instruct the orchestrator to follow it. Keep the visible spawn payload display-safe and never copy hidden handoff details into the transcript.
 
-Hide:
-- raw spawn input
-- "Hard instructions" sections
-- spawned-agent prompt text
-- detailed handoff file contents
-- system, developer, or AGENTS.md rule recitations
-- complete file loadout lists
-- internal routing metadata unless it directly affects a user decision
-
-If an internal instruction must influence a pause, translate it into the
-smallest user-facing question. For example, ask for
-`STAGING_APP_URL=<deployed staging origin>` at final sign-off instead of
-exposing the full Shipping Closure Protocol.
-
-## Step Cards
-
-Relay the orchestrator's step cards when present. If the orchestrator output is
-missing them, synthesize them from disk state before continuing.
-
-Before work starts:
-
-```text
-Next step
-Phase: <plain-language phase> (tier <human ordinal> of <human total>)
-Step: <sub-step-label>
-Progress: <pct>% (<done> of <total> steps complete; step <n> of <total>)
-Why this now: <one sentence>
-What will happen:
-  1. <observable action>
-  2. <observable action>
-Expected output: <artifact path or verification result>
-```
-
-After work completes or pauses:
-
-```text
-Step result
-Phase: <plain-language phase> (tier <human ordinal> of <human total>)
-Step: <sub-step-label>
-Progress: <pct>% (<done> of <total> steps complete; step <n> of <total>)
-Result: <done | blocked | failed | skipped | imported>
-What happened:
-  1. <observable action completed>
-  2. <artifact or verification result>
-Next: <next command or pause question>
-```
-
-## Pause Format (relay from orchestrator)
-
-```
-PAUSE: [one-sentence question]
-
-Why only you can answer: [one sentence]
-
-| Option | Tradeoff |
-|--------|----------|
-| A: ... | ... |
-| B: ... | ... |
-
-Default: If you say "go", I'll pick [X] because [Y].
-```
-
-## Flags
-
-### --yolo
-Pass through to orchestrator. Orchestrator picks defaults at every pause point
-and logs decisions to `.godpowers/YOLO-DECISIONS.md`. Pillar sync proposals
-generated from durable Godpowers artifact changes are auto-applied in this
-mode and logged as YOLO decisions.
-
-`--yolo` does not skip release-truth gates. If safe sync is unresolved, route
-to `/god-reconcile Release Truth And Safe Sync`. If harden has unresolved
-Critical findings, pause even under `--yolo`.
-
-For brownfield and bluefield, `--yolo` still runs `/god-preflight` first when
-`.godpowers/preflight/PREFLIGHT.md` is absent. The orchestrator then follows
-the preflight report's safest recommended route automatically, logging that
-choice to `.godpowers/YOLO-DECISIONS.md`. Preflight may only pause under
-`--yolo` for Critical security findings or a contradiction that makes route
-selection impossible.
-
-### --conservative
-Pass through. Orchestrator pauses at every tier boundary.
-
-### --from=<tier>
-Pass through. Orchestrator re-derives state from disk and starts from named tier.
-
-### --audit
-Pass through. Orchestrator skips building, runs god-auditor on existing artifacts.
-
-### --dry-run
-Pass through. Orchestrator plans but writes nothing.
-
-### --with-hygiene
-After Launch, run a post-launch hygiene pass: god-auditor + god-deps-auditor +
-god-docs-writer verification. Catches pre-existing CVEs, doc drift, artifact
-quality drift before declaring complete.
-
-### --skip-hygiene
-Default. Skip the hygiene pass. Use when iterating quickly.
-
-## Mandatory final sync
-
-Regardless of flags, `/god-mode` always runs `/god-sync` before declaring
-complete. This ensures all 14 core artifact categories and local sync surfaces
-are in a consistent state:
-
-- 10 Tier 0-3 artifacts validated (have-nots passing)
-- 4 capture artifacts noted as `not-yet-created` (graceful handling)
-- repo-doc, repo-surface, feature awareness, source sync-back, host capability,
-  checkpoint, Pillars, and context refresh statuses reported
-- SYNC-LOG.md updated with project-run completion entry
-- state.json reflects final tier statuses
-
-Under `--yolo`, the sync step auto-applies (no pause). Under
-`--conservative`, it pauses for confirmation. Under `--with-hygiene`,
-it runs alongside the hygiene pass.
-
-Display this before the final completion block:
-
-```
-Sync status:
-  Trigger: /god-mode final sync
-  Agent: god-updater spawned
-  Local syncs:
-    + feature-awareness: <recorded runtime features, refreshed context, or no-op>
-    + reverse-sync: <counts and result>
-    + repo-doc-sync: <refreshed repo docs, recommended god-docs-writer, or no-op>
-    + repo-surface-sync: <checked structural surfaces, recommended scoped agents, or no-op>
-    + pillars-sync: <counts and result>
-    + checkpoint-sync: <created, updated, no-op, or skipped>
-    + context-refresh: <spawned, no-op, or skipped>
-  Artifacts: <changed files or no-op>
-  Log: .godpowers/SYNC-LOG.md
-```
-
-The sync step also reconciles native Pillars context. When `.godpowers`
-artifacts create or change durable project truth, Godpowers maps those changes
-to relevant pillar files through `lib/pillars.planArtifactSync`. Default mode
-proposes pillar updates for review. `--yolo` applies them immediately and logs
-the action to `.godpowers/YOLO-DECISIONS.md`.
-
-When `/god-mode` resumes an existing `.godpowers` project, it auto-invokes
-`lib/feature-awareness.run(projectRoot)` before the final sync report. This
-keeps upgraded projects aware of new runtime features, current context fences,
-and migration routes without rewriting user artifacts.
-
-The mandatory final sync also receives repo documentation sync through
-`/god-sync`. This keeps README badges, release surfaces, contribution guidance,
-security policy checks, and Pillars context planning arc-ready before the
-project run is declared complete.
-
-The mandatory final sync also receives repo surface sync through `/god-sync`.
-This keeps routes, packages, agent handoffs, workflow metadata, recipe routes,
-extension packs, and release policy checks aligned before the project run is
-declared complete.
-
-If `/god-mode` resumes an existing `.godpowers` project that lacks Pillars,
-it Pillar-izes the project before continuing. Existing `.godpowers` artifacts
-become managed source references in the relevant `agents/*.md` files.
-
-The sync step is what closes the loop between greenfield project-run creation and
-the comprehensive 14-artifact reconciliation system. See
-`docs/greenfield-coverage.md` for what's created when.
-
-## Completion
-
-When orchestrator returns "complete", display:
-
-```
-Godpowers project run complete.
-
-Sync status:
-  Trigger: /god-mode final sync
-  Agent: god-updater spawned
-  Local syncs:
-    + feature-awareness: <recorded runtime features, refreshed context, or no-op>
-    + reverse-sync: <counts and result>
-    + repo-doc-sync: <refreshed repo docs, recommended god-docs-writer, or no-op>
-    + repo-surface-sync: <checked structural surfaces, recommended scoped agents, or no-op>
-    + pillars-sync: <counts and result>
-    + checkpoint-sync: <created, updated, no-op, or skipped>
-    + context-refresh: <spawned, no-op, or skipped>
-  Artifacts: <changed files or no-op>
-  Log: .godpowers/SYNC-LOG.md
-
-Current status:
-  State: complete
-  Progress: <pct>% (<done> of <total> steps complete; current step <n> of <total>)
-  Worktree: <clean | modified files unstaged | staged changes | mixed>
-  Index: <untouched | staged files listed>
-
-Planning visibility:
-  PRD: <done | pending | missing | deferred> <artifact path when present>
-  Roadmap: <done | pending | missing | deferred> <artifact path when present>
-  Current milestone: <roadmap milestone, tier, or next planning gate when known>
-  Completion: <pct>% <brief basis, for example done steps over total tracked steps>
-
-Artifacts on disk:
-  + PRD           .godpowers/prd/PRD.md
-  + Architecture  .godpowers/arch/ARCH.md
-  + Roadmap       .godpowers/roadmap/ROADMAP.md
-  + Stack         .godpowers/stack/DECISION.md
-  + Repo          .godpowers/repo/AUDIT.md
-  + Build         .godpowers/build/STATE.md
-  + Deploy        .godpowers/deploy/STATE.md
-  + Observe       .godpowers/observe/STATE.md
-  + Launch        .godpowers/launch/STATE.md
-  + Harden        .godpowers/harden/FINDINGS.md
-
-Built. Tested. Shipped. Hardened.
-
-Project is now in STEADY STATE. From here, use these workflows:
-
-  Adding features:        /god-feature
-  Production bugs:        /god-hotfix
-  Code cleanup:           /god-refactor
-  Research questions:     /god-spike
-  Post-incident:          /god-postmortem
-  Framework upgrades:     /god-upgrade
-  Documentation:          /god-docs
-  Dependency updates:     /god-update-deps
-
-Periodic hygiene:
-  Quality audit:          /god-audit
-  Health check:           /god-hygiene
-
-Open items:
-  1. <none, or deployed staging deferred, pending review, unstaged files, etc.>
-
-Next:
-  Recommended: <single safest command or decision>
-  Why: <one sentence tied to disk state>
-
-Proposition:
-  1. Review status: /god-status
-  2. Continue work: /god-next or describe the next intent
-  3. Commit release-ready changes: stage only the intended files, then commit
-  4. Run deployed staging: provide STAGING_APP_URL=<deployed staging origin> when needed
-```
-
-If the run edited code but did not stage or commit, the completion block must
-say so. If unrelated or pre-existing worktree changes are present, do not imply
-the worktree is clean. Recommend a scoped review or explicit staging path.
-
-If the run is a focused brownfield/refactor workflow rather than a full greenfield
-project run, adapt the same closeout shape and replace "Project is now in STEADY
-STATE" with the actual disk-derived lifecycle and next route.
+Use the runbook for:
+- User-visible transcript contract
+- Step cards
+- Pause format
+- Flag semantics
+- Mandatory final sync
+- Completion block

package/skills/god-org-context.md

@@ -49,7 +49,7 @@ Spawn god-org-context-loader in fresh context. Agent creates or reads
 ## Effect on other commands
 
 Once org-context.yaml exists, downstream agents respect it:
-- /god-stack-selector prefers org-standard tools (won't choose Python if org-standard is TypeScript without explicit override)
+- god-stack-selector prefers org-standard tools (won't choose Python if org-standard is TypeScript without explicit override)
 - /god-arch respects org infrastructure (won't propose Kubernetes if org uses Vercel)
 - /god-deploy uses org's deploy platform
 - /god-observe uses org's observability stack

package/skills/god-repair.md

@@ -21,8 +21,8 @@ Detect and fix drift between `state.json` and disk.
 | state.json says PRD done; PRD.md missing | mark PRD pending, alert user |
 | state.json says PRD pending; PRD.md exists and passes lint | mark PRD imported |
 | state.json file hash differs from current PRD.md hash | re-hash and update |
-| linkage.json entry points at deleted code file | remove entry, mark artifact for review |
-| linkage.json entry missing for an annotated code file | scan + add |
+| links/ entry points at deleted code file | remove entry, mark artifact for review |
+| links/ entry missing for an annotated code file | scan + add |
 | Schema version in state.json older than installed | migrate (if path exists) |
 | .trash/ contains items older than 30 days | offer to permanently delete |
 
@@ -60,7 +60,7 @@ Walk every drift item with the user, even safe-auto-fixes.
 
 Built-in. Reads + writes:
 - `.godpowers/state.json`
-- `.godpowers/linkage.json`
+- `.godpowers/links/`
 - `.godpowers/log` (appends repair event)
 
 Calls into `lib/drift-detector.js`, `lib/code-scanner.js`, `lib/reverse-sync.js`.

package/skills/god-review.md

@@ -28,6 +28,11 @@ Spawn **god-spec-reviewer** in fresh context with:
 - The plan or PRD acceptance criteria
 - The test results
 
+Stage 1 also checks that touched files trace to the request, acceptance
+criteria, failing test, or implementation-caused cleanup. Scope creep,
+speculative flexibility, and unrelated churn fail here before code-quality
+review begins.
+
 If FAIL: report findings and STOP. The code must be fixed before Stage 2.
 If PASS: proceed to Stage 2.
 
@@ -36,6 +41,10 @@ If PASS: proceed to Stage 2.
 Spawn **god-quality-reviewer** in fresh context with:
 - The code to review (independent of stage 1 findings)
 
+Stage 2 checks readability, security, error handling, performance,
+maintainability, and simplicity/surgicality. A solution that is technically
+correct but broader than needed still fails review.
+
 If FAIL: report findings.
 If PASS: review complete.
 

package/skills/god-stories.md

@@ -55,6 +55,6 @@ If dep cycles exist, surface them at the end.
 
 ## What this does NOT do
 
-- Modify any STORY.md (use /god-story-close, /god-story-block to change status)
+- Modify any STORY.md (use /god-story-close, /god-story-verify to change status)
 - Spawn agents (read-only)
 - Trigger reverse-sync

package/skills/god-version.md

@@ -14,12 +14,12 @@ Print version and a short capability summary.
 ## Output
 
 ```
-Godpowers v2.0.0
+Godpowers v2.1.1
 Install: /Users/.../.claude/  (matches package.json)
 Surface: 110 skills, 40 agents, 13 workflows, 40 recipes
 Schema: intent.v1, state.v1, events.v1, workflow.v1, routing.v1, recipe.v1
 External integrations available: impeccable, agent-browser (others lazy)
-Feature awareness: planning-system migration, source-system sync-back, context refresh, dashboard status labels, repo documentation sync, repo surface sync
+Feature awareness: planning-system migration, source-system sync-back, context refresh, dashboard status labels, repo documentation sync, repo surface sync, quick proof, request trace, release hardening, maintenance hardening
 ```
 
 ## Subcommands