godpowers 2.0.0 → 2.1.1

package/references/HAVE-NOTS.md

@@ -590,11 +590,12 @@ Updates applied without reading changelog for breaking changes. Fail.
 ## Reference Tally
 
 - Universal: 12
-- Tier 0 Orchestration: 6
+- Tier 0 Orchestration: 10
 - Tier 1 PRD: 15
-- Tier 1 Architecture: 12
+- Tier 1 Architecture: 13
 - Tier 1 Roadmap: 10
 - Tier 1 Stack: 5
+- Tier 1 Domain Glossary: 5
 - Tier 2 Repo: 8
 - Tier 2 Build: 12
 - Tier 3 Deploy: 8
@@ -607,7 +608,7 @@ Updates applied without reading changelog for breaking changes. Fail.
 - Workflow Docs: 5
 - Workflow Deps: 6
 
-**Total: 146 named have-nots.**
+**Total: 156 named have-nots.**
 
 Each is grep-testable. Each is a documented failure mode. Together they form
 the mechanical quality definition for Godpowers output.

package/references/orchestration/GOD-MODE-RUNBOOK.md

@@ -0,0 +1,273 @@
+# God Mode Runbook
+
+This reference contains the detailed transcript, flag, final sync, and completion contracts for `/god-mode`. The skill file remains the dispatch contract and points here for operational templates.
+
+## User-Visible Transcript Contract
+
+The God Mode transcript is an operator console, not a prompt debugger.
+
+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
+
+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.

package/routing/god-arch.yaml

@@ -31,7 +31,7 @@ execution:
 standards:
   substitution-test: true
   three-label-test: true
-  have-nots: [A-01, A-02, A-03, A-04, A-05, A-06, A-07, A-08, A-09, A-10, A-11, A-12]
+  have-nots: [A-01, A-02, A-03, A-04, A-05, A-06, A-07, A-08, A-09, A-10, A-11, A-12, A-13]
   gate-on-failure: pause-for-user
 
 success-path:

package/routing/god-build.yaml

@@ -11,7 +11,7 @@ prerequisites:
       auto-complete: /god-roadmap
       human-required: true
     - check: state:tier-2.repo.status == done
-      auto-complete: /god-roadmap
+      auto-complete: /god-repo
       human-required: true
 
 execution:

package/skills/god-add-backlog.md

@@ -2,7 +2,7 @@
 name: god-add-backlog
 description: |
   Add an idea to the backlog. Less urgent than a todo. Reviewed periodically
-  via /god-review-backlog. Captured in .godpowers/backlog/BACKLOG.md.
+  via /god-add-backlog list. Captured in .godpowers/backlog/BACKLOG.md.
 
   Triggers on: "god add backlog", "/god-add-backlog", "backlog this", "for later"
 ---

package/skills/god-agent-audit.md

@@ -1,7 +1,7 @@
 ---
 name: god-agent-audit
 description: |
-  Validates every `agents/*.md` against the agent contract:
+  Validates every `agents/god-*.md` against the agent contract:
   required frontmatter, recommended sections (Have-Nots, Inputs,
   Outputs, Handoff), hand-off targets exist, no dual-ownership of
   output paths. Lenient by design: most issues are warnings; only
@@ -50,7 +50,7 @@ opportunities, not failures.
 ```
 Agent audit
 
-37 agents audited
+40 agents audited
 0 errors, 2 warnings, 90 infos
 
 Errors:

package/skills/god-build.md

@@ -39,12 +39,14 @@ For each slice in the wave (parallel):
    - The slice plan only (not the whole PLAN.md)
    - Relevant ARCH context for this slice
    - Stack DECISION
-2. Wait for executor to complete (TDD enforced)
+2. Wait for executor to complete (TDD and request-trace discipline enforced)
 3. Spawn **god-spec-reviewer** in fresh context (independent of executor)
-   - If FAIL: return slice to god-executor with findings
+   - If FAIL: return slice to god-executor with findings, including any
+     scope creep or request-trace failures
    - If PASS: proceed to stage 2
 4. Spawn **god-quality-reviewer** in fresh context (independent)
-   - If FAIL: return slice to god-executor with findings
+   - If FAIL: return slice to god-executor with findings, including any
+     overcomplication, speculative abstraction, or unrelated cleanup
    - If PASS: commit the slice atomically
 5. Update `.godpowers/build/STATE.md`
 

package/skills/god-context-scan.md

@@ -60,9 +60,8 @@ called drifts.
      last 3 events)
    - **info**: claim mentions facts not in CHECKPOINT held-facts
      (might be new, worth recording)
-6. Suggested actions: `/god-locate` to re-orient, `/god-repair`
-   for state drift, or accept the new facts via `/god-checkpoint
-   --record-facts`.
+6. Suggested actions: `/god-locate` to re-orient, or `/god-repair`
+   to reconcile state drift and record the new facts.
 
 ### Output
 

package/skills/god-design.md

@@ -54,7 +54,7 @@ producing DESIGN.md in the
 | `/god-design optimize` | Performance improvements (impeccable optimize) |
 | `/god-design live` | Visual variant mode (impeccable live) |
 | `/god-design status` | Lint findings + drift report |
-| `/god-design impact "<change>"` | What-if analysis (delegates to god-impact-analyzer) |
+| `/god-design impact "<change>"` | What-if analysis (delegates to /god-design-impact) |
 
 ## Process
 
@@ -100,7 +100,7 @@ Project root:
 
 Inside `.godpowers/design/`:
 - `STATE.md` (lint history, version, impeccable command log)
-- `HISTORY.md` (append-only log of design changes; populated by god-design-updater)
+- `HISTORY.md` (append-only log of design changes; populated by god-designer)
 - `REJECTED.md` (append-only log of blocked changes; populated by god-design-reviewer)
 
 ## Output to events.jsonl

package/skills/god-doctor.md

@@ -50,7 +50,7 @@ GODPOWERS DOCTOR
 Install: claude (~/.claude/)
   [OK] 110 skills installed
   [OK] 40 agents installed
-  [OK] VERSION matches (1.6.6)
+  [OK] VERSION matches (2.1.1)
   [WARN] routing/god-doctor.yaml exists but skill file did not until now
 
 Project: /Users/.../my-project/.godpowers/
@@ -144,7 +144,7 @@ findings should recommend the scoped specialist named by the helper.
 Built-in, no spawned agent. Reads:
 - `<runtime>/GODPOWERS_VERSION` (compare to package.json)
 - `<runtime>/skills/` and `<runtime>/agents/` listings
-- `.godpowers/state.json`, `intent.yaml`, `log`, `linkage.json`
+- `.godpowers/state.json`, `intent.yaml`, `log`, `links/`
 - `lib/feature-awareness.detect(projectRoot)` for existing-project upgrade
   awareness
 - `lib/repo-doc-sync.detect(projectRoot)` for repo documentation freshness

package/skills/god-help.md

@@ -28,9 +28,10 @@ All installed skills grouped by category. Categories match
 `docs/reference.md` order.
 
 ### 4. Where to go for more
-- Full reference: `<runtime>/godpowers-references/reference.md`
-- Concepts: `<runtime>/godpowers-references/concepts.md`
-- Roadmap: `<runtime>/godpowers-references/ROADMAP.md`
+- Full reference: https://github.com/aihxp/godpowers/blob/main/docs/reference.md
+- Concepts: https://github.com/aihxp/godpowers/blob/main/docs/concepts.md
+- Roadmap: https://github.com/aihxp/godpowers/blob/main/docs/ROADMAP.md
+- Installed have-nots catalog: `<runtime>/godpowers-references/HAVE-NOTS.md`
 
 ## Subcommands