@event4u/agent-config 7.5.0 → 8.0.0

package/docs/contracts/governance-enforcement-projection.md

@@ -1,3 +1,8 @@
+---
+stability: beta
+keep-beta-until: 2026-08-17
+---
+
 # Governance Enforcement at Projection Time — design spec
 
 > **Status: Measured → honest-null (2026-06-25). NOT shipped.** The length-controlled

package/docs/contracts/gui-wizard.md

@@ -64,7 +64,7 @@ Finish drives the **whole** install through `POST /api/v1/wizard/apply` →
 without `DISPLAY`), or a CLI-mode flag (`--no-ui` / `--tools` / `--ai` /
 `--yes` / `--quiet` / `--dry-run` / `--minimal` / `--settings-only` /
 `--list-tools`). `install.py`'s own tail-launch (`_wizard_spawn`, matching the
-`WIZARD_READY <url>` handshake) remains for direct `python3 install.py` runs.
+`WIZARD_READY <url>` handshake) remains for direct CLI install runs.
 
 ### `WIZARD_READY` stdout contract
 

package/docs/contracts/hook-architecture-v1.md

@@ -25,12 +25,12 @@ Last refreshed: 2026-05-04.
 | **Concern** | A single agent-config behaviour wired to one or more lifecycle events — e.g. `chat-history`, `roadmap-progress`, `verify-before-complete`. Lives as a Python script under `scripts/hooks/concerns/<name>.py`. |
 | **Event** | The agent-config-internal event vocabulary the dispatcher exposes — `session_start`, `session_end`, `user_prompt_submit`, `pre_tool_use`, `post_tool_use`, `stop`, `pre_compact`, `agent_error`. Per-platform native names map to these. `agent_error` is synthetic — fired by the agent (or wrapper) when the host crashes outside a concern, so chat-history can checkpoint partial sessions on abnormal exit. (Added in Round 2 — 2026-05-04.) |
 | **Trampoline** | A 5–10 line per-platform shell script that reads the platform's native payload, calls the dispatcher with `--platform <name>`, and forwards the platform's exit-code semantics. |
-| **Dispatcher** | `scripts/hooks/dispatch_hook.py` — single Python entrypoint that reads the manifest, resolves which concerns fire on `(platform, event)`, runs each one with the contract envelope below, and reduces their exit codes. |
+| **Dispatcher** | `src/scripts/hooks/dispatch_hook.ts` — single Python entrypoint that reads the manifest, resolves which concerns fire on `(platform, event)`, runs each one with the contract envelope below, and reduces their exit codes. |
 
 ## Dispatcher invocation
 
 ```
-python3 scripts/hooks/dispatch_hook.py \
+./scripts-run src/scripts/hooks/dispatch_hook \
     --platform <name> \
     --event <agent-config-event> \
     [--native-event <platform-event>] \

package/docs/contracts/implement-ticket-flow.md

@@ -101,7 +101,7 @@ A v0 file (no `version` key, ticket under flat `ticket`) is
 upgraded by `work_engine.migration.v0_to_v1`:
 
 ```bash
-python3 -m work_engine.migration.v0_to_v1 .implement-ticket-state.json
+node agent-config-templates/scripts/work_engine/migration/v0_to_v1.js .implement-ticket-state.json
 ```
 
 The migration:

package/docs/contracts/kernel-membership.md

@@ -100,6 +100,19 @@ demote largest projected, re-sum; abort after 3 rounds.
 under median projection. Headroom = 1929 chars (= ~one median rule)
 absorbs pilot variance for the 6 untested rules.
 
+**2026-07-06 demotion (council: claude-sonnet-4-5 + gpt-4o, 2-round
+debate).** `user-interrupt-priority` had been added as an 11th-hour
+`type: always` rule without a membership amendment, pushing the live
+always set to 10 and the Augment workspace-guidelines budget past its
+empirical cap. Demoted back to `type: auto` (trigger-loaded); its
+one-line interrupt essence lives in `agent-authority § Rules` so the
+always-loaded surface keeps the STOP → run → ASK contract visible.
+The locked kernel remains the 9 rules below. In the same pass the 9
+rules' post-P2.2 prose growth was telegraph-trimmed back under the
+26k bucket (Iron-Law fences byte-stable; load-bearing additions —
+direct-answers' live-state clause, verify-before-complete's mechanics
+pointer — retained per council verdict).
+
 ## § 4 — Locked kernel set
 
 | id | current | projected (× 0.712) | inclusion criterion |

package/docs/contracts/mcp-tool-inventory.md

@@ -5,10 +5,10 @@ keep-beta-until: 2026-08-14
 
 # MCP tool inventory
 
-> Generated by [`scripts/audit_mcp_tools.py`](../../scripts/audit_mcp_tools.py)
+> Generated by [`src/scripts/audit_mcp_tools.ts`](../../src/scripts/audit_mcp_tools.ts)
 > from the source-of-truth catalog
-> [`scripts/mcp_server/consumer_tool_catalog.json`](../../scripts/mcp_server/consumer_tool_catalog.json).
-> Do **not** hand-edit; rerun `python3 scripts/audit_mcp_tools.py --write`.
+> [`src/scripts/mcp_server/consumer_tool_catalog.json`](../../src/scripts/mcp_server/consumer_tool_catalog.json).
+> Do **not** hand-edit; rerun `./scripts-run src/scripts/audit_mcp_tools --write`.
 >
 > Step-11 Phase 5 Step 3 (an internal parity roadmap (local-only)).
 
@@ -23,26 +23,26 @@ keep-beta-until: 2026-08-14
 
 | Tool | Side-effect | Transports | Catalog | Handler |
 |---|---|---|---|---|
-| `lint_skills` | `ro` | stdio | [`consumer_tool_catalog.json:7`](../../scripts/mcp_server/consumer_tool_catalog.json#L7) | [`tools.py:509`](../../scripts/mcp_server/tools.py#L509) |
-| `chat_history_append` | `fs-write` | stdio | [`consumer_tool_catalog.json:24`](../../scripts/mcp_server/consumer_tool_catalog.json#L24) | [`tools.py:539`](../../scripts/mcp_server/tools.py#L539) |
-| `chat_history_read` | `ro` | stdio | [`consumer_tool_catalog.json:43`](../../scripts/mcp_server/consumer_tool_catalog.json#L43) | [`tools.py:606`](../../scripts/mcp_server/tools.py#L606) |
-| `memory_lookup` | `ro` | stdio | [`consumer_tool_catalog.json:59`](../../scripts/mcp_server/consumer_tool_catalog.json#L59) | [`tools.py:654`](../../scripts/mcp_server/tools.py#L654) |
-| `memory_signal` | `fs-write` | _(stub)_ | [`consumer_tool_catalog.json:75`](../../scripts/mcp_server/consumer_tool_catalog.json#L75) | _stub-only_ |
-| `memory_status` | `ro` | stdio | [`consumer_tool_catalog.json:91`](../../scripts/mcp_server/consumer_tool_catalog.json#L91) | [`tools.py:701`](../../scripts/mcp_server/tools.py#L701) |
-| `skill_trigger_eval` | `ro` | _(stub)_ | [`consumer_tool_catalog.json:98`](../../scripts/mcp_server/consumer_tool_catalog.json#L98) | _stub-only_ |
-| `suggest_command` | `ro` | _(stub)_ | [`consumer_tool_catalog.json:114`](../../scripts/mcp_server/consumer_tool_catalog.json#L114) | _stub-only_ |
-| `suggest_skill_for_task` | `ro` | _(stub)_ | [`consumer_tool_catalog.json:129`](../../scripts/mcp_server/consumer_tool_catalog.json#L129) | _stub-only_ |
-| `mine_session` | `ro` | _(stub)_ | [`consumer_tool_catalog.json:144`](../../scripts/mcp_server/consumer_tool_catalog.json#L144) | _stub-only_ |
-| `update_form_request_messages` | `fs-write` | _(stub)_ | [`consumer_tool_catalog.json:158`](../../scripts/mcp_server/consumer_tool_catalog.json#L158) | _stub-only_ |
-| `sync_gitignore` | `fs-write` | _(stub)_ | [`consumer_tool_catalog.json:173`](../../scripts/mcp_server/consumer_tool_catalog.json#L173) | _stub-only_ |
-| `sync_agent_settings` | `fs-write` | _(stub)_ | [`consumer_tool_catalog.json:186`](../../scripts/mcp_server/consumer_tool_catalog.json#L186) | _stub-only_ |
-| `run_tests` | `shell` | _(stub)_ | [`consumer_tool_catalog.json:200`](../../scripts/mcp_server/consumer_tool_catalog.json#L200) | _stub-only_ |
-| `run_quality_checks` | `shell` | _(stub)_ | [`consumer_tool_catalog.json:214`](../../scripts/mcp_server/consumer_tool_catalog.json#L214) | _stub-only_ |
-| `list_skills` | `ro` | stdio | [`consumer_tool_catalog.json:227`](../../scripts/mcp_server/consumer_tool_catalog.json#L227) | [`tools.py:716`](../../scripts/mcp_server/tools.py#L716) |
-| `list_commands` | `ro` | stdio | [`consumer_tool_catalog.json:234`](../../scripts/mcp_server/consumer_tool_catalog.json#L234) | [`tools.py:732`](../../scripts/mcp_server/tools.py#L732) |
-| `list_rules` | `ro` | stdio | [`consumer_tool_catalog.json:241`](../../scripts/mcp_server/consumer_tool_catalog.json#L241) | [`tools.py:748`](../../scripts/mcp_server/tools.py#L748) |
-| `compile_router` | `shell` | _(stub)_ | [`consumer_tool_catalog.json:248`](../../scripts/mcp_server/consumer_tool_catalog.json#L248) | _stub-only_ |
-| `read_resource_body` | `ro` | stdio | [`consumer_tool_catalog.json:261`](../../scripts/mcp_server/consumer_tool_catalog.json#L261) | [`tools.py:765`](../../scripts/mcp_server/tools.py#L765) |
+| `lint_skills` | `ro` | stdio | [`consumer_tool_catalog.json:7`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L7) | [`tools.ts:575`](../../src/scripts/mcp_server/tools.ts#L575) |
+| `chat_history_append` | `fs-write` | stdio | [`consumer_tool_catalog.json:24`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L24) | [`tools.ts:603`](../../src/scripts/mcp_server/tools.ts#L603) |
+| `chat_history_read` | `ro` | stdio | [`consumer_tool_catalog.json:43`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L43) | [`tools.ts:664`](../../src/scripts/mcp_server/tools.ts#L664) |
+| `memory_lookup` | `ro` | stdio | [`consumer_tool_catalog.json:59`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L59) | [`tools.ts:706`](../../src/scripts/mcp_server/tools.ts#L706) |
+| `memory_signal` | `fs-write` | _(stub)_ | [`consumer_tool_catalog.json:75`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L75) | _stub-only_ |
+| `memory_status` | `ro` | stdio | [`consumer_tool_catalog.json:91`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L91) | [`tools.ts:748`](../../src/scripts/mcp_server/tools.ts#L748) |
+| `skill_trigger_eval` | `ro` | _(stub)_ | [`consumer_tool_catalog.json:98`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L98) | _stub-only_ |
+| `suggest_command` | `ro` | _(stub)_ | [`consumer_tool_catalog.json:114`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L114) | _stub-only_ |
+| `suggest_skill_for_task` | `ro` | _(stub)_ | [`consumer_tool_catalog.json:129`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L129) | _stub-only_ |
+| `mine_session` | `ro` | _(stub)_ | [`consumer_tool_catalog.json:144`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L144) | _stub-only_ |
+| `update_form_request_messages` | `fs-write` | _(stub)_ | [`consumer_tool_catalog.json:158`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L158) | _stub-only_ |
+| `sync_gitignore` | `fs-write` | _(stub)_ | [`consumer_tool_catalog.json:173`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L173) | _stub-only_ |
+| `sync_agent_settings` | `fs-write` | _(stub)_ | [`consumer_tool_catalog.json:186`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L186) | _stub-only_ |
+| `run_tests` | `shell` | _(stub)_ | [`consumer_tool_catalog.json:200`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L200) | _stub-only_ |
+| `run_quality_checks` | `shell` | _(stub)_ | [`consumer_tool_catalog.json:214`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L214) | _stub-only_ |
+| `list_skills` | `ro` | stdio | [`consumer_tool_catalog.json:227`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L227) | [`tools.ts:762`](../../src/scripts/mcp_server/tools.ts#L762) |
+| `list_commands` | `ro` | stdio | [`consumer_tool_catalog.json:234`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L234) | [`tools.ts:777`](../../src/scripts/mcp_server/tools.ts#L777) |
+| `list_rules` | `ro` | stdio | [`consumer_tool_catalog.json:241`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L241) | [`tools.ts:792`](../../src/scripts/mcp_server/tools.ts#L792) |
+| `compile_router` | `shell` | _(stub)_ | [`consumer_tool_catalog.json:248`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L248) | _stub-only_ |
+| `read_resource_body` | `ro` | stdio | [`consumer_tool_catalog.json:261`](../../src/scripts/mcp_server/consumer_tool_catalog.json#L261) | [`tools.ts:808`](../../src/scripts/mcp_server/tools.ts#L808) |
 
 ## Glossary
 

package/docs/contracts/no-runtime-boundary.md

@@ -1,3 +1,8 @@
+---
+stability: beta
+keep-beta-until: 2026-08-17
+---
+
 # No-Runtime Boundary Contract
 
 > **Audience:** Every Mission-Mode decision, skill author, and recipe reviewer.
@@ -52,5 +57,5 @@ and violating the no-runtime principle).
 ## Decision authority
 
 A mission step that is unclear against this contract goes to the AI Council
-(`python3 src/scripts/council_cli.py`) before any build work starts.
+(`./scripts-run src/scripts/council_cli`) before any build work starts.
 The council verdict becomes an ADR if it changes this table.

package/docs/contracts/review-lens-schema.md

@@ -1,3 +1,8 @@
+---
+stability: beta
+keep-beta-until: 2026-08-17
+---
+
 # Review-lens routing schema
 
 Defines what a review **lens** is, the metadata it carries, and which review

package/docs/contracts/rule-router.md

@@ -29,10 +29,10 @@ are preserved. New / formalized fields:
 | Key | Required | Values | Purpose |
 |---|---|---|---|
 | `type` | yes | `always` \| `auto` | Existing. Kernel = `always`; everything else = `auto`. |
-| `tier` | yes | `kernel` \| `tier-1` \| `tier-2` | New names. Kernel = always-loaded; tier-1 = balanced + full; tier-2 = full only. |
+| `tier` | yes | `kernel` \| `tier-1` \| `tier-2` | New names. Kernel = always-loaded; tier-1 / tier-2 = trigger-routed on demand, in every discipline profile (ADR-040 / ADR-110). |
 | `triggers` | yes for non-kernel | list of objects | When the rule activates. **Forbidden** on kernel rules. |
 | `routes_to` | yes for non-kernel | list of strings | Skills / guidelines whose body fulfils the rule. **Forbidden** on kernel rules. |
-| `profile` | no | `minimal` \| `balanced` \| `full` | Override the tier-derived default profile. Rare; used only when a tier-2 rule must ship in `balanced`. |
+| `profile` | no | `minimal` \| `essential` \| `full` | Override the tier-derived default profile. Rare; currently unused by any shipped rule. |
 | `triggered_by` | back-ref, on routed artifact | list of strings | Skill / guideline frontmatter declares which rule(s) route to it. Bidirectional check (P3.3). |
 
 ### `triggers:` shape
@@ -82,13 +82,13 @@ whose body is fully covered by an existing architectural contract.
 
 ## Compiled output — `router.json`
 
-`scripts/compile_router.py` reads every rule frontmatter and emits
+`src/scripts/compile_router.ts` reads every rule frontmatter and emits
 `dist/router.json` (tracked in git), used by host agents at session
 start. Deterministic key order, sorted lists, stable across runs.
 
 ```json
 {
-  "schema_version": 1,
+  "schema_version": 2,
   "kernel": ["agent-authority", "ask-when-uncertain", "commit-policy",
              "direct-answers", "language-and-tone", "no-cheap-questions",
              "non-destructive-by-default", "scope-control",
@@ -96,18 +96,75 @@ start. Deterministic key order, sorted lists, stable across runs.
   "tier_1": [{"id": "source-of-truth",
               "triggers": [{"path_prefix": "agents/"},
                            {"path_prefix": "dist/agent-src/"}],
-              "routes_to": ["skill:agent-docs-writing"]}],
+              "routes_to": ["skill:agent-docs-writing"],
+              "workspaces": ["agent-config-maintainer"],
+              "packs": ["meta"]}],
   "tier_2": [/* same shape as tier_1 */],
   "profiles": {
-    "minimal":  ["__kernel__"],
-    "balanced": ["__kernel__", "__tier_1__"],
-    "full":     ["__kernel__", "__tier_1__", "__tier_2__"]
+    "minimal":   ["__kernel__"],
+    "essential": ["__kernel__", "downstream-changes"],
+    "full":      ["__kernel__", "__tier_1__", "__tier_2__"]
   }
 }
 ```
 
 Generated alongside `marketplace.json` during `task generate-tools`.
 
+### Schema v2 — installation-scoping fields (2026-07-07)
+
+Every **non-kernel** entry carries `workspaces:` and `packs:`, copied
+verbatim (sorted) from the rule's frontmatter. They let projection- and
+install-time tooling filter rule bodies AND thin-projection pointer lines
+by the installed workspace/pack set (`road-to-request-scoped-rule-load`
+Phase 1) — per ADR-040 the filtering happens at projection time; there is
+no runtime resolver.
+
+- **Additive only.** v1 readers ignore unknown keys; nothing else in the
+  shape changed. Readers MUST NOT hard-fail on `schema_version: 2`.
+- **Kernel entries stay bare id strings.** The kernel is unconditional
+  and workspace-independent by definition — it never carries scoping
+  fields and is never filtered by installation.
+- **Source of the values:** `src/rules/*.md` frontmatter.
+  `lint_artefact_frontmatter` (wired into `task ci`) enforces that every
+  rule declares non-empty `workspaces:` + `packs:` lists whose ids exist
+  in `src/config/discovery/{workspaces,packs}.yml` — unknown ids fail
+  lint before they can reach the router.
+
+## Host-native glob activation (Cursor / Windsurf)
+
+Since 2026-07-07 (`road-to-request-scoped-rule-load` Phase 2) the
+Cursor/Windsurf projectors derive `globs:` from the rule's path-shaped
+triggers: `file_pattern` maps verbatim, `path_prefix` maps as
+`<prefix>**`. Rules with ≥1 path-shaped trigger auto-attach host-natively
+(Cursor auto-attach / Windsurf `trigger: glob`) — deterministic, no
+model-compliance dependency. Keyword/phrase/intent-only rules keep
+description-based activation (Agent-Requested / `model_decision`).
+
+**No-double-fire invariant:** when thin projection lands on those hosts, a
+glob-attached rule must NOT also ship an eager inline body there — the
+host-native attach IS its conditional load. The thin projector treats
+glob-capable rules on glob-capable hosts as already-conditional; the
+pointer mechanism is for hosts without a native equivalent (Claude Code).
+
+### Profiles — the always-honoured surface (ADR-110)
+
+Profiles name the **always-honoured** rule surface per discipline tier;
+entries without the `__` wrapper are individual rule ids. Trigger routing of
+tier-1/tier-2 stays active under **every** profile — trigger semantics are
+configuration-independent (ADR-040). The runtime knob is
+`discipline_profile: auto | off | essential | full` (`off` → `minimal`
+surface); resolution semantics (including the legacy `rule_loading_tier`
+mapping and the `auto` host-capability check against
+`src/config/host-capabilities.yml`) live in `resolve_discipline_profile()`
+in the work-engine settings lib.
+
+**`balanced` was retired 2026-07-07** (deleted, not renamed): the size cut
+(kernel + tier_1) measured a NULL discipline lift (p=0.81, n=24 —
+`docs/benchmark.md § Cost-factor sweep`) because it missed the lift-carrying
+`downstream-changes`. Its successor `essential` is cut by measured content
+(kernel + the lift-carrying rules; +0.458 lift at ~3.3x tokens, p=0.0135).
+Legacy `rule_loading_tier: balanced` values map to `essential`.
+
 ## Activation semantics
 
 The host agent reads `dist/router.json` once per session. Per turn:
@@ -123,6 +180,43 @@ The host agent reads `dist/router.json` once per session. Per turn:
 No runtime profile resolution — the profile is fixed at session
 start, the router lookup is keyword/phrase/path/intent matching only.
 
+### Intent-trigger semantics — two gates, two purposes (reconciled 2026-07-07)
+
+Two tools consume `intent:` triggers with deliberately different semantics.
+This divergence is **justified and locked**, not drift
+(`road-to-token-proof-and-story` Phase 2):
+
+| Tool | Intent semantics | Purpose |
+|---|---|---|
+| `trigger_coverage.ts` + the golden-set fires-check | word-set inclusion (every alpha word >2 chars of the intent appears in the prompt) | **Falsifiability floor** — a deliberately generous mechanical proxy proving a rule CAN fire on a phrasing; gates coverage claims. |
+| `router_telemetry.ts` (replay / field evidence) | informational-only — never auto-matches | **Field estimation** — real hosts resolve intents by model judgment, which cannot be replayed deterministically; pretending the word-set proxy models host behaviour would fabricate activation counts. |
+
+Consequence: **replay UNDERCOUNTS intent-triggered rule loads.** Every
+replay-derived figure (field-token-evidence report, benchmark refresh,
+release story) MUST state the chosen semantics and carry this caveat. Rules
+relying on intent triggers alone have no mechanical signal at all — hence
+the intent-only backstop audit (Phase 0 of
+`road-to-request-scoped-rule-load`: every intent-only rule gained
+keyword/phrase backstops or a written disposition).
+
+## Activation end-state — one runtime knob (token program, 2026-07-07)
+
+Locked by the token-program integration council
+(`agents/settings/contexts/token-program-integration-verdict.md`) so no
+track ships a competing setting:
+
+- **Runtime:** ONE knob — `discipline_profile: auto | off | essential |
+  full` (shipped default `auto` = ON once its evidence gates pass; owned by
+  `road-to-discipline-profile-tiering`). Thin projection, when un-deferred,
+  folds under `essential` as an implementation detail; `lean_projection.mode`
+  is then absorbed/retired. No new runtime toggles for this layer.
+- **Install-time (not a runtime setting):** consumer scoping via
+  `projection.rule_workspaces` / `projection.rule_packs` — default flips
+  `legacy-all` → scoped as a reviewed release decision after the
+  misclassification audit (done 2026-07-07) + measured before/after.
+- **Host-native (no setting):** Cursor/Windsurf glob auto-attach (§ above)
+  is always on — deterministic, no compliance risk.
+
 ## Kill-switch — thin-projection rollback (lean-initial-context Phase 2.3)
 
 Phase 3 of the lean-initial-context migration makes the per-tool projector

package/docs/contracts/skill-bundled-assets.md

@@ -27,7 +27,7 @@ A BUNDLED SCRIPT RESOLVES EVERY SIBLING ASSET VIA ITS OWN FILE LOCATION
 ```
 
 - The agent invokes bundled scripts with an **absolute or skills-root-
-  relative path**: `python3 <skills-root>/<name>/scripts/<tool>.py …`.
+  relative path**: `node_modules/.bin/tsx <skills-root>/<name>/scripts/<tool>.ts …`.
   `<skills-root>` = `~/.claude/skills` (Claude Code consumer install),
   the tool-specific projection dir for other agents, or `src/skills`
   inside this repo.

package/docs/contracts/skill-dry-run.md

@@ -17,7 +17,7 @@ plain-language "this skill will…" summary. It surfaces:
 - its **execution type** (`manual` / `assisted` / `automated`, default `manual`) and **handler**
   (`none` / `shell` / `php` / `node` / `internal`);
 - its declared **`allowed_tools`**;
-- any **file or command targets** named in the body (backtick paths, `python3 scripts/…` invocations).
+- any **file or command targets** named in the body (backtick paths, `./scripts-run src/scripts/…` invocations).
 
 ## Explicit non-goals
 

package/docs/contracts/subagent-boundary.md

@@ -1,3 +1,8 @@
+---
+stability: beta
+keep-beta-until: 2026-08-17
+---
+
 # Subagent Boundary Contract
 
 What a subagent **owns** and what it must **never** own. As delegation spreads

package/docs/contracts/ticket-bundle-format.md

@@ -1,3 +1,8 @@
+---
+stability: beta
+keep-beta-until: 2026-08-17
+---
+
 # Ticket-bundle format
 
 > The contract every downstream artifact reads from: the `emit-tickets` skill,
@@ -62,9 +67,9 @@ source_refs:                   # files the build reads/changes, SHA-pinned (drif
   - { path: src/scripts/build_linear_digest.py, sha: <git-blob-sha> }
 assets: [T-001.assets/wireframe.png]   # relative to the bundle dir
 acceptance:                    # runnable AND isolation-testable; no prose-only
-  - "python3 src/scripts/lint_ticket_buildable.py exits 0"
+  - "./scripts-run src/scripts/lint_ticket_buildable exits 0"
 boundaries:                    # ENFORCED by the work_engine boundary guard
-  must_touch:    [src/scripts/lint_ticket_buildable.py]
+  must_touch:    [src/scripts/lint_ticket_buildable]
   may_touch:     [Taskfile.yml]
   must_not_touch: [src/scripts/work_engine/**, ".github/**"]
 ---
@@ -91,7 +96,7 @@ context spine or `source_refs`, the ticket is incomplete.
 
 ## 5. Self-containedness floor (per `model_tier`)
 
-Enforced by `lint_ticket_buildable.py`. A ticket FAILS the gate if its tier's
+Enforced by `lint_ticket_buildable`. A ticket FAILS the gate if its tier's
 row is not satisfied:
 
 | tier | acceptance | ≥1 concrete path | non-empty boundaries | resolvable assets | size floor |
@@ -177,7 +182,7 @@ Git LFS is **not** configured in this repo today, and wiring it (install +
 remote LFS store) is heavier than v1 needs. v1 decision: assets are git-tracked
 binaries under a **size cap** — ≤ 500 KB per asset — and authors prefer vector /
 text context (Mermaid, ASCII, SVG, example-I/O Markdown) over raster where it
-carries the same information. `lint_ticket_buildable.py` warns on any asset over
+carries the same information. `lint_ticket_buildable` warns on any asset over
 the cap. LFS is revisited only if `agents/tickets/**` binary weight is proven a
 real problem (same "defer until observed" discipline as the mutable-tickets
 mode). Non-binary design context lives as plain Markdown in the `.assets/` folder.

package/docs/contracts/tier-3-contrib-plugin.md

@@ -58,10 +58,10 @@ When the first user request lands, the responder MUST:
    schema below.
 2. Add the tool ID to `_VALID_TOOLS`, `USER_SCOPE_PATHS`,
    `SCOPE_SUPPORT`, and the bash `VALID_TOOLS` set.
-3. Implement `ensure_<tool>_bridge` in `scripts/install.py` (≤60 LOC
+3. Implement `ensure_<tool>_bridge` in `src/install/` (≤60 LOC
    — if larger, escalate via ADR per Phase 2.5 gate).
 4. Append a row to the `README.md` "Supported Tools" table.
-5. Re-run `task lint-skills` + `python3 -m pytest tests/test_install_py.py`.
+5. Re-run `task lint-skills` + `task test`.
 
 ```yaml
 # agents/manifests/contrib/<tool-id>.yml

package/docs/contracts/write-engine.md

@@ -132,6 +132,9 @@ effects on disk.
   blending voices is deferred.
 - **No file writes.** The engine prints; the user copies. Saving the
   output to `agents/` or anywhere else is a future feature.
+- **Quote floor applies.** Any draft citing an external source follows
+  [`content-quoting-floor`](../../src/rules/content-quoting-floor.md) —
+  ≤15 words per quote, one quote per source, paraphrase by default.
 
 ## See also
 

package/docs/customization.md

@@ -229,17 +229,28 @@ the sourced rationale lives in the design dossier
 > a budget is tight, reach for the **model** lever first — lowering the rule
 > tier saves little and drops guardrails.
 
-`rule_loading_tier` is the master switch for rule-tier loading. The kernel
-(always-loaded Iron-Law floor, ≤ 26k chars across 9 rules) ships in every
-profile. Tier-1 and tier-2 rules are gated by profile and resolved at
-session start from `dist/router.json` (compiled by `scripts/compile_router.py`).
-
-| Profile | Rule tiers loaded | Token footprint | Best for |
+`rule_loading_tier` is the **legacy** master switch for rule-tier loading; its
+successor is the single runtime knob `discipline_profile: auto | off |
+essential | full` (ADR-110 — when set, it wins; legacy values map
+minimal→off, balanced→essential, full→full). The kernel (always-loaded
+Iron-Law floor, ≤ 26k chars across 9 rules) ships in every profile. Tier-1
+and tier-2 trigger routing stays active under every profile (trigger
+semantics are configuration-independent, ADR-040); the profile names the
+always-honoured surface, resolved at session start from `dist/router.json`
+(compiled by `scripts/compile_router.ts`).
+
+| Profile | Always-honoured surface | Token footprint | Best for |
 |---|---|---|---|
-| `minimal` | kernel only (no router, no auto-rules) | lowest | Cost-sensitive sessions; trivial Q&A; CI runs |
-| `balanced` | kernel + tier-1 auto-rules (default) | medium | Day-to-day work — current behaviour superset |
-| `full` | kernel + tier-1 + tier-2 (everything) | highest | Agent-config development; full rule fidelity |
-| `custom` | profile ignored — every matrix value must be set explicitly | varies | Power users with bespoke rule sets |
+| `off` (legacy `minimal`) | kernel only | ~1x (lowest) | Hosts with a MEASURED null discipline lift (`src/config/host-capabilities.yml`); cost-sensitive sessions |
+| `essential` | kernel + the lift-carrying rules (`downstream-changes`) | ~3.3x | Day-to-day work — keeps the measured weak-host discipline lift (+0.458, p=0.0135) |
+| `full` | kernel + tier-1 + tier-2 (everything) | ~11.7x (highest) | EXPERIMENTAL opt-in — residual lift over `essential` not established (p=0.37); agent-config development |
+| `auto` | resolved per session: measured-null host → `off`, otherwise → `essential` | varies | The evidence-gated default target |
+| `custom` (legacy) | profile ignored — every matrix value must be set explicitly | varies | Power users with bespoke rule sets |
+
+> **`balanced` was retired 2026-07-07** — the size cut (kernel + tier-1)
+> measured a NULL discipline lift (p=0.81, `docs/benchmark.md § Cost-factor
+> sweep`) because it missed the lift-carrying `downstream-changes`. Existing
+> `rule_loading_tier: balanced` settings keep working and map to `essential`.
 
 The kernel-and-router architecture is documented in
 [`docs/contracts/rule-router.md`](contracts/rule-router.md) and
@@ -345,19 +356,80 @@ level.
 
 ---
 
+## Autonomous roadmap execution
+
+Roadmaps can declare how `/roadmap:process-full` / `process-phase`
+should interact, via frontmatter (`/roadmap:create` asks this as one
+question at creation time):
+
+```yaml
+execution:
+  mode: autonomous   # autonomous | phase-checkpoints | interactive
+```
+
+- `interactive` (absent-field default) — every gate fires as today.
+- `phase-checkpoints` — one compact status + continue prompt per phase
+  boundary.
+- `autonomous` — at run start the loop derives an **execution
+  contract** (feature branch, chunked commits, push to that branch
+  only, PR-open — never merge, batched artifact drafting, council
+  auto-enable). ONE acceptance activates all grants for the run; after
+  that the run is uninterrupted except the safety floors (Hard Floor,
+  security-sensitive-stop, N=3 validation budget, context-hygiene
+  aborts, deferred-`[~]` archival gate).
+
+The frontmatter field is a declaration of intent, never a permission
+grant — authorization happens only at the run-start contract, derived
+fresh from the roadmap's current content on every invocation. Details:
+`contexts/execution/roadmap-execution-contract.md`, template rule 18 in
+`templates/roadmaps.md`. Global `roadmap.*` keys in
+`.agent-settings.yml` (quality/dashboard cadence, pre-run gate) keep
+their meaning in every mode.
+
+---
+
 ## Project documentation
 
 Consumer projects can maintain their own agent documentation:
 
 ```
 agents/
-├── docs/                    ← Feature docs, architecture decisions
-├── contexts/                ← Shared knowledge documents
-├── features/                ← Feature plans
-├── roadmaps/                ← Active roadmaps
-└── overrides/               ← Skill/rule/command overrides
+├── overrides/               ← Skill/rule/command overrides (required after migrate)
+├── .event4u-bridge.yml      ← Global-only bridge marker (ADR-020)
+├── knowledge/               ← Optional: curated project-specific knowledge pages
+├── memory/                  ← Optional: memory promotion pipeline
+├── roadmaps/                ← Optional: project-local roadmaps
+├── tmp/                     ← Optional: user inbox (gitignored)
+└── tmp.old/                 ← Optional: processed inbox archive (gitignored)
 ```
 
+Full classification (git policy, retention, owner) for every allowed entry:
+[`docs/contracts/agents-layout.md`](contracts/agents-layout.md).
+
+#### User inbox workflow (`agents/tmp/` → `agents/tmp.old/`)
+
+Drop a note or draft into `agents/tmp/` and point a command at it
+(e.g. "create a roadmap from `agents/tmp/my-idea.md`"). The agent reads
+the file, processes it, and moves it to `agents/tmp.old/` in the same
+reply. The archive decays via a 30-day janitor TTL.
+
+- Both dirs are **gitignored** — they never enter the commit graph.
+- The agent's own scratch goes to `agents/runtime/tmp/` — never into `agents/tmp/`.
+- Run `task janitor` for a dry-run report; `task janitor-apply` to sweep.
+
+#### Keeping your consumer `agents/` clean
+
+Run the sync-gitignore fix command after an install or migration:
+
+```bash
+agent-config sync-gitignore --cleanup-legacy
+# Or via the chat command: /sync-gitignore:fix
+```
+
+This scrubs legacy patterns, syncs the managed block, and reports any
+files that are tracked but now ignored (the `git rm --cached` commands
+to fix them are printed — never run automatically).
+
 Module-level documentation goes into `app/Modules/*/agents/`.
 
 ### `agents/` overlay cascade

package/docs/decisions/ADR-107-legal-domain-pack-adoption.md

@@ -43,7 +43,7 @@ experimental`, flipping `default_install` to anything but `false`, or any
 commercial / hosted surface, is **blocked** until a licensed German attorney has
 reviewed the *framing* (the `legal-safety-floor` rule, `LEGAL_NOTICE.md`, and the
 RDG individual-case wording — **not** skill correctness) and the review is recorded
-in `LEGAL_NOTICE.md` as `Framing reviewed by <name>, Rechtsanwalt/Rechtsanwältin,
+in `LEGAL_NOTICE.md` as `Framing reviewed by <name>, Rechtsanwalt/Rechtsanwältin,  <!-- md-language-check: ignore -->
 <date>`. The deep AI-council (2026-06-24) scoped this as a bounded (~€300–800,
 1–2h) one-time gate, **not** a blocker for the current lab release (lab is
 explicitly unvetted; users opt in knowingly via the consent gate). Enforced by