godpowers 1.6.16 → 1.6.19

package/skills/god-next.md

@@ -25,6 +25,9 @@ Before reading routing data or calling runtime modules, resolve the Godpowers ru
 4. For status output, load `<runtimeRoot>/lib/dashboard.js` and call
    `dashboard.compute(projectRoot)`. Use `dashboard.render(result)` for the
    shared dashboard section before adding route-specific detail.
+5. If the checkout runtime and installed runtime differ, say which runtime root
+   was used. Only call the output a manual disk scan when `lib/dashboard.js`
+   cannot be loaded at all.
 
 ## Three modes of invocation
 
@@ -347,11 +350,13 @@ Godpowers Next
 
 Godpowers Dashboard
 
+Source: runtime dashboard (lib/dashboard.js)
+
 Current status:
   State: proposal
   Phase: [plain-language phase] (tier [human ordinal] of [human total])
   Step: [current step label] (step [n] of [total steps])
-  Progress: [pct]% ([done] of [total] steps complete)
+  Progress: [pct]% workflow progress ([done] of [total] tracked steps complete)
   Worktree: [clean | modified files unstaged | staged changes | mixed]
   Index: [untouched | staged files listed]
 
@@ -359,7 +364,7 @@ Planning visibility:
   PRD: [done | pending | missing | deferred] [path when present]
   Roadmap: [done | pending | missing | deferred] [path when present]
   Current milestone: [roadmap milestone, phase, tier, or next planning gate]
-  Completion: [pct]% [basis from state.json, PROGRESS.md, or artifacts]
+  Completion basis: [state.json, PROGRESS.md, artifacts, or audit score source]
 
 Suggested next: [/god-X]
 

package/skills/god-status.md

@@ -38,9 +38,10 @@ Re-derive state from disk. Your memory is not authoritative. The file system is.
    - 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
 8. Report the Godpowers Dashboard from `dashboard.render(result)`:
+   - Dashboard source: runtime dashboard or unavailable manual scan
    - Current mode and scale
    - Current phase, tier number, step label, and step number
-   - Progress summary: percentage, completed step count, current step number
+   - Workflow 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
@@ -55,11 +56,16 @@ Re-derive state from disk. Your memory is not authoritative. The file system is.
 If the runtime module is unavailable, fall back to the manual scan below and
 say `Dashboard engine: unavailable, manual scan used`.
 
+Never mix workflow progress with audit, hygiene, or remediation scores. If an
+audit score is relevant, label it separately as `Audit score`.
+
 ## Output Format
 
 ```text
 Godpowers Dashboard
 
+Source: runtime dashboard (lib/dashboard.js)
+
 Mode: A (greenfield)    Scale: medium
 Started: 2026-05-09
 
@@ -67,7 +73,7 @@ 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)
+  Progress: 15% workflow progress (2 of 13 tracked steps complete)
   Worktree: clean
   Index: untouched
 
@@ -75,7 +81,7 @@ Planning visibility:
   PRD: done .godpowers/prd/PRD.md
   Roadmap: pending
   Current milestone: Planning / Architecture
-  Completion: 15% based on PROGRESS.md tracked steps
+  Completion basis: .godpowers/state.json workflow steps
 
 What happened recently:
   1. PRD artifact verified on disk
@@ -171,8 +177,10 @@ 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`
+- Docs: `fresh`, `<N> stale, suggest /god-docs`, `possible drift, suggest
+  /god-docs`, or `repo-doc-sync ran`
+- Repo surface: `fresh`, `<N> stale, suggest /god-doctor`, or
+  `repo-surface-sync ran`
 - Runtime: `not-applicable`, `known URL, suggest /god-test-runtime`, or
   `no known URL, defer deployed verification`
 - Automation: `not configured`, `<N> active`, or

package/skills/god-sync.md

@@ -35,11 +35,23 @@ User runs `/god-sync` after manual changes. Useful for:
 3. Call `lib/pillars.pillarizeExisting(projectRoot)` if Pillars is absent or
    partial, because every Godpowers project must also carry native Pillars
    context.
-4. If `state.json` contains enabled `source-systems`, auto-invoke
+4. Call `lib/repo-doc-sync.run(projectRoot)` so README badges, public surface
+   counts, release references, contribution docs, and security policy are
+   checked before sync closes. Safe mechanical updates are local runtime work.
+   Narrative drift should recommend or spawn `god-docs-writer`.
+5. Call `lib/repo-surface-sync.run(projectRoot)` so command routing, package
+   payload, agent handoffs, workflow metadata, recipe routes, extension packs,
+   and release policy are checked before sync closes. Structural drift should
+   recommend scoped agents such as `god-auditor`, `god-roadmap-reconciler`, or
+   `god-coordinator`.
+6. If repo documentation changed durable project truth, plan or apply Pillars
+   updates through `lib/pillars.planArtifactSync` or
+   `lib/pillars.applyArtifactSync` under the active Pillars policy.
+7. If `state.json` contains enabled `source-systems`, auto-invoke
    `lib/source-sync.run(projectRoot)` so current Godpowers progress is written
    back to imported GSD, BMAD, or Superpowers companion files. Report this as
    `Agent: none, local runtime only`.
-5. Spawn god-updater in fresh context with:
+8. Spawn god-updater in fresh context with:
    - The reconciliation verdict (if available from a prior /god-reconcile)
    - Or: re-run reconciliation against current state to detect what changed
    - Recent commits for context
@@ -51,7 +63,7 @@ Auto-invoked:
   Trigger: <manual /god-sync, recipe closeout, /god-mode final sync, or other source>
   Agent: god-updater
   Local syncs:
-    - pending: feature-awareness, reverse-sync, source-sync, pillars-sync, checkpoint-sync, context-refresh
+    - pending: feature-awareness, reverse-sync, source-sync, repo-doc-sync, repo-surface-sync, pillars-sync, checkpoint-sync, context-refresh
   Artifacts: pending
   Log: .godpowers/SYNC-LOG.md
 ```
@@ -78,6 +90,8 @@ Sync status:
     + reverse-sync: <scanned N files, updated M footers, populated K review items>
     + feature-awareness: <recorded runtime features, refreshed context, or no-op>
     + source-sync: <written GSD/BMAD/Superpowers companion files, no-op, or skipped>
+    + repo-doc-sync: <refreshed README badges/counts, recommended god-docs-writer, or no-op>
+    + repo-surface-sync: <checked routes/package/agents/workflows/extensions, recommended scoped agents, or no-op>
     + 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>
@@ -122,6 +136,8 @@ Next:
 | Orphan todos | Closes superseded todos |
 | Lost threads | Active threads get progress notes |
 | Pillars drift | Keeps `agents/*.md` aligned with current `.godpowers` artifacts |
+| Repo docs drift | Keeps README badges, repo docs, and release surfaces aligned |
+| Repo surface drift | Keeps routes, packages, agents, workflows, recipes, and extensions aligned |
 
 The loop:
 

package/skills/god-version.md

@@ -14,12 +14,12 @@ Print version and a short capability summary.
 ## Output
 
 ```
-Godpowers v1.6.16
+Godpowers v1.6.19
 Install: /Users/.../.claude/  (matches package.json)
 Surface: 109 skills, 40 agents, 13 workflows, 36 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
+Feature awareness: planning-system migration, source-system sync-back, context refresh, dashboard status labels, repo documentation sync, repo surface sync
 ```
 
 ## Subcommands