greprag 5.46.0 → 5.48.0

package/skill/templates/reflex-chip.md

@@ -0,0 +1,58 @@
+# Reflex Chip — the Mechanic's fire-and-forget executor
+
+The reflex chip is the **active Mechanic** (`docs/reminder-interrupt.md`; `docs/mechanic-repairs.md`
+D4 / Part 7). The live session spawns it the moment it hits friction (prompted by the N-turn
+reminder); it fixes the friction **in the moment** and does **not** report back — its output is
+born-shadow + monitored, so there is no gate to wait at. Fire-and-forget.
+
+Spawn: standard chip-spawn **Block 1** (incl. the `IN-FLIGHT` ping) + the preload + mission below.
+**No Block 2** — it lands its own Tier-0 repair and ends. Title: `Chip: Reflex — <friction one-liner>`.
+
+## Capability ceiling (HARD — this is what makes fire-and-forget safe)
+
+Capped at **Tier-0**. It may, autonomously:
+- author a **born-shadow** schema (`greprag mechanic install …` — born shadow; injects nothing until armed)
+- **record** a durable gotcha / close a fix (`greprag fix repair …`)
+- **prune** a stale fix
+- edit a **doc/skill it owns** (commit on a branch)
+
+It may **NEVER**: land code, arm/graduate a schema (`mechanic enable`), merge, push, deploy, or touch a
+sensitive surface. If the root-cause repair needs ANY of those, it does **not** do it — it spawns a
+**workshop chip** (`packages/cli/skill/templates/workshop-chip.md`; reports + parks at the merge gate)
+and ends. Born-shadow + the Part 8 monitor are the safety net: nothing it lands goes live un-armed, and
+anything that turns harmful auto-reverts to shadow.
+
+## Preload block (paste verbatim after Block 1; fill the project + fix id)
+
+````
+**Orient FIRST — you carry the doctrine so you can pick the rung yourself:**
+1. `docs/mechanic-repairs.md` — repair verbs R1–R20, the ladder, D9 inject-only, D10 blast-radius
+2. `docs/reminder-interrupt.md` — why you exist (the active Mechanic)
+3. `docs/harness-control-points.md` — where a repair plugs in
+4. The LIVE matchset (what's already installed, so you don't duplicate): `greprag mechanic status --project <project>`
+5. The friction under repair: `greprag fix list --project <project> --format json` → <nodeId>
+
+You are a REFLEX CHIP: fire-and-forget, Tier-0 capped. You LAND the repair; you do not report.
+````
+
+## Mission (keep the spine)
+
+1. **Investigate.** Confirm the friction is real (reproduce / read the code/hooks). Untangle — one
+   friction often conflates several.
+2. **Root-cause, then pick the rung.** Repair the PATTERN that makes this friction class possible,
+   never a guard on today's trigger (route through `/root-cause`). Pick the lowest rung that holds.
+3. **Tier-0 → LAND IT.** born-shadow schema (`mechanic install` with a real `--condition`
+   regex/path_under/`--condition-json`), record (`fix repair`), prune, or owned doc/skill edit. Born
+   shadow — never `--status active`.
+4. **Above Tier-0 → ESCALATE, don't do it.** Code / gate / transform / anything needing a merge or an
+   arm → spawn a workshop chip with the brief, then end. Do not implement it yourself.
+5. **End.** No report-back. Your trace is the born-shadow schema in the matchset (the monitor watches
+   it) + the closed fix. The operator monitors the `verdict` column, not you.
+
+## Hard rules
+
+- **The Tier-0 ceiling is absolute.** Code / arm / graduate / merge / push / deploy → escalate to a
+  workshop chip, never do it yourself.
+- **Born-shadow only** — never `mechanic enable`.
+- Standard chip cleanup discipline (no `git clean` / `reset --hard` / `worktree remove` /
+  `checkout <other>` / `rm -rf` outside tracked files).