godpowers 2.4.2 → 2.4.3

package/skills/god-skip.md

@@ -64,15 +64,4 @@ Built-in. Reads + writes `state.json` and PROGRESS.md. Appends to reflog.
 
 ## Locking
 
-The orchestrator acquires a state-lock before this skill mutates anything,
-scoped to the smallest affected unit (e.g. `tier-1.prd` for `/god-prd`,
-`linkage` for `/god-scan`). Lock TTL is 5 minutes; reentrant for the
-same holder; force-reclaimable if stale via `/god-repair`.
-
-Read-only inspection commands (`/god-status`, `/god-doctor`,
-`/god-locate`) do NOT block on the lock. Concurrent writers on
-non-overlapping scopes are allowed; on overlapping scopes, the second
-writer pauses or routes elsewhere via `/god-next`.
-
-See [ARCHITECTURE.md "Concurrency contract"](../ARCHITECTURE.md) for
-the full contract.
+See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.

package/skills/god-stack.md

@@ -60,15 +60,4 @@ The reflog records every god-stack invocation as `op:god-stack` for `/god-undo`.
 
 ## Locking
 
-The orchestrator acquires a state-lock before this skill mutates anything,
-scoped to the smallest affected unit (e.g. `tier-1.prd` for `/god-prd`,
-`linkage` for `/god-scan`). Lock TTL is 5 minutes; reentrant for the
-same holder; force-reclaimable if stale via `/god-repair`.
-
-Read-only inspection commands (`/god-status`, `/god-doctor`,
-`/god-locate`) do NOT block on the lock. Concurrent writers on
-non-overlapping scopes are allowed; on overlapping scopes, the second
-writer pauses or routes elsewhere via `/god-next`.
-
-See [ARCHITECTURE.md "Concurrency contract"](../ARCHITECTURE.md) for
-the full contract.
+See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.

package/skills/god-status.md

@@ -13,8 +13,8 @@ Re-derive state from disk. Your memory is not authoritative. The file system is.
 
 ## Status family views
 
-`/god-status` is the hub for the continue family. It should render the overview
-first, then offer direct shortcuts when the user wants a narrower view:
+`/god-status` is the continue-family overview. It renders operational state,
+proactive checks, blockers, planning visibility, and the next action first.
 
 | View | Shortcut | Purpose |
 |------|----------|---------|
@@ -24,211 +24,34 @@ first, then offer direct shortcuts when the user wants a narrower view:
 | Resume location | `/god-locate` | Orientation from checkpoint, handoff, and disk state. |
 | Next action | `/god-next` | Single recommended command with reason. |
 
+`/god-lifecycle` remains separate because it answers phase and workflow-fit questions without the full dashboard. `/god-locate` remains separate because it is optimized for fresh-session resume from CHECKPOINT.md, handoff files, and disk state.
+
 ## Process
 
-1. Check if `.godpowers/PROGRESS.md` exists
-   - If not: "No Godpowers project found. Run `god init` to start."
+1. Check whether `.godpowers/PROGRESS.md` or `.godpowers/state.json` exists. If neither exists, report that no Godpowers project was found and suggest `/god-init`.
 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`
-   - `.godpowers/stack/DECISION.md`
-   - `.godpowers/repo/AUDIT.md`
-   - `.godpowers/build/STATE.md`
-   - `.godpowers/deploy/STATE.md`
-   - `.godpowers/observe/STATE.md`
-   - `.godpowers/launch/STATE.md`
-   - `.godpowers/harden/FINDINGS.md`
-   - `.godpowers/SYNC-LOG.md`
-   - `.godpowers/CHECKPOINT.md`
-   - `.godpowers/REQUIREMENTS.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
-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
-   - Workflow progress summary: percentage, completed step count, current step number
-   - Planning visibility: PRD status, roadmap status, active milestone, and
-     completion basis
-   - Deliverable progress: requirement and increment status from
-     `lib/requirements` (requirements done / in progress / not started, by
-     priority, and increment counts), or "none declared yet" before a PRD exists
-   - 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
-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`.
-
-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
-
-Current status:
-  State: in progress
-  Phase: Planning (tier 2 of 4, internal tier-1)
-  Step: Architecture (step 3 of 13)
-  Progress: 15% workflow progress (2 of 13 tracked steps complete)
-  Worktree: clean
-  Index: untouched
-
-Planning visibility:
-  PRD: done .godpowers/prd/PRD.md
-  Roadmap: pending
-  Current milestone: Planning / Architecture
-  Completion basis: .godpowers/state.json workflow steps
-
-Deliverable progress:
-  Requirements: [########------------] 8/14 done (57%), 3 in progress, 3 not started
-  By priority: MUST 6/8, SHOULD 2/4, COULD 0/2
-  Increments: 2 done, 1 building, 1 pending
-  Ledger: .godpowers/REQUIREMENTS.md
-
-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
-  Automation: available via codex-app, suggest /god-automation-setup
-  Security: clear
-  Dependencies: clear
-  Hygiene: stale, suggest /god-hygiene
-
-What happens next:
-  1. Run /god-arch
-  2. Verify architecture artifact
-  3. Recompute next gate with /god-next
-
-Tier 1: Planning
-  + PRD           done     .godpowers/prd/PRD.md (lint clean: 0 errors)
-  + Architecture  done     .godpowers/arch/ARCH.md (lint clean: 0 errors)
-  - Roadmap       pending
-  - Stack         pending
-  - Design        not-required (backend-only project)
-  - Product       not-required (backend-only project)
-
-Tier 2: Building
-  - Repo          pending
-  - Build         pending
-
-Tier 3: Shipping
-  - Deploy        pending
-  - Observe       pending
-  - Launch        pending
-  - Harden        pending
-
-Linkage status (from .godpowers/links/):
-  Coverage: 87% (15 of 17 declared IDs implemented)
-  Orphans: 2 (P-MUST-09, P-SHOULD-03)
-  Drift: 1 (colors.removed referenced in src/old.css but missing in DESIGN.md)
-  Pending reviews: 5 (see REVIEW-REQUIRED.md)
-  Last scan: 2026-05-10T14:23:11Z
-  Requirement checklist: run /god-progress or open .godpowers/REQUIREMENTS.md
-
-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.
-
-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
-
-Every status report must end with a proposition block so the user can choose
-how much momentum to give Godpowers:
-
-```
-Proposition:
-  1. Implement partial: [single next command from "What happens next"]
-  2. Implement complete: /god-mode to continue the current project run when no blockers are present
-  3. Discuss more: /god-discuss [unclear state, blocker, or inconsistency]
-  4. Inspect status: /god-locate or /god-next for a smaller routing view
-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`, `<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
-  `available via <provider>, suggest /god-automation-setup`
-- 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`
+3. Call `dashboard.compute(projectRoot)` and render with `dashboard.render(result)`.
+4. Use PROGRESS.md only as fallback or legacy explanation when state.json is missing.
+5. Scan canonical artifact paths for PRD, design, architecture, roadmap, stack, repo, build, deploy, observe, launch, harden, sync, checkpoint, and requirements evidence.
+6. Compare disk state to recorded state and flag phantom resume or untracked work.
+7. Offer `/god-repair` when recorded state and disk evidence conflict.
+
+## Required reference
+
+Read `<runtimeRoot>/references/shared/DASHBOARD-CONTRACT.md` before rendering output. The shared contract owns the dashboard shape, proactive labels, and proposition block.
+
+If the runtime module is unavailable, fall back to a manual scan and say `Dashboard engine: unavailable, manual scan used`.
+
+Never mix workflow progress with audit, hygiene, remediation, or launch-readiness scores. Label those scores separately when they appear.
+
+## Proactive behavior
+
+`/god-status` is read-only by default. It suggests Level 3 agents instead of spawning them unless the user asked status to continue work.
+
+Report checkpoint, review, sync, docs, repo surface, host, runtime, automation, security, dependency, and hygiene signals using the labels in the shared dashboard contract.
 
 ## Mode D awareness
 
-If `lib/multi-repo-detector.detect(projectRoot)` returns
-`isMultiRepo: true`, /god-status appends a "Suite (Mode D) status"
-section showing:
-- Suite name and our role (hub or sibling)
-- Hub path
-- Suggestion to run /god-suite-status for the aggregate view
-
-For the hub itself, this section becomes:
-```
-Suite (Mode D) status:
-  This repo IS the hub for suite "my-products" (3 siblings).
-  Aggregate: 42 artifacts done, 1 drift, 5 pending reviews.
-  Last suite refresh: 2026-05-10T16:45:00Z
-```
-
-The suite section is omitted entirely when the project is not part of
-a registered suite.
+If `lib/multi-repo-detector.detect(projectRoot)` returns `isMultiRepo: true`, append suite status with the suite name, role, hub path, aggregate status when available, and a suggestion to run `/god-suite-status`.
+
+Omit the suite section when the project is not part of a registered suite.

package/skills/god-story-build.md

@@ -62,15 +62,4 @@ Reverse-sync writes Implementation Linkage footer to ROADMAP.md
 
 ## Locking
 
-The orchestrator acquires a state-lock before this skill mutates anything,
-scoped to the smallest affected unit (e.g. `tier-1.prd` for `/god-prd`,
-`linkage` for `/god-scan`). Lock TTL is 5 minutes; reentrant for the
-same holder; force-reclaimable if stale via `/god-repair`.
-
-Read-only inspection commands (`/god-status`, `/god-doctor`,
-`/god-locate`) do NOT block on the lock. Concurrent writers on
-non-overlapping scopes are allowed; on overlapping scopes, the second
-writer pauses or routes elsewhere via `/god-next`.
-
-See [ARCHITECTURE.md "Concurrency contract"](../ARCHITECTURE.md) for
-the full contract.
+See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.

package/skills/god-story-close.md

@@ -68,15 +68,4 @@ linkage updates.
 
 ## Locking
 
-The orchestrator acquires a state-lock before this skill mutates anything,
-scoped to the smallest affected unit (e.g. `tier-1.prd` for `/god-prd`,
-`linkage` for `/god-scan`). Lock TTL is 5 minutes; reentrant for the
-same holder; force-reclaimable if stale via `/god-repair`.
-
-Read-only inspection commands (`/god-status`, `/god-doctor`,
-`/god-locate`) do NOT block on the lock. Concurrent writers on
-non-overlapping scopes are allowed; on overlapping scopes, the second
-writer pauses or routes elsewhere via `/god-next`.
-
-See [ARCHITECTURE.md "Concurrency contract"](../ARCHITECTURE.md) for
-the full contract.
+See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.

package/skills/god-story.md

@@ -41,15 +41,4 @@ Add a new story under `.godpowers/stories/<feature-slug>/`.
 
 ## Locking
 
-The orchestrator acquires a state-lock before this skill mutates anything,
-scoped to the smallest affected unit (e.g. `tier-1.prd` for `/god-prd`,
-`linkage` for `/god-scan`). Lock TTL is 5 minutes; reentrant for the
-same holder; force-reclaimable if stale via `/god-repair`.
-
-Read-only inspection commands (`/god-status`, `/god-doctor`,
-`/god-locate`) do NOT block on the lock. Concurrent writers on
-non-overlapping scopes are allowed; on overlapping scopes, the second
-writer pauses or routes elsewhere via `/god-next`.
-
-See [ARCHITECTURE.md "Concurrency contract"](../ARCHITECTURE.md) for
-the full contract.
+See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.

package/skills/god-sync.md

@@ -156,15 +156,4 @@ invoked manually for spot-checks.
 
 ## Locking
 
-The orchestrator acquires a state-lock before this skill mutates anything,
-scoped to the smallest affected unit (e.g. `tier-1.prd` for `/god-prd`,
-`linkage` for `/god-scan`). Lock TTL is 5 minutes; reentrant for the
-same holder; force-reclaimable if stale via `/god-repair`.
-
-Read-only inspection commands (`/god-status`, `/god-doctor`,
-`/god-locate`) do NOT block on the lock. Concurrent writers on
-non-overlapping scopes are allowed; on overlapping scopes, the second
-writer pauses or routes elsewhere via `/god-next`.
-
-See [ARCHITECTURE.md "Concurrency contract"](../ARCHITECTURE.md) for
-the full contract.
+See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.

package/skills/god-undo.md

@@ -54,15 +54,4 @@ Suggested next:
 
 ## Locking
 
-The orchestrator acquires a state-lock before this skill mutates anything,
-scoped to the smallest affected unit (e.g. `tier-1.prd` for `/god-prd`,
-`linkage` for `/god-scan`). Lock TTL is 5 minutes; reentrant for the
-same holder; force-reclaimable if stale via `/god-repair`.
-
-Read-only inspection commands (`/god-status`, `/god-doctor`,
-`/god-locate`) do NOT block on the lock. Concurrent writers on
-non-overlapping scopes are allowed; on overlapping scopes, the second
-writer pauses or routes elsewhere via `/god-next`.
-
-See [ARCHITECTURE.md "Concurrency contract"](../ARCHITECTURE.md) for
-the full contract.
+See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.

package/skills/god-update-deps.md

@@ -122,15 +122,4 @@ in the linkage system:
 
 ## Locking
 
-The orchestrator acquires a state-lock before this skill mutates anything,
-scoped to the smallest affected unit (e.g. `tier-1.prd` for `/god-prd`,
-`linkage` for `/god-scan`). Lock TTL is 5 minutes; reentrant for the
-same holder; force-reclaimable if stale via `/god-repair`.
-
-Read-only inspection commands (`/god-status`, `/god-doctor`,
-`/god-locate`) do NOT block on the lock. Concurrent writers on
-non-overlapping scopes are allowed; on overlapping scopes, the second
-writer pauses or routes elsewhere via `/god-next`.
-
-See [ARCHITECTURE.md "Concurrency contract"](../ARCHITECTURE.md) for
-the full contract.
+See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.

package/skills/god-upgrade.md

@@ -125,15 +125,4 @@ in the linkage system:
 
 ## Locking
 
-The orchestrator acquires a state-lock before this skill mutates anything,
-scoped to the smallest affected unit (e.g. `tier-1.prd` for `/god-prd`,
-`linkage` for `/god-scan`). Lock TTL is 5 minutes; reentrant for the
-same holder; force-reclaimable if stale via `/god-repair`.
-
-Read-only inspection commands (`/god-status`, `/god-doctor`,
-`/god-locate`) do NOT block on the lock. Concurrent writers on
-non-overlapping scopes are allowed; on overlapping scopes, the second
-writer pauses or routes elsewhere via `/god-next`.
-
-See [ARCHITECTURE.md "Concurrency contract"](../ARCHITECTURE.md) for
-the full contract.
+See `<runtimeRoot>/references/shared/LOCKING.md` for the shared state-lock contract.