@event4u/agent-config 5.10.1 → 6.1.0

package/.agent-src/contexts/communication/rules-auto/skill-quality-mechanics.md

@@ -1,138 +0,0 @@
-# Skill quality — mechanics
-
-Description-triggering recipe, merge-preservation invariants, and
-condensation-preservation invariants for the
-[`skill-quality`](../../../rules/skill-quality.md) rule. The minimum
-sharpness table, required sections, frontmatter contract, the
-skill-independence Iron Law, and the refactor-safety NEVER list live
-in the rule; this file is the lookup material when authoring or
-refactoring a skill.
-
-## Description Triggering
-
-Claude routes skills by reading the frontmatter `description`. Polite, generic,
-or hedged descriptions cause **undertriggering** — the skill never loads when it
-should, and the user never learns it exists.
-
-Make descriptions "pushy" — explicit about when to fire:
-
-- Start with a concrete verb phrase: `Use when ...`, `Creates ...`, `Reviews ...`.
-- Name 2+ concrete triggers — domains, symptoms, file types, user phrasing.
-- End with: `... even if they don't explicitly ask for \`<skill-name>\`.`
-- Avoid hedges: `may help with`, `can be useful for`, `covers various`.
-- **Keep it ≤ 200 characters.** `scripts/skill_linter.py` warns at
-  `description_too_long` above this. If the pushy tail pushes you over, cut
-  adjectives, drop the second example phrasing, or collapse a list — do
-  **not** drop the trigger vocabulary or the `even if ...` tail.
-
-Source: [`skills/skill-creator` in `anthropics/skills`](https://github.com/anthropics/skills/blob/main/skills/skill-creator/SKILL.md).
-
-**Litmus test:** Read the description cold, without the skill's body. If you
-cannot name at least two phrasings a user would realistically type that should
-route to this skill, the description is too polite. Rewrite it.
-
-## Merge Preservation
-
-When merging or refactoring skills, the merged result MUST preserve:
-
-1. **Strongest validation** from each source skill
-2. **Strongest example** (good/bad contrast) from each source
-3. **Strongest anti-pattern** from each source
-4. **All concrete decision criteria** that differ between sources
-
-A merge is invalid if:
-- Validation got weaker than the strongest source
-- Examples were lost without replacement
-- Anti-pattern coverage decreased
-- The merged skill became a generic umbrella doc
-
-## Condensation Preservation
-
-When condensing a skill, the condensed version MUST preserve:
-
-- Trigger quality (description + When to use)
-- All procedure steps that contain decisions
-- All concrete validation checks
-- All gotchas and anti-patterns
-- Strongest example (at minimum one good/bad contrast)
-
-Condensation may remove:
-- Verbose explanations
-- Redundant examples (keep the strongest)
-- Commentary that doesn't affect execution
-
-## Senior-tier patterns
-
-Detail spec for the four blocks the [`skill-quality`](../../../rules/skill-quality.md)
-rule requires on `tier: senior` skills. Each block ≤ 6-line spec + 1
-reference pattern. Forward-only — applies to new senior-tier skills,
-no retrofit on existing Wing-1 skills.
-
-### 1. Context-First lead (description)
-
-Two-sentence frontmatter `description`. First sentence: cognition
-cluster anchor — name the domain + the senior role's stance. Second
-sentence: the trigger — what the user types that should fire this.
-
-Pattern:
-
-```
-description: "Use when {trigger paraphrase}. {Domain} cognition for the
-{senior role} — produces {artifact name}."
-```
-
-Anti-pattern: leading with the artifact ("Produces a DCF model …") —
-buries the cognition cluster, undertriggers on cluster-shaped prompts.
-
-### 2. Related Skills (`## Related Skills`)
-
-Two named lists, no ambiguity:
-
-```markdown
-## Related Skills
-
-**WHEN to use this**
-- {situation A this skill resolves better than {peer-1}}
-- {situation B}
-
-**WHEN NOT to use this**
-- {situation C} — route to [`{peer-1}`](../{peer-1}/SKILL.md)
-- {situation D} — route to [`{peer-2}`](../{peer-2}/SKILL.md)
-```
-
-WHEN-NOT entries MUST name the peer and link it. Naming without a
-link drifts the moment the peer renames.
-
-### 3. Proactive Triggers (`## When the agent should load this`)
-
-3–5 concrete user-prompt patterns the agent watches for. Concrete =
-phrases users actually type, not abstract categories.
-
-```markdown
-## When the agent should load this
-
-- "should we build feature X or Y first" → opportunity-tree shaped
-- "what's the ICE / RICE on this backlog" → prioritization shaped
-- "how do I split this epic into shippable slices" → INVEST shaped
-```
-
-Anti-pattern: abstract categories ("prioritization questions",
-"product-shaped requests") — the routing layer matches phrases, not
-taxonomies.
-
-### 4. Output Artifacts (`## Output`)
-
-1–4 named artifacts with concrete shape. Each entry: name +
-shape-hint the orchestrator can cite by name in a handoff.
-
-```markdown
-## Output
-
-1. **opportunity-tree.md** — markdown tree, root = north-star metric,
-   leaves = candidate solutions with hypothesis + evidence rank
-2. **prioritization-table.md** — markdown table, columns =
-   {opportunity, ICE score, evidence-grade, owner, next-step}
-```
-
-Anti-pattern: prose summary ("a doc explaining the prioritization") —
-no orchestrator-citable identifier, no shape contract.

package/.agent-src/contexts/communication/rules-auto/slash-command-routing-policy-mechanics.md

@@ -1,89 +0,0 @@
-# Slash-command routing — cluster mechanics
-
-Lookup table for the `slash-command-routing-policy` rule. Lists the
-locked clusters and their sub-commands so the rule itself can stay at
-its current LOC while still reflecting the full surface. Source of
-truth for the cluster names is
-[`docs/contracts/command-clusters.md`](../../../../../docs/contracts/command-clusters.md);
-this file mirrors that contract for runtime lookup. Linter:
-`scripts/check_cluster_patterns.py` (verifies dispatcher shape).
-
-## Locked clusters and sub-commands
-
-| Cluster | Phase | Sub-commands | Replaces                                                                                                                                        |
-|---|:-:|---|-------------------------------------------------------------------------------------------------------------------------------------------------|
-| `/fix` | 1 | `ci` · `pr-comments` · `pr-bot-comments` · `pr-developer-comments` · `portability` · `refs` · `seeder` | `/fix-ci` · `/fix-pr-comments` · `/fix-pr-bot-comments` · `/fix-pr-developer-comments` · `/fix-portability` · `/fix-references` · `/fix-seeder` |
-| `/optimize` | 1 | `agents` · `augmentignore` · `rtk` · `skills` | `/optimize-agents` · `/optimize-augmentignore` · `/optimize-rtk-filters` · `/optimize-skills`                                                   |
-| `/feature` | 1 | `explore` · `plan` · `refactor` · `roadmap` | `/feature-explore` · `/feature-plan` · `/feature-refactor` · `/feature-roadmap`                                                                 |
-| `/chat-history` | 2 | `show` | `/chat-history` (legacy status) — `resume` / `clear` / `checkpoint` removed in `road-to-chat-history-hook-only`                                 |
-| `/agents` | 2 | `init` · `optimize` · `audit` | `/copilot-agents-init` · merger of `/optimize-agents-md` + `/copilot-agents-optimize` · `/optimize-agents` (folder ops moved to `/optimize:agents-dir`) |
-| `/memory` | 2 | `add` · `load` · `promote` · `propose` | `/memory-add` · `/memory-full` · `/memory-promote` · `/propose-memory`                                                                          |
-| `/roadmap` | 2 | `create` · `process-step` · `process-phase` · `process-full` | `/roadmap-create` · `/roadmap-process` (replaced — autonomous, no per-step gate; `process-phase` is the default execution scope)                |
-| `/module` | 2 | `create` · `explore` | `/module-create` · `/module-explore`                                                                                                            |
-| `/tests` | 2 | `create` · `execute` | `/tests-create` · `/tests-execute`                                                                                                              |
-| `/context` | 2 | `create` · `refactor` | `/context-create` · `/context-refactor`                                                                                                         |
-| `/override` | 2 | `create` · `manage` | `/override-create` · `/override-manage`                                                                                                         |
-| `/judge` | 2 | `solo` · `on-diff` · `steps` | `/judge` (legacy standalone) · `/do-and-judge` · `/do-in-steps`                                                                                 |
-| `/commit` | 2 | flag: `--in-chunks` | `/commit:in-chunks`                                                                                                                             |
-| `/create-pr` | 2 | flag: `--description-only` | `/create-pr:description-only`                                                                                                                   |
-
-## Routing semantics
-
-1. The user invokes a cluster sub-command in **one of two equivalent
-   forms**:
-   - `/<cluster>:<sub> [args]` — **canonical**. Single token, plays
-     well with shell autocompletion and the slash-command picker.
-   - `/<cluster> <sub> [args]` — **space-separated equivalent**.
-     Identical semantics. Accept everywhere.
-
-   Both forms route to the **same file** and the **same dispatcher**.
-   Implementations MUST treat `:` and `<space>` as interchangeable
-   delimiters at the cluster boundary. Autocompletion-aware UIs
-   (Claude.ai picker, IDE slash-menus, shell completers) should
-   surface the `:` form because it stays a single token.
-
-2. Match the cluster against the table above. If the leading token is
-   a dispatcher cluster, route to the dispatcher's `commands/<cluster>.md`
-   and let the dispatcher's "Dispatch" section pick the sub-command.
-
-3. If the leading token is a flag-cluster (`/commit`, `/create-pr`),
-   the cluster file is the entry point itself; flags absorb the
-   former helper command.
-
-4. **Legacy atomic shims** (`/fix-ci`, `/agents-audit`, …) keep working
-   for one release cycle. They emit a deprecation warning and forward
-   to the cluster invocation. New invocations should always use the
-   cluster form. **`/roadmap-execute` is removed** — invocations route
-   to `/roadmap:process-phase` (default execution scope) with a
-   one-time migration notice. Legacy `/roadmap-process[:<sub>]`
-   invocations (the short-lived top-level cluster) likewise forward
-   to `/roadmap:process-<sub>`.
-
-5. If a sub-command is unknown, the dispatcher prints the menu — never
-   guess.
-
-## Why colon is canonical
-
-Locked by [ADR-003](../../../../docs/decisions/ADR-003-flat-cluster-subs-and-colon-syntax.md)
-(2026-05-07) alongside the flat-cluster + composite-sub-name shape.
-
-- **Single token in autocompleters.** `roadmap:process-phase` completes
-  as one piece; `roadmap process-phase` requires the picker to
-  re-prompt after the space.
-- **Stable in chat history and logs.** Greppable as one string.
-- **Unambiguous against free-text args.** `/roadmap:process-phase
-  road-to-X.md` parses cleanly; the picker never confuses the sub
-  with the first argument.
-- **Symmetric across the catalog.** `/commit:in-chunks` and
-  `/create-pr:description-only` already use this form; cluster
-  dispatchers gain it without regressing the space form.
-
-## Removal cycle
-
-| Cycle | Active form | Shim form |
-|---|---|---|
-| `1.15.x` / `1.16.x` | Phase 1 cluster commands | Phase 1 atomic shims |
-| `1.17.0` | Phase 1 + Phase 2 cluster commands | Phase 2 atomic shims (Phase 1 atomics removed) |
-| next minor after `1.17.x` | Cluster commands only | — (Phase 2 atomics removed) |
-
-Consumers see the canonical surface as the cluster form throughout.

package/.agent-src/contexts/communication/rules-auto/think-before-action-mechanics.md

@@ -1,98 +0,0 @@
-# Think Before Action — mechanics
-
-Workflow tables, verification matrix, and failure modes for the
-[`think-before-action`](../../../rules/think-before-action.md) rule.
-The rule body holds the obligation surface (analyze before coding,
-verify with real tools, no blind retries). This file is the lookup
-material agents pull when the rule fires.
-
-## The Developer Workflow — five-step order
-
-Work like a developer, not a text generator. Skipping steps 1–3 is the
-#1 cause of wrong implementations and wasted retries.
-
-1. **Understand** — Read the task, ticket, acceptance criteria. Unclear
-   → ask, don't assume.
-2. **Analyze** — Read affected code, trace data flow, compare with
-   requirements and existing patterns.
-3. **Plan** — Decide what to change, what NOT to change, and how to
-   verify success.
-4. **Implement** — Focused changes. Follow existing patterns. No
-   unrelated rewrites.
-5. **Verify** — Run tests, hit the endpoint, check the UI. Real
-   execution, never "should work".
-
-## Minimum read set — read before you write
-
-Before editing code, read the minimum set that defines its behavior:
-
-1. **Symbol under edit** — full method/function body, not just the
-   planned line.
-2. **Direct callers** — one level up (`grep -rn "<symbol>"` + open
-   the matches).
-3. **Tests** — if a test file exists, it encodes the contract.
-4. **One layer of related abstractions** — interface, parent class,
-   or trait (one hop, not the full hierarchy).
-5. **Data changes** — the migration that created the column + any
-   seeder/factory that references it.
-
-Stop expanding once you can explain, in your own words, what the
-symbol does, who calls it, and what breaks if you change its
-behavior. Cannot → read more.
-
-## Consult memory before editing
-
-Prior decisions and invariants live in the memory layer. Via
-[`memory-access`](../../../../../docs/guidelines/agent-infra/memory-access.md),
-call `retrieve(types=["architecture-decisions", "domain-invariants"], keys=<touched paths>, limit=3)`.
-A matching `architecture-decision` explains *why* the current shape
-exists; a matching `domain-invariant` is a hard constraint. Cite the
-`id` if a match influences the plan.
-
-## Verify with real tools
-
-| What changed | How to verify |
-|---|---|
-| **Backend/API** | `curl`, Postman (or Postman MCP if available), test endpoint |
-| **Frontend/UI** | Playwright MCP or browser — check rendered state, interactions |
-| **Logic/flow** | Xdebug (or Xdebug MCP if available) — trace execution, inspect variables |
-| **CLI/Jobs** | Run the command, check side effects, verify exit code |
-| **Database** | Query the result, check migrations ran correctly |
-
-If a debugging/testing tool is available as MCP server — prefer it
-over manual alternatives. Verification not possible (no endpoint, no
-UI, no test) → state what is missing and explain how the change
-should be tested.
-
-## Reduce output — targeted tools over full dumps
-
-Never load full datasets into context. Extract what you need:
-
-- `jq` for JSON: `curl -s /api/users | jq '.[0] | {id, email}'` — not the full response
-- `rg` / `grep` for text: search specific patterns, not full files
-- `head`, `tail`, `cut`, `sort`, `uniq` for narrowing results
-- `--filter`, `--json`, `--format` flags on CLI tools — use them
-- Laravel: `route:list --json | jq` over raw `route:list` dump
-- Logs: filter by request ID, timestamp, or error type — not full log files
-
-## No blind retries
-
-- Failure → **read the error**, analyze the cause, then fix it.
-- Do NOT retry the same approach hoping for a different result.
-- Do NOT loop through trial-and-error when one targeted inspection
-  would reveal the cause.
-- Max 2 retries for the same approach — then stop and rethink.
-
-## Open files are context, not intent
-
-The editor may report that the user has a file open. Background
-context only — does NOT mean the user's message is about that file.
-
-- The user's message determines intent — not which file is open.
-- A user can have `README.md` open and type `/condense` — intent is
-  to condense, not to discuss the README.
-- A user can have `UserController.php` open and ask "how do tests
-  work?" — intent is testing, not the controller.
-- Treat the open file as relevant only when the user's message
-  explicitly references it (e.g. "fix this file", "what does this
-  do?", "update the open file").

package/.agent-src/contexts/contracts/artifact-engagement-flow.md

@@ -1,259 +0,0 @@
----
-stability: beta
----
-
-# Artifact Engagement — Flow & Recording Contract
-
-> Cross-cutting reference for the artifact-engagement telemetry system.
-> The schema, CLI, and engine ship first; the agent-side hooks (this
-> document) ship after.
->
-> - **Created:** 2026-04-30
-> - **Status:** schema, engine, recording, aggregator, renderer, and
->   redaction validator are in place. Dogfooding next.
-
-This document is the stable reference for **what gets recorded, when, and
-under which constraints**. The roadmap tracks phased delivery; the rule
-([`artifact-engagement-recording`](../../.agent-src.uncondensed/rules/artifact-engagement-recording.md))
-tells the agent when to fire; this doc explains the contract every
-recording must honour.
-
-## What this is
-
-A measurement layer that tells maintainers which **skills, rules,
-commands, guidelines and personas** the agent actually consults and
-applies during a `/implement-ticket` or `/work` run. The output (a local
-JSONL log) becomes the input to the Phase 4 aggregator + report renderer.
-
-## What this is *not*
-
-- Token-spend tracking — handled separately by the cost-profile system.
-- Tool-call telemetry — out of scope.
-- A retirement decision-maker — Phase 4's report surfaces signal; humans
-  decide what to retire.
-- A consumer-facing analytics product — local-only, opt-in, never
-  uploaded.
-
-## Threat model in one paragraph
-
-Engagement data is **observation**, not delivery. A missed event is
-cheap. A leaked prompt, a leaked path, or a leaked secret is not. Every
-field in the schema is **id-only**: no free-text, no payloads, no paths.
-The CLI rejects oversized strings on the input boundary; the agent must
-not even attempt to write content.
-
-## When the agent records
-
-Two granularities, one per task or one per phase-step:
-
-```
-refine → memory → analyze → plan → implement → test → verify → report
-                          ↑
-            granularity: phase-step → 1 record per arrow crossed
-            granularity: task        → 1 record on terminal state only
-```
-
-The setting lives at `telemetry.artifact_engagement.granularity` in
-`.agent-settings.yml`. Default `task`. Both flows
-([`/implement-ticket`](../../.agent-src.uncondensed/commands/implement-ticket.md)
-and [`/work`](../../.agent-src.uncondensed/commands/work.md)) use the
-same eight-step contract from
-[`implement-ticket-flow.md`](implement-ticket-flow.md).
-
-### Boundary semantics
-
-A boundary is **closed** when:
-
-- The dispatcher returns `SUCCESS`, `BLOCKED`, or `PARTIAL` for the
-  current step (phase-step granularity), or
-- The full eight-step flow reaches a terminal state (task granularity).
-
-A boundary is **never** closed by:
-
-- An error inside the agent's tool call (the user's task is paramount;
-  see "failure modes" below).
-- A model-side exception or timeout.
-- Settings reload mid-flow — settings are read once per task and cached.
-
-Within a single boundary, repeated `consulted` / `applied` mentions of
-the same `<kind>:<id>` pair **dedupe**. Reading `php-coder` three times
-records once.
-
-## What counts as consulted vs applied
-
-| Term | Meaning | Examples |
-|---|---|---|
-| **`consulted`** | The agent **read** the artefact this boundary | Opened `SKILL.md`, scanned a rule body, looked at a guideline, checked persona contract, cited the artefact id in reasoning |
-| **`applied`** | The artefact **influenced the output** this boundary | A skill's procedure produced the code; a rule's gate halted a flow; a guideline's pattern shaped the diff |
-
-`applied` is a strict subset of `consulted`. When in doubt → record as
-`consulted` only. Over-recording `applied` inflates the engagement
-signal and defeats the whole point of the system.
-
-## Forbidden — what NEVER goes into a record
-
-The privacy contract is enforced at **four** layers — schema (write
-gate), aggregator (read gate via `parse_event`), renderer (export gate),
-and CLI (surface gate). Each layer rejects the same set of shapes;
-defense in depth means a leak has to bypass all four to escape:
-
-- File paths — any string containing `/`, `\`, or a control character.
-- File extensions — trailing `.md`, `.py`, `.json`, `.yaml`, `.yml`,
-  `.php`, `.ts`, `.js`, etc. Detected by
-  `re.compile(r"\.[a-z0-9]{1,10}$", re.IGNORECASE)` in
-  `telemetry.engagement.check_id_redaction`.
-- Source code, prompts, ticket bodies, AC text, comments.
-- Branch names, commit shas, PR numbers, URLs.
-- Secrets, env vars, credentials, customer data.
-- Free-text strings longer than 200 chars.
-- Leading or trailing whitespace, tabs, newlines.
-- Empty strings.
-
-The id namespaces are stable and bounded:
-
-| Kind | Source | Example |
-|---|---|---|
-| `skills` | `.agent-src/skills/<id>/SKILL.md` | `php-coder`, `eloquent` |
-| `rules` | `.agent-src/rules/<id>.md` | `scope-control`, `language-and-tone` |
-| `commands` | `.agent-src/commands/<id>.md` | `commit`, `create-pr` |
-| `guidelines` | `docs/guidelines/<path>/<id>.md` | `agent-interaction-and-decision-quality` |
-| `personas` | `.agent-src/personas/<id>.md` | `qa`, `senior-engineer` |
-
-`task_id` is the ticket key (`PROJ-123`) for `/implement-ticket` or a
-short opaque slug derived from the prompt for `/work`. Branch names,
-file paths, and free-text titles are forbidden in `task_id` — see the
-schema's `EngagementSchemaError` cases.
-
-### The four enforcement layers
-
-1. **Schema (write gate)** — `EngagementEvent.validate()` in
-   `telemetry/engagement.py` runs `check_id_redaction` over `task_id`
-   and every `consulted` / `applied` artefact id. The CLI exits `1`
-   when this fires; nothing reaches the JSONL.
-2. **Aggregator (read gate)** — `aggregator._iter_events` calls
-   `parse_event`, which re-runs the same validator. A pre-validator
-   line (e.g. an archived snapshot from before the validator landed)
-   is **skipped** and counted in `result.skipped_lines`. The renderer
-   never sees it.
-3. **Renderer (export gate)** — `_stat_to_dict` (JSON) and the
-   markdown row builder both call `check_id_redaction` again before
-   emitting any id. If a caller bypasses `parse_event` and hand-builds
-   an `AggregateResult`, the renderer raises `EngagementSchemaError`
-   instead of producing the row.
-4. **CLI (surface gate)** — `telemetry_report.main` catches
-   `EngagementSchemaError` from the renderer and exits `2` with a
-   `redaction validator refused report` message. A bad row is never
-   written to stdout, never piped to a teammate.
-
-A leak would have to defeat all four layers — write the JSONL outside
-the CLI, parse it outside `parse_event`, render it outside the
-project's renderer, and ship it to a teammate without the CLI in the
-loop. The contract treats that as out of scope.
-
-## How the agent records
-
-```bash
-./agent-config telemetry:record \
-  --task-id "$TASK_ID" \
-  --boundary task \
-  --consulted skills:php-coder \
-  --consulted rules:scope-control \
-  --applied skills:php-coder
-```
-
-Exit codes (the agent must read these):
-
-| Exit | Meaning | Action |
-|---|---|---|
-| `0` | Recorded, or telemetry disabled (silent no-op) | Continue |
-| `1` | Schema validation failed | Log internally, **continue** the user's task — do not halt |
-| `2` | IO failure (lock contention, disk full) | Same — observation, not delivery |
-
-Schema-rejection messages go to stderr; the agent reads them once and
-moves on. The user's task always takes priority.
-
-## Failure modes — DO NOT block the user's task
-
-- Telemetry is **observation**, not a delivery requirement.
-- A missing event is cheap; a halted task because telemetry can't write
-  is a critical failure mode that defeats the whole opt-in property.
-- The only error the agent surfaces to the user: when the user asked
-  for telemetry (`telemetry:status` confirms enabled) but no event
-  reached the log over a full task — that is a real bug.
-
-## Cost floor — what "default-off" means
-
-When `telemetry.artifact_engagement.enabled: false` (or section absent):
-
-- The rule is `auto` and the description does not match a typical
-  conversation; the rule never loads. Cost floor: 0 tokens.
-- The CLI exits `0` with no output and no file IO.
-- The engine (`work_engine.dispatcher`, `work_engine.cli`) does not
-  import any `telemetry.*` module — locked by
-  [`tests/telemetry/test_cost_floor.py`](../../tests/telemetry/test_cost_floor.py).
-- On cloud surfaces (Claude.ai Web, Skills API), the rule's
-  `cloud_safe: noop` marker keeps the rule inert regardless of settings.
-
-## Where the JSONL lives
-
-Default path: `.agent-engagement.jsonl` in the consumer repo root.
-Configurable via `telemetry.artifact_engagement.output.path`. The path
-is **always** added to the consumer's `.gitignore` block by the
-installer (Phase 1 wiring). Verify locally:
-
-```
-$ grep agent-engagement .gitignore
-.agent-engagement.jsonl
-```
-
-## How to audit a JSONL by hand
-
-The fastest path is the project's own validator — it enforces every
-rule listed above:
-
-```bash
-# Validate every line against the schema + redaction floor
-python3 -c '
-import pathlib, sys
-sys.path.insert(0, ".agent-src.uncondensed/templates/scripts")
-from telemetry.engagement import EngagementSchemaError, parse_event
-log = pathlib.Path(".agent-engagement.jsonl")
-ok = bad = 0
-for i, line in enumerate(log.read_text().splitlines(), 1):
-    if not line.strip():
-        continue
-    try:
-        parse_event(line + "\n")
-        ok += 1
-    except EngagementSchemaError as e:
-        bad += 1
-        print(f"line {i}: {e}", file=sys.stderr)
-print(f"{ok} valid, {bad} rejected")
-'
-
-# A bad-line spot-check that does not depend on the validator
-python3 -c '
-import json, pathlib, re
-forbidden = re.compile(r"[/\\\\]|\.[a-z0-9]{1,10}$", re.IGNORECASE)
-for line in pathlib.Path(".agent-engagement.jsonl").read_text().splitlines():
-    if not line.strip():
-        continue
-    obj = json.loads(line)
-    for kind in ("consulted", "applied"):
-        for ids in obj.get(kind, {}).values():
-            for v in ids:
-                if forbidden.search(v) or len(v) > 200:
-                    print("LEAK:", v)
-'
-```
-
-Either recipe is safe to run on a co-worker's archived JSONL — neither
-writes anything, both surface the same shapes the four enforcement
-layers reject.
-
-## See also
-
-- [`artifact-engagement-recording`](../../.agent-src.uncondensed/rules/artifact-engagement-recording.md) — agent-side trigger
-- [`implement-ticket-flow`](implement-ticket-flow.md) — the eight-step contract this rule observes
-- [`scripts/telemetry/`](../../.agent-src.uncondensed/templates/scripts/telemetry/) — schema, boundary session, settings reader
-- [`tests/telemetry/`](../../tests/telemetry/) — contract enforcement (schema, settings, aggregator, renderer, CLI, cost-floor, redaction)