@event4u/agent-config 3.3.0 → 4.2.0

package/docs/customization.md

@@ -66,7 +66,7 @@ ide
 cost_profile
 personal.bot_icon
 personal.autonomy
-caveman.speak_scope
+telegraph.speak_scope
 ```
 
 **Merge order** (lowest → highest precedence; every layer optional):
@@ -179,7 +179,7 @@ is recovered on the next server boot.
 | `chat_history.enabled` | `true` | Persistent JSONL log at `agents/runtime/.agent-chat-history` for crash recovery. |
 | `chat_history.frequency` | per profile | Logging granularity: `per_turn`, `per_phase`, or `per_tool` (see matrix below). |
 | `chat_history.max_size_kb` | per profile | Max file size before overflow handling (see matrix below). |
-| `chat_history.on_overflow` | per profile | `rotate` drops oldest, `compress` marks for summarization (see matrix below). |
+| `chat_history.on_overflow` | per profile | `rotate` drops oldest, `condense` marks for summarization (see matrix below). |
 | `onboarding.onboarded` | `false` | Whether the setup wizard has run. The `onboarding-gate` rule prompts for `agent-config setup` while this is `false`. |
 | `ai_council.enabled` | `false` | Master switch for the `/council` command. Even when enabled, every consultation asks before spending tokens. |
 | `ai_council.members.<provider>.enabled` | `false` | Per-provider opt-in (`anthropic`, `openai`). Tokens live in `~/.event4u/agent-config/<provider>.key` (mode 0600), never in this file. Legacy `~/.config/agent-config/<provider>.key` is read as a fallback. |
@@ -226,7 +226,7 @@ to `false` in `.agent-settings.yml` to silence post-task analysis without
 changing the profile.
 
 The authoritative matrix of all matrix-controlled settings lives in
-[`.agent-src.uncompressed/templates/agent-settings.md`](../.agent-src.uncompressed/templates/agent-settings.md).
+[`.agent-src.uncondensed/templates/agent-settings.md`](../.agent-src.uncondensed/templates/agent-settings.md).
 
 ### Chat-history defaults per profile
 
@@ -240,13 +240,13 @@ behavior — the per-profile table is just the initial default.
 | `chat_history.enabled` | `true` | `true` | `true` |
 | `chat_history.frequency` | `per_turn` | `per_phase` | `per_tool` |
 | `chat_history.max_size_kb` | `128` | `256` | `512` |
-| `chat_history.on_overflow` | `rotate` | `rotate` | `compress` |
+| `chat_history.on_overflow` | `rotate` | `rotate` | `condense` |
 
 `custom` ignores these defaults — set every value explicitly.
 
 ### Verbosity
 
-The `verbosity:` block and `caveman.speak_scope` control how much narration
+The `verbosity:` block and `telegraph.speak_scope` control how much narration
 the agent emits around routine actions. Defaults are tuned for token
 frugality — flip values to `true` (or higher tier) to restore legacy verbose
 output. Iron-Law gates (`commit-policy`, `scope-control` git-ops,
@@ -261,10 +261,10 @@ output. Iron-Law gates (`commit-policy`, `scope-control` git-ops,
 | `verbosity.intent_announcements` | `true`, `false` | `false` | Intent announcements ("Let me check…", "Now I will…", "Found it") in skill bodies. `false` = act and emit the result. |
 | `verbosity.script_output` | `silent`, `minimal`, `verbose` | `minimal` | Stdout chatter from `scripts/*.py`, `scripts/*.sh`, and `.augment/scripts/`. `silent` = stderr only; `minimal` = one summary line per script; `verbose` = pre-Phase-10 per-step prints. Iron-Law surfaces (release confirms, install secrets prompts, error markers) ignore this key. |
 | `verbosity.taskfile_command_echo` | `true`, `false` | `false` | Suppress the `task: [name] cmd...` echo Taskfile prints before each task body. `true` = echoes preserved (legacy behaviour); `false` = `silent: true` is set on every Phase-10 safe task. |
-| `caveman.speak_scope` | `off`, `prose_only`, `aggressive` | `prose_only` | How widely caveman-speak grammar applies in chat. `off` = no caveman; `prose_only` = caveman in body prose, numbered options + Iron-Law-literal blocks stay full prose; `aggressive` = caveman everywhere except Iron-Law literals. |
+| `telegraph.speak_scope` | `off`, `prose_only`, `aggressive` | `prose_only` | How widely telegraph-speak grammar applies in chat. `off` = no telegraph; `prose_only` = telegraph in body prose, numbered options + Iron-Law-literal blocks stay full prose; `aggressive` = telegraph everywhere except Iron-Law literals. |
 
 The cross-rule index for these defaults lives in
-[`.agent-src.uncompressed/contexts/contracts/frugality-charter.md`](../.agent-src.uncompressed/contexts/contracts/frugality-charter.md).
+[`.agent-src.uncondensed/contexts/contracts/frugality-charter.md`](../.agent-src.uncondensed/contexts/contracts/frugality-charter.md).
 Writer skills (`skill-writing`, `rule-writing`, `command-writing`,
 `guideline-writing`, `roadmap-writing`, `persona-writing`,
 `agent-docs-writing`, `context-authoring`, `conventional-commits-writing`,
@@ -394,7 +394,7 @@ tarball and is the source of truth consumed by:
 > When you read "the Laravel pack", picture a filter over the shared
 > artefact tree — not a separate npm package. The day ADR-011's
 > extraction trigger flips, the same scan output drives the split;
-> until then, every artefact lives under `.agent-src.uncompressed/`.
+> until then, every artefact lives under `.agent-src.uncondensed/`.
 
 Alongside the JSON manifest, the scanner writes
 `dist/discovery/discovery-manifest.json.sha256` — a sidecar hash that
@@ -502,6 +502,26 @@ in `.agent-settings.yml`; the command then exits 0 with a one-line
 notice instead of producing a trace. Exit codes: `0` rendered or
 disabled · `1` no recent run found · `2` invocation error.
 
+## Troubleshooting
+
+### A skill appears twice in my AI tool
+
+Most common cause: cross-scope drift between a user-global install (e.g.
+`~/.claude/skills/`) and a project-local install (e.g. `./.claude/skills/`).
+Run the probe to confirm:
+
+```bash
+task probe:skills
+# or directly: python3 scripts/probe_skill_registration.py
+```
+
+The probe lists every registration across all six tools and flags
+`DUPLICATE` (same skill in ≥ 2 sources) and `DRIFT` (same skill, different
+descriptions or versions — the actual 2026-05-25 failure mode). To clean a
+stale install at the other scope: `bash scripts/cleanup_other_scope.sh --confirm`.
+Background: [`docs/contracts/skill-distribution-channels.md`](contracts/skill-distribution-channels.md)
++ [`docs/contracts/install-scopes.md`](contracts/install-scopes.md).
+
 ---
 
 ← [Back to README](../README.md)

package/docs/decisions/ADR-001-kernel-swap-deferred.md

@@ -37,7 +37,7 @@ landed in `kernel-membership.md` § 5.2:
 **Variant (a) — status quo through P2.2 + P3.1.**
 
 - Keep `agent-authority` in the kernel.
-- Keep `autonomous-execution` in `compress-and-keep` (auto-tier) per
+- Keep `autonomous-execution` in `condense-and-keep` (auto-tier) per
   `docs/contracts/rule-classification.md` § 3.2.
 - Re-evaluate the swap as a P3.2 ADR after the router schema and
   compiler ship.
@@ -47,7 +47,7 @@ landed in `kernel-membership.md` § 5.2:
 ### Accepted
 
 - 25k hard cap stays intact (no governance erosion via cap-raise).
-- 2 Iron-Law-override ADRs land in P2.2 if post-compression
+- 2 Iron-Law-override ADRs land in P2.2 if post-condensation
   measurement confirms overage (`direct-answers`, `language-and-tone`).
 - The 9-rule set carried into P2.2 is the locked § 4 list.
 
@@ -78,7 +78,7 @@ precedence at build time. At that point:
   (`docs/guidelines/agent-authority.md`) as documentation of the
   band model.
 - `autonomous-execution` can be promoted into the kernel under a
-  new ADR (ADR-N) that replaces this one, *if* its post-compression
+  new ADR (ADR-N) that replaces this one, *if* its post-condensation
   size fits the cap with no further demotion.
 
 This deferral is **not** indefinite: P3.2 ships the router compiler;
@@ -90,7 +90,7 @@ migrations) so the migration plan reflects the final kernel set.
 - **Variant (b) — swap + raise cap to 27k.** Rejected. Raising the
   hard cap mid-roadmap weakens the original 25k contract that the
   whole roadmap is built around. If 27k turns out to be the real
-  ceiling, that is a separate ADR after compression measurement
+  ceiling, that is a separate ADR after condensation measurement
   proves the band, not a pre-emptive concession.
 - **Variant (c) — swap + demote `verify-before-complete`.**
   Rejected. `verify-before-complete` carries criterion #1 (Iron
@@ -105,5 +105,5 @@ migrations) so the migration plan reflects the final kernel set.
 - `docs/contracts/kernel-membership.md` § 4, § 5.2
 - `agents/runtime/council/sessions/20260506T044941Z-phase1-cross-check-r2.json` <!-- council-ref-allowed: ADR decision trace -->
 - `agents/roadmaps/road-to-kernel-and-router.md` § Decisions, § Phase 2
-- `.agent-src.uncompressed/rules/agent-authority.md` (subject)
-- `.agent-src.uncompressed/rules/autonomous-execution.md` (proposed promotion)
+- `.agent-src.uncondensed/rules/agent-authority.md` (subject)
+- `.agent-src.uncondensed/rules/autonomous-execution.md` (proposed promotion)

package/docs/decisions/ADR-002-kernel-bucket-overrides.md

@@ -1,7 +1,7 @@
 # ADR-002 — Kernel-Bucket Cap Raise (25k → 26k) and Per-Rule Iron-Law Overrides
 
 - **Status:** Accepted (2026-05-06)
-- **Phase:** Road to Rule Kernel and Router · P2.2 (Heavy Compression)
+- **Phase:** Road to Rule Kernel and Router · P2.2 (Heavy Condensation)
 - **Supersedes:** none — extends the Council R2 amendments locked in
   `docs/contracts/kernel-membership.md` § 5.1 (median r=0.712, per-rule cap 2.5k,
   kernel-bucket 25k).
@@ -10,27 +10,27 @@
 
 ## Context
 
-P1.3 projected the post-compression kernel bucket at **23 071 chars** using
+P1.3 projected the post-condensation kernel bucket at **23 071 chars** using
 the median pilot ratio r=0.712 (3 pilots: agent-authority, direct-answers,
 language-and-tone). Pilot rules were **short to medium** (1.0k–2.5k baseline).
 
-P2.2 applied the same compression discipline to the remaining 6 kernel rules
+P2.2 applied the same condensation discipline to the remaining 6 kernel rules
 (ask-when-uncertain, commit-policy, no-cheap-questions,
 non-destructive-by-default, scope-control, plus the verify-before-complete
 auto-tier rule kept by ADR-001). Iron-Law SHA preservation verified for
 all 8 rules with Iron-Law fences (`scripts/iron_law_sha.py`).
 
-**Empirical post-compression measurements (2026-05-06):**
+**Empirical post-condensation measurements (2026-05-06):**
 
 | metric | projected | actual |
 |---|---:|---:|
 | kernel bucket sum | 23 071 | **25 590** |
-| compression ratio r (kernel-wide) | 0.712 (median pilot) | **0.795** |
+| condensation ratio r (kernel-wide) | 0.712 (median pilot) | **0.795** |
 | rules > 2.5k cap | 2 (pilots) | 6 |
 | rules > 4.0k ceiling | 0 | 0 |
 
 The actual ratio (0.795) is worse than the pilot median (0.712) because
-**longer rules compress less efficiently than short ones**: each Iron-Law
+**longer rules condense less efficiently than short ones**: each Iron-Law
 rule has a fixed payload of frontmatter, Iron-Law fence, exception
 enumeration, see-also list — shrinkage is bounded by what cannot leave
 the rule without breaking the rule's contract. The 5 longest source rules
@@ -61,7 +61,7 @@ enumeration + pre-send self-check + decline/fence semantics).
    | `direct-answers` | 2 841 | +341 | ✓ |
 
 3. **Cap stays sticky.** Future kernel additions or rule-body growth must
-   either (a) compress within the 26k bucket, (b) externalise to a
+   either (a) condense within the 26k bucket, (b) externalise to a
    `contexts/authority/*` companion, or (c) require a follow-up ADR.
 
 ## Rationale
@@ -92,23 +92,23 @@ place.
 The `commit-policy` rule was trimmed below 2.5k (2 354 chars) by removing
 a redundant cross-reference line, demonstrating that aggressive trimming
 is possible where the rule does not carry an enumeration. The 6 overrides
-are the rules where further compression would force semantic loss.
+are the rules where further condensation would force semantic loss.
 
 ## Consequences
 
 - **Pro:** Iron-Law fidelity preserved — every fence still byte-identical
   to baseline (verified by `iron_law_sha.py --all-kernel`).
-- **Pro:** Empirical compression r=0.795 documented; future kernel work
+- **Pro:** Empirical condensation r=0.795 documented; future kernel work
   uses this as the realistic ratio (not 0.712, which was a pilot-skewed
   optimum).
 - **Pro:** Override ceiling (4 000) untouched — no rule grows
   unboundedly; the 4k cap remains the next checkpoint.
 - **Con:** 25 590 / 26 000 = 98.4 % bucket utilisation. Adding any
-  10th kernel rule would require either compression of an existing rule
+  10th kernel rule would require either condensation of an existing rule
   or a further cap raise.
 - **Con:** ratio 0.795 means future "always" promotions cost more than
   Phase 1 estimated. Phase 4 token-budget measurements should treat
-  0.795 as the reference compression rate.
+  0.795 as the reference condensation rate.
 
 ## Rollback
 

package/docs/decisions/ADR-003-flat-cluster-subs-and-colon-syntax.md

@@ -120,7 +120,7 @@ ceiling.
 
 - [`docs/contracts/command-clusters.md`](../contracts/command-clusters.md)
   — locked cluster set + sub-command naming contract.
-- [`.agent-src.uncompressed/contexts/communication/rules-auto/slash-command-routing-policy-mechanics.md`](../../.agent-src.uncompressed/contexts/communication/rules-auto/slash-command-routing-policy-mechanics.md)
+- [`.agent-src.uncondensed/contexts/communication/rules-auto/slash-command-routing-policy-mechanics.md`](../../.agent-src.uncondensed/contexts/communication/rules-auto/slash-command-routing-policy-mechanics.md)
   — runtime routing semantics and the colon-canonical rule.
-- [`.agent-src.uncompressed/contexts/execution/roadmap-process-loop.md`](../../.agent-src.uncompressed/contexts/execution/roadmap-process-loop.md)
+- [`.agent-src.uncondensed/contexts/execution/roadmap-process-loop.md`](../../.agent-src.uncondensed/contexts/execution/roadmap-process-loop.md)
   — the shared mechanics that motivated the cluster shape.

package/docs/decisions/ADR-004-rule-governance-pruning.md

@@ -234,7 +234,7 @@ documentation rewrite for marginal additional savings.
   (Phase 5.4 R3 raw debate)
 - `docs/decisions/ADR-rule-kernel-and-router.md` (kernel-membership
   contract — Phase 5 changes leave kernel untouched per Lever C lock)
-- `.agent-src.uncompressed/rules/guidelines.md` (deprecated subject)
-- `.agent-src.uncompressed/rules/size-enforcement.md` (merged subject)
-- `.agent-src.uncompressed/rules/package-ci-checks.md` (demoted subject)
-- `.agent-src.uncompressed/rules/analysis-skill-routing.md` (demoted subject)
+- `.agent-src.uncondensed/rules/guidelines.md` (deprecated subject)
+- `.agent-src.uncondensed/rules/size-enforcement.md` (merged subject)
+- `.agent-src.uncondensed/rules/package-ci-checks.md` (demoted subject)
+- `.agent-src.uncondensed/rules/analysis-skill-routing.md` (demoted subject)

package/docs/decisions/ADR-005-subagent-worktrees.md

@@ -21,7 +21,7 @@ and specialist review lenses. Step A7 derives from council iter-1
 verdict **CC-OQ1 (a)** — adopt the AgentHub pattern from
 `claude-skills` (per-candidate git-worktree isolation) into the
 existing `subagent-orchestration` skill **without** weakening the
-[`non-destructive-by-default`](../../.agent-src.uncompressed/rules/non-destructive-by-default.md)
+[`non-destructive-by-default`](../../.agent-src.uncondensed/rules/non-destructive-by-default.md)
 Hard Floor.
 
 The AgentHub pattern in its native form is appealing: spawn N
@@ -49,13 +49,13 @@ variant** under three Hard-Floor-derived rules:
    branch into the integration branch. The user invokes the merge
    explicitly (e.g. `/finishing-a-development-branch`), or the
    orchestrator hands back with a numbered-options block per
-   [`user-interaction`](../../.agent-src.uncompressed/rules/user-interaction.md).
+   [`user-interaction`](../../.agent-src.uncondensed/rules/user-interaction.md).
 2. **Ranked presentation.** Judge ranks candidates 1..N with a
    one-line justification per rank. The judge does **not** apply
    anything; ranking is the only output.
 3. **Loser worktrees stay.** The orchestrator does not delete
    losing worktrees automatically. Cleanup happens via
-   [`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)
    on user request, after harvesting any salvageable partial idea.
 
 Mode 7's chained-handoff variant is unchanged. The two variants
@@ -114,7 +114,7 @@ Both conditions must hold. Either alone is insufficient.
 
 - `agents/roadmaps/road-to-better-skills-and-profiles.md` § A7
   (council iter-1 CC-OQ1 verdict (a))
-- `.agent-src.uncompressed/skills/subagent-orchestration/SKILL.md` § Mode 7
-- `.agent-src.uncompressed/skills/using-git-worktrees/SKILL.md` (mechanics layer)
-- `.agent-src.uncompressed/rules/non-destructive-by-default.md` § Hard Floor catalog
-- `.agent-src.uncompressed/skills/finishing-a-development-branch/SKILL.md` (cleanup path)
+- `.agent-src.uncondensed/skills/subagent-orchestration/SKILL.md` § Mode 7
+- `.agent-src.uncondensed/skills/using-git-worktrees/SKILL.md` (mechanics layer)
+- `.agent-src.uncondensed/rules/non-destructive-by-default.md` § Hard Floor catalog
+- `.agent-src.uncondensed/skills/finishing-a-development-branch/SKILL.md` (cleanup path)

package/docs/decisions/ADR-011-domain-pack-readiness.md

@@ -76,17 +76,17 @@ this — they are a single execution surface.
 
 ## Consequences
 
-### (i) What stays under `.agent-src.uncompressed/` today
+### (i) What stays under `.agent-src.uncondensed/` today
 
 The complete video capability stays in the existing flat layout —
 no path changes, no symlink relocation, no namespace prefix:
 
-- `.agent-src.uncompressed/skills/{character-consistency,motion-choreographer,pixar-storyteller,scene-expander,video-director}/`
-- `.agent-src.uncompressed/personas/{ai-video-technical-director,hollywood-director}.md`
+- `.agent-src.uncondensed/skills/{character-consistency,motion-choreographer,pixar-storyteller,scene-expander,video-director}/`
+- `.agent-src.uncondensed/personas/{ai-video-technical-director,hollywood-director}.md`
   (the third video persona, `pixar-storyboard-artist`, was folded
   into `skills/pixar-storyteller/` per the persona-cap council pass
   recorded in `persona-governance`)
-- `.agent-src.uncompressed/commands/video/{from-script,scene,storyboard,stitch}.md`
+- `.agent-src.uncondensed/commands/video/{from-script,scene,storyboard,stitch}.md`
 - `scripts/ai-video/` (the 5 adapter scripts + `lib/`)
 - `agents/settings/policies/media/` (Phase 2 output — already structured as
   a project-local policy directory, *not* a pack)
@@ -146,8 +146,8 @@ for ambiguity:
 
 - The five video adapters (`gemini-veo`, `kling`, `openai-images`,
   `higgsfield`, `sora`) — stay in `scripts/ai-video/`.
-- The two remaining video personas — stay in `.agent-src.uncompressed/personas/`.
-- The `/video:*` command cluster — stays in `.agent-src.uncompressed/commands/video/`.
+- The two remaining video personas — stay in `.agent-src.uncondensed/personas/`.
+- The `/video:*` command cluster — stays in `.agent-src.uncondensed/commands/video/`.
 - The `media-governance-routing` rule + `agents/settings/policies/media/`
   policy files — stay where Phase 2 placed them.
 - The provider-lifecycle contract + the `provider-lifecycle-discipline`

package/docs/decisions/ADR-013-discovery-frontmatter-contract.md

@@ -142,7 +142,7 @@ matching `config/discovery/packs.yml` row in the same PR.
   are accepted; the scanner emits `unassigned[]` warnings; CI logs but
   does not fail.
 - **Phase 4**: every artefact under
-  `.agent-src.uncompressed/{skills,rules,commands,templates}` either
+  `.agent-src.uncondensed/{skills,rules,commands,templates}` either
   declares the new keys, or sits in `config/discovery/unassigned-artefacts.yml`
   with a one-line reason.
 - **Phase 4+**: CI flips strict; missing annotation is a fail.
@@ -150,7 +150,7 @@ matching `config/discovery/packs.yml` row in the same PR.
 ### Trust-root allow-list (security-engineer council fold-in)
 
 The scanner honours frontmatter only on files under the trusted roots:
-`.augment/`, `.claude/`, `.agent-src.uncompressed/`, `.agent-src/`.
+`.augment/`, `.claude/`, `.agent-src.uncondensed/`, `.agent-src/`.
 Files under `agents/`, `tmp/`, or any consumer-writable path **cannot**
 claim ownership of a workspace or pack. Phase 2 enforces.
 
@@ -201,7 +201,7 @@ discovery-driven action.
 
 The five required keys (`workspaces`, `packs`, `lifecycle`, `trust`,
 `install`) are now **strictly enforced** across every artefact under
-`.agent-src.uncompressed/{skills,rules,commands,templates}` by
+`.agent-src.uncondensed/{skills,rules,commands,templates}` by
 [`scripts/lint_artefact_frontmatter.py`](../../scripts/lint_artefact_frontmatter.py),
 wired into `task lint-artefact-frontmatter`, `task ci`, and the opt-in
 combined pre-commit hook (`./agent-config hooks:install`). The migration

package/docs/decisions/ADR-015-discovery-manifest-contract.md

@@ -66,10 +66,10 @@ install-axis without a current consumer. Re-evaluate in Phase 5.
 
 ### Source-of-truth tree
 
-The generator walks `.agent-src.uncompressed/`, **not** `.agent-src/`.
-The Phase-2 roadmap text §Phase 2 says "the compressed canonical tree"
+The generator walks `.agent-src.uncondensed/`, **not** `.agent-src/`.
+The Phase-2 roadmap text §Phase 2 says "the condensed canonical tree"
 — that is a documentation slip. `augment-source-of-truth` rule states
-that uncompressed is canonical; the compressed tree is a build output
+that uncondensed is canonical; the condensed tree is a build output
 and may be regenerated. Manifest pipelines that read build outputs are
 fragile to bootstrap order.
 

package/docs/decisions/ADR-017-monorepo-physical-layout.md

@@ -36,7 +36,7 @@ TypeScript installer **without** moving a single file. The on-disk
 source tree is still flat:
 
 ```text
-.agent-src.uncompressed/
+.agent-src.uncondensed/
   rules/        # 72 entries
   skills/       # 218 entries
   commands/     # 129 entries
@@ -64,11 +64,11 @@ refs, cross-pack drift, hand-edited paths) all bite hardest here.
 packages/
   core/
     installer/                       # TS CLI (already there post-Phase 3)
-    .agent-src.uncompressed/         # rules + kernel skills + scaffolds
-  pack-php/.agent-src.uncompressed/
-  pack-laravel/.agent-src.uncompressed/
+    .agent-src.uncondensed/         # rules + kernel skills + scaffolds
+  pack-php/.agent-src.uncondensed/
+  pack-laravel/.agent-src.uncondensed/
   …
-  pack-ai-video/.agent-src.uncompressed/
+  pack-ai-video/.agent-src.uncondensed/
 ```
 
 No flag day: every commit between "before" and "after" the move builds
@@ -98,7 +98,7 @@ Implemented in [`scripts/plan_physical_move.py`](../../scripts/plan_physical_mov
 6. **Quarantined scaffolds** (the 26 entries in
    [`config/discovery/unassigned-artefacts.yml`](../../config/discovery/unassigned-artefacts.yml))
    → `packages/core/` with `unassigned scaffold:` reason recorded in the
-   move plan. The top-level `.agent-src.uncompressed/README.md` was added
+   move plan. The top-level `.agent-src.uncondensed/README.md` was added
    here during dry-run.
 7. **`primary pack: meta`** → `packages/core/` (package-internal
    scaffolding, not a real pack).
@@ -135,7 +135,7 @@ installer behaviour change.
 - Metadata-to-disk parity: a consumer can now `cd packages/pack-laravel`
   and see exactly what `pack.laravel` ships, no manifest indirection.
 - Phase 5 (trust) lands cleanly inside `packages/core/installer/` and
-  reads per-pack metadata from `packages/pack-*/.agent-src.uncompressed/`.
+  reads per-pack metadata from `packages/pack-*/.agent-src.uncondensed/`.
 - Phase 6 (browser wizard) maps packs 1:1 to its left-nav.
 - Cross-pack drift is now lintable (`task lint-pack-boundaries` in
   Phase 4.4 of the roadmap).
@@ -172,11 +172,11 @@ installer behaviour change.
 Four blocking items and two refinements raised by the council; each
 resolved before `--apply` runs.
 
-### B1 — Final source location of `.agent-src.uncompressed/`
+### B1 — Final source location of `.agent-src.uncondensed/`
 
 The council asked whether the source tree nests inside `packages/core/`
 (current design) or becomes a peer `pack-core/`. **Decision: keep
-`packages/core/.agent-src.uncompressed/`.** Three reasons:
+`packages/core/.agent-src.uncondensed/`.** Three reasons:
 
 1. `packages/core/` is the engine + installer + kernel rules +
    scaffolding (templates, profiles, presets, contexts, user-types).
@@ -199,7 +199,7 @@ similarity) on every moved file. Verification script enforces this.
 
 ### B3 — Consumer-facing output contract
 
-`task sync` writes `.agent-src/` (compressed) and `.augment/` (overlay)
+`task sync` writes `.agent-src/` (condensed) and `.augment/` (overlay)
 at repo root — **unchanged** location and structure. The byte-identity
 contract covers exactly these two trees plus the discovery manifest.
 What changes:

package/docs/decisions/ADR-018-trust-and-safety-layer.md

@@ -16,7 +16,7 @@ type: prospective
 **Accepted** · 2026-05-21 · external AI Council pass on the Phase 5
 roadmap (`claude-sonnet-4-5` + `gpt-4o`, `design` lens). Council
 confirmed the closed-enum trust ladder, the per-pack safety-floor
-rule, and the compressor-injected HRR banner; refinement folded into
+rule, and the condenseor-injected HRR banner; refinement folded into
 the lint script and the installer's confirm copy.
 
 Session: [`agents/runtime/council/responses/phase-5-trust-safety.json`](../../agents/runtime/council/responses/phase-5-trust-safety.json) <!-- council-ref-allowed: ADR decision-trace -->
@@ -25,7 +25,7 @@ Companion artefacts:
 - Contract: [`docs/contracts/trust-and-safety.md`](../contracts/trust-and-safety.md)
 - Roadmap: [`agents/roadmaps/monorepo-phase-5-trust-safety-layer.md`](../../agents/roadmaps/monorepo-phase-5-trust-safety-layer.md)
 - Lint: [`scripts/lint_trust_coherence.py`](../../scripts/lint_trust_coherence.py) + [`tests/test_lint_trust_coherence.py`](../../tests/test_lint_trust_coherence.py)
-- Compressor: [`scripts/compress.py`](../../scripts/compress.py) (`_inject_hrr_banner`)
+- Condenseor: [`scripts/condense.py`](../../scripts/condense.py) (`_inject_hrr_banner`)
 - Installer: [`packages/core/installer/src/trust-escalation.ts`](../../packages/core/installer/src/trust-escalation.ts)
 
 ## Context
@@ -44,7 +44,7 @@ After Phase 4 we had the **metadata** end-to-end but **no enforcement**:
 - Installer treated all packs identically — no surface for advisory
   content, no confirm step before opting into legally-flavoured
   finance / strategy material.
-- Compressor preserved frontmatter but did not propagate the
+- Condenseor preserved frontmatter but did not propagate the
   `human_review_required` signal into the compiled artefact, so the
   runtime had no parser-stable hook to gate output on.
 - Domain-specific safety floors (finance, founder-strategy,
@@ -70,10 +70,10 @@ Ship a four-piece trust & safety layer:
 1. **Closed-enum trust ladder.** `core` · `professional` · `advisory`
    · `restricted` · `experimental`. Authoritative table and meaning
    live in [`trust-and-safety § 1`](../contracts/trust-and-safety.md#-1--trust-levels).
-2. **HRR banner injection.** The compressor scans frontmatter and
+2. **HRR banner injection.** The condenseor scans frontmatter and
    prepends `<!-- agent-config:human-review-banner -->\n> HUMAN REVIEW
    REQUIRED · trust: <level> · owner: <domain>` to any artefact with
-   `trust.human_review_required: true`. Idempotent on re-compression.
+   `trust.human_review_required: true`. Idempotent on re-condensation.
 3. **Per-pack safety-floor rules.** `core` ships
    `engineering-safety-floor.md`; `pack-finance-basic` ships
    `finance-safety-floor.md`; `pack-founder-strategy` ships
@@ -97,7 +97,7 @@ Ship a four-piece trust & safety layer:
 ### Good
 
 - **Single source of trust truth.** The frontmatter field is the
-  one input; the installer, compressor, lint, and runtime all read
+  one input; the installer, condenseor, lint, and runtime all read
   it. No parallel registry, no duplicated copy.
 - **Banner is parser-stable.** The HTML-comment marker survives every
   downstream surface (Augment, Claude, Cursor, Windsurf) because it is

package/docs/decisions/ADR-019-router-json-dist-location.md

@@ -101,8 +101,8 @@ Rationale:
   `docs/contracts/explain-trace.schema.json`,
   `docs/adrs/router/0001-three-tier-routing.md`,
   `docs/adrs/smoke/0001-per-tier-smoke-scripts.md`.
-- **Source rules.** Uncompressed rule sources referencing the path
-  (`caveman-speak.md`, `git-history-discipline.md`) updated and
+- **Source rules.** Uncondensed rule sources referencing the path
+  (`telegraph-speak.md`, `git-history-discipline.md`) updated and
   re-projected.
 
 ## Reversal cost

package/docs/decisions/ADR-020-global-only-consumer-scope.md

@@ -25,7 +25,7 @@ Companion artefacts:
 - Wizard contract: [`docs/contracts/gui-wizard.md`](../contracts/gui-wizard.md)
 - Predecessor ADR: [`ADR-007`](ADR-007-agent-discovery-scopes.md) — scope precedence, global-default amendment
 - Perms entry-gate: [`scripts/lint_global_paths.py`](../../scripts/lint_global_paths.py)
-- Payload schema: [`schemas/wizard-apply-payload.schema.json`](../../schemas/wizard-apply-payload.schema.json)
+- Payload schema: [`internal/schemas/wizard-apply-payload.schema.json`](../../internal/schemas/wizard-apply-payload.schema.json)
 
 ## Context
 
@@ -65,7 +65,7 @@ fanning out from there.
 
 The single project-local exception is `agents/overrides/`, which
 remains the canonical place to override or extend a shared skill /
-rule / command per [override-management](../../.agent-src.uncompressed/skills/override-management/SKILL.md).
+rule / command per [override-management](../../.agent-src.uncondensed/skills/override-management/SKILL.md).
 
 The maintainer-side dev experience is preserved by the
 `AGENT_CONFIG_DEV_MODE=1` environment gate documented in

package/docs/decisions/ADR-021-deployment-shape.md

@@ -25,7 +25,7 @@ Companion artefacts:
 - Roadmap: [`agents/roadmaps/road-to-internal-ai-os-deployment.md`](../../agents/roadmaps/road-to-internal-ai-os-deployment.md)
 - Artefacts: [`packages/core/deploy/`](../../packages/core/deploy/)
 - Env contract: [`docs/deploy/env-vars.md`](../deploy/env-vars.md)
-- Council question (drafted, not invoked — no keys): [`agents/tmp/council-question-deployment-shape.md`](../../agents/tmp/council-question-deployment-shape.md)
+- Council question (drafted, not invoked — no keys): [`agents/tmp/council-question-deployment-shape.md`](../../agents/tmp/old/council-question-deployment-shape.md)
 - Predecessor ADR: [`ADR-016`](ADR-016-installer-architecture.md) — installer architecture (agent-mode protocol the GUI server wraps).
 
 ## Context
@@ -64,7 +64,7 @@ their own chart using this Compose as the reference until v2 ships.
 The GUI server (`packages/core/installer/src/gui/server.ts`) is the
 only long-running process. The Python install supervisor is spawned
 per-install, not a sidecar. The Compose image stays Node-only to keep
-the budget under 600 MB compressed and the surface area minimal.
+the budget under 600 MB condensed and the surface area minimal.
 
 If Phase 2+ needs a separate identity-broker process, it lands in a
 separate service in the same Compose; the agent-config container stays
@@ -141,7 +141,7 @@ orchestrator-agnostic.
 ## Open questions (council-deferred)
 
 The accompanying council question file
-[`agents/tmp/council-question-deployment-shape.md`](../../agents/tmp/council-question-deployment-shape.md)
+[`agents/tmp/council-question-deployment-shape.md`](../../agents/tmp/old/council-question-deployment-shape.md)
 has not yet been run (no provider keys configured). A maintainer with
 keys should run it and either ratify or supersede this ADR.
 

package/docs/decisions/ADR-022-daily-workspace-decomposition.md

@@ -31,7 +31,7 @@ Companion artefacts:
 
 - Roadmap: [`agents/roadmaps/road-to-employee-product-and-external-proof.md`](../../agents/roadmaps/road-to-employee-product-and-external-proof.md)
 - Council question: [`agents/decisions/open-questions/daily-workspace-shape.md`](../../agents/decisions/open-questions/daily-workspace-shape.md)
-- Council verdict: `agents/runtime/council/responses/daily-workspace-shape.json` (gitignored)
+- Council verdict: `agents/runtime/council/responses/daily-workspace-shape.json` (gitignored) <!-- council-ref-allowed: ADR decision trace -->
 - Predecessor ADRs: [`ADR-014`](ADR-014-gui-framework-choice.md) (installer chrome), [`ADR-016`](ADR-016-installer-architecture.md) (installer architecture), [`ADR-020`](ADR-020-global-only-consumer-scope.md) (consumer scope).
 
 ## Context

package/docs/decisions/ADR-027-changelog-machine-vs-manual.md

@@ -57,7 +57,7 @@ of narrative + bullets in the current convention):
 |---|---:|---:|---:|
 | **Token budget per release** | ~2.8k (141 lines × ~80 chars) | ~1.1k (38 commits × ~120 chars) | ~2.6k (same as current; bullets generated, paragraph hand-written) |
 | **Maintainer minutes per release** | 5–15 (write narrative; auto-split runs in `task release`) | 0 direct + ~30/month policing commit messages | 5–10 (paragraph only) |
-| **Information density per line** | high — narrative compresses 5–10 bullets of context | low — every infrastructure commit becomes a line | high — same as current |
+| **Information density per line** | high — narrative condenses 5–10 bullets of context | low — every infrastructure commit becomes a line | high — same as current |
 | **Parseability for downstream agents** | high — `### Features` / `### Fixes` / `### BREAKING` are semantic anchors | medium — same headings, but no narrative anchor to disambiguate scope churn | high |
 | **Hands-off failure mode** | era over-cap → auto-split fires | commit-message drift pollutes the log → no recovery without rewriting commits | narrative drift → degrades to release-please equivalent |
 
@@ -123,7 +123,7 @@ entries over a flat commit dump.
 
 - [`docs/contracts/CHANGELOG-conventions.md`](../contracts/CHANGELOG-conventions.md) — convention being confirmed.
 - [`agents/roadmaps/archive/road-to-changelog-era-auto-split.md`](../../agents/roadmaps/archive/road-to-changelog-era-auto-split.md) — closes Phase 4.
-- [`agents/runtime/council/responses/changelog-era-split-2026-05-25.json`](../../agents/runtime/council/responses/changelog-era-split-2026-05-25.json) — the originating council synthesis.
+- [`agents/runtime/council/responses/changelog-era-split-2026-05-25.json`](../../agents/runtime/council/responses/changelog-era-split-2026-05-25.json) — the originating council synthesis. <!-- council-ref-allowed: ADR decision trace -->
 - `scripts/_lib/changelog_eras.py` — shared cap + splitter (Tier 2 output).
 - `scripts/release.py:818` — `plan.changelog_body` → GitHub Release notes wire.
 - `tests/test_changelog_eras.py`, `tests/test_changelog_split.py` — gate + splitter coverage.

package/docs/decisions/ADR-028-root-layout.md

@@ -15,7 +15,7 @@ review_date: 2027-05-25
 ## Status
 
 **Accepted** · 2026-05-25. Encodes the AI Council verdict from
-[`root-cleanup-organizing-principle-2026-05-25.synthesis.md`](../../agents/runtime/council/sessions/root-cleanup-organizing-principle-2026-05-25.synthesis.md)
+[`root-cleanup-organizing-principle-2026-05-25.synthesis.md`](../../agents/runtime/council/sessions/root-cleanup-organizing-principle-2026-05-25.synthesis.md) <!-- council-ref-allowed: ADR decision trace -->
 and opens
 [`road-to-root-layout-cleanup.md`](../../agents/roadmaps/archive/road-to-root-layout-cleanup.md) (archived; complete).
 Time-boxed: review on **2027-05-25** or earlier if any trigger below fires.
@@ -48,7 +48,7 @@ conditional follow-up gated by evidence the package does not yet have.
 Re-audit of `bench/`, `evals/`, `workers/`, `user-types/` against the
 installer / projector / CI:
 
-| Dir | `scripts/install.py` | `scripts/compress.py` projection | `.github/workflows/*` | Verdict |
+| Dir | `scripts/install.py` | `scripts/condense.py` projection | `.github/workflows/*` | Verdict |
 |---|---|---|---|---|
 | `bench/` | — | — | `bench-drift.yml` (path filter) | **movable** |
 | `evals/` | — | — | — | **movable** |
@@ -91,7 +91,7 @@ Four audits must complete and pass before Phase 3 opens:
    `scripts/`, `templates/`, `config/`, `schemas/` references.
 2. **Symlink-mobility test** — verify Cursor / Claude / Windsurf
    honor symlinked projections (`.cursor/` → `./projections/.cursor/`).
-3. **Hash-sequencing audit** — confirm `.compression-hashes.json`
+3. **Hash-sequencing audit** — confirm `.condensation-hashes.json`
    uses paths that survive `.agent-src/` relocation (or document the
    regeneration migration).
 4. **CI-path audit** — every hardcoded path in
@@ -131,17 +131,17 @@ blocker.
 |---|---|
 | Move everything into `./src/` (original request) | `./src/` is the TS app per ADR-012/016. Collision. |
 | Option 2 — `./tooling/` umbrella with `templates/` / `config/` / `schemas/` | Council: cost underestimated (duplicate-then-deprecate + 2-month window + major bump); installer paths in those dirs are unaudited. |
-| Option 3 — full category-coded migration | Council hard-reject: projection mobility unproven; compression-hash sequencing risk; unshippable without symlink test. |
+| Option 3 — full category-coded migration | Council hard-reject: projection mobility unproven; condensation-hash sequencing risk; unshippable without symlink test. |
 | Option 4 — `MAP.md` documentation | Council: adds 51st entry; documentation-as-apology; AGENTS.md already serves this role. |
 | Skip Phase 1, jump to multi-workspace prototype | Loses the cheap visible win; Phase 2 audits unfunded; risks scope creep into Phase 3. |
 
 ## References
 
-- [`agents/runtime/council/questions/root-cleanup-organizing-principle-2026-05-25.md`](../../agents/runtime/council/questions/root-cleanup-organizing-principle-2026-05-25.md) — council brief.
-- [`agents/runtime/council/sessions/root-cleanup-organizing-principle-2026-05-25.synthesis.md`](../../agents/runtime/council/sessions/root-cleanup-organizing-principle-2026-05-25.synthesis.md) — full synthesis.
+- [`agents/runtime/council/questions/root-cleanup-organizing-principle-2026-05-25.md`](../../agents/runtime/council/questions/root-cleanup-organizing-principle-2026-05-25.md) — council brief. <!-- council-ref-allowed: ADR decision trace -->
+- [`agents/runtime/council/sessions/root-cleanup-organizing-principle-2026-05-25.synthesis.md`](../../agents/runtime/council/sessions/root-cleanup-organizing-principle-2026-05-25.synthesis.md) — full synthesis. <!-- council-ref-allowed: ADR decision trace -->
 - [`agents/roadmaps/archive/road-to-root-layout-cleanup.md`](../../agents/roadmaps/archive/road-to-root-layout-cleanup.md) — execution roadmap (archived; Phase 1 ✅, Phase 2 ✅, Phase 3 closed).
 - [`agents/evidence/audits/2026-05-root-layout-phase2/`](../../agents/evidence/audits/2026-05-root-layout-phase2/) — Phase 2 audit verdict bundle.
 - [`ADR-029`](ADR-029-multi-workspace-deferred.md) — Phase 3 close-out (multi-workspace deferred indefinitely).
 - [`ADR-012`](ADR-012-typescript-cli-shell.md), [`ADR-016`](ADR-016-installer-architecture.md) — `./src/` is the TS app.
 - [`ADR-019`](ADR-019-router-json-dist-location.md) — `router.json` lives in `./dist/`.
-- `scripts/install.py:52` (`USER_TYPES_DIR`), `scripts/compress.py:1106` (`AUGMENT_SYMLINK_DIRS`) — evidence pinning `user-types/` to root.
+- `scripts/install.py:52` (`USER_TYPES_DIR`), `scripts/condense.py:1106` (`AUGMENT_SYMLINK_DIRS`) — evidence pinning `user-types/` to root.

package/docs/decisions/ADR-029-multi-workspace-deferred.md

@@ -118,5 +118,5 @@ Phase 3 becomes eligible when **all** of these hold:
   full audit bundle (4 verdict files + README).
 - [`agents/roadmaps/archive/road-to-root-layout-cleanup.md`](../../agents/roadmaps/archive/road-to-root-layout-cleanup.md) —
   execution roadmap, archived (Phase 1 ✅, Phase 2 ✅, Phase 3 closed via this ADR).
-- [`agents/runtime/council/sessions/root-cleanup-organizing-principle-2026-05-25.synthesis.md`](../../agents/runtime/council/sessions/root-cleanup-organizing-principle-2026-05-25.synthesis.md) —
-  original council synthesis that proposed the multi-workspace shape.
+- [`agents/runtime/council/sessions/root-cleanup-organizing-principle-2026-05-25.synthesis.md`](../../agents/runtime/council/sessions/root-cleanup-organizing-principle-2026-05-25.synthesis.md) <!-- council-ref-allowed: ADR decision trace -->
+  — original council synthesis that proposed the multi-workspace shape.