@event4u/agent-config 9.7.0 → 9.9.0

package/docs/migration/yaml-roundtrip-spike.md

@@ -1,163 +0,0 @@
-# YAML Round-Trip Spike — Verdict
-
-> Phase 1 Step 7 of `agents/roadmaps/archive/road-to-typescript-only-scripts.md`.
-> Originally framed as a "ruamel.yaml → npm `yaml`" risk. The survey below
-> shows that framing was wrong: there is **no ruamel usage anywhere** — the
-> comment-preserving round-trip layer is `src/scripts/sync_yaml_rt.py`, a
-> **self-contained, stdlib-only, hand-written narrow-subset parser**, and it
-> ports 1:1 to TypeScript with no external library.
-
-## 1. Usage survey
-
-Grep surface: `src/scripts/` + `src/agent-src/templates/scripts/` for
-`import yaml`, `from yaml`, `ruamel`, `safe_load`, `safe_dump`,
-`yaml.load`, `yaml.dump` (2026-06-11, branch `feat/py2ts-phase1-infra`).
-
-| Category | Files | What it is |
-|---|---:|---|
-| (a) `sync_yaml_rt` own parser | 1 (+2 consumers) | `src/scripts/sync_yaml_rt.py` — stdlib-only round-trip parser/emitter/merger for `.agent-settings.yml`. Consumed by `src/scripts/sync_agent_settings.py` and `src/scripts/_cli/cmd_settings_check.py`. |
-| (b) PyYAML read-only consumers | 90 | 81 under `src/scripts/` + 9 under `src/agent-src/templates/scripts/`. All `safe_load` only — frontmatter readers, settings readers, linters, manifest loaders. |
-| (c) PyYAML writers (`safe_dump`) | 6 | Listed below — these risk formatting drift on port. |
-| (d) ruamel users | **0** | Verified: `grep -rn ruamel` over both trees → no hits. The council's "ruamel showstopper" has no code behind it. |
-
-Mention-only matches (not consumers): `audit_cloud_compatibility.py`
-(regex pattern for a linter), `render_value_md.py` / `render_benchmark_md.py`
-(local helper functions named `safe_load` that read JSON, not YAML).
-
-### Category (c) — the six writer scripts, explicitly
-
-| Script | What it dumps | Drift risk |
-|---|---|---|
-| `src/scripts/new_skill.py` | New-skill frontmatter block (`sort_keys=False, allow_unicode=True`) | New files only — no existing bytes to preserve. Low. |
-| `src/scripts/move_artefact.py` | Rewritten artefact frontmatter after a move (`sort_keys=False, allow_unicode=True`) | Touches existing frontmatter — PyYAML's quote/wrap style differs from `yaml.stringify`. **Flag for its port phase.** |
-| `src/scripts/generate_pack_manifests.py` | Generated pack-manifest YAML (`sort_keys=True`, deterministic header) | Generated output with goldens — port must match or goldens regenerate once. **Flag.** |
-| `src/scripts/measure_projection_bytes.py` | Temporary rewrite of `agents/.agent-tools.yml`, restored on exit | Transient file, restored from the original string. Low. |
-| `src/scripts/config/session_profiles.py` | Whole `.agent-settings.local.yml` overlay (atomic write) | Gitignored per-machine file, machine-managed (no user comments preserved today either). Low-medium. |
-| `src/scripts/ai_council/compile_corpus.py` | Deterministic corpus lock YAML (`dump_lock_yaml`, `width=10_000`) | Determinism is asserted by tests — port must reproduce or the lock format is re-baselined once. **Flag.** |
-
-## 2. Spike results
-
-### 2.1 `sync_yaml_rt` 1:1 port (`tests/spikes/yaml_rt_spike.ts`)
-
-The core round-trip property (parse → emit reproduces every user line
-character-for-character) was ported to TypeScript — ~430 lines, **zero
-dependencies**, mirroring the Python module function-for-function
-(tokeniser, inline-comment splitter honouring quote boundaries, mapping/
-list line parsers, indent-stack tree builder, verbatim emitter).
-
-Fixture corpus: `tests/spikes/fixtures/yaml-rt/` — 12 fixtures derived
-from the documented subset and from the `src/config/agent-settings.template.yml`
-shape (synthetic/generic values):
-
-| Fixture | Nasty case covered |
-|---|---|
-| `01-basic-mapping.yml` | 2-space block mapping, header comment |
-| `02-inline-comments.yml` | inline comments after values, comment-only values, `#` inside quotes |
-| `03-blank-line-runs.yml` | multi-blank-line runs, trailing comment + blank |
-| `04-block-list.yml` | block lists, item inline comments, bare `-` item |
-| `05-inline-flat-list.yml` | inline flat lists `[a, b, c]`, empty `[]` |
-| `06-four-space-indent.yml` | 4-space indent |
-| `07-crlf.yml` | CRLF-terminated file |
-| `08-duplicate-keys.yml` | duplicate keys, last-wins |
-| `09-quoted-scalars.yml` | quoted scalars, `~`/`null`/`None`, bools, quoted key with `:` |
-| `10-agent-settings-shape.yml` | real template shape (comment banners, nested sections, list) |
-| `11-no-trailing-newline.yml` | final line without terminator |
-| `12-deep-nesting-mixed.yml` | deep nesting, comments between siblings |
-
-Differential test (`tests/spikes/yaml_rt_spike.test.ts`, 31 tests, green):
-
-- **Round-trip property:** for every fixture except the duplicate-keys one,
-  TS `emit(parse(x)) === x` byte-for-byte (CRLF and missing-final-newline
-  included).
-- **Differential parity:** for **all 12** fixtures, TS output is
-  byte-identical to the Python reference output
-  (`tests/spikes/yaml_rt_py_driver.py` → `sync_yaml_rt.parse`/`emit`).
-- **Duplicate keys** are round-trip *lossy by design* in **both**
-  implementations identically: last wins, the earlier line and its leading
-  comment block are dropped; the result is idempotent. (Verified against
-  Python: `'a: 1\na: 2\nb: 3\n'` → `'a: 2\nb: 3\n'` on both sides.)
-- **Error parity** spot-checked: tabs in indent and inconsistent dedent
-  ("over-indent") raise on both sides; mixed per-line EOLs are preserved.
-
-### 2.2 PyYAML readers → npm `yaml` (`tests/spikes/pyyaml_vs_npm.test.ts`)
-
-Representative real files — `Taskfile.yml`, `taskfiles/engine.yml`,
-`src/config/agent-settings.template.yml`, `.github/workflows/consistency.yml`
-— parsed with PyYAML `safe_load` and with npm `yaml` (`YAML.parse`),
-canonicalised to sorted compact JSON on both sides: **semantically equal**
-(5 tests, green).
-
-Two load-bearing findings for the production port:
-
-1. **YAML version pin.** PyYAML implements YAML 1.1: `on:` (workflow files)
-   resolves to boolean `true`, `yes`/`off` are booleans. npm `yaml`
-   defaults to YAML 1.2 (those stay strings). Every PyYAML replacement
-   must pass `{ version: '1.1' }` to keep semantics identical. Without
-   the pin, the workflow fixture fails.
-2. Non-string keys (boolean `true` from `on:`) must be canonicalised the
-   same way on both sides when comparing (Python dict key `True` ↔ JS
-   object key `"true"`); with that, equality holds.
-
-## 3. Verdict
-
-- **Comment-preserving round-trip = self-contained 1:1 port of
-  `sync_yaml_rt.py`. NO external library needed.** The council's
-  "ruamel.yaml has no npm equivalent" showstopper is **moot** — ruamel is
-  used nowhere, and the actual round-trip layer is a hand-written
-  stdlib-only parser whose core property has now been reproduced
-  byte-for-byte in TypeScript against a 12-fixture differential corpus.
-- **PyYAML read-only consumers (90 files) → npm `yaml` with
-  `{ version: '1.1' }`.** Semantic equality verified on real repo files.
-- **PyYAML writers (6 files) → npm `yaml` `stringify`,** with a
-  formatting-drift review in each script's own port phase. `new_skill.py`
-  and `measure_projection_bytes.py` are low-risk (new/transient output);
-  `move_artefact.py`, `generate_pack_manifests.py`,
-  `compile_corpus.py` (and to a lesser degree `session_profiles.py`)
-  emit bytes that other tooling or goldens see — handle any
-  PyYAML-vs-`yaml.stringify` style differences as documented divergences
-  (`docs/migration/divergences/`) or one-time golden re-baselines.
-
-## 4. What the production port (Phase 5) must cover beyond the spike
-
-The spike ports **`parse` + `emit` only**. The production
-`sync_yaml_rt.ts` additionally needs:
-
-1. **`merge(user, template)`** — additive merge: insert-position logic
-   honouring user reordering, blank-line separator insertion for
-   top-level sections, EOL normalisation of cloned template subtrees
-   (`_detect_eol`, `_normalize_line_endings`, `_ensure_blank_separator`,
-   `_find_insert_pos`).
-2. **`heal_user_block(user, template)`** — legacy `_user._user.foo`
-   corruption healer: leaf collection with `_user`-segment stripping,
-   re-homing into template paths, orphan rebuild, idempotency.
-3. **`sync(user_text, template_text)`** — the pipeline entry point
-   (parse → heal → merge → emit).
-4. **Synthetic-node rendering** under merge (the spike includes
-   `renderSyntheticHeader` but no caller exercises it — production tests
-   must).
-5. **Full error-message parity or documented divergence** — the Python
-   `ValueError` strings (line numbers included) are user-visible via
-   `sync_agent_settings.py` / `cmd_settings_check.py`; decide verbatim
-   parity vs. documented divergence.
-6. **The existing Python test suite as the conformance oracle** —
-   `tests/test_sync_agent_settings.py`, `tests/test_sync_round_trip.py`
-   and friends should be mirrored (or run differentially, as in this
-   spike) until the Python side is deleted.
-7. **Lone-`\r` line endings** — Python `splitlines` recognises more
-   terminators (`\v`, `\f`, `\x1c`…) than the spike's `\n`/`\r\n`/`\r`
-   splitter. The spike handles `\r`; the exotic terminators are outside
-   the documented subset — confirm and document as a divergence.
-
-## 5. Verification evidence
-
-```
-npx vitest run tests/spikes/
-
- ✓ tests/spikes/pyyaml_vs_npm.test.ts (5 tests)
- ✓ tests/spikes/yaml_rt_spike.test.ts (31 tests)
-
- Test Files  2 passed (2)
-      Tests  36 passed (36)
-```
-
-Environment: node v25.9.0, npm `yaml` 2.9.0, python3 3.9.6, PyYAML 6.0.3.

package/docs/migrations/commands-1.15.0.md

@@ -1,117 +0,0 @@
-# Command migration — 1.15.0
-
-> **Audience:** consumers of `event4u/agent-config` upgrading from
-> `1.14.x` to `1.15.0`.
-> **Authoritative spec:** [`docs/contracts/command-clusters.md`](../contracts/command-clusters.md).
-
-`1.15.0` collapses 15 atomic commands into 3 verb clusters
-(`fix`, `optimize`, `feature`) to reduce command-palette
-fragmentation. **Old commands keep working through the entire
-1.15.x cycle**; they emit a one-line deprecation warning on
-invocation and are removed in `1.16.0`.
-
-## Summary table
-
-| Old command | New invocation | Removed in |
-|---|---|---|
-| `/fix-ci` | `/fix ci` | 1.16.0 |
-| `/fix-pr-comments` | `/fix pr-comments` | 1.16.0 |
-| `/fix-pr-bot-comments` | `/fix pr-bot-comments` | 1.16.0 |
-| `/fix-pr-developer-comments` | `/fix pr-developer-comments` | 1.16.0 |
-| `/fix-portability` | `/fix portability` | 1.16.0 |
-| `/fix-references` | `/fix refs` | 1.16.0 |
-| `/fix-seeder` | `/fix seeder` | 1.16.0 |
-| `/optimize-agents` | `/optimize agents` | 1.16.0 |
-| `/optimize-augmentignore` | `/optimize augmentignore` | 1.16.0 |
-| `/optimize-rtk-filters` | `/optimize rtk` | 1.16.0 |
-| `/optimize-skills` | `/optimize skills` | 1.16.0 |
-| `/feature-explore` | `/feature explore` | 1.16.0 |
-| `/feature-plan` | `/feature plan` | 1.16.0 |
-| `/feature-refactor` | `/feature refactor` | 1.16.0 |
-| `/feature-roadmap` | `/feature roadmap` | 1.16.0 |
-
-## What changes for you
-
-**Nothing breaks in 1.15.x.** Old slugs continue to work — the agent
-recognises them, dispatches to the new cluster command, and prints
-one warning line at the top of the reply:
-
-```
-⚠️  /fix-ci is deprecated; use /fix ci instead.
-```
-
-**Your existing custom skills, rules, or agents/roadmaps that
-reference old slugs do not need to change in 1.15.x.** Update at
-your own pace.
-
-## What to update before 1.16.0
-
-Search your project for any direct references to the old slugs and
-swap them for the new invocation:
-
-```bash
-# Find references in agents/, docs/, README, custom rules
-rg -n '/(fix|optimize|feature)-[a-z-]+' \
-   agents/ docs/ README.md AGENTS.md .github/ 2>/dev/null
-```
-
-Common spots:
-
-- `agents/roadmaps/*.md` — roadmap steps that name commands
-- `agents/settings/contexts/*.md` — context docs cross-linking commands
-- Custom skills/rules under `.augment/` overrides
-- Internal team docs / runbooks / onboarding pages
-
-## Why this changed
-
-The atomic-command surface had grown to 77 commands by 1.14.0. Three
-prefix families (`fix-*`, `optimize-*`, `feature-*`) accounted for 15
-of those — same verb, same invocation pattern, only the noun
-differed. Collapsing the families into clusters:
-
-- Reduces palette noise (15 → 3 top-level entries).
-- Makes new sub-commands additive (`/fix tests` ships without a new
-  top-level slug).
-- Holds the line: `scripts/lint_no_new_atomic_commands.py` fails CI
-  if a new atomic command lands without a `cluster:` field declared
-  in [`docs/contracts/command-clusters.md`](../contracts/command-clusters.md).
-
-## Phase 2 (deferred)
-
-A second wave of collapses (`chat-history`, `agents`, `memory`,
-`roadmap`, `module`, `tests`, `context`, `override`, `copilot-agents`,
-`commit`, `judge`, `create-pr`) is scheduled after 1.15.0 ships and
-the deprecation cycle for Phase 1 closes. Tracked in
-[`agents/roadmaps/archive/road-to-governance-cleanup.md`](../../agents/roadmaps/archive/road-to-governance-cleanup.md)
-§ F2.
-
-## Related rule split — `chat-history` (post-1.15.0, superseded)
-
-> **Superseded · 2026-05-04** by
-> [`agents/settings/contexts/chat-history-platform-hooks.md`](../../agents/settings/contexts/chat-history-platform-hooks.md).
-> The three sibling rules (`chat-history-ownership`,
-> `chat-history-cadence`, `chat-history-visibility`) and the heartbeat
-> marker no longer exist. Persistence is now a pure platform-hook
-> contract — `session_start` auto-adopts foreign sessions silently;
-> the agent never reads or writes `agents/runtime/.agent-chat-history` cooperatively.
-> Manual recovery lever: `./agent-config chat-history:adopt`.
-
-For historical context: the monolithic `rules/chat-history.md` was
-first split into three sibling `always` rules in the post-1.15.0
-optimization phase, recorded in
-[`docs/contracts/adr-chat-history-split.md`](../contracts/adr-chat-history-split.md)
-(also marked superseded). The hook-only roadmap then collapsed all
-three rules into structural-only artefacts.
-
-## Rollback
-
-If a deprecation warning blocks tooling that screen-scrapes agent
-output, suppress it for the 1.15.x cycle by setting
-`commands.deprecation_warnings: false` in `.agent-settings.yml`.
-The setting disappears in 1.16.0 along with the shims.
-
-## See also
-
-- [`docs/contracts/command-clusters.md`](../contracts/command-clusters.md) — locked cluster spec.
-- [`docs/contracts/STABILITY.md`](../contracts/STABILITY.md) — public-surface stability tiers.
-- [`agents/roadmaps/archive/road-to-post-pr29-optimize.md`](../../agents/roadmaps/archive/road-to-post-pr29-optimize.md) — P0.8 anchor for this migration.

package/docs/parity/bench-external.json

@@ -1,58 +0,0 @@
-{
-  "schema": "parity-bench-external-v1",
-  "status": "infrastructure_ready_awaiting_corpus_run",
-  "owner_roadmap": "agents/roadmaps/step-11-external-parity.md",
-  "parity_doc": "docs/parity/external.md",
-  "parent_bench": "docs/parity/bench.json",
-  "claim_under_test": {
-    "source": "agents/evidence/audits/2026-05-14-north-star/external-findings.md § 2",
-    "headline": "Average dollar cost per 25-prompt corpus run, separated by model tier (Haiku / Sonnet / Opus) and by token class (input / output / cache-read / cache-write).",
-    "comparison_target": "external cost-tracker README (claimed upstream, not yet pulled into this repo)",
-    "type": "claimed_upstream_not_verified_in_repo"
-  },
-  "measurement_protocol": {
-    "corpus": "internal/bench/corpus/* (25-prompt corpus owned by step-4-measurement-and-benchmark.md)",
-    "tracker": "scripts/cost/track.mjs",
-    "pricing": "internal/bench/pricing.yaml",
-    "session_source": "~/.claude/projects/*/sessions/*.jsonl (Claude Code-native, no manual tracking)",
-    "tokens_to_dollars": "track.mjs multiplies input/output/cache-read/cache-write tokens by per-1M pricing from internal/bench/pricing.yaml, separated by model id",
-    "headline_output": "average dollar cost per 25-prompt run, with min / max / p50 / p90 across N reports"
-  },
-  "current_window": {
-    "report_count": 0,
-    "verdict": "awaiting_first_corpus_run",
-    "notes": "Phase 1-5 of step-11 delivered the cost-tracking and bench infrastructure. Phase 6 Step 2 awaits the first end-to-end 25-prompt corpus run against the live tracker. Until then this file exists as a methodology contract, not a verdict surface."
-  },
-  "soak_inheritance": {
-    "follows": "docs/parity/bench.json",
-    "min_days": 60,
-    "min_reports": 30,
-    "earliest_flip": "2026-07-15",
-    "arbiter_command": "task bench:baseline-ready",
-    "notes": "bench-external.json flips status to 'baseline_ready' only after the parent bench.json flips. No independent soak window — same corpus, same arbiter."
-  },
-  "redundancy_verdict": {
-    "status": "pending",
-    "criterion": "Once bench.json soak completes, this verdict is set by comparing the dollar cost in current_window vs the external runtime's published table.",
-    "outcome_branches": {
-      "redundant": "Our cost-per-25-prompt-run sits within the external runtime's published range (or beats it). G5 redundancy gate row for cost surface flips green.",
-      "behind": "Our cost-per-run > the external runtime's. Follow-up issue filed; G5 stays open."
-    }
-  },
-  "fields_pending_first_run": [
-    "current_window.avg_cost_per_run_usd",
-    "current_window.cost_by_model.haiku_usd",
-    "current_window.cost_by_model.sonnet_usd",
-    "current_window.cost_by_model.opus_usd",
-    "current_window.cost_by_class.input_usd",
-    "current_window.cost_by_class.output_usd",
-    "current_window.cost_by_class.cache_read_usd",
-    "current_window.cost_by_class.cache_write_usd"
-  ],
-  "decisions_pending": {},
-  "_meta": {
-    "created": "2026-05-16",
-    "created_by": "step-11-external-parity.md Phase 6 Step 2",
-    "spec": "scripts/cost/track.mjs --bench-external (planned wiring); for now the file is a methodology contract"
-  }
-}

package/docs/parity/bench.json

@@ -1,41 +0,0 @@
-{
-  "schema": "parity-bench-v1",
-  "status": "soak_in_progress",
-  "owner_roadmap": "agents/roadmaps/step-4-measurement-and-benchmark.md",
-  "contract": "docs/contracts/measurement-baseline.md",
-  "soak": {
-    "start_date": "2026-05-16",
-    "min_days": 60,
-    "min_reports": 30,
-    "earliest_flip": "2026-07-15",
-    "arbiter_command": "task bench:baseline-ready"
-  },
-  "current_window": {
-    "report_count": 1,
-    "days_elapsed": 0,
-    "verdict": "warmup",
-    "notes": "First infrastructure-shakedown run only. Numbers below are not the baseline."
-  },
-  "shakedown_run": {
-    "report": "bench/reports/2026-05-16T06-13-07Z-dev-projection.md",
-    "corpus": "dev",
-    "selection_accuracy_augment": 0.5,
-    "selection_accuracy_claude": 0.5,
-    "projection_fidelity_claude": 1.0,
-    "projection_fidelity_cursor": "not_applicable",
-    "projection_fidelity_cline": "not_applicable",
-    "projection_fidelity_windsurf": "not_applicable"
-  },
-  "decisions_pending": {
-    "condensation_default": {
-      "kill_criterion": "docs/contracts/condensation-default-kill-criterion.md",
-      "verdict": "deferred_until_baseline_closes",
-      "decision_owner": "step-4 closeout phase"
-    }
-  },
-  "downstream_consumers": [
-    "agents/roadmaps/step-99-north-star-restructure.md#G1",
-    "agents/roadmaps/step-2-skill-inventory-rationalization.md#G0",
-    "docs/contracts/condensation-default-kill-criterion.md"
-  ]
-}

package/docs/parity/command-frontmatter.md

@@ -1,60 +0,0 @@
-# Command frontmatter — per-host projection parity
-
-> Which command frontmatter fields each host bridge actually consumes, and the
-> deliberate divergences from the official command-authoring field standard.
-> Source of truth for command definitions: `src/domains/<pack>/<name>/command.md`
-> (projected verbatim to `dist/agent-src/commands/` by the condensation
-> pipeline). Schema: [`command.schema.json`](../../src/scripts/schemas/command.schema.json).
-> Roadmap origin: `road-to-ecosystem-harvest-skill-quality-gates` Phase 4 (Source C).
-
-## Projection paths per host
-
-| Host | Projection | Frontmatter reaches host? |
-|---|---|---|
-| Claude Code | `.claude/skills/<slug>/SKILL.md` — symlink to the command source; rendered copy (with native `model:`) when `model.auto_switch: auto` and a `model_tier` maps | Yes — full frontmatter, verbatim |
-| Cursor | `.cursor/commands/<slug>.md` — symlink to the command source | Yes — file verbatim; Cursor treats unknown frontmatter as inert |
-| Windsurf | `.windsurf/workflows/<slug>.md` — symlink to the command source | Yes — same inert-passthrough as Cursor |
-| Cline / Gemini / Copilot / Roo / Codex / Continue | Text reference via `AGENTS.md` only (no native command surface) | No — invocation is conversational |
-
-## Field consumption matrix (official-standard fields)
-
-| Field | Claude Code | Cursor / Windsurf | Notes |
-|---|---|---|---|
-| `name` | ✅ load rule: must equal the skill directory slug | inert | Path-derived hyphen slug; enforced by `check_host_loadability` |
-| `description` | ✅ routing + display | inert | ≤ 200 chars per schema |
-| `argument-hint` | ✅ rendered next to the slash command | inert | Added Phase 4; set on every command whose body documents an invocation argument (140/183 at introduction) |
-| `disable-model-invocation` | ✅ honored natively | inert (vacuously true — no model-invocation surface) | Schema pins `enum: [true]` — commands are user-invoked by design |
-| `model` | ✅ (rendered copies only) | inert | Never authored by hand: the generator rewrites `model_tier:` → native `model:` at projection time (ADR-034/035) |
-
-All other fields (`tier`, `visibility`, `pack`, `cluster`, `intent`,
-`routes_to`, `replaces`, `suggestion`, `workspaces`, `packs`, `trust`,
-`install`, `model_tier`, …) are **suite governance metadata** — consumed by the
-package's own linters, router, discovery manifest, and docs generators, never
-by a host. Hosts that read the file verbatim ignore them; that is the intended
-contract, not drift.
-
-## Deliberate divergences from the official standard
-
-1. **No colon names.** The official examples allow `/cluster:sub` invocation;
-   this suite forbids colons in `name:` (Agent-Skills-spec compliance for
-   strict consumers like Zed). Claude Code's `/cluster:sub` invocation still
-   works — it is path-derived from `commands/<cluster>/<sub>.md`, not from the
-   `name:` field.
-2. **`disable-model-invocation` is locked to `true`.** The standard allows
-   model-invocable commands; this suite's commands are always user-invoked
-   (`command-suggestion-policy` owns proactive surfacing instead — suggest,
-   never invoke).
-3. **`model` is generated, never authored.** Authors declare the
-   vendor-neutral `model_tier:`; the Claude bridge renders a native `model:`
-   only when the consumer opted into `model.auto_switch: auto`.
-4. **`argument-hint` is host-passthrough.** Only Claude Code renders it today;
-   it stays in the neutral source (harmless elsewhere) rather than being
-   projected host-specifically — per the do-NOT-chase-host-fields rule for the
-   neutral tree.
-
-## Verification
-
-- `./scripts-run src/scripts/validate_frontmatter` — every command validates
-  against the schema (including `argument-hint` shape, ≤ 120 chars).
-- `./scripts-run src/scripts/check_host_loadability --root .` — generated
-  `.claude/skills/` entries parse and satisfy the host load rule.

package/docs/parity/external-runtime.md

@@ -1,46 +0,0 @@
-# Parity verdict — an external multi-agent runtime
-
-> Per-row verdict against the eight external-runtime measurement-governance patterns
-> catalogued in
-> [`external-findings.md § 2`](../../agents/evidence/audits/2026-05-14-north-star/external-findings.md).
-> Owner roadmap: an internal parity record (local-only)
-> (Phase 6 Step 1). Cross-index lives at
-> [`step-99-north-star-restructure.md`](../../agents/roadmaps/step-99-north-star-restructure.md)
-> Phase 5 Step 2.
->
-> **Verdict legend:** `[x] covered by <file:line>` · `[~] superseded by <approach>` · `[!] gap`.
-> **Acceptance:** zero `[!]` rows. Closure flips the corresponding cell in the
-> [composite scorecard](../../agents/evidence/audits/2026-05-14-north-star/external-findings.md#5-composite-scorecard--agent-config-vs-the-field)
-> `vs the external runtime` column from `–` to `=` or `+`.
-
-**Measured-vs-claimed disclaimer:** Each row cites the **mechanism** that
-covers the external runtime's pattern. Numbers attached to those mechanisms (cost figures,
-smoke baselines, ADR count) are claimed until the 25-prompt bench corpus
-soak in [`bench.json`](bench.json) flips from `warmup` to `baseline_ready`
-(min 60 days, ≥ 30 reports — earliest 2026-07-15).
-
-## Verdict table
-
-| # | External-runtime pattern | Verdict | Evidence |
-|---|---|---|---|
-| 1 | **Cost-tracker plugin** — real model pricing, per-1M, separated input/output/cache | `[x] covered by` | [`scripts/cost/track.mjs`](../../src/scripts/cost/track.mjs) + [`internal/bench/pricing.yaml`](../../bench/pricing.yaml) (Haiku/Sonnet/Opus per-1M, input/output/cache-read/cache-write split). Step-11 Phase 1. |
-| 2 | **Auto-capture from session jsonl** — reads Claude Code log, no manual tracking | `[x] covered by` | [`scripts/cost/track.mjs`](../../src/scripts/cost/track.mjs) reads `~/.claude/projects/*/sessions/*.jsonl` automatically. Step-11 Phase 1 Step 1. |
-| 3 | **50/75/90/100 % budget ladder with hard stop** | `[x] covered by` | [`scripts/cost/budget.mjs`](../../src/scripts/cost/budget.mjs) — exit codes 0/1/2/3 per tier; opt-in fail-closed via `cost.enforcement` setting. Fixtures: `tests/fixtures/cost/budget/{under-50,at-100,over-100}/`. Step-11 Phase 2. |
-| 4 | **Measured-vs-claimed disclaimer** — every percentage tagged "claimed upstream" | `[x] covered by` | One-line `**Measured-vs-claimed disclaimer:**` header block on all 9 active roadmaps in `agents/roadmaps/`. Verified 2026-05-16. Step-11 Phase 5 Step 4. |
-| 5 | **Smoke test as contract** — `bash scripts/smoke.sh` with declared baseline | `[x] covered by` | Four per-tier smoke scripts: [`scripts/smoke/kernel.sh`](../../src/scripts/smoke/kernel.sh), [`router.sh`](../../src/scripts/smoke/router.sh), [`schema.sh`](../../src/scripts/smoke/schema.sh), [`skills.sh`](../../src/scripts/smoke/skills.sh). Declared baselines in [`docs/contracts/smoke-contracts.md`](../contracts/smoke-contracts.md). CI gate: [`.github/workflows/smoke.yml`](../../.github/workflows/smoke.yml). Step-11 Phase 3. |
-| 6 | **Per-plugin ADR directory** — `docs/adrs/0001-*.md` co-located with subsystem | `[x] covered by` | Six bootstrap ADRs under [`docs/adrs/{cost,memory,router,schema,smoke,telegraph}/`](../adrs/). Coverage gate: [`scripts/audit_adr_coverage.py`](../../src/scripts/audit_adr_coverage.py) (`task lint-adr-coverage`). Contract: [`docs/contracts/adr-layout.md`](../contracts/adr-layout.md). Step-11 Phase 4. |
-| 7 | **Namespace contract** — `<stem>-<intent>` kebab-case, reserved-names list | `[x] covered by` | [`scripts/lint_namespace.py`](../../src/scripts/lint_namespace.py) enforces shape + length floors + reserved-names + skill-dir-matches-name across 430 names · 0 issues. Contract: [`docs/contracts/namespace.md`](../contracts/namespace.md). CI gate: `task lint-namespace`. Step-11 Phase 5 Step 1. |
-| 8 | **Topology choices in swarm** — `hierarchical / mesh / star / adaptive` with anti-drift defaults | `[x] covered by` | [`.agent-src.uncondensed/skills/subagent-orchestration/SKILL.md`](../../.agent-src.uncondensed/skills/subagent-orchestration/SKILL.md) `Topology hints` subsection — 7-row table mapping each mode to topology + external-runtime anti-drift default (`hierarchical, 6–8 agents, raft consensus`). Step-11 Phase 5 Step 2. |
-| 9 | **MCP-tool count + source-line refs** — every tool with `<file>:<line>` citation | `[x] covered by` | [`docs/contracts/mcp-tool-inventory.md`](../contracts/mcp-tool-inventory.md) — 20 tools (9 stdio-implemented · 11 discovery stubs) each with catalog `<file>:<line>` + handler `<file>:<line>`. Generator: [`scripts/audit_mcp_tools.py`](../../src/scripts/audit_mcp_tools.py). CI drift gate: `task lint-mcp-inventory`. Step-11 Phase 5 Step 3. |
-
-## Open `[!]` rows
-
-**Zero.** Every external-runtime pattern is mechanism-covered. Numbers behind those
-mechanisms remain claimed until [`bench.json`](bench.json) soak completes
-(see disclaimer above).
-
-## Cross-references
-
-- Composite scorecard refresh: owned by [`step-99-north-star-restructure.md`](../../agents/roadmaps/step-99-north-star-restructure.md) Phase 5 Step 4 (replaces [`external-findings.md § 5`](../../agents/evidence/audits/2026-05-14-north-star/external-findings.md)).
-- External-runtime bench redundancy verdict: [`bench-external.json`](bench-external.json) (step-11 Phase 6 Step 2).
-- G5 redundancy gate cite: step-99 Acceptance Criteria row "G5 — external redundancy (Domination Mandate)".