@event4u/agent-config 16.2.0 → 16.4.0

package/dist/agent-src/contexts/execution/toolchain-resolver.md

@@ -13,7 +13,16 @@ tools and run the right one — instead of a per-stack command explosion.
 > pytest / go / cargo, not N per-stack variants. "Only genuine PHP-space
 > commands stay PHP-locked."
 
-**Size budget:** ≤ 6,000 chars.
+**Size budget: none of its own.** The enforced ceiling is
+`check_depth_budget`'s 16,000 chars (`DEPTH_CEILING_CHARS`), and that is the
+only one. Do not add a page-local ceiling: one fitted to the file's current
+size breaks on the next edit and constrains nothing.
+
+What actually bounds this page is **what belongs in it**: the resolver's
+contract — the axes, the detection order, the confidence tiers, the refusal
+doctrine, the cache key. Narration, worked examples and per-round history
+belong in the roadmap and the review artifacts, not here. That rule is
+checkable by a reader; a character count was only ever checkable by `wc`.
 
 ## 1. The resolver
 
@@ -29,9 +38,25 @@ for (const r of result.selected) {
 }
 ```
 
-Resolution is filesystem-cheap (a handful of small manifest reads) and
-**never raises** — a malformed manifest or unknown stack degrades to a
-`LOW`-confidence empty result so the command can ask, never crash. This
+Resolution costs **per scope**, not per repository: a fixed name list stat-ed,
+six-or-so manifests read, and the .NET probe's directory listings — three at
+the root with no .NET target present, where the native axis lists once and the
+behavior axis twice. They run in every repository, .NET or not; WITH a root
+target the descent runs too and the count rises with the project tree. A wide workspace pays that times
+its package count, so the cost is proportional and not negligible.
+
+The **cache probe is the expensive path**, with the magnitude stated, not
+implied as a SHAPE, because the arithmetic has already been published wrong
+once: `latest_manifest_mtime` stats both fixed-name lists in every scope,
+bounded at 200 scopes (`_MAX_BEHAVIOR_SCOPES`), each hit paying a second stat — and without
+an explicit `scopes` it also expands the globs. The guard can cost more than
+the resolution it guards, so a caller holding the scope list passes it. The
+widening is still right: a root-only key cannot see a behavior runner
+arriving in a package, and a key invalidating too often is recoverable where
+one that never invalidates is not.
+
+Resolution **never raises** — a malformed manifest or unknown stack degrades
+to a `LOW`-confidence empty result so the command can ask, never crash. This
 mirrors the recoverable-error contract of the frontend `detect_stack`.
 
 ## 2. Detection order — per ecosystem, first match wins
@@ -47,6 +72,30 @@ mirrors the recoverable-error contract of the frontend `detect_stack`.
 | Python | `pytest` in pyproject / `pytest.ini` | pytest | `pytest` |
 | Go | `go.mod` present | go-test | `go test ./...` |
 | Rust | `Cargo.toml` present | cargo-test | `cargo test` |
+| Ruby | `rspec` gem in `Gemfile`/`gems.rb`, `.rspec`, `spec/spec_helper.rb` | rspec | `bundle exec rspec`, or bare `rspec` with no Gemfile |
+| JVM | `build.gradle[.kts]` / `settings.gradle[.kts]` by PRESENCE; `pom.xml` by CONTENT | junit | `./mvnw`/`./gradlew test`, else `mvn`/`gradle test` |
+| .NET | `*.sln[x]` or `*.csproj`/`*.fsproj`/`*.vbproj` **in the scope root** | dotnet-test | `dotnet test` |
+
+Each Ruby signal stands alone, and Ruby has **no MEDIUM default** (minitest is
+in the stdlib): no signal, no row. JVM defaults to `junit` at MEDIUM when the
+build file names no runner. A wrapper wins where one exists, since it pins the
+build-tool version.
+
+**.NET needs a target in the scope ROOT, because `dotnet test` is not
+recursive.** With no project or solution in the working directory it fails
+MSB1003, whatever sits below — so the row is gated on the root listing, and
+`global.json` / `Directory.Build.props` never produce one on their own. They
+are SDK pins, not targets, and confidence does not gate `selected`
+(`_apply_guard` has never read it), so a row emitted on one would be a
+command the repository cannot run.
+
+Given a root target: HIGH when a PROJECT file names a test stack
+(`Microsoft.NET.Test.Sdk`, xunit, nunit, mstest), MEDIUM otherwise. A root
+`.sln` IS a valid target even though its own body names no package, so the
+projects it references are read to decide the tier — which is the one case
+the scan descends for. A `src/<Name>/<Name>.csproj` layout with NO root
+solution therefore emits nothing: correct, because `dotnet test` from that
+root does not run either.
 
 **Task-runner wrappers win.** When the project root has a `Makefile`
 `test:` target, a `Taskfile.yml` `test:` task, or a `package.json`
@@ -57,6 +106,33 @@ container access, env, and parallelism (the architecture rule's
 The package manager is read from the lockfile (`pnpm-lock.yaml` → pnpm,
 `yarn.lock` → yarn, else npm).
 
+## 2b. Behavior-runner axis — per scope, detection only
+
+`result.behavior_runners` is a **separate list** from `runners`: it reports
+which behavior runner each scope already owns, across the same ecosystems.
+
+- **`command` is relative to `scope_root`, not to the project root.** It is
+  built from files inside the scope (`vendor/bin/behat`, `./gradlew test`), so
+  a consumer runs it WITH `scope_root` as the working directory. Every NATIVE
+  `runners` command is root-relative; this axis is the exception.
+- **Per scope, never repository-wide.** Each row carries `scope_root` (the
+  root plus every declared workspace package). A monorepo
+  returns a row per owning package and none for the others; one answer would
+  erase which package owns it.
+- **Two of the SAME ecosystem in one scope is a refusal, not a pick** —
+  `runner: "unknown"` plus `conflict: [both names]`, the same refusal the
+  frontend detector makes between two mutually exclusive workspaces. Two
+  DIFFERENT ecosystems are a polyglot repository, not a conflict: a PHP app
+  with a JS frontend returns two rows.
+- **Detection, never adoption.** No row recommends installing anything and the
+  axis is unreachable from `selected`, so nothing runs *because* this axis
+  reported it. That is reachability, not execution: for four of the eight
+  labels the behavior command equals a native command already in `selected`
+  (`pytest-bdd`/`pytest`, `cucumber-jvm`/`jvm.command`, `reqnroll` and
+  `specflow`/`dotnet test`), and those rows are `SPEED_FAST`, so the suite
+  runs anyway as part of the native run. The axis adds nothing to what
+  executes and removes nothing from it.
+
 ## 3. Confidence tiers — declarative, shared with the non-interactive contract
 
 Each runner carries a `confidence` (`HIGH` / `MEDIUM` / `LOW`) and a
@@ -71,6 +147,17 @@ tables:
   asking (interactive) or `ambiguous_routing` (CI, per the
   non-interactive contract).
 
+**`confidence` is about the RUNNER, never about `quality`.** The three
+ecosystems this change added — ruby, jvm, dotnet — contribute a runner and NO
+quality commands, because picking `rubocop`, a Spotless task or
+`dotnet format` is an adoption decision this resolver has no standing to make.
+The consequence is worth stating because it is silent: a Ruby-, JVM- or
+.NET-only repository used to resolve `LOW` with an empty `quality`, which is
+the tier that makes a command ASK; it now resolves `HIGH` with an empty
+`quality`, which a quality pass can read as nothing to do. An empty `quality`
+means **no quality tool was resolved**, never **no quality step is needed** —
+a command that finds one should ask rather than report success.
+
 ## 4. Monorepo guard — fast by default, opt-in for the rest
 
 `resolve_toolchain` returns the full `runners` inventory **and** a
@@ -91,9 +178,10 @@ e2e and slow stay out until their flag is passed.
 
 `write_config(root, result)` persists the resolved per-stack commands to
 `agents/runtime/state/toolchain.json` (best-effort; never raises). The
-config is keyed on the manifest `mtime`, so it is re-read cheaply and
-re-resolved only when a manifest changes — the same cache-invalidation
-hook the frontend detector uses.
+config is keyed on the latest `mtime` across every scope's manifests and
+markers — not the root's alone, or a behavior runner arriving in a workspace
+package would never invalidate it. Same hook the frontend detector uses,
+widened to the scopes the behavior axis reads.
 
 ## 6. What stays stack-locked
 

package/dist/agent-src/contexts/subagent-configuration.md

@@ -10,7 +10,7 @@ Loaded by the `subagent-orchestration` skill and the `/do-and-judge`,
 |---|---|---|
 | `subagents.implementer_model` | _(empty → session model)_ | Model alias used for implementer subagents |
 | `subagents.judge_model` | _(empty → one tier up)_ | Model alias used for judge subagents |
-| `subagents.max_parallel` | `3` | Hard cap on concurrent subagent invocations |
+| `subagents.max_parallel` | `3` | Limit on concurrent subagent invocations the model reads from settings — no code counts spawns against it |
 
 ## Model tier ladder
 

package/dist/agent-src/guidelines/agent-infra/active-remediation-mechanics.md

@@ -150,6 +150,45 @@ artifact exists because the issue is still owed, and "it failed one of six" is n
 something a later triage can act on. A deferral with no reason is the
 note-and-forget this rule already forbids, wearing an artifact's clothes.
 
+## fix-what-you-see — why a separate rule, and its activation gap
+
+Moved verbatim from [`fix-what-you-see`](../../rules/fix-what-you-see.md)
+on 2026-10-06 to pay for the standing-payload cost of `neighbour-precedence`;
+the rule keeps a pointer here.
+
+### Why separate from `active-remediation`
+
+That rule forbids ignoring a spotted issue and its ladder permits **note + ask**.
+Two properties made it insufficient, both measured 2026-08-20: it is `type: auto`
+on `refactor`/`legacy`/`cleanup` triggers — **none of which a failing CI job
+matches**, so it does not load when the obligation matters most — and its
+note-and-ask tier is what let a session name a red check's cause, name the
+file's author, and hand it back still red.
+
+Mechanics (fix-now size criteria, follow-up shape) stay there; this rule only
+deletes the two escapes.
+
+### Honest activation gap — this rule is `auto`, and it wanted to be `always`
+
+It shipped `auto` for a budget reason, not a design one, and the gap that leaves
+is exactly the one it was written to close: **a red check the agent sees in tool
+output triggers nothing.** Keyword triggers match the PROMPT. So the rule loads
+when a human says "CI is red" or "not my test", and does NOT load when a test
+run comes back red and nobody has said a word.
+
+`check_always_budget` is the reason: the extended always-budget sat at
+60,252 / 60,254 chars — **two characters of headroom** — and the cap is a
+ratchet that may only move down. The other nine always-rules are the kernel,
+which `block_kernel_rule_writes` denies agent writes to, so no room can be made
+from this side. A 2,332-char rule puts the total at 103.9 %.
+
+Closing the gap needs one of: the ext-cap ratchet opened deliberately (a
+maintainer decision, recorded), a kernel rule shortened to make room, or a
+`post_tool_use` carrier that notices a non-zero verification exit — the only
+option that would fire on tool output rather than on wording. Until then, `auto`
+plus this paragraph is the honest state: the obligation is real, its delivery is
+partial, and the partiality is named rather than implied away.
+
 ## See also
 
 - [`active-remediation`](../../rules/active-remediation.md) — the rule this file details (Iron Law + ladder + live-security carve-out).

package/dist/agent-src/guidelines/agent-infra/context-hygiene-mechanics.md

@@ -69,7 +69,7 @@ If you need an ignored skill: read its SKILL.md directly, apply guidance, then a
 GitHub Copilot has no `PostToolUse` hook surface, so
 `scripts/context_hygiene_hook.ts` cannot run structurally and
 `agents/state/context-hygiene.json` is not maintained automatically
-(tool-call count, loop signal, freshness milestones at 20/40/60).
+(tool-call count, 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

package/dist/agent-src/guidelines/agent-infra/cross-source-consistency-mechanics.md

@@ -37,19 +37,17 @@ from a ticket/spec that carries a second source:
 4. **Classify confidence.** High = the sources plainly disagree, or the missing
    behavior is clearly load-bearing. Low = the "conflict" is a plausible
    re-reading, or the missing behavior may be intentionally out of scope.
-5. **Decide per the setting** (below), then **batch** every surviving discrepancy
-   into ONE question folded into this turn's single `ask-when-uncertain` prompt.
+5. **Batch** every surviving discrepancy into ONE question folded into this
+   turn's single `ask-when-uncertain` prompt.
 
-## Confidence-tiered noise control (`consistency.cross_source`)
+## Noise control
 
 The rule fires only under a real trade-off (it must pass the
-`no-cheap-questions` Pre-Send Self-Check). The setting tunes how aggressively:
-
-| Value | High-confidence discrepancy | Low-confidence discrepancy |
-|---|---|---|
-| `on` (default) | Surface + ask before proceeding. | Surface + ask (batched into the same question). |
-| `auto` | Surface + ask. | State as an explicit assumption and proceed (no question). |
-| `off` | No cross-source checking — legacy behavior. | No cross-source checking. |
+`no-cheap-questions` Pre-Send Self-Check). Every real discrepancy, high- or
+low-confidence, is surfaced and asked — batched into the same question. That
+is the fixed behavior since the `consistency.cross_source` key (which offered
+`auto` and `off`) was retired on 2026-10-09 with this, its default, as the only
+mode.
 
 Batching is the anti-noise mechanism: N discrepancies for one artefact become
 one numbered-options block, never N prompts. Plain vagueness (a single unclear

package/dist/agent-src/guidelines/agent-infra/frontier-reasoning-operating-profile.md

@@ -141,8 +141,9 @@ is therefore **agent self-assessed**, never looked up (roadmap L10/L17):
 **One** constraint-light scaffold ships — no heavy/light content variants, since
 two variants would be a hidden model→band table. A standard host **expands it on
 request**. Two gates, both default-on: automatic (task signal + agent
-self-assessment) + the user `reasoning:` settings toggle (global + per-component
-+ hard off).
+self-assessment) + the user's `reasoning.enabled` hard off. The per-component
+toggles and `reasoning.auto_gate` were retired on 2026-10-09; the automatic gate
+decides per component.
 
 ## Notes template grounding
 

package/dist/agent-src/guidelines/agent-infra/layered-settings.md

@@ -18,7 +18,7 @@ on user request.
 | File | Git | Scope | Owner | Example values |
 |---|---|---|---|---|
 | `.agent-project-settings.yml` | **committed** | team / repo | lead maintainer | `project.stack`, `quality.php.tools`, `memory.dogfood` |
-| `~/.event4u/agent-config/agent-settings.yml` | **n/a** (outside repo) | individual developer · cross-project | individual | `name`, `ide`, `rule_loading_tier`, `personal.bot_icon`, `personal.autonomy`, `memory.cadence` (legacy `~/.config/agent-config/agent-settings.yml` read as fallback) |
+| `~/.event4u/agent-config/agent-settings.yml` | **n/a** (outside repo) | individual developer · cross-project | individual | `name`, `ide`, `rule_loading_tier`, `personal.autonomy` — the full whitelist is `MERGEABLE_KEYS` in `scripts/_lib/agent_settings.ts` (legacy `~/.config/agent-config/agent-settings.yml` read as fallback) |
 | `agents/settings/.agent-settings.yml` | **gitignored** | individual developer · this project | individual | `personal.ide`, `personal.user_name`, `subagents.max_parallel`, `onboarding.onboarded` | <!-- ref-ignore -->
 
 > **Canonical location (ADR-038):** the developer file lives in the settings
@@ -27,6 +27,12 @@ on user request.
 > `.agent-settings.yml` is read as a **back-compat fallback** and is migrated
 > into the canonical location by `install` on the next run.
 
+The `git.*` keys (`commit_format`, `branch_pattern`, `update_strategy`) have a
+fourth home a team uses instead: `.git-convention.yml` at the repository root,
+committed, read over every file above (ADR-283). `update_strategy` is read from
+it at the commit a pull request is judged against, the other two at `HEAD`.
+The team file carries no `git.*` key.
+
 All three are YAML. Schemas:
 
 - Developer (project-local): [`agent-settings.md`](../../templates/agent-settings.md).
@@ -45,6 +51,12 @@ Lowest priority → highest priority:
 4. agents/settings/.agent-settings.yml                (developer file, gitignored; legacy repo-root .agent-settings.yml read as fallback — ADR-038) <!-- ref-ignore -->
 ```
 
+For the `git.*` keys, `.git-convention.yml` sits above all four layers when it
+sets a key, and either value there is a declaration; a key it does not set
+falls through to this order, read at the repository root rather than per
+directory. `agent-config git:convention show` prints the value in force and a
+differing checkout value as a candidate.
+
 Keys from higher layers win unless a lower layer marks them
 `locked` (team file only). The user-global file does **not** support
 `locked` — its purpose is cross-project comfort, never policy.

package/dist/agent-src/guidelines/agent-infra/roadmap-progress-mechanics.md

@@ -224,7 +224,7 @@ Keep aligned with the dashboard counter in `scripts/update_roadmap_progress.ts`
 
 See [`guarded-baseline`](guarded-baseline.md).
 
-**Dashboard regen cadence — opt-in batching.** The checkbox flip is non-batchable. The **subprocess regen** (`./agent-config roadmap:progress`) is batchable per `roadmap.dashboard_regen_cadence` in `.agent-settings.yml` (`every_5_steps` default · `per_step` · `phase_boundary`). Run end, phase boundary, and any file-shape touch (rename / phase add / archive — Iron Law 1) always force an immediate regen regardless of cadence.
+**Dashboard regen cadence — fixed batching.** The checkbox flip is non-batchable. The **subprocess regen** (`./agent-config roadmap:progress`) batches to every 5th closed step — a fixed cadence since the `roadmap.dashboard_regen_cadence` key was retired on 2026-10-09 with that default as the behavior. Run end, phase boundary, and any file-shape touch (rename / phase add / archive — Iron Law 1) always force an immediate regen.
 
 **Blockers follow the same cadence as checkboxes.** Clearing a `## Blockers` entry (per `templates/roadmaps.md` rule 20) flips its `Status: resolved` and regenerates the dashboard in the same reply — Iron Law 1's "same response" obligation applies to blocker resolution exactly as it applies to a checkbox flip.
 

package/dist/agent-src/guidelines/agent-infra/self-improvement-pipeline.md

@@ -1,8 +1,11 @@
 # Self-Improvement Pipeline
 
 Five-stage flow that turns real project experience into reviewed
-rule / skill / command / guideline changes. No autonomous self-edits;
-every upstream change ships via a human-reviewed PR.
+rule / skill / command / guideline changes. Self-modification is a goal
+(ADR-281): for a proposal scoped to the package the approval is the AI
+council's ratification record, and the user is its last rung; a change a
+user asked for keeps that user's approval as now. A passing record makes a
+change ready, not landed — every upstream change still ships via a PR.
 
 Referenced by `road-to-curated-self-improvement.md`. Consumed by the live
 artifacts — the `skill-improvement-trigger` rule and the existing skills
@@ -84,7 +87,11 @@ blocks — it does not hand a half-filled doc to the next stage.
 
 ### Stage 5 — Upstream
 
-- **Trigger:** gate passed AND a human approver signed off.
+- **Trigger:** gate passed AND, for a proposal scoped to the package, a
+  council ratification record whose `subject` matches the proposal's change
+  passed it (ADR-281); where the council cannot conclude, the user decides by
+  the route ADR-281 § 5 names. A proposal scoped to a consumer's own project
+  needs that user's approval, as before.
 - **Executor:** `upstream-contribute` skill. Refuses invocation if
   the proposal frontmatter is not `stage: gated`.
 - **Input:** gated proposal doc.

package/dist/agent-src/guidelines/agent-infra/size-and-scope.md

@@ -221,6 +221,42 @@ Before creating or modifying:
 5. Is this entrypoint → AGENTS.md
 6. Is this behavior hint → copilot-instructions.md
 
+## Rich-class size band — moved from `token-budget-discipline`
+
+Moved verbatim from the rule on 2026-10-06 to pay for the standing-payload cost
+of `neighbour-precedence`; the rule keeps the band and a pointer here.
+
+### Candidate rich skills (justified, not exhaustive)
+
+These skills are approved `rich` by this roadmap's council:
+
+| Skill | Justification summary |
+|---|---|
+| `design-intelligence` | 11 corpus CSVs + 16 design-language prose specs + a 10-category checklist; grounded selection needs the full reference to avoid random corpus subsets |
+| `typography-system` | Modular-scale math + 6 worked example type systems; condensing to "use 1.25 ratio" produces agents that invent arbitrary px values |
+| `accessibility-auditor` | WCAG criteria are non-negotiable detail; every criterion has a testable condition + failure mode; compression loses the test procedures |
+| `design-system-capture` (Phase 6) | Writes + maintains DESIGN.md + PRODUCT.md; needs full templates + worked examples to generate useful artifacts |
+
+### The size band is measured, and only its ceiling is gated
+
+The `rich` band is **2,000–3,500 tokens** (ADR-217, `docs/decisions/ADR-217-rich-class-band-measured-and-enforced.md`).
+It was 2,000–5,000 and enforced by nothing until that record: measured with the
+exact BPE tokenizer, the largest rich artifact in the tree is 3,331 tokens, so
+the old ceiling described no artifact that existed. An unused permission costs
+nothing until someone uses it.
+
+`lint_token_budget_discipline.ts` gates the **ceiling** and publishes every rich
+artifact's size on the green path. It does **not** gate the floor, and that is a
+finding rather than an omission: running the check once surfaced a 1,931-token
+skill legitimately holding the class, because `rich` buys exemption from
+condensation — a claim about what compression would *lose*, not about file size.
+The published study supplies a degradation threshold, which is a ceiling.
+Nothing measures a minimum.
+
+Measurement is exact where `js-tiktoken` resolves and the character proxy where
+it does not; the gate says which, and a proxy reading within its own error
+margin of the ceiling is reported **unresolved** rather than classified.
+
 ---
 
 # Final principle

package/dist/agent-src/guidelines/php/git.md

@@ -34,6 +34,11 @@ hotfix/DEV-999/critical-payment-bug
 - Always include the Jira ticket ID when one exists
 - Use kebab-case for the description part
 - Keep branch names short but descriptive
+- The shape above is this guideline's convention; the agent renders branches from `git.branch_pattern` per [`commit-subject`](../../skills/git-workflow/references/commit-subject.md).
+- A team declares `git.branch_pattern`, `git.commit_format` and
+  `git.update_strategy` in `.git-convention.yml` at the repository root, committed
+  so every checkout, worktree and CI run reads the same value; there either value
+  is a declaration. `agent-config git:convention show` prints what is in force.
 
 ## Commit Messages
 
@@ -68,9 +73,14 @@ that is not better classified as `build`, `ci`, or `docs`.
 
 Use a scope when it adds clarity. Good scopes:
 
-- Jira ticket ID: `DEV-1234`
+- Jira ticket ID: placed per [`commit-subject`](../../skills/git-workflow/references/commit-subject.md) § Placing the ticket
 - Module/area: `api`, `auth`, `skills`, `rules`, `ci`, `frontend`, `linter`
 
+Under `git.commit_format: ticket-conventional` the ticket leads the subject and is
+**never** in the scope (`DEV-1234 feat(exporter-models): …`); tooling that parses
+subjects (commitlint, release automation, changelog generators) must be
+configured for that prefixed form.
+
 Do not add a scope if it adds no value. `fix(core): fix typo` → just `fix: fix typo`.
 
 ### Description rules
@@ -157,7 +167,10 @@ Before writing the commit message:
 
 ## Pull Requests
 
-- PR title follows commit message format: `feat(DEV-1234): short description`
+- PR title per [`commit-subject`](../../skills/git-workflow/references/commit-subject.md) § A title that becomes a commit
+- Bring the branch up to date per `git.update_strategy` — merge the base in
+  (default) or rebase onto `origin/main` and push with `--force-with-lease`;
+  see `git-workflow` › `references/branch-update.md`
 - Fill in the PR template (checklist, description, testing notes)
 - Link the Jira ticket in the PR description
 - Ensure all quality gates pass before requesting review

package/dist/agent-src/rules/active-remediation.md

@@ -20,7 +20,6 @@ enforced_by:
   - "instruction-only: the note, the ask and the user decision are all prose, so no gate can tell a discharged issue from a mentioned one"
 collision_ok:
   "refactor": "an explicit clean-up/refactor ask is the remediation ladder's own trigger"
-# obligation: line 31
 obligation_frequency: "per-edit"
 ---
 
@@ -103,7 +102,7 @@ The note, the ask and the user's decision are all prose, and the issue set is
 whatever the agent happened to see, so no gate can tell a discharged issue from a
 mentioned one. This rule ships `instruction-only` — the honesty boundary
 [`security-sensitive-stop`](security-sensitive-stop.md) and
-[`ui-audit-gate`](ui-audit-gate.md) state for their own obligations. The ladder
+`ui-audit-gate` state for their own obligations. The ladder
 is the control; skipping it is caught by nothing.
 
 Body migrated to [`guideline:agent-infra/active-remediation-mechanics`](../guidelines/agent-infra/active-remediation-mechanics.md) (per P4 of `road-to-kernel-and-router.md`) — per-tier fix-now/note+ask/follow-up-PR criteria, version-gated modernization, anti-nagging guardrails.

package/dist/agent-src/rules/analysis-skill-routing.md

@@ -10,7 +10,6 @@ routes_to:
   - "skill:analysis-skill-router"
 workspaces: [agent-config-maintainer, engineering]
 packs: [meta]
-# obligation: line 19
 obligation_frequency: "none"
 ---
 

package/dist/agent-src/rules/architecture.md

@@ -13,7 +13,6 @@ workspaces: [agent-config-maintainer, engineering]
 packs: [meta]
 collision_ok:
   "controller": "thin-handler floor on controller work"
-# obligation: line 26
 obligation_frequency: "per-edit"
 ---
 

package/dist/agent-src/rules/artifact-drafting-protocol.md

@@ -14,7 +14,6 @@ routes_to:
   - "guideline:agent-infra/artifact-drafting-protocol-mechanics"
 workspaces: [agent-config-maintainer, engineering]
 packs: [meta]
-# obligation: line 41
 obligation_frequency: "per-task"
 ---
 

package/dist/agent-src/rules/artifact-engagement-recording.md

@@ -13,7 +13,6 @@ load_context:
   - "../contexts/contracts/artifact-engagement-flow.md"
 workspaces: [agent-config-maintainer, engineering]
 packs: [meta]
-# obligation: line 22
 obligation_frequency: "per-task"
 ---
 

package/dist/agent-src/rules/augment-edit-discipline.md

@@ -19,7 +19,6 @@ workspaces: [agent-config-maintainer]
 packs: [meta]
 collision_ok:
   ".augment/": "portability + sync floors for the .augment tree"
-# obligation: line 28
 obligation_frequency: "per-edit"
 ---
 

package/dist/agent-src/rules/autonomous-execution.md

@@ -1,6 +1,7 @@
 ---
 type: "auto"
 tier: "3"
+consequence_class: "authority-bypass"
 description: "Ask-or-act on a workflow step — trivial-vs-blocking, autonomy opt-in, commit default; Hard Floor stays"
 alwaysApply: false
 load_context:
@@ -13,7 +14,6 @@ triggers:
 self_contained: true
 workspaces: [agent-config-maintainer, construction, engineering, finance, founder, gtm, legal-review-prep, ops, product, small-business]
 packs: [meta]
-# obligation: line 4
 obligation_frequency: "per-turn"
 ---
 

package/dist/agent-src/rules/brand-consistency.md

@@ -10,7 +10,6 @@ applies_to_user_types:
 self_contained: true
 workspaces: [engineering]
 packs: [brand]
-# obligation: line 20
 obligation_frequency: "none"
 ---
 

package/dist/agent-src/rules/brand-source-of-truth.md

@@ -20,7 +20,6 @@ applies_to_user_types:
 self_contained: true
 workspaces: [engineering]
 packs: [brand]
-# obligation: line 51
 obligation_frequency: "per-edit"
 ---
 

package/dist/agent-src/rules/broken-access-control.md

@@ -2,6 +2,7 @@
 type: "auto"
 tier: "2a"
 alwaysApply: false
+consequence_class: "security-boundary"
 description: "Endpoint/query on user/tenant data — authenticated ≠ authorized: server-derived ownership/tenant/role + negative tests (401/non-owner/cross-tenant)"
 triggers:
   - keyword: "endpoint"
@@ -23,7 +24,6 @@ collision_ok:
   "controller": "controllers return user data — the ownership/tenant check floor"
   "endpoint": "every data-returning endpoint needs the three negative tests"
   "tenant": "cross-tenant isolation is this rule's core subject"
-# obligation: line 55
 obligation_frequency: "per-edit"
 evidence:
   source_type: external-standard

package/dist/agent-src/rules/cli-output-handling.md

@@ -35,7 +35,6 @@ collision_ok:
   "composer": "composer output is verbose — rtk wrap applies"
   "docker": "docker output is verbose — rtk wrap applies"
   "rector": "rector output is verbose — rtk wrap applies"
-# obligation: line 42
 obligation_frequency: "per-edit"
 ---
 

package/dist/agent-src/rules/code-comment-discipline.md

@@ -20,7 +20,6 @@ packs: [engineering-base]
 collision_ok:
   "refactor": "refactors churn comments — the keep/drop discipline applies"
   "implement": "fresh implementation is where over-commenting lands"
-# obligation: line 5
 obligation_frequency: "per-edit"
 enforced_by:
   - "validator:src/scripts/lint_code_comments.ts"

package/dist/agent-src/rules/code-provenance.md

@@ -23,7 +23,6 @@ packs: [engineering-base]
 roles: [developer, reviewer, tester, po, incident, planner]
 enforced_by:
   - "instruction-only: close-the-source-and-re-derive is a pre-write reasoning step only the model observes; CI checks the ledger, never the derivation"
-# obligation: line 40
 obligation_frequency: "per-edit"
 evidence:
   source_type: external-research

package/dist/agent-src/rules/command-suggestion-policy.md

@@ -1,6 +1,7 @@
 ---
 type: "auto"
 tier: "mechanical-already"
+consequence_class: "authority-bypass"
 description: "Prompt matches an eligible slash command — surface as numbered options with as-is escape; never auto-execute"
 triggers:
   - phrase: "free-form prompt"
@@ -11,7 +12,6 @@ load_context:
   - "../contexts/contracts/command-suggestion-flow.md"
 workspaces: [agent-config-maintainer, construction, engineering, finance, founder, gtm, legal-review-prep, ops, product, small-business]
 packs: [meta]
-# obligation: line 18
 obligation_frequency: "per-turn"
 ---
 

package/dist/agent-src/rules/commit-conventions.md

@@ -12,13 +12,12 @@ workspaces: [engineering]
 packs: [engineering-base]
 collision_ok:
   "commit": "format floor for every commit message"
-# obligation: line 19
 obligation_frequency: "per-commit"
 ---
 
 # Commit Conventions
 
-**Iron Law.** Match the repo's configured or approved convention; else Conventional Commits (`feat:`, `fix:` …), branches `<type>/<short-slug>`; never invent one. Subjects + branch names stay emoji-free per [`no-decorative-emojis-in-git-surfaces`](no-decorative-emojis-in-git-surfaces.md); body emojis need an in-artifact legend.
+**Iron Law.** Match a repo's configured, then git.* settings, then approved convention; else Conventional Commits, branches `<type>/<short-slug>`; never invent one. Subjects + branch names stay emoji-free per [`no-decorative-emojis-in-git-surfaces`](no-decorative-emojis-in-git-surfaces.md); body emojis need an in-artifact legend.
 
 Body migrated to `skill:conventional-commits-writing` (per P4 of `road-to-kernel-and-router.md`).
 Trigger-set above activates this routing on demand, independent of the discipline profile (ADR-110).

package/dist/agent-src/rules/communication-through-line.md

@@ -8,7 +8,6 @@ workspaces: [agent-config-maintainer, construction, engineering, finance, founde
 packs: [meta]
 triggers:
   - phrase: "reporting progress"
-# obligation: line 20
 obligation_frequency: "per-turn"
 ---
 
@@ -34,7 +33,7 @@ CLOSE THE LOOP WITH ONE END-SUMMARY. NEVER MAKE THE USER RE-DERIVE WHERE THINGS
 ## When NOT to over-apply
 
 - A one-shot answer or trivial reply needs no plan-anchor or end-summary (`direct-answers` brevity wins).
-- Don't narrate for its own sake — the thread is orientation, not play-by-play (respect `personal.play_by_play`).
+- Don't narrate for its own sake — the thread is orientation, not play-by-play.
 - Never let the through-line inflate a reply past what the task needs; brevity and the one-recommendation rule win on conflict.
 
 ## See also

package/dist/agent-src/rules/content-quoting-floor.md

@@ -9,7 +9,6 @@ triggers:
 self_contained: true
 workspaces: [agent-config-maintainer, construction, engineering, finance, founder, gtm, legal-review-prep, ops, product, small-business]
 packs: [meta]
-# obligation: line 19
 obligation_frequency: "per-event"
 ---
 
@@ -88,7 +87,7 @@ does not substitute for engaging with the source.
   **markup**: a design artifact the user hands over is their own material, so
   adapting its code is not a borrow. Third-party code arriving inside that
   handover is not covered, on either side.
-- [`docs/contracts/write-engine.md`](../docs/contracts/write-engine.md) —
+- `docs/contracts/write-engine.md` —
   ghostwriter's disclosure-footer contract; this rule's quote floor
   applies to any ghostwriter draft that cites an external source.
 - [`source-confidentiality`](source-confidentiality.md) — the license-