@event4u/agent-config 3.3.0 → 4.1.0

package/docs/contracts/file-ownership-matrix.md

@@ -19,7 +19,7 @@ This contract defines the **schema** of the file-ownership matrix: the
 machine-readable JSON at `docs/contracts/file-ownership-matrix.json` and
 the human-readable mirror at
 `agents/settings/contexts/structural/file-ownership-matrix.md`. Both are
-regenerated from `.agent-src.uncompressed/` by the generator and locked
+regenerated from `.agent-src.uncondensed/` by the generator and locked
 by CI.
 
 **Status:** internal-locked (`stability: beta`). Schema bumps require a
@@ -49,7 +49,7 @@ The JSON document is a single object:
 {
   "version": 1,
   "generated_by": "scripts/generate_ownership_matrix.py",
-  "source_of_truth": ".agent-src.uncompressed/",
+  "source_of_truth": ".agent-src.uncondensed/",
   "files": {
     "<repo-root-relative path>": {
       "kind": "rule | skill | command | context | persona",
@@ -111,7 +111,7 @@ backstop; the consistency gate fails if regeneration drifts.
 ## Scope notes (v1)
 
 - **Greppable surface:** `rules/`, `skills/`, `commands/`, `contexts/`,
-  `personas/` under `.agent-src.uncompressed/`. Generated tool
+  `personas/` under `.agent-src.uncondensed/`. Generated tool
   projections (`.augment/`, `.claude/`, `.cursor/`, …) are intentionally
   ignored — they are downstream of the source of truth.
 - **`skill:` frontmatter in rules** (named in roadmap 0.1.2) is reserved.

package/docs/contracts/frontmatter-contract.md

@@ -10,7 +10,7 @@ keep-beta-until: 2026-08-19
 > ADR is the decision; this file is the worked-example reference linters,
 > installer, and contributors cite at runtime.
 
-Every `.md` artefact under `.agent-src.uncompressed/` MUST declare the five
+Every `.md` artefact under `.agent-src.uncondensed/` MUST declare the five
 ADR-013 discovery keys. The release-time manifest builder
 (`scripts/build_discovery_manifest.py`) derives all workspace/pack assignment
 from these alone — **no manual workspace or pack list is ever maintained**.
@@ -118,7 +118,7 @@ the linter rejects that collision.
 | Surface | What runs | When |
 |---|---|---|
 | Local | `task lint-artefact-frontmatter` | manual / pre-commit |
-| Pre-commit | `pre-commit-roadmap-progress` template | when `.agent-src.uncompressed/*.md`, `config/discovery/*.yml`, or the linter itself is staged |
+| Pre-commit | `pre-commit-roadmap-progress` template | when `.agent-src.uncondensed/*.md`, `config/discovery/*.yml`, or the linter itself is staged |
 | CI | `task ci` → `lint-artefact-frontmatter` | every push / PR |
 
 Install the pre-commit hook with:
@@ -133,8 +133,8 @@ are staged.
 
 ## Roundtrip invariant
 
-Frontmatter survives the `task sync` compression pipeline. Path-bearing
+Frontmatter survives the `task sync` condensation pipeline. Path-bearing
 keys (`load_context`) may be rewritten relative to the projected location,
 but the five Phase-1 keys above are byte-stable between
-`.agent-src.uncompressed/`, `.agent-src/`, and `.augment/`. Enforced by
+`.agent-src.uncondensed/`, `.agent-src/`, and `.augment/`. Enforced by
 `tests/test_frontmatter_roundtrip.py`.

package/docs/contracts/ghostwriter-schema.md

@@ -25,7 +25,7 @@ explicit `accept` step on `/ghostwriter:fetch` re-runs.
   profiles live here. **Gitignored by default** via the package-managed
   `.gitignore` block. A `--shared` opt-in to commit profiles is
   deferred to v2; only the doc note lands in v1.
-- **Package source** — `.agent-src.uncompressed/ghostwriter/` ships
+- **Package source** — `.agent-src.uncondensed/ghostwriter/` ships
   the README, this schema doc, and `fictional: true` fixtures only.
   **Zero real-person profiles ever ship with the OSS package.** A CI
   lint (`task lint-ghostwriter-source`) enforces this rule by failing
@@ -181,7 +181,7 @@ attribution stays deterministic.
 fixtures are schema examples for a single canonical name; aliases are a
 consumer-only deployment feature. The package-source lint
 (`task lint-ghostwriter-source`) fails on `aliases:` in
-`.agent-src.uncompressed/ghostwriter/`.
+`.agent-src.uncondensed/ghostwriter/`.
 
 ### Settings toggle (consumer-only)
 
@@ -293,7 +293,7 @@ instead of merging.
 
 The lint runs in `task ci` and fails on:
 
-1. Any file under `.agent-src.uncompressed/ghostwriter/` whose stem is
+1. Any file under `.agent-src.uncondensed/ghostwriter/` whose stem is
    **not** on the fixture allowlist (`scripts/ghostwriter_fixture_allowlist.txt`).
 2. Any allowlisted file missing `fictional: true` in frontmatter.
 3. Any package-source file (`fictional: true`) carrying an `aliases:`

package/docs/contracts/gui-wizard.md

@@ -135,7 +135,7 @@ tracked under the Phase 6 follow-ups.
 
 `/api/apply` accepts a discriminated-union body keyed on
 `schema_version`. The full JSON Schema lives at
-[`schemas/wizard-apply-payload.schema.json`](../../schemas/wizard-apply-payload.schema.json).
+[`internal/schemas/wizard-apply-payload.schema.json`](../../internal/schemas/wizard-apply-payload.schema.json).
 
 | `schema_version` | Variant | Shape |
 |---|---|---|

package/docs/contracts/harness-expectations.md

@@ -0,0 +1,123 @@
+# Harness Expectations — when AI tool behaviour looks like a package bug but isn't
+
+**Status:** Active (Phase D of `road-to-clean-skill-distribution-channels.md`)
+**Owner:** maintainer-team
+**Inputs:** Phase D roadmap steps + the 2026-05-25 misdiagnosis chat session that opened this track.
+
+## The case for this document
+
+On 2026-05-25 a Claude Code session surfaced three behaviours that looked like `event4u/agent-config` bugs. Two of the three turned out to be **host-harness behaviour** the package has no control over. The third (cross-scope skill drift) was a real package-side bug fixed in Phases A–C. This document captures the host-side three so the next agent / onboarding session / opened issue does not re-run the misdiagnosis loop.
+
+## Class A — Plugin-namespaced peer skills
+
+### Symptom
+
+The session shows skills under namespaces like `codex:`, `cc-gemini-plugin:`, or another `<vendor>:` prefix:
+
+```
+- codex:setup
+- cc-gemini-plugin:gemini-agent
+- codex:rescue
+```
+
+These names do NOT appear in `event4u/agent-config`'s skill catalog, the README, or the contracts.
+
+### What's actually happening
+
+Claude Code (and similar harnesses) supports **sibling plugins** in addition to the primary `event4u/agent-config` install. Each sibling plugin owns its own skills, namespaced by the plugin id. The harness surfaces every loaded plugin's skills in the same `<available_skills>` list during the session.
+
+- `codex:*` skills come from a sibling plugin that wraps the Codex CLI.
+- `cc-gemini-plugin:*` skills come from a sibling plugin that wraps Gemini-CLI integration.
+
+`event4u/agent-config` does not ship, control, or update these plugins. They are independent installs by independent maintainers.
+
+### What the package can do
+
+Nothing — sibling plugins are out of scope by construction. The user can:
+
+- Remove the sibling plugin if it is unwanted (via the harness's plugin management — outside this package).
+- Ignore the namespaced names; they will not collide with this package's skill IDs because the prefix differs.
+
+### Where to look for the true source
+
+Per Claude Code: `claude plugin list` (or equivalent) shows every loaded plugin. Each `<vendor>:` namespace traces back to a plugin row in that listing. Bug reports for those skills go to the respective plugin maintainer.
+
+## Class B — Deferred tools that need ToolSearch
+
+### Symptom
+
+A session sees a `<system-reminder>` block like:
+
+```
+The following deferred tools are now available via ToolSearch.
+Their schemas are NOT loaded — calling them directly will fail with
+InputValidationError. Use ToolSearch with query "select:<name>[,<name>...]"
+to load tool schemas before calling them:
+TaskCreate
+WebFetch
+Monitor
+mcp__claude_ai_Linear__authenticate
+...
+```
+
+The named tools are real — they show up in the harness's runtime — but the agent cannot call them directly because the tool **schema** isn't loaded yet.
+
+### What's actually happening
+
+Claude Code's tool-loading is **context-budgeted**. The full tool registry (TaskCreate, WebFetch, every MCP tool from every registered server, etc.) can be many kilobytes of JSON-schema. Loading every schema on every turn would blow the context budget for routine reads. The harness solves this by registering tool **names** up-front and deferring schema load until `ToolSearch` is called — that's the on-ramp.
+
+This is not a package issue, and `event4u/agent-config` cannot pre-load these schemas — the harness owns the budget.
+
+### What the package can do
+
+Nothing — the loading strategy is the harness's contract with the model. Skills that want to use a deferred tool must:
+
+1. Run `ToolSearch` with `select:<name>` to load the schema.
+2. Call the tool with the now-known parameters.
+
+Skills in this package that need deferred tools document the load step explicitly (see `agents-md-thin-root` § Tool loading for the pattern).
+
+### Where to look for the true source
+
+Per Claude Code's documentation on tool surfaces and the `ToolSearch` primitive. The package does not own this behaviour.
+
+## Class C — Duplicate skill registration (real package bug, fixed in Phases A–C)
+
+### Symptom
+
+The same skill appears twice in `<available_skills>` with different `description:` strings, or behaves inconsistently across calls.
+
+### What's actually happening
+
+A user-global install (e.g. `~/.claude/skills/`) and a project-local install (`./.claude/skills/`) coexist at **different versions**. The harness loads both. The earlier register wins the description in some calls, the later in others.
+
+Unlike Classes A and B, this is a real package-side issue.
+
+### What the package does
+
+1. **Default install is filesystem-only** ([`skill-distribution-channels.md`](skill-distribution-channels.md)).
+2. **Pre-flight scope guard** refuses installs that would create cross-scope drift ([`install-scopes.md`](install-scopes.md)).
+3. **Post-install probe** surfaces any remaining drift after install (`task probe:skills`).
+4. **Cleanup script** for stale other-scope installs (`bash scripts/cleanup_other_scope.sh --confirm`).
+
+### Where to look for the true source
+
+```bash
+task probe:skills
+```
+
+The probe lists every duplicate / drift finding with the exact source paths so the cause is visible in one read.
+
+## When in doubt — diagnostic sequence
+
+1. Run `task probe:skills` — rules out Class C.
+2. If the suspicious skill carries a `<vendor>:` prefix you don't recognise → Class A. Check `claude plugin list`.
+3. If the harness logs `deferred tools … available via ToolSearch` → Class B. The skill needs an explicit `ToolSearch` step.
+4. None of the above → file an issue at https://github.com/event4u-app/agent-config with the output of `task probe:skills` attached.
+
+## See also
+
+- [`skill-distribution-channels.md`](skill-distribution-channels.md) — canonical channel per tool.
+- [`install-scopes.md`](install-scopes.md) — scope guard contract.
+- [`agents/evidence/audits/2026-05-distribution-channels/`](../../agents/evidence/audits/2026-05-distribution-channels/) — the underlying audits.
+- [`README.md` § Harness expectations](../../README.md#harness-expectations) — front-of-house pointer to this contract.

package/docs/contracts/host-agent-protocol.md

@@ -1,3 +1,7 @@
+---
+stability: experimental
+---
+
 # Host-Agent Protocol Contract
 
 > **Status** · v0 / inventory · 2026-05-24. The daily workspace shells out to

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

@@ -12,7 +12,7 @@ keep-beta-until: 2026-08-12
 > - **Created:** 2026-04-22
 > - **Status:** Phase 1 shipped 2026-04-23 — `DeliveryState` +
 >   dispatcher live under
->   [`.agent-src.uncompressed/templates/scripts/implement_ticket/`](../../.agent-src.uncompressed/templates/scripts/implement_ticket/).
+>   [`.agent-src.uncondensed/templates/scripts/implement_ticket/`](../../.agent-src.uncondensed/templates/scripts/implement_ticket/).
 >   Step wiring (Phase 2) still open. Schema **v1** envelope
 >   (`work_engine.state` / `work_engine.migration.v0_to_v1`) shipped
 >   2026-04-27 as R1 Phase 2 — see [State schema v1](#state-schema-v1)
@@ -265,7 +265,7 @@ Bounded per the top-level roadmap rule:
 - **Four allowed types:** `domain-invariants`,
   `architecture-decisions`, `incident-learnings`,
   `historical-patterns`. All four exist in the
-  [templates directory](../../.agent-src.uncompressed/templates/agents/memory/).
+  [templates directory](../../.agent-src.uncondensed/templates/agents/memory/).
 - **Keys:** files touched by the plan, symbols referenced by the
   ticket.
 - **Decision-change rule:** a memory hit that did not change an
@@ -278,7 +278,7 @@ Bounded per the top-level roadmap rule:
 
 Read from `.agent-settings.yml` `roles.active_role` and resolved
 via `resolve_policy()` in
-[`persona_policy.py`](../../.agent-src.uncompressed/templates/scripts/implement_ticket/persona_policy.py).
+[`persona_policy.py`](../../.agent-src.uncondensed/templates/scripts/implement_ticket/persona_policy.py).
 Policies live alongside the dispatcher so the flow can consume
 them directly; the shared
 [`role-contracts`](../../docs/guidelines/agent-infra/role-contracts.md)
@@ -319,7 +319,7 @@ skill.
 When a step returns `blocked`, the orchestrator:
 
 1. Emits the numbered questions per
-   [`user-interaction`](../../.agent-src.uncompressed/rules/user-interaction.md).
+   [`user-interaction`](../../.agent-src.uncondensed/rules/user-interaction.md).
 2. Writes a partial report up to the last successful step.
 3. Exits with a `blocked` status — no guess, no fallback.
 
@@ -332,7 +332,7 @@ the context. V1 explicitly does **not** attempt resumable sessions.
 Every step declares — in code — the conditions under which it
 can return `blocked`. The declarations live as module-level
 `AMBIGUITIES` tuples (see
-[`directives/backend/__init__.py`](../../.agent-src.uncompressed/templates/scripts/work_engine/directives/backend/__init__.py)
+[`directives/backend/__init__.py`](../../.agent-src.uncondensed/templates/scripts/work_engine/directives/backend/__init__.py)
 `.all_ambiguities()`). The
 [`test_ambiguity_coverage.py`](../../tests/implement_ticket/test_ambiguity_coverage.py)
 suite locks the contract: adding a new `blocked` path without
@@ -377,7 +377,7 @@ empty, but all headings are present unless explicitly marked
    because nothing was changed.
 
 Implementation: see
-[`directives/backend/report.py`](../../.agent-src.uncompressed/templates/scripts/work_engine/directives/backend/report.py).
+[`directives/backend/report.py`](../../.agent-src.uncondensed/templates/scripts/work_engine/directives/backend/report.py).
 Section renderers are pure and deterministic; consumers can rely
 on the heading order and on each section either rendering with
 content or being omitted per the rules above.
@@ -621,6 +621,6 @@ are blocked by `freeze-guard.yml::manifest-integrity` at PR time.
 - [`../../.github/workflows/freeze-guard.yml`](../../.github/workflows/freeze-guard.yml) — manifest-integrity + live-replay gates
 - [`agent-memory-contract.md`](agent-memory-contract.md)
 - [`../../docs/guidelines/agent-infra/role-contracts.md`](../../docs/guidelines/agent-infra/role-contracts.md)
-- [`../../.agent-src.uncompressed/rules/user-interaction.md`](../../.agent-src.uncompressed/rules/user-interaction.md)
-- [`../../.agent-src.uncompressed/rules/scope-control.md`](../../.agent-src.uncompressed/rules/scope-control.md)
-- [`../../.agent-src.uncompressed/rules/minimal-safe-diff.md`](../../.agent-src.uncompressed/rules/minimal-safe-diff.md)
+- [`../../.agent-src.uncondensed/rules/user-interaction.md`](../../.agent-src.uncondensed/rules/user-interaction.md)
+- [`../../.agent-src.uncondensed/rules/scope-control.md`](../../.agent-src.uncondensed/rules/scope-control.md)
+- [`../../.agent-src.uncondensed/rules/minimal-safe-diff.md`](../../.agent-src.uncondensed/rules/minimal-safe-diff.md)

package/docs/contracts/install-scopes.md

@@ -0,0 +1,77 @@
+# Install Scopes — user-global vs project-local
+
+**Status:** Active (locked 2026-05-25 via Phase B of `road-to-clean-skill-distribution-channels.md`)
+**Owner:** maintainer-team
+**Inputs:** [`docs/contracts/skill-distribution-channels.md`](skill-distribution-channels.md), [`agents/evidence/audits/2026-05-distribution-channels/03-installer-scope-flow.md`](../../agents/evidence/audits/2026-05-distribution-channels/03-installer-scope-flow.md)
+
+## Rule
+
+`event4u/agent-config` may be installed at **one** of two scopes per developer machine:
+
+| Scope | Lives at | Default for | Rationale |
+|---|---|---|---|
+| **project-local** | `<project-root>/.augment/`, `<project-root>/.claude/skills/`, … | Application repos | The skills, rules, and personas are pinned alongside the code they serve. The install is reproducible from the repo. |
+| **user-global** | `~/.augment/`, `~/.claude/skills/`, … | Tooling repos / dotfiles | The same skills follow the developer across every project they touch. Useful when no specific repo "owns" the install. |
+
+Installing at **both** scopes simultaneously is the failure mode the canonical-channel contract prevents — the host harness loads both registrations, and any version drift surfaces as duplicate skills with stale frontmatter (the 2026-05-25 bug).
+
+## The installer enforces this
+
+`scripts/install.sh` runs `scripts/_lib/scope_guard.sh` before any file write:
+
+1. **`OK`** — no install at the other scope. Proceed.
+2. **`WARN`** — install at the other scope, same version. Same content; duplicate registration but no drift. Surface a warning, proceed.
+3. **`DRIFT`** — install at the other scope, different version. Block with a numbered-options prompt:
+
+```
+  1. Abort install — fix drift first (recommended)
+  2. Upgrade the OTHER scope first
+  3. Force install at this scope — accept drift (set SCOPE_GUARD_BYPASS=1)
+  4. Clean the other scope (bash scripts/cleanup_other_scope.sh --confirm)
+```
+
+Non-interactive shells default to **abort**. CI runs and the orchestrator set `SCOPE_GUARD_BYPASS=1` to skip the gate.
+
+The `agent-config setup` wizard exposes the same check at `GET /api/v1/wizard/scope-guard` (extended-mode endpoint). The first wizard step renders the verdict before the user picks an install scope.
+
+## How to clean a stale other-scope install
+
+Use the companion script:
+
+```bash
+# Dry-run (default) — list what would be removed
+bash scripts/cleanup_other_scope.sh --user
+
+# Confirm and delete
+bash scripts/cleanup_other_scope.sh --user --confirm
+
+# Narrow to a single tool
+bash scripts/cleanup_other_scope.sh --user --confirm --tools=claude-code
+
+# Remove from a specific project root
+bash scripts/cleanup_other_scope.sh --project /path/to/proj --confirm
+```
+
+The script refuses to delete anything without `--confirm` per `non-destructive-by-default`. It only touches the tool-scoped paths the contract names (`.claude/skills/`, `.augment/`, `.cursor/rules/`, `.clinerules/`, `.windsurf/rules/`, `.github/copilot-instructions.md`); the rest of the scope root is never modified.
+
+## When to pick which scope
+
+- **App repo** (Laravel, Next.js, monorepo) → project-local. The skills/rules ship with the code; CI installs them deterministically.
+- **Tooling repo** (dotfiles, personal sandbox) → user-global. The install follows the developer.
+- **Both apply** (a tooling repo that also has project-specific overrides) → project-local for the overrides, no user-global install. The override mechanism at `agents/overrides/` covers the divergence.
+
+The scope guard does **not** make the picking decision; it enforces "one scope per machine at one version".
+
+## Failure modes the guard catches
+
+- A user installed `event4u/agent-config` globally a year ago, then `npx`d a recent project that pulled v3.x into `./.claude/skills/`. Same skill ID, different frontmatter on disk. Without the guard, the Claude session sees both registrations and the agent reasons against the wrong description.
+- A maintainer ran `scripts/install.sh --target=$HOME` for a quick test and forgot to clean up. The next project install at the same scope spawns a drift the user has no easy way to debug.
+- A CI run on a worker that previously cached `~/.claude/skills/` from a stale prior job. `CI=true` skips the gate, but the probe (Phase C) catches it post-install.
+
+## See also
+
+- [`docs/contracts/skill-distribution-channels.md`](skill-distribution-channels.md) — per-tool canonical channel.
+- [`scripts/_lib/scope_guard.sh`](../../scripts/_lib/scope_guard.sh) — guard implementation.
+- [`scripts/cleanup_other_scope.sh`](../../scripts/cleanup_other_scope.sh) — companion cleanup.
+- [`tests/test_cleanup_other_scope.py`](../../tests/test_cleanup_other_scope.py) — safety regression.
+- [`README.md` § Installation](../../README.md) — consumer-facing install path.

package/docs/contracts/iron-law-overrides.txt

@@ -15,7 +15,7 @@
 # ADR-002 (2026-05-06) — kernel-bucket cap raise + per-rule overrides.
 # Source: docs/decisions/ADR-002-kernel-bucket-overrides.md
 # Empirical r_actual=0.795 vs r_projected=0.712. The 6 rules below carry
-# Iron-Law fences + non-externalisable enumerations; further compression
+# Iron-Law fences + non-externalisable enumerations; further condensation
 # would force semantic loss. All sit ≤ 4 000-char override ceiling.
 ask-when-uncertain
 direct-answers

package/docs/contracts/kernel-membership.md

@@ -10,7 +10,7 @@ keep-beta-until: 2026-08-12
 > · **Source of truth:** `docs/contracts/rule-classification.md` § 3.1
 > · **Pilot artifacts:** `docs/contracts/pilot/`
 
-Locks the kernel set and the empirical compression rate `r` derived
+Locks the kernel set and the empirical condensation rate `r` derived
 from the P1.3 pilot. Phase 2.2 executes against this contract.
 
 ## § 1 — Inclusion criteria (kernel-only)
@@ -37,7 +37,7 @@ A rule belongs in the kernel iff it satisfies **all** of:
    `no-cheap-questions` are first-class kernel members even though
    they fire during deliberation, not strictly pre-send.)*
 
-All other rules → `compress-and-keep` (auto-tier) or migrate to
+All other rules → `condense-and-keep` (auto-tier) or migrate to
 skill / guideline per `rule-classification.md`.
 
 > **Council amendment (P1.4).** Criterion #3 originally read "must be
@@ -49,12 +49,12 @@ skill / guideline per `rule-classification.md`.
 > existing 9-rule kernel set. See
 > `agents/runtime/council/sessions/20260506T044941Z-phase1-cross-check-r2.json`. <!-- council-ref-allowed: contract decision trace -->
 
-## § 2 — Empirical compression rate (pilot)
+## § 2 — Empirical condensation rate (pilot)
 
 Pilot picks (per P1.3 algorithm: shortest / median / longest of the 9
 always-rules in `rule-classification.md` § 3.1):
 
-| pilot | original | compressed | r | per-rule cap (2.5k) | Iron-Law SHA |
+| pilot | original | condensed | r | per-rule cap (2.5k) | Iron-Law SHA |
 |---|---:|---:|---:|---|---|
 | agent-authority   | 1217 | 1020 | 0.838 | OK        | match (`e3b0c442…`) |
 | direct-answers    | 3991 | 2841 | 0.712 | +341 over | match (`ef438530…`) |
@@ -65,21 +65,21 @@ always-rules in `rule-classification.md` § 3.1):
 | mean r (outlier-skewed by lean pilot) | 0.742 |
 | **median r** (locked for projection) | **0.712** |
 | max r (already-lean floor) | 0.838 |
-| min r (most compressible) | 0.677 |
+| min r (most condensable) | 0.677 |
 
 Locked `r = 0.712` (median) for P2.2 projection. Council amendment
 (P1.4) — the original lock was the **mean** (0.742), but Sonnet 4.5
 flagged outlier skew: `agent-authority` at 1217 chars pre-pilot was
-already near the compression floor (`r = 0.838`), pulling the mean
+already near the condensation floor (`r = 0.838`), pulling the mean
 above the typical band. Median (0.712) is robust to the lean
 outlier and sits inside the roadmap-stated 0.6–0.75 band. Risk
-asymmetry confirms the choice: under-estimating compressed size
+asymmetry confirms the choice: under-estimating condensed size
 blows the 25k cap mid-P2.2 (no abort path); over-estimating just
 yields headroom. GPT-4o concurred. Source:
 `agents/runtime/council/sessions/20260506T044941Z-phase1-cross-check-r2.json`. <!-- council-ref-allowed: contract decision trace -->
 
 **Pilot caveat — already-lean floor.** `agent-authority` (1217 chars
-pre-pilot) yielded only `r = 0.838`. Pre-compressed rules give less
+pre-pilot) yielded only `r = 0.838`. Pre-condensed rules give less
 back; rules > 3k chars give more back. Future kernel additions
 ≤ 1.5k chars should not assume the median — they may already be at
 floor.
@@ -117,7 +117,7 @@ absorbs pilot variance for the 6 untested rules.
 
 ### § 4.1 — Post-P2.2 locked kernel (empirical, 2026-05-06)
 
-P2.2 applied compression (imperative rewrite, examples → guidelines,
+P2.2 applied condensation (imperative rewrite, examples → guidelines,
 rationale → contexts) + verified Iron-Law fence preservation.
 Empirical r=0.795 (vs 0.712 projected). Bucket cap raised 25k → 26k
 via `docs/decisions/ADR-002-kernel-bucket-overrides.md`. Six rules
@@ -164,7 +164,7 @@ until the next kernel re-measurement.
 
 † **agent-authority swap candidate (P1.4 ADR).** Sonnet 4.5 argues
 this is a routing index (zero Iron Law fences, dispatches to other
-kernel rules) and should be `compress-and-keep` (auto-tier-3),
+kernel rules) and should be `condense-and-keep` (auto-tier-3),
 freeing 867 projected chars. The Council also recommends promoting
 `autonomous-execution` (5631 → 4009 projected) into kernel as a
 mode-independent Band-4 authority. Net effect: 23071 − 867 + 4009 =
@@ -191,10 +191,10 @@ Both Council members concurred — the original 1.5k figure forced 8 of
 The 2.5k cap fits 7 of 9 rules without ADR; only the two largest
 remain as legitimate Iron-Law-density exceptions.
 
-Rules that land **above the 2.5k per-rule cap** even after compression
+Rules that land **above the 2.5k per-rule cap** even after condensation
 and Iron-Law preservation:
 
-| rule | post-compression chars | over-cap (2.5k) | reason cap cannot be hit |
+| rule | post-condensation chars | over-cap (2.5k) | reason cap cannot be hit |
 |---|---:|---:|---|
 | direct-answers    | 2842 | +342  | Three Iron-Law fences (≈ 470 chars) + severity-tiered claim table required for invented-facts gate |
 | language-and-tone | 3786 | +1286 | Iron-Law fence + exhaustive user-visible-prose catalog + pre-send gate are co-load-bearing |
@@ -204,12 +204,12 @@ and Iron-Law preservation:
 ADR (see § 5.2).
 
 Per roadmap § "Iron-Law over budget = ADR exception, not auto-
-compress" — these surface as `iron-law-override` exceptions for P2.1
+condense" — these surface as `iron-law-override` exceptions for P2.1
 to gate behind ADRs in `docs/decisions/`.
 
 The remaining 6 always-rules project to 1669–2916 chars post-
-compression — all under the 2.5k cap with no ADR needed. P2.2
-measures the real post-compression sizes; if any breach the cap, an
+condensation — all under the 2.5k cap with no ADR needed. P2.2
+measures the real post-condensation sizes; if any breach the cap, an
 ADR lands per-rule.
 
 ### § 5.2 — Kernel-set swap ADR (agent-authority ↔ autonomous-execution)
@@ -236,19 +236,19 @@ clearing the way for the swap under a fresh ADR.
 
 ## § 6 — Abort criteria for P2.2
 
-**Council amendment (P1.4).** Sonnet 4.5 flagged that P2.2 compresses
+**Council amendment (P1.4).** Sonnet 4.5 flagged that P2.2 condenses
 in place with no defined abort path. The following triggers force
 revert + re-projection rather than mid-phase scramble:
 
 - **Iron-Law drift.** Any kernel rule loses Iron-Law SHA equivalence
-  after compression (whitespace-normalised, case-folded fence-block
-  content). Single occurrence aborts the rule's compression.
-- **Bucket overflow.** Kernel sum post-compression > 27 500 chars
+  after condensation (whitespace-normalised, case-folded fence-block
+  content). Single occurrence aborts the rule's condensation.
+- **Bucket overflow.** Kernel sum post-condensation > 27 500 chars
   (10 % over hard cap). Aborts the entire P2.2 phase.
-- **Single-rule runaway.** Any kernel rule post-compression
-  > 4 000 chars. Aborts that rule's compression; flag for ADR.
+- **Single-rule runaway.** Any kernel rule post-condensation
+  > 4 000 chars. Aborts that rule's condensation; flag for ADR.
 - **Empirical r drift.** Median of measured r across the first 4
-  compressed rules deviates > 0.10 from the locked 0.712 (i.e.,
+  condensed rules deviates > 0.10 from the locked 0.712 (i.e.,
   measured median outside [0.612, 0.812]). P2.2 pauses, re-locks r,
   re-runs § 3 projection.
 
@@ -266,10 +266,10 @@ with the trigger-relaxed parameter, lock new value, re-attempt.
 
 ## § 8 — What this contract does NOT do
 
-- It does **not** edit any source rule. P2.2 ships compression to
-  `.agent-src.uncompressed/rules/`.
+- It does **not** edit any source rule. P2.2 ships condensation to
+  `.agent-src.uncondensed/rules/`.
 - It does **not** lock per-rule `chars` (only the bucket sum). Per-
-  rule values are projections; P2.2 measures real post-compression.
+  rule values are projections; P2.2 measures real post-condensation.
 - It does **not** decide kernel additions. Adding a rule to the
   kernel requires an ADR per roadmap § "Sequencing-drift time-box"
   and re-runs P1.3 with the new candidate.
@@ -288,4 +288,4 @@ with the trigger-relaxed parameter, lock new value, re-attempt.
 | 2026-05-06 | `agents/runtime/council/sessions/20260506T044821Z-phase1-cross-check.json` | Council R1 (truncated at 1024 tokens) | <!-- council-ref-allowed: contract decision trace -->
 | 2026-05-06 | `agents/runtime/council/sessions/20260506T044941Z-phase1-cross-check-r2.json` | Council R2 (3500 tokens) — locks median r, splits criterion #3, adds criterion #5, raises per-rule cap to 2.5k, defines abort criteria | <!-- council-ref-allowed: contract decision trace -->
 | 2026-05-06 | this file | kernel set locked: 9 rules, projected 23 071 chars (median r = 0.712) |
-| 2026-05-06 | P2.2 compression + `scripts/iron_law_sha.py --all-kernel` | empirical: 25 590 chars (r_actual = 0.795 across kernel; longer rules compress less than the pilot median) — see `docs/decisions/ADR-002-kernel-bucket-overrides.md` (KERNEL_HARD raised 25k → 26k, 6 per-rule overrides ≤ 4k ceiling, all Iron-Law SHAs preserved) |
+| 2026-05-06 | P2.2 condensation + `scripts/iron_law_sha.py --all-kernel` | empirical: 25 590 chars (r_actual = 0.795 across kernel; longer rules condense less than the pilot median) — see `docs/decisions/ADR-002-kernel-bucket-overrides.md` (KERNEL_HARD raised 25k → 26k, 6 per-rule overrides ≤ 4k ceiling, all Iron-Law SHAs preserved) |

package/docs/contracts/linear-ai-rules-inclusion.md

@@ -130,7 +130,7 @@ persistence on cloud platforms; the rule is a no-op.
   partitions workspace / team / personal. Step 3 only needs to
   document the three-layer rationale for the README.
 - Re-classify on every audit run; if a rule is added to
-  `.agent-src.uncompressed/rules/`, this document MUST gain a row.
+  `.agent-src.uncondensed/rules/`, this document MUST gain a row.
 
 ## Source of tier data
 

package/docs/contracts/linter-structural-model.md

@@ -88,7 +88,7 @@ procedure → no warning under the new model. ✓ roadmap success criterion.
 success criterion.
 
 Of 13 commands ≥ 1000 words, only **2** lack a delegation signal —
-both are candidates for Phase 4.1 review (`compress.md`,
+both are candidates for Phase 4.1 review (`condense.md`,
 `project-analyze.md`; the latter has density 0.86, exempt under the
 density-AND-delegation gate).
 
@@ -115,7 +115,7 @@ Calibration sweep on the 2026-05-08 corpus (310 artifacts):
 Pass rate: 186 → 209 (`pass`); 124 → 101 (`pass_with_warnings`); 0
 errors. Each remaining warning is a genuine structural defect:
 
-- `compress.md` (1569 words, density 0.58, no delegation signal) —
+- `condense.md` (1569 words, density 0.58, no delegation signal) —
   inlined logic in a non-orchestrator command.
 - `artifact-drafting-protocol.md` rule (65 lines, density 0.37, no
   Iron-Law block) — prose-dominant long rule.

package/docs/contracts/load-context-budget-model.md

@@ -44,10 +44,10 @@ Where:
   (per [`load-context-schema.md`](load-context-schema.md)).
 - `transitive_closure` walks `load_context:` declarations on
   context files **up to depth 2** — see § Nesting cap below.
-- `RawSize` is the byte size of the compressed file
+- `RawSize` is the byte size of the condensed file
   (`.agent-src/...`), measured by `os.path.getsize()`. The
-  uncompressed source paths in frontmatter are mapped to their
-  compressed counterparts before sizing.
+  uncondensed source paths in frontmatter are mapped to their
+  condensed counterparts before sizing.
 - A context loaded by N always-rules counts **N times** (once per
   loading rule). Rationale: the always-budget protects context-window
   utilization at activation time; if rule A and rule B both fire on
@@ -138,7 +138,7 @@ the full `RawSize(X)` under Model (b). No `chars(X) / N` discount.
   has no measurable upside.
 - Phase 4c (shared-context discount) becomes a no-op under 3a.
   Phase 4 leverage shifts to 4a (demote), 4b (merge), and 4d
-  (hard-compress) — see `road-to-context-layer-maturity` Phase 4
+  (hard-condense) — see `road-to-context-layer-maturity` Phase 4
   inputs gate.
 
 **Reopener:** if a future inventory shows ≥ 3 shared-context loaders