@event4u/agent-config 9.8.0 → 9.10.0

package/docs/adrs/router/0001-three-tier-routing.md

@@ -1,119 +0,0 @@
-# ADR 0001 — Three-tier rule router (kernel · tier-1 · tier-2)
-
-> Area: `router` · Status: accepted · Date: 2026-05-16 · Type: retrospective
-> Roadmap: an internal parity roadmap (local-only) Phase 4 Step 3
-> Supersedes: —
-
-## Context
-
-Every rule in `.agent-src.uncondensed/rules/` loads into a host
-agent's system prompt. Loading them all is wasteful (the workspace
-budget is finite) and noisy (irrelevant rules degrade attention).
-The kernel-membership work
-([`docs/contracts/kernel-membership.md`](../../contracts/kernel-membership.md))
-proved 9 rules are unconditionally relevant; the rest are
-situational.
-
-The router question is: **how does a non-kernel rule declare when it
-fires, what artefacts carry its body, and how does the host agent
-look that up cheaply at session start**.
-
-## Decision
-
-**Three tiers, declared in rule frontmatter, compiled into a single
-[`dist/router.json`](../../../dist/router.json), tracked in git.** Host
-agents read `dist/router.json` once per session.
-
-### Tier semantics
-
-| Tier | Load behaviour | Workspace cost |
-|---|---|---|
-| `kernel` | Body injected verbatim every turn | High (capped per ADR-002 · ≤ 26k chars) |
-| `tier-1` | Description stub injected; body loaded on trigger | Low (stub only) |
-| `tier-2` | No injection; loaded only on explicit trigger match | Zero (until activated) |
-
-The tier value sits in the rule's `tier:` frontmatter key; the
-schema enforces the enum (`scripts/schemas/rule.schema.json`).
-
-### Trigger vocabulary
-
-Six match kinds, OR-combined across entries, AND-combined within an
-entry's qualifier object (full grammar:
-[`rule-router.md`](../../contracts/rule-router.md) § `triggers:` shape):
-
-`keyword` · `phrase` · `intent` · `file_pattern` · `path_prefix` ·
-`command`. Kernel rules **forbid** `triggers:` — they are
-unconditional by definition.
-
-### Compilation pipeline
-
-1. `scripts/sync.py` projects `.agent-src.uncondensed/` → `dist/agent-src/`.
-2. `scripts/compile_router.py` walks rule frontmatter, validates the
-   `routes_to:` targets exist on disk, writes `dist/router.json`.
-3. `scripts/skill_linter.py` runs the bidirectional check: every
-   `routes_to:` target has a matching `triggered_by:` back-ref.
-
-### `routes_to:` resolution
-
-Plain `<kind>:<id>` strings; kinds are `skill`, `guideline`,
-`command`, `contract`. Resolution paths are pinned in
-[`rule-router.md`](../../contracts/rule-router.md) lines 73–77 and
-enforced by the linter.
-
-## Considered alternatives
-
-### Alt 1 — Single flat list (rejected)
-
-All rules `always`-load.
-
-**Why rejected:** the rules tree is ~70 entries; even with telegraph
-condensation the workspace budget blows past the kernel cap. Static
-loading wastes attention on rules irrelevant to the current turn.
-
-### Alt 2 — Pure-runtime semantic search (rejected)
-
-Embed every rule, semantic-match the turn against the index, load
-top-k.
-
-**Why rejected:** introduces a runtime (this package is a governance
-layer, not a runtime — see step-11 scope boundary); index drift adds
-a non-trivial maintenance surface; first-turn cold-start is slow.
-
-### Alt 3 — Two tiers (kernel + load-on-trigger, rejected)
-
-Skip the `tier-1` description-stub layer.
-
-**Why rejected:** the stub layer carries 70 % of the "does this turn
-need this rule?" signal at < 5 % of the body cost. Removing it
-forces the host agent to either over-load (cost spike) or
-mis-trigger (correctness loss).
-
-### Alt 4 — Three-tier with frontmatter declaration (accepted)
-
-The chosen path. Kernel + tier-1 stubs (balanced + full profiles) +
-tier-2 (full profile only). Cost stays bounded; trigger declarations
-diff cleanly in PRs.
-
-## Consequences
-
-- **Positive:** every rule declares its activation cost; the kernel
-  cap is enforceable; the host agent's session-start cost is one
-  JSON read; the `routes_to:` link makes "where does this rule's
-  body live?" answerable without grep.
-- **Negative:** two layers of indirection (rule → stub → body)
-  raise the bar for new contributors. Mitigated by
-  [`rule-router.md`](../../contracts/rule-router.md) being the
-  single citable contract and the linter catching shape errors.
-- **Reversal cost:** flatten by removing tier-1 / tier-2 distinction
-  in the compiler — `dist/router.json` becomes a list of all rules. The
-  rule frontmatter stays valid (extra fields are tolerated by
-  Draft-07 once `additionalProperties` is relaxed).
-
-## References
-
-- [`docs/contracts/rule-router.md`](../../contracts/rule-router.md) — frontmatter contract.
-- [`docs/contracts/kernel-membership.md`](../../contracts/kernel-membership.md) — kernel cap.
-- [`dist/router.json`](../../../dist/router.json) — compiled output.
-- [`scripts/compile_router.py`](../../../src/scripts/compile_router.py) — compiler.
-- [`scripts/schemas/rule.schema.json`](../../../src/scripts/schemas/rule.schema.json) — schema.
-- an internal parity roadmap (local-only) Phase 4 Step 3 — origin.

package/docs/adrs/router/README.md

@@ -1,9 +0,0 @@
-# ADRs — `router`
-
-> router.json shape, tier semantics, dispatch precedence.
-
-Contract: [`docs/contracts/rule-router.md`](../../../docs/contracts/rule-router.md).
-
-| # | Title | Status | Date | Supersedes |
-|---|---|---|---|---|
-| [0001](0001-three-tier-routing.md) | Three Tier Routing | — | — | — |

package/docs/adrs/schema/0001-json-schema-frontmatter.md

@@ -1,102 +0,0 @@
-# ADR 0001 — JSON Schema as the frontmatter source of truth
-
-> Area: `schema` · Status: accepted · Date: 2026-05-16 · Type: retrospective
-> Roadmap: an internal parity roadmap (local-only) Phase 4 Step 3
-> Supersedes: —
-
-## Context
-
-Skills, rules, commands, and personas all declare YAML frontmatter
-with required and optional keys. Validation needs to be:
-
-1. Machine-checkable on every PR (no "guideline" enforcement).
-2. Diff-readable so the contract drift is visible.
-3. Tool-agnostic — the same artefacts ship to Claude, Cursor, Cline,
-   Windsurf, and Augment, all of which parse the same YAML.
-
-The contract is documented for humans in
-[`agents/reference/docs/frontmatter-contract.md`](../../../agents/reference/docs/frontmatter-contract.md);
-the question this ADR records is **how that contract is enforced**.
-
-## Decision
-
-**JSON Schema (Draft-07) files in
-[`scripts/schemas/`](../../../src/scripts/schemas/) are the
-machine-readable source of truth.** The human contract document
-defers to the schema (`$comment` in each schema file pins
-`agents/reference/docs/frontmatter-contract.md` as the source).
-
-### Schema files
-
-| Type | Schema | Validator entry-point |
-|---|---|---|
-| Skill | `scripts/schemas/skill.schema.json` | `scripts/skill_linter.py` |
-| Rule | `scripts/schemas/rule.schema.json` | `scripts/skill_linter.py` |
-| Command | `scripts/schemas/command.schema.json` | `scripts/validate_frontmatter.py` |
-| Persona | `scripts/schemas/persona.schema.json` | `scripts/validate_frontmatter.py` |
-
-### Required-key threshold
-
-A key is **required** (in the schema's `required:` array) if ≥ 95 %
-of files in the type declare it. Everything else is optional. The
-threshold is documented inline in
-[`frontmatter-contract.md`](../../../agents/reference/docs/frontmatter-contract.md)
-§ "Definition of required". Re-derive counts with
-`python3 scripts/inventory_frontmatter.py`.
-
-### Validation hooks
-
-- `task lint-skills` — runs `skill_linter.py` against all skills + rules.
-- `task ci` — wraps `lint-skills` plus router + smoke smokes.
-- Smoke contract `scripts/smoke/schema.sh` — fast random-sample check
-  for PRs touching `.agent-src.uncondensed/**` (see
-  [`docs/contracts/smoke-contracts.md`](../../contracts/smoke-contracts.md)).
-
-## Considered alternatives
-
-### Alt 1 — Inline regex in the linter (rejected)
-
-Hard-code shape checks in `skill_linter.py`.
-
-**Why rejected:** the linter becomes the contract, the contract is
-hidden in Python, and the artefacts can't be validated by external
-tools (CI, editors, IDE plugins). Cross-tool portability is the
-whole point of YAML frontmatter — the schema must be portable too.
-
-### Alt 2 — Pydantic / dataclass models (rejected)
-
-Validate via typed Python models.
-
-**Why rejected:** ties validation to Python runtime, prevents
-JS/TS / Node tooling from reusing the same contract, and forces a
-non-trivial dependency on every consumer that wants to validate
-their own artefacts. JSON Schema is the lingua franca.
-
-### Alt 3 — JSON Schema Draft-07 (accepted)
-
-The chosen path. One source-of-truth file per artefact type,
-referenced by Python linter today, reusable by Node / VS Code /
-JetBrains / any JSON-Schema-aware tool tomorrow.
-
-## Consequences
-
-- **Positive:** schemas are diffable; new keys land via PR with
-  reviewable shape changes; non-Python tools can validate the same
-  contract; the linter stays thin.
-- **Negative:** Draft-07 is older than Draft-2020-12; some keyword
-  niceties (`unevaluatedProperties`, conditional `then`/`else`) are
-  awkward. Mitigated by `additionalProperties: false` plus
-  `oneOf` / `if`-then composition where needed.
-- **Reversal cost:** the linter is the only consumer today; replacing
-  the schema with Pydantic models would be a one-PR swap. The choice
-  is reversible without contract churn.
-
-## References
-
-- [`scripts/schemas/skill.schema.json`](../../../src/scripts/schemas/skill.schema.json) — skill contract.
-- [`scripts/schemas/rule.schema.json`](../../../src/scripts/schemas/rule.schema.json) — rule contract.
-- [`scripts/schemas/command.schema.json`](../../../src/scripts/schemas/command.schema.json) — command contract.
-- [`scripts/schemas/persona.schema.json`](../../../src/scripts/schemas/persona.schema.json) — persona contract.
-- [`agents/reference/docs/frontmatter-contract.md`](../../../agents/reference/docs/frontmatter-contract.md) — human-readable contract.
-- [`scripts/skill_linter.py`](../../../src/scripts/skill_linter.py) — primary validator.
-- an internal parity roadmap (local-only) Phase 4 Step 3 — origin.

package/docs/adrs/schema/README.md

@@ -1,9 +0,0 @@
-# ADRs — `schema`
-
-> Frontmatter schemas, v2 rigor, lint behaviour for skills / rules / commands.
-
-Contract: [`agents/reference/docs/frontmatter-contract.md`](../../../agents/reference/docs/frontmatter-contract.md).
-
-| # | Title | Status | Date | Supersedes |
-|---|---|---|---|---|
-| [0001](0001-json-schema-frontmatter.md) | Json Schema Frontmatter | — | — | — |

package/docs/adrs/smoke/0001-per-tier-smoke-scripts.md

@@ -1,99 +0,0 @@
-# ADR 0001 — Per-tier smoke scripts (kernel · router · schema · skills)
-
-> Area: `smoke` · Status: accepted · Date: 2026-05-16 · Type: retrospective
-> Roadmap: an internal parity roadmap (local-only) Phase 4 Step 3
-> Supersedes: —
-
-## Context
-
-The North-Star audit
-(an internal findings note (local-only))
-flagged "smoke contracts" as an absorbed the external runtime pattern: every
-high-traffic tier needs a fast, deterministic, measurable check that
-runs in CI and surfaces regressions before they reach the rules /
-router / schema / skill linter pipelines.
-
-The full `task ci` run is ≥ 90 s and exercises every linter. That's
-fine for merge gates; it's too slow for path-change feedback on PRs
-that touch one tier in isolation.
-
-## Decision
-
-**One smoke script per tier, each ≤ 30 s, each emitting a baseline
-declaration as its last stdout line.** Scripts live under
-[`scripts/smoke/`](../../../src/scripts/smoke/):
-
-| Tier | Script | Validates | Path-trigger globs |
-|---|---|---|---|
-| Kernel | [`kernel.sh`](../../../src/scripts/smoke/kernel.sh) | 9 kernel rules present, char-budget respected | `.agent-src.uncondensed/rules/**`, `docs/contracts/kernel-membership.md` |
-| Router | [`router.sh`](../../../src/scripts/smoke/router.sh) | `dist/router.json` compiles, all `routes_to:` resolve | `dist/router.json`, `.agent-src.uncondensed/rules/**` |
-| Schema | [`schema.sh`](../../../src/scripts/smoke/schema.sh) | Random skill / rule sample validates against JSON Schema | `scripts/schemas/**`, `.agent-src.uncondensed/{rules,skills}/**` |
-| Skills | [`skills.sh`](../../../src/scripts/smoke/skills.sh) | 5 random skills pass frontmatter + `name == dir` | `.agent-src.uncondensed/skills/**` |
-
-### Runtime contract
-
-Per [`smoke-contracts.md`](../../contracts/smoke-contracts.md) § 1:
-
-| Limit | Value |
-|---|---:|
-| Wall time | ≤ 30 s |
-| External I/O | filesystem only — no network, no MCP |
-| Output | last stdout line = baseline declaration |
-| Exit code | non-zero on baseline regression |
-
-### CI wiring
-
-[`.github/workflows/smoke.yml`](../../../.github/workflows/smoke.yml)
-dispatches each smoke independently on path-trigger match. Local
-aggregator: `task smoke` (sub-tasks `task smoke:{kernel,router,schema,skills}`)
-wired in [`taskfiles/engine.yml`](../../../taskfiles/engine.yml).
-
-### Baseline declarations (lock-in 2026-05-16)
-
-- Kernel: `9 rules · 23 / 26 kB used (88 %) · 0 fence breaches`.
-- Router: `tier_1: N · tier_2: M · 0 unresolved routes`.
-- Schema: deterministic seed = epoch day · 10 random files validated.
-- Skills: deterministic seed = epoch day · `210 skills · 5/5 pass`.
-
-## Considered alternatives
-
-### Alt 1 — One monolithic smoke (rejected)
-
-Single `task smoke` running every check.
-
-**Why rejected:** path-change PRs pay the full cost every time;
-flaky tier-X regression masks tier-Y signal; output is harder to
-diff. The per-tier split costs four files and saves CI minutes.
-
-### Alt 2 — Inline-in-`task ci` only (rejected)
-
-Skip the smoke layer; rely on `task ci` for everything.
-
-**Why rejected:** `task ci` is the merge gate, not the feedback
-loop. Smokes are the cheap-and-fast layer between push and review.
-
-### Alt 3 — Per-tier, ≤ 30 s budget, baseline-declaring (accepted)
-
-The chosen path. One script per tier, declared budget, declared
-baseline, CI-dispatched on path-trigger.
-
-## Consequences
-
-- **Positive:** PRs touching one tier get tier-specific feedback in
-  ≤ 30 s; baseline declarations are diff-readable so regressions
-  surface in PR descriptions; the `task ci` merge gate stays the
-  authoritative full-run.
-- **Negative:** four scripts to maintain, one workflow file, one
-  taskfile entry. Mitigated by the runtime contract — a smoke that
-  approaches 30 s gets split, not optimised in place.
-- **Reversal cost:** delete `smoke.yml`; the scripts stay as opt-in
-  local checks (`task smoke:*`). No contract churn.
-
-## References
-
-- [`docs/contracts/smoke-contracts.md`](../../contracts/smoke-contracts.md) — runtime + path-trigger contract.
-- [`scripts/smoke/`](../../../src/scripts/smoke/) — four scripts.
-- [`.github/workflows/smoke.yml`](../../../.github/workflows/smoke.yml) — CI dispatch.
-- [`taskfiles/engine.yml`](../../../taskfiles/engine.yml) — local aggregator.
-- an internal findings note (local-only) § 5 — origin pattern.
-- an internal parity roadmap (local-only) Phase 3 (delivery) + Phase 4 Step 3 (this ADR).

package/docs/adrs/smoke/README.md

@@ -1,9 +0,0 @@
-# ADRs — `smoke`
-
-> Per-tier smoke contracts, baseline locks, regression gates.
-
-Contract: [`docs/contracts/smoke-contracts.md`](../../../docs/contracts/smoke-contracts.md).
-
-| # | Title | Status | Date | Supersedes |
-|---|---|---|---|---|
-| [0001](0001-per-tier-smoke-scripts.md) | Per Tier Smoke Scripts | — | — | — |

package/docs/adrs/telegraph/0001-default-off-until-bench.md

@@ -1,93 +0,0 @@
-# ADR 0001 — Telegraph condensation default stays OFF until `task bench`
-
-> Area: `telegraph` · Status: accepted · Date: 2026-05-16 · Type: retrospective
-> Roadmap: an internal parity roadmap (local-only) Phase 4 Step 3
-> Supersedes: —
-
-## Context
-
-Telegraph-speak is a turn-time condensation dialect that trades English
-grammar for tokens. The dialect is documented in
-[`telegraph-speak`](../../../.agent-src.uncondensed/rules/telegraph-speak.md);
-the question this ADR records is **whether the dialect should default
-ON for all consumers**.
-
-The North-Star council ([`council-synthesis.md` § 7](../../../agents/evidence/audits/2026-05-14-north-star/council-synthesis.md))
-landed split: two voices (token-efficiency, ops) argued default-ON
-saves 40 %+ tokens on long sessions; two voices (UX, governance)
-argued default-ON degrades novice readability and locks in a dialect
-nobody has measured against the real benchmark corpus.
-
-## Decision
-
-**`telegraph.speak_scope` defaults `off`**. Carve-outs (security ·
-destructive · multi-step · code blocks · paths · numbered options ·
-Iron-Law markers) stay in the rule body so the dialect is **defined**
-even when **inactive**. The default flips only when `task bench`
-produces measured win/loss numbers against the locked 25-prompt corpus.
-
-Authoritative kill-criterion:
-[`docs/contracts/condensation-default-kill-criterion.md`](../../contracts/condensation-default-kill-criterion.md)
-§ Rule lines 8–11.
-
-### Decision owner
-
-`step-4-measurement-and-benchmark.md` closeout phase. Not this doc.
-Not `step-99`. Not the North-Star council. The closeout reads
-`docs/parity/bench.json` and applies exactly one of three branches
-defined in the kill-criterion.
-
-### Default-ON gates (all required)
-
-1. ≥ 30 % token reduction averaged across the 25-prompt corpus.
-2. ≤ 5 % regression on the readability score from the same run.
-3. Reversibility check passes (telegraph → English round-trip ≥ 95 %
-   semantic preservation per the bench scorer).
-
-Any gate fails → default stays OFF. Re-bench after the next dialect
-edit.
-
-## Considered alternatives
-
-### Alt 1 — Default ON now (rejected)
-
-Flip the default immediately; let consumers opt out.
-
-**Why rejected:** no measured baseline exists. The two pro voices'
-40 % claim is from informal turn-snippet comparisons, not the locked
-corpus. Default-on without measurement is exactly the external-runtime-style
-"trust me it's faster" pattern the audit calls out.
-
-### Alt 2 — Default ON for cost-profile `lean`, OFF for `default` (rejected)
-
-Couple the default to the cost profile.
-
-**Why rejected:** cost profiles already carry profile-specific budget
-ladders and smoke contracts. Adding a dialect coupling makes the
-matrix `2 × N` instead of `1 × N`. The kill-criterion measurement is
-the same regardless of profile — make the decision once.
-
-### Alt 3 — Keep default OFF, measure first (accepted)
-
-The chosen path. Dialect ships, stays dormant, gets benched, then
-either ships default-on or gets deprecated. No middle state.
-
-## Consequences
-
-- **Positive:** new consumers get standard English by default; the
-  novice-onboarding path is unaffected; the dialect is auditable and
-  measurable before it becomes the default cost vector.
-- **Negative:** the 40 %+ token savings are leave-on-table for any
-  consumer who doesn't explicitly opt in. Mitigated by surfacing the
-  flag in `/onboard` once `task bench` lands.
-- **Reversal cost:** flip the default in
-  [`.agent-settings.yml`](../../../.agent-settings.yml.example)
-  template; existing user settings unaffected by template change.
-
-## References
-
-- [`docs/contracts/condensation-default-kill-criterion.md`](../../contracts/condensation-default-kill-criterion.md) — kill-criterion contract.
-- [`.agent-src.uncondensed/rules/telegraph-speak.md`](../../../.agent-src.uncondensed/rules/telegraph-speak.md) — dialect definition.
-- [`agents/roadmaps/step-4-measurement-and-benchmark.md`](../../../agents/roadmaps/step-4-measurement-and-benchmark.md) — bench owner.
-- [`agents/evidence/audits/2026-05-14-north-star/council-synthesis.md`](../../../agents/evidence/audits/2026-05-14-north-star/council-synthesis.md) § 7 — council split.
-- an internal parity roadmap (local-only) Phase 4 Step 3 — origin.

package/docs/adrs/telegraph/README.md

@@ -1,9 +0,0 @@
-# ADRs — `telegraph`
-
-> Telegraph-speak condensation, decondensation, reversibility guards.
-
-Contract: [`docs/contracts/condensation-default-kill-criterion.md`](../../../docs/contracts/condensation-default-kill-criterion.md).
-
-| # | Title | Status | Date | Supersedes |
-|---|---|---|---|---|
-| [0001](0001-default-off-until-bench.md) | Default Off Until Bench | — | — | — |

package/docs/announcements/2026-05-non-dev-launch.md

@@ -1,79 +0,0 @@
-# Non-dev launch announcements — step-12 Phase 7 L126
-
-Three drafts, one per surface. Drafted via the `ghostwriter` cluster pattern; final voice tuning happens at post-merge surface time.
-
-Status: **drafted, not yet posted**. Posting is out-of-scope for the autonomous merge — it lights up after the README and `--user-type` UX are live in `main`.
-
----
-
-## 1. Product Hunt (no-code tag) — long-form launch post
-
-**Title:** `agent-config — a governed skill suite that finally treats consultants, creators, and finance/ops as first-class AI-tool users`
-
-**Tagline (60 chars):** `AI agent OS for non-developers — no terminal required`
-
-**Body:**
-
-Most "AI assistant" tools assume you write code. The rest assume you just want to chat. `agent-config` is the third option: a **governed skill, rule, and command suite** that gives every AI coding tool (Claude Code, Cursor, Windsurf, Copilot, Augment) a shared playbook — and it works just as well for a marketer drafting launch copy, a consultant building a discovery guide, or a founder modelling runway as it does for an engineer shipping a feature.
-
-What's actually new:
-- **`--user-type` axis.** `npx agent-config init --user-type=creator` loads the ~7 skills relevant to you, not all 195.
-- **Domain safety floors.** PII never leaks into a support macro draft. Health, legal, financial outputs ship with mandatory disclaimers.
-- **No fork required.** All projection trees regenerate from a single source-of-truth; consumer config is one `.agent-settings.yml`.
-
-Open source, MIT. Comments welcome — especially "this is wrong for my workflow, here's why."
-
----
-
-## 2. Indie Hackers — consulting forum post
-
-**Title:** `[Open-source release] A shared skill library for solo consultants who use Claude or ChatGPT every day`
-
-**Body:**
-
-Hey IH —
-
-If you run a one-person consulting practice and you already lean on an AI assistant for discovery guides, positioning audits, voice-of-customer extraction, or stakeholder trade-off matrices — I built (and just open-sourced) a shared library of skills for that.
-
-It's called `agent-config`. The bit relevant to consultants:
-- ~7 skills auto-loaded for `--user-type=consultant` (vs. 195 total) — `discovery-interview`, `competitive-positioning`, `voc-extract`, `stakeholder-tradeoff`, `market-entry-analysis`, `customer-research`, `competitive-moat-analysis`.
-- Works inside Claude Code, Cursor, Windsurf, ChatGPT custom GPTs, and Copilot — same skills, different host.
-- 16-prompt benchmark proves the agent picks the right skill 93.75 % of the time on real consulting prompts.
-
-`npx agent-config init --user-type=consultant` and you're done.
-
-Looking for **5 working consultants** to try it on a real client engagement and let me know where it breaks. Comment or DM if interested.
-
----
-
-## 3. r/ContentWritingJobs — short link-and-ask post
-
-**Title:** `Open-sourced a skill library for marketers and content writers who use AI assistants — looking for 3 real test runs`
-
-**Body:**
-
-Built and released `agent-config` — a governed skill, rule, and command suite for AI assistants (Claude, ChatGPT, Cursor). Includes the skills marketers actually use:
-
-- `voice-and-tone-design` — three-attribute voice + tone-by-context matrix
-- `messaging-architecture` — primary message, supporting proofs, audience matrix
-- `editorial-calendar` — evergreen / campaign / reactive split, per-channel beats
-- `release-comms` — turn changelogs into value-framed announcements
-- `content-funnel-design` — per-stage content shape, mid-funnel leak diagnosis
-
-Setup: `npx agent-config init --user-type=creator`. No coding, no terminal homework beyond one command.
-
-Free, MIT, no telemetry without opt-in. Looking for **3 content writers** to walk through a real brief end-to-end and tell me where the skill descriptions confuse you. I'll credit you in the case studies.
-
-DM or comment.
-
----
-
-## Anti-patterns (what NOT to do)
-
-- **No "the future of AI" framing.** Concrete artefacts only.
-- **No fake testimonials.** Recruit live (5 IH + 3 Reddit + Product Hunt traffic) and run real case studies (Phase 7 L128–131).
-- **No "killer of X" framing.** Position as the missing layer between general assistants and code-only tools.
-
-## Provenance
-
-Drafts produced 2026-05-15 in the step-12 autonomous closure run. Voice tuning at post-merge time per the post-as cluster.

package/docs/announcements/2026-07-honest-cost-sweep-launch.md

@@ -1,84 +0,0 @@
-# Launch story — the anti-thread thread (road-to-adoption-without-narrative-debt, Phase 2)
-
-Status: **drafted, not yet posted** — posting to external channels is a
-maintainer decision and out of scope for an autonomous merge. Voice-tune at
-post time. Every number below resolves via `docs/CLAIMS.md`
-(`task check-claims`); the story's hook IS the honesty, including the
-published nulls.
-
-## The one story (canonical body — adapt per channel, never inflate)
-
-**Title:** We measured our own AI-agent layer. Here are the runs where it
-changed nothing.
-
-**Body:**
-
-Most AI-agent tooling grows on headline numbers nobody can re-run. We went the
-other way: every public claim binds to a machine-checked ledger
-(`docs/CLAIMS.md` — CI fails on drift), and the benchmark page keeps the
-honest nulls.
-
-What we measured, reproducible on a fresh checkout:
-
-- The discipline lift is real but SCOPED: on a weak host the `essential` tier
-  transplants scope/downstream discipline at a measured 1.71× corpus cost
-  (down from 11.7× for the full load) — and it auto-disables on hosts where
-  we measured null. A strong host is a ceiling null; a non-Claude weak host
-  FAILED replication and we say so. (Claim: `essential-tier-cost-factor`.)
-- Swapping our advisor personas' identities changed ~nothing (Δ=0.17,
-  p=0.607) while the provider choice mattered ~15× more — so persona identity
-  is published as a placebo, not shipped as theater. (Claim:
-  `persona-identity-placebo-null`.)
-- The 30-second wedge (one read-only subagent, one command) has a scoped
-  eval behind its promise: correct verdict on both fixtures, exact
-  `file:line` on the planted hollow implementation, zero spurious findings
-  on the clean control. (Claim: `wedge-hollow-detection`.)
-
-Verify it yourself, fresh checkout:
-
-```bash
-task check-claims        # every markered public claim binds to resolvable evidence
-task check-comparison    # every comparison-table "our evidence" pointer resolves
-task build-proof-check   # the proof page is in sync with its sources
-```
-
-Try the wedge (30 seconds, installs nothing else):
-
-```bash
-mkdir -p .claude/agents
-curl -fsSL https://raw.githubusercontent.com/event4u-app/agent-config/main/docs/wedge/production-validator/production-validator.md \
-  -o .claude/agents/production-validator.md
-```
-
-Proof page: https://event4u-app.github.io/agent-config/proof/
-
-## 1. Hacker News (Show HN)
-
-- **Title:** Show HN: An AI-agent layer that publishes the runs where it
-  changed nothing
-- **Body:** canonical body above, verbatim numbers, lead with the nulls. HN
-  will test the falsifiable positioning line — that is the desired
-  conversation.
-
-## 2. Reddit (r/ClaudeAI, r/LocalLLaMA)
-
-- **Title:** We A/B-tested our own persona prompts. Identity was a placebo
-  (p=0.607). Provider choice mattered 15×.
-- **Body:** persona-null section first, then the cost sweep, then the wedge
-  one-liner. Link the proof page, not the catalog.
-
-## 3. Dev.to / blog cross-post
-
-- **Title:** Adoption without narrative debt: growing an OSS agent layer on
-  falsifiable claims only
-- **Body:** canonical body + a short section on the claims-ledger mechanism
-  (markered spans, `check-claims`, comparison-honesty table) as the
-  engineering story.
-
-## Posting checklist (maintainer, at post time)
-
-- [ ] Numbers re-checked against `docs/CLAIMS.md` at post-day HEAD.
-- [ ] No number added that lacks a ledger entry.
-- [ ] Links point at the proof page as primary CTA.
-- [ ] Session for B9 recruited via the same thread if possible
-      (`agents/recruit-sessions/_install-friction-runbook.md`).