@event4u/agent-config 3.2.0 → 4.1.0

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

@@ -0,0 +1,129 @@
+---
+adr: 027
+status: accepted
+date: 2026-05-25
+decision: changelog-machine-vs-manual
+supersedes: —
+superseded_by: —
+phase: v3.x · changelog-era-auto-split Phase 4
+type: discovery-loop-closure
+review_date: 2027-05-25
+---
+
+# ADR-027 — CHANGELOG convention — confirm manual narrative + auto-split for 12 months
+
+## Status
+
+**Accepted** · 2026-05-25. Closes Phase 4 of
+[`road-to-changelog-era-auto-split.md`](../../agents/roadmaps/archive/road-to-changelog-era-auto-split.md).
+Time-boxed: review on 2027-05-25 or earlier if a trigger below fires.
+
+## Context
+
+The AI Council that produced the auto-split design surfaced one upstream
+question: **is the manual changelog convention itself the right primitive
+for a package that bills itself as an "Universal AI Agent OS"?** Phase 4
+investigates without committing to a rewrite — either confirm
+`docs/contracts/CHANGELOG-conventions.md` + the Tier 2/3 machinery stand
+for 12 months, or draft a successor roadmap.
+
+### Step 1 — Consumer touchpoint audit
+
+Every place a consumer reads the changelog and which fields they read:
+
+| # | Surface | What the consumer sees | Field weight |
+|---|---|---|---|
+| 1 | **GitHub Release notes** | `plan.changelog_body` rendered via `scripts/release.py:818` | narrative + bullets + tests-delta |
+| 2 | **npmjs.com package page** | auto-rendered `CHANGELOG.md` (top of file) | narrative paragraph dominates the fold |
+| 3 | **packagist.org package page** | same — auto-rendered `CHANGELOG.md` | same |
+| 4 | **`README.md` footer** | link only to `CHANGELOG.md` and `releases/latest` | navigation, no content |
+| 5 | **`CHANGELOG.md` direct** | full structured entries | full Keep-a-Changelog shape |
+| 6 | **`docs/archive/CHANGELOG-pre-*.md`** | historical eras behind the active-era pointer | follow-up reads only |
+| 7 | **`agents/settings/contexts/adr-artifact-engagement.md` § L100** | guidance to write a deprecation note in `CHANGELOG.md` | governance / authoring, not consumer |
+
+`docs/getting-started-by-role.md` — not in scope. No role-pack `FIRST_WIN.md` references the changelog.
+
+**Reader insight.** Surfaces 1–3 are the high-traffic consumer surfaces.
+Each renders the *top* of the changelog: the narrative paragraph + the
+first bullet group + the tests-delta. The narrative paragraph carries
+the framing every other layer (bullets, compare-link) loses.
+
+### Step 2 — Spike comparison against the audit
+
+Three shapes, measured against the 3.2.0 release (38 commits, 141 lines
+of narrative + bullets in the current convention):
+
+| Metric | Current (manual narrative + auto-split) | (a) `release-please` fully generated | (b) Hybrid (manual paragraph + generated bullets) |
+|---|---:|---:|---:|
+| **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 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 |
+
+The fully-generated shape **loses the narrative paragraph**, which is
+the field weight #1–3 surfaces lean on. The hybrid shape is what the
+current convention *already* allows — `release-please` is just the
+extreme end of the auto-spectrum; the convention sits at a defensible
+middle.
+
+The operational cost that prompted the question (era over-cap blocking
+the release PR) is solved by Tier 2 in the same roadmap. The discovery
+question therefore reduces to: **is the narrative paragraph worth
+~2.5k tokens per release?** Audit says yes — it is the field consumers
+read first and the field that differentiates the package from bot
+output.
+
+## Decision
+
+**Confirm `docs/contracts/CHANGELOG-conventions.md` + Tier 2/3
+machinery for 12 months.** No successor roadmap.
+
+The current convention:
+
+- Keeps the **hand-written narrative paragraph** as the load-bearing
+  framing for consumer surfaces (npm, packagist, GitHub Releases).
+- Lets `scripts/release.py` generate the **bullet list** under
+  Features / Fixes / Chores / Docs / BREAKING via the auto-split flow
+  plus the existing Keep-a-Changelog shape.
+- Lets the **drift gate** (`tests/test_changelog_eras.py`) catch
+  non-release edits that grow the active era past 250 lines.
+
+The "Universal AI Agent OS" framing **argues for**, not against, a
+human-curated changelog — agents that consume `CHANGELOG.md` as a
+ground-truth of "what changed" prefer structured, semantic, framed
+entries over a flat commit dump.
+
+## Consequences
+
+- `docs/contracts/CHANGELOG-conventions.md` stands as-is. The
+  Tier 3 Step 3 "Gate-vs-script contract" subsection is the canonical
+  reference for the gate / script split.
+- No new tooling lands as a Phase 4 follow-up.
+- Review on **2027-05-25** or earlier if any trigger fires:
+  1. The narrative paragraph stops being written for two consecutive
+     releases (signal: convention is breaking down naturally).
+  2. The active-era body grows past 250 lines from non-release edits
+     more than twice in a quarter (signal: humans are bypassing the
+     gate; auto-split is no longer the right primitive).
+  3. A downstream consumer (npm/packagist/GitHub Release renderer)
+     changes how it slices the top-of-file (signal: the field weight
+     assumption above is invalidated).
+  4. Council session re-opens the question with new evidence.
+
+## Alternatives considered
+
+| Option | Why rejected |
+|---|---|
+| **`release-please` fully generated** | Loses the narrative paragraph; surfaces 1–3 lose their highest-weight field. |
+| **Hybrid (manual paragraph + generated bullets, separate tool)** | Indistinguishable from current convention in output; adds a tool boundary without changing the artefact. |
+| **Drop the changelog entirely, point to GitHub Releases** | npm / packagist auto-render `CHANGELOG.md` from the repo; deleting it degrades surfaces 2–3 to a generic placeholder. |
+
+## References
+
+- [`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. <!-- 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

@@ -0,0 +1,147 @@
+---
+adr: 028
+status: accepted
+date: 2026-05-25
+decision: root-layout
+supersedes: —
+superseded_by: —
+phase: v3.x · root-layout-cleanup Phase 1
+type: structural
+review_date: 2027-05-25
+---
+
+# ADR-028 — Root layout — targeted prune now, multi-workspace deferred behind four audits
+
+## 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) <!-- 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.
+
+## Context
+
+A request to move "everything not needed at root into `./src/`" failed
+the reality check on three counts:
+
+1. **`./src/` is occupied** — the TypeScript application (CLI · Server · UI · shared) per
+   [`ADR-012`](ADR-012-typescript-cli-shell.md) / [`ADR-016`](ADR-016-installer-architecture.md).
+   Moving general tooling into `./src/` collides with the app boundary.
+2. **`router.json` is not at root** — lives under `./dist/`, governed by
+   [`ADR-019`](ADR-019-router-json-dist-location.md). Out of scope.
+3. **`setup.sh` is the curl entry point** — referenced by external installers
+   (`bash <(curl …setup.sh)`). Discovery surface, immovable.
+
+A council session (2 members, $0.13 actual) reframed the problem:
+
+> "Root noise" is not a *discoverability* problem (GitHub paginates
+> anyway, npm consumers never see it). It is a *maintainability*
+> problem — "where do new internal tools belong?"
+
+With that reframe, the cheap-and-safe move (Option 1 — targeted prune)
+becomes obvious, and the deep restructure (multi-workspace) drops to a
+conditional follow-up gated by evidence the package does not yet have.
+
+### Consumer-contract surface check (Phase 1 scope)
+
+Re-audit of `bench/`, `evals/`, `workers/`, `user-types/` against the
+installer / projector / CI:
+
+| Dir | `scripts/install.py` | `scripts/condense.py` projection | `.github/workflows/*` | Verdict |
+|---|---|---|---|---|
+| `bench/` | — | — | `bench-drift.yml` (path filter) | **movable** |
+| `evals/` | — | — | — | **movable** |
+| `workers/` | — | — | `deploy-mcp-worker.yml` (working-dir, 6+ refs) | **movable** (CI updates only) |
+| `user-types/` | `USER_TYPES_DIR = "user-types"` (line 52) | `AUGMENT_SYMLINK_DIRS` includes `"user-types"` | — | **immovable — public contract** |
+
+`user-types/` is dropped from Phase 1 — installer + projector reference
+it as a stable root path. Surfaced during execution, not in the
+council's original scope (the council recommended all four; the audit
+narrowed it).
+
+## Decision
+
+**Two-phase strategy.** Phase 1 ships now; Phases 2–3 are conditional.
+
+### Phase 1 — Targeted Prune (immediate, ≤ 1 day, no version bump)
+
+Move into a new `./internal/` umbrella:
+
+- `bench/` → `internal/bench/`
+- `evals/` → `internal/evals/`
+- `workers/` → `internal/workers/`
+
+Update:
+
+- `.github/workflows/bench-drift.yml` — path filter.
+- `.github/workflows/deploy-mcp-worker.yml` — `working-directory` + `cache-dependency-path`.
+- `taskfiles/engine.yml`, `taskfiles/mcp.yml` — `dir:` references.
+- `AGENTS.md` — placement rule pointer.
+
+Outcome: 3 fewer root entries; zero consumer risk; precedent for
+"maintainer-internal → `./internal/`".
+
+### Phase 2 — Pre-audits (gates Phase 3, no time-box)
+
+Four audits must complete and pass before Phase 3 opens:
+
+1. **Consumer-contract audit** — GitHub code search +
+   `node_modules/@event4u/agent-config/` path probing for
+   `scripts/`, `templates/`, `config/`, `schemas/` references.
+2. **Symlink-mobility test** — verify Cursor / Claude / Windsurf
+   honor symlinked projections (`.cursor/` → `./projections/.cursor/`).
+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
+   `.github/workflows/*.yml` and `taskfiles/*.yml`.
+
+Each audit produces a verdict file under
+`agents/evidence/audits/2026-XX-root-layout-phaseN/`.
+
+### Phase 3 — Conditional multi-workspace (deferred, gated)
+
+Only if **all four audits pass**: restructure to npm-workspaces with
+`tooling/` (Python maintainer scripts), `runtime/` (TS app), and
+optionally `projections/` (host-agent configs). If any audit fails,
+Phase 3 closes as "not feasible" and a successor ADR documents the
+blocker.
+
+## Consequences
+
+- New top-level `./internal/` directory becomes the home for
+  maintainer-only tooling. `AGENTS.md` documents this with one line.
+- `.gitignore` and `eslint`/`pyproject` ignore rules updated as
+  needed.
+- The four Phase 2 audits are pre-requirements, not work. They are
+  *not* sprint tasks — they run on demand when someone wants to
+  re-open multi-workspace.
+- Review on **2027-05-25** or earlier if any trigger fires:
+  1. A new maintainer-only dir is added at root (signal: `./internal/`
+     convention is breaking down).
+  2. Phase 2 audits all return clean (signal: Phase 3 is ready).
+  3. A consumer reports breakage from a Phase 1 path change (signal:
+     audit missed a contract).
+  4. Council session re-opens the question with new evidence.
+
+## Alternatives considered
+
+| Option | Why rejected |
+|---|---|
+| 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; 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. <!-- 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/condense.py:1106` (`AUGMENT_SYMLINK_DIRS`) — evidence pinning `user-types/` to root.

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

@@ -0,0 +1,122 @@
+---
+adr: 029
+status: accepted
+date: 2026-05-25
+decision: multi-workspace-deferred
+supersedes: —
+superseded_by: —
+phase: v3.x · root-layout-cleanup Phase 3 close-out
+type: structural
+review_date: 2027-05-25
+---
+
+# ADR-029 — Multi-workspace restructure deferred; Phase 3 closed pending L0 symlink-mobility evidence
+
+## Status
+
+**Accepted** · 2026-05-25. Successor to
+[`ADR-028`](ADR-028-root-layout.md) Phase 3. Closes the multi-workspace
+restructure (Option 5 from the original council session) as **not
+feasible today**, with a re-open path documented below. Time-boxed:
+review on **2027-05-25** or earlier if any re-open trigger fires.
+
+## Context
+
+[`ADR-028`](ADR-028-root-layout.md) defined a three-phase strategy:
+
+1. **Phase 1** — move `bench/`, `evals/`, `workers/` to `internal/`. **Shipped.**
+2. **Phase 2** — run four pre-audits that gate Phase 3.
+3. **Phase 3** — conditional multi-workspace restructure
+   (`tooling/` · `runtime/` · `projections/`), only if all four
+   Phase 2 audits return clean.
+
+Phase 2 ran in the same PR as Phase 1 (under maintainer mandate).
+Verdict bundle:
+[`agents/evidence/audits/2026-05-root-layout-phase2/`](../../agents/evidence/audits/2026-05-root-layout-phase2/).
+
+| # | Audit | Verdict |
+|---|---|---|
+| 1 | Consumer-contract | ✅ Pass — published surface enumerated |
+| 2 | Symlink-mobility | ⚠️ Partial — subdirectory symlinks proven, top-level untested |
+| 3 | Hash-sequencing | ✅ Pass — source-relative keys, idempotent regeneration |
+| 4 | CI-path inventory | ✅ Pass — ~27 edit points enumerated |
+
+Audit 2 is the blocker. The multi-workspace option requires
+**L0 symlinks** (tool root directory itself becomes a symlink, e.g.
+`.cursor/ → projections/.cursor/`). The package today only proves
+**L1 symlinks** (subdirectory level, e.g. `.augment/skills/ →
+../.agent-src/skills/`). L0 has never been tested against current
+Cursor, Claude Code, or Windsurf builds — and one of those three
+(Augment Code) is already known to refuse symlinked rule files at L1,
+which is the precedent that motivates the audit in the first place.
+
+Without L0 evidence, executing Phase 3 would either ship a broken
+projection for at least one host agent or force a fallback to
+per-directory copies that defeat the "single source of truth" win the
+multi-workspace shape is meant to deliver.
+
+## Decision
+
+**Defer Phase 3 indefinitely.** Close the Phase 3 roadmap step as "not
+feasible today". Keep the audit bundle as the canonical evidence base
+so that a future maintainer can re-open the question without redoing
+the work.
+
+The four root-layout claims survive Phase 1 unchanged:
+
+- `bench/`, `evals/`, `workers/` are gone from root (under `internal/`).
+- `user-types/` stays at root (immovable per Audit 1 + ADR-028).
+- Top-level tool roots (`.augment/`, `.cursor/`, `.claude/`, `.clinerules/`)
+  stay as real directories with L1 symlinks pointing at `.agent-src/`.
+- The "maintainer-internal → `./internal/`" precedent is the new
+  placement rule for new internal dirs (already in `AGENTS.md`).
+
+## Re-open conditions
+
+Phase 3 becomes eligible when **all** of these hold:
+
+1. A maintainer (or community contributor) runs the L0 symlink test
+   documented in
+   [`02-symlink-mobility.md`](../../agents/evidence/audits/2026-05-root-layout-phase2/02-symlink-mobility.md)
+   against current Cursor + Claude Code + Windsurf, captures the
+   result, and amends Audit 2 to ✅ or ❌.
+2. If Audit 2 lands ✅: the ~27 CI-path edit points from Audit 4 are
+   accepted as in-scope for the migration window; no new hardcoded
+   paths added in the interim invalidate the inventory.
+3. A council session synthesizes the updated verdict bundle and
+   produces a fresh recommendation (multi-workspace vs. stay-as-is).
+4. The maintainer accepts the deprecation cycle cost (installer
+   version bump + dual-write window for the projection contract).
+
+## Consequences
+
+- The root layout stabilizes at the Phase 1 shape for ≥ 1 year (the
+  `2027-05-25` review date).
+- New maintainer-internal directories go under `internal/`. New
+  tooling that needs to ship to consumers goes under `scripts/`,
+  `config/`, or a new top-level entry that earns its own ADR.
+- The `projections/` umbrella idea is **not dead** — it is gated on
+  fresh L0 evidence, not on a new design decision.
+- The four audit files are reusable: Audit 1 (consumer surface),
+  Audit 3 (hash portability), and Audit 4 (CI path inventory) remain
+  valid until a structural change invalidates them; only Audit 2
+  needs runtime re-verification.
+
+## Alternatives considered
+
+| Option | Why rejected |
+|---|---|
+| Execute Phase 3 anyway with L0 untested | Ships projection breakage to one of three host agents in the worst case; the win (single source of truth) collapses if any agent forces a fallback to copies. |
+| Run the L0 test in CI | The L0 test requires the host agent's runtime (Cursor / Claude Code IDE plugins); CI cannot exercise it. |
+| Defer **all** of Phase 3 to a separate roadmap | Phase 2 already produced the audit bundle; closing Phase 3 with an ADR captures the verdict without leaving a stale roadmap open. |
+| Re-shape Phase 3 as L1-only | The council's recommendation specifically called out the `projections/` umbrella, which requires L0. Re-shaping to L1-only is a different decision the council did not weigh; would need a fresh council session. |
+
+## References
+
+- [`ADR-028`](ADR-028-root-layout.md) — parent decision.
+- [`agents/evidence/audits/2026-05-root-layout-phase2/`](../../agents/evidence/audits/2026-05-root-layout-phase2/) —
+  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) <!-- council-ref-allowed: ADR decision trace -->
+  — original council synthesis that proposed the multi-workspace shape.

package/docs/decisions/ADR-rule-kernel-and-router.md

@@ -40,13 +40,13 @@ size budgets.
 - **Budget gates:** `task lint-rule-budget` enforces kernel ≤ 26k chars
   and per-rule ≤ 2.5k (Iron-Law overrides up to 4.0k via ADR-002).
   Daily snapshots in `agents/runtime/.rule-budget-history.jsonl`.
-- **Compression discipline:** P4.3 brought the auto-bucket from
+- **Condensation discipline:** P4.3 brought the auto-bucket from
   ~75k → 59 220 chars (under the 60k target) without behaviour drift.
 
 ### What we cut
 
 - **P4.1 / P4.2** — auto-rule → skill / guideline migrations.
-  Cancelled as scope-cut after P4.3 compression alone landed the
+  Cancelled as scope-cut after P4.3 condensation alone landed the
   auto-bucket under target. The migrations were a means, not an end.
 - **road-to-package-optimization Phase 1.2 / 1.3 / Phase 2 / Phase 3**
   — cancelled per P1.1's binary acceptance gate. The prototype
@@ -61,9 +61,9 @@ size budgets.
 ### What stayed
 
 - All Iron-Law fences. SHA-verified preserved by
-  `scripts/iron_law_sha.py` across the kernel compression pass.
+  `scripts/iron_law_sha.py` across the kernel condensation pass.
 - Behaviour parity. Golden transcripts pass under all three profiles.
-- The pre-existing `auto`-tier rules; only their compressed bodies
+- The pre-existing `auto`-tier rules; only their condensed bodies
   changed, never their obligation surface.
 
 ## Profile semantics
@@ -89,7 +89,7 @@ If the Kernel + Router model needs unwinding:
    running `compile_router.py --no-router` returns the always-loaded
    model.
 
-No data migration, no irreversible compression. Iron-Law SHA fences
+No data migration, no irreversible condensation. Iron-Law SHA fences
 mean Iron Laws can be diffed against the pre-roadmap baseline at any
 point.
 

package/docs/decisions/INDEX.md

@@ -25,6 +25,14 @@ _Auto-generated by `scripts/adr/regenerate_index.py`. Do not edit._
 | [ADR-019](ADR-019-router-json-dist-location.md) | Router Json Dist Location | accepted | 2026-05-23 | — |
 | [ADR-020](ADR-020-global-only-consumer-scope.md) | Global Only Consumer Scope | accepted | 2026-05-23 | — |
 | [ADR-021](ADR-021-deployment-shape.md) | Deployment Shape | accepted | 2026-05-24 | — |
+| [ADR-022](ADR-022-daily-workspace-decomposition.md) | Daily Workspace Decomposition | accepted | 2026-05-24 | — |
+| [ADR-023](ADR-023-host-agent-protocol.md) | Host Agent Protocol | accepted | 2026-05-24 | — |
+| [ADR-024](ADR-024-workspace-v0-feature-floor.md) | Workspace V0 Feature Floor | accepted | 2026-05-24 | — |
+| [ADR-025](ADR-025-workspace-chrome.md) | Workspace Chrome | accepted | 2026-05-24 | — |
+| [ADR-026](ADR-026-explain-mode-translation.md) | Explain Mode Translation | accepted | 2026-05-24 | — |
+| [ADR-027](ADR-027-changelog-machine-vs-manual.md) | Changelog Machine Vs Manual | accepted | 2026-05-25 | — |
+| [ADR-028](ADR-028-root-layout.md) | Root Layout | accepted | 2026-05-25 | — |
+| [ADR-029](ADR-029-multi-workspace-deferred.md) | Multi Workspace Deferred | accepted | 2026-05-25 | — |
 
 ## Unnumbered (legacy)
 

package/docs/deploy/team-deployment-posture.md

@@ -58,6 +58,26 @@ them**. The cancellations stand:
 | **Team-shared overrides server** | Shared-overrides-via-git already works for the small-team case. Server only makes sense once the org-mode threshold is reached. | `road-to-team-context.md` |
 | **OAuth connectors (Google, Slack, M365)** | Per-connector OAuth flow is a permanent footprint we can't ship without an org user agreeing to scope it. | `road-to-internal-connectors.md` |
 
+### 2026-05 feedback citation — same three asks, same Hard-Floor
+
+The 9.3/10 feedback round (delivered in chat 2026-05-25) re-affirmed
+the same three P0 items the cancellations cover: OAuth knowledge
+connectors, IAM / org mode with admin roles + quotas + audit
+retention, and organization-shared memory. The verbatim asks land on
+the same Hard-Floor wall — no funded audit, no recruited team
+customer, no scope to adopt auth-adjacent code into the package.
+
+| 9.3/10 ask | Verbatim phrasing (2026-05-25) | Maps to cancellation |
+|---|---|---|
+| OAuth knowledge connectors | "GitHub / Jira / Confluence connectors so the team's docs join the agent's knowledge index" | `road-to-internal-connectors.md` |
+| IAM / org governance | "user accounts + admin roles + quotas + audit retention" | `road-to-team-sso.md` + `road-to-central-policy.md` |
+| Organization-shared memory | "team-wide memory so what one engineer answers, the next one inherits" | `road-to-team-context.md` |
+
+Each row carries the same three release gates: **recruited customer
++ funded audit + maintainer ADR**. Until all three are met, the
+cancellation stands. Feedback rounds 11+ that re-ask the same
+questions land on this row directly.
+
 Each successor roadmap is an empty-named stub today; activation
 requires a recruited team customer plus a human-reviewed security
 audit. Until then, the answer to "team SSO when?" is: **not on this

package/docs/development.md

@@ -3,14 +3,14 @@
 ## Prerequisites
 
 - [Task](https://taskfile.dev/) (task runner)
-- Python 3.10+ (for linter, compression tools)
+- Python 3.10+ (for linter, condensation tools)
 - Bash (for install scripts, tests)
 
 ## Editing content
 
-1. **Always edit in `.agent-src.uncompressed/`** — never in `.agent-src/` or `.augment/` directly
+1. **Always edit in `.agent-src.uncondensed/`** — never in `.agent-src/` or `.augment/` directly
 2. Run `task sync` to copy non-`.md` files
-3. Use the `/compress` command to compress changed `.md` files
+3. Use the `/condense` command to condense changed `.md` files
 4. Run `task ci` to verify everything passes before pushing
 
 ---
@@ -30,15 +30,15 @@ task consistency               # Verify sync + generated tool outputs are clean
 task consistency-fix           # Regenerate all derived outputs from source
 ```
 
-### Sync & Compression
+### Sync & Condensation
 
 ```bash
-task sync                      # .agent-src.uncompressed/ → .agent-src/, then project → .augment/
-task sync-changed              # List .md files changed since last compression
+task sync                      # .agent-src.uncondensed/ → .agent-src/, then project → .augment/
+task sync-changed              # List .md files changed since last condensation
 task sync-check                # Check if .agent-src/ is in sync (for CI)
-task sync-check-hashes         # Verify compressed .md hashes match source
-task sync-mark-done <file>     # Mark a single file as compressed
-task sync-mark-all-done        # Mark ALL files as compressed
+task sync-check-hashes         # Verify condensed .md hashes match source
+task sync-mark-done <file>     # Mark a single file as condensed
+task sync-mark-all-done        # Mark ALL files as condensed
 task sync-clean-hashes         # Remove stale hashes for deleted source files
 ```
 
@@ -54,7 +54,7 @@ task clean-tools               # Remove all generated tool directories
 ```bash
 task test                      # Run all tests (bash + Python)
 task test-install              # Install script integration tests
-task test-python               # Compression and linter tests
+task test-python               # Condensation and linter tests
 task test-linter               # Skill linter unit tests
 task test-readme-linter        # README linter unit tests
 task test-runtime              # Runtime registry + dispatcher tests
@@ -85,14 +85,14 @@ task lint-skills-strict        # Lint with warnings as failures
 task lint-skills-changed       # Lint only changed files
 task lint-skills-report        # Per-file quality breakdown
 task lint-skills-regression    # Compare against main branch (detect regressions)
-task lint-skills-pairs         # Check compression quality (source vs compressed)
+task lint-skills-pairs         # Check condensation quality (source vs condensed)
 task lint-readme               # Lint README.md
 ```
 
 ### Quality Checks
 
 ```bash
-task check-compression         # Verify code blocks, headings, frontmatter preserved
+task check-condensation         # Verify code blocks, headings, frontmatter preserved
 task check-refs                # No broken cross-references
 task check-portability         # No project-specific references in shared files
 task quality-report            # Per-artifact-type quality scores
@@ -167,8 +167,8 @@ scripts/
 ├── install.py                 ← Bridge files stage (.agent-settings.yml, JSONs)
 ├── postinstall.sh             ← npm postinstall hook → scripts/install
 ├── setup.sh                   ← One-time Composer hook setup
-├── compress.py                ← Compression hash management
-├── check_compression.py       ← Compression quality checker
+├── condense.py                ← Condensation hash management
+├── check_condensation.py       ← Condensation quality checker
 ├── skill_linter.py            ← Skill/rule/command linter
 ├── lint_regression.py         ← Branch regression detection
 ├── generate_tools.sh          ← Generate tool-specific directories
@@ -190,7 +190,7 @@ tests/
 └── consistency.yml            ← Sync + hash + tool verification
 templates/consumer-settings/   ← Settings templates for consumer projects
 
-.agent-src.uncompressed/         ← Source of truth (human-readable, verbose)
+.agent-src.uncondensed/         ← Source of truth (human-readable, verbose)
 ├── rules/                     ← Behavior rules
 ├── skills/                    ← Skill definitions (SKILL.md per skill)
 ├── commands/                  ← Slash command definitions
@@ -198,8 +198,8 @@ templates/consumer-settings/   ← Settings templates for consumer projects
 ├── templates/                 ← Document scaffolds
 └── contexts/                  ← System knowledge documents
 
-.agent-src/                    ← Compressed output (token-efficient, shipped)
-├── (same structure)           ← Compressed .md + copied non-.md files
+.agent-src/                    ← Condensed output (token-efficient, shipped)
+├── (same structure)           ← Condensed .md + copied non-.md files
 
 .augment/                      ← Local projection for Augment Code (gitignored)
 ├── rules/                     ← Real file copies (Augment cannot load symlinked rules)

package/docs/distribution/registries.md

@@ -20,6 +20,38 @@ Use this exact text for the awesome-list entry. Adjust the link anchor per direc
 - [event4u/agent-config](https://github.com/event4u-app/agent-config#readme) — Universal AI Agent OS. Audited skills, governance rules, commands, and templates for Claude Code, Cursor, Windsurf, Copilot. Bring your own provider.
 ```
 
+## PR body update — 3.2.0 reality
+
+When the maintainer opens the PR / posts the directory entry, the
+description block carries the concrete reality the 3.2.0 review
+named. Reviewer verbatim quote: *"deutlich mehr vorzuweisen als bei
+jedem vorherigen Erwähnungszeitpunkt."* The numbers below mirror the
+3.2.0 release notes and the `task adoption:status` snapshot from
+that release; refresh them before posting if a later release has
+shipped.
+
+```
+event4u/agent-config 3.2.0 ships:
+
+- 4929 tests across Python + TypeScript matrix (Linux + macOS).
+- /knowledge cluster — local-only document ingestion via markitdown;
+  per-namespace memory_retrieve with trust scoring.
+- Three role experiences (galabau / content-creator / consultant) +
+  daily workspace browser surface in the modern Preact shell.
+- Cinematic AI-video pipeline (/video:from-script, /video:scene,
+  /video:storyboard, /video:stitch) — provider-agnostic; dry-run
+  default; the package never sees API keys.
+- 9 Iron-Law rules + tier-1/2 routed kernel; ai-council
+  second-opinion loop for high-impact decisions.
+
+Bring your own provider (Anthropic / OpenAI / Google / Cloudflare).
+No SaaS; no remote sync; npx-quickstart installs in ~3 minutes.
+```
+
+Drop this block into the PR description once and reuse it across
+the three registries; it is the "deutlich mehr vorzuweisen" frame
+condensed to a half-screen.
+
 ## Submission checklist
 
 Before opening any submission PR: