@event4u/agent-config 9.8.0 → 9.9.0

package/docs/anti-reskin-gate.md

@@ -1,60 +0,0 @@
-# Anti-reskin gate for your skills repo
-
-If you maintain a catalog of AI-agent skills and accept community PRs, your
-failure mode is the **find-replace re-skin**: an existing skill resubmitted
-with "Laravel" → "Symfony", "Vietnam" → "Korea", new name, same substance.
-Keyword-cosine and token-Jaccard checks miss it; manual review does not scale
-past a handful of PRs per month.
-
-This package ships the gate that catches it: `lint_originality` — an
-entity-neutralized shingle-overlap linter. Framework / vendor / region proper
-nouns are neutralized before comparing 8-word shingles, so the swap does not
-move the score: a re-skin scores ~100 % overlap while the worst legitimate
-pair in a 496-artifact corpus scores 40 %. Class templates and
-document-frequency boilerplate are subtracted, so shared scaffolding never
-scores. The `--changed` mode is batch-masking-hardened: a batch of
-near-identical submissions cannot classify its own shared shingles as
-boilerplate (regression-locked in `tests/scripts/lint_originality.test.ts`).
-
-It runs as a blocking PR gate on this repo (`originality-gate` job in
-[`.github/workflows/skill-lint.yml`](../.github/workflows/skill-lint.yml)).
-
-## Run it on your own catalog — today
-
-The tool is not yet a standalone package; it runs from a clone. The corpus
-roots are fixed (`src/skills/*/SKILL.md`), so you stage your skills into one:
-
-```bash
-git clone --depth 1 https://github.com/event4u-app/agent-config
-cd agent-config && npm ci
-
-# Stage your catalog into the skills corpus root (one dir per skill):
-for f in /path/to/your-repo/skills/*/SKILL.md; do
-  d="src/skills/ext-$(basename "$(dirname "$f")")"
-  mkdir -p "$d" && cp "$f" "$d/SKILL.md"
-done
-
-# Compare your skills against each other (and this corpus) in one pass:
-./scripts-run src/scripts/lint_originality --changed src/skills/ext-*/SKILL.md
-```
-
-Exit `1` with an offending pair + overlap % means a re-skin; exit `0` means no
-same-class pair exceeds the 40 % warn floor. Thresholds are env-overridable
-(`ORIGINALITY_FAIL`, `ORIGINALITY_WARN`).
-
-## Want this as a zero-config `npx` tool?
-
-We will extract `lint_originality` as a standalone zero-config package
-(`--changed` mode for PR CI, no repo coupling, regression suite included) **if
-there is real demand** — the bet is settled by a measured floor, not opinion:
-
-- **Signal:** open an issue on this repo titled `anti-reskin gate: standalone
-  request` (or reference `lint_originality` in an issue/PR about your own
-  catalog).
-- **Floor:** ≥ 3 distinct external maintainers signal within 90 days of this
-  page landing on `main` → we ship the extraction.
-- **Kill criterion:** floor missed → extraction is cancelled and recorded;
-  this page stays as the run-from-clone recipe.
-
-Contract: [`docs/contracts/adoption-signal-floor.md` § Extraction demand
-gate](contracts/adoption-signal-floor.md#extraction-demand-gate--lint_originality-standalone-probe).

package/docs/architecture/augment-projection.md

@@ -1,70 +0,0 @@
-# Pipeline B — Augment projection
-
-> **Scope:** project the shipped `dist/agent-src/` payload into the
-> `.augment/` tree that Augment Code (CLI + IDE) reads on startup.
-
-## Input → Transform → Output
-
-```
-dist/agent-src/**                      ← Condensed payload (shipped in @event4u/agent-config)
-    ↓ scripts/condense.py:project_to_augment()
-.augment/**                        ← Local projection (gitignored on consumer side)
-    rules/                         ← copies (Augment historically does not load symlinked rules)
-    skills/ commands/ contexts/
-    personas/ templates/           ← symlinks into dist/agent-src/<dir>/
-    docs/guidelines/               ← symlink → docs/guidelines/ (only docs/ subdir exposed)
-```
-
-The default mode is **copy-rules-symlink-everything-else**. The toggle
-`augment.rules_use_symlinks: true` in `.agent-settings.yml` flips
-rules to symlinks once the host supports it. The toggle is honored by
-both [`scripts/install.sh`](../../src/scripts/install.sh) on the consumer
-side and `project_to_augment()` in the package's own self-projection.
-
-Cross-references inside `dist/agent-src/rules/*.md` use **relative paths
-from `dist/agent-src/rules/`** (e.g. `../contexts/execution/foo.md`).
-After projection, those paths resolve through the symlinks in
-`.augment/`. The host agent reads `.augment/`, follows the symlink to
-`dist/agent-src/`, and lands on the payload.
-
-## Entry points
-
-| Surface | Command |
-|---|---|
-| Project self-projection | `task sync` (`project_to_augment()` step) — [`taskfiles/content.yml:4`](../../taskfiles/content.yml) |
-| Standalone project-augment | `task project-augment` — [`taskfiles/content.yml:23`](../../taskfiles/content.yml) |
-| Consumer install | `scripts/install.sh` (delegates to `scripts/install.py`) |
-| Direct script | `./scripts-run src/scripts/condense --project-augment` |
-
-## Invariants
-
-1. **`.augment/rules/` are real files** by default — symlinks break
-   Augment's rule loader on current versions.
-2. **Symlink targets exist** — `task sync-check` verifies every
-   `.augment/` symlink resolves into `dist/agent-src/`.
-3. **Single docs subtree** — only `docs/guidelines/` is exposed; the
-   `docs/contracts/` and `docs/decisions/` trees stay package-internal
-   (rules inline 2–3 line excerpts instead of linking out).
-4. **Idempotent** — re-running projection on a clean tree must
-   produce no diff. Enforced by CI.
-
-## Failure modes
-
-| Symptom | Cause | Fix |
-|---|---|---|
-| Rule not loading in Augment | rule was symlinked instead of copied | unset `augment.rules_use_symlinks` or re-run `task project-augment` |
-| Broken `load_context:` path | symlink target missing in `dist/agent-src/` | run `task sync` first (Pipeline A must succeed) |
-| `task sync-check` fails on clean tree | source edited but `.augment/` not regenerated | `task sync` |
-| Stale skill / command in `.augment/` after rename in source | projection didn't clean orphans | `task project-augment` re-runs cleanup |
-
-## Proving the pipeline
-
-- [`tests/test_condense.py`](../../tests/test_condense.py) §
-  `test_project_to_augment_rules_mode_toggle` and surrounding cases
-  — exercises both copy-mode and symlink-mode for rules; verifies
-  symlink targets for skills / commands / contexts.
-- [`scripts/smoke_path_resolution.py`](../../src/scripts/smoke_path_resolution.py)
-  — walks `.augment/rules/*.md` and resolves every `load_context:`
-  entry; non-zero exit means a consumer would see the same break.
-
-← [Architecture overview](../architecture.md)

package/docs/architecture/claude-bundle.md

@@ -1,77 +0,0 @@
-# Pipeline D — Claude.ai cloud bundle
-
-> **Scope:** package shipped skills into Anthropic Skills ZIP bundles
-> for upload to Claude.ai Web or the Skills API. Cloud-side surfaces
-> have no filesystem access, so the builder applies sandbox-aware
-> transformations not needed in the on-disk projections.
-
-## Input → Transform → Output
-
-```
-dist/agent-src/skills/<id>/SKILL.md     ← Condensed skill (+ supporting assets)
-    ↓ scripts/build_cloud_bundle.py
-dist/cloud/<skill>.zip              ← Anthropic Skills bundle (Claude.ai Web / Skills API)
-```
-
-Per-skill tier classification comes from
-[`scripts/audit_cloud_compatibility.py`](../../src/scripts/audit_cloud_compatibility.py):
-
-| Tier | Bundle action |
-|---|---|
-| **T1** | Bundle as-is — pure guidance, sandbox-safe |
-| **T2** | Bundle with prepended sandbox note + package-internal path-swap |
-| **T3-S** | Same as T2; optional script calls degrade gracefully on cloud |
-| **T3-H** | **Skipped** — cloud-aware variant required before bundling |
-
-Cloud-side caps enforced by the builder:
-
-- `description` ≤ 200 chars (Claude.ai Web display limit).
-- 1024-char hard cap (Anthropic Skills API spec).
-- Sandbox note explains to the agent that `dist/agent-src/`, `agents/`,
-  and `task …` references are descriptive — the host has no
-  filesystem access.
-
-## Entry points
-
-| Surface | Command |
-|---|---|
-| Build one skill | `task build-cloud-bundle -- SKILL=<id>` ([`taskfiles/engine.yml:184`](../../taskfiles/engine.yml)) |
-| Build all eligible | `task build-cloud-bundles-all` ([`taskfiles/engine.yml:189`](../../taskfiles/engine.yml)) |
-| CI dry-run | `task ci-cloud-bundle` ([`taskfiles/engine.yml:194`](../../taskfiles/engine.yml)) |
-| Tier audit only | `task audit-cloud` ([`taskfiles/engine.yml:199`](../../taskfiles/engine.yml)) |
-
-## Invariants
-
-1. **No T3-H bundles** — high-coupling skills are skipped, never
-   silently bundled with broken expectations.
-2. **Description budget enforced** — overlong descriptions fail
-   the build (and CI via `ci-cloud-bundle --check`).
-3. **Package-internal paths swapped** — references to `dist/agent-src/`,
-   `scripts/`, `agents/` are rewritten to descriptive form so the
-   cloud agent does not attempt filesystem access.
-4. **`mcp_scope: lite`** — bundles tagged `lite` may not reference
-   MCP servers that require local stdio (per
-   [`docs/contracts/mcp-cloud-scope.md`](../contracts/mcp-cloud-scope.md)).
-5. **Deterministic ZIP** — same skill input produces identical
-   archive bytes (modulo timestamps, normalized in the builder).
-
-## Failure modes
-
-| Symptom | Cause | Fix |
-|---|---|---|
-| `ci-cloud-bundle` fails on a skill | description > 200 chars, or T3-H detected | shorten frontmatter, or add cloud variant |
-| `frontmatter.description` reflows to the prompt unexpectedly | over the 200-char Claude.ai cap (hard 1024) | tighten the description |
-| Bundle references `dist/agent-src/` in body | path-swap rule missing | extend `build_cloud_bundle.py` rewrite table |
-| Skill silently dropped from `dist/cloud/` | T3-H tier (cloud-unsafe) | author a cloud-aware variant, re-classify |
-
-## Proving the pipeline
-
-- [`tests/test_build_cloud_bundle.py`](../../tests/test_build_cloud_bundle.py)
-  — covers tier filtering, sandbox-note injection, path-swap, and
-  description-cap enforcement.
-- [`tests/test_claude_desktop_bundler.py`](../../tests/test_claude_desktop_bundler.py)
-  — complementary coverage for the Claude Desktop bundle surface.
-- CI gate: `task ci-cloud-bundle` runs the builder in `--check` mode
-  on every PR.
-
-← [Architecture overview](../architecture.md)

package/docs/architecture/current-onboard-baseline.md

@@ -1,126 +0,0 @@
-# Current `/onboard` Baseline (pre-step-15)
-
-> **Status:** descriptive baseline · **Owner:** package maintainer ·
-> **Last reviewed:** 2026-05-16
->
-> Documents the **current** `/onboard` flow so the Phase 1 Guided
-> Setup Wizard (step-15 item 2) has a baseline to extend. Council v3
-> unique finding (cannot "extend" an undocumented surface). This file
-> describes what ships today; it is **not** a proposal.
-
-## Surface
-
-`/onboard` lives at [`.agent-src.uncondensed/commands/onboard.md`](../../.agent-src.uncondensed/commands/onboard.md)
-(canonical source) and is triggered by the
-[`onboarding-gate`](../../dist/agent-src/rules/onboarding-gate.md) rule on
-the first turn when `onboarding.onboarded == false` in
-`.agent-settings.yml`. Cloud surfaces (Claude.ai Web, Skills API): fully
-inert — no settings file, no flow.
-
-## The 12 steps today
-
-| # | Step | Captures | Asked if |
-|---|---|---|---|
-| 1 | Greet + set expectations | — | always |
-| 2 | Offer user-global cross-project defaults | intent flag for step 9 | first-time-setup heuristic only |
-| 3 | `personal.user_name` | first name | unset |
-| 4 | `personal.ide` (+ auto-detect via `ps aux`) and `personal.open_edited_files` | IDE id, auto-open flag | unset |
-| 5 | `personal.pr_comment_bot_icon` | bool | always (no detection possible) |
-| 6 | `personal.rtk_installed` (via `which rtk`) | bool + install action | rtk not found |
-| 7 | `rule_loading_tier` and `pipelines.skill_improvement` | profile id, learning bool | always (one summary screen) |
-| 8 | Mark `onboarding.onboarded: true` | — | always |
-| 9 | Write user-global `~/.event4u/agent-config/agent-settings.yml` | six whitelisted keys | step 2 captured "yes" |
-| 10 | Summary block | — | always |
-| 11 | Quickstart pointer (`/work` and `/implement-ticket`) | — | local only |
-| 12 | Maintainer telemetry hint (opt-in) | — | local only |
-
-## What `/onboard` does **not** capture today
-
-Step-15 Phase 1 item 2 introduces a new role-selection step ("8 options
-covering Software / Content / Founder / Consulting / Marketing / Finance
-/ Handwerk / Self-configure") that produces a `user_type`. Today, no
-`user_type` is captured. Specifically:
-
-- **No audience/role question.** `/onboard` knows the developer's name,
-  IDE, and rtk install status — never the audience taxonomy.
-- **No `profile.id`.** `profile.id` does not exist as a key in
-  `.agent-settings.yml`. Per
-  [ADR-010](../decisions/ADR-010-profile-pack-preset-boundary.md), it
-  is owned by the Phase 1 item 1 profile loader.
-- **No `preset.id`.** Same status — `preset.id` arrives with Phase 1
-  item 4.
-- **No `pack.id`.** Arrives with Phase 2 item 7.
-- **No risk-appetite question.** The current flow defers risk posture
-  to `personal.autonomy`, which is itself not part of the onboard
-  questions (it inherits the template default).
-- **No stack question.** Stack is inferred at runtime by detectors
-  (`scripts/detect/*`), not asked here.
-
-## Settings keys written today
-
-```yaml
-personal:
-  user_name: "<first-name>"        # step 3
-  ide: "code|phpstorm|cursor"       # step 4
-  open_edited_files: true|false     # step 4
-  pr_comment_bot_icon: true|false   # step 5
-  rtk_installed: true|false         # step 6
-rule_loading_tier: "balanced"             # step 7 (default unchanged)
-pipelines:
-  skill_improvement: true            # step 7 (default unchanged)
-onboarding:
-  onboarded: true                    # step 8
-```
-
-User-global file (step 9, opt-in): the six whitelisted keys in
-[`scripts/_lib/agent_settings.py`](../../src/scripts/_lib/agent_settings.py)
-— `name`, `ide`, `rule_loading_tier`, `personal.bot_icon`,
-`personal.autonomy`, `telegraph.speak_scope`.
-
-## Iron Laws today
-
-- **One question per turn** ([`ask-when-uncertain`](../../dist/agent-src/rules/ask-when-uncertain.md)).
-- **Re-runnable** — invoking `/onboard` when `onboarded: true` walks the
-  flow again, never silently rewrites a value (asks before overwriting
-  `user_name` / `ide`).
-- **Never commits** — `.agent-settings.yml` is git-ignored.
-- **User-global write is opt-in + one-shot + never silent** — step 2
-  captures intent, step 9 re-confirms.
-
-## Gaps the wizard (Phase 1 item 2) must close
-
-1. **Add role-selection step** producing a `user_type` (later mapped to
-   `profile.id`). Eight options covering Software / Content / Founder /
-   Consulting / Marketing / Finance / Handwerk / Self-configure.
-   Inserted **before** step 8 (mark onboarded) so the profile loader
-   has a value to read on the next session start.
-2. **Add stack-detection confirmation step.** Run the existing
-   `scripts/detect/*` detectors, present the result, allow the user
-   to override. Without confirmation, profile-aware presets cannot
-   resolve.
-3. **Add risk-appetite question.** Maps to `preset.id` from
-   [`config-presets.md`](../contracts/config-presets.md). Three
-   options: `fast` / `balanced` / `strict`.
-4. **Write the new keys.** `profile.id`, `preset.id`, optionally
-   `pack.id`, plus the user-typed `user_type` as a stable audit field.
-
-## Wizard contract (Phase 1 item 2 acceptance)
-
-The wizard MUST:
-
-- Preserve every existing step semantically (no silent removal).
-- Insert role + stack + risk-appetite questions **before** step 8.
-- Honor the one-question-per-turn Iron Law.
-- Write `profile.id`, `preset.id`, and `user_type` to
-  `.agent-settings.yml` using the section-aware merge rules.
-- Be re-runnable (idempotent for unchanged answers).
-- Work offline (no network call required for any question).
-- Skip itself on cloud surfaces (inherit current cloud-noop behavior).
-
-## See also
-
-- [`/onboard` command](../../.agent-src.uncondensed/commands/onboard.md) — canonical source.
-- [`onboarding-gate`](../../dist/agent-src/rules/onboarding-gate.md) — trigger rule.
-- [`ADR-010`](../decisions/ADR-010-profile-pack-preset-boundary.md) — boundary the wizard must respect.
-- [`config-presets.md`](../contracts/config-presets.md) — preset axis the wizard writes.
-- [`agents/roadmaps/step-15-product-refinement.md`](../../agents/roadmaps/step-15-product-refinement.md) — Phase 1 item 2.

package/docs/architecture/current-safety-behavior.md

@@ -1,137 +0,0 @@
-# Current Safety Behavior — Baseline (pre-step-15)
-
-> **Status:** descriptive baseline · **Owner:** package maintainer ·
-> **Last reviewed:** 2026-05-16
->
-> Documents the **current** safety / autonomy surface so the Phase 2
-> Universal Safety Model ADR (step-15 item 9) has a baseline to diff
-> against. Council v3 action #4 prerequisite. This file describes what
-> ships today; it is **not** a proposal for what should ship next.
-
-## Scope
-
-The current package has **one autonomy switch** plus **four
-non-overridable floors**. The Phase 2 ADR will replace the single switch
-with per-profile, per-domain `deny / ask / allow` declarations. Before
-that ADR can specify "replace X", X has to be written down.
-
-## The one switch — `personal.autonomy`
-
-**Where defined:** `.agent-settings.yml` under `personal.autonomy`.
-Template: `src/config/agent-settings.template.yml`.
-
-**Values:** `on` · `off` · `auto`.
-
-**Read site:** [`dist/agent-src/rules/autonomous-execution.md`](../../dist/agent-src/rules/autonomous-execution.md)
-(Iron-Law rule, kernel-loaded in every profile). Cached on the first
-turn; missing key treated as `on`.
-
-**What it gates:** trivial workflow questions (suppression). Examples:
-"Should I run the tests now?", "Should I create the branch?", "Continue
-with the next phase?". These are suppressed when `autonomy` resolves to
-`on`.
-
-**What it does NOT gate:** any of the four floors below, any
-[`scope-control`](../../dist/agent-src/rules/scope-control.md) git operation,
-or any [`commit-policy`](../../dist/agent-src/rules/commit-policy.md) commit
-default. The switch only narrows the **trivial-question** surface.
-
-### State table
-
-| State | Behavior on trivial workflow questions | Blocking / Hard-Floor / Commit gates |
-|---|---|---|
-| `on` | **Suppress** — agent acts, surfaces what it did | Unchanged — still apply |
-| `off` | **Ask** — numbered options, single question | Unchanged — still apply |
-| `auto` | Same as `off` until the user opts in via a standing autonomy directive ("just work", "arbeite eigenständig"). Then sticky-flip to `on` for the rest of the conversation. Mirror opt-out flips back. | Unchanged — still apply |  <!-- md-language-check: ignore -->
-
-### Opt-in detection
-
-Intent-matched, not literal-string-matched. Speech-act-checked: the
-phrase must be a meta-instruction, not content / quote / code. Detail:
-[`autonomy-detection`](../../dist/agent-src/contexts/execution/autonomy-detection.md),
-[`autonomy-mechanics`](../../dist/agent-src/contexts/execution/autonomy-mechanics.md).
-
-### Task scope vs conversation scope
-
-Two distinct autonomy shapes:
-
-| Shape | Trigger | Scope |
-|---|---|---|
-| **Conversation-wide trivial-question suppression** | "stop asking on trivial steps" — no deliverable named | Sticky for the rest of the conversation. Suppresses trivial workflow questions only. |
-| **Task-scoped autonomous execution** | "work autonomously on X", "arbeite die Roadmap Y komplett ab" — deliverable named | Bound to that task. Ends when the task ends. Does NOT authorize a different later deliverable. |  <!-- md-language-check: ignore -->
-
-Per [`autonomous-execution § task-scope`](../../dist/agent-src/rules/autonomous-execution.md#task-scope--autonomy-is-bound-to-the-named-task).
-
-## The four non-overridable floors
-
-No value of `personal.autonomy` lifts any of these. Standing
-autonomy directives, roadmap authorizations, or "just keep going"
-phrases never reach them.
-
-### 1. Hard Floor — `non-destructive-by-default`
-
-[`dist/agent-src/rules/non-destructive-by-default.md`](../../dist/agent-src/rules/non-destructive-by-default.md).
-Stops on: production-branch merges; deploy / release; push to remote;
-production data / infra writes; whimsical bulk deletions; commits
-containing bulk deletions or infra changes. **Always confirm this turn.**
-
-### 2. Git-ops Permission Gate — `scope-control`
-
-[`dist/agent-src/rules/scope-control.md § Git operations`](../../dist/agent-src/rules/scope-control.md#git-operations--permission-gated).
-Stops on: commit · push · merge · rebase · force-push · branch create /
-switch / delete · PR create / close / retarget · tag / release / pin.
-Permission must be **this turn or a standing instruction not yet
-revoked**.
-
-### 3. Commit Default — `commit-policy`
-
-[`dist/agent-src/rules/commit-policy.md`](../../dist/agent-src/rules/commit-policy.md).
-**Never commit, never ask about committing.** Four exceptions: user
-says so this turn · standing instruction · `/commit` invoked · roadmap
-authorization. Anything else → no commit.
-
-### 4. Security-sensitive STOP — `security-sensitive-stop`
-
-[`dist/agent-src/rules/security-sensitive-stop.md`](../../dist/agent-src/rules/security-sensitive-stop.md).
-Stops on: auth, billing, tenant boundaries, secrets, uploads,
-integrations, webhooks, public endpoints. Threat-model **before**
-editing.
-
-## Coverage map
-
-| Surface | What governs it |
-|---|---|
-| Trivial workflow question | `personal.autonomy` (the switch) |
-| Blocking architectural / scope question | [`ask-when-uncertain`](../../dist/agent-src/rules/ask-when-uncertain.md) (always) |
-| Tool / MCP call cost | None today — Phase 1 item 4 introduces preset-loader Hard Enforcement |
-| Skill / command allowlist per audience | None today — Phase 2 item 7 introduces packs |
-| Per-domain `deny / ask / allow` | None today — Phase 2 item 9 introduces this |
-| Hard Floor (prod, deploy, push, bulk-destructive) | Universal — not switchable |
-| Git ops | Universal permission gate — not switchable |
-| Commit | Universal default-deny — not switchable |
-
-## Gaps the Phase 2 ADR will address
-
-1. **One switch, one granularity.** Today, `autonomy: on` suppresses
-   *every* trivial question identically. A founder running the
-   `content-engine` pack may want autonomy for content, ask-mode for
-   spend; the current model cannot express that.
-2. **No per-domain policy.** Domain-safety rules
-   (`dist/agent-src/rules/domain-safety-*.md`) act as output floors but do
-   not declare `deny / ask / allow` per profile. The Phase 2 model
-   centralizes this.
-3. **No machine-readable safety schema.** The current behavior is
-   distributed across four rules. A consuming tool (the wizard, the
-   explain command) cannot ask "what is this install's safety posture?"
-   without reading rule prose.
-
-The Phase 2 ADR (`docs/contracts/safety-model.md`) inherits this
-baseline and adds: per-profile policy table, machine-readable schema,
-explain-trace integration. It MUST NOT silently relax any of the four
-floors above.
-
-## See also
-
-- [`autonomous-execution`](../../dist/agent-src/rules/autonomous-execution.md) · [`non-destructive-by-default`](../../dist/agent-src/rules/non-destructive-by-default.md) · [`scope-control`](../../dist/agent-src/rules/scope-control.md) · [`commit-policy`](../../dist/agent-src/rules/commit-policy.md) · [`security-sensitive-stop`](../../dist/agent-src/rules/security-sensitive-stop.md).
-- [`docs/safety.md`](../safety.md) — domain-safety output floors.
-- [`agents/roadmaps/step-15-product-refinement.md`](../../agents/roadmaps/step-15-product-refinement.md) — Phase 1 item 2a (this doc) and Phase 2 item 9 (Universal Safety Model ADR).

package/docs/architecture/multi-tool-projection.md

@@ -1,125 +0,0 @@
-# Pipeline C — Multi-tool projection
-
-> **Scope:** generate the tool-specific surface files that non-Augment
-> hosts (Claude Code, Cursor, Cline, Windsurf, Gemini CLI, Copilot CLI)
-> read from their conventional locations.
-
-## Input → Transform → Output
-
-```
-dist/agent-src/**                      ← Condensed payload
-    ↓ scripts/condense.py --generate-tools
-.claude/      .cursor/             ← Claude Code, Cursor (rules + skills)
-.clinerules/  .windsurfrules       ← Cline (rules dir), Windsurf (concatenated file)
-GEMINI.md                          ← Gemini CLI (symlink → AGENTS.md)
-.github/copilot-instructions.md    ← Copilot Chat + PR review (already shipped)
-```
-
-Per-tool method ([`scripts/condense.py:_filter_tool_dirs`](../../src/scripts/condense.py)):
-
-| Tool | Surface | Method | Coverage |
-|---|---|---|---|
-| Claude Code | `.claude/` | native plugin + symlinks | rules + skills + commands |
-| Augment VSCode/IntelliJ | `.augment/` | install.sh copies + symlinks | rules + skills + commands |
-| Copilot CLI | (plugin) | native plugin | rules + skills + commands |
-| Cursor | `.cursor/` | install.sh symlinks | rules only |
-| Cline | `.clinerules/` | install.sh symlinks | rules only |
-| Windsurf | `.windsurfrules` | install.sh concatenates | rules only |
-| Gemini CLI | `GEMINI.md` | install.sh symlink → AGENTS.md | rules only |
-
-Hosts opt in / out via `.agent-settings.yml § tools.enabled`. The
-generator filters output to enabled tools only — disabling Cursor
-removes `.cursor/` on next `task generate-tools`.
-
-## Entry points
-
-| Surface | Command |
-|---|---|
-| Regenerate all enabled | `task generate-tools` ([`taskfiles/content.yml:63`](../../taskfiles/content.yml)) |
-| Clean output | `task clean-tools` ([`taskfiles/content.yml:69`](../../taskfiles/content.yml)) |
-| Direct script | `./scripts-run src/scripts/condense --generate-tools` |
-| Consumer install | `scripts/install.sh` (calls `--generate-tools` after `--project-augment`) |
-
-## Invariants
-
-1. **Modern formats only** — Claude / Cursor get the host's modern
-   skill / rule format; legacy XML / `.cursorrules` is not emitted.
-2. **Tool gating respected** — output for `tools.enabled = false`
-   never appears on disk.
-3. **Determinism** — same input + settings produce identical output;
-   CI enforces via `task sync-check`.
-4. **Path stability** — surface files live at the host's documented
-   location ([Cursor](https://docs.cursor.com), [Cline](https://docs.cline.bot),
-   [Windsurf](https://docs.codeium.com)).
-
-## Failure modes
-
-| Symptom | Cause | Fix |
-|---|---|---|
-| Cursor doesn't see rules | `.cursor/` not generated | `tools.enabled.cursor: true` then `task generate-tools` |
-| Claude Code missing a skill | skill not in `dist/agent-src/` yet | run Pipeline A (`task sync`) first |
-| Stale `.windsurfrules` after rule rename | concatenation cache | `task clean-tools && task generate-tools` |
-| Gemini CLI reads outdated content | `AGENTS.md` changed without re-symlink | `task generate-tools` |
-
-## Per-tool projection size
-
-The previous "0.45 % reduction" headline was a wrong-boundary
-measurement: that figure compares `.agent-src.uncondensed/` to
-`dist/agent-src/`, but the pipeline's claimed function is *projection*, not
-byte condensation. The table below is produced by
-[`scripts/measure_projection_bytes.py --regenerate`](../../src/scripts/measure_projection_bytes.py)
-with every tool ID temporarily enabled in `agents/.agent-tools.yml`.
-
-| Surface | Files | Symlinks | Bytes materialized | Method |
-|---|---:|---:|---:|---|
-| `.agent-src.uncondensed/` | 596 | 0 | 3,253,997 | verbose source (input) |
-| `dist/agent-src/` | 596 | 0 | 3,242,579 | source projection (path-rewrite + `.npmignore`) |
-| `.augment/` | 61 | 7 | 136,146 | Augment Code — copies (rules) + symlinks (skills/cmds) |
-| `.claude/` | 0 | 395 | 0 | Claude Code — pure symlinks |
-| `.cursor/` | 61 | 189 | 124,741 | Cursor — per-rule `.mdc` materialized + symlinks |
-| `.clinerules/` | 0 | 61 | 0 | Cline — pure symlinks |
-| `.windsurf/` | 61 | 106 | 125,010 | Windsurf — per-rule wave-8 `.md` + symlinks |
-| `.windsurfrules` | 1 | 0 | 114,263 | Windsurf legacy — concatenated single file |
-| `GEMINI.md` | 0 | 1 | 0 | Gemini CLI — symlink → `AGENTS.md` |
-
-**What the pipeline optimises**
-
-- **Format fidelity** — each tool receives content in the format its host
-  reads natively (Cursor `.mdc` frontmatter, Windsurf Wave-8 frontmatter,
-  Claude / Cline symlinked into the source tree, Gemini single-file).
-- **Path stability** — surface paths match the host vendor's
-  documentation so users opt in by enabling the tool, not by remapping.
-- **Materialization minimization** — pure-symlink tools (`.claude/`,
-  `.clinerules/`, `GEMINI.md`) contribute zero bytes; tools that need a
-  format transform materialize only the transformed rule files.
-
-**What the pipeline does not optimise**
-
-- **Raw byte count** — `.cursor/` and `.windsurf/` *grow* the on-disk
-  footprint by ~125 KB each because their host formats require
-  per-rule frontmatter that cannot be supplied via symlink alone.
-  `.windsurfrules` materializes the rule set a second time as a
-  concatenated single file for users who prefer that surface.
-- **Source dedup** — the same rule body appears in `dist/agent-src/rules/`
-  *and* in every tool's materialized projection. This is intentional:
-  removing the duplication would push format conversion into runtime.
-
-Re-run the measurement after every change to the projection logic:
-
-```bash
-./scripts-run src/scripts/measure_projection_bytes --regenerate
-./scripts-run src/scripts/measure_projection_bytes --json    # CI-friendly
-```
-
-## Proving the pipeline
-
-- [`tests/test_modern_editor_formats.py`](../../tests/test_modern_editor_formats.py)
-  — verifies Claude / Cursor receive modern format with correct
-  frontmatter; runs only when `task generate-tools` has been executed.
-- [`tests/test_condense.py`](../../tests/test_condense.py) — covers
-  the shared condense / generate-tools entrypoint and `_filter_tool_dirs`.
-- [`scripts/measure_projection_bytes.py`](../../src/scripts/measure_projection_bytes.py)
-  — per-tool byte / file / symlink count; the per-tool-size table above
-  is its output.
-
-← [Architecture overview](../architecture.md)