@event4u/agent-config 3.3.0 → 4.2.0

package/docs/contracts/ci-green-floor.md

@@ -0,0 +1,141 @@
+---
+stability: beta
+keep-beta-until: 2026-08-26
+roadmap_ref: road-to-adoption-proof-and-ci-green.md
+---
+
+# CI Green Floor
+
+> **Status** · v0 / beta · 2026-05-26. Phase A Step 4 of
+> [`road-to-adoption-proof-and-ci-green.md`](../../agents/roadmaps/road-to-adoption-proof-and-ci-green.md).
+> Defines what counts as a **blocking** CI failure (must be green
+> before merge) vs. an **advisory** signal (visible but not
+> merge-blocking), and the freeze rule that fires when main goes
+> red on a required check.
+
+## The Iron Law
+
+```
+ANY REQUIRED-CHECK RED ON `main` FREEZES SUBSEQUENT PR MERGES
+UNTIL THE RED IS CLEARED. ADVISORY REDS NEVER FREEZE.
+PHANTOM 0-JOB RUNS ARE ADVISORY BY CONSTRUCTION.
+```
+
+The required-check set is the source of truth for what blocks. Every
+other workflow is advisory until it earns inclusion.
+
+## Three tiers — blocking · advisory · phantom
+
+| Tier | Definition | Effect on merge | Effect on freeze |
+|---|---|---|---|
+| **Blocking** | Listed in [`branch-protection-policy.md`](branch-protection-policy.md) § Per-PR-shape required-check matrix for the current PR shape. | Red blocks the PR merge. | Red on `main` (post-merge) triggers a freeze tag — see [Freeze rule](#freeze-rule-the-mechanics). |
+| **Advisory** | Workflow ships in `.github/workflows/` but is NOT listed in the required-check matrix (e.g. `bench-drift.yml`, `cloud-release.yml`, `deploy-mcp-worker.yml`). | Red is visible on the PR page but does not block merge. | Red on `main` does not freeze. |
+| **Phantom** | Workflow registers a run with `Jobs: 0` and `Conclusion: failure` — typically `workflow_dispatch`-only workflows that GitHub's check-suite still registers on push. | Filtered out of every status query. | Never. |
+
+`task ci:status` (Phase A Step 6) is the canonical filter: it
+queries `gh run list`, drops Jobs-0 phantoms, then asserts the
+required-check set has zero non-success conclusions for the
+current HEAD SHA.
+
+## Blocking set — anchored to `branch-protection-policy.md`
+
+The blocking set is defined per PR shape (feature / release /
+docs-only) in [`branch-protection-policy.md`](branch-protection-policy.md)
+§ Per-PR-shape required-check matrix. The summary for `main`:
+
+- **Feature PR set** — `Consistency`, `Smoke Contracts`, `Skill Lint`,
+  `Tests` (every matrix entry), `Public Install Smoke`.
+- **Release PR set** — `Consistency`, `Smoke Contracts`, three
+  `Release Validation` jobs.
+- **Docs-only PR set** — `Consistency`, `Smoke Contracts`.
+
+`task ci:status` reads the same set when run with `--strict` (Phase
+A Step 6); the set is single-sourced from `scripts/ci_status.py`.
+
+## Advisory list — explicit non-blockers
+
+These workflows MAY fail without blocking merges. Each carries a
+documented rationale (link to the file header or roadmap step) so
+"advisory" never silently expands.
+
+| Workflow | Rationale | Promotion criterion |
+|---|---|---|
+| `bench-drift.yml` | Performance bench — informational only until the bench-stability roadmap completes. | Three consecutive green weekly runs after the bench is stabilised. |
+| `cloud-release.yml` | Release artefact publish — Hard-Floor adjacent fix pending. See [`02-deployment-failures.md`](../../agents/evidence/audits/2026-05-ci-triage/02-deployment-failures.md) § Finding 1. | Maintainer ships the rate-limit fix; smoke probe stays green for two consecutive releases. |
+| `deploy-mcp-worker.yml` | MCP worker deploy — auth contract regression pending. See [`02-deployment-failures.md`](../../agents/evidence/audits/2026-05-ci-triage/02-deployment-failures.md) § Finding 2. | Maintainer aligns the smoke probe with the Worker auth gate; passes for two consecutive deploys. |
+| `sync-visibility.yml` | `workflow_dispatch`-only mutator. GitHub registers a phantom 0-job failure on every push to main — documented in the workflow header. **Phantom, not advisory** — `task ci:status` filters it. | n/a; the filter is the fix. |
+| `check-visibility-drift.yml` | PR-paths + schedule + dispatch. Same GitHub Actions quirk produces phantom 0-job failures on push to main. **Phantom, not advisory.** | n/a; the filter is the fix. |
+
+Adding a row here is a maintainer-level call: the rationale must
+exist, and the promotion criterion must be writable.
+
+## Phantom 0-job runs — the filter
+
+A "phantom" run is one where:
+
+1. The workflow registers a check-suite entry on the commit, AND
+2. The run has `Jobs: 0` (no job actually executed), AND
+3. The conclusion is `failure`.
+
+This is a documented GitHub Actions quirk for `workflow_dispatch`-only
+workflows and for path-filtered workflows whose paths do not match
+the push diff. Removing the `push:` trigger does NOT eliminate the
+phantom; the check-suite still registers.
+
+`task ci:status` and `scripts/ci_status.py` drop any run with
+`Jobs: 0` from the tally before computing pass/fail. The phantom
+is visible in the GitHub UI but invisible to the gate.
+
+## Freeze rule — the mechanics
+
+When a commit lands on `main` and any required-check workflow turns
+red within ~5 minutes (the standard required-check window):
+
+1. The required-check status remains red on the merge commit.
+2. Subsequent PRs targeting `main` see the same required-check set
+   evaluated against the PR's head SHA. If the same workflow fails
+   again on the PR head, the PR is blocked.
+3. The maintainer either (a) reverts the offending commit, or (b)
+   ships a fix-forward PR that turns the required check green. No
+   PR merges meanwhile.
+
+The freeze is therefore behavioural, not enforced via a separate
+"freeze-mode" workflow — branch protection already does the
+gating. `freeze-guard.yml` ([source](../../.github/workflows/freeze-guard.yml))
+is a **different** mechanism: it locks the behavioural baseline of
+the work-engine via golden-transcript diff, and is a required check
+in the engine-path subset (not the universal floor). Both apply
+together; the names don't conflict.
+
+## What this contract is not
+
+- **Not a list of "all green workflows".** Advisory and phantom
+  reds are routine and do not constitute a violation.
+- **Not a guarantee against false-greens.** A workflow that ran
+  but tested nothing meaningful can still report success; the
+  contract only governs how red signals are routed.
+- **Not a license to add workflows to the blocking set silently.**
+  Promotion to blocking is a `branch-protection-policy.md` edit
+  with a written rationale and a maintainer review.
+
+## Re-audit cadence
+
+Re-audit on each of:
+
+- A new workflow lands in `.github/workflows/`.
+- A workflow is promoted from advisory to blocking (or vice versa)
+  in `branch-protection-policy.md`.
+- A new phantom-failure class is observed (e.g. GitHub Actions ships
+  behaviour the filter doesn't catch).
+- Quarterly review (Phase C of `road-to-ci-budget-and-cost.md` or
+  its successor).
+
+## See also
+
+- [`branch-protection-policy.md`](branch-protection-policy.md) —
+  the required-check matrix per PR shape.
+- [`release-pr-gating.md`](release-pr-gating.md) — release-PR shape
+  detection + cut surface.
+- [`../../agents/evidence/audits/2026-05-ci-triage/01-red-workflows.md`](../../agents/evidence/audits/2026-05-ci-triage/01-red-workflows.md)
+  — current red-workflow inventory.
+- `AGENTS.md` § Emergency triage — root-of-repo pointer for agents.

package/docs/contracts/command-clusters.md

@@ -56,7 +56,7 @@ collapses 26 atomics → 11 sub-command clusters. Sub-commands use
 colon syntax (`/cluster:sub`) so Claude Code's command palette can
 autocomplete them. The standalone `/review` surface that mirrors
 `judge solo` lives at
-[`commands/review-changes.md`](../../.agent-src.uncompressed/commands/review-changes.md).
+[`commands/review-changes.md`](../../.agent-src.uncondensed/commands/review-changes.md).
 
 ## Cluster depth and sub-command naming
 
@@ -98,12 +98,12 @@ every new sub-command added to an existing cluster.
    `/<cluster> <sub>` is a first-class equivalent and routes to the
    same dispatcher; it must keep working. Autocompletion-aware UIs
    surface the colon form because it stays a single token. Full
-   semantics: [`slash-command-routing-policy-mechanics.md`](../../.agent-src.uncompressed/contexts/communication/rules-auto/slash-command-routing-policy-mechanics.md)
+   semantics: [`slash-command-routing-policy-mechanics.md`](../../.agent-src.uncondensed/contexts/communication/rules-auto/slash-command-routing-policy-mechanics.md)
    § Routing semantics.
 
 ## Frontmatter contract
 
-A new command file under `.agent-src.uncompressed/commands/` MUST
+A new command file under `.agent-src.uncondensed/commands/` MUST
 declare `cluster:` in its frontmatter, pointing to one of the locked
 clusters above:
 
@@ -133,7 +133,7 @@ here so future lens additions follow the same shape.
   (resolve target + capture `original_ask`), Step 2 (configure check +
   price-table freshness), Step 3 (cost confirmation), Step 4 (run CLI),
   Step 5 / 5a / 5b (render → critical-evaluation lens → user options),
-  Step 6 (hard floor). See [`commands/council.md` → `## Architecture`](../../.agent-src.uncompressed/commands/council.md).
+  Step 6 (hard floor). See [`commands/council.md` → `## Architecture`](../../.agent-src.uncondensed/commands/council.md).
 - **Wrappers:** `/council pr` · `/council design` · `/council optimize`
   resolve lens-specific input (PR target / design artefact / optimization
   target + metric), capture a wrapper-specific `original_ask`, then
@@ -182,7 +182,7 @@ has fewer findings.
 
 A shim is a one-file stub that:
 
-1. Keeps the old command slug in `.agent-src.uncompressed/commands/`.
+1. Keeps the old command slug in `.agent-src.uncondensed/commands/`.
 2. Declares `superseded_by:` in frontmatter pointing to the new
    cluster command (e.g. `superseded_by: fix ci`).
 3. Declares `deprecated_in:` with the release version (e.g.
@@ -299,4 +299,4 @@ A command that fails either floor drops to **Tier-1** at the next minor release;
 - [`docs/contracts/STABILITY.md`](STABILITY.md) — `beta` level rules apply.
 - [`docs/contracts/command-surface-tiers.md`](command-surface-tiers.md) — what each tier means and what `--help` surfaces.
 - [`docs/contracts/command-taxonomy.md`](command-taxonomy.md) — profile axis (discoverability) layered on top of this verb axis (invocation).
-- [`.agent-src.uncompressed/contexts/contracts/artifact-engagement-flow.md`](../../.agent-src.uncompressed/contexts/contracts/artifact-engagement-flow.md) — sibling telemetry surface; same privacy floor and four-layer enforcement model.
+- [`.agent-src.uncondensed/contexts/contracts/artifact-engagement-flow.md`](../../.agent-src.uncondensed/contexts/contracts/artifact-engagement-flow.md) — sibling telemetry surface; same privacy floor and four-layer enforcement model.

package/docs/contracts/command-surface-tiers.md

@@ -10,7 +10,7 @@ keep-beta-until: 2026-08-12
 > command surfaces this package ships:
 >
 > - **CLI commands** rendered by `./agent-config --help`.
-> - **Slash commands** under `.agent-src.uncompressed/commands/**`.
+> - **Slash commands** under `.agent-src.uncondensed/commands/**`.
 >
 > Per Phase 4 of the distribution-maturity roadmap (see
 > `agents/roadmaps/` for current status).
@@ -147,7 +147,7 @@ the help text groups commands under `## Tier 0`, `## Tier 1`,
 
 `scripts/lint_command_tiers.py` enforces:
 
-1. Every file under `.agent-src.uncompressed/commands/**.md` has
+1. Every file under `.agent-src.uncondensed/commands/**.md` has
    a `tier:` frontmatter key whose value is `0`, `1`, or `2`.
 2. Every command listed under `## Tier 0` / `## Tier 1` /
    `## Tier 2` in this contract resolves to a real command file or

package/docs/contracts/command-taxonomy.md

@@ -33,7 +33,7 @@ single-source.
 ### Profile membership
 
 A command appears in a profile's `commands_hint` (in
-`.agent-src.uncompressed/profiles/<id>.yml`) iff **all** hold:
+`.agent-src.uncondensed/profiles/<id>.yml`) iff **all** hold:
 
 1. **First-week reach.** A user of that profile will reach for this
    command within their first five sessions without being told.
@@ -92,7 +92,7 @@ Three surfaces consume this contract:
 |---|---|---|
 | **README** | `README.md` § "Six entry paths" | Per-profile `commands_hint` (max 5) rendered as the first-commands list per profile block |
 | **Catalog** | `docs/catalog.md` | All commands grouped by verb-cluster (primary axis), with a per-command `profiles:` line listing which profiles surface it |
-| **Wizard** | `.agent-src.uncompressed/commands/onboard.md` | After role selection, prints the five-command starter list from the selected profile's `commands_hint` |
+| **Wizard** | `.agent-src.uncondensed/commands/onboard.md` | After role selection, prints the five-command starter list from the selected profile's `commands_hint` |
 
 The README and wizard surfaces are already wired. The catalog `profiles:`
 line is a Phase 2 deliverable.

package/docs/contracts/{compression-default-kill-criterion.md → condensation-default-kill-criterion.md}

@@ -3,71 +3,71 @@ stability: beta
 keep-beta-until: 2026-08-14
 ---
 
-# Compression default — kill-criterion
+# Condensation default — kill-criterion
 
-> **Status:** v1-measured · criterion not met · default stays `off` · **Owner:** `step-16-caveman-substance.md`
-> Phase 1 closeout · **Sources:** [`internal/bench/reports/caveman-v1.md`](../../bench/reports/caveman-v1.md) ·
+> **Status:** v1-measured · criterion not met · default stays `off` · **Owner:** `step-16-telegraph-substance.md`
+> Phase 1 closeout · **Sources:** [`internal/bench/reports/telegraph-v1.md`](../../bench/reports/telegraph-v1.md) ·
 > [`council-synthesis.md` § 7](../../agents/evidence/audits/2026-05-14-north-star/council-synthesis.md) <!-- council-ref-allowed: ADR decision trace for v1 kill-criterion verdict --> ·
-> [`caveman-v1-kc-verdict.json`](../../agents/runtime/council/responses/caveman-v1-kc-verdict.json) <!-- council-ref-allowed: ADR decision trace for v1 kill-criterion verdict -->
+> [`telegraph-v1-kc-verdict.json`](../../agents/runtime/council/responses/telegraph-v1-kc-verdict.json) <!-- council-ref-allowed: ADR decision trace for v1 kill-criterion verdict -->
 
 ## Rule
 
 ```
-DEFAULT STAYS OFF UNTIL `task bench -- --caveman` PRODUCES A POSITIVE vs_terse MEDIAN.
+DEFAULT STAYS OFF UNTIL `task bench -- --telegraph` PRODUCES A POSITIVE vs_terse MEDIAN.
 DECISION OWNED BY THE NEXT BENCH CLOSEOUT, NOT BY THIS DOC.
 ```
 
-1. **Current state.** `caveman.speak_scope` defaults `off`. Carve-outs
+1. **Current state.** `telegraph.speak_scope` defaults `off`. Carve-outs
    (security · destructive · multi-step · code blocks · paths · numbered
    options · Iron-Law markers) are documented in
-   [`caveman-speak`](../../.agent-src.uncompressed/rules/caveman-speak.md)
+   [`telegraph-speak`](../../.agent-src.uncondensed/rules/telegraph-speak.md)
    but the feature is non-promoted: no skill recommends turning it on,
    no preset enables it, no profile depends on it.
-2. **Baselines.** Every published `internal/bench/reports/caveman-v<N>.{json,md}`
-   measures three arms (`compressed` · `terse-control` ·
-   `uncompressed`) and reports two savings columns:
-   - `vs_raw` — median savings against the uncompressed arm.
+2. **Baselines.** Every published `internal/bench/reports/telegraph-v<N>.{json,md}`
+   measures three arms (`condensed` · `terse-control` ·
+   `uncondensed`) and reports two savings columns:
+   - `vs_raw` — median savings against the uncondensed arm.
    - `vs_terse` — **load-bearing** median savings against the
      `Answer concisely.` terse-control arm. `vs_raw` is inflated by the
      carve-out-tax-free pure-prose case and is **not** the gate metric.
-3. **Decision table.** Read the latest `internal/bench/reports/caveman-v<N>.md`
+3. **Decision table.** Read the latest `internal/bench/reports/telegraph-v<N>.md`
    and apply exactly one of:
 
    | Measured `vs_terse` median | Quality regression on corpus | Verdict |
    |---|---|---|
-   | < 0 % | any | **Criterion not met — defer.** Keep default `off`. No telemetry multiplier. Next move owned by the corpus-widening / methodology-revision step that produces `caveman-v<N+1>`. |
+   | < 0 % | any | **Criterion not met — defer.** Keep default `off`. No telemetry multiplier. Next move owned by the corpus-widening / methodology-revision step that produces `telegraph-v<N+1>`. |
    | 0 % – < 30 % | any | **Hold.** Keep default `off`. Authorised follow-up: widen corpus or tune carve-out share; no default flip. |
-   | ≥ 30 % | < 5 % | **Flip default on** — `caveman.speak_scope` defaults to a non-`off` value (separate roadmap), carve-outs stay, statusline surfaces lifetime tokens saved. |
+   | ≥ 30 % | < 5 % | **Flip default on** — `telegraph.speak_scope` defaults to a non-`off` value (separate roadmap), carve-outs stay, statusline surfaces lifetime tokens saved. |
    | ≥ 30 % | ≥ 5 % | **Hold** — repeat the window once with tuned intensity ladder; second hold → deprecate. |
 
    "Quality regression" = host-side rubric on the corpus per
    `benchmark-report-schema.md`. Numbers checked into the published
-   `caveman-v<N>.json` as the decision artefact.
+   `telegraph-v<N>.json` as the decision artefact.
 4. **No interim flip.** The default does not move on anecdote,
    gut feeling, or a single positive prompt. Only a published
-   `caveman-v<N>` report with a `vs_terse` median in the "Flip" row
+   `telegraph-v<N>` report with a `vs_terse` median in the "Flip" row
    above authorises a default change, under a follow-up roadmap.
 
 ## v1 verdict (2026-05-16)
 
-[`internal/bench/reports/caveman-v1.md`](../../bench/reports/caveman-v1.md)
+[`internal/bench/reports/telegraph-v1.md`](../../bench/reports/telegraph-v1.md)
 landed 30 calls · $0.0805 · 0 errors · `claude-sonnet-4-5`:
 
 | Metric | Median | p10 | p90 |
 |---|---:|---:|---:|
 | `vs_raw` savings | +23.51 % | -18.29 % | +52.53 % |
 | **`vs_terse` savings** | **−9.27 %** | **−109.85 %** | +51.32 % |
-| Realised carve-out share (compressed arm) | 30.67 % | — | — |
+| Realised carve-out share (condensed arm) | 30.67 % | — | — |
 
 Per row 1 of the table, the v1 verdict is **criterion not met — defer**.
 Default stays `off`; no telemetry multiplier ships; no rule retirement
-in this roadmap. Wins exist only on pure-prose prompts (caveman-09
-+50.5 %, caveman-10 +58.4 %); carve-out-heavy prompts drag the median
-negative (caveman-04 path-list −108 %, caveman-06 mode-marker −123 %).
+in this roadmap. Wins exist only on pure-prose prompts (telegraph-09
++50.5 %, telegraph-10 +58.4 %); carve-out-heavy prompts drag the median
+negative (telegraph-04 path-list −108 %, telegraph-06 mode-marker −123 %).
 
 ### Council split (recorded, not decisive)
 
-Council run [`caveman-v1-kc-verdict.json`](../../agents/runtime/council/responses/caveman-v1-kc-verdict.json) <!-- council-ref-allowed: ADR decision trace for v1 kill-criterion verdict -->
+Council run [`telegraph-v1-kc-verdict.json`](../../agents/runtime/council/responses/telegraph-v1-kc-verdict.json) <!-- council-ref-allowed: ADR decision trace for v1 kill-criterion verdict -->
 (2 members · 1 round · $0.0514 actual) split:
 
 - **`claude-sonnet-4-5`** → Decision A.1 (deprecate now) + Decision B.3
@@ -77,7 +77,7 @@ Council run [`caveman-v1-kc-verdict.json`](../../agents/runtime/council/response
 - **`gpt-4o`** → Decision A.3 (hold + re-bench with widened corpus +
   revised terse-control prompt) + Decision B.2 (per-category
   multipliers, suppress negatives). Reasoning: 10 prompts is a
-  razor-thin sample; the terse-control prompt may under-compress; the
+  razor-thin sample; the terse-control prompt may under-condense; the
   carve-out validator (Phase 4) is not yet shipped, so we are
   measuring a half-implemented feature.
 
@@ -96,21 +96,21 @@ predated v1 numbers. The 2026-05-16 council split (Sonnet = deprecate now,
 GPT-4o = re-bench) is informed by v1 but disagrees on which methodological
 weakness is decisive. The kill table above gives every future bench run a
 deterministic resolution path and stops every downstream roadmap from
-re-litigating compression on every PR.
+re-litigating condensation on every PR.
 
 ## Cross-references
 
-- [`internal/bench/reports/caveman-v1.md`](../../bench/reports/caveman-v1.md)
+- [`internal/bench/reports/telegraph-v1.md`](../../bench/reports/telegraph-v1.md)
   — v1 measurement; canonical baseline this doc cites.
 - [`docs/benchmarks.md`](../benchmarks.md)
   — cadence + when the next bench run is mandatory.
-- [`caveman-telemetry`](caveman-telemetry.md)
+- [`telegraph-telemetry`](telegraph-telemetry.md)
   — multiplier contract; records the suspended state v2 must lift.
-- [`caveman-speak`](../../.agent-src.uncompressed/rules/caveman-speak.md)
-  — runtime rule; reads `caveman.speak_scope` from settings.
+- [`telegraph-speak`](../../.agent-src.uncondensed/rules/telegraph-speak.md)
+  — runtime rule; reads `telegraph.speak_scope` from settings.
 
 ## Done
 
 This doc reflects the v1 verdict. It is **not** an action item. The next
-bench closeout (against `caveman-v2` once a widened corpus or revised
+bench closeout (against `telegraph-v2` once a widened corpus or revised
 methodology is shipped) closes the loop.

package/docs/contracts/config-presets.md

@@ -17,7 +17,7 @@ keep-beta-until: 2026-08-14
 
 A **preset** owns governance knobs that the user wants to tune as a
 bundle, not individually. Three seed presets ship; users can declare
-their own under `.agent-src.uncompressed/presets/<id>.yml`.
+their own under `.agent-src.uncondensed/presets/<id>.yml`.
 
 | `preset.id` | Stance | Typical user |
 |---|---|---|

package/docs/contracts/context-paths.md

@@ -13,7 +13,7 @@ keep-beta-until: 2026-08-12
 > frontmatter contract for citing a context from a rule.
 
 This contract defines **where** a context file is allowed to live under
-`.agent-src.uncompressed/contexts/` (the source-of-truth tree). It is the
+`.agent-src.uncondensed/contexts/` (the source-of-truth tree). It is the
 DAG root of `road-to-structural-optimization` Phase 0: the file-ownership
 matrix (Phase 0.1) greps for context-file fan-out at the locked tree, and
 several later phases (2A, 2B, 3a/b/c, 6) extract material into specific
@@ -55,7 +55,7 @@ contexts/subagent-configuration.md
 ## Rules enforced by `check_context_paths.py`
 
 1. **Sub-tree allow-list.** Every `*.md` under
-   `.agent-src.uncompressed/contexts/` must be either (a) in one of the
+   `.agent-src.uncondensed/contexts/` must be either (a) in one of the
    nine locked sub-trees above, or (b) one of the six grandfathered
    root-level files. Anything else fails CI.
 2. **No collisions.** No two context files may share the same basename
@@ -66,7 +66,7 @@ contexts/subagent-configuration.md
    a frontmatter `load_context:` / `load_context_eager:` entry, **or** a
    markdown body mention of the relative path
    (`contexts/<sub-tree>/<file>.md` or
-   `.agent-src.uncompressed/contexts/<sub-tree>/<file>.md`).
+   `.agent-src.uncondensed/contexts/<sub-tree>/<file>.md`).
 
 The linter exits non-zero on any violation and prints a one-line
 diagnostic per offence.

package/docs/contracts/context-spine.md

@@ -172,7 +172,7 @@ Before shipping a senior skill that opts into the spine:
 
 ## See also
 
-- `.agent-src.uncompressed/rules/skill-quality.md` § Senior-Tier
+- `.agent-src.uncondensed/rules/skill-quality.md` § Senior-Tier
   Required Structure — the four blocks every `tier: senior` skill
   ships independently of spine opt-in.
 - `docs/contracts/cross-wing-handoff.md` — typed handoffs between

package/docs/contracts/cost-summary-schema.md

@@ -11,7 +11,7 @@ Schema-versioned so downstream consumers can pin and migrate explicitly.
 
 Design reference: Ruflo `scripts/summary.mjs` (upstream cite). Our shape
 diverges to align with the local `agents/cost-tracking/sessions.jsonl`
-fields and the caveman-suspended-multiplier contract.
+fields and the telegraph-suspended-multiplier contract.
 
 ## Envelope
 
@@ -43,15 +43,15 @@ fields and the caveman-suspended-multiplier contract.
   "total_cost_usd": 1.2345,
   "input_tokens": 100000,
   "output_tokens": 50000,
-  "caveman_delta_tokens": 0,
-  "caveman_multiplier_version": "v1",
-  "caveman_multiplier_active": false
+  "telegraph_delta_tokens": 0,
+  "telegraph_multiplier_version": "v1",
+  "telegraph_multiplier_active": false
 }
 ```
 
-`caveman_delta_tokens` is always `0` while
-`caveman_multiplier_active == false` — see
-[`caveman-telemetry.md`](caveman-telemetry.md) for the suspension contract.
+`telegraph_delta_tokens` is always `0` while
+`telegraph_multiplier_active == false` — see
+[`telegraph-telemetry.md`](telegraph-telemetry.md) for the suspension contract.
 
 ## `by_session` / `by_conversation` row shape
 
@@ -62,7 +62,7 @@ fields and the caveman-suspended-multiplier contract.
   "total_cost_usd": 0.4567,
   "input_tokens": 8000,
   "output_tokens": 4500,
-  "caveman_delta_tokens": 0
+  "telegraph_delta_tokens": 0
 }
 ```
 
@@ -81,7 +81,7 @@ group by inspecting which array the row lives in.
 }
 ```
 
-`by_model` omits caveman fields — the multiplier is dialect-scoped, not
+`by_model` omits telegraph fields — the multiplier is dialect-scoped, not
 model-scoped.
 
 ## Stability guarantees
@@ -100,8 +100,8 @@ model-scoped.
 
 ## See also
 
-- [`caveman-telemetry.md`](caveman-telemetry.md) — defines the
-  `caveman_*` fields and the suspended-multiplier contract.
+- [`telegraph-telemetry.md`](telegraph-telemetry.md) — defines the
+  `telegraph_*` fields and the suspended-multiplier contract.
 - [`scripts/cost_summary.py`](../../scripts/cost_summary.py) — implementation.
 - [`scripts/cost_by_conversation.py`](../../scripts/cost_by_conversation.py) — narrower per-conversation lens with the same JSONL source.
-- [`scripts/caveman_stats.py`](../../scripts/caveman_stats.py) — caveman-only delta lens with the same JSONL source.
+- [`scripts/telegraph_stats.py`](../../scripts/telegraph_stats.py) — telegraph-only delta lens with the same JSONL source.

package/docs/contracts/cross-wing-handoff.md

@@ -54,15 +54,15 @@ linter rejects it.
 ## § 3 — Worktree boundary
 
 Each handoff MAY run in a fresh git worktree when invoked through
-[`subagent-orchestration`](../../.agent-src.uncompressed/skills/subagent-orchestration/SKILL.md)
+[`subagent-orchestration`](../../.agent-src.uncondensed/skills/subagent-orchestration/SKILL.md)
 mode 6 (`do-in-worktrees`). Mode 6 is the state-machine layer — it
 declares when worktree isolation is mandatory (multi-step cross-wing
 chain, each step ≥30 min, branch state would otherwise leak between
 steps) and what handoff shape each step emits / consumes. The
 executor lives in
-[`using-git-worktrees`](../../.agent-src.uncompressed/skills/using-git-worktrees/SKILL.md)
+[`using-git-worktrees`](../../.agent-src.uncondensed/skills/using-git-worktrees/SKILL.md)
 and
-[`finishing-a-development-branch`](../../.agent-src.uncompressed/skills/finishing-a-development-branch/SKILL.md);
+[`finishing-a-development-branch`](../../.agent-src.uncondensed/skills/finishing-a-development-branch/SKILL.md);
 this contract does not duplicate that runtime.
 
 The boundary is **advisory** for chains that do not opt into mode 6:
@@ -128,7 +128,7 @@ Three shipped chains across the suite illustrate the contract:
 
 ## See also
 
-- `.agent-src.uncompressed/rules/skill-quality.md` § Senior-Tier
+- `.agent-src.uncondensed/rules/skill-quality.md` § Senior-Tier
   Required Structure — defines the `## Related Skills` and `## Output`
   blocks the contract reads.
 - `scripts/lint_handoffs.py` — mechanical enforcement.

package/docs/contracts/daily-workspace.md

@@ -1,3 +1,7 @@
+---
+stability: experimental
+---
+
 # Daily Workspace Surface Contract
 
 > **Status** · v0 / design · 2026-05-24. Surface contract for the daily

package/docs/contracts/decision-trace-v1.md

@@ -85,7 +85,7 @@ compat extensions and MUST NOT raise on them.
 | `phase` | Engine phase that produced the trace. One of the eight phases above. |
 | `confidence_band` | One of `low` / `medium` / `high`. Heuristic defined below — derived from memory hits + ambiguity flags + verify evidence count. |
 | `risk_class` | One of `low` / `medium` / `high`. Per [`rule-interactions.md`](rule-interactions.md) — drives reviewer routing. |
-| `rules[].rule_id` | Stable rule id, matches the filename under `.agent-src.uncompressed/rules/` minus `.md`. |
+| `rules[].rule_id` | Stable rule id, matches the filename under `.agent-src.uncondensed/rules/` minus `.md`. |
 | `rules[].applied` | True if the rule's Iron Law fired and changed engine behaviour this phase. |
 | `rules[].skipped` | True if the rule was checked but produced no effect (no trigger match). |
 | `rules[].conflicted_with` | List of rule_ids that fired against this one. Reduction handled per `rule-interactions.md`. |
@@ -163,7 +163,7 @@ majors.
 ## Cross-references
 
 - Personas (Architect, Risk-Officer) live in the package's persona
-  library under [`.agent-src.uncompressed/personas/`](../../.agent-src.uncompressed/personas/).
+  library under [`.agent-src.uncondensed/personas/`](../../.agent-src.uncondensed/personas/).
   This contract does not duplicate them — when a future trace consumer
   attributes a decision to one of those personas, the persona file is
   the source of truth, not this envelope.

package/docs/contracts/discovery-manifest.md

@@ -15,7 +15,7 @@ keep-beta-until: 2026-08-19
 
 The generator
 [`scripts/build_discovery_manifest.py`](../../scripts/build_discovery_manifest.py)
-walks `.agent-src.uncompressed/` and emits the manifest to
+walks `.agent-src.uncondensed/` and emits the manifest to
 `dist/discovery/discovery-manifest.json` plus a sidecar
 `discovery-manifest.json.sha256` for tamper detection.
 
@@ -58,7 +58,7 @@ per-artefact checksum drift all fail CI (Phase-6 invariants).
 
 ```jsonc
 {
-  "path": ".agent-src.uncompressed/skills/laravel/SKILL.md",
+  "path": ".agent-src.uncondensed/skills/laravel/SKILL.md",
   "category": "skill",
   "name": "laravel",
   "workspaces": ["engineering"],
@@ -156,7 +156,7 @@ there is no `id` field.
       "optional_packs": ["symfony"],
       "artefact_count": 124,
       "packs": [
-        { "id": "engineering-base", "artefact_count": 83, "artefacts": [".agent-src.uncompressed/skills/…/SKILL.md", "…"] }
+        { "id": "engineering-base", "artefact_count": 83, "artefacts": [".agent-src.uncondensed/skills/…/SKILL.md", "…"] }
       ]
     }
   ]
@@ -178,7 +178,7 @@ there is no `id` field.
       "requires_hint": [],
       "trust_level_default": "core",
       "artefact_count": 83,
-      "artefacts": [".agent-src.uncompressed/skills/…/SKILL.md", "…"],
+      "artefacts": [".agent-src.uncondensed/skills/…/SKILL.md", "…"],
       "by_lifecycle":   { "active": 82, "experimental": 1, "deprecated": 0, "archived": 0 },
       "by_trust_level": { "core": 83, "professional": 0, "experimental": 0, "advisory": 0, "restricted": 0 }
     }

package/docs/contracts/explain-modes.md

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