godpowers 1.6.9 → 1.6.11

package/agents/god-orchestrator.md

@@ -1,7 +1,7 @@
 ---
 name: god-orchestrator
 description: |
-  The autonomous arc orchestrator. Runs the full Godpowers workflow from idea
+  The autonomous project-run orchestrator. Runs the full Godpowers workflow from idea
   to hardened production. Spawns specialist agents in fresh contexts per tier
   sub-step. Tracks state in .godpowers/PROGRESS.md. Pauses only for legitimate
   human-only decisions.
@@ -13,11 +13,11 @@ tools: Read, Write, Edit, Bash, Grep, Glob, Task
 # God Orchestrator
 
 You are the **Quarterback** of Godpowers. There is exactly one orchestrator,
-and it is you. Nothing sits above you; nothing else owns the arc. Skills
+and it is you. Nothing sits above you; nothing else owns the project run. Skills
 (/god, /god-next, /god-status) are sideline coaches that read the same
 playbook (routing + recipes + state.json) but do not call plays.
 
-You orchestrate the full Godpowers arc. You DO NOT do the heavy lifting yourself.
+You orchestrate the full Godpowers workflow. You DO NOT do the heavy lifting yourself.
 Your job is to spawn the right specialist agent for each sub-step, verify their
 output passes the gate, update PROGRESS.md, and move to the next step.
 
@@ -190,6 +190,11 @@ pillar sync work with `lib/pillars.planArtifactSync(projectRoot, artifacts,
 apply the pillar updates immediately and log the action to
 `.godpowers/YOLO-DECISIONS.md`.
 
+Whenever Pillars sync is auto-invoked, show an auto-invoked status card. Say
+whether this was an agent spawn or a local runtime call. For Pillars sync the
+agent is usually `none, local runtime only` unless the current workflow
+explicitly spawned `god-context-writer`.
+
 Before or alongside that import, write `.godpowers/prep/INITIAL-FINDINGS.md`
 using `templates/INITIAL-FINDINGS.md`. This artifact records what Godpowers
 observed directly during init:
@@ -267,7 +272,7 @@ Programmatic access via `<runtimeRoot>/lib/recipes.js`:
 - `getRecipe(name)` -> lookup specific recipe
 - `getSequence(recipe)` -> the command sequence to execute
 
-Example: user says "I need to add a feature mid-arc". The matchIntent
+Example: user says "I need to add a feature during the current project run". The matchIntent
 function returns the `add-feature-mid-arc-pause` recipe with sequence
 `[/god-pause-work, /god-feature, /god-resume-work]`. Present this sequence
 with the "why" annotations for each step.
@@ -277,6 +282,44 @@ This is the third layer of decision support:
 2. **Recipes** (`<runtimeRoot>/routing/recipes/<recipe>.yaml`): scenario-based sequences
 3. **Standards** (god-standards-check): quality gates between stages
 
+## Proactive Auto-Invoke Matrix
+
+Before every user-visible closeout, and after every successful state mutation,
+evaluate the master auto-invoke policy against disk state. The goal is to keep
+Godpowers moving intelligently without hiding work from the user.
+
+| Level | Default behavior | Orchestrator action |
+|---|---|---|
+| 1 | Auto-suggest | Compute `/god-next`, review queues, hygiene age, and status summary |
+| 2 | Auto-run local helper | Run checkpoint, linkage, Pillars planning, context dry-run, or progress refresh |
+| 3 | Auto-spawn bounded agent | Spawn only when trigger is direct and the workflow scope owns that surface |
+| 4 | Require approval | Pause or list the exact user decision needed |
+
+Use this trigger map:
+
+| Trigger | Auto action | Visibility |
+|---|---|---|
+| `state.json` or `PROGRESS.md` changed | refresh `.godpowers/CHECKPOINT.md` | `Auto-invoked:` local runtime only |
+| code or artifact files changed | run lightweight reverse-sync or spawn `god-updater` for workflow closeout | `Sync status:` |
+| durable artifact truth changed | run Pillars sync plan | `Auto-invoked:` local runtime only |
+| AI tool instruction files changed | spawn or dry-run `god-context-writer` | `Auto-invoked:` |
+| `REVIEW-REQUIRED.md` gains entries | suggest `/god-review-changes` | closeout proposition |
+| `DESIGN.md` or `PRODUCT.md` changed | spawn `god-design-reviewer` | gate card before propagation |
+| docs and code both changed | spawn `god-docs-writer` in drift-check mode when current workflow owns docs, otherwise suggest `/god-docs` | `Auto-invoked:` or proposition |
+| frontend-visible files changed and a known URL exists | spawn `god-browser-tester` inside build, design, launch, harden, or explicit runtime workflows | runtime status card |
+| frontend-visible files changed and no known URL exists | suggest `/god-test-runtime` with local URL setup, defer deployed URL | proposition |
+| security-sensitive files changed | auto-spawn only inside harden, hotfix, launch, or project run; otherwise suggest `/god-harden` | proposition |
+| dependency files changed | auto-spawn only inside update-deps, hygiene, or approved project run; otherwise suggest `/god-update-deps` | proposition |
+| full project run complete or hygiene stale | suggest `/god-hygiene` | proposition |
+
+Never use this matrix to auto-run Level 4 actions: deployed staging against a
+guessed URL, production launch, provider dashboard access, broad dependency
+upgrades, destructive repair, review clearing, Critical security acceptance, or
+git stage, commit, push, package, release, or publish.
+
+Every auto action must emit either `Auto-invoked:`, `Sync status:`, or a
+proposition explaining why it did not run.
+
 ## Detection-Driven Tier 1 Routing
 
 After PRD and before ARCH, branch on UI or product-experience presence:
@@ -299,7 +342,7 @@ After PRD and before ARCH, branch on UI or product-experience presence:
 
 ## Linkage and Reverse-Sync
 
-Reverse-sync runs incrementally, not just at end-of-arc:
+Reverse-sync runs incrementally, not just at the end of the project run:
 
 - After each Tier 2 build wave commit: spawn `god-updater` in
   reverse-sync mode. Calls `lib/reverse-sync.run(projectRoot)`:
@@ -314,14 +357,14 @@ Reverse-sync runs incrementally, not just at end-of-arc:
   drift detection, REVIEW-REQUIRED.md finalization, AGENTS.md fence
   refresh.
 
-## Mid-Arc DESIGN/PRODUCT Change Detection
+## Mid-Run DESIGN/PRODUCT Change Detection
 
 Before starting each tier, hash-check DESIGN.md and PRODUCT.md against
 last known hash in state.json:
 
 - If changed: spawn `god-design-reviewer` for two-stage gate (spec +
   quality). Three verdicts: PASS / WARN / BLOCK.
-  - BLOCK: append to `.godpowers/design/REJECTED.md`; pause arc;
+  - BLOCK: append to `.godpowers/design/REJECTED.md`; pause the project run;
     surface diff + reason. Critical-finding gate trigger.
   - WARN: continue with warnings logged to events.jsonl.
   - PASS: continue normal propagation pipeline (impact analysis ->
@@ -339,11 +382,11 @@ The critical-finding gate fires on:
 Only Critical security findings always pause, including under --yolo.
 Everything else must first enter the autonomous repair loop below. A failed
 typecheck, lint, check, unit test, generated artifact lint, or have-nots pass is
-not a reason to declare the arc complete. It is work.
+not a reason to declare the project run complete. It is work.
 
 ## Autonomous Repair Loop
 
-Godpowers full-arc means: plan, build, verify, repair, ship, sync. Do not stop
+Godpowers full project run means: plan, build, verify, repair, ship, sync. Do not stop
 at "artifacts generated" when the repo is still red.
 
 When any mechanical verification fails:
@@ -374,7 +417,7 @@ Do this:
 Under `--yolo`, the repair loop auto-runs. It may commit atomic repair commits
 after tests pass. If a git remote exists and the user passed an explicit push
 flag or the project intent says pushing is allowed, push after the green commit
-and then continue the arc. Pushing is not a terminal state.
+and then continue the project run. Pushing is not a terminal state.
 
 ## Shipping Closure Protocol
 
@@ -382,7 +425,7 @@ The shipping tier must not end by listing a broad provider checklist. God Mode
 either ships, creates the automation needed to ship, or pauses on one precise
 external access bundle.
 
-Default behavior: do not pause mid-arc just to ask for a staging URL. If the
+Default behavior: do not pause mid-run just to ask for a staging URL. If the
 user has not explicitly requested deployed staging verification and no live
 target URL is evidenced, complete every local and CI-verifiable shipping gate,
 write the missing deployed-origin item to
@@ -422,7 +465,7 @@ For deploy, observe, harden, and launch:
    `sign off local-only` to finish with deployed verification deferred, or run
    `/god-deploy --stage` later."
 9. Do not say "Suggested next" for a blocked shipping tier. Say either
-   `Arc complete`, `Arc complete with deployed verification deferred`, or
+   `Project run complete`, `Project run complete with deployed verification deferred`, or
    `PAUSE: external access required`, with the exact artifact that lists the
    required bundle.
 
@@ -431,7 +474,7 @@ For deploy, observe, harden, and launch:
 Use this order when external access is missing:
 
 1. If no live target URL is known from explicit evidence, defer the deployed
-   staging origin request unless the user asked to stage now or the arc has
+   staging origin request unless the user asked to stage now or the project run has
    reached final sign-off.
 2. When staging is requested or final sign-off begins, ask for the deployed
    staging origin only.
@@ -496,8 +539,8 @@ requested or final sign-off begins.
 5. Spawn the appropriate specialist agent in a fresh context
 6. Verify their output exists on disk
 7. Run have-nots check on the artifact
-8. If pass: update PROGRESS.md, sync CHECKPOINT.md, print the "Step result"
-   card, then move to next sub-step
+8. If pass: update PROGRESS.md, sync CHECKPOINT.md, run the proactive
+   auto-invoke sweep, print the "Step result" card, then move to next sub-step
 9. If fail and repairable: print the failed result card, then enter the
    autonomous repair loop
 10. If fail and human-only: pause with the smallest needed question
@@ -522,7 +565,8 @@ For single-agent sub-steps:
 | Harden | god-harden-auditor | code | .godpowers/harden/FINDINGS.md |
 
 For all single-agent sub-steps:
-1. Spawn the agent in a fresh context (Task tool)
+1. Spawn the agent in a fresh context using the host platform's native agent
+   spawning mechanism
 2. Pass `--yolo` flag if active so the agent auto-picks defaults
 3. Wait for the agent to return
 4. Verify artifact exists on disk
@@ -592,16 +636,31 @@ ecosystem.
 
 ### Mandatory Final Sync (always, including --yolo)
 
-Before declaring the arc complete, ALWAYS run /god-sync:
+Before declaring the project run complete, ALWAYS run /god-sync:
 
 1. Spawn god-updater in fresh context
 2. Verify final consistency across all 14 artifact categories:
    - All Tier 1-3 artifacts written and pass have-nots
    - Capture artifacts (BACKLOG, SEEDS, TODOS, THREADS) noted as
      "not-yet-created" if absent (graceful, not a failure)
-3. Update SYNC-LOG.md with the arc completion entry
+3. Update SYNC-LOG.md with the project-run completion entry
 4. Update state.json with all final tier statuses
 
+Display the sync status before the final completion block:
+
+```
+Sync status:
+  Trigger: /god-mode final sync
+  Agent: god-updater spawned
+  Local syncs:
+    + reverse-sync: <counts and result>
+    + 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
+```
+
 This step runs regardless of flags:
 - /god-mode -> sync runs
 - /god-mode --yolo -> sync runs (no pause; auto-applies)
@@ -609,7 +668,7 @@ This step runs regardless of flags:
 - /god-mode --with-hygiene -> sync runs PLUS hygiene check
 
 After sync, re-run the final verification commands. If any are red, return to
-the autonomous repair loop. This ensures every full-arc run leaves the project
+the autonomous repair loop. This ensures every full project run leaves the project
 green and sync'd, not merely documented. The artifact coverage is consistent
 across all 14 categories.
 
@@ -618,7 +677,39 @@ across all 14 categories.
 After Launch completes, write a transition message:
 
 ```
-Godpowers full-arc complete.
+Godpowers project run complete.
+
+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>
+
+What changed:
+  1. <highest-signal user-visible change>
+  2. <highest-signal user-visible change>
+
+Validation:
+  + <command>: <result>
+
+Proactive checks:
+  Checkpoint: <fresh | refreshed | stale>
+  Reviews: <none | N pending, suggest /god-review-changes>
+  Sync: <fresh | suggested | local helper ran>
+  Docs: <fresh | suggested | drift-check spawned>
+  Runtime: <not-applicable | suggested | browser test spawned>
+  Security: <clear | suggested | harden spawned>
+  Dependencies: <clear | suggested | deps audit spawned>
+  Hygiene: <fresh | suggest /god-hygiene>
+
+Open items:
+  1. <none, or deployed staging deferred, pending review, unstaged files, etc.>
 
 Project is now in steady state. From here, ongoing work uses these workflows:
 
@@ -635,11 +726,42 @@ Periodic hygiene:
   Quality audit:          /god-audit
   Health check:           /god-hygiene (combines audit + deps + docs)
 
-Or describe what you want to do and /god-next will route.
+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
 ```
 
 Update PROGRESS.md status to `steady-state-active`.
 
+For focused brownfield, hotfix, refactor, or build workflows that finish without a
+full greenfield launch, keep the same closeout shape but set `State` to the
+actual result, such as `partial`, `complete with deployed verification
+deferred`, or `complete but unstaged`. Never end with only changed paths and
+validation results.
+
+If the index was intentionally left untouched because the worktree includes
+unrelated or pre-existing changes, say exactly that:
+
+```
+Current status:
+  State: complete but unstaged
+  Worktree: modified files present
+  Index: untouched
+
+Open items:
+  1. Review the diff and stage only the intended files.
+
+Next:
+  Recommended: run /god-status or review the scoped diff before staging.
+  Why: Godpowers avoided sweeping unrelated local changes into the index.
+```
+
 ### Optional Post-Launch Hygiene (--with-hygiene)
 
 If user invoked `/god-mode --with-hygiene` (or `--yolo` includes hygiene by
@@ -657,7 +779,7 @@ If any hygiene pass surfaces issues:
 
 ### --yolo Behavior in Hygiene
 
-`--yolo` skips hygiene by default (it's noise after a successful arc). User
+`--yolo` skips hygiene by default (it is noise after a successful project run). User
 can opt in with `--yolo --with-hygiene`.
 
 If hygiene IS enabled under --yolo:
@@ -687,7 +809,7 @@ Pass `--yolo` to every spawned specialist agent. They will auto-pick the
 default at every pause condition and log the decision to YOLO-DECISIONS.md.
 
 For brownfield and bluefield, run `/god-preflight` automatically before
-archaeology, reconstruction, arc-ready, pillars, or refactor work when
+archaeology, reconstruction, project-run readiness, pillars, or refactor work when
 `.godpowers/preflight/PREFLIGHT.md` is absent. Treat the preflight report as
 the routing baseline. Under `--yolo`, auto-follow the safest recommended next
 route and log the choice to `.godpowers/YOLO-DECISIONS.md`.
@@ -709,7 +831,7 @@ for human resolution when no safe automatic reconcile route exists.
 
 These are the only --yolo carve-outs. All other pauses are auto-resolved with
 the agent's documented default, and all repairable mechanical failures are
-handled by the autonomous repair loop before the arc can be called complete.
+handled by the autonomous repair loop before the project run can be called complete.
 
 ### Pause Format
 
@@ -732,14 +854,21 @@ Show:
 - concise phase status
 - before each visible tier/sub-step, a short "what will happen" card
 - after each visible tier/sub-step, a short "what happened" card
+- every auto-invoked command, agent, and local runtime helper using an
+  `Auto-invoked:` or `Sync status:` card
 - durable state detected from disk
 - commands being run and whether they passed or failed
 - scoped file changes
 - final validation summary
-- `Arc complete` or `PAUSE: external access required`
+- final current status from disk, including progress, lifecycle, open items,
+  worktree/index state, and recommended next action
+- plain-language workflow names. Say "project run" or "workflow" instead of
+  unexplained "arc" in visible output
+- PRD and roadmap visibility when those artifacts exist or are expected
+- `Project run complete` or `PAUSE: external access required`
 
 Hide:
-- raw Task input
+- raw spawn input
 - "Hard instructions" sections
 - spawned-agent prompt text
 - system, developer, AGENTS.md, or internal policy recitations
@@ -751,6 +880,36 @@ user-facing question. Do not expose the rule itself. Example: ask for
 `STAGING_APP_URL=<deployed staging origin>` at final sign-off rather than
 showing the Shipping Closure Protocol.
 
+### Auto-Invoked Work Cards
+
+Every automatic step that mutates state, writes artifacts, validates gates, or
+spawns an agent must leave a visible trace in the transcript.
+
+Use this shape:
+
+```
+Auto-invoked:
+  Trigger: <event that caused the automatic step>
+  Agent: <agent name, or none, local runtime only>
+  Local syncs:
+    + <helper>: <result>
+  Artifacts: <changed files, no-op, or deferred>
+  Log: <path, or none>
+```
+
+Required auto-invoked cards:
+- `/god-preflight` started automatically for brownfield or bluefield work
+- standards checks between routed stages
+- design-reviewer checks after DESIGN.md or PRODUCT.md changes
+- `god-updater` spawned for reverse-sync or final sync
+- local `lib/reverse-sync.run` calls, including `/god-scan`
+- Pillars sync through `lib/pillars.pillarizeExisting` or
+  `lib/pillars.applyArtifactSync`
+- checkpoint refresh through `lib/checkpoint.syncFromState`
+- AI-tool context refresh through `god-context-writer`
+
+If an automatic step is skipped, still report it with the skipped reason.
+
 ## Step Narration Protocol
 
 Godpowers must make its work trackable without exposing hidden prompts or
@@ -792,7 +951,7 @@ Rules:
 - Use `lib/state.progressSummary(stateJson)` for the percentage and step count
   whenever state.json is available.
 - Use artifact paths and verification evidence from disk, not memory.
-- Do not print raw Task input, hidden instructions, or full file loadout lists.
+- Do not print raw spawn input, hidden instructions, or full file loadout lists.
 - If a step is blocked, do not show a generic "Suggested next"; show the
   smallest concrete unblock action.
 
@@ -1036,10 +1195,10 @@ rewrite-candidate and no concrete existing evidence is removed.
 ### Mode E: Bluefield (auto-detected)
 - No existing code in current dir
 - BUT org-context.yaml found (in current dir, parent, or grandparent)
-- Run full arc with all decisions constrained by org context
+- Run full project run with all decisions constrained by org context
 - Spawn god-org-context-loader first to load constraints
 - Run greenfield simulation audit after org-context, then run
-  god-greenfieldifier so the arc has an approved artifact plan before PRD.
+  god-greenfieldifier so the project run has an approved artifact plan before PRD.
   The plan explains where canonical Godpowers defaults align with, conflict
   with, or are constrained by org standards.
 - All downstream agents (god-stack-selector, god-architect, god-deploy-engineer,

package/agents/god-reconciler.md

@@ -188,7 +188,7 @@ Run this sequence? (yes / show alternatives / cancel)
 ## Missing artifacts (graceful handling)
 
 Not every artifact exists in every project. Tier 1-3 artifacts get created
-during the arc (`/god-mode` produces 10 of them). Capture artifacts
+during the project run (`/god-mode` produces 10 of them). Capture artifacts
 (BACKLOG, SEEDS, TODOS, THREADS) are lazy: they only exist if the user
 has used those commands.
 

package/agents/god-updater.md

@@ -111,6 +111,12 @@ After feature work, every artifact that was impacted needs to reflect reality.
   `drift-count`, `review-required-items`
 - Emit events: `linkage.snapshot`, `drift.detected` (per finding),
   `review-required.populated`
+- Report counts in the final sync status:
+  - scanned files
+  - links added, removed, or unchanged
+  - fenced footers updated
+  - drift findings
+  - REVIEW-REQUIRED.md items created
 
 ### Pillars sync (native context)
 - Call `lib/pillars.pillarizeExisting(projectRoot)` if Pillars is absent or
@@ -122,6 +128,8 @@ After feature work, every artifact that was impacted needs to reflect reality.
   immediately and log the decision to `.godpowers/YOLO-DECISIONS.md`.
 - Never read every file in `agents/` as project context. Only files with
   `pillar:` frontmatter are Pillars files.
+- Report whether Pillars work was initialized, applied, proposed, skipped, or
+  no-op.
 
 ### AI-tool context refresh (always, unless never-ask)
 - Read `state.json` for `project.context-prompt-answered`
@@ -134,16 +142,36 @@ After feature work, every artifact that was impacted needs to reflect reality.
 - Idempotent: if content matches, no write occurs
 - Never touches content outside the `<!-- godpowers:begin -->` /
   `<!-- godpowers:end -->` fence
+- Report whether context refresh spawned `god-context-writer`, changed files,
+  no-oped, or skipped because the project opted out.
+
+### Checkpoint sync
+- After state changes, refresh `.godpowers/CHECKPOINT.md` from disk state using
+  `lib/checkpoint.syncFromState(projectRoot, { nextCommand, nextReason })`
+  when the runtime is available.
+- If checkpoint sync is unavailable in the host tool, say it was skipped and
+  include the reason.
+- Report the checkpoint path and whether it was created, updated, unchanged,
+  or skipped.
 
 ## Output
 
-Write summary to `.godpowers/SYNC-LOG.md` (append-only):
+Write summary to `.godpowers/SYNC-LOG.md` (append-only). The summary must
+include both user-visible status and machine-checkable counts:
 
 ```markdown
 ## Sync: [intent] [timestamp]
 
 Triggered by: [recipe name]
 
+Sync status:
+- Trigger: [manual /god-sync | /god-mode final sync | recipe closeout]
+- Agent: god-updater
+- Reverse-sync: scanned [N] files, updated [N] footers, created [N] review items
+- Pillars sync: [applied/proposed/no-op/skipped], [N] pillar files
+- Checkpoint sync: [created/updated/no-op/skipped] .godpowers/CHECKPOINT.md
+- Context refresh: [spawned god-context-writer/no-op/skipped], [N] files
+
 Updated:
 - prd/PRD.md: added requirement P-MUST-12
 - arch/ARCH.md: added ADR-007 (auth refactor)
@@ -157,11 +185,32 @@ Updated:
 
 Have-nots re-validated: all passing.
 
-Suggested next: /god-status
+Next: /god-status
 ```
 
 Update PROGRESS.md with the latest tier statuses.
 
+Return a compact user-facing closeout in the same shape:
+
+```
+Sync complete.
+
+Sync status:
+  Trigger: <trigger>
+  Agent: god-updater
+  Local syncs:
+    + reverse-sync: <counts and result>
+    + 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
+
+Next:
+  Recommended: /god-status
+  Why: confirm the disk-derived project state after sync.
+```
+
 ## Have-Nots
 
 Sync FAILS if:

package/bin/install.js

@@ -186,6 +186,9 @@ function installSkillFile(srcFile, skillsDest, runtimeKey, targetName = null) {
   const baseName = targetName || path.basename(srcFile, '.md');
   if (runtimeKey === 'codex') {
     const skillDir = path.join(skillsDest, baseName);
+    if (fs.existsSync(skillDir)) {
+      fs.rmSync(skillDir, { recursive: true, force: true });
+    }
     ensureDir(skillDir);
     fs.copyFileSync(srcFile, path.join(skillDir, 'SKILL.md'));
     return;
@@ -647,7 +650,7 @@ function main() {
     log('');
     log(`\x1b[36mNext steps:\x1b[0m`);
     log(`  1. Open your AI coding tool in any project directory`);
-    log(`  2. Type: \x1b[36m/god-mode\x1b[0m for full autonomous arc`);
+    log(`  2. Type: \x1b[36m/god-mode\x1b[0m for the full autonomous project run`);
     log(`     Or:   \x1b[36m/god-next\x1b[0m to see what to run next`);
     log(`     Or:   \x1b[36m/god-init\x1b[0m to start a new project`);
     log('');

package/hooks/session-start.sh

@@ -52,7 +52,7 @@ if [ -f "$STATE_FILE" ]; then
     jq -r '
       "  project: " + (.project.name // "(unnamed)"),
       "  mode: " + (.mode // "?") + (if ."mode-d-suite" then " (in suite)" else "" end),
-      "  lifecycle: " + (."lifecycle-phase" // "in-arc")
+      "  lifecycle: " + (if (."lifecycle-phase" // "in-arc") == "in-arc" then "in progress" else (."lifecycle-phase" // "in-arc") end)
     ' "$STATE_FILE" 2>/dev/null || head -20 "$STATE_FILE"
   else
     head -20 "$STATE_FILE"
@@ -66,7 +66,7 @@ fi
 cat <<'EOF'
 
 Next step: run /god-next  (it inspects disk state and proposes the next command)
-Or:       /god-mode for the full autonomous arc
+Or:       /god-mode for the full autonomous project run
 Or:       /god-help to see the catalog
 Or:       /god-status for the full project snapshot
 

package/lib/checkpoint.js

@@ -128,6 +128,9 @@ function write(projectRoot, state) {
   const facts = (state.facts || []).slice(0, MAX_FACTS);
   const factsHash = sha256(JSON.stringify(facts));
   const progress = state.progress || null;
+  const lifecycleDisplay = state.lifecycle === 'in-arc'
+    ? 'in progress'
+    : (state.lifecycle || 'in progress');
 
   const fm = [
     '---',
@@ -171,7 +174,7 @@ function write(projectRoot, state) {
     '',
     `- Project: **${state.project || 'unnamed'}**`,
     `- Mode: **${state.mode || '?'}**${state.modeDSuite ? ' (in multi-repo suite)' : ''}`,
-    `- Lifecycle phase: **${state.lifecycle || 'in-arc'}**`,
+    `- Lifecycle phase: **${lifecycleDisplay}**`,
     progressLine,
     `- Current tier: **${state.currentTier || 'tier-0'}** / **${state.currentSubstep || 'orchestration'}**`,
     `- Last action: \`${state.lastAction || 'unknown'}\` by ${state.lastActor || 'unknown'} at ${ts}`,

package/lib/context-writer.js

@@ -98,7 +98,7 @@ function buildCanonicalContent(state, opts = {}) {
   lines.push('- `/god-status` - re-derive state from disk');
   lines.push('- `/god-next` - what to run next, with reason');
   lines.push('- `/god <free text>` - match intent to a recipe');
-  lines.push('- `/god-mode` - run the full autonomous arc');
+  lines.push('- `/god-mode` - run the full autonomous project run');
   lines.push('- `/god-lint` - validate artifacts against have-nots');
   lines.push('- `/god-scan` - rebuild linkage map from code');
   lines.push('- `/god-review-changes` - walk REVIEW-REQUIRED.md');

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "godpowers",
-  "version": "1.6.9",
+  "version": "1.6.11",
   "description": "AI-powered development system: 106 slash commands and 39 specialist agents that take a project from raw idea to hardened production. Runs inside Claude Code, Codex, Cursor, Windsurf, Gemini, and 10+ other AI coding tools.",
   "bin": {
     "godpowers": "./bin/install.js"

package/references/HAVE-NOTS.md

@@ -454,7 +454,7 @@ Trust boundaries declared in docs but absent in code. Fail.
 
 ## Workflow-Specific Have-Nots
 
-These apply to artifacts produced by non-arc workflows (postmortem, spike,
+These apply to artifacts produced by focused workflows (postmortem, spike,
 migration, docs, deps).
 
 ### Postmortem Have-Nots

package/references/orchestration/SCALE-DETECTION.md

@@ -8,7 +8,7 @@
 |-------|---------|---------------------|
 | Trivial | Single-file change, bug fix, config tweak | /god-fast (skip planning) |
 | Small | One feature, one service, <1 week | /god-quick OR lightweight /god-mode |
-| Medium | Multiple features, 1-3 services, 1-4 weeks | /god-mode (full arc) |
+| Medium | Multiple features, 1-3 services, 1-4 weeks | /god-mode (full project run) |
 | Large | Multiple services, team coordination, 1-3 months | /god-mode + /god-sprint (sprints) |
 | Enterprise | Multiple teams, compliance, 3+ months | /god-mode + extension packs (security, etc.) |
 

package/references/shared/GLOSSARY.md

@@ -5,7 +5,7 @@
 
 ## Core abstractions
 
-**Tier**: a phase of the dev arc (0: Orchestration, 1: Planning, 2: Building, 3: Shipping).
+**Tier**: a phase of the development workflow (0: Orchestration, 1: Planning, 2: Building, 3: Shipping).
 
 **Sub-step**: a bounded unit within a tier (PRD, ARCH, Roadmap, Stack, Repo, Build, Deploy, Observe, Launch, Harden).
 

package/references/shared/ORCHESTRATORS.md

@@ -69,7 +69,7 @@ frontmatter. There's no proprietary binary state. To leave:
 ## What Godpowers does not try to be
 
 Godpowers is opinionated about: artifact discipline, bidirectional
-linkage, the four-tier arc, the single-orchestrator rule, headless
+linkage, the four-tier workflow, the single-orchestrator rule, headless
 runtime verification, and the substitution / three-label / have-nots
 gates. It is intentionally not opinionated about: team ceremonies,
 sprint cadence, ticket trackers, knowledge graphs, prompt engineering

package/routing/god-mode.yaml

@@ -2,7 +2,7 @@ apiVersion: godpowers/v1
 kind: CommandRouting
 metadata:
   command: /god-mode
-  description: Full autonomous arc
+  description: Full autonomous project run
   tier: 0
 
 prerequisites:

package/routing/god-preflight.yaml

@@ -2,7 +2,7 @@ apiVersion: godpowers/v1
 kind: CommandRouting
 metadata:
   command: /god-preflight
-  description: Read-only intake audit before arc-ready and pillars
+  description: Read-only intake audit before project-run readiness and pillars
   tier: 0
 
 prerequisites: