@event4u/agent-config 8.9.0 → 8.11.0

package/docs/contracts/release-pr-gating.md

@@ -80,6 +80,27 @@ the feature-PR floor by adding:
 | `release-validation.yml` (Phase B) | `release-shape` | shape detector — fails closed if diff exits the allowlist |
 | `release-validation.yml` (Phase B) | `changelog-entry` | CHANGELOG carries an entry matching the head-branch version |
 | `release-validation.yml` (Phase B) | `version-consistency` | `package.json` / `marketplace.json` / pack manifests agree on the version |
+| `consumer-matrix.yml` | `consumer-matrix` · `publish-dry-run` · `mcp-worker-dry-run` · `plugin-bootstrap` | pack-based consumer E2E + pre-tag dry-runs of the release-adjacent workflows — see the exemption note below |
+
+## Consumer-matrix exemption — the tarball window
+
+The cut surface above rests on "release PRs cannot regress install or
+runtime behaviour by construction". That argument covers the **source
+diff** — it is blind to the **published tarball**. Every historical
+packaging incident (tarball missing `src/install/` across two minors,
+`tsx` absent from the package, npm-pin drift, the MCP worker deploy red
+across five releases) entered `main` on ordinary PRs and manifested only
+at publish time — exactly the window between merge and tag where nothing
+pack-based ran.
+
+[`consumer-matrix.yml`](../../.github/workflows/consumer-matrix.yml) is
+therefore **exempt from the release-PR skip and runs ON release PRs** (its
+primary trigger), packing the tarball and exercising it as a consumer,
+plus dry-running `publish-npm.yml` and `deploy-mcp-worker.yml` before the
+tag exists. Contract + counterfactual map:
+[`docs/distribution/consumer-matrix.md`](../distribution/consumer-matrix.md).
+The source-level skips above stay unchanged — the exemption adds the
+tarball dimension, it does not reopen the source matrices.
 
 ## Rollback trigger — fail-closed
 
@@ -122,3 +143,8 @@ name alone never bypasses the heavy matrix.
   release-branch naming convention.
 - [`ADR-113`](../decisions/ADR-113-ci-native-release-label-trigger.md) — the
   CI-native (`release`-label) entry point into the same script.
+- [`docs/distribution/consumer-matrix.md`](../distribution/consumer-matrix.md) —
+  pack-based consumer E2E; the documented exemption from the cut surface.
+- [`release-sizing.md`](release-sizing.md) — release scope floor: one primary
+  goal per minor, `Rollback:` lines for new / reworked subsystems (gate:
+  `src/scripts/lint_changelog_rollback.ts`).

package/docs/contracts/release-sizing.md

@@ -0,0 +1,107 @@
+---
+stability: beta
+keep-beta-until: 2026-09-10
+---
+
+# Release Sizing
+
+> **Status:** active · v0 / beta · 2026-07-10. Governs how much a
+> minor release may carry and what every shipped subsystem owes the
+> reader: one primary goal, a disable path, and a named rollback.
+> No version numbers appear here as commitments — this contract
+> shapes releases, it does not schedule them.
+
+## One primary product goal per minor release
+
+Every minor release names **exactly one primary product goal** — the
+one-sentence answer to "why does this release exist?". Secondary
+changes may ride along, but the release notes lead with the primary
+goal, and a release that cannot name one is not ready to cut.
+Scope discipline, not a ratio: what qualifies is a judgment call the
+maintainer makes when labeling the release PR
+([`release-pr-gating.md`](release-pr-gating.md)).
+
+### Primary goal declaration
+
+Every release PR body carries one literal line:
+
+```
+Primary-Goal: <one sentence>
+```
+
+A release bundling multiple major themes anyway annotates the
+**exception + reason** in the release notes ("this release bundles N
+themes because <reason>; future releases return to one primary goal").
+The declaration keeps the norm visible and the exception deliberate.
+
+Explicitly REJECTED (council, anthropic/claude-sonnet-4-5 +
+openai/gpt-4o, 2026-07-10): a mechanical subsystem-count lint on the
+release PR. A file→subsystem map is its own maintenance burden, and
+changed-file counts are a bad proxy for scope (a one-line kernel change
+has a larger blast radius than 50 lines in a niche skill). Sizing stays
+a norm enforced by declaration + human judgment; if the maintainer
+wrote a nine-theme release, the maintainer already judged it — the
+header makes that judgment explicit, not automatic.
+
+## Major subsystems are independently disableable where feasible
+
+A major subsystem shipped or substantially reworked in a release is
+**independently disableable** where feasible — a settings key in
+`.agent-settings.yml`, a pack that can stay uninstalled, or an
+explicit opt-in flag. The release notes **name the flag / config
+key** so a consumer who hits a regression can switch the subsystem
+off without downgrading the whole package. "Where feasible" is a
+real qualifier: kernel rules and the install skeleton have no
+sensible off-switch; everything above that floor should.
+
+## Rollback path — the `Rollback:` line
+
+Every CHANGELOG entry that **introduces or substantially reworks a
+subsystem** names its rollback path in the entry itself via a
+`Rollback:` line:
+
+```md
+* **workspace:** task-orchestration layer behind `/work` ([abc1234](…))
+  Rollback: set `workspace.enabled: false` in `.agent-settings.yml`.
+```
+
+The rollback path is the disable flag from the section above, a
+revert instruction, or a downgrade note — whatever actually undoes
+the subsystem for a consumer. Enforced mechanically:
+`src/scripts/lint_changelog_rollback.ts` fails when a new minor /
+major section (`## [X.Y.0]`) contains no `Rollback:` line. The gate
+only fires for versions **strictly greater** than the version in
+`package.json` at lint time, so historical sections never retro-fail;
+entry shape stays governed by
+[`CHANGELOG-conventions.md`](CHANGELOG-conventions.md).
+
+## Consumer matrix is the floor for every release
+
+The pack-based consumer matrix —
+[`../distribution/consumer-matrix.md`](../distribution/consumer-matrix.md)
+(authored in parallel; forward link) — is the **floor** for every
+release: no release ships a change that knowingly breaks a supported
+cell of that matrix without the break being declared under
+`### BREAKING CHANGES` and reflected in the matrix in the same
+release.
+
+## REJECTED — consumer-facing effort ratio
+
+The proposed meta-ratio *"≥ 2/3 of effort per release must be
+consumer-facing"* was **CUT by council 2026-07-10**
+(claude-sonnet-4-5 + gpt-4o, unanimous) as a **gameable vanity
+metric**: effort is unmeasurable at review time, "consumer-facing"
+is reclassifiable at will, and the ratio punishes necessary
+infrastructure releases. Recorded here so it is not re-proposed;
+re-opening it requires new evidence per the decision-revisit gate.
+
+## Cross-references
+
+- [`CHANGELOG-conventions.md`](CHANGELOG-conventions.md) — entry
+  shape the `Rollback:` line extends.
+- [`release-pr-gating.md`](release-pr-gating.md) — release-PR shape
+  detection; the sizing judgment happens at labeling time.
+- [`../release-runbook.md`](../release-runbook.md) — the cut
+  procedure this contract's pre-flight check lives in.
+- `src/scripts/lint_changelog_rollback.ts` — the mechanized
+  `Rollback:` gate (run `--selftest` for its fixture proof).

package/docs/contracts/surface-agent-contracts.md

@@ -0,0 +1,153 @@
+# Surface-Agent Contracts — medium invariants, not one generic agent
+
+Backbone for `road-to-surface-specific-agent-contracts`.
+One generic agent does every medium badly. Each **surface** (spreadsheet, deck,
+document, browser, mobile/chat, code, …) has non-negotiable local invariants and
+its own verification truth source. This contract names them, maps them to owner
+skills, and defines how the agent detects a surface, resolves conflicts, and
+hands off between surfaces — advisory first (staged rollout below).
+
+Capability + honest-degrade for the *verification* primitives these contracts
+rely on is the sibling [`design-artifact-verification`](design-artifact-verification.md)
+(browser / screenshot / pdf_render / doc_export / image_decode / static_inspect);
+this contract adds the office/data primitives and the surface-routing layer.
+
+## Iron Law — the medium's truth source verifies the work
+
+```
+EACH SURFACE HAS A NON-NEGOTIABLE INVARIANT AND ITS OWN TRUTH SOURCE.
+VERIFY WITH THE MEDIUM'S TRUTH SOURCE — A FORMULA READ-BACK, A RENDERED SLIDE,
+A FETCHED PAGE — NEVER A GENERIC "LOOKS RIGHT". WHEN THE SURFACE TOOL IS
+ABSENT, SAY WHAT COULD NOT BE VERIFIED — NEVER PRETEND THE MEDIUM STEP RAN.
+```
+
+## Surface detection — before applying any surface rule
+
+Resolve the surface from these signals, in priority order:
+
+1. **Explicit file type** — `.xlsx`/`.csv` → spreadsheet, `.pptx`/`.key` → deck, `.docx`/`.md` → document, `.ipynb` → notebook.
+2. **Requested output format** — "as a deck", "export to PDF", "a spreadsheet".
+3. **Named tool / plugin / connector** — a named app connector wins over generic browsing.
+4. **User environment** — mobile/chat host vs desktop IDE vs CI.
+5. **Data shape** — tabular/numeric → spreadsheet; slides → deck; prose → document.
+6. **Task verb** — "chart", "model", "present", "browse", "refactor".
+7. **Target deliverable** — what the user will actually use.
+
+**Ambiguity handling.** When ≥2 surfaces plausibly apply and the choice changes
+the work materially, ask ONE compact question (per
+[`ask-when-uncertain`](../../src/rules/ask-when-uncertain.md)); when the user
+already constrained it, proceed and state the surface assumption.
+
+## Surface conflict rule
+
+When the user asks for output **native to a different connected surface**,
+delegate to (or ask to enable) that surface — do not force a local workaround.
+A request for a spreadsheet answered with a markdown table, or a deck answered
+with prose, is a surface violation. Prefer the connected surface; if it is
+unavailable, say so and offer the degraded form explicitly as degraded.
+
+## Surface taxonomy
+
+Each surface records: **owner** skills/commands · **allowed** tools · **forbidden**
+shortcuts · **truth source** (how the medium verifies) · **handoff** in/out ·
+**trigger** examples · **capability** requirement · **degrade** language.
+
+| Surface | Owner skills | Forbidden shortcut | Truth source | Capability → degrade |
+|---|---|---|---|---|
+| **code** | `scope-control`/`verify-before-complete` (rules), stack skills | edit unread files; broad refactor around a fix | tests + type-checker + fresh run | local exec → static-only caveat |
+| **design** | `fe-design`, `design-review`, `existing-ui-audit` | taste before inspecting the system | rendered artifact ([design-artifact-verification](design-artifact-verification.md)) | browser/screenshot → static caveat |
+| **spreadsheet** | `spreadsheet-authoring` (Phase 2) | hardcode a computed value; unofficial financial source unmarked | formula read-back after write | native tooling → exported-file only → "cannot verify" |
+| **document** | `doc-coauthoring`, `markitdown` | rasterize selectable text to PDF | open/export readback | doc parser → format caveat |
+| **deck** | `html-deck` | build slides before an outline; tiny text | export + slide render | deck export → outline-only caveat |
+| **browser** | `browser` surface (Phase 4), MCP fetch | invent a URL; fetch when not needed | the fetched page itself | fetch → "not fetched, cannot confirm" |
+| **mobile/chat** | interaction floor (Phase 5) | markdown tables in narrow chat; multi-question walls | the host's rendering | tappable UI → concise text choices |
+| **research** | `research:deep`/`research:report` | claim without a retrieved source | per-part grounding + disconfirmation | — |
+| **visualizer/diagram** | `html-deck`, image skills | decorative chart over the data's shape | the rendered diagram | render → described-structure caveat |
+| **cowork/dispatch** | `subagent-orchestration` | one agent doing parallel-safe work serially | verified subagent returns | spawn primitive → in-session |
+| **MCP/app connector** | `mcp` | generic web search when a connector fits | the connector's own result | connector present → suggest/opt-in |
+
+This taxonomy table **is** the canonical work-surface map. (Note: the existing
+`src/config/surface-matrix.yml` is a *different* concept — per-tool **install-surface**
+de-duplication, set-equality-enforced against `install.ts::USER_SCOPE_PATHS` by
+`lint_surface_matrix`; extending it with *work* surfaces would break that
+linter, so the work-surface map lives here, not there.) Host verification
+capability is `src/config/host-capabilities.yml` +
+[`design-artifact-verification`](design-artifact-verification.md). Carrier
+choice vs host capability vs these invariants stay aligned with the
+artifact-routing work — do not let the three diverge.
+
+## Staged rollout
+
+Each surface contract: **advisory** (skills reference the invariant) →
+**routed** (owner skills updated + eval fixtures pass) → **default-on** only
+once the host capability/degrade behaviour is documented for that surface. A
+contract is never default-on for a host class that cannot run the surface's
+truth-source check — it stays advisory + caveat there.
+
+## Cross-surface handoff envelope
+
+When work moves between surfaces (spreadsheet → deck, research → document,
+browser evidence → report, design prototype → production code), the source
+surface emits a **handoff envelope** the target consumes instead of redoing
+work:
+
+```
+source_surface · target_surface · user_goal · assets/files ·
+constraints · verification_already_done · pending_checks ·
+capability_limits · assumptions · privacy/source_restrictions
+```
+
+- The target surface **trusts `verification_already_done`** and does not repeat
+  it; it runs only `pending_checks`.
+- The target honours `privacy/source_restrictions` — a source-specific
+  restriction (e.g. an internal-only dataset) is never widened by the handoff.
+- **Degrade:** if the target surface's tooling is absent, the envelope remains a
+  durable **plan** (what to do + what is verified) — never a faked generated
+  artifact.
+
+## Mobile/chat interaction floor
+
+Interaction style is host-sensitive, not one verbose desktop default.
+
+- **Narrow-chat output.** Avoid markdown tables in a narrow chat host; use short
+  prose/bullets. Keep post-tool summaries short.
+- **Ask at most one compact question**, and only when it changes the work:
+  - **No options** when the user asked for the agent's *analysis* of A vs B — give the recommendation (fixture `ssac-a-or-b-analysis`).
+  - **Offer options** when *eliciting a preference* — tappable choices where the host supports them, degrading to concise text choices otherwise (fixture `ssac-preference-elicitation`).
+  - **Proceed on stated constraints** when the prompt already fixes them — no redundant questions (fixture `ssac-enough-constraints-no-question`).
+
+## Code surface — audit dispositions (Phase 6)
+
+The external code-prompt mechanisms, audited against existing rules — **covered**
+(cite the owner, do not duplicate), **tightened** (a note added), or **rejected**
+(host-specific):
+
+| Mechanism | Disposition | Owner / note |
+|---|---|---|
+| Read before proposing | **covered** | `think-before-action`, `source-discovery-gate` (fixture `ssac-edit-unread-file`) |
+| Minimal scoped changes | **covered** | `minimal-safe-diff` (fixture `ssac-broad-refactor-around-bugfix`) |
+| Todo/task visibility | **covered** | host task tooling + roadmap loop; no new rule |
+| Parallel independent exploration | **tighten** | note in `subagent-orchestration` / this contract's cowork row — sequential independent reads when parallel is available is a miss |
+| Specialized tools over shell | **covered** | `mcp` § tool-tier ladder (execution-discipline harvest) |
+| No shell as user communication | **covered** | `output-discipline` / `direct-answers` |
+| Line-specific references | **covered** | `file_path:line` convention in host instructions |
+| No time estimates | **covered** | `direct-answers` § no-duration (execution-discipline harvest) |
+| Fresh verification before "done" | **covered** | `verify-before-complete` (fixture `ssac-claim-done-without-verification`) |
+
+No new code-surface rule is created — the deltas are already owned; the one
+**tighten** (parallel-safe exploration) is recorded here + in the cowork row. No
+Codex/host-specific phrasing is adopted.
+
+## Rejected (host/vendor-specific — not adopted)
+
+Vendor-specific tool names, per-host UI affordance details, and single-provider
+prompt phrasings from the source family are **not** adopted here — this contract
+encodes surface invariants, not one vendor's tooling. Per-phase rejects are
+recorded in the roadmap.
+
+## Related
+
+- [`design-artifact-verification`](design-artifact-verification.md) — verification-primitive capability + honest-degrade (design surface).
+- [`design-artifact-lifecycle`](design-artifact-lifecycle.md) — the design surface's own lifecycle.
+- [`host-capability-manifest`](../../src/agent-src/contexts/execution/host-capability-manifest.md) — subagent primitives (cowork/dispatch surface).
+- [`tests/surface-contracts/eval-fixtures.md`](../../tests/surface-contracts/eval-fixtures.md) — the surface-contract eval fixtures.

package/docs/contracts/write-engine.md

@@ -65,7 +65,8 @@ One question per turn, in this order:
 Modifiers may be supplied via flags (`--tone=casual --length=200
 --channel=linkedin-post --audience="early-stage founders"`) to skip
 the interactive interview. `--as=<slug>` selects the ghostwriter
-non-interactively for `/ghostwriter:write` and the alias.
+non-interactively for `/ghostwriter:write` and the alias. `--raw`
+skips the step-4b humanize audit for this run (see § 4b).
 
 #### Per-channel defaults
 
@@ -102,6 +103,42 @@ Emit the body as a single fenced markdown block. The body MUST:
 - Respect `style.fingerprint.hashtag_rules` and `emoji_rules`.
 - Stay within ±15% of the requested length.
 
+### 4b. Humanize audit (default-on, `--raw` opts out)
+
+After drafting and before the footer, run the AI-tell audit from the
+[`humanizer`](../../src/skills/humanizer/SKILL.md) skill against the
+draft body:
+
+1. Ask: "What makes this draft read AI-generated?" — audit against the
+   pattern catalog (`src/skills/humanizer/data/patterns.md`), counting
+   clusters, never isolated hits.
+2. Revise the draft to clear the audit findings while preserving the
+   step-4 fingerprint constraints and full coverage.
+3. Where a runtime is available, verify the final body with
+   `npx tsx src/scripts/detect_ai_tells.ts --stdin --fail` under the
+   thresholds from the consumer's `humanizer:` block in
+   `.agent-project-settings.yml` (defaults: hard 0, cluster score 3 per
+   500 words, dash density 2 per 500 words). No runtime → the prose
+   audit in (1) is the pass; do not skip it.
+
+Precedence and scope rules (binding, not judgment calls):
+
+- **Fingerprint wins.** When the profile's captured voice legitimately
+  uses a watched pattern (a figure who genuinely writes in em dashes,
+  `emoji_rules: allowed`, hashtag rules), the step-4 fingerprint
+  constraint is authoritative and the corresponding tell is suppressed
+  for that run.
+- **The disclosure footer (§ 5) is exempt.** It is a literal template
+  string appended after this step — the audit never inspects, rewords,
+  or removes it.
+- **Technical/reference output is excluded.** When the requested
+  artifact is reference or technical documentation, skip step 4b and
+  say so — neutral, plain prose is the correct register there.
+- **`--raw` opts out per run.** The flag skips step 4b entirely (for
+  deliberate neutral-register output); it never touches the footer
+  rules. Default is on for every engine consumer
+  (`humanizer.write_engine: on`).
+
 ### 5. Append the disclosure footer (ghostwriter only)
 
 For ghostwriter consumers, append on its own line, separated by a

package/docs/customization.md

@@ -406,6 +406,18 @@ agents/
 Full classification (git policy, retention, owner) for every allowed entry:
 [`docs/contracts/agents-layout.md`](contracts/agents-layout.md).
 
+#### Environment bootstrap (optional)
+
+If standing up your project takes more than a package install — starting
+services, seeding fixtures, generating config — declare a single **`env-bootstrap`**
+entry in your runner file (a `Taskfile.yml` / `Makefile` target or a
+`package.json` script named `env-bootstrap`). When present, the agent surfaces
+it as the suggested first action at worktree/session stand-up (see the
+`using-git-worktrees` skill § 5) — **suggest-only, never auto-run**. This gives
+long-running work one deterministic stand-up entry instead of re-deriving it
+each session. Purely optional: with no entry, dependency install + a green
+baseline is the whole stand-up.
+
 #### User inbox workflow (`agents/tmp/` → `agents/tmp.old/`)
 
 Drop a note or draft into `agents/tmp/` and point a command at it

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

@@ -1,3 +1,14 @@
+---
+adr: 002
+status: accepted
+date: 2026-05-06
+decision: kernel-bucket-overrides
+supersedes: —
+superseded_by: —
+phase: road-to-kernel-and-router · P2.2
+type: structural
+---
+
 # ADR-002 — Kernel-Bucket Cap Raise (25k → 26k) and Per-Rule Iron-Law Overrides
 
 - **Status:** Accepted (2026-05-06)

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

@@ -1,3 +1,14 @@
+---
+adr: 003
+status: accepted
+date: 2026-05-07
+decision: flat-cluster-subs-and-colon-syntax
+supersedes: —
+superseded_by: —
+phase: command-cluster contract (Phase 2 follow-up)
+type: structural
+---
+
 # ADR-003 — Flat Cluster Sub-Commands and Colon-Canonical Invocation
 
 - **Status:** Accepted (2026-05-07)

package/docs/decisions/ADR-006-skill-tools-python-pilot.md

@@ -5,7 +5,7 @@ date: 2026-05-09
 decision: skill-tools-python-pilot-pass
 supersedes: —
 superseded_by: —
-phase: road-to-better-skills-and-profiles · Block D (D1–D5)
+phase: road-to-better-skills-and-profiles · Block D (D1–D5) — historical: Python pilot; zero .py remains post-ADR-200
 ---
 
 # ADR-006 — Skill-Tools Python Pilot: Outcome and Decision

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

@@ -1,6 +1,6 @@
 ---
 adr: 028
-status: accepted
+status: superseded
 date: 2026-05-25
 decision: root-layout
 supersedes: —

package/docs/decisions/ADR-038-canonical-settings-path.md

@@ -1,3 +1,13 @@
+---
+adr: 038
+status: accepted
+date: 2026-06-01
+decision: canonical-settings-path
+supersedes: —
+superseded_by: —
+type: structural
+---
+
 # ADR-038: Canonical settings path is `agents/settings/.agent-settings.yml`
 
 - **Status:** Accepted

package/docs/decisions/ADR-092-defer-command-tier-alias-removal.md

@@ -29,13 +29,16 @@ question with the Phase-3 investigation evidence.
 Investigation findings (`road-to-metadata-and-command-surface-leanness`, Phase 3):
 
 - **Integer-`tier` readers are internal:** `src/cli/commands/commands.ts`
-  (fallback after `visibility`), `src/scripts/audit_command_surface.py`
-  (report column + budget fallback), `src/scripts/build_discovery_manifest.py`
-  (**dual-emits `tier`** into the manifest). `src/cli/python/workspace_hosts.py`
+  (fallback after `visibility`), `src/scripts/audit_command_surface.ts`
+  (report column + budget fallback), `src/scripts/build_discovery_manifest.ts`
+  (**dual-emits `tier`** into the manifest). `src/cli/python/workspace_hosts.ts`
   uses a semantically unrelated host-inventory tier.
+  <!-- paths updated 2026-07-12: every reader migrated to TS during the
+  completed ADR-200 py2ts migration; the original .py list is preserved in
+  git history. -->
 - **The discovery manifest is a published npm artifact** — `package.json`
   `files` + `build:discovery` in `prepack` + `prepublishOnly:
-  check_release_includes_discovery.py`. It dual-emits the integer `tier`.
+  check_release_includes_discovery.ts`. It dual-emits the integer `tier`.
   **External npm consumers that read the integer key are unknown.**
 - The defer rests on a **Runtime Risk that cannot be ruled out** (a consumer
   may register/branch on the integer `tier`), not on evidence that such a
@@ -75,7 +78,7 @@ forcing function so it cannot calcify into permanent debt:
 ## Consequences
 
 - The `tier:` ⇄ `visibility:` dual-field persists during the deferral;
-  drift is mitigated by the `lint_command_tiers.py` consistency check (when
+  drift is mitigated by the `lint_command_tiers.ts` consistency check (when
   both present, they must agree).
 - The removal is **cheaply reversible** if ever executed: restoring the `tier`
   field is a manifest schema patch (< 1h to publish), far below the rollback
@@ -84,6 +87,27 @@ forcing function so it cannot calcify into permanent debt:
 - `road-to-tier-removal.md` institutionalises the trigger so the defer stays
   visible in planning rather than becoming folklore.
 
+## Addendum (2026-07-12) — re-open mechanism mid-flight
+
+Recorded during `road-to-opt-decision-flips` Phase 2; not a re-litigation —
+this ADR's own forcing function is executing:
+
+- **All integer-`tier` readers are now TypeScript** (ADR-200 migration landed
+  on `main`; the reader list above updated in place).
+- **Re-open mechanism #1 shipped:** `build_discovery_manifest.ts` emits the
+  machine-readable `deprecations` block + `sunset` field announcing the
+  `tier` deprecation (road-to-tier-removal Phase 1). Verified in the
+  **released** artifact: npm `8.10.0` (published 2026-07-10) ships
+  `dist/discovery/discovery-manifest.json` with
+  `deprecations[0] = {key: tier, replacement: visibility, since: ADR-092,
+  sunset: null}`.
+- **Soak status:** the soak clock runs since publish; zero tier-related
+  breakage reports (issue sweep 2026-07-12). The unknown-external-consumer
+  hard stop is NOT lifted by the notice alone — the soak must elapse.
+- **Execution continues in `road-to-tier-removal.md`**, revived from
+  `later/` to active on 2026-07-12 with the soak evidence cited in its
+  banner (portfolio-consolidation Phase 2).
+
 ## References
 
 - [ADR-090](ADR-090-visibility-command-frontmatter-field.md) — the deferred

package/docs/decisions/ADR-093-ai-council-config-user-global.md

@@ -1,6 +1,6 @@
 ---
 adr: 093
-status: accepted
+status: superseded
 date: 2026-06-13
 decision: ai-council-config-user-global
 supersedes: —

package/docs/decisions/ADR-100-global-knowledge-card-sharing.md

@@ -11,6 +11,13 @@ type: structural
 
 # ADR-100 — Global cross-project knowledge-card sharing
 
+> **Partial supersession (clarified 2026-07-12):** this ADR supersedes
+> ADR-098 **Decision-10 only** (the measure-then-decide gate for the
+> global layer); every other ADR-098 decision stands. The frontmatter
+> `supersedes:` field carries the bare number because the index
+> link-checker validates it; this note is the qualifier's home.
+
+
 ## Status
 
 Accepted (2026-06-15). Council-designed (claude-sonnet-4-5 + gpt-4o, design

package/docs/decisions/ADR-103-global-knowledge-default-off-until-measured.md

@@ -1,10 +1,10 @@
 ---
 adr: 103
-status: accepted
+status: superseded
 date: 2026-06-16
 decision: global-knowledge-default-off-until-measured
 supersedes: —
-superseded_by: —
+superseded_by: 119
 phase: evidence-v2
 type: structural
 ---

package/docs/decisions/ADR-105-automatic-subagent-orchestration.md

@@ -4,7 +4,7 @@ status: accepted
 date: 2026-06-23
 decision: automatic-subagent-orchestration
 supersedes: —
-superseded_by: —
+superseded_by: — (Decision 2 amended by ADR-117: shipped default ask → on)
 phase: auto-subagent-orchestration
 type: structural
 ---

package/docs/decisions/ADR-114-commit-policy-iron-law-override.md

@@ -1,3 +1,14 @@
+---
+adr: 114
+status: accepted
+date: 2026-07-08
+decision: commit-policy-iron-law-override
+supersedes: —
+superseded_by: —
+phase: kernel-budget overrides (extends ADR-002)
+type: structural
+---
+
 # ADR-114 — commit-policy Iron-Law Override (per-rule cap 2.5k → ceiling 4.0k)
 
 - **Status:** Accepted (2026-07-08)

package/docs/decisions/ADR-115-command-cluster-consolidation-phase-4.md

@@ -85,7 +85,7 @@ not exploit: **nesting `bug-fix` as `bug/fix` keeps the invoked slug
 
 - `docs/contracts/command-clusters.md` — locked table (Phase 4 rows) + the
   new "Bare invocation" section.
-- `agents/roadmaps/road-to-command-structure-optimization.md` — inventory,
+- `agents/roadmaps/archive/road-to-command-structure-optimization.md` — inventory,
   council verdicts, phases.
 - ADR-003 (flat clusters), ADR-041 (controlled verbs), ADR-044 (path-derived
   hyphen slugs).

package/docs/decisions/ADR-116-memory-tripwire-activation-path.md

@@ -5,11 +5,21 @@ date: 2026-07-08
 decision: memory-tripwire-activation-path
 supersedes: —
 superseded_by: —
-phase: road-to-memory-retrieval-economy · Phase 6
+phase: road-to-memory-retrieval-economy · Phase 6 (amended — see 2026-07-12 note)
 ---
 
 # ADR-116 — Memory scale-tripwire activation path: one engine, measured at fire time
 
+> **Amended in practice (recorded 2026-07-12):** the SQLite-FTS5 engine
+> this ADR pre-decided was never built. The activation path was
+> re-resolved by road-to-retrieval-substrate-hardening B2 (done
+> 2026-07-09): a hand-rolled stdlib BM25 + trigram prefilter in
+> `src/scripts/_lib/lexical_index.ts` (no SQLite, ADR-061 honoured),
+> dormant until the `lint_knowledge_scale` tripwire fires (200/type,
+> 500 total). The tripwire thresholds and measurement-at-activation
+> discipline of this ADR stand unchanged; only the engine choice moved.
+
+
 - **Deciders:** maintainer + AI council (anthropic/claude-sonnet-4-5 +
   openai/gpt-4o; disposition debate 2 rounds + engine tie-break 2 rounds,
   2026-07-08 — tie-break converged after the in-repo `node:sqlite`

package/docs/decisions/ADR-117-subagents-auto-default-on.md

@@ -3,10 +3,11 @@ adr: 117
 status: accepted
 date: 2026-07-09
 decision: subagents-auto-default-on
-supersedes: 105
+supersedes: —
 superseded_by: —
 phase: auto-subagent-orchestration
 type: structural
+amends: 105 (Decision 2 only — the shipped default; the contract itself stands)
 ---
 
 # ADR-117 — Flip `subagents.auto` shipped default to `on` (host-gated) on bounded-downside re-evaluation