ultra-builder-pro-cli 0.26.2 → 5.0.0

package/docs/DECISIONS.md

@@ -1,8 +1,66 @@
-# Ultra Builder Pro v0.26 decisions
+# Ultra Builder Pro decisions
 
 This file records durable product-level decisions that explain the current source tree.
 Project decisions created by Ultra belong in each project's `.ultra/decisions/`.
 
+## Ultra Core Protocol (3.0, accepted 2026-08-17; r3 revision same day)
+
+The owner accepted `docs/ULTRA-BUILDER-PRO-3.0.zh-CN.md` and projected it as North
+Star revision `north-star-v2-r2`
+(`.ultra/decisions/2026-08-17-ultra-3-0-north-star-r2.md`), then converged the
+constitution with the owner-directed r3 design
+(`docs/ULTRA-BUILDER-PRO-3.0-NORTH-STAR-R3.zh-CN.md`) as revision
+`north-star-v2-r3`
+(`.ultra/decisions/2026-08-17-ultra-3-0-north-star-r3.md`). Ultra Builder Pro is
+the file-first, provider-neutral Ultra Core Protocol: cognitive alignment through
+checkpoints, per-fact canonical authority, explicit dual-mode authorization, typed
+evidence with recovery, exclusive verified Agent handover, and review convergence
+bounded by an owner-visible budget. The constitution itself stays count-free —
+agent counts and topology detail, Host and Skill counts, provider names, and
+exact review-round numbers live in the versioned product contract and exact
+work-package grants. Authorization has two
+modes — `session-local` by default, `durable work-package` when the owner issues an
+exact grant (see `.ultra/decisions/2026-08-17-ultra-builder-pro-3.0-mode-b.md`); no
+file, status, Hook, or Resume note ever implies activation. Optional Graph/Loop
+coordination layers own observations only and none is integrated.
+
+## Ultra 5.0 workflow projection (accepted 2026-08-25)
+
+The owner accepted the 5.0 scope and interaction boundary in
+`.ultra/decisions/2026-08-25-ultra-5-0-scope.md`; the versioned contract is
+`docs/ULTRA-BUILDER-PRO-5.0.zh-CN.md`. One shared Route Contract projects the existing
+owner-checkpoint semantics into every public Skill without adding route state. Research
+has explicit baseline and grant-continuable Change-scoped modes; Change makes
+intake/evidence/reconcile/accepted visible and permits only same-Change non-material
+reconciliation under a valid grant; Plan returns product evidence gaps through Change.
+Host invocation bits remain coarse discovery metadata and every Skill rechecks mode,
+grant, effects, and material checkpoints. Team Pack, remote shared assets, a semantic
+state machine, daemon, and resident ACP service remain outside 5.0.
+
+## Primary transfer between Agents (r3, accepted 2026-08-17)
+
+A work package's canonical writer moves to another Agent only through an
+owner-granted primary transfer: the sender writes current reality into the task
+context and Resume Note, derives an OFFER binding canonical refs/hashes, HEAD,
+and the worktree digest, and stops writing after the receiver's ready ACK; the
+receiver stable-reads, verifies every digest, becomes the sole canonical writer,
+and freezes a terminal RESULT. Receipts under `.ultra/.runtime/handoffs/` are
+derived and rebuildable, never authority; mismatches block instead of
+auto-repairing; delegated workers stay mutually exclusive with this path and
+never write canonical `.ultra`
+(`.ultra/decisions/2026-08-17-ultra-3-0-r3-primary-handoff.md`,
+`skills/ultra-change/references/primary-transfer.md`).
+
+## ZCode headless transport stays experimental (r3, accepted 2026-08-17)
+
+The ZCode app-bundled CLI is a verified-local surface — it exists, launches, and
+passed local drills — but the provider publishes no headless CLI, SDK, or
+protocol stability contract. Its transport maturity is recorded `experimental`
+in the shared host profile and compatibility matrix; promotion to `supported`
+requires both official documentation and a full recovery drill. Interactive
+Desktop use and the documented plugin surface are unaffected, and no adapter may
+pass an app-internal binary off as an official stable interface.
+
 ## File-first authority
 
 Owner-readable repository files and Git are the complete semantic authority. Ultra
@@ -13,14 +71,58 @@ ownership of route and meaning.
 
 ## Three Skill roles
 
-The product exposes eight owner-invoked workflows, five model-invoked disciplines, and
-one router. Public workflows require explicit owner selection. A public workflow may
-recommend but never launch another public workflow. A model discipline needs at least
-two canonical callers or it is inlined.
+The product exposes eight owner-invocable public workflows, five model-invoked
+disciplines, and one router. Public modes are `explicit-entry` or
+`grant-continuable`. Scoped Research, same-Change reconciliation, Plan, Dev, Test, and
+Deliver reconciliation may be selected under an activated Change-scoped execution
+grant — session-local activation in the current conversation, or a stably verified
+durable work-package grant. All other public modes stay explicit-entry; Status stays
+owner-invoked and read-only. A model discipline needs at least two canonical callers or it is inlined.
 
 This keeps reusable reasoning in one place without turning it into another user-facing
 route or custom-agent registry.
 
+## Bounded same-session continuation
+
+The stored grant text is descriptive authority, not an executable grant. Session-local
+activation is a current owner utterance approving the exact grant and current task
+ledger; a durable work-package grant is executable only after a fresh Agent stably
+verifies its recorded subject, scope, topology, effects, budgets, expiry, revocation,
+and invalidation. A fresh session without a durable grant, host change, lost
+activation context, semantic stop, or budget ceiling pauses
+the loop. Plan, task, and aggregate reviews remain mandatory. Delivery continuation is
+reconcile-only; finalization, archive, authenticated providers, install, commit, push,
+publish, and deploy remain separately authorized.
+
+The native host model-tool loop performs the work. Existing files and Git carry
+recovery; no route position, daemon, or extra semantic store is introduced.
+
+## Review topology is owner-selected
+
+The owner chooses reviewer and provider count for each stage. The default is one reviewer:
+the current Agent. An initial task review selects `review-spec` plus the
+lenses justified by risk and touched seams; a delta review reruns only affected
+lenses; an aggregate Change review may default to the full roster only when cross-task
+wiring justifies it — never as a mandatory count or a quality proxy. Specification
+fidelity owns both accepted-behavior mapping and the challenge to a Change's claimed
+North Star contribution, with actual execution mode and coverage recorded. When
+another model family is available, a blind premise challenger is an additional probe
+rather than a voting lens.
+
+The seeded 2026-08-14 evaluation found no consequential defect class uniquely caught
+by a permanent premise lens: the strengthened specification lens, the six-concern Kimi
+probe, and the ZCode specification probe each found all five hidden classes. Grok's
+malformed terminal output was rejected and was not counted as semantic evidence. See
+`docs/evals/adversarial-review-2026-08-14.md`.
+
+## ZCode activation uses documented plugin directories
+
+ZCode receives a managed local marketplace for importability and a documented
+`plugins.dirs` entry for immediate native discovery. Ultra owns only the entry it adds,
+so reinstall is idempotent and uninstall preserves unrelated user configuration. It
+does not write ZCode's private plugin cache or copy desktop provider credentials into
+headless CLI configuration.
+
 ## Intake, baseline, and delta
 
 Init preserves raw owner intake in the Project Brief; Research establishes the accepted North Star, domain language, and specification baseline; Change reconciles only the sections touched by one requested delta.
@@ -47,14 +149,41 @@ Directory position and explicit fields record mechanically checkable facts. The
 model reads those facts and chooses the next route. There is no persisted “current
 workflow stage” whose value can override the actual files.
 
-Task status is written to both the ledger and context, then read back. Tasks retain a
-stable `change_id` in an append-only ledger; current readers select only rows matching
-the one active Change. Archive or abandonment is a `git mv`. Test-report freshness
-compares Change id, current task ids, intent digest, `git_commit`, and product-worktree
-digest with the current checkout. Deliver reconciles first and finalizes only while
-that complete snapshot remains current. A separate request cannot create a second
-active Change; it waits, exits the current Change, or is explicitly reconciled into the
-same id.
+The `UBP Route Card` is the owner-visible projection of those facts: it adds Route,
+Mode, Position, and Exit condition around the eight accepted checkpoint semantics. It
+is derived at public boundaries, has no canonical path, and provides neither completion
+nor continuation authority.
+
+Task status lives only in the `ultra-task-ledger-v2` row and is read back there. New task
+contexts do not duplicate it; legacy context Status and Complexity fields remain
+migration diagnostics and the ledger wins. Tasks retain a stable `change_id` in the
+append-only ledger; current readers select only rows matching the one active Change.
+Archive or abandonment is a `git mv`. Test-report freshness is governed normatively by the complete v2 rule in [Artifact Authority](ARTIFACT-AUTHORITY.md#evidence-promotion).
+That authority binds the current Change snapshot, ordered v2 task-evidence identities,
+and strict aggregate-review packet, admission, subject, and summary bindings. This
+decision intentionally does not maintain a second field mirror. Deliver reconciles
+first and finalizes only while that complete snapshot remains current. A separate
+request cannot create a second active Change; it waits, exits the current Change, or is
+explicitly reconciled into the same id.
+
+## Typed task evidence and completion ordering
+
+Current work uses `ultra-task-evidence-v2`. Command, inspection, owner-judgment, and
+external-observation evidence retain distinct authorities; the owner alone can supply
+an owner-judgment result. Structural validators report exact fields, identities,
+digests, provenance, and freshness, never semantic acceptance. A task remains
+`in_progress` through its task review. Blocking findings and their dispositions are
+recorded and affected evidence is refreshed before the primary model writes
+`completed` to the ledger. Historical v1 evidence remains readable but cannot satisfy a
+current Change's Test or Deliver input without migration.
+
+## Counts are observations, not semantic gates
+
+Task, file, line, context, question, finding, repair-round, and complexity counts do not
+decide plan quality, review convergence, staleness, or completion. The model interprets
+concrete coupling, evidence, risk, and recovery facts. Explicit physical ceilings such
+as time, bytes, cost, provider spend, or bounded process resources still stop resource
+consumption and return a typed recovery path; exhaustion never dispositions a finding.
 
 ## Three independent integration defences
 
@@ -75,11 +204,17 @@ their repair is authorization scoped to the exact command digest.
 
 ## Delegation is a process boundary
 
-`ubp delegate run` starts a supported CLI with an immutable instruction, explicit
-permission JSON, and named worktree. Files are the cross-host state. The parent reads a
-stable terminal result instead of worker chatter. Delegation adds no semantic store and
-no authority. The instruction selects task execution, scoped Research evidence, or
-aggregate Change review/verification; only task execution requires a task row.
+The installed `ultra-delegate/scripts/delegate.cjs` starts a supported CLI with an
+immutable instruction, explicit permission JSON, and named worktree. Its exact
+digest-bound sources are embedded in
+the worker prompt because some native sandboxes correctly deny reads outside the
+worktree. Files remain the cross-host state; the embedded copy is transport, not another
+authority. The parent reads a stable terminal result instead of worker chatter. The
+package `ubp delegate` surface is a one-release compatibility import of that same
+launcher, not a second implementation or a runtime installation requirement.
+Delegation adds no semantic store and no authority. The instruction selects task
+execution, scoped Research evidence, or aggregate Change review/verification; only task
+execution requires a task row.
 
 ## Installation isolation
 

package/docs/PHILOSOPHY.md

@@ -45,10 +45,36 @@ one or more.
 
 The agent never stops seeing the current steering contract. Before Research accepts a
 baseline, the session Hook injects the raw Project Brief fallback. After Research, it
-injects the accepted North Star: Project Direction, any settled North Star Outcome, and
-Hard Constraints. Current task acceptance is appended in both cases. The cost of
+requires the exact field ``- Status: `accepted``` and injects the accepted North Star v2 `## Problem Reality`,
+`## First-Principle Propositions`, `## North Star Outcomes`, and `## Hard Constraints`.
+The complete selected sections have a 32 KiB SessionStart ceiling. Above it, the Hook
+uses a reference-only fallback containing the canonical path, immutable accepted snapshot
+path, revision, status, exact validated SHA-256 and byte length, and a direct-read
+instruction that rejects different bytes as authority; semantic truncation is forbidden.
+Brownfield fallback still reads the actual v0.26 `## Project Direction`, `## North Star
+Outcome`, and `## Hard Constraints` shape, or the older `## One-line` shape, without
+misreporting either as v2. Current task acceptance is appended in every case. The cost of
 repetition is always less than the cost of drift.
 
+The publication choice is exact: inject a mechanically bound accepted North Star, otherwise use the Project Brief fallback or a recognized legacy shape.
+When selected accepted sections exceed 32 KiB, use the reference-only path instead of
+semantic truncation. A v2 file whose decision, digest, or immutable snapshot binding is
+invalid is never labelled accepted session authority.
+The Hook does not maintain a second accepted-publication grammar. It safely locates the
+installed sibling Research validator and invokes that one JavaScript report through a
+bounded argv-only subprocess. Missing Node.js, a missing validator, timeout, malformed or
+oversized output, invalid UTF-8, and repository path escape all produce a typed repair
+fallback rather than accepted authority. The report checks the complete mechanical
+structure; it does not decide whether the accepted semantics are true or valuable.
+North Star and Project Brief ingress share one bounded 8 MiB regular-file snapshot:
+repository root, parent components, and file identity are recorded, symlink components
+are rejected, and the canonical root-to-file chain is freshly reopened after the read.
+Every accepted, reference-only, legacy, or Project Brief publication consumes only those
+captured bytes. An unavailable Project Brief produces a typed repair note and is never
+reread through an unbounded path API. This detects ordinary cooperative-workspace drift;
+it is not a claim that a process can prevent malicious operating-system-level replacement.
+The v0.26 legacy branch recognizes headings `## Project Direction`, `## North Star Outcome`, `## Hard Constraints` exactly.
+
 > **Test**: pick a random in-progress task, ask the agent "what's the acceptance criteria?" — if
 > it cannot answer in one sentence, this commandment is broken.
 
@@ -90,6 +116,30 @@ The agent always knows "how far from done." Each edit updates `.ultra/progress/<
 with evidence completeness across six dimensions. Final-gate audits are forbidden — if a gap
 matters at the end, it matters mid-flight.
 
+Canonical task evidence uses `ultra-task-evidence-v2`: command, inspection,
+owner-judgment, and external-observation retain distinct authorities, while the six
+dimensions remain independent observations. The owner alone supplies an
+owner-judgment result. Validators may check structure, identity, provenance, freshness,
+and exact references; they never decide semantic acceptance. `.ultra/tasks.json` is the
+sole task-status authority. A task remains `in_progress` through task review and becomes
+`completed` only after blocking findings are resolved or authoritatively dispositioned
+and affected evidence is refreshed. First-review admission uses the ledger, task
+context, immutable packet, and actual pre-review evidence; the one final v2 record is
+published only after its final review summary validates. Its `subject` is an independently
+captured completion-snapshot freshness observation made after that validation and
+immediately before evidence publication. Its `task_review` separately binds the retained strict summary; the summary does not prove the subject worktree digest. Aggregate Test
+recomputes each command or external receipt's bounded stable bytes against
+`raw_evidence_sha256`, then recomputes the exact record `evidence_digest`. The
+product-worktree digest excludes `.ultra/evidence/**`; these separate raw and record
+bindings make publication non-self-referential without making it invisible.
+Aggregate Test
+separately binds the current whole Change and rechecks current Acceptance, criterion and
+verification type, review summary, owner record, and cited-artifact evidence. If later work
+invalidates a completed task, Dev records affected criteria and reason in Change Log
+and Resume Note before the explicit ledger `completed` to `in_progress` transition;
+there is no silent demotion. Legacy context Status/Complexity and v1 evidence remain
+honest migration diagnostics, not alternative truth.
+
 > **Scoped exception**: whole-system wiring audit (`ultra-test`) is necessarily terminal, because
 > "this export has no non-test importer" cannot be evaluated while later tasks are still pending.
 > It is a terminal **sensor**, never a gate: it reports and hands the trade-off to the owner.
@@ -187,15 +237,16 @@ Skill instruction. Do not touch it casually.
 
 | Consumer | Reads | Source of truth | Failure mode if drifted |
 |---|---|---|---|
-| `session_context` | North Star headings `## Project Direction`, `## North Star Outcome`, `## Hard Constraints`; Project Brief `## One-line`, or legacy North Star `## One-line` | `.ultra-template/north-star.md`, `.ultra-template/project-brief.md`, and the Hook's legacy-read branch | SessionStart shows no accepted North Star or Project Brief fallback; C1 dies |
-| `session_context` | unique active `change_id` → one matching `in_progress` task, else first dependency-ready `pending` task → its context | active Change directory plus `tasks.json[].change_id`, dependencies, status, and `context_file` | abandoned or blocked acceptance is injected, or current acceptance never surfaces |
+| `session_context` | the canonical JavaScript North Star validation report; bound accepted v2 sections or the 32 KiB immutable-snapshot reference with exact validated SHA-256 and byte length, without semantic truncation; Project Brief `## One-line`; actual v0.26 `## Project Direction` / `## North Star Outcome` / `## Hard Constraints`; or older North Star `## One-line` | `skills/ultra-research/scripts/validate_north_star.cjs`, `.ultra-template/north-star.md`, `.ultra-template/project-brief.md`, accepted `.ultra/north-star.md`, its owner decision and immutable snapshot, and the validator's two legacy-read shapes | Python and JavaScript publication grammars diverge, SessionStart labels unbound or different bytes accepted, truncates steering semantics, or shows no honest Project Brief/legacy fallback; C1 dies |
+| `session_context` | unique active `change_id` → one matching ledger `in_progress` task, else first dependency-ready ledger `pending` task → its context; legacy context Status/Complexity are diagnostics only | active Change directory plus `tasks.json[].change_id`, dependencies, sole status, and `context_file` | abandoned or blocked acceptance is injected, a legacy context overrides the ledger, or current acceptance never surfaces |
 | `mid_workflow_recall` | heading `## Acceptance Criteria` | `.ultra-template/contexts/TEMPLATE.md` | hook injects nothing; C1 dies silently |
 | `ultra-tdd` | path `references/templates/*` | `skills/ultra-tdd/references/templates/` | guidance points at a missing runnable alternative; C2 dies |
-| `post_edit_guard` | writes `.ultra/progress/<task-id>.json` for the active Change's current task | active Change directory plus `tasks.json[].change_id` and `id`, created on demand | historical work receives current observations; C4 weakens |
-| `ultra-dev` and `post_edit_guard` | 6 keys: `tests_written`, `tests_passed`, `persistence_real`, `feature_flags_audit`, `vertical_slice`, `spec_trace` | the six-dimension table in `skills/ultra-dev/SKILL.md` | sensor and workflow report different evidence |
+| `post_edit_guard` | writes `.ultra/progress/<task-id>.json` for the active Change's current ledger task | active Change directory plus `tasks.json[].change_id`, `id`, and sole `status`, created on demand | historical work receives current observations or a Hook invents completion; C4 weakens |
+| `ultra-dev` and `post_edit_guard` | 6 keys: `tests_written`, `tests_passed`, `persistence_real`, `feature_flags_audit`, `vertical_slice`, `spec_trace` | the six-dimension table in `skills/ultra-dev/SKILL.md` and typed evidence contract in `skills/ultra-plan/references/task-evidence-v2.md` | sensor and workflow report different evidence or a progress observation becomes semantic acceptance |
+| plan/dev/review/test/deliver | ledger status; actual pre-review inputs; one final `ultra-task-evidence-v2` carrying an independent completion-snapshot freshness observation and separate task-review provenance; aggregate Test identity | `.ultra/tasks.json`, task context, immutable Review artifacts, and `skills/ultra-plan/references/task-evidence-v2.md` | first review requires its own final output, context becomes a second status authority, review provenance is claimed to prove the independent subject, task subject is rebound to a later aggregate worktree, or invalid evidence is silently demoted |
 | planning and status | marker `[NEEDS CLARIFICATION]` | `.ultra-template/specs/*.md` | unresolved product truth is hidden |
 | `ultra-plan` / `ultra-dev` / hooks | `trace_to` form `.ultra/specs/file.md#anchor` | `tasks.json[].trace_to` + GFM heading slugify | traces appear resolved when their heading is absent |
-| `ultra-deliver` / `ultra-status` | fields `change_id`, `task_ids`, `intent_digest`, `git_commit`, and `worktree.diff_digest` | `.ultra/test-report.json` plus `worktree_digest.cjs` | stale Change, intent, task set, or product results pass as current |
+| `ultra-deliver` / `ultra-status` | root Change identity, ordered v2 task-evidence/review identities, and strict aggregate Review packet/admission/subject/summary bindings | `.ultra/test-report.json`, retained task evidence and Review artifacts, `worktree_digest.cjs`, and existing structural validators | stale Change, intent, task set, task evidence, Review transport, or product results pass as current |
 | `compact_context` | `.ultra/.runtime/compact-snapshot.md` | derived from canonical files and Git | compact recovery loses acceleration, not authority |
 | every hook | existence of `.ultra/` | the project directory | Ultra taxes projects that never opted in (see `docs/PLUGIN-ISOLATION-CONTRACT.md`) |
 | `ultra-init` | the project data skeleton | `.ultra-template/` and the exact file list in its Skill | later Skills read missing authority paths; C1 dies |

package/docs/PLUGIN-ISOLATION-CONTRACT.md

@@ -1,19 +1,25 @@
 # Plugin isolation contract
 
-Ultra Builder Pro owns a narrow install surface and becomes active only in a project
-that contains `.ultra/` or when the owner explicitly invokes an Ultra Skill.
+Ultra Builder Pro owns a narrow install surface. Installation and discovery create no
+project authority. A public workflow becomes active only through an explicit owner
+entry or one mode covered by a currently valid Execution Grant; Hooks separately use
+the presence of `.ultra/` as their idle guard.
 
 ## Owned surfaces
 
 Per host, Ultra may install:
 
 - exactly fourteen managed Skills;
+- the launcher, worker, Host profile, and launch-only profile assets below the managed
+  `ultra-delegate/scripts/` Skill directory;
 - exactly five hook scripts plus `_common.py` and any required wire adapter;
 - one native plugin manifest or entrypoint;
 - provenance and managed-ownership markers;
 - the host's native registry entry where required.
 
-The package also owns `ubp delegate run`, its worker, and rule-side Skill references.
+For one release cycle the package also owns thin `ubp delegate` launcher/worker
+compatibility imports. They execute the Skill-local implementation and contain no
+forked behavior.
 
 ## Surfaces Ultra does not own
 
@@ -29,9 +35,10 @@ Ultra must not create or rewrite:
 
 ## Installation lifecycle
 
-Install builds a complete staging tree, marks it managed, writes provenance, then
-atomically publishes it. An existing unmanaged target is never overwritten. Reinstall
-replaces only the managed tree. Doctor is read-only. Uninstall removes only assets
+Install builds a complete staging tree, including the Skill-local delegation runtime,
+marks it managed, writes provenance, then atomically publishes it. An existing unmanaged
+target is never overwritten. Reinstall replaces only the managed tree. Doctor is
+read-only and reports runner reachability separately. Uninstall removes only assets
 whose ownership can be proven.
 
 Host-owned sidecars must resolve from the same isolation root as `--config-dir`. For
@@ -55,14 +62,29 @@ non-empty, modified, symlinked, or unowned path. Codex marketplace and Kimi regi
 files additionally remember whether Ultra created the registry itself, so an empty
 registry that existed before installation is retained.
 
-## Activation
+ZCode publishes one managed local marketplace whose nested plugin is activated through
+the host's documented `plugins.dirs` configuration. Install preserves unrelated ZCode
+configuration, and uninstall removes only Ultra's exact directory entry and restores
+the pre-install `plugins.enabled` value when that value has not since been changed by
+the owner.
 
-Owner-invoked Skills activate only through the host's explicit Skill surface.
-Model-invoked Skills may be selected by the host model only as methods inside the
-current authorized task. Hooks activate only through host lifecycle registrations.
+## Activation
 
-One public Skill may recommend another but never launches it. Installation does not
-create project authority or start background work.
+Public Skill modes are `explicit-entry`, `grant-continuable`, or read-only `router`.
+Explicit-entry modes activate only through the Host's owner-facing Skill surface.
+Grant-continuable modes may be model-selected only after the loaded Skill verifies the
+same active Change, valid grant, allowed effects, and material checkpoints. A router may
+diagnose read-only state only on explicit owner invocation and creates no continuation
+authority. Model-discipline Skills
+may be selected only as methods inside the current covered workflow.
+
+Host invocation metadata is a coarse discovery aid. It cannot express every per-mode
+boundary, so the in-Skill check remains mandatory and Hosts without an equivalent bit
+rely on discriminating descriptions plus that same check. A public Skill may transition
+to another only when a valid grant covers the exact next mode and effects, after showing
+the Route Card; otherwise it stops and recommends the explicit route. Installation does
+not create a grant, launch a workflow, or start background work. Hooks activate only
+through Host lifecycle registrations and retain their independent idle guard.
 
 ## Idle behavior