godpowers 1.6.10 → 1.6.11

package/CHANGELOG.md

@@ -5,6 +5,45 @@ All notable changes to Godpowers will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.6.11] - 2026-05-16
+
+Auto-invoke visibility and platform-neutral spawning patch.
+
+### Added
+- Added a core auto-invoke visibility rule requiring Godpowers to show when it
+  automatically runs a command, spawns an agent, or calls a local runtime
+  helper.
+- Added a proactive auto-invoke policy with four levels: read-only
+  suggestions, visible local helpers, bounded specialist agent spawns, and
+  explicit-approval-only actions.
+- Added proactive checks to `/god-next`, `/god-status`, and God Mode closeouts
+  so users can see checkpoint, review, sync, docs, runtime, security,
+  dependency, and hygiene opportunities without asking.
+- Added docs drift, runtime verification, and review queue guidance for
+  proactive closeouts.
+- Added `docs/auto-invoke-visibility.md` as a local design note for the
+  auto-invoke policy.
+
+### Changed
+- Replaced Claude-specific "Task tool" spawning wording in high-traffic skills
+  with platform-neutral host-agent spawning language.
+- Clarified that Claude, Codex, Cursor, Windsurf, Gemini, OpenCode, Copilot,
+  Augment, Trae, Cline, Kilo, Antigravity, Qwen, CodeBuddy, and Pi may expose
+  specialist spawning differently while sharing the same Markdown agent
+  contracts.
+- Updated the Codex installer path to replace skill directories before copying
+  `SKILL.md`, preventing stale nested files from older install shapes.
+- `/god-sync`, `/god-scan`, `god-updater`, and `god-orchestrator` now describe
+  local sync helpers separately from spawned agents.
+
+### Guardrails
+- Production launch, guessed staging URLs, provider dashboards, credentials,
+  destructive repair, review clearing, Critical security acceptance, git
+  staging, commits, pushes, packages, releases, and npm publishing still require
+  explicit user intent.
+- If a host platform cannot provide a true fresh-context spawn, Godpowers must
+  say so instead of pretending a background agent ran.
+
 ## [1.6.10] - 2026-05-16
 
 Progress visibility and plain-language closeout patch.

package/README.md

@@ -2,7 +2,7 @@
 
 [![CI](https://github.com/aihxp/godpowers/actions/workflows/ci.yml/badge.svg)](https://github.com/aihxp/godpowers/actions/workflows/ci.yml)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
-[![Version](https://img.shields.io/badge/version-1.6.10-blue)](CHANGELOG.md)
+[![Version](https://img.shields.io/badge/version-1.6.11-blue)](CHANGELOG.md)
 [![npm](https://img.shields.io/npm/v/godpowers.svg)](https://www.npmjs.com/package/godpowers)
 
 **Ship fast. Ship right. Ship everything. Ship accountably.**
@@ -12,10 +12,10 @@ idea to hardened production. It runs as **slash commands inside your AI coding
 tool** (Claude Code, Codex, Cursor, etc.) that orchestrate **specialist agents**
 in fresh contexts to do the work.
 
-Version 1.6.10 keeps the stable Godpowers surface while making progress more
-visible: user-facing output now prefers "project run" over internal "arc"
-jargon and status closeouts show PRD, roadmap, milestone, and completion
-position when available.
+Version 1.6.11 keeps the stable Godpowers surface while making automatic work
+more visible and portable: syncs, proactive checks, and specialist spawning now
+report what ran, what changed, and which host-platform agent mechanism is being
+used.
 
 It fuses four disciplines into one unified workflow:
 
@@ -50,6 +50,13 @@ The installer copies:
 - Codex agent metadata to `<runtime>/agents/*.toml`
 - SessionStart hook (Claude Code only) to `<runtime>/hooks/`
 
+Agent spawning is host-native. Claude uses its native agent/task interface,
+Codex uses installed `agents/*.toml` metadata backed by the same Markdown agent
+contracts, and the other runtimes use their supported agent or subagent
+mechanism against the installed `agents/god-*.md` files. If a host cannot
+provide a true fresh-context spawn, Godpowers must report that limitation
+instead of pretending a background agent ran.
+
 ## Usage
 
 Open your AI coding tool in any project directory and type:

package/RELEASE.md

@@ -1,11 +1,11 @@
-# Godpowers 1.6.10 Release
+# Godpowers 1.6.11 Release
 
 Date: 2026-05-16
 
-Godpowers 1.6.10 makes progress easier to understand while work is running and
-when it closes. The goal of this patch is to keep user-facing output from
-requiring internal "arc" vocabulary and to show PRD, roadmap, milestone, and
-completion position wherever status is reported.
+Godpowers 1.6.11 makes automatic work easier to trust across supported AI
+coding tools. The release keeps the existing 106 slash commands, 39 specialist
+agents, 13 workflows, and 36 recipes, while clarifying when Godpowers spawned
+an agent, called a local runtime helper, or only suggested the next action.
 
 ## What is stable
 
@@ -14,7 +14,8 @@ completion position wherever status is reported.
 - 13 executable workflows
 - 36 intent recipes
 - 15-runtime installer
-- Codex installs with 39 generated `god-*.toml` agent metadata files
+- Codex installs with generated `god-*.toml` agent metadata files
+- Markdown specialist agent contracts at `<runtime>/agents/god-*.md`
 - Safe-sync routing before deploy, observe, harden, launch, or god-mode work
 - Critical harden finding gate before launch
 - Native Pillars project context through `AGENTS.md` and `agents/*.md`
@@ -22,8 +23,6 @@ completion position wherever status is reported.
 - Core schemas: intent, state, events, workflow, routing, recipes, extension
   manifests
 - Extension pack compatibility range for the 1.x line
-- Domain precision through `.godpowers/domain/GLOSSARY.md` and DG-01 through
-  DG-05 checks
 - GSD-style proposition closeouts for exploratory, diagnostic, audit,
   lifecycle, status, reconciliation, and decision-support outputs
 - Plain-language project-run wording in user-facing reports
@@ -31,58 +30,60 @@ completion position wherever status is reported.
 
 ## What is new
 
-- The core Godpowers skill now defines "arc" as internal vocabulary and tells
-  user-facing output to prefer "project run", "workflow", "phase", "current
-  step", or "current milestone".
-- `/god-mode`, `god-orchestrator`, `/god-status`, `/god-next`, and
-  `/god-lifecycle` now include planning visibility guidance for PRD, roadmap,
-  milestone, and percent complete when the information is available.
-- The installer, session-start hook, `/god` front door, routing descriptions,
-  workflow descriptions, and high-traffic skill propositions now use
-  project-run language instead of unexplained "arc" wording.
-- Checkpoint and session-start summaries display lifecycle `in-arc` as
-  "in progress" while preserving the internal state key for compatibility.
-
-## What 1.6.10 means
-
-Godpowers 1.6.10 does not expand the public command surface. It changes how
-Godpowers explains itself: the user should see the current project run, PRD,
-roadmap, milestone, completion percentage, open items, and next action without
-decoding internal terminology.
-
-Internal workflow names and state constants such as `full-arc.yaml` and
-`in-arc` remain unchanged for compatibility. Visible reports should translate
-them to plain language.
-
-Safe sync and unresolved Critical harden findings remain release-truth gates.
-Per-repo Quarterback ownership remains intact for Mode D suite work.
-
-## Stability policy
-
-During the 1.x stability window, do not add broad new command families, change
-schema formats, or rename public artifacts without evidence from real use.
-
-The `v1.6.10` git tag points to the release commit that matches the npm
-`godpowers@1.6.10` package. Public publishes should prefer the tag-triggered
-GitHub workflow so npm provenance, git history, and release notes stay aligned.
-
-Allowed changes:
-
-- Critical bug fixes
-- Documentation clarity
-- Test coverage for frozen behavior
-- Compatibility fixes for supported AI coding tools
-- Small fixes that make existing 1.x behavior work as documented
-
-Deferred changes:
-
-- New lifecycle phases
-- New schema versions
-- Pillars format changes
-- Major routing semantics
-- Large extension API changes
-
-## Adoption ask
-
-Run `npm run release:check` before publishing changes. Report any release path
-step that still depends on memory, manual inspection, or local machine state.
+- The master skill now defines a proactive auto-invoke policy with four levels:
+  read-only suggestions, visible local helpers, bounded specialist agent spawns,
+  and explicit-approval-only actions.
+- `/god-next`, `/god-status`, and God Mode closeouts now include proactive
+  checks for checkpoint freshness, pending reviews, sync state, docs drift,
+  runtime verification, security, dependencies, and hygiene.
+- `/god-sync`, `/god-scan`, `god-updater`, and `god-orchestrator` now distinguish
+  spawned agents from local runtime helpers such as reverse-sync, Pillars sync,
+  checkpoint sync, and context refresh.
+- Docs drift, runtime verification, and review queue workflows now document when
+  they may be suggested or auto-invoked.
+- Spawning instructions now use platform-neutral host-agent language instead of
+  Claude-specific "Task tool" wording.
+- The installer now replaces Codex skill directories before writing `SKILL.md`,
+  which removes stale nested files from older Codex install shapes.
+
+## Platform behavior
+
+Claude Code, Codex, Cursor, Windsurf, Gemini, OpenCode, Copilot, Augment,
+Trae, Cline, Kilo, Antigravity, Qwen, CodeBuddy, and Pi all receive the same
+portable Markdown agent contracts. Codex also receives `god-*.toml` files as
+its registry adapter.
+
+If a host platform cannot provide a true fresh-context agent spawn, Godpowers
+must say so visibly and report the work as local runtime only or simulated in
+current context. It must not imply that a detached background agent ran.
+
+## Safety policy
+
+Godpowers may proactively suggest next steps and may run directly evidenced
+local helpers. It may spawn bounded agents only when the current workflow owns
+that surface.
+
+Godpowers still must not auto-run these without explicit user intent:
+
+- deployed staging verification against a guessed URL
+- production launch
+- provider dashboard, admin console, DNS, credential, or secret checks
+- broad dependency upgrades
+- destructive repair, rollback, reset, delete, or cleanup
+- clearing `.godpowers/REVIEW-REQUIRED.md`
+- accepting Critical security findings
+- git stage, commit, push, package, release, or publish
+
+## Validation
+
+Release validation should include:
+
+- `node scripts/validate-skills.js`
+- `bash scripts/smoke.sh`
+- `node scripts/test-agent-validator.js`
+- `node scripts/test-install-smoke.js`
+- `node scripts/check-package-contents.js`
+- `npm run release:check`
+
+The `v1.6.11` git tag should point to the release commit that matches the npm
+`godpowers@1.6.11` package.

package/SKILL.md

@@ -49,6 +49,19 @@ unresolved Critical security findings.
 Every execution agent gets a fresh context window. The orchestrator is thin; it
 spawns workers with full context budgets. This defeats context rot.
 
+Spawning is platform-neutral. Use the host platform's native agent spawning
+mechanism and the installed `agents/god-*.md` contract:
+- Claude Code: spawn the matching Markdown agent from `~/.claude/agents/`.
+- Codex: spawn the matching Codex agent type from `~/.codex/agents/*.toml`;
+  the Markdown copy remains the source contract.
+- Cursor, Windsurf, Gemini, OpenCode, Copilot, Augment, Trae, Cline, Kilo,
+  Antigravity, Qwen, CodeBuddy, and Pi: use the platform's supported agent or
+  subagent mechanism against the installed Markdown files.
+
+When a platform cannot spawn a true fresh-context agent, say so plainly,
+preserve the same role contract, and report `Agent: none, local runtime only`
+or `Agent: simulated in current context` in the visible auto-invoked card.
+
 ### 6. TDD Enforcement
 Tests are written before implementation. Code written before its test is flagged
 and must be rewritten. RED-GREEN-REFACTOR is not optional.
@@ -156,6 +169,103 @@ and roadmap visibility when those files exist or are expected. Show whether
 the PRD is done, whether the roadmap exists, which milestone or tier is active,
 how close the tracked workflow is to completion, and the next concrete move.
 
+### 12. Auto-Invoke Visibility
+When Godpowers automatically runs another command, agent, or local runtime
+helper, show the user what happened. Do not describe these as "background"
+unless they are truly detached from the current run. Most Godpowers sync work
+is auto-invoked but still part of the current workflow.
+
+Use this shape whenever an automatic step runs or is skipped:
+
+```
+Auto-invoked:
+  Trigger: <what caused this automatic step>
+  Agent: <god-updater | god-context-writer | none, local runtime only>
+  Local syncs:
+    + <reverse-sync | pillars-sync | checkpoint-sync | context-refresh>: <result or skipped reason>
+  Artifacts: <changed files, no-op, or deferred>
+  Log: <SYNC-LOG.md, CHECKPOINT.md, REVIEW-REQUIRED.md, or none>
+```
+
+If no agent was spawned, say so plainly:
+
+```
+Agent: none, local runtime only
+Why: this path calls lib/reverse-sync.run directly
+```
+
+Automatic steps that especially need visible reporting:
+- `/god-sync` spawning `god-updater`
+- `god-updater` calling reverse-sync, Pillars sync, checkpoint sync, or
+  AI-tool context refresh
+- `/god-mode` mandatory final sync
+- standards checks between routed stages
+- brownfield and bluefield automatic `/god-preflight`
+- DESIGN/PRODUCT change detection that spawns `god-design-reviewer`
+- `/god-scan` when it runs reverse-sync directly without an agent
+- checkpoint refresh after state mutations
+
+### 13. Proactive Auto-Invoke Policy
+Godpowers should be proactive from disk evidence, not from guesswork. Before
+auto-invoking anything, classify the action by risk and apply the safest
+allowed behavior.
+
+#### Level 1: Auto-suggest, read-only
+Run or apply these by default in every relevant closeout:
+- Compute `/god-next` routing after successful commands.
+- Show `/god-status` style progress after `/god-sync`, `/god-scan`, and
+  `/god-mode`.
+- Suggest `/god-review-changes` when `.godpowers/REVIEW-REQUIRED.md` has
+  pending items.
+- Suggest `/god-hygiene` after a full project run, after 30 days, or when
+  status shows stale docs, deps, or review queues.
+- Suggest `/god-locate` when `.godpowers/CHECKPOINT.md` is missing, stale, or
+  conflicts with `state.json`.
+
+#### Level 2: Auto-run local helpers, visible and logged
+Run these local runtime helpers automatically when their trigger is present:
+- `lib/checkpoint.syncFromState` after every `state.json` or
+  `PROGRESS.md` mutation.
+- Lightweight reverse-sync or linkage scan after code or artifact edits.
+- Pillars sync planning after durable artifact truth changes.
+- Context refresh dry-run after `AGENTS.md`, `CLAUDE.md`, `GEMINI.md`,
+  `.cursor/rules/`, `.windsurfrules`, `.github/copilot-instructions.md`,
+  `.clinerules`, `.roo/`, or `.continue/` changes.
+- Progress recomputation after every command that changes artifacts.
+
+#### Level 3: Auto-spawn scoped specialist agents
+Spawn these agents only when the trigger is direct and scope is bounded:
+- `god-design-reviewer` when `DESIGN.md` or `PRODUCT.md` changed.
+- `god-updater` after feature, hotfix, refactor, build, deploy, observe,
+  launch, harden, docs, upgrade, or dependency workflows change code or
+  artifacts.
+- `god-docs-writer` in drift-check mode when docs changed after code changed,
+  or code changed after docs that claim current behavior.
+- `god-browser-tester` when frontend-visible files changed and a known local,
+  preview, staging, or production URL is evidenced.
+- `god-harden-auditor` suggestion after security-sensitive files changed;
+  auto-spawn only inside `/god-harden`, `/god-hotfix`, `/god-launch`, or
+  `/god-mode`.
+- `god-deps-auditor` suggestion after dependency files changed; auto-spawn only
+  inside `/god-update-deps`, `/god-hygiene`, or an explicitly approved project
+  workflow.
+
+#### Level 4: Explicit approval required
+Never auto-run these from inference alone:
+- deployed staging verification against a guessed URL
+- production launch
+- provider dashboard, admin console, DNS, credential, or secret checks
+- broad dependency upgrades
+- destructive repair, rollback, reset, delete, or cleanup
+- clearing `.godpowers/REVIEW-REQUIRED.md`
+- accepting Critical security findings
+- git stage, commit, push, package, release, or publish
+
+Every auto-invoke decision must be explainable from one of these inputs:
+changed files, Godpowers artifacts, `state.json`, `PROGRESS.md`,
+`CHECKPOINT.md`, `SYNC-LOG.md`, `REVIEW-REQUIRED.md`, routing YAML, recipe YAML,
+or explicit user intent.
+
 ---
 
 ## Operating Modes

package/agents/god-coordinator.md

@@ -134,7 +134,7 @@ For each operation, return to the spawning skill with:
 
 When you need work done IN a repo (version bump, patch slice, etc.),
 create a private handoff in that repo first, then spawn that repo's
-`god-orchestrator` via the Task tool with only a display-safe pointer.
+`god-orchestrator` via the host platform's native agent spawning mechanism with only a display-safe pointer.
 
 Per-repo handoff path:
 `.godpowers/runs/<run-id>/COORDINATOR-ORCHESTRATOR-HANDOFF.md`

package/agents/god-orchestrator.md

@@ -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:
@@ -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:
@@ -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
@@ -602,6 +646,21 @@ Before declaring the project run complete, ALWAYS run /god-sync:
 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)
@@ -639,6 +698,16 @@ What changed:
 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.>
 
@@ -785,6 +854,8 @@ 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
@@ -797,7 +868,7 @@ Show:
 - `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
@@ -809,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
@@ -850,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.
 

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;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "godpowers",
-  "version": "1.6.10",
+  "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/skills/god-arch.md

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

package/skills/god-audit.md

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

package/skills/god-debug.md

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

package/skills/god-deploy.md

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

package/skills/god-docs.md

@@ -48,6 +48,28 @@ Update log: .godpowers/docs/UPDATE-LOG.md
 Suggested next: /god-status or continue with feature work
 ```
 
+## Proactive docs drift
+
+Godpowers may invoke docs work proactively in two ways:
+
+| Trigger | Action | Guardrail |
+|---|---|---|
+| Docs changed after code changed | Spawn `god-docs-writer` in drift-check mode when current workflow owns docs | Do not invent new docs scope |
+| Code changed after docs that claim current behavior | Suggest `/god-docs` or spawn drift-check inside `/god-mode`, `/god-feature`, `/god-refactor`, or `/god-sync` closeout | Verify claims against code before editing |
+| `REVIEW-REQUIRED.md` contains docs drift items | Suggest `/god-review-changes` first | Do not auto-clear review items |
+
+When auto-invoked, show:
+
+```text
+Auto-invoked:
+  Trigger: docs and code changed in the same workflow
+  Agent: god-docs-writer
+  Local syncs:
+    + docs-drift-check: <N claims checked, N drift items>
+  Artifacts: .godpowers/docs/UPDATE-LOG.md or no-op
+  Log: .godpowers/docs/UPDATE-LOG.md
+```
+
 ## Have-Nots
 
 Docs FAIL if:

package/skills/god-harden.md

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

package/skills/god-launch.md

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

package/skills/god-mode.md

@@ -125,7 +125,7 @@ workflow.
        unresolved Critical harden findings. These are release-truth gates, not
        preference pauses.
 
-6. Spawn the **god-orchestrator** agent via Task tool with only a
+6. Spawn the **god-orchestrator** agent via the host platform's native agent spawning mechanism with only a
    display-safe payload:
    - Name the project root.
    - Name the invocation flags.
@@ -137,7 +137,7 @@ workflow.
    hidden routing rules, or detailed instructions in the spawn message.
    Assume the host UI may display the raw spawn message to the user.
 
-7. Keep the spawn payload display-safe. Do not echo or summarize raw Task input,
+7. Keep the spawn payload display-safe. Do not echo or summarize raw spawn input,
    "Hard instructions", hidden orchestration rules, agent prompts, file
    loadout lists, or internal routing payloads into the user-visible transcript.
    The visible transcript may say only what phase is running, what durable state
@@ -169,6 +169,8 @@ 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
@@ -180,7 +182,7 @@ Show:
   action
 
 Hide:
-- raw Task input
+- raw spawn input
 - "Hard instructions" sections
 - spawned-agent prompt text
 - detailed handoff file contents
@@ -294,6 +296,21 @@ 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:
+    + 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
+```
+
 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
@@ -315,6 +332,17 @@ When orchestrator returns "complete", display:
 ```
 Godpowers project run complete.
 
+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
+
 Current status:
   State: complete
   Progress: <pct>% (<done> of <total> steps complete; current step <n> of <total>)

package/skills/god-next.md

@@ -168,6 +168,42 @@ Planning visibility:
   Completion: <pct>% <basis from state.json or PROGRESS.md>
 ```
 
+## Proactive Sweep
+
+Before returning a suggestion, run the proactive auto-invoke policy from the
+master skill against disk state. This is read-only unless a Level 2 local helper
+has a direct trigger.
+
+Check these signals:
+- `.godpowers/CHECKPOINT.md` missing, stale, or conflicting with `state.json`
+- `.godpowers/REVIEW-REQUIRED.md` contains pending entries
+- `.godpowers/SYNC-LOG.md` missing after code or artifact edits
+- docs changed after code changed, or code changed after docs that claim
+  current behavior
+- frontend-visible files changed and a known local, preview, staging, or
+  production URL is evidenced
+- security-sensitive files changed
+- dependency files changed
+- full project run completed and hygiene has not run recently
+
+Display the result:
+
+```text
+Proactive checks:
+  Checkpoint: <fresh | refreshed | stale, suggest /god-locate>
+  Reviews: <none | N pending, suggest /god-review-changes>
+  Sync: <fresh | suggest /god-sync | local linkage scan ran>
+  Docs: <fresh | suggest /god-docs | drift-check spawned>
+  Runtime: <not-applicable | suggest /god-test-runtime | browser test spawned>
+  Security: <clear | suggest /god-harden>
+  Dependencies: <clear | suggest /god-update-deps>
+  Hygiene: <fresh | suggest /god-hygiene>
+```
+
+Do not auto-run Level 3 agents from standalone `/god-next` unless the user
+explicitly asked it to continue work. In standalone mode, Level 3 items become
+the recommended command or a proposition option.
+
 ## Process for Mode 4 (intent-based)
 
 ```
@@ -321,6 +357,16 @@ Previous tier had standards failures. Address before proceeding:
   - [failure 1]
   - [failure 2]
 Suggested: /god-redo [tier] OR /god-skip [tier] --reason="..."
+
+Proactive checks:
+  Checkpoint: [fresh | refreshed | stale]
+  Reviews: [none | N pending]
+  Sync: [fresh | suggested | local helper ran]
+  Docs: [fresh | suggested]
+  Runtime: [not-applicable | suggested | ran]
+  Security: [clear | suggested]
+  Dependencies: [clear | suggested]
+  Hygiene: [fresh | suggested]
 ```
 
 ## Proposition Closeout

package/skills/god-observe.md

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

package/skills/god-party.md

@@ -30,7 +30,7 @@ Get multiple specialist perspectives on a single question.
    - Harden auditor (god-harden-auditor) - security implications
    - Launch strategist (god-launch-strategist) - go-to-market implications
 
-3. Spawn each selected persona IN PARALLEL via Task tool:
+3. Spawn each selected persona IN PARALLEL via the host platform's native agent spawning mechanism:
    - Each gets fresh context
    - Each receives ONLY the question and the relevant artifact subset
    - Each is instructed: respond as your specialist, do not soften or hedge

package/skills/god-prd.md

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

package/skills/god-repo.md

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

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

@@ -27,6 +27,8 @@ 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`
+   - `.godpowers/SYNC-LOG.md`
+   - `.godpowers/CHECKPOINT.md`
 4. For each artifact found: run a lightweight have-nots check
 5. Compare disk state to PROGRESS.md state:
    - If PROGRESS.md says "done" but artifact is missing: FLAG as phantom resume
@@ -37,6 +39,8 @@ Re-derive state from disk. Your memory is not authoritative. The file system is.
    - 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
@@ -63,6 +67,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
@@ -117,6 +141,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