@deftai/directive-content 0.95.0 → 0.97.0

package/docs/getting-started.md

@@ -80,6 +80,8 @@ checks tools without rewriting consumer-managed files.
 
 If you are adopting Deft on a project that already has an issue tracker (existing repo, brownfield migration, an upstream bug list that has been accumulating), you do not have to start from an empty `xbrief/proposed/`. The refinement skill's **Phase 0 triage workflow** lets you walk an existing backlog locally, decide what to keep, and let only the **accepted** items land in `xbrief/proposed/`. Trigger words: **"triage"**, **"work the cache"**, **"pre-ingest"**, **"action menu"**.
 
+**Labels first:** capacity and triage matchers only help when labels exist. For a bare or thin label set, adopt the [consumer issue-label kit](./consumer-issue-label-kit.md) (#2611) before you rely on ranking or `triage:classify -- --mirror`.
+
 ### Step 1 — Scoped first populate
 
 A real-sized backlog can drain the shared GitHub GraphQL bucket if you fetch everything at once (see [#976](https://github.com/deftai/directive/issues/976) for the recurring symptom). Scope the first populate so it lands in seconds rather than minutes:

package/docs/openclaw-agent-host.md

@@ -56,7 +56,7 @@ Bodies stay **thin** (L5): frontmatter + short dispatch pointer to the same cont
 4. Opt-out: `plan.policy.openClawProductCommands: false` — removes **managed** L2 thin skills only; preserves consumer custom skills at the same slug.
 5. After deposit: **restart the OpenClaw gateway or start a new session** so `available_skills` refreshes.
 
-Always-pin skills (`deft-directive-build`, `pre-pr`, `review-cycle`, `swarm`) remain a **different** surface from L2 product commands (`/deft:directive:run:interview`, `/deft:continue`, …).
+Always-pin skills (`deft-directive-build`, `pre-pr`, `review-cycle`, `swarm`) remain a **different** surface from L2 product commands (`/deft:directive:run:interview`, `/deft:continue`, …). Soft post-compact re-bind (`deft-directive-post-compact-rebind`, #3171) is a third surface — see § Soft post-compact AGENTS re-bind below.
 
 Inspect policy:
 
@@ -66,6 +66,41 @@ deft policy:show --field=openClawProductCommands
 
 ---
 
+## Soft post-compact AGENTS re-bind (#3171 / #2769)
+
+OpenClaw is a **Family-2** session host. Soft AGENTS re-bind after compaction / long-session amnesia is **required** on OpenClaw and is **not** claimed via Cursor/Claude/Grok file-host `PreCompact` hooks alone.
+
+| Surface | OpenClaw posture |
+|---------|------------------|
+| **Hard** compact re-arm (file-host PreToolUse stale → deny writes) | **Not** provided by file-host compact hooks on OpenClaw. Mutation still requires `session:start` / `session:ready` / gated ritual via CLI/skills before gated writes. |
+| **Soft** AGENTS re-bind | **Required** durable workspace skill from the **shared checklist SoT** (`packages/core/src/session/compact-ritual.ts`). |
+
+### Checklist obligations (same SoT as file hosts)
+
+1. Re-read managed `AGENTS.md` session routing (#2176) — summary ≠ SoT.
+2. Confirm-what-you-learned (brief) in the user-visible reply.
+3. Deposit integrity: `deft` on PATH ≠ healthy `.deft/core` deposit.
+4. Summary/runbook (demo DBs, “start the app”) are hypotheses — re-verify PROJECT-DEFINITION / USER.md / local config.
+5. Operational-ask trap: “open/start/run the app” is still session-routed (#3161).
+6. Read-only → soft only; mutation → soft **plus** hard re-arm where supported. Soft **never** authorizes skipping the mutation ritual for writes.
+
+### Deposit / amnesia boundary
+
+| Step | Action |
+|------|--------|
+| Detect / fix | `deft doctor` warns when OpenClaw is detected and the managed skill is missing/stale; `deft doctor --fix` deposits it (multi-seat: `--openclaw-all-agents`) |
+| init / update | Deposits when OpenClaw signals are present (fail-closed otherwise) |
+| Skill id | `deft-directive-post-compact-rebind` under the OpenClaw workspace skills root |
+| After deposit | **Restart the OpenClaw gateway or start a new session** so skills reload |
+| Trigger | Session start / resume, gateway restart, long-session amnesia, operational asks after summary resume |
+
+⊗ Claim OpenClaw soft coverage from file-host hook deposits alone.  
+⊗ Treat “pins present” as “session ritual completed.”
+
+Shared dual-surface + five-host matrix: [commands.md](../commands.md) § Agent-host hooks → Compact re-arm + soft AGENTS re-bind.
+
+---
+
 ## Mental model (host class)
 
 | Host | Host-native background spawn (typical) | Directive review-monitor role |
@@ -204,7 +239,7 @@ deft doctor --fix --openclaw-all-agents
 
 ---
 
-## Swarm on OpenClaw (#2929 / #2934 / #2943)
+## Swarm on OpenClaw (#2929 / #2934 / #2943 / #3131)
 
 ! For **parallel** swarm leaves on OpenClaw:
 
@@ -214,16 +249,20 @@ deft doctor --fix --openclaw-all-agents
 
 ! After a coding cohort completes, dispatch the next phase with a **real tool call in the same turn**, or write explicit terminal status (`blocked` / `awaiting-human` / `done`). Do not end on narrative-only “I will spawn…”.
 
-### Parent-monitor after `subagent_announce` (#2943)
+### Parent-monitor after `subagent_announce` (#2943 / hard-stop #3131)
 
-OpenClaw parents can lock into a **text-only repetition hang** after thin leaf completions: the model regenerates the same “checking worktrees / open PRs next” sentence with **zero tool calls** until length cap or abort. Subagents may still be healthy; only the parent appears hung.
+OpenClaw parents can lock into a **text-only repetition hang** after thin leaf completions: the model regenerates the same “checking worktrees / open PRs next” sentence with **zero tool calls** until length cap or abort. Subagents may still be healthy; only the parent appears hung. Soft skill prose alone is **not** enough (#2943 closed; recurrence under production → **#3131**).
 
-! After any leaf completion event (`subagent_announce` / parent-push completion), the parent’s **first response** MUST be **tool-first** or **yield**:
+! After any leaf completion event (`subagent_announce` / parent-push completion), the parent’s **first response** MUST be exactly one of:
 
-1. **Tool-first ground-truth batch** — one same-turn tool batch that inspects reality (`gh` PR/issue status, `git` / worktree status, or file/xBRIEF state), **or**
-2. **`sessions_yield`** (or host equivalent yield) — leave the turn steerable without narrating unfinished work.
+1. **Tool-first ground-truth batch** — one same-turn tool batch that inspects reality (`gh` PR/issue status, `git` / worktree status, or file/xBRIEF state), then one consolidate, **or**
+2. **`sessions_yield`** (or host equivalent yield / wait) — leave the turn steerable without narrating unfinished work, **or**
+3. **One short user answer** that is **not** a repeated progress line.
 
 ⊗ Open the first response after announce with multi-sentence progress-only prose (“Two leaves look unfinished…”, “Checking worktrees next…”, “Implementing both myself…”) and **zero** tool calls / yield.
+⊗ Emit **N>2** near-identical assistant sentences (or streaming text chunks) in one turn with no `tool_use` / yield — **FC14 text-repetition hang** (illegal turn shape; hard-stop).
+
+! **Machine check (hard-stop, not prose-only):** `evaluateParentTurnShape` in `@deftai/directive-core` / `@deftai/directive-core/parent-turn-shape` (`packages/core/src/parent-turn-shape/`). Hosts and parents SHOULD feed ordered turn events (`assistant_text` / `tool_use` / `yield`) mid-stream; when `ok === false` and `failClass` is `FC14` (or `progress-only-no-tool` after announce), **abort the turn** / force tool-or-yield — do not burn the output budget. Soft skill text is **not** the sole mitigation.
 
 ! **Thin DONE = failed leaf:** a completion without PR URL / merge evidence (and without a structured `BLOCKED` / `FAILED` terminal) is **not** success. Treat as failed: re-dispatch or take over after the ground-truth batch. Do not celebrate thin DONE as shipped.
 
@@ -231,6 +270,16 @@ OpenClaw parents can lock into a **text-only repetition hang** after thin leaf c
 
 Full rules: [`skills/deft-directive-swarm/references/host-openclaw.md`](../skills/deft-directive-swarm/references/host-openclaw.md), thin swarm SKILL hard-gates, and [`templates/agent-prompt-preamble.md`](../templates/agent-prompt-preamble.md) §11. This page does not fork a second source of truth.
 
+### Operator recovery — FC14 parent hang on current OpenClaw beta pins (#3131)
+
+When the Control UI / parent seat is stuck replaying the same progress sentence with no tools:
+
+1. **Abort the parent turn** (Control UI stop / interrupt / cancel generation). Do **not** wait for length-cap.
+2. **Do not assume leaves failed.** Check worktrees, open PRs, and xBRIEF state with a **tool-first** batch from a fresh parent turn (`gh` / `git` / files). Leaves may already be DONE or mid-review.
+3. **Resume with a legal shape only:** tool-first ground truth, `sessions_yield`, or one short non-repeated answer. ⊗ Restart by pasting more “checking next…” prose.
+4. **If the hang returns immediately:** refresh Directive deposit (`npm i -g @deftai/directive@latest` then `directive update` / `deft update` / `deft doctor --fix` for OpenClaw skill pins — see § Wire skills into OpenClaw workspace), re-open the parent with current `openclaw-agent-host` + swarm host adapter text, and re-dispatch only after ground truth.
+5. **Host pin note:** On OpenClaw beta pins that do not yet call `evaluateParentTurnShape` in the stream, the operator abort in step 1 **is** the hard stop. Directive still ships the machine-check library + skill/docs so soft prose is not the only mitigation once the host wires it (or an agent-side gate evaluates a recorded turn). Surface `FC14` in notes when reporting the incident.
+
 ## Anti-patterns
 
 - ⊗ Main-session `gh` poll + **cron** as the default babysit path when the installed skill offers a Tier 1 / background monitor.
@@ -239,9 +288,11 @@ Full rules: [`skills/deft-directive-swarm/references/host-openclaw.md`](../skill
 - ⊗ Substituting host-native review theater for `deft-directive-review-cycle` on Deft-managed repos.
 - ⊗ Claiming this doc alone makes `sessions_spawn` a shipped register/matrix primitive — that is epic skill/engine work (#2875 / #2876).
 - ⊗ Multi-sentence progress-only first response after `subagent_announce` with zero tools / yield (#2943 text-repetition hang).
+- ⊗ N>2 near-identical assistant sentences in one turn with no tool_use / yield (FC14 / #3131 hard-stop).
 - ⊗ Treating thin DONE (no PR URL / merge evidence) as success (#2943).
 - ⊗ Assuming package install alone populates OpenClaw `available_skills` — wire main workspace pins via `deft doctor --fix` (#3001).
 - ⊗ Auto-enumerating every `workspace-*` seat without `--openclaw-all-agents` (#3001).
+- ⊗ Relying on soft skill prose alone as the sole mitigation for the parent hang (#3131).
 
 ---
 

package/docs/operator-log-hygiene-checklist.md

@@ -0,0 +1,57 @@
+# Operator-log hygiene checklist (#1940)
+
+Copy-paste block for **story acceptance criteria** and **probe locked
+decisions**. Full pattern:
+[`patterns/operator-log-hygiene.md`](../patterns/operator-log-hygiene.md).
+
+Legend (RFC2119): `!`=MUST, `~`=SHOULD, `⊗`=MUST NOT, `?`=MAY.
+
+**Load when:** building operator-facing services, adding WARN/ERROR paths
+operators triage, multi-process workers, or probing logging decisions.
+
+## Story AC / probe locked decisions (copy-paste)
+
+Use as-is in scope xBRIEF acceptance, probe locked decisions, or PR
+checklist. Mark N/A only with a one-line reason.
+
+```markdown
+### Operator-log hygiene (#1940)
+
+Legend: ! = MUST, ~ = SHOULD, ? = MAY (from patterns/operator-log-hygiene.md)
+
+- [ ] ! Terminal / completion events on **all** exit paths (success, skip,
+      timeout, supersede, cancel, failure) — not happy path only
+- [ ] ! Correlation IDs for multi-process / pool designs (job id, slot,
+      phase, parent id as applicable)
+- [ ] ! Infrastructure paths (rotation, flush-before-exit, IPC handoff,
+      boot supervision) fail-open where possible and emit structured
+      events when they degrade
+- [ ] ~ Operator-visible WARN/ERROR use a stable, queryable shape
+      (consumer-owned fields; e.g. stable event id + short operator
+      summary) — not ticket numbers alone
+- [ ] ~ Operator glossary / plain-English docs updated in the **same PR**
+      when operator-facing log lines change
+- [ ] ? Optional: wire consumer-owned validator into *your* check aggregate
+      (see docs/operator-log-hygiene-consumer-pack-stub.md) — not core default
+- [ ] Explicit non-goals respected: no assumption that core `deft check`
+      enforces this; log shape stays consumer-owned
+```
+
+## Agent rules when applying the checklist
+
+- ! MUST run this checklist before claiming "logging done" on an
+  operator-visible lifecycle path
+- ! MUST keep log field names and schemas **project-owned** unless the
+  consumer already defined them
+- ~ SHOULD attach the checklist under probe locked decisions when the plan
+  introduces or changes operator-facing logs
+- ⊗ MUST NOT invent a framework-wide required field set (`operatorSummary`,
+  etc.) from this checklist alone
+- ⊗ MUST NOT treat Product Insights (#2603) or LLM telemetry (#481) as
+  substitutes for operator-log hygiene
+
+## Related
+
+- Pattern: `content/patterns/operator-log-hygiene.md`
+- Optional consumer pack stub: `content/docs/operator-log-hygiene-consumer-pack-stub.md`
+- External case study (reference only): deftai/slizard operator-log hygiene docs and `operator-log:validate` — do not import schema into core

package/docs/operator-log-hygiene-consumer-pack-stub.md

@@ -0,0 +1,75 @@
+# Operator-log hygiene — optional consumer pack stub (#1940)
+
+Skeleton for **consumer projects** that want a ship-gate for operator-facing
+logs. Wire this into *your* check aggregate only if you opt in.
+
+Full pattern: [`patterns/operator-log-hygiene.md`](../patterns/operator-log-hygiene.md).
+Checklist: [`operator-log-hygiene-checklist.md`](./operator-log-hygiene-checklist.md).
+
+## Settled boundaries
+
+| Topic | Rule |
+|-------|------|
+| Default-on | **Off.** Directive core does not enable this for all services. |
+| Schema | **Consumer-owned.** You define fields and glossary path. |
+| Framework `deft check` | **Does not** hard-fail consumers who never opted in. |
+| External refs | SLizard `task operator-log:validate` is a **reference** only. |
+
+## Suggested Taskfile target name
+
+Prefer a project-local name so it does not imply framework ownership:
+
+```yaml
+# tasks/observability.yml (consumer-owned example — not shipped by core)
+version: "3"
+
+tasks:
+  operator-log:validate:
+    desc: Validate operator-facing log shape / glossary (consumer-owned)
+    cmds:
+      - echo "Implement inventory + schema checks for YOUR log contract"
+      # - node scripts/validate-operator-log.mjs --strict
+```
+
+Optional aliases consumers sometimes use:
+
+- `observability:validate`
+- `ops-log:check`
+
+Pick one name and keep it stable in your repo.
+
+## Validator skeleton (comments only)
+
+```js
+// scripts/validate-operator-log.mjs  (consumer-owned skeleton)
+//
+// 1. Inventory: find operator-facing log call sites (WARN/ERROR + terminal events).
+// 2. Schema: load YOUR glossary / field contract (path from project config).
+// 3. Strict mode: fail if new events lack required consumer fields.
+// 4. Exit 0 when clean; exit 1 with actionable paths when not.
+//
+// ⊗ Do not import SLizard glossary JSON as universal SoT.
+// ⊗ Do not expect @deftai/directive to ship or enforce this script.
+//
+// Reference shape (external): deftai/slizard task operator-log:validate
+```
+
+## Wire into *your* check (optional)
+
+```yaml
+# In the consumer Taskfile check aggregate — only if you want hard-fail
+tasks:
+  check:
+    deps:
+      - operator-log:validate
+      # ...other consumer gates...
+```
+
+- ! MUST document the gate as **project policy** when enabled
+- ⊗ MUST NOT claim framework `deft check` mandates this target by default
+- ? MAY keep the script warn-only until glossary coverage is good enough
+
+## Related
+
+- #1940 thin v1 — content + checklist + this stub
+- Pattern non-goals: no `plan.observability` core schema, no default-on

package/docs/scope-provenance.md

@@ -0,0 +1,54 @@
+# Approved-scope provenance (`verify:scope-provenance`)
+
+Refs: #3145 · Related: #1310, #2944 human-origin grants, #516 file scope
+
+## Problem
+
+An implementation PR could edit its own active xBRIEF to add new paths, after which one-way forward-coverage still passed. The modified xBRIEF became its own authorization source.
+
+## Contract
+
+At activation or operator approval, record an immutable **approved-scope digest** under:
+
+```text
+.deft/approved-scope/<plan-id>.json
+```
+
+Shape:
+
+```json
+{
+  "schemaVersion": 1,
+  "xbriefRelPath": "xbrief/active/….xbrief.json",
+  "planId": "…",
+  "approvedAt": "2026-08-06T00:00:00Z",
+  "fileScope": ["packages/core/src/foo.ts"],
+  "fileScopeDigest": "<sha256 of sorted paths>",
+  "humanApproval": {
+    "kind": "operator",
+    "actor": "scott",
+    "mintedAt": "2026-08-06T00:00:00Z"
+  }
+}
+```
+
+`task verify:scope-provenance` compares the live active xBRIEF `plan.metadata.swarm.file_scope` to the digest when that xBRIEF is modified in the current change set.
+
+| Outcome | Behavior |
+| --- | --- |
+| No expansion | Pass |
+| Expansion + renewed human stamp / re-recorded matching digest | Pass |
+| Expansion without renewal | **Fail** — self-authorizing scope |
+| Modified active xBRIEF, no digest yet | **Warn** by default; `--enforce` fails closed |
+
+Agent-shaped stamps (`kind: agent`, `actor: agent:…`) never count as renewal.
+
+## Migration path
+
+1. Ship gate in warn mode (missing digests do not fail)
+2. Start recording digests on activation / promote
+3. Enable `--enforce` or project policy when ready
+
+## Remediation
+
+Re-record the approved-scope file after human review of the expanded `file_scope`. Editing the xBRIEF alone does not authorize new implementation paths.

package/docs/test-boundary.md

@@ -0,0 +1,43 @@
+# Test / source boundary (`verify:test-boundary`)
+
+Refs: #3145 · Related: #1310 forward-coverage, testing layout guidance
+
+## Problem
+
+Directive accepted test harnesses, fixtures, and smoke orchestration under production-owned roots (`src/**`, `infra/**`, `Tools/**`, …) while gates stayed green. Placement guidance was prose-only.
+
+## Contract
+
+`task verify:test-boundary` / `deft verify:test-boundary` enforces a typed policy:
+
+| Field | Meaning |
+| --- | --- |
+| `sourceRoots` | Production-owned path globs |
+| `testRoots` | Allowed test roots |
+| `fixtureRoots` | Fixture roots |
+| `testFilePatterns` | Conventional test basenames (`test_*.py`, `*Tests.cs`, `*.test.ts`, `*.spec.ts`, …) |
+| `productionMayReferenceTestRoots` | Default `false` — production must not reference test/fixture roots |
+| `allow` | Narrow exceptions (`kind: exception` or `production-liveness`) |
+| `enforcementMode` | `warn` (migration/discovery) or `enforce` |
+
+## Policy sources (first wins)
+
+1. `--policy <path>`
+2. `.deft/test-boundary.policy.json`
+3. `plan.policy.testBoundary` in `xbrief/PROJECT-DEFINITION.xbrief.json`
+4. **Defaults** (conventional roots + patterns, `enforcementMode: warn`)
+
+## Migration path
+
+1. Run with defaults (warn-only): `task verify:test-boundary`
+2. Review findings; move test artifacts under declared test roots or classify production liveness/canaries in `allow`
+3. Persist reviewed policy under `.deft/test-boundary.policy.json` or `plan.policy.testBoundary` with `enforcementMode: "enforce"`
+4. Wire stays green via `task check` / consumer deposit
+
+## Production liveness carve-out
+
+Health probes, canaries, and operational evidence collectors may live under production roots when listed in `allow` with `kind: "production-liveness"` and a recorded reason. Do not use the word “smoke” alone as classification.
+
+## Remediation
+
+Failures name the path, violated boundary, and next step (move under test root, allow entry, or reclassify). See `content/contracts/test-boundary.md`.

package/main.md

@@ -71,6 +71,35 @@ See #634, #642. See [ADR-001](./docs/decisions/ADR-001.md) for the token-economi
 - ⊗ Continue executing a skill past its explicit instruction boundary — when a skill's steps are complete, stop and return to the calling context; do not drift into adjacent work (#198)
 - ! The end of a skill's final step is an exit condition — do not continue into adjacent work, even if it seems related or trivial
 
+## Dual Stop Rule (#2442)
+
+Loop engineering requires **two** stop conditions on multi-iteration autonomous work: a **success stop** (goal / AC / checker met) and a **failure or budget stop** (retries exhausted, no progress, or time/token budget). Directive already has strong success-shaped gates (`task check`, acceptance criteria, STOP on plan precondition mismatch -- #1613). This section requires the complementary failure envelope so agents escalate instead of thrashing forever.
+
+**Applies to:** multi-iteration autonomous loops -- build quality / implement-fix loops, pre-PR polish cycles, swarm repair and monitor loops, research fan-out, review fix cycles, and similar retrying work.
+
+**Does not apply to:** single-turn tasks (one shot answer, one file edit, one status probe). Not every task is a loop; do not invent iteration caps where there is no multi-step retry envelope.
+
+**Required stops on every multi-iteration loop:**
+
+1. ! **Success stop** -- goal, acceptance criteria, or checker is met; exit the loop and continue the skill or report done.
+2. ! **Failure stop** -- at least one of:
+   - **max iterations** (task-class default; e.g. a short quality-fix class vs a longer research class)
+   - **no-progress** (same outcome or same failure fingerprint N times in a row with no material change)
+   - **explicit budget** (time, tool-call, or token budget when the host exposes it)
+
+**On failure stop:**
+
+- ! Halt the loop. Do not silently continue, re-dispatch, or open a new identical attempt without an operator decision.
+- ! Emit an **operator-visible halt report** that states: (a) what was tried, (b) what is still missing or failing, (c) what human decision is needed next (scope change, unblock, override, or abandon).
+- ⊗ Keep iterating after the failure envelope is exhausted because "one more try" might work.
+- ⊗ Reset iteration counters solely by creating a new revision, swapping workers, or compacting context when the same failure class remains.
+
+**Relation to other rules:**
+
+- #1613 covers STOP when plan **preconditions** fail (reality mismatch). Dual stop covers the case where the plan is still "valid" but the agent must quit after N failed attempts, N identical no-progress outcomes, or a budget limit.
+- Skills name concrete defaults: `skills/deft-directive-build/SKILL.md` (implement / pre-PR loops), `skills/deft-directive-swarm/SKILL.md` and its Phase 4 / core-ops references (repair / monitor loops).
+- **Delivery / acceptance mechanical enforcement** (durable attempt ledger, material-progress circuit breaker, cross-revision budgets) is **#3143** — library: `packages/core/src/delivery-attempt/` (`evaluatePreDispatch`, unit ledger under `.deft/delivery-attempts/`). Docs: `content/docs/delivery-attempt.md`. #2442 is the principle + skill defaults; #3143 is the deterministic pre-dispatch gate. Route delivery/acceptance loops through that surface rather than inventing a parallel ledger.
+
 **Adaptive Teaching:**
 - ~ When a recommendation is accepted without question, be concise
 - ! When a recommendation is questioned or overridden, explain the reasoning

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@deftai/directive-content",
-  "version": "0.95.0",
+  "version": "0.97.0",
   "description": "Shippable Directive framework content in the consumer .deft/core/ layout (C1 flatten), plus the engine surfaces (.githooks/, Taskfile.yml, tasks/) the deposit wires. Python-free per #2022 Phase 3. Refs #11, #1669, #1967.",
   "license": "MIT",
   "type": "module",

package/packs/patterns/patterns-pack-0.1.json

@@ -35,6 +35,16 @@
       "path": "patterns/llm-app.md",
       "body": null
     },
+    {
+      "id": "operator-log-hygiene",
+      "title": "Operator-log hygiene (#1940)",
+      "description": "Consumer guidance for structured, operator-facing logs: six failure modes, anti-patterns, positive rules, explicit non-goals (no core schema, no default-on, not Insights/LLM telemetry). SLizard is external reference only. Checklist and optional consumer pack stub under docs/.",
+      "triggers": [
+        "operator-log-hygiene"
+      ],
+      "path": "patterns/operator-log-hygiene.md",
+      "body": null
+    },
     {
       "id": "multi-agent",
       "title": "Multi-agent identity separation pattern (#983)",