@event4u/agent-config 3.2.0 → 4.1.0

package/docs/contracts/load-context-schema.md

@@ -33,10 +33,10 @@ load_context_eager:          # opt-in eager — auto-loaded on rule fire
 ---
 ```
 
-> **Logical names only.** The `.agent-src.uncompressed/` prefix is
+> **Logical names only.** The `.agent-src.uncondensed/` prefix is
 > rejected by the schema regex (`scripts/schemas/rule.schema.json`) and
-> by `scripts/lint_load_context.py`. The compress-time rewriter
-> (`scripts/compress.py::_rewrite_paths`) resolves logical names to the
+> by `scripts/lint_load_context.py`. The condense-time rewriter
+> (`scripts/condense.py::_rewrite_paths`) resolves logical names to the
 > deployment-correct relative path (e.g. `../contexts/<area>/<file>.md`
 > for a rule at `rules/<name>.md`). The full migration history lives
 > in the archived path-fixes roadmap under `agents/roadmaps/archive/`.
@@ -53,16 +53,16 @@ opt-in and budget-gated.
 ## Path rules
 
 - Logical names rooted at the source. The rewriter resolves them at
-  compress time.
+  condense time.
 - Paths MUST end in `.md`.
 - Allowed roots:
   - `contexts/<area>/<file>.md` — canonical logical name (resolves
-    against `.agent-src.uncompressed/`).
+    against `.agent-src.uncondensed/`).
   - `agents/settings/contexts/<file>.md` — project-local material (consumer
     repo only).
-  - `.agent-src/contexts/<file>.md` — compressed mirror; tolerated
+  - `.agent-src/contexts/<file>.md` — condensed mirror; tolerated
     defensively, not authored.
-- The `.agent-src.uncompressed/` prefix is **rejected** by the schema
+- The `.agent-src.uncondensed/` prefix is **rejected** by the schema
   regex and by `lint_load_context.py` with a remediation hint pointing
   at the canonical logical name.
 - A rule MAY reference contexts under either tree, but a package-shipped
@@ -144,10 +144,10 @@ definition it is not loaded into every turn.
 
 ## Public-vs-internal leak
 
-A rule shipped to consumers (`.agent-src.uncompressed/rules/`) may
+A rule shipped to consumers (`.agent-src.uncondensed/rules/`) may
 declare `load_context:` entries pointing at:
 
-- `.agent-src.uncompressed/contexts/` — public, OK.
+- `.agent-src.uncondensed/contexts/` — public, OK.
 - `agents/settings/contexts/` — package-internal, **lint warning** (the entry
   will not exist in consumer projects).
 
@@ -163,7 +163,7 @@ defined across both `load_context:` and `load_context_eager:` edges.
 
 ### Real consumer — `autonomous-execution`
 
-`.agent-src.uncompressed/rules/autonomous-execution.md` is the first
+`.agent-src.uncondensed/rules/autonomous-execution.md` is the first
 production rule to declare `load_context:`. Its frontmatter:
 
 ```yaml
@@ -173,9 +173,9 @@ description: "Deciding whether to ask the user or just act on a workflow step
 alwaysApply: false
 source: package
 load_context:
-  - .agent-src.uncompressed/contexts/execution/autonomy-detection.md
-  - .agent-src.uncompressed/contexts/execution/autonomy-mechanics.md
-  - .agent-src.uncompressed/contexts/execution/autonomy-examples.md
+  - .agent-src.uncondensed/contexts/execution/autonomy-detection.md
+  - .agent-src.uncondensed/contexts/execution/autonomy-mechanics.md
+  - .agent-src.uncondensed/contexts/execution/autonomy-examples.md
 ---
 ```
 

package/docs/contracts/local-analytics.md

@@ -1,3 +1,7 @@
+---
+stability: experimental
+---
+
 # Local Analytics Contract
 
 > **Status** · v0 / design · 2026-05-24. Phase 7 of the

package/docs/contracts/local-knowledge-ingestion.md

@@ -1,6 +1,6 @@
 ---
 stability: beta
-keep-beta-until: 2026-08-24
+keep-beta-until: 2026-08-23
 ---
 
 # Local knowledge ingestion contract

package/docs/contracts/mcp-beta-criteria.md

@@ -7,7 +7,7 @@ mcp_scope: lite
 
 > **Status:** Active · governs the `experimental → beta` promotion for
 > the MCP surface (`scripts/mcp_server/` local stdio kernel + the
-> hosted `workers/mcp/` bridge). Owned by Phase 3 of the
+> hosted `internal/workers/mcp/` bridge). Owned by Phase 3 of the
 > `road-to-surface-discipline` roadmap (see `agents/roadmaps/`).
 > Companion contract:
 > [`mcp-phase-1-scope.md`](mcp-phase-1-scope.md) (local) ·

package/docs/contracts/mcp-cloud-scope.md

@@ -5,7 +5,7 @@ mcp_scope: lite
 
 # MCP Server — Cloud Scope (A0-cloud Hard Contract)
 
-> **Status:** Active · covers `workers/mcp/` (TypeScript Cloudflare
+> **Status:** Active · covers `internal/workers/mcp/` (TypeScript Cloudflare
 > Worker bridge), MVP-1 surface. Extends — does **not** supersede —
 > [`mcp-phase-1-scope.md`](mcp-phase-1-scope.md), which retains
 > exclusive ownership of `scripts/mcp_server/` (local stdio).
@@ -15,7 +15,7 @@ mcp_scope: lite
 ## Purpose
 
 Locks the **execution-safety boundary** for the hosted MCP Worker. Any
-code under `workers/mcp/` must satisfy this contract verbatim. The
+code under `internal/workers/mcp/` must satisfy this contract verbatim. The
 local stdio kernel and the hosted Worker are two distinct surfaces; a
 deviation in one is **not** authorized by a precedent in the other.
 
@@ -45,8 +45,8 @@ prose-only.
   `list_*`, `read_resource_body`) that touch the content blob only.
 - **What it never does:** execute Python scripts, shell out, spawn
   runtimes, touch consumer FS, write to R2, mutate consumer state,
-  call upstream LLM APIs, or read `.agent-src.uncompressed/`.
-- **Owner code path:** `workers/mcp/` (TypeScript, Cloudflare Worker).
+  call upstream LLM APIs, or read `.agent-src.uncondensed/`.
+- **Owner code path:** `internal/workers/mcp/` (TypeScript, Cloudflare Worker).
   This contract is the normative spec.
 - **Auth model:** `public` (default) or `bearer-auth` (operator opt-in)
   per `## Auth surface`. HMAC and CF Access are declared but deferred.
@@ -120,7 +120,7 @@ prose-only.
   shape `releases/v<X.Y.Z>-<sha>/` (immutable per release). The blob
   bundles `.agent-src/skills/<name>/SKILL.md`,
   `.agent-src/commands/**/*.md`, and `docs/guidelines/` (the same
-  projection the local kernel reads). Never reads `.agent-src.uncompressed/`.
+  projection the local kernel reads). Never reads `.agent-src.uncondensed/`.
 - **Identity surface:** `serverInfo.version` reads from a Worker-
   bundled constant, `_meta.packageVersion` reads from a
   `wrangler.toml` env var, `_meta.skillSetSignature` reads from a
@@ -194,7 +194,7 @@ runtime mode switch.
   returns HTTP `401` with a JSON-RPC error envelope (code `-32001`,
   message `"Unauthorized"`) and the RFC 6750
   `WWW-Authenticate: Bearer realm="agent-config-mcp"` header.
-  Implementation: `workers/mcp/src/index.ts` § auth gate (the
+  Implementation: `internal/workers/mcp/src/index.ts` § auth gate (the
   `if (requiredToken) { … }` block).
 - **Liveness carve-out:** the `GET /` liveness probe is
   unauthenticated by design — health checks and `curl` smoke tests

package/docs/contracts/mcp-phase-1-scope.md

@@ -26,8 +26,8 @@ phase with its own design-call gate.
 - Transport: **stdio**. No SSE, no HTTP, no WebSocket.
 - MCP primitives: **`prompts/list`** + **`prompts/get`** — read-only.
 - Source data: **`.agent-src/skills/<name>/SKILL.md`** and
-  **`.agent-src/commands/**/*.md`** (compressed projections, never the
-  uncompressed source-of-truth tree).
+  **`.agent-src/commands/**/*.md`** (condensed projections, never the
+  uncondensed source-of-truth tree).
 - Loaded set (Phase 2): every well-formed skill + command under
   `.agent-src/` (Phase 1 hand-picked set retained as a smoke fixture
   in `prompts.py::PHASE_1_SKILLS`).
@@ -154,7 +154,7 @@ change invalidates it.
 
 ### F3 — Stdio Docker bundle
 
-`docker/mcp-server/Dockerfile` ships a stdio-only image. The contract:
+`internal/docker/mcp-server/Dockerfile` ships a stdio-only image. The contract:
 
 - **No HTTP / SSE listener** in the image. Stdio is the only wire.
 - The image embeds `scripts/mcp_server/`, the two tool dependencies

package/docs/contracts/mcp-registry-manifest.schema.json

@@ -52,7 +52,7 @@
                 "tools_count": {
                     "type": "integer",
                     "minimum": 0,
-                    "description": "Sourced from workers/mcp/content.json#/tool_catalog/tools. Hard-sourced — no fallback. R3 (discovery roadmap) is a hard prerequisite per the AI-Council external review."
+                    "description": "Sourced from internal/workers/mcp/content.json#/tool_catalog/tools. Hard-sourced — no fallback. R3 (discovery roadmap) is a hard prerequisite per the AI-Council external review."
                 },
                 "install_hint_stdio": { "type": "string", "minLength": 1 }
             }

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

@@ -47,7 +47,7 @@ keep-beta-until: 2026-08-14
 ## Glossary
 
 - **Side-effect** — `ro` (read-only) · `fs-write` (filesystem write) · `shell` (spawns processes).
-- **Transports** — `stdio` (`scripts/mcp_server/`) · `worker` (`workers/mcp/`). A tool may live on both.
+- **Transports** — `stdio` (`scripts/mcp_server/`) · `worker` (`internal/workers/mcp/`). A tool may live on both.
 - **Stub** — catalog-listed for discovery; returns the `not_implemented` envelope from
   [`mcp-tool-stub-envelope.md`](mcp-tool-stub-envelope.md) until promoted.
 

package/docs/contracts/mcp-tool-stub-envelope.md

@@ -20,7 +20,7 @@ a 500.
 ## Source of truth
 
 `scripts/mcp_server/consumer_tool_catalog.json` (schema_version 1).
-Both the stdio server and the Cloud Worker bundle (`workers/mcp/`,
+Both the stdio server and the Cloud Worker bundle (`internal/workers/mcp/`,
 packed by `scripts/pack_mcp_content.py`) read from this file. The
 manifest returned by `tools/list` is byte-identical apart from
 per-tool `implemented_on` metadata.

package/docs/contracts/measurement-baseline.md

@@ -5,7 +5,7 @@ stability: stable
 # Measurement baseline — contract
 
 > **Status:** locked 2026-05-16 · **Owner:** `step-4-measurement-and-benchmark.md`
-> · **Cited by:** every P2 enforcement roadmap (skill rationalization G0, north-star G1, compression default decision).
+> · **Cited by:** every P2 enforcement roadmap (skill rationalization G0, north-star G1, condensation default decision).
 
 Single source of truth for what `task bench` measures, what counts as
 drift, and what unblocks enforcement. Read this before pinning a number
@@ -24,7 +24,7 @@ Four axes, all numeric, all reproducible from the same input:
 
 Schemas: [`benchmark-report-schema.md`](benchmark-report-schema.md) ·
 [`benchmark-corpus-spec.md`](benchmark-corpus-spec.md). Reports land at
-`bench/reports/<utc-stamp>-<corpus>[-projection].{json,md}` —
+`internal/bench/reports/<utc-stamp>-<corpus>[-projection].{json,md}` —
 timestamped, never overwritten, content-addressed by run.
 
 ## Corpora — frozen for the soak window
@@ -36,7 +36,7 @@ timestamped, never overwritten, content-addressed by run.
 
 Total 26 prompts ≥ Acceptance Criteria floor of 25. Mid-window edits
 to either YAML restart the 60-day clock per
-[`compression-default-kill-criterion.md`](compression-default-kill-criterion.md) § 2.
+[`condensation-default-kill-criterion.md`](condensation-default-kill-criterion.md) § 2.
 
 ## What counts as drift
 
@@ -67,30 +67,30 @@ NO ANECDOTE, NO INDIVIDUAL REPORT, NO ROADMAP-SIDE OVERRIDE.
 [`scripts/bench_baseline_ready.py`](../../scripts/bench_baseline_ready.py)
 returns exit 0 iff both:
 
-1. **Wall-clock soak:** `today − bench/baseline-start.txt ≥ --min-days` (default 60)
-2. **Report density:** `bench/reports/*-<corpus>.json` count ≥ `--min-reports` (default 30)
+1. **Wall-clock soak:** `today − internal/bench/baseline-start.txt ≥ --min-days` (default 60)
+2. **Report density:** `internal/bench/reports/*-<corpus>.json` count ≥ `--min-reports` (default 30)
 
-Soak start anchored at [`bench/baseline-start.txt`](../../bench/baseline-start.txt)
+Soak start anchored at [`internal/bench/baseline-start.txt`](../../bench/baseline-start.txt)
 = **2026-05-16**. Earliest possible flip: **2026-07-15**, contingent
 on the 30-report floor.
 
 Downstream consumers:
 
 - ``step-99-north-star-restructure.md` § Acceptance G1` — reads this exit code.
-- [`compression-default-kill-criterion.md` § 3](compression-default-kill-criterion.md) — reads the decision table after baseline closes.
+- [`condensation-default-kill-criterion.md` § 3](condensation-default-kill-criterion.md) — reads the decision table after baseline closes.
 - ``step-2-skill-inventory-rationalization.md` § G0` — usage-data soak floor.
 
 ## What the closeout writes
 
 On baseline closure, the step-4 closeout writes the numeric verdict to
 [`docs/parity/bench.json`](../parity/bench.json) — frozen snapshot with
-the 30+ reports averaged, drift verdict, and the compression-default
+the 30+ reports averaged, drift verdict, and the condensation-default
 decision per the kill-criterion table. That file is the artefact every
-P2 roadmap reads — not the live `bench/reports/` directory.
+P2 roadmap reads — not the live `internal/bench/reports/` directory.
 
 ## Carve-outs
 
-- **Pricing freshness:** [`bench/pricing.yaml`](../../bench/pricing.yaml) rows must carry `sourced_on: YYYY-MM-DD`. Stale prices = stale numbers = no trust (ruflo "measured-vs-claimed" pattern).
+- **Pricing freshness:** [`internal/bench/pricing.yaml`](../../bench/pricing.yaml) rows must carry `sourced_on: YYYY-MM-DD`. Stale prices = stale numbers = no trust (ruflo "measured-vs-claimed" pattern).
 - **Subjective grading excluded:** quality scoring is mechanical via `quality_assertion`. No vibes.
 - **Cursor / Cline / Windsurf:** rules-only surfaces, no SKILL.md projection. `bench:projection` reports them as `not_applicable` — the gap is acknowledged, not silently dropped.
 
@@ -98,5 +98,5 @@ P2 roadmap reads — not the live `bench/reports/` directory.
 
 - [`benchmark-report-schema.md`](benchmark-report-schema.md) · per-report JSON schema
 - [`benchmark-corpus-spec.md`](benchmark-corpus-spec.md) · corpus YAML schema
-- [`compression-default-kill-criterion.md`](compression-default-kill-criterion.md) · decision table read by step-4 closeout
+- [`condensation-default-kill-criterion.md`](condensation-default-kill-criterion.md) · decision table read by step-4 closeout
 - `step-4-measurement-and-benchmark.md` · the owning roadmap

package/docs/contracts/mental-models.md

@@ -37,7 +37,7 @@ decisions. The expensive part is identifying which "principle" is
 actually load-bearing vs. inherited belief; the cheap part is the
 re-derivation. Use when an inherited approach feels stale and you
 suspect the real constraint moved.
-*Cited by:* `.agent-src.uncompressed/skills/improve-before-implement/`
+*Cited by:* `.agent-src.uncondensed/skills/improve-before-implement/`
 (challenges weak requirements before code is written).
 
 ### 2. Jobs-to-be-Done (JTBD)
@@ -47,7 +47,7 @@ the job is the situation × motivation × expected outcome, not the
 demographic. The unit of analysis is the **switch event** — what
 caused them to fire the previous solution. JTBD reframes feature
 requests as evidence of an unmet job, not feature gaps.
-*Cited by:* `.agent-src.uncompressed/skills/po-discovery/`
+*Cited by:* `.agent-src.uncondensed/skills/po-discovery/`
 (reframes fuzzy product asks via job-shape).
 
 ### 3. Pareto principle (80/20)
@@ -56,7 +56,7 @@ Roughly 80% of effects come from 20% of causes. The lift is in
 **identifying** the 20% — which user segment, which test failure,
 which N+1 query — not in re-stating the ratio. Anti-pattern: using
 80/20 as permission to ignore the long tail without measuring it.
-*Cited by:* `.agent-src.uncompressed/skills/performance-analysis/`
+*Cited by:* `.agent-src.uncondensed/skills/performance-analysis/`
 (N+1 detection prioritizes the 20% of queries causing 80% of latency).
 
 ### 4. Second-order thinking
@@ -66,7 +66,7 @@ what looks best now; second-order weighs the consequences of the
 consequences. Most "obvious" decisions die at second-order — the
 optimization that ships now creates the maintenance debt that kills
 velocity in 6 months.
-*Cited by:* `.agent-src.uncompressed/skills/adversarial-review/`
+*Cited by:* `.agent-src.uncondensed/skills/adversarial-review/`
 (stress-tests a plan by walking past the immediate verdict).
 
 ### 5. Opportunity cost
@@ -76,7 +76,7 @@ not pick**, not the dollar / time spent. A 2-week feature is not
 "2 weeks expensive" — it is the highest-value 2-week feature you
 chose not to ship instead. Naming the alternative makes the cost
 legible; pretending there isn't one is the failure mode.
-*Cited by:* `.agent-src.uncompressed/skills/rice-prioritization/`
+*Cited by:* `.agent-src.uncondensed/skills/rice-prioritization/`
 (scores compete for capacity; non-shipped items are the cost basis).
 
 ### 6. Theory of constraints
@@ -86,7 +86,7 @@ Improving any non-constraint resource is local optimization with
 zero system effect — usually negative, since it loads the actual
 constraint harder. The discipline: identify, exploit, subordinate,
 elevate, then find the next constraint.
-*Cited by:* `.agent-src.uncompressed/skills/funnel-analysis/`
+*Cited by:* `.agent-src.uncondensed/skills/funnel-analysis/`
 (identifies the single funnel stage that bounds conversion throughput).
 
 ### 7. MVP (Minimum Viable Product)
@@ -97,7 +97,7 @@ junior-grade product. The trap is shipping an MVP that cannot
 distinguish "user behavior validates the hypothesis" from "user
 behavior was driven by something else"; that is just a small
 product.
-*Cited by:* `.agent-src.uncompressed/skills/po-discovery/`
+*Cited by:* `.agent-src.uncondensed/skills/po-discovery/`
 (scopes a discovery slice that produces a learning, not a feature).
 
 ### 8. Build-Measure-Learn
@@ -107,7 +107,7 @@ to persevere or pivot. The skill is in **shortening the loop** —
 weeks beat months because months let teams rationalize a failed
 hypothesis. The loop is the artefact; any individual cycle is just
 one iteration.
-*Cited by:* `.agent-src.uncompressed/skills/test-driven-development/`
+*Cited by:* `.agent-src.uncondensed/skills/test-driven-development/`
 (the build-measure-learn loop applied to one function at a time).
 
 ### 9. Hypothesis-driven development
@@ -116,7 +116,7 @@ State the hypothesis as a falsifiable sentence with a metric and a
 threshold **before** writing the code. "If we do X, metric Y will
 move by Z." Without the threshold, the team will declare any
 movement victory. With it, the team learns from the misses.
-*Cited by:* `.agent-src.uncompressed/skills/project-analysis-hypothesis-driven/`
+*Cited by:* `.agent-src.uncondensed/skills/project-analysis-hypothesis-driven/`
 (competing hypotheses + validation loops + evidence-based conclusions).
 
 ### 10. Reversible vs. irreversible decisions
@@ -126,7 +126,7 @@ plus speed. The bias under uncertainty: shipping a reversible
 decision early is almost always cheaper than the meeting required
 to decide. The skill is recognizing irreversibility — usually data
 shape, public API surface, or hiring.
-*Cited by:* `.agent-src.uncompressed/skills/decision-record/`
+*Cited by:* `.agent-src.uncondensed/skills/decision-record/`
 (records the reversal-criteria so the irreversibility verdict is auditable).
 
 ### 11. DX as first-class concern
@@ -136,7 +136,7 @@ a polish task. Slow tests, fragile local setup, and surprising tool
 output compound — every developer pays the tax every day. Treat DX
 issues like user-facing bugs, with severity and SLA. The compounding
 math makes "fix it later" almost always wrong.
-*Cited by:* `.agent-src.uncompressed/skills/test-performance/`
+*Cited by:* `.agent-src.uncondensed/skills/test-performance/`
 (test-suite latency is a developer-facing metric, optimized as such).
 
 ### 12. Conway's Law
@@ -145,7 +145,7 @@ The systems an organization builds mirror its communication structure.
 Re-orgs propagate to architecture; architecture changes that fight the
 org chart fail. The lever is bidirectional: pick the architecture you
 want, then engineer the communication paths that produce it.
-*Cited by:* `.agent-src.uncompressed/skills/api-design/`
+*Cited by:* `.agent-src.uncondensed/skills/api-design/`
 (bounded-context choices follow team boundaries, not the other way around).
 
 ### 13. Occam's Razor
@@ -155,7 +155,7 @@ that introduces the fewest new entities. In debugging, the boring
 explanation (typo, off-by-one, stale cache) is usually correct. The
 trap is **assuming** instead of **falsifying** — Occam suggests
 order of investigation, not a verdict.
-*Cited by:* `.agent-src.uncompressed/skills/systematic-debugging/`
+*Cited by:* `.agent-src.uncondensed/skills/systematic-debugging/`
 (reproduce → isolate → hypothesize, simplest hypothesis first).
 
 ### 14. Meadows leverage points
@@ -165,7 +165,7 @@ system are paradigm shifts, then goals, then rules — far above
 parameter tweaks. Most "improvement" effort fights parameters
 (numbers, delays) at the bottom of the ranking. Climb the ranking
 before optimizing.
-*Cited by:* `.agent-src.uncompressed/skills/architecture-review-lens/`
+*Cited by:* `.agent-src.uncondensed/skills/architecture-review-lens/`
 (boundary / dependency-direction issues are higher-leverage than tweaks).
 
 ### 15. Signal vs. noise
@@ -175,7 +175,7 @@ A change of size N is meaningful only if N exceeds the noise floor
 for that metric × that horizon. The discipline: estimate the noise
 band first, then evaluate the change. Without the noise band, every
 movement looks like a trend.
-*Cited by:* `.agent-src.uncompressed/skills/funnel-analysis/`
+*Cited by:* `.agent-src.uncondensed/skills/funnel-analysis/`
 (stage-to-stage drop is read against the typical week-on-week noise).
 
 ### 16. Leading vs. lagging indicators
@@ -185,7 +185,7 @@ late. Leading indicators (activation events, repeat-use, support
 volume) are noisy and early. Operating on lagging alone means the
 team learns about problems after they cost money. Pair them: lagging
 is the score, leading is the steering wheel.
-*Cited by:* `.agent-src.uncompressed/skills/dashboard-design/`
+*Cited by:* `.agent-src.uncondensed/skills/dashboard-design/`
 (RED / USE / Golden Signals split leading from lagging explicitly).
 
 ### 17. Churn as health metric
@@ -195,7 +195,7 @@ delivers ongoing value. A flat retention tail means the product
 works for the survivors; a sliding tail means the underlying job is
 not getting done. Churn is upstream of CAC payback — fix it first,
 then scale.
-*Cited by:* `.agent-src.uncompressed/skills/funnel-analysis/`
+*Cited by:* `.agent-src.uncondensed/skills/funnel-analysis/`
 (retention bend distinguishes activation problems from product-fit).
 
 ### 18. Pull vs. push systems
@@ -205,7 +205,7 @@ start work when upstream capacity is free. Push optimizes individual
 utilization, pull optimizes flow. Most software teams claim pull and
 operate push (queues filling up, sprints overcommitted, WIP
 unmanaged). The fix is WIP limits, not motivation.
-*Cited by:* `.agent-src.uncompressed/skills/laravel-horizon/`
+*Cited by:* `.agent-src.uncondensed/skills/laravel-horizon/`
 (queue-balance strategies are pull-vs-push policy in concrete form).
 
 ### 19. Shift-left
@@ -215,7 +215,7 @@ lifecycle — to the developer's machine, the PR, the design — where
 the cost of fixing is order-of-magnitude lower. The trade-off:
 shift-left adds friction at the front; the math holds when defect
 escape rate drops faster than the friction cost.
-*Cited by:* `.agent-src.uncompressed/skills/threat-modeling/`
+*Cited by:* `.agent-src.uncondensed/skills/threat-modeling/`
 (threats enumerated before implementation, not after pen-test).
 
 ### 20. Latency vs. throughput
@@ -225,7 +225,7 @@ not implementation-detail. Batch processing trades latency for
 throughput; real-time pipelines trade throughput for latency. The
 mistake is optimizing without naming which one matters for the user
 job at hand.
-*Cited by:* `.agent-src.uncompressed/skills/database/`
+*Cited by:* `.agent-src.uncondensed/skills/database/`
 (index strategy and query batching surface the trade-off explicitly).
 
 ### 21. Trust boundaries
@@ -235,7 +235,7 @@ trusted: client → server, tenant A → tenant B, free tier → paid
 tier, public endpoint → internal service. Threats enter at boundary
 crossings; defense lives at the crossing, not deeper. Drawing the
 boundary correctly is half the security work.
-*Cited by:* `.agent-src.uncompressed/skills/threat-modeling/`
+*Cited by:* `.agent-src.uncondensed/skills/threat-modeling/`
 (produces trust boundaries + abuse cases mapped to files).
 
 ### 22. Defense in depth
@@ -245,7 +245,7 @@ rules, environment hardening, and instrumentation so a bypass at
 one layer is caught at the next. The trap is mistaking redundancy
 for security theatre — each layer must have an independent failure
 mode, not a copy of the previous one.
-*Cited by:* `.agent-src.uncompressed/skills/defense-in-depth/`
+*Cited by:* `.agent-src.uncondensed/skills/defense-in-depth/`
 (turns local fix into structural one across four guard layers).
 
 ### 23. Blast radius
@@ -255,7 +255,7 @@ consumer, queue worker, API client, migration, and test that the
 change touches. The radius is the work; the diff is the artefact.
 Underestimating radius is the failure mode that breaks production
 when the change "looked small".
-*Cited by:* `.agent-src.uncompressed/skills/blast-radius-analyzer/`
+*Cited by:* `.agent-src.uncondensed/skills/blast-radius-analyzer/`
 (file:line citation per dependency, BEFORE the edit).
 
 ### 24. Iron triangle (scope / time / quality)
@@ -264,7 +264,7 @@ Scope, time, and quality are coupled — fix two, the third moves.
 Pretending to fix all three is how teams ship at low quality and
 call it on-time. The honest move is naming which two are fixed and
 which one absorbs the variance, BEFORE the work starts.
-*Cited by:* `.agent-src.uncompressed/skills/refine-ticket/`
+*Cited by:* `.agent-src.uncondensed/skills/refine-ticket/`
 (AC sharpening forces explicit scope decisions before estimation).
 
 ### 25. Definition of Done
@@ -274,7 +274,7 @@ work — tests, docs, deployment, comms. Without one, every team
 member ships their personal threshold and disputes downstream. The
 discipline is making it visible, agreed, and consistently applied —
 not the specific items on it.
-*Cited by:* `.agent-src.uncompressed/skills/verify-completion-evidence/`
+*Cited by:* `.agent-src.uncondensed/skills/verify-completion-evidence/`
 (fresh evidence is required before any "done" claim).
 
 ### 26. Postmortem-driven learning
@@ -284,7 +284,7 @@ the team that hides the incident. Blameless postmortems separate
 contribution from blame, surface systemic causes, and produce
 mitigations that reduce future incident rate — not just the count
 of one-off fixes.
-*Cited by:* `.agent-src.uncompressed/skills/incident-commander/`
+*Cited by:* `.agent-src.uncondensed/skills/incident-commander/`
 (severity framing + comms cadence + post-mortem skeleton).
 
 ### 27. Tech debt as interest
@@ -294,7 +294,7 @@ payment (the ongoing tax on velocity). Carrying the debt is the
 right call when the principal is repayable and the interest is
 small; the failure is treating ongoing high-interest debt as a
 fixed cost. Track it like a balance sheet.
-*Cited by:* `.agent-src.uncompressed/skills/tech-debt-tracker/`
+*Cited by:* `.agent-src.uncondensed/skills/tech-debt-tracker/`
 (interest-vs-principal framing, prioritisation by carrying cost).
 
 ### 28. Mise en place
@@ -304,7 +304,7 @@ before the cooking step starts. Switching between prep and cook is
 where errors enter. In software, the analogue is staged commits,
 prepared test fixtures, and decisions locked before implementation.
 The discipline is the savings, not the metaphor.
-*Cited by:* `.agent-src.uncompressed/skills/existing-ui-audit/`
+*Cited by:* `.agent-src.uncondensed/skills/existing-ui-audit/`
 (inventory before any non-trivial UI edit, hard gate).
 
 ### 29. Premortem
@@ -314,7 +314,7 @@ risks the team already knows but has not voiced. The trick is the
 past-tense framing; "what could go wrong" surfaces less than "it
 failed, what happened". Cheap; high signal-to-noise; the residual
 output is a risk register the team actually defends.
-*Cited by:* `.agent-src.uncompressed/skills/risk-officer/`
+*Cited by:* `.agent-src.uncondensed/skills/risk-officer/`
 (blast-radius framing, mitigations, residual-risk verdict pre-commit).
 
 ### 30. Inversion
@@ -324,7 +324,7 @@ guarantee failure at X?" — then avoid that. Inversion exposes the
 non-obvious failure modes that direct planning misses, especially
 in security, ops, and people problems where the failure surface is
 larger than the success surface.
-*Cited by:* `.agent-src.uncompressed/skills/adversarial-review/`
+*Cited by:* `.agent-src.uncondensed/skills/adversarial-review/`
 (devil's-advocate stress-test poking holes in a plan).
 
 ## Adding or removing a model

package/docs/contracts/multi-tool-projection-fidelity.md

@@ -8,11 +8,11 @@ keep-beta-until: 2026-08-13
 **Status:** beta · **Phase 4 of the `step-1-v2-feedback-followup`
 roadmap** (under `agents/roadmaps/`).
 
-Names the **per-tool guarantees** the projection pipeline (`scripts/compress.py --sync` + `scripts/compress.py --generate-tools`) actually delivers. Byte-equivalence is not behaviour-fidelity — each consumer tool has its own frontmatter grammar, its own activation model, and its own surface for skills / rules / commands.
+Names the **per-tool guarantees** the projection pipeline (`scripts/condense.py --sync` + `scripts/condense.py --generate-tools`) actually delivers. Byte-equivalence is not behaviour-fidelity — each consumer tool has its own frontmatter grammar, its own activation model, and its own surface for skills / rules / commands.
 
 ## Source of truth
 
-Every projection starts from `.agent-src/` (compressed) which is generated from `.agent-src.uncompressed/`. The projection layer **never** writes to source; it only reads.
+Every projection starts from `.agent-src/` (condensed) which is generated from `.agent-src.uncondensed/`. The projection layer **never** writes to source; it only reads.
 
 ## Per-tool projection map
 
@@ -96,7 +96,7 @@ These are **architectural facts**, not regressions. They are documented so insta
 2. **Windsurf single-file (`.windsurfrules`) strips per-rule frontmatter.** Legacy compatibility surface. The new `.windsurf/rules/*.md` per-rule files preserve the full frontmatter — consumers should prefer those.
 3. **Skills do not project to Cursor / Windsurf / Cline / Gemini / Copilot.** These tools have no native skill loader. Skill content reaches consumers indirectly via rule bodies and the `AGENTS.md` catalogue.
 4. **Augment historically did not load symlinked rules.** Default is to **copy** rules into `.augment/rules/`. Opt into symlinks via `augment.rules_use_symlinks: true` in `.agent-settings.yml`.
-5. **`task generate-tools` does not refresh `.augment/rules/`.** Only `task sync` (== `scripts/compress.py --sync`) copies rules into the Augment tree. Investigators who edit a rule, run only `generate-tools`, and then `ls .augment/rules/` will see stale state.
+5. **`task generate-tools` does not refresh `.augment/rules/`.** Only `task sync` (== `scripts/condense.py --sync`) copies rules into the Augment tree. Investigators who edit a rule, run only `generate-tools`, and then `ls .augment/rules/` will see stale state.
 
 ## Acceptance criteria for this contract
 
@@ -108,7 +108,7 @@ These are **architectural facts**, not regressions. They are documented so insta
 
 ## Related
 
-- [`source-projection`](../architecture/source-projection.md) — pipeline A (source compression)
+- [`source-projection`](../architecture/source-projection.md) — pipeline A (source condensation)
 - [`augment-projection`](../architecture/augment-projection.md) — pipeline B (Augment-specific)
 - [`multi-tool-projection`](../architecture/multi-tool-projection.md) — pipeline C (the per-tool emitters)
 - [`rule-router`](rule-router.md) — the `triggers:` / `routes_to:` grammar this contract pins

package/docs/contracts/namespace.md

@@ -59,10 +59,10 @@ skipped by the linter.
 
 | Type | Source path | Naming nuance |
 |---|---|---|
-| Skill | `.agent-src.uncompressed/skills/<name>/SKILL.md` | Directory name == frontmatter `name`. |
-| Rule | `.agent-src.uncompressed/rules/<name>.md` | Filename stem == frontmatter `id` (when present). |
-| Command | `.agent-src.uncompressed/commands/<name>.md` or `<group>/<verb>.md` | Slash-command invocation `<name>` or `<group>:<verb>`. |
-| Persona | `.agent-src.uncompressed/personas/<name>.md` | Cited from skill frontmatter `personas:` list. |
+| Skill | `.agent-src.uncondensed/skills/<name>/SKILL.md` | Directory name == frontmatter `name`. |
+| Rule | `.agent-src.uncondensed/rules/<name>.md` | Filename stem == frontmatter `id` (when present). |
+| Command | `.agent-src.uncondensed/commands/<name>.md` or `<group>/<verb>.md` | Slash-command invocation `<name>` or `<group>:<verb>`. |
+| Persona | `.agent-src.uncondensed/personas/<name>.md` | Cited from skill frontmatter `personas:` list. |
 
 Sub-namespacing (`commit/in-chunks.md` →  `/commit:in-chunks`) uses
 the same charset rules per segment; the joining colon is implicit.

package/docs/contracts/orchestration-dsl-v1.md

@@ -13,7 +13,7 @@ that re-runs the same step sequence with the same inputs.
 **Scope.** Defines the file location, top-level shape, step kinds,
 input / output wiring, and the linter contract. Does **not** define
 the runtime semantics of each step kind — those live in the
-[`/orchestrate`](../../.agent-src.uncompressed/commands/orchestrate.md)
+[`/orchestrate`](../../.agent-src.uncondensed/commands/orchestrate.md)
 command and the `work_engine` directive modules it delegates to.
 
 Last refreshed: 2026-05-11.
@@ -95,10 +95,10 @@ outputs:
 
 | `kind` | `ref` resolves to | Runtime |
 |---|---|---|
-| `skill` | `.agent-src.uncompressed/skills/<ref>/SKILL.md` | Dispatched via `work_engine` directive matching the skill's domain. |
-| `command` | `.agent-src.uncompressed/commands/<ref>.md` | Same dispatch path the slash-command takes when typed by the user. |
-| `persona` | `.agent-src.uncompressed/personas/<ref>.md` | Sets `roles.active_role` for the next dependent step; does not produce its own output. |
-| `subagent` | `subagent-orchestration` mode name | Spawned per [`subagent-orchestration`](../../.agent-src.uncompressed/skills/subagent-orchestration/SKILL.md). |
+| `skill` | `.agent-src.uncondensed/skills/<ref>/SKILL.md` | Dispatched via `work_engine` directive matching the skill's domain. |
+| `command` | `.agent-src.uncondensed/commands/<ref>.md` | Same dispatch path the slash-command takes when typed by the user. |
+| `persona` | `.agent-src.uncondensed/personas/<ref>.md` | Sets `roles.active_role` for the next dependent step; does not produce its own output. |
+| `subagent` | `subagent-orchestration` mode name | Spawned per [`subagent-orchestration`](../../.agent-src.uncondensed/skills/subagent-orchestration/SKILL.md). |
 
 ## Interpolation
 
@@ -147,7 +147,7 @@ majors.
 
 ## Cross-references
 
-- Command surface: [`/orchestrate`](../../.agent-src.uncompressed/commands/orchestrate.md).
+- Command surface: [`/orchestrate`](../../.agent-src.uncondensed/commands/orchestrate.md).
 - Linter: [`lint_orchestration_dsl.py`](../../scripts/lint_orchestration_dsl.py).
 - Runtime dispatcher precedent: [`implement-ticket-flow.md`](implement-ticket-flow.md).
-- Subagent runtime: [`subagent-orchestration`](../../.agent-src.uncompressed/skills/subagent-orchestration/SKILL.md).
+- Subagent runtime: [`subagent-orchestration`](../../.agent-src.uncondensed/skills/subagent-orchestration/SKILL.md).