@event4u/agent-config 1.19.0 → 1.21.0

package/.agent-src/rules/no-cheap-questions.md

@@ -8,12 +8,7 @@ source: package
 
 # No Cheap Questions
 
-A question is **cheap** when the answer follows from stated context,
-an option breaches an Iron Law, choices differ only in sequencing /
-format, or one option is obviously dominant. Mode-independent — holds
-in `off`, `auto`, and `on`; autonomy never lifts the no-trade-off
-floor (cf. [`autonomous-execution`](autonomous-execution.md), whose
-"trivial" failure modes only scope to `on` / opted-in `auto`).
+A question is **cheap** when context already answers, an option breaches an Iron Law, choices differ only in sequencing / format, or one option is dominant. Mode-independent — `off`, `auto`, `on`. Autonomy never lifts the floor.
 
 ## The Iron Laws
 
@@ -23,54 +18,43 @@ NEVER PRESENT AN OPTION THAT VIOLATES AN IRON LAW.
 NEVER OFFER NUMBERED CHOICES WITHOUT A REAL TRADE-OFF.
 ```
 
-Hold in `off`, `auto`, and `on`. Autonomy never lifts them.
-
 ## What counts as cheap
 
 - **Sequencing** — "Step 2 or 3 next?" when the roadmap orders them.
 - **Format-only** — "Table or paragraph?"; no semantic trade-off.
 - **Commit asks** — forbidden by [`commit-policy`](commit-policy.md).
 - **CI / test asks** — [`verify-before-complete`](verify-before-complete.md) decides, not the user.
-- **Fenced-step re-asks** — "Start Phase 1?" after *"plan only"*; see
-  [`scope-control § fenced step`](scope-control.md#fenced-step--user-set-review-gates).
-- **Iron-Law option** — breaches `commit-policy`, `scope-control` § git-ops, or `non-destructive-by-default`.
+- **Fenced-step re-asks** — "Start Phase 1?" after *"plan only"*; see [`scope-control § fenced step`](scope-control.md#fenced-step--user-set-review-gates).
+- **Iron-Law option** — breaches `commit-policy`, `scope-control § git-ops`, or `non-destructive-by-default`.
 - **Context-derived** — answer follows from prior turn / standing instruction / roadmap; act, state the assumption inline.
 - **Dominant option** — one choice obviously correct; alternatives carry no upside.
 - **Re-ask after decline** — forbidden per [`scope-control § decline = silence`](scope-control.md#decline--silence--no-re-asking-on-the-same-task).
 
-Examples per class:
-[`asking-and-brevity-examples`](../../docs/guidelines/agent-infra/asking-and-brevity-examples.md#cheap-question-class-catalog--extended-examples).
+Examples per class: [`asking-and-brevity-examples § cheap-question-catalog`](../docs/guidelines/agent-infra/asking-and-brevity-examples.md#cheap-question-class-catalog--extended-examples).
 
 ## Pre-Send Self-Check — MANDATORY before every question
 
 Run silently before any numbered-options block:
 
 1. Answer already in stated context?
-2. Any option violates `commit-policy`, `scope-control` § git-ops, or `non-destructive-by-default`?
+2. Any option violates `commit-policy`, `scope-control § git-ops`, or `non-destructive-by-default`?
 3. Options pure sequencing / format, no trade-off?
 4. One option obviously dominant?
-5. User fenced next step (*"plan only"*, *"review first"*) → deliver + handback per `scope-control` § fenced step.
-6. User already declined? Re-ask forbidden per `scope-control` § decline = silence.
+5. User fenced next step (*"plan only"*, *"review first"*) → deliver + handback per `scope-control § fenced step`.
+6. User already declined? Re-ask forbidden per `scope-control § decline = silence`.
 
-Any "yes" → **do not ask**. Pick the dominant path, state assumption
-inline (*"assuming X — adjust if wrong"*), hand back. One-question-per-turn
-from [`ask-when-uncertain`](ask-when-uncertain.md) still applies when
-the question is genuine.
+Any "yes" → **do not ask**. Pick the dominant path, state assumption inline (*"assuming X — adjust if wrong"*), hand back. One-question-per-turn from [`ask-when-uncertain`](ask-when-uncertain.md) still applies when the question is genuine.
 
 ## When asking IS allowed
 
 - Real architectural / scope decision with non-obvious trade-offs.
-- Vague-request trigger per [`ask-when-uncertain`](ask-when-uncertain.md#vague-request-triggers--must-ask).
+- Vague-request trigger per [`ask-when-uncertain § vague-triggers`](ask-when-uncertain.md#vague-request-triggers--must-ask).
 - Security-sensitive path per [`security-sensitive-stop`](security-sensitive-stop.md).
-- Hard Floor per `non-destructive-by-default` — confirmation mandatory.
+- Hard Floor per [`non-destructive-by-default`](non-destructive-by-default.md) — confirmation mandatory.
 - Two genuinely-equivalent paths; user preference is the tiebreaker.
 
 In doubt → ask. This rule narrows asking, never widens silence.
 
 ## Interactions
 
-- [`ask-when-uncertain`](ask-when-uncertain.md) — vague triggers + one-question-per-turn; narrows the cheap subset.
-- [`autonomous-execution`](autonomous-execution.md) — mode-scoped triviality there; mode-independent floor here.
-- [`commit-policy`](commit-policy.md) · [`scope-control`](scope-control.md) · [`non-destructive-by-default`](non-destructive-by-default.md) — Iron Laws this rule defends.
-- [`user-interaction`](user-interaction.md) — numbered-options shape; this rule decides whether to send.
-- [`direct-answers`](direct-answers.md) — brevity, no flattery.
+[`ask-when-uncertain`](ask-when-uncertain.md) · [`autonomous-execution`](autonomous-execution.md) · [`commit-policy`](commit-policy.md) · [`scope-control`](scope-control.md) · [`non-destructive-by-default`](non-destructive-by-default.md) · [`user-interaction`](user-interaction.md) · [`direct-answers`](direct-answers.md).

package/.agent-src/rules/no-council-references.md

@@ -0,0 +1,76 @@
+---
+type: "auto"
+tier: "mechanical-already"
+description: "Linking a specific file in agents/council-{questions,responses,sessions}/ from any artifact — council files are gitignored, local-only, auto-pruned; inline the convergence instead"
+alwaysApply: false
+source: package
+triggers:
+  - path_prefix: "agents/council-questions/"
+  - path_prefix: "agents/council-responses/"
+  - path_prefix: "agents/council-sessions/"
+  - intent: "link to council artefact"
+routes_to:
+  - "skill:ai-council"
+validator_ignore:
+  - type: "substring"
+    pattern: ".agent-src.uncompressed/"
+    reason: "Rule references the authoring tree when contrasting transient council files."
+---
+
+# No Council References from Any Artifact
+
+Council artefacts under `agents/council-{questions,responses,sessions}/`
+are **gitignored, local-only, and auto-pruned** after
+`ai_council.session_retention_days` (default 7). They are
+disposable scratch — never part of the repo, never visible to a
+reviewer who clones, never durable across the retention window.
+
+A link to a specific council file rots three ways: gitignored
+(not in cloned repo), pruned after retention window (gone even
+locally), and the installed `.augment/` projection cannot follow a
+path that does not exist in the consumer.
+
+## The Iron Law
+
+```
+NEVER LINK TO A SPECIFIC FILE INSIDE
+agents/council-{questions,responses,sessions}/
+FROM ANY ARTIFACT — ROADMAPS INCLUDED.
+INLINE THE CONVERGENCE WITH DATE + MEMBERS, NEVER THE PATH.
+```
+
+Applies to **every** artifact. Council artefacts are more transient
+than roadmaps — the local copy disappears too.
+
+## Forbidden vs allowed
+
+**Forbidden** in any `*.md` / `*.yml` / `*.json` / `*.py`:
+`agents/council-questions/<file>.md`,
+`agents/council-responses/<file>.json`,
+`agents/council-sessions/<file>.json` or `<timestamp>/...`.
+
+**Allowed**: directory mentions (talking about the output convention,
+not a specific file); the `ai-council` skill and `/council:*` commands
+documenting the output path schema; inline convergence summary —
+e.g. *"Council (claude-sonnet-4-5 + gpt-4o, 2026-05-06) converged
+on …"* with date + members, no filepath.
+
+## What to do instead
+
+Identify the durable conclusion (decision, contract, lesson),
+inline a convergence-summary block (members, date, cost if relevant
+— see `ai-council` § Output format), and optionally promote the
+lesson to `agents/contexts/`. The context is durable; the council
+file was the catalyst.
+
+Failure mode: *"I'll just link to the session JSON, it's evidence."*
+The session is gone in 7 days. **Inline first, link never.**
+
+## See also
+
+- [`no-roadmap-references`](no-roadmap-references.md) — sibling rule
+  for the roadmap layer
+- [`augment-source-of-truth`](augment-source-of-truth.md) — edit
+  `.agent-src.uncompressed/`
+- [`ai-council`](../skills/ai-council/SKILL.md) — output path
+  convention and convergence-summary format

package/.agent-src/rules/no-roadmap-references.md

@@ -4,6 +4,13 @@ tier: "mechanical-already"
 description: "Adding a link to a specific file in agents/roadmaps/ from any stable artifact (rule, skill, command, context, guideline) — roadmaps are transient; promote durable findings to agents/contexts/ instead"
 alwaysApply: false
 source: package
+triggers:
+  - path_prefix: "agents/roadmaps/"
+  - intent: "link from stable artifact"
+validator_ignore:
+  - type: "substring"
+    pattern: ".agent-src.uncompressed/"
+    reason: "Rule contrasts the authoring tree with transient roadmap files."
 ---
 
 # No Roadmap References from Stable Artifacts
@@ -45,7 +52,7 @@ CI enforcement: `scripts/check_no_roadmap_refs.py` (companion linter
 - `agents/roadmaps/` and its subdirectories as directory mentions
   (talking about the layer, not a specific file)
 - Roadmap → roadmap references (siblings within the transient layer)
-- Council sessions, `.agent-chat-history`, commit messages, PR
+- Council sessions, `agents/.agent-chat-history`, commit messages, PR
   descriptions — transient by construction, not part of the package
   surface
 

package/.agent-src/rules/non-destructive-by-default.md

@@ -5,16 +5,12 @@ description: "Agent is never destructive — Hard Floor always asks for prod-tru
 alwaysApply: true
 source: package
 load_context:
-  - .agent-src.uncompressed/contexts/authority/destructive-mechanics.md
+  - ../contexts/authority/destructive-mechanics.md
 ---
 
 # Non-Destructive by Default
 
-The agent is **never** destructive and **never** endangers user work
-or production systems. This is the universal safety floor — it applies
-in every mode, every conversation, every turn. Autonomy settings, "just
-keep going" directives, roadmap authorizations, and standing
-permissions narrow other rules; **none of them lift this one**.
+Universal safety floor. Applies in every mode, every conversation, every turn. Autonomy, "just keep going", roadmap authorizations, and standing permissions narrow other rules — **none lift this one**.
 
 ## The Iron Law
 
@@ -24,61 +20,35 @@ NO AUTONOMY SETTING, NO ROADMAP STEP, NO STANDING INSTRUCTION,
 NO "JUST KEEP GOING" CAN BYPASS IT.
 ```
 
-Triggers below require explicit user confirmation **on this turn** —
-not from a previous turn, not from a roadmap, not from a standing
-autonomy directive (see [`autonomous-execution`](autonomous-execution.md#opt-in-detection--match-by-intent-not-exact-string)
-for the anchor list of recognized phrases):
+Triggers below require explicit user confirmation **on this turn** — not from a previous turn, not from a roadmap, not from a standing autonomy directive (anchor list: [`autonomous-execution § opt-in detection`](autonomous-execution.md#opt-in-detection--match-by-intent-not-exact-string)):
 
 | Trigger | Examples |
 |---|---|
-| **Production-branch merge** | merging into `main`, `master`, `prod`, `production`, `release/*`, or any branch the project marks as deployment trunk |
+| **Production-branch merge** | `main`, `master`, `prod`, `production`, `release/*`, or any branch the project marks as deployment trunk |
 | **Deploy / release** | `terraform apply` on prod, `kubectl apply` on prod, deploy scripts, release commands, tag pushes that trigger CI deployment |
 | **Push to remote** | any `git push` (also covered by [`scope-control`](scope-control.md), restated so the floor never weakens) |
-| **Production data / infra** | prod DB writes or migrations, prod config, secrets rotation, IAM / role / policy, DNS, anything in a `prod`-scoped path or pipeline |
-| **Whimsical or unscoped bulk deletion** | `rm -rf <dir>`, `git rm -r`, glob deletions, `DROP TABLE`, `TRUNCATE`, `git reset --hard` past unpushed work — when the deletions are **not required by the current task**. Task-aligned bulk deletions are allowed during WIP — see below. |
-| **Commit containing bulk deletions or infra changes** | a commit whose diff removes a directory, deletes ≥5 unrelated files, or touches Terraform / Pulumi / k8s manifests / Ansible / cloud-config — surface the diff and confirm even when [`commit-policy`](commit-policy.md) otherwise authorizes the commit |
+| **Production data / infra** | prod DB writes / migrations, prod config, secrets rotation, IAM / role / policy, DNS, anything in a `prod`-scoped path or pipeline |
+| **Whimsical / unscoped bulk deletion** | `rm -rf <dir>`, `git rm -r`, glob deletions, `DROP TABLE`, `TRUNCATE`, `git reset --hard` past unpushed work — when **not required** by the current task. Task-aligned WIP deletions are allowed (below) |
+| **Commit containing bulk deletions or infra changes** | commit whose diff removes a directory, deletes ≥5 unrelated files, or touches Terraform / Pulumi / k8s manifests / Ansible / cloud-config — surface diff and confirm even when [`commit-policy`](commit-policy.md) otherwise authorizes |
 
-Standing "just keep going" + next step crosses the floor → STOP,
-surface what's about to happen (one numbered-options block per
-[`user-interaction`](user-interaction.md)), wait. Other rules still
-apply to every other step.
+Standing "just keep going" + next step crosses the floor → STOP, surface what's about to happen (one numbered-options block per [`user-interaction`](user-interaction.md)), wait. Other rules still apply to every other step.
 
 ## Not in scope — deterministic regeneration
 
-Output regenerated from a tracked source (compression, code-gen,
-formatter passes, lock-file rebuilds) is not destructive — the source
-of truth makes it reversible. Lives in
-[`autonomous-execution`](autonomous-execution.md#trivial--just-act-do-not-ask)
-§ Trivial, not here. Per-file diff approval is theater.
+Output regenerated from a tracked source (compression, code-gen, formatter passes, lock-file rebuilds) is reversible from source — **not destructive**. Lives in [`autonomous-execution § Trivial`](autonomous-execution.md#trivial--just-act-do-not-ask). Per-file diff approval is theater.
 
 ## Bulk deletions during WIP — allowed if task-connected
 
-Deletions inside an **active, user-stated task** are allowed in the
-working tree, **even multiple files or multiple folders** — the Hard
-Floor moves to the **commit** (row 6 above), not the in-progress edit.
-Whimsical / drive-by / unnamed-scope deletions still trip the floor on
-the edit. Full allowed/forbidden lists in
-[`destructive-mechanics`](../contexts/authority/destructive-mechanics.md)
-§ Bulk deletions during WIP.
+Deletions inside an **active, user-stated task** are allowed in the working tree, even multiple files / folders — the Hard Floor moves to the **commit** (row 6), not the in-progress edit. Whimsical / drive-by / unnamed-scope deletions still trip the floor on the edit. Allowed / forbidden lists: [`destructive-mechanics § Bulk deletions during WIP`](../contexts/authority/destructive-mechanics.md).
 
 ## Failure modes
 
-The full failure-mode catalog (autonomy-as-cover, roadmap-as-authorization,
-refusing-named-deletions, commit-without-diff-surface,
-roadmap-step-≠-commit-authorization) lives in
-[`destructive-mechanics`](../contexts/authority/destructive-mechanics.md)
-§ Failure modes. Reach for it when a Hard-Floor situation feels
-ambiguous; the rule itself stays focused on the trigger table.
+Full catalog (autonomy-as-cover, roadmap-as-authorization, refusing-named-deletions, commit-without-diff-surface, roadmap-step ≠ commit-authorization): [`destructive-mechanics § Failure modes`](../contexts/authority/destructive-mechanics.md).
 
 ## Cloud Behavior
 
-The Hard Floor applies on every surface, including Claude.ai Web,
-Skills API, and any cloud agent. There is no "cloud override" — the
-floor predates and outranks any platform-specific autonomy default.
+Floor applies on every surface — Claude.ai Web, Skills API, any cloud agent. No "cloud override".
 
 ## See also
 
-- [`autonomous-execution`](autonomous-execution.md) — defers to this rule for the floor; covers trivial-vs-blocking and opt-in detection only
-- [`commit-policy`](commit-policy.md) — four commit-exception paths; row 6 of the floor still applies on top of all four
-- [`scope-control`](scope-control.md) — git-ops permission gate; the floor is the never-overridable subset
-- [`user-interaction`](user-interaction.md) — numbered-options Iron Law for the confirmation prompt
+[`autonomous-execution`](autonomous-execution.md) · [`commit-policy`](commit-policy.md) · [`scope-control`](scope-control.md) · [`user-interaction`](user-interaction.md).

package/.agent-src/rules/onboarding-gate.md

@@ -2,126 +2,18 @@
 type: "auto"
 tier: "1"
 description: "First turn of a conversation on a project — check onboarding.onboarded in .agent-settings.yml; when false, prompt the user to run /onboard before executing any other request"
-alwaysApply: false
 source: package
+triggers:
+  - phrase: "first turn"
+  - keyword: "onboarding"
+  - path_prefix: ".agent-settings.yml"
+routes_to:
+  - "command:onboard"
 ---
 
 # Onboarding Gate
 
-> **Enforced by:** [`scripts/onboarding_gate_hook.py`](../../scripts/onboarding_gate_hook.py)
-> on Augment + Claude Code (`SessionStart`). The hook refreshes
-> `agents/state/onboarding-gate.json` from `.agent-settings.yml`; the
-> prose below is the spec the hook implements and the fallback for
-> platforms without a hook surface.
+**Iron Law.** First turn of a project: if `onboarding.onboarded` is false, prompt `/onboard` before executing any other request.
 
-Forces a one-time `/onboard` run for each developer on each project. This
-replaces the previously scattered "ask once" patterns across `user_name`,
-`personal.ide`, `personal.rtk_installed`, and cost profile confirmation.
-
-## When to activate
-
-Read `onboarding.onboarded` from `.agent-settings.yml` **once per
-conversation**, on the very first agent turn.
-
-- Key missing entirely → **legacy project**. Treat as onboarded, do
-  nothing. Do not write the key.
-- `true` → do nothing. Rule is inert for the rest of the conversation.
-- `false` → gate is active for this conversation (see below).
-
-Cache the result for the whole conversation. Do not re-read on every turn.
-
-## Gate behavior when `onboarded: false`
-
-On the **first** turn of the conversation, before executing the user's
-request, emit this prompt and stop:
-
-```
-> 👋 First-run setup hasn't been completed for this project.
->
-> Run /onboard once (≈2 minutes) to capture:
-> • your name, IDE, and rtk status
-> • cost profile + learning loop confirmation
->
-> 1. Run /onboard now
-> 2. Skip — mark as onboarded and continue with the request
-> 3. Snooze — continue just this turn; ask again next conversation
-```
-
-- `1` → invoke `/onboard`. Resume the user's original request afterwards.
-- `2` → set `onboarding.onboarded: true` in `.agent-settings.yml` (touch
-  only that field; preserve comments and order). Then execute the
-  original request.
-- `3` → proceed with the original request. Do not ask again in this
-  conversation. Do not write the file.
-
-Free-text replies (`"mach weiter"`, `"just do it"`) count as `3`.
-
-## Exceptions — do NOT block
-
-Skip the gate when the user's request already is an onboarding or
-settings operation, so we don't prompt users mid-setup:
-
-- `/onboard`, `/set-cost-profile`, `/mode`
-- The user explicitly asks about `.agent-settings.yml` or onboarding
-- Incident / break-glass signals (`hotfix`, `break-glass`, `"prod is
-  down"`). The gate waits for normal operations to resume.
-
-## Non-blocking for legacy projects
-
-If `.agent-settings.yml` exists but has no `onboarding` section at all,
-treat as onboarded. Only `onboarded: false` (explicit) triggers the
-gate. This protects projects that were set up before this rule shipped.
-
-## What this rule does NOT do
-
-- Write `onboarded: true` automatically. Only `/onboard` (step 6) and
-  the user's explicit `2` choice do that.
-- Re-prompt across turns in the same conversation. One prompt per
-  conversation, max.
-- Replace normal settings edits. Mid-life changes are ad-hoc (edit the
-  file directly or ask the agent, which follows
-  [`layered-settings`](../../docs/guidelines/agent-infra/layered-settings.md#section-aware-merge-rules));
-  this rule is a one-time gate.
-- Run on every agent turn. First turn only.
-
-## Interactions
-
-- `ask-when-uncertain` — the gate uses its numbered-options iron law;
-  one question per turn.
-- `language-and-tone` — prompt is translated to the user's language at
-  runtime; `.md` source stays English.
-- `scope-control` — option `2` writes exactly one key; no side effects.
-- `role-mode-adherence` — gate runs BEFORE the mode marker is emitted.
-
-## Copilot fallback
-
-GitHub Copilot has no `SessionStart` hook surface, so
-`scripts/onboarding_gate_hook.py` cannot run structurally and
-`agents/state/onboarding-gate.json` is not refreshed for the agent.
-On the first turn of a Copilot conversation:
-
-1. Read `onboarding.onboarded` from `.agent-settings.yml` directly
-   (one read per conversation, then cache as the prose above
-   describes).
-2. Optionally refresh the state file manually so other tooling sees
-   the same value the hook would have written:
-
-   ```bash
-   python3 scripts/onboarding_gate_hook.py < /dev/null
-   ```
-
-   The script reads `.agent-settings.yml`, atomically writes
-   `agents/state/onboarding-gate.json`, and exits 0 — same payload
-   the Augment / Claude / Cursor / Cline / Windsurf / Gemini hook
-   would have produced.
-3. Apply the gate behavior from "Gate behavior when `onboarded:
-   false`" above. The cooperative path is the spec; the hook is the
-   cache.
-
-## See also
-
-- [`/onboard`](../commands/onboard.md) — the command this gate invokes
-- [`layered-settings`](../../docs/guidelines/agent-infra/layered-settings.md) — merge rules for mid-life edits
-- [`agent-settings` template](../templates/agent-settings.md) — `onboarding.onboarded` reference
-- [`rule-type-governance`](rule-type-governance.md) — why this is `always`
-- [`hardening-pattern`](../../agents/contexts/hardening-pattern.md) — Tier 1 mechanical-rule contract
+Body migrated to `command:onboard` (per P4 of `road-to-kernel-and-router.md`).
+Trigger-set above activates this routing under the `balanced` and `full` profiles.

package/.agent-src/rules/package-ci-checks.md

@@ -1,46 +1,19 @@
 ---
 type: "auto"
 tier: "mechanical-already"
-alwaysApply: false
 description: "Before pushing to remote or creating a PR in the agent-config package — run all CI checks locally first"
 source: package
-load_context:
-  - .agent-src.uncompressed/contexts/communication/rules-auto/package-ci-checks-mechanics.md
+triggers:
+  - phrase: "task ci"
+  - phrase: "before push"
+  - phrase: "before pr"
+routes_to:
+  - "skill:lint-skills"
 ---
 
-# Package CI Checks
+# Package Ci Checks
 
-## When this applies
+**Iron Law.** Run `task ci` locally and confirm green before pushing or opening a PR in this package.
 
-Before **any** push to remote or PR creation in the **agent-config** package.
-This rule is specific to this package — it does NOT apply to consumer projects.
-
-## The Iron Law
-
-```
-NEVER push without running ALL CI checks locally first.
-```
-
-Every CI pipeline failure is preventable by running these checks before pushing.
-
-## Required checks — see mechanics
-
-Five checks must pass locally before push, in this order:
-
-1. **Sync** — `compress.sh --check` and `--check-hashes`.
-2. **Consistency** — `check_compression.py`, `check_references.py`, `check_portability.py`.
-3. **Linter** — `skill_linter.py --all`, 0 FAIL required.
-4. **Tests** — `pytest tests/`.
-5. **README** — `readme_linter.py`.
-
-The full command snippets, common-failure notes per step, the quick
-chained one-liner, and the post-edit workflow ("after editing
-skills/rules", "after editing `scripts/compress.py`") all live in
-[`contexts/communication/rules-auto/package-ci-checks-mechanics.md`](../contexts/communication/rules-auto/package-ci-checks-mechanics.md).
-Pull it whenever pre-push verification is needed.
-
-## Do NOT
-
-- Do NOT push "to see if CI passes" — that wastes pipeline minutes
-- Do NOT skip hash checks because "I only changed one file"
-- Do NOT assume tests pass because linter passes — they check different things
+Body migrated to `skill:lint-skills` (per P4 of `road-to-kernel-and-router.md`).
+Trigger-set above activates this routing under the `balanced` and `full` profiles.

package/.agent-src/rules/php-coding.md

@@ -2,63 +2,18 @@
 type: "auto"
 tier: "3"
 description: "Writing or reviewing PHP code — strict types, naming, comparisons, early returns, Eloquent conventions"
-alwaysApply: false
 source: package
+triggers:
+  - file_pattern: "*.php"
+  - keyword: "phpstan"
+  - keyword: "ecs"
+routes_to:
+  - "guideline:php/php-coding-patterns"
 ---
 
-# PHP Coding Rules
+# Php Coding
 
-- Use `declare(strict_types=1)` in every **new** PHP file. Not required when modifying existing files that don't have it.
-- If the project has a `Math` helper class, use it for ALL business calculations. Never use native PHP arithmetic operators (`+`, `-`, `*`, `/`) for business calculations. Search for the `Math` class in the project.
-- Never use `var_dump()`, `print_r()`, or `dd()` — they are disallowed by PHPStan config. Exception: legacy projects where these are already used and no alternative is feasible.
-- Never use `float` for money — use `decimal` or the `Math` helper.
-- Always use `===` / `!==` (strict comparison), Yoda style: `null === $var`.
-- Early return over nested if/else.
-- No one-liner if statements.
-- Single quotes for strings without interpolation. `sprintf()` for complex strings.
-- Variables: `camelCase`. Array keys: `snake_case`. Constants: `UPPER_SNAKE_CASE`.
-- Typed properties, parameters, and return types — always.
-- Constructor property promotion where it makes sense.
+**Iron Law.** PHP: strict types, named comparisons, early returns, Eloquent conventions — full pattern library in the guideline.
 
-## Eloquent Models — Attribute Access
-
-Read `eloquent.access_style` from `.agent-settings.yml` to determine the preferred style.
-Default: `getters_setters`. See the `eloquent` skill for the full reference table and examples.
-
-- **`getters_setters`** (strict): Every attribute has a typed getter + fluent setter. Inside the model: `getAttribute('column_name')`/`setAttribute('column_name', $value)`. Outside: always getters/setters. If a getter doesn't exist yet, create it first.
-- **`get_attribute`**: Use `getAttribute('column_name')`/`setAttribute('column_name', $value)` everywhere, no getters/setters needed.
-- **`magic_properties`**: Laravel default `$model->column_name` everywhere.
-
-### Relationship Getters
-
-- Every relationship MUST have a typed getter method **above** the relationship method.
-- **Inside the getter:** use `$this->getAttribute('relationship_name')`, NEVER `$this->relationship_name`.
-- **Outside the model:** ALWAYS use the getter (`$model->getEquipment()`), NEVER access the magic property (`$model->equipment`).
-- Use `instanceof` checks instead of `null ===` when checking relationship results.
-
-## Eloquent Models — Observers over `booted()`
-
-- Do NOT use `booted()` / `boot()` for model lifecycle hooks (saving, saved, deleted, etc.).
-- Use a dedicated **Observer** class registered via `#[ObservedBy]` attribute.
-- This keeps models slim and lifecycle logic testable and discoverable.
-
-## PHPStan
-
-- Always fix the root cause. Do NOT add entries to `phpstan-baseline.neon`.
-- Adding `ignoreErrors` to `phpstan.neon` is allowed for **structural toolchain limitations** (e.g., Pest runtime bindings). NOT for individual code issues. **If unsure → ask the user.**
-- If a fix is truly impossible (confirmed false positive), use an inline ignore as last resort:
-  ```php
-  // @phpstan-ignore-next-line — false positive: reason here
-  ```
-
-## Testing
-
-- Always write tests in **Pest**, not PHPUnit class syntax — unless the user explicitly asks for PHPUnit.
-- Pest tests in `tests/Unit/` automatically use `UnitTestCase` as the base class (configured in `tests/Pest.php`).
-
-## PHPDoc
-
-- Only add PHPDoc when type hints are insufficient (e.g. generic arrays: `@param array<int, MyObject> $items`).
-- Do NOT add PHPDoc that just repeats the method signature.
-- One docblock per method — never split into multiple `/** */` blocks.
-- Tag order: `@param` → `@return` → `@throws`.
+Body migrated to `guideline:php/php-coding-patterns` (per P4 of `road-to-kernel-and-router.md`).
+Trigger-set above activates this routing under the `balanced` and `full` profiles.

package/.agent-src/rules/preservation-guard.md

@@ -4,6 +4,15 @@ tier: "2b"
 alwaysApply: false
 description: "When merging, refactoring, compressing, or restructuring skills, rules, commands, or guidelines — prevent quality loss"
 source: package
+triggers:
+  - intent: "merge skill"
+  - intent: "compress rule"
+  - intent: "refactor artifact"
+  - keyword: "Iron Law"
+validator_ignore:
+  - type: "substring"
+    pattern: ".agent-src.uncompressed/"
+    reason: "Rule references the authoring tree as the operand of compression/preservation."
 ---
 
 # Preservation Guard