godpowers 1.6.10 → 1.6.12

package/skills/god-review-changes.md

@@ -52,6 +52,23 @@ When showing "affected files," this skill cross-references
 `lib/linkage.queryByFile(projectRoot, file)` so the user sees which
 artifact IDs that file is linked to. Helps decide what to fix.
 
+## Proactive invocation
+
+Godpowers should suggest this skill automatically when
+`REVIEW-REQUIRED.md` gains pending entries from reverse-sync, design impact,
+runtime verification, docs drift, or security-sensitive changes.
+
+Default behavior is suggestion only:
+
+```text
+Proactive checks:
+  Reviews: <N> pending, suggest /god-review-changes
+```
+
+Do not auto-run the interactive walkthrough unless the user asks to address
+the pending items now. Do not auto-clear review items under default mode or
+`--yolo`.
+
 ## Output
 
 ```

package/skills/god-review.md

@@ -9,7 +9,7 @@ description: |
 
 # /god-review
 
-Spawn two specialist review agents in fresh contexts via Task tool.
+Spawn two specialist review agents in fresh contexts via the host platform's native agent spawning mechanism.
 
 ## Setup
 

package/skills/god-roadmap.md

@@ -9,7 +9,7 @@ description: |
 
 # /god-roadmap
 
-Spawn the **god-roadmapper** agent in a fresh context via Task tool.
+Spawn the **god-roadmapper** agent in a fresh context via the host platform's native agent spawning mechanism.
 
 ## Setup
 

package/skills/god-scan.md

@@ -17,6 +17,19 @@ god-build, god-feature, god-hotfix etc. trigger automatically (per
 Phase 7 workflow integration). Useful when you want to refresh state
 between automatic triggers, or after manual code edits.
 
+Because `/god-scan` calls the local reverse-sync runtime directly, it must be
+explicit when no agent is spawned:
+
+```
+Auto-invoked:
+  Trigger: /god-scan
+  Agent: none, local runtime only
+  Local syncs:
+    + reverse-sync: pending
+  Artifacts: pending
+  Log: REVIEW-REQUIRED.md if drift is found
+```
+
 ## Forms
 
 | Form | Action |
@@ -43,6 +56,17 @@ between automatic triggers, or after manual code edits.
    - Drift findings (errors, warnings, infos)
    - Footers updated
    - REVIEW-REQUIRED items added
+4. End with sync status:
+
+```
+Sync status:
+  Trigger: /god-scan
+  Agent: none, local runtime only
+  Local syncs:
+    + reverse-sync: <scanned N files, updated M footers, populated K review items>
+  Artifacts: <changed linkage files, fenced artifacts, REVIEW-REQUIRED.md, or no-op>
+  Log: <REVIEW-REQUIRED.md or none>
+```
 
 ## Fence rules
 

package/skills/god-stack.md

@@ -9,7 +9,7 @@ description: |
 
 # /god-stack
 
-Spawn the **god-stack-selector** agent in a fresh context via Task tool.
+Spawn the **god-stack-selector** agent in a fresh context via the host platform's native agent spawning mechanism.
 
 ## Setup
 

package/skills/god-status.md

@@ -15,8 +15,12 @@ Re-derive state from disk. Your memory is not authoritative. The file system is.
 
 1. Check if `.godpowers/PROGRESS.md` exists
    - If not: "No Godpowers project found. Run `god init` to start."
-2. Read PROGRESS.md for recorded state
-3. Scan ALL artifact paths on disk:
+2. Resolve the runtime root and load `<runtimeRoot>/lib/dashboard.js`.
+3. Call `dashboard.compute(projectRoot)` and use the returned object as the
+   primary dashboard source.
+4. Read PROGRESS.md for recorded state when state.json is missing or when you
+   need to explain legacy progress.
+5. Scan ALL artifact paths on disk:
    - `.godpowers/prd/PRD.md`
    - `.godpowers/arch/ARCH.md`
    - `.godpowers/roadmap/ROADMAP.md`
@@ -27,31 +31,45 @@ Re-derive state from disk. Your memory is not authoritative. The file system is.
    - `.godpowers/observe/STATE.md`
    - `.godpowers/launch/STATE.md`
    - `.godpowers/harden/FINDINGS.md`
-4. For each artifact found: run a lightweight have-nots check
-5. Compare disk state to PROGRESS.md state:
+   - `.godpowers/SYNC-LOG.md`
+   - `.godpowers/CHECKPOINT.md`
+6. For each artifact found: run a lightweight have-nots check
+7. Compare disk state to PROGRESS.md state:
    - If PROGRESS.md says "done" but artifact is missing: FLAG as phantom resume
    - If artifact exists but PROGRESS.md says "pending": FLAG as untracked work
-6. Report:
+8. Report the Godpowers Dashboard from `dashboard.render(result)`:
    - Current mode and scale
+   - Current phase, tier number, step label, and step number
    - Progress summary: percentage, completed step count, current step number
    - Planning visibility: PRD status, roadmap status, active milestone, and
      completion basis
    - What happened recently, using CHECKPOINT.md actions when available
+   - Last sync status, using SYNC-LOG.md when available
+   - Proactive opportunities based on the auto-invoke policy
    - What happens next, using routing and disk state
    - Per-tier status (with disk verification)
    - Any inconsistencies between PROGRESS.md and disk
    - Suggested next action
-7. If inconsistencies found: offer to repair PROGRESS.md to match disk truth
+9. If inconsistencies found: offer to repair PROGRESS.md to match disk truth
+
+If the runtime module is unavailable, fall back to the manual scan below and
+say `Dashboard engine: unavailable, manual scan used`.
 
 ## Output Format
 
-```
-Godpowers Status
+```text
+Godpowers Dashboard
 
 Mode: A (greenfield)    Scale: medium
 Started: 2026-05-09
-Progress: 15% (2 of 13 steps complete; current step 3 of 13)
-Current: Tier 1 Planning / Architecture
+
+Current status:
+  State: in progress
+  Phase: Planning (tier 2 of 4, internal tier-1)
+  Step: Architecture (step 3 of 13)
+  Progress: 15% (2 of 13 steps complete)
+  Worktree: clean
+  Index: untouched
 
 Planning visibility:
   PRD: done .godpowers/prd/PRD.md
@@ -63,6 +81,26 @@ What happened recently:
   1. PRD artifact verified on disk
   2. Tier state refreshed from state.json
 
+Last sync:
+  Trigger: /god-mode final sync
+  Agent: god-updater
+  Local syncs:
+    + reverse-sync: scanned 14 files, updated 2 footers, populated 0 review items
+    + pillars-sync: no-op
+    + checkpoint-sync: CHECKPOINT.md updated
+    + context-refresh: no-op
+  Log: .godpowers/SYNC-LOG.md
+
+Proactive opportunities:
+  Checkpoint: fresh
+  Reviews: 5 pending, suggest /god-review-changes
+  Sync: fresh
+  Docs: possible drift, suggest /god-docs
+  Runtime: known local URL, suggest /god-test-runtime
+  Security: clear
+  Dependencies: clear
+  Hygiene: stale, suggest /god-hygiene
+
 What happens next:
   1. Run /god-arch
   2. Verify architecture artifact
@@ -97,7 +135,12 @@ Suite (Mode D) status:
   This repo is a sibling of suite "my-products" (hub: ../hub)
   Run /god-suite-status to see all 3 repos and meta-linter findings.
 
-Next: god roadmap
+Open items:
+  1. Roadmap and stack are still pending
+
+Next:
+  Recommended: /god-roadmap
+  Why: architecture is done and the roadmap is the next planning gate.
 ```
 
 ## Proposition Closeout
@@ -117,6 +160,24 @@ Recommended: [one option and why it fits the disk-derived state]
 If inconsistencies are present, make `/god-repair` the partial option and do
 not recommend `/god-mode` until disk state is coherent.
 
+## Proactive Opportunity Rules
+
+Use the master auto-invoke policy to populate `Proactive opportunities`.
+`/god-status` is read-only by default, so it suggests Level 3 agents instead of
+spawning them unless the user asked status to continue work.
+
+Report:
+- Checkpoint: `fresh`, `missing`, `stale`, or `conflicts with state.json`
+- Reviews: `none` or `<N> pending, suggest /god-review-changes`
+- Sync: `fresh`, `missing`, `stale`, or `suggest /god-sync`
+- Docs: `fresh`, `possible drift, suggest /god-docs`, or
+  `docs drift-check already logged`
+- Runtime: `not-applicable`, `known URL, suggest /god-test-runtime`, or
+  `no known URL, defer deployed verification`
+- Security: `clear` or `sensitive files changed, suggest /god-harden`
+- Dependencies: `clear` or `dependency files changed, suggest /god-update-deps`
+- Hygiene: `fresh` or `stale, suggest /god-hygiene`
+
 ## Mode D awareness
 
 If `lib/multi-repo-detector.detect(projectRoot)` returns

package/skills/god-sync.md

@@ -37,6 +37,18 @@ User runs `/god-sync` after manual changes. Useful for:
    - Or: re-run reconciliation against current state to detect what changed
    - Recent commits for context
 
+Before spawning, show a visible auto-invoke card:
+
+```
+Auto-invoked:
+  Trigger: <manual /god-sync, recipe closeout, /god-mode final sync, or other source>
+  Agent: god-updater
+  Local syncs:
+    - pending: reverse-sync, pillars-sync, checkpoint-sync, context-refresh
+  Artifacts: pending
+  Log: .godpowers/SYNC-LOG.md
+```
+
 ## Verification
 
 After god-updater returns:
@@ -52,6 +64,21 @@ After god-updater returns:
 ```
 Sync complete.
 
+Sync status:
+  Trigger: /god-mode final sync
+  Agent: god-updater spawned
+  Local syncs:
+    + reverse-sync: <scanned N files, updated M footers, populated K review items>
+    + pillars-sync: <updated N pillar files, no-op, or proposed>
+    + checkpoint-sync: <CHECKPOINT.md updated or skipped>
+    + context-refresh: <updated AGENTS.md/tool pointers, no-op, or skipped by setting>
+  Artifacts: <changed files, no-op, or deferred>
+  Log: .godpowers/SYNC-LOG.md
+
+If this path ran only a local helper, say:
+  Agent: none, local runtime only
+  Why: this path called lib/reverse-sync.run directly
+
 Updated:
   - prd/PRD.md (added requirement P-MUST-12)
   - arch/ARCH.md (added ADR-007)
@@ -65,7 +92,13 @@ Updated:
 Have-nots: all passing
 SYNC-LOG.md updated.
 
-Suggested next: /god-status
+Current status:
+  State: <complete | partial | blocked | no-op>
+  Progress: <pct>% when available
+
+Next:
+  Recommended: /god-status
+  Why: verify the disk-derived state after sync.
 ```
 
 ## What this prevents

package/skills/god-test-runtime.md

@@ -96,6 +96,32 @@ critical findings have the same gate semantics.
 | `/god-harden` | a11y portion | warning |
 | `/god-design` (post-change) | audit | warning |
 
+Automatic runtime verification requires evidenced URL input:
+
+- A local dev server URL from `state.json.dev-server.url`
+- A deploy URL from `state.json.deploy.url`
+- A user-provided URL in the current session
+- A checked-in config or Godpowers artifact that explicitly identifies the URL
+  as current
+
+If frontend-visible files changed but no URL is evidenced, do not guess. Add a
+proactive suggestion for `/god-test-runtime` and explain what URL source is
+missing. If only a local URL is evidenced, run local verification and defer
+deployed staging verification until the user provides
+`STAGING_APP_URL=<deployed staging origin>` or reaches final sign-off.
+
+When auto-invoked, show:
+
+```text
+Auto-invoked:
+  Trigger: frontend-visible files changed and URL was evidenced
+  Agent: god-browser-tester
+  Local syncs:
+    + runtime-verification: <audit | test | full pipeline>
+  Artifacts: .godpowers/runtime/<run-id>/
+  Log: .godpowers/runtime/<run-id>/summary.md
+```
+
 ## Output to events.jsonl
 
 ```json