Skip to content

wired-not-just-present

Wired, Not Just Present — A File That Exists May Still Never Run

Section titled “Wired, Not Just Present — A File That Exists May Still Never Run”

Shipping a hook, script or config file is half the change: until something loads it, it does nothing and nothing says so. Check BOTH facts separately, naming the consumer of the second: (1) Present — the file exists at the path the runtime actually reads; (2) Wired — a registration, manifest entry or caller invokes it (which settings.json entry, which module.json list, which caller). A check that proves only (1) reports green on an install where (2) is missing.

  • Adding a hook → also its settings.json registration, with a matcher covering the event you need (Task|Agent, Bash, …). Adding a script → also the owning module.json list (an unclaimed script does not ship: validate-all-shippable-claimed).
  • A doctor/health check asserts the path the RUNTIME loads, not the repo copy; broken wiring is FAIL, not WARN. Kit-owned config must propagate on update, not only on first install. A matcher can be structurally blind (a closed tool set misses future write paths): keep a tool-agnostic end-of-turn/session sweep underneath.
  • Verify content, not state: a clean git status proves only that the tree matches HEAD; read the content (docs/verify-content-not-state.md).

Incidents, graded joins: docs/wired-not-just-present.md.