@event4u/agent-config 8.12.0 → 9.0.0

package/dist/agent-src/rules/context-hygiene.md

@@ -8,6 +8,8 @@ triggers:
   - intent: "tool loop"
   - intent: "fresh chat"
   - keyword: "3-failure"
+routes_to:
+  - "guideline:agent-infra/context-hygiene-mechanics"
 workspaces: [agent-config-maintainer, construction, engineering, finance, founder, gtm, legal-review-prep, ops, product, small-business]
 packs: [meta]
 ---
@@ -24,31 +26,13 @@ packs: [meta]
 
 Monitor for **context decay** — long conversations degrade quality and waste tokens.
 
-**Suggest a new chat when:**
-
-- Conversation exceeds **~20 user messages**
-- Topic **changes completely**
-- Re-reading files already in context
-- **15+ completed tasks** and new unrelated topic
-- Branch changed since start
-- ~24 hours passed
+**Suggest a new chat when:** ~20+ user messages · complete topic change ·
+re-reading files already in context · 15+ completed tasks and a new unrelated
+topic · branch changed since start · ~24 hours passed.
 
 **Repeat** at multiples: messages 20/40/60, tasks 15/30/45.
-**ONLY at exact thresholds.** Between: silence.
-
-**How to suggest:**
-
-Estimate token cost: responses × ~1,500 tokens.
-
-```
-> ⚡ This conversation has ~{N} messages (~{N×1500} tokens history cost — charged on EVERY request).
-> A fresh chat saves ~{N×1500} input tokens per request.
->
-> 1. Start fresh — I'll initiate a session handoff
-> 2. Continue here
-```
-
-**If the user picks 1:** Initiate a session handoff or start fresh.
+**ONLY at exact thresholds.** Between: silence. Suggestion template
+(token-cost estimate + numbered options): the mechanics guideline below.
 
 ## The 3-Failure Rule
 
@@ -58,40 +42,20 @@ When **3 consecutive attempts** at the same task fail (code fix, test fix, confi
 2. **State dump** — summarize what was tried, what failed, and what you know so far.
 3. **Recommend fresh start** — suggest a fresh session with the state dump as context, or ask for a different approach.
 
-**What counts as a failure:**
-
-- Code change that doesn't fix the problem
-- Test that still fails after the fix
-- Quality check (type-checker, linter, formatter) that still errors
-- Build/deploy that fails after config change
-
-**Does NOT reset the counter:** Unrelated tasks. User providing new information (course correction).
+**What counts as a failure:** a change that doesn't fix the problem · a test still failing after the fix · a quality check still erroring · a build/deploy failing after a config change. **Does NOT reset the counter:** unrelated tasks; the user providing new information (course correction).
 
 **Failure identity — same error vs new error.** Failure signature = **same target + same error class** (same failing test + same assertion/exception, same lint rule id, same build error).
 
 - **Same failure signature twice → stop and pivot now.** Don't burn the third attempt on a near-identical retry of a fix that already failed the same way — a repeated identical signature means the hypothesis is wrong, not under-applied. Change strategy (re-read source, new hypothesis, ask).
 - **New error signature each attempt = progress.** Peeling one error to reveal a different one is forward motion; counter continues — learning, not looping.
 
-**Hard-blocker classes — skip retries, go straight to ask/surface.** On the **first** occurrence, do not count toward the 3 — stop and surface:
-
-- Missing credentials / unset required secret or token.
-- Permission denied (auth/authz, file mode, protected branch, scope).
-- Spend / quota / rate limit reached (billing cap, API quota, 429 that won't self-clear).
-- External-service `5xx` / outage / DNS-unreachable — a dependency is down, not your code.
-
-Retrying a hard-blocker is the canonical wasted-attempt; the fix is a decision or external change only the user/environment can make.
+**Hard-blocker classes — skip retries, go straight to ask/surface.** On the **first** occurrence, do not count toward the 3 — stop and surface: missing credentials / unset secret · permission denied · spend / quota / rate limit reached · external-service 5xx / outage. Retrying a hard-blocker is the canonical wasted attempt; the fix is a decision or external change only the user/environment can make.
 
 ## Tool Loop Detection
 
 Calling the **same tool** more than **2 times in a row** with similar parameters = loop.
-
-**Immediate action:**
-1. **STOP** all tool calls.
-2. **Do the task directly** — write the code, run the command, answer the question.
-3. If you can't proceed — ask the user for help.
-
-`sequentialthinking` is especially prone to loops. Use at most **once** per task,
-NEVER for simple file operations, command execution, or straightforward edits.
+**Immediate action:** 1. STOP all tool calls. 2. Do the task directly. 3. Can't proceed → ask the user.
+`sequentialthinking` is especially prone to loops: at most **once** per task, NEVER for simple file operations, command execution, or straightforward edits.
 
 ## Read-Loop Detection — the 15 / 25 rule
 
@@ -101,74 +65,16 @@ EVERY TURN MUST EDIT, RUN, OR ASK.
 ```
 
 **Read-only turn:** only `view` / `codebase-retrieval` / `grep` /
-`git log` / `git show`. No `str-replace-editor`, `save-file`, no
-test/build/quality run, no `git commit`.
-
-**15-min warning (3 read-only turns in a row) — change approach.**
-Next turn MUST contain at least one of: an edit, a test/build/quality
-command, or an explicit user question. Self-check:
-
-1. Source expectation known? If no → read **once**, then act.
-2. Can a single failing test name the error? If yes → run it now.
-3. Regression in working code? → `git log` + `git show <sha> -- <file>`.
-4. Guessing at mock / payload shape? → read the producer **once**.
-
-**25-min abort (5 read-only turns) — STOP and ask:**
+`git log` / `git show`. No edit/save, no test/build/quality run, no `git commit`.
 
-```
-> ⛔ Loop: N read-only turns, ~M min. Read: <files>. Hypothesis: <X>.
-> 1. Different approach (suggestion: <Y>)
-> 2. Point me at the right spot
-> 3. Fresh chat with state dump
-```
-
-Non-bypassable. Autonomous mandate (`/work`, `/roadmap:process-*`,
-"entscheide selbst") does **not** lift the abort — it is the safety
-net that protects autonomy from becoming a token sink.
-
-Debug procedure for "I'm in a read loop fixing tests" →
-[`systematic-debugging § Debug micro-loop`](../skills/systematic-debugging/SKILL.md#debug-micro-loop--one-test-one-fix-one-re-run).
-
-## State dump format
-
-```
-## State Dump: [Task]
-### Tried: 1. [Approach] → [Why failed] 2. ... 3. ...
-### Known: [Key facts]
-### Hypothesis: [Best guess for root cause]
-### Recommendation: [Next approach for fresh session]
-```
+**15-min warning (3 read-only turns in a row) — change approach.** The next turn MUST contain at least one of: an edit, a test/build/quality command, or an explicit user question (self-check in the mechanics guideline).
 
-Use `/agent-handoff` to generate a context summary for a fresh conversation.
+**25-min abort (5 read-only turns) — STOP and ask** with the abort block (template in the mechanics guideline). Non-bypassable: an autonomous mandate does **not** lift the abort — it is the safety net that protects autonomy from becoming a token sink.
 
-## Augment-specific: Ignored Skills Recovery
+Body migrated to [`guideline:agent-infra/context-hygiene-mechanics`](../docs/guidelines/agent-infra/context-hygiene-mechanics.md) (per P4 of `road-to-kernel-and-router.md`) — the freshness-suggestion template, the read-loop self-check + abort block, the state-dump format + `/agent-handoff` pointer, the Augment ignored-skills recovery flow, and the Copilot no-hook fallback (manual `context_hygiene_hook` refresh).
+Trigger-set above activates this routing on demand, independent of the discipline profile (ADR-110).
 
-Skills excluded via `.augmentignore` don't appear in `<available_skills>`.
-If you need an ignored skill: read its SKILL.md directly, apply guidance, then ask:
-
-```
-> 💡 I loaded `{name}` manually — currently ignored in `.augmentignore`.
-> 1. Remove from ignore — relevant for this project
-> 2. Keep ignored — one-off
-```
-
-## Copilot fallback
-
-GitHub Copilot has no `PostToolUse` hook surface, so
-`scripts/context_hygiene_hook.ts` cannot run structurally and
-`agents/runtime/state/context-hygiene.json` is not maintained automatically
-(turn count, loop signal, freshness milestones at 20/40/60).
-
-The cooperative path: track turns and tool-loop signals from memory
-during the conversation and apply the suggest-a-new-chat / 3-failure
-stop / loop-detection rules above. To refresh the state file
-manually so the dashboard or another tool can read the latest
-counters, run:
-
-```bash
-./scripts-run src/scripts/context_hygiene_hook < /dev/null
-```
+## See also
 
-The script reads from stdin if a JSON envelope is provided and
-otherwise writes a no-op snapshot under the shared dispatcher lock.
-Exit code is always 0 — hooks must never block the agent loop.
+- [`guideline:agent-infra/context-hygiene-mechanics`](../docs/guidelines/agent-infra/context-hygiene-mechanics.md) — templates + per-host procedures.
+- [`systematic-debugging § Debug micro-loop`](../skills/systematic-debugging/SKILL.md) — the read-loop debug procedure.

package/dist/agent-src/rules/design-fidelity.md

@@ -17,6 +17,8 @@ applies_to_user_types:
   - "creator"
   - "developer"
   - "maintainer"
+routes_to:
+  - "guideline:design-fidelity-mechanics"
 workspaces: [engineering]
 packs: [frontend-design]
 ---
@@ -71,66 +73,8 @@ porting, or modifying UI to match it.
 - The user explicitly invites exploration ("show me options", "redesign this", "improve the layout") — that authorises deviation for that turn.
 - Non-UI surfaces (scripts, CLI, backend).
 
-## How to surface a deviation — do NOT execute it
-
-Name what the spec shows, what you would change, and why — as a numbered option
-per [`user-interaction`](user-interaction.md). The user picks. Honesty about
-**behaviour** (a control not yet wired) never licenses changing the **design**:
-a faithful visual plus a labelled "not wired yet" note beats an invented
-redesign.
-
-## Failure modes
-
-- Swapping the prototype's font / typeface because another "reads better".
-- Replacing a specified control (slider, stepper, chip) with a different control.
-- Dropping or adding an element the prototype shows ("+", a send→stop toggle, a warning chip).
-- Restructuring layout or moving sections "because the flow is better".
-- Treating an internal "honesty gate" or "stub" concern as licence to redesign the UI.
-- Re-running a redesign after the user already said "match the prototype".
-
-## Surgical visual edits
-
-A request to change one visual thing — a colour, a label, a single element — is
-a **targeted edit**, not a redesign licence. Apply the same
-[`minimal-safe-diff`](minimal-safe-diff.md) discipline to design work that
-backend edits have always owed.
-
-- **Change only the semantic target.** Preserve the surrounding layout,
-  spacing, typography, dimensions, content, animation, and interaction states.
-  Do not rewrite the component, reflow the section, or "modernise" neighbours
-  while you are in there. (fixtures: `daf-edit-preservation`, `daf-unwanted-variations`.)
-- **A broader redesign needs an explicit trigger.** Only phrases like *"new
-  direction"*, *"from scratch"*, *"make it feel premium"*, *"rework the flow"*,
-  or *"give me variations / options"* license a from-scratch rework. Absent such
-  a phrase, a "fix / change / update the X" request is surgical — when unsure
-  which, ask ([`ask-when-uncertain`](ask-when-uncertain.md)). (fixture: `daf-redesign-trigger`.)
-- **Preserve stable anchors.** Where the host exposes DOM/comment metadata, keep
-  comment anchors and screen labels intact so the edit stays locatable. Where
-  the host has no such surface, preserve stable semantic anchors already present
-  in source comments / `data-*` attributes — never strip them, and do not invent
-  new ones.
-
-## Asset & imagery discipline
-
-Visual artifacts carry **real assets or honest placeholders — never fabricated
-brand evidence**. The design-surface instance of the no-invented-facts floor.
-
-- **Copy owned assets through the project's accepted path.** Reference or copy
-  project-owned assets (logos, icons, fonts, images) via the target project's
-  asset directory/pipeline — never hotlink a design-system's internal URL, never
-  bulk-copy a huge source folder. (fixtures: `daf-missing-asset`, `daf-external-asset-url`.)
-- **Real imagery where inspection matters.** On visual pages/decks, use actual
-  product / place / object / state imagery where the image IS the proof (a
-  product screenshot, a real dashboard state). Decorative atmosphere is not proof
-  — never pass a stock-like or invented image off as the real product. An
-  invented product screenshot is fabricated evidence. (fixture: `daf-invented-screenshot`.)
-- **Icons follow the iconography floor** — no emoji-as-icon in serious UI, no
-  hand-rolled icon when a set exists; see
-  [`iconography`](../skills/iconography/SKILL.md) § Iconography floor.
-- **Ask before adding material — no unrequested filler.** Never generate copy,
-  placeholder sections, or decorative blocks the user did not ask for to "complete"
-  a design. Brief silent on a region → surface the gap ([`ask-when-uncertain`](ask-when-uncertain.md))
-  or leave an honest placeholder; never invent filler to fill space.
+Body migrated to [`guideline:design-fidelity-mechanics`](../docs/guidelines/design-fidelity-mechanics.md) (per P4 of `road-to-kernel-and-router.md`) — surgical visual edits (targeted-edit vs redesign-trigger discipline, stable anchors), asset & imagery discipline (owned-asset path, real-imagery-as-proof, iconography floor, no unrequested filler), deviation-surfacing shape, failure-mode catalog, `daf-*` fixtures.
+Trigger-set above activates this routing on demand, independent of the discipline profile (ADR-110).
 
 ## See also
 

package/dist/agent-src/rules/domain-adoption-policy.md

@@ -15,6 +15,8 @@ validator_ignore:
   - type: "substring"
     pattern: ".agent-src.uncondensed/"
     reason: "Rule names the authoring tree as the gated-entry location for new domain plates."
+routes_to:
+  - "guideline:agent-infra/domain-adoption-gates"
 workspaces: [agent-config-maintainer]
 packs: [meta]
 ---
@@ -40,116 +42,18 @@ ALL THREE PASS, OR THE ROADMAP MARKS THE DOMAIN GATED.
 ```
 
 The three gates fire before any skill, guideline, command, or rule from the
-domain enters `.agent-src.uncondensed/`. A council session may inform the
-decision but cannot replace the gate evidence.
+domain enters `src/`. A council session may inform the decision but cannot
+replace the gate evidence. Any gate not citeable → **defer** + a watch-only
+note under `agents/settings/contexts/domain-watch/<domain>.md`; never silently
+shrink scope to dodge a gate.
 
-## Gate 1 — Demand signal
-
-At least one of the following must be **true and citeable** in the roadmap:
-
-- **≥ 2 consumer projects** in the domain. Cite repository names or
-  `agents/settings/contexts/` notes — not "I think there might be".
-- **Named user direction with target.** A specific user ask plus a target
-  project / use case — e.g. "harvest the mobile skills for project X, due
-  next quarter". Vague *"this might be useful"* does not count.
-- **Public-incident pull.** A reproducible incident on a consumer project
-  the domain would have prevented, captured in `agents/settings/contexts/` with
-  the missing surface area named.
-
-If none of the three is citeable, **defer**. Open a watch-only context note
-under `agents/settings/contexts/domain-watch/<domain>.md` listing the missing signal
-so the next harvest can re-evaluate without re-relitigating the case.
-
-## Gate 2 — Named maintenance owner
-
-Domain plates rot. Pick the owner before the import, not after.
-
-- The roadmap names a **single maintainer** (not "the team", not "TBD")
-  responsible for the domain quarterly review.
-- The owner commits to the **refresh cadence** — quarterly review at
-  minimum, faster if the domain is volatile (mobile RN/Expo SDK,
-  ML model APIs).
-- Each adopted artefact carries an **inline upstream-source line** with
-  SHA + last-checked timestamp so refresh is mechanical, not archaeological.
-
-If no owner is named or no cadence is set, **defer**. An unowned domain
-plate becomes broken authoritative-links and stale skills inside two cycles.
-
-## Gate 3 — CI-tooling decision
-
-Either the domain's verification tooling is validated in CI, or the suite
-explicitly accepts platform-bound reference-only status.
-
-- **Validated.** The CI pipeline runs the relevant linters/tests/integration
-  checks for the domain (e.g. `mobile-e2e` runners, ML model validation,
-  contract conformance) on every PR. Cost noted in the roadmap risk
-  register.
-- **Out-of-scope (reference-only).** The domain is a platform fact the
-  suite cannot validate (iOS Simulator on non-macOS runners, GPU-bound
-  ML, hardware-bound IoT). The roadmap states this explicitly; affected
-  artefacts carry a "reference-only on \<unsupported platforms\>" header
-  so consumers do not file false-positive bugs.
-
-If neither line is drawn, **defer**. Half-validated CI silently rots the
-domain — green builds while the underlying tooling drifts.
-
-## Sunset Policy stacks on top
-
-Every domain track inherits the authoritative-link Sunset path documented
-in any plate that imports volatile upstream content:
-
-- Volatile content (SDK-pinned, API-pinned, tool-version-pinned) lives as
-  guideline body + SHA-pinned upstream link, not as forked scripts.
-- Refresh trigger: quarterly cadence or earlier if a SHA-pinned link
-  404s in CI.
-- The `check-refs` and `check-portability` linters apply unchanged.
-
-Adopting a domain does not exempt it from any other suite-wide rule —
-`augment-edit-discipline`, `skill-quality`, `size-enforcement`,
-`rule-type-governance`. Every domain artefact passes the same gates as a
-core artefact.
-
-## Failure modes
-
-- *"It's just one skill, not a domain."* — Audit the skill's prerequisites.
-  If it pulls in a new toolchain, simulator, language runtime, or
-  platform-specific build system, it **is** a domain entry. Run the gates.
-- *"The upstream is well-maintained, we can just track it."* — Tracking
-  upstream means owning the diff, the breaking changes, and the migrations.
-  Tracking is maintenance work; budget for it under Gate 2 or skip the
-  adoption.
-- *"We'll add CI later."* — Later does not arrive. Either CI is wired in
-  the same plate, or the artefacts ship with explicit reference-only
-  headers so users do not assume validated coverage.
-- *"Council convergence is enough."* — Council informs the gates; it does
-  not replace them. A council session may surface that all three gates
-  pass; the roadmap still cites the evidence.
-- *"Demand-signal is the user asking once."* — Single-shot interest is a
-  watch trigger, not an open trigger. Either name the target use case
-  with project + timeline, or open a watch note and wait.
-
-## What to do when the gates fail
-
-1. Mark the domain plate `[-] gated — <gate name> not met` in the relevant
-   roadmap. Do **not** silently shrink scope to dodge the gate.
-2. Open a watch-only context note under `agents/settings/contexts/domain-watch/`
-   capturing what's missing — citations, owner candidates, CI feasibility.
-3. Re-evaluate at the next harvest cycle. The note is the evidence trail
-   so the same questions are not relitigated.
-
-## Allowed without gates
-
-- Adding **a single skill** to an **already-opened** domain follows the
-  regular harvest plate; the gates do not re-fire per skill.
-- Authoring a **guideline** that documents a domain the suite already
-  ships in — the domain is open, the guideline is a within-domain artefact.
-- A **rule** that constrains an already-opened domain — within-domain.
+Body migrated to [`guideline:agent-infra/domain-adoption-gates`](../docs/guidelines/agent-infra/domain-adoption-gates.md) (per P4 of `road-to-kernel-and-router.md`) — per-gate evidence bars (demand signal, named owner + cadence, CI-vs-reference-only), the sunset policy, the failure-mode catalog, the gates-fail procedure, and the allowed-without-gates list.
+Trigger-set above activates this routing on demand, independent of the discipline profile (ADR-110).
 
 ## See also
 
-- [`augment-edit-discipline`](augment-edit-discipline.md) —
-  `dist/agent-src/` must stay project-agnostic and cross-references must stay
-  in sync; domain plates inherit both floors
+- [`augment-edit-discipline`](augment-edit-discipline.md) — portability +
+  cross-reference floors domain plates inherit
 - [`size-enforcement`](size-enforcement.md) — size budgets apply per
   artefact regardless of domain
 - [`rule-type-governance`](rule-type-governance.md) — within-domain rules

package/dist/agent-src/rules/framework-neutrality-in-generic-skills.md

@@ -28,6 +28,8 @@ validator_ignore:
   - type: "substring"
     pattern: "scripts/lint_framework_leakage"
     reason: "Rule cites the enforcing linter script by name in body and enforcement section."
+routes_to:
+  - "guideline:agent-infra/framework-neutrality-patterns"
 workspaces: [agent-config-maintainer]
 packs: [meta]
 ---
@@ -49,11 +51,8 @@ into surfaces the agent must trigger on regardless of project stack.
 
 ## Scope
 
-This rule fires on edits under:
-
-- `.agent-src.uncondensed/skills/`
-- `.agent-src.uncondensed/rules/`
-- `.agent-src.uncondensed/commands/`
+This rule fires on edits under `src/skills/`, `src/rules/`, and
+`src/agent-src/commands/`.
 
 **Exempt** (file or directory name matches — these are correctly
 framework-specific): `laravel*`, `symfony*`, `nextjs*`, `react-*`,
@@ -63,63 +62,16 @@ framework-specific): `laravel*`, `symfony*`, `nextjs*`, `react-*`,
 `^terraform*`, `^terragrunt*`, `^traefik`, `^mobile-e2e`,
 `-routing$`, `project-analysis-(laravel|symfony|nextjs|react|node-express|zend-laminas)`.
 
-## Forbidden patterns in generic artifacts
-
-| Pattern | Why it leaks | Fix |
-|---|---|---|
-| `FormRequest` as a mandate | Laravel-only validation class | Say "request-validation primitive (FormRequest in Laravel, zod in Next.js, pydantic in FastAPI)" or move to `laravel-validation` carve-out |
-| `php artisan …` as a canonical command | Laravel CLI | Generalize to "the framework's CLI" or move to `artisan-commands` carve-out |
-| `PHPStan` as the only example | PHP-only static analyser | List peers (`mypy` for Python, `tsc` for TypeScript) or move to `quality-tools` carve-out |
-| `composer.json` mentioned alone | PHP package manifest | Add `package.json` / `pyproject.toml` peers, or move to a PHP-scoped carve-out |
-| `Eloquent` / `Model::…` | Laravel ORM | Generalize to "the project's ORM/data layer" or move to `eloquent` carve-out |
-| `Pest` as the only test runner | PHP/Laravel test framework | List peers (`pytest`, `vitest`, `jest`) or move to `pest-testing` carve-out |
-| `Blade` / `Livewire` / `Flux` as default UI | Laravel view stack | Generalize to "the project's UI layer" or move to `blade-ui` / `livewire` / `flux` carve-outs |
-| `vendor/bin/<tool>` as a canonical path | PHP/Composer-specific binary path | Say "the project's quality CLI" or carve-out it |
-| `Rector` as the only refactor tool | PHP-only refactorer | List peers (`ts-morph`, `libcst`) or carve-out it |
-| "every controller" / "all controllers" | Assumes MVC PHP framework | Generalize to "every request handler" / "every endpoint" |
-
-## Allowed: cross-stack documentation
-
-Multi-stack tables or detection maps with **at least two ecosystems
-side-by-side** are documentation, not leakage. The linter's
-auto-detect heuristic (Step 0.5 of the audit roadmap) skips a hit when
-its ±2-line window contains patterns from a different ecosystem family
-(`php_family` vs `js_family` vs `python_family`).
-
-Example (allowed):
-
-```
-- PHP/Composer project → `composer.json` present
-- Node project        → `package.json` present
-- Python project      → `pyproject.toml` present
-```
-
-## Allowed: carve-out pointers
-
-A generic artifact may end a section with a one-line handoff to its
-framework-specific peers. Canonical shape:
-
-```
-→ Laravel-specific: see [laravel-validation](../skills/laravel-validation/SKILL.md)
-→ Next.js-specific: see [nextjs-patterns](../skills/nextjs-patterns/SKILL.md)
-```
-
-The pointer is a link, not a procedure — the generic artifact never
-inlines stack-specific code.
-
-## Enforcement
-
-`scripts/lint_framework_leakage.ts` runs in the package CI pipeline.
-Exit codes:
+## The discipline in one breath
 
-- `0` — no hits, or every hit is auto-detected as cross-stack, or
-  every hit is allowlisted in
-  `scripts/lint_framework_leakage_allowlist.json` with a `reason`.
-- `1` — at least one hit in a generic artifact (non-carve-out) that
-  is neither cross-stack nor allowlisted.
+Framework names in a generic artifact appear only as **multi-stack peers**
+(≥ 2 ecosystems side-by-side — documentation, not leakage) or as a one-line
+**carve-out pointer** to the framework-specific artifact — never as the
+mandated procedure. `scripts/lint_framework_leakage.ts` is the deterministic
+CI backstop (exit 1 on a non-allowlisted hit in a generic artifact).
 
-The linter is intentionally noisy on first introduction — the audit
-roadmap drives hits to zero phase by phase.
+Body migrated to [`guideline:agent-infra/framework-neutrality-patterns`](../docs/guidelines/agent-infra/framework-neutrality-patterns.md) (per P4 of `road-to-kernel-and-router.md`) — the 10-row forbidden-pattern table with fixes, the cross-stack documentation allowance + auto-detect heuristic, the carve-out pointer shape, and the linter exit-code contract.
+Trigger-set above activates this routing on demand, independent of the discipline profile (ADR-110).
 
 ## See also
 

package/dist/agent-src/rules/improve-before-implement.md

@@ -38,10 +38,16 @@ Before implementing:
 - Tasks where the user said "just do it" or "skip validation"
 - Trivial changes (rename, typo, formatting)
 
+## Demand gate — should this exist? (build / defer)
+
+On a "build me an app / add this feature" ask, ONE reflexive pre-check before the three checks: **who asked · what breaks if unbuilt · what's the evidence?** Recommend **build** only at a real retention/activation blocker (evidence, not anxiety); else **defer/validate**, naming the missing evidence. Advisory — "just build it" proceeds immediately; no network lookup. Hierarchy + build/defer table: guideline § 8-pre.
+
 ## The three checks
 
 Run, in order: **1. Is the request clear?** · **2. Does it fit the existing architecture?** · **3. Is the approach sound?**
 
+Verification stays concrete — a `curl` probe against the endpoint, a Playwright spec, an `xdebug` step-through, or the project's test runner with a targeted filter — never a from-memory assertion (full section in the guideline below).
+
 Body migrated to [`guideline:agent-infra/agent-interaction-and-decision-quality` § 8](../docs/guidelines/agent-infra/agent-interaction-and-decision-quality.md#8-improve-before-implement--pre-implementation-validation) (per P4 of `road-to-kernel-and-router.md`) — the three checks' detail, how-to-challenge example, scope limits, verify-with-concrete-tools, RDP intent-inference.
 Trigger-set above activates this routing on demand, independent of the discipline profile (ADR-110).
 

package/dist/agent-src/rules/minimal-safe-diff.md

@@ -9,6 +9,8 @@ triggers:
   - keyword: "drive-by"
   - keyword: "rewrite"
   - keyword: "fix"
+routes_to:
+  - "guideline:agent-infra/minimal-safe-diff-mechanics"
 workspaces: [engineering]
 packs: [engineering-base]
 ---
@@ -47,21 +49,6 @@ Ask yourself, in order:
 3. **Is any of this a refactor?** If yes, it belongs in its own commit or
    PR, clearly labeled as a refactor, with no behavior change.
 
-## When the task seems to require a larger change
-
-- A rename, restructure, or framework upgrade that crosses the minimal-diff
-  line is a **separate, explicit** task — ask the user before expanding.
-- A bug fix that exposes a broader design problem stays a bug fix. Log the
-  design problem as a follow-up (ticket, note, TODO) and ship the fix alone.
-- A new feature that tempts you to "clean up" the module first: resist.
-  Add the feature, commit it, then propose the cleanup as a separate change.
-
-## Auto-formatter or linter rewrites unrelated code
-
-Revert those hunks before staging. The diff you present is the diff you own.
-If project policy forbids partial formatting, split into two commits:
-*format only* · *behavior change*.
-
 ## Red flags in your own diff — reject them
 
 Files the task never mentioned · import reordering, whitespace, or comments
@@ -74,37 +61,6 @@ task scope · dependency bumps "because it was close to the cache".
 Ask. A minimal diff plus one follow-up is cheaper than a sprawling diff the
 reviewer has to untangle.
 
-## Anti-over-engineering
-
-The smallest change is also the least *abstract* and least *speculative* one:
-
-- **Three similar lines beat a premature abstraction.** Do not extract a helper
-  / generic / config layer to dedupe two or three call sites — inline
-  repetition is cheaper to read and change than the wrong abstraction. Per new
-  abstraction: **cite the second caller — or inline it.**
-- **No speculative features.** Nothing beyond what was asked: no
-  configurability or "flexibility" nobody requested, no parameters with one
-  call site, no error handling for scenarios that cannot occur in this
-  codebase.
-- **The rewrite trigger.** If the change could be half the size without losing
-  behavior, rewrite before presenting. Self-check: *"Would a senior engineer
-  call this overcomplicated?"* — if yes, simplify.
-- **No tombstones.** Delete removed code completely — no `_oldName` renames,
-  no `// removed X` / `// no longer used` markers, no dead re-export shims kept
-  "for safety". Git history is the tombstone.
-- **No docstrings/comments on untouched code.** Do not annotate code the diff
-  does not change.
-
-Wrong/right pairs for each ban:
-[`simplicity-and-goal-demos`](../docs/guidelines/agent-infra/simplicity-and-goal-demos.md)
-— the demos are the recognition surface; match your diff against the *right*
-column before presenting.
-
-**Not adopted (council):** the source's "validate only at system boundaries /
-trust internal code" clause is **rejected** — internal code can be wrong, and
-"trust" is not a testing strategy. Keep validating internal invariants; this
-fold is about *diff shape*, not about dropping internal checks.
-
 ## Own-orphan cleanup
 
 Your diff cleans up exactly the mess it made — nothing more:
@@ -122,45 +78,9 @@ Your diff cleans up exactly the mess it made — nothing more:
   own-orphan (delete); otherwise → note. (`downstream-changes` runs the same
   sweep for renames — this is that sweep applied to the new diff.)
 
-## Break-glass exception
-
-This rule stays in force during production incidents. "Break-glass mode"
-narrows verification (see `verify-before-complete`) — it does **not**
-license drive-by edits.
-
-Allowed during break-glass:
-
-- The **smallest** change that stops the bleeding — one file, one
-  method, one guard — preferred over any refactor.
-- A fast revert to a known-good commit, even if it undoes unrelated
-  improvements shipped in the same PR.
-
-Not allowed, even in break-glass:
-
-- "While I'm in there" cleanups, reformatting, or dependency bumps.
-- Expanding the fix to neighboring modules without evidence they are
-  part of the incident.
-- Merging the hotfix with pending refactors from another branch.
-
-After the incident, open a **follow-up PR** for any scope that was
-intentionally deferred and reference the break-glass commit in its
-description.
-
-## Bounded remediation carve-out
+Body migrated to [`guideline:agent-infra/minimal-safe-diff-mechanics`](../docs/guidelines/agent-infra/minimal-safe-diff-mechanics.md) (per P4 of `road-to-kernel-and-router.md`) — larger-change guidance, auto-formatter hunk handling, anti-over-engineering criteria (premature abstraction, speculative features, rewrite trigger, no tombstones + the council's rejected trust-internal-code clause), break-glass exception, and the full bounded-remediation carve-out prose (five conditions summarized: same path/module, ≤ ~10 lines, no API change, no dependency/migration, verification in the same commit — everything outside is note + ask per `active-remediation`; a live cross-user/tenant exposure is the sole interrupt).
+Trigger-set above activates this routing on demand, independent of the discipline profile (ADR-110).
 
-The default stands: no drive-by edits, no opportunistic refactors. The one
-bounded exception — a **small, task-aligned security/correctness fix in code
-the current task already touches** — is governed by
-[`active-remediation`](active-remediation.md). It is permitted inline **only**
-when ALL hold: same request path / module, ≤ ~10 changed lines in one
-production file (plus its test file), no public-API / response-shape change, no dependency bump or migration,
-and its verification (e.g. the negative test) ships in the same commit.
-Anything outside those five conditions is **not** this carve-out — it is
-note + ask per `active-remediation`. This never licenses reformatting,
-renames, dependency bumps, or version upgrades (a syntax-idiom modernization
-is allowed only under `active-remediation`'s version-gated, behavior-preserving
-clause; a dependency/version bump stays ask-only). The sole case that may
-interrupt is a **live cross-user/tenant data exposure** ([`broken-access-control`](broken-access-control.md)) —
-fix-now-if-small, else stop and surface; never defer it silently.
+## See also
 
-See also: `scope-control` · `downstream-changes` · `think-before-action` · `preservation-guard` · `verify-before-complete` · [`active-remediation`](active-remediation.md) · [`broken-access-control`](broken-access-control.md).
+`scope-control` · `downstream-changes` · `think-before-action` · `preservation-guard` · `verify-before-complete` · [`active-remediation`](active-remediation.md) · [`broken-access-control`](broken-access-control.md).

package/dist/agent-src/rules/size-enforcement.md

@@ -25,6 +25,16 @@ packs: [meta]
 
 - If a component grows too large, mixes responsibilities, or becomes hard to scan → split or refactor.
 
+## Per-tool pitfall content
+
+Known-pitfall / troubleshooting content for a tool is a **`## Known pitfalls`
+section on that tool's existing skill** (format: `skill-writing` § Known-pitfalls
+section) — **never** a new skill per pitfall, and **never** a generated per-tool
+grid. A per-vendor pitfall generator (N slots × M tools) is exactly the
+skill-sprawl this rule exists to prevent; the topic taxonomy is a *checklist for
+authoring one good section*, not a template for many thin skills. Cap: **≤ 5
+real, sourced entries** per skill.
+
 - Prefer small files:
   - Rules and system instructions should stay well below 200 lines
   - Smaller (≈60 lines) is strongly preferred