@ikon85/agent-workflow-kit 0.33.0 → 0.34.1

package/.claude/skills/setup-workflow/board-sync.md

@@ -16,7 +16,7 @@ How the board-managed workflow skills (`to-prd`, `to-issues`, `board-to-waves`,
 | Cluster | text | optional | thematic cluster tag |
 | Spec-Path | text | optional | link from an issue to its spec doc |
 | Plan-Path | text | optional | link from an issue to its plan doc |
-| Phase | single-select | optional | groups waves into phases for the Program route (`to-waves`/`validate-graph`) — only needed if this project uses it |
+| Phase | single-select | optional | groups waves into phases for the Program route (`to-issues` Program mode / internal graph validation) — only needed if this project uses it |
 
 ## Machine profile (SSOT) — `scripts/board_config.py` reads this
 
@@ -112,7 +112,12 @@ their titles unchanged; set it once to match your board's language.
 
 ## Optional: the Program route (Phase field + saved Views)
 
-Skip this section entirely unless this project actually plans to use the Program route (`scale-check` → `to-waves` → `validate-graph`) — `fields.phase` / `labels.programType` are never auto-discovered or auto-created (a Phase field's option set is plan-specific, not something `/setup-workflow` can guess), and a profile without them keeps loading unchanged.
+Skip this section entirely unless this project actually plans to use the Program
+route (`scale-check` → `to-issues` with explicit Program identity → internal
+graph validation) — `fields.phase` / `labels.programType` are never
+auto-discovered or auto-created (a Phase field's option set is plan-specific,
+not something `/setup-workflow` can guess), and a profile without them keeps
+loading unchanged.
 
 1. **Create the Phase field:** `gh project field-create <number> --owner <owner> --name Phase --data-type SINGLE_SELECT --single-select-options "P1,P2,P3"` (name the options after this project's actual phases).
 2. **Fill `fields.phase`** in the `<!-- board-sync:profile -->` block above with the same `{id, options}` shape as `fields.status` — read both back via `gh project field-list <number> --owner <owner> --format json`.

package/.claude/skills/setup-workflow/workflow-overview.md

@@ -8,8 +8,7 @@ Use this section as the entry-point map for agent-assisted work. The individual
 - **A new build whose size is unclear** (a new app, a big cross-cutting feature, an unclear where-to-start): run `scale-check` — a short plain-language dialog that routes it to a program, a feature, a single slice, or a bug, and hands back a paste-ready start prompt.
 - **New capability or unclear change:** start with `grill-with-docs` when the domain language or decisions need sharpening, then publish the agreed shape with `to-prd`.
 - **A slice hinges on an unresolved fact or trade-off before it can be built:** clear it first — a binary yes/no question against real code/runtime/platform with `verify-spike`, a bounded "which option" choice with `decision-gate`.
-- **Existing plan, PRD, or ready issue:** use `to-issues` to split it into independently buildable tracer-bullet slices.
-- **A Program-PRD with a wave plan:** use `to-waves` to unfold it into named wave stubs + slice leaves on the board, after a chat preview gate that shows the whole plan before any write.
+- **Existing plan, PRD, or ready issue:** use `to-issues`, the single Planning facade. Explicit Feature identity selects tracer-bullet decomposition; explicit Program identity selects the internal graph path and its complete preview before any write.
 - **A backlog of open issues needs clustering into themed waves:** use `board-to-waves`.
 - **A whole wave anchor (file-disjoint slices, specs already locked) to build, verify and land end-to-end — often AFK:** use `orchestrate-wave` — it dispatches implementers per slice, integrates serially, verifies centrally, and lands. (A single slice just goes to `implement`.)
 - **Bugs or requests piling up that you didn't create:** use `triage` to move them into agent-ready issues.

package/.claude/skills/to-issues/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: to-issues
-description: Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
+description: Break a Feature or Program plan, spec, or PRD into independently-grabbable issues on the project issue tracker. This is the single public Planning facade: explicit Feature identity uses tracer-bullet decomposition; explicit Program identity delegates to the internal graph engine.
 ---
 
 # To Issues
@@ -23,6 +23,39 @@ node scripts/readiness.mjs check --skill to-issues --json
 - `managedBoard=not-applicable`: `STOP` and report that `/to-issues` is **inapplicable** for a project that deliberately has no managed board. This is a terminal project decision, not invalid evidence and not a partially active mode.
 <!-- readiness:required-preflight:end -->
 
+## Planning facade — select by explicit identity only
+
+`to-issues` is the **single public Planning facade**. After the readiness
+preflight and before any remote write, classify the source from its explicit PRD
+identity:
+
+- **Feature identity → `planning-mode=feature`.** The body carries
+  `<!-- prd: awaiting-decomposition -->` and its one `type:*` label is not the
+  configured Program type. Run the existing Feature decomposition path below:
+  one slice stays ATOMIC; two or more slices PROMOTE to a wave anchor.
+- **Program identity → `planning-mode=program`.** The body carries
+  `<!-- prd: program -->` and its one `type:*` label is the board profile's
+  `labels.programType` value. Preserve the source and delegate to the internal
+  `to-waves` graph engine. That engine still validates the graph, shows the
+  complete Program preview, waits for the single explicit approval, and performs
+  zero remote writes before approval.
+
+**Missing or contradictory identity is a hard stop before a remote write.**
+Missing means neither marker is present, including a raw issue, file bundle, or
+external PRD without an explicit identity. Contradictory means both markers are
+present, the marker disagrees with the `type:*` label, or the source carries
+multiple type labels. Report the observed markers and type labels, then ask the
+user to establish exactly one identity. A cold-entry source may receive a
+Feature or Program identity only after that explicit choice; rerun this
+classification before any normalization or publication.
+
+**Size, prose, and model judgment never select the mode.** A `## Wellenplan`
+heading, estimated file count, wording such as “large program”, or an agent's
+inference may validate or contradict an already explicit identity, but none may
+create or switch it. A Program identity without the graph grammar is a blocking
+contract error, not a fallback to Feature. A Feature identity with Program-only
+graph grammar is likewise contradictory and stops.
+
 ## Process
 
 ### 1. Gather context
@@ -110,7 +143,8 @@ Ask the user:
 
 Iterate until the user approves the breakdown.
 
-**Program batch handoff.** When `to-waves` invokes this skill for a Stufe-1p stub,
+**Program batch handoff.** When the internal Program graph engine invokes this
+skill for a Stufe-1p stub,
 the complete Program preview has already shown and approved every wave's slice
 contract. Reuse that approval when this pass preserves the approved cut: do not
 pause again merely because the internal pipeline crossed a skill boundary. Run
@@ -122,9 +156,21 @@ newly discovered gate invalidates the inherited approval and returns to §4.
 
 **Cluster/Wave discriminator (identical wording — `to-prd` §2 / `to-issues` §5):** `type:cluster` (label) always stops. A Wave number also stops, **unless** the target carries the `wave-stub` label — a Wave-stamped `wave-stub` issue is a **Stufe-1p Program-stub** (`to-waves`-published, native parent = a Program-PRD) and remains a **valid target**. A Wave-stamped issue **without** `wave-stub` (an already-assigned leaf, or a drifted item) is still a hard stop.
 
-The canonical source is a **Draft-PRD** issue from `to-prd` (carries `plan_revision`, `<!-- prd: awaiting-decomposition -->`, exactly one `type:*` + one `priority:*`, **no** `type:cluster`, and no Wave **unless** the discriminator's `wave-stub` exception applies — a Program-stub's per-wave-start content pass writes this same shape into an already Wave-stamped stub, `to-prd` §2). But `to-issues` is **provenance-independent**: it re-derives readiness from the **artefact** (§3b), never from which tool produced it.
-
-**Cold entry on an already-existing issue.** The source can also be a **raw issue**, an **external PRD embedded in an issue**, or a **mechanical file bundle** — without the `to-prd` markers. Then a **cold-entry preflight applies before anything is mutated:**
+The canonical Feature source is a **Draft-PRD** issue from `to-prd` (carries
+`plan_revision`, `<!-- prd: awaiting-decomposition -->`, exactly one `type:*` +
+one `priority:*`, **no** `type:cluster`, and no Wave **unless** the
+discriminator's `wave-stub` exception applies — a Program-stub's per-wave-start
+content pass writes this same shape into an already Wave-stamped stub, `to-prd`
+§2). The facade is provenance-independent but not identity-optional: it
+re-derives readiness from the **artefact** (§3b), never from which tool produced
+it, only after the explicit identity classification above selected the mode.
+
+**Cold entry on an already-existing issue.** The source can also be a **raw
+issue**, an **external PRD embedded in an issue**, or a **mechanical file
+bundle** — without the `to-prd` markers. That absence first triggers the
+facade's identity hard stop above. Only after the user explicitly establishes
+Feature identity may this **cold-entry preflight apply before anything is
+mutated:**
 - **Hard-stop per the discriminator above** — `type:cluster` always; Wave only when the issue is **not** a `wave-stub` (the exception is already an intended promote target — `promote` reuses its pre-stamped Wave number, §5a below).
 - **Normalize labels** (mirroring `to-prd`'s normalization): exactly **one `type:*` + one `priority:*`**; `needs-info`/`ready-for-agent` **stripped** until the final bucket assignment (§5c).
 - **Synthesize missing `to-prd` markers in place** (never assume them): `plan_revision r1` at the body head, render the Tier-2 anchor body from the template. Surface `source`/`synthesized` in the §7 audit.
@@ -389,7 +435,8 @@ Reference the blocking ticket(s), or "None - can start immediately".
 <!-- mirror-xform:start codex-escalation -->
 ```
 Welle <N> · Slice <X> (<closes #x | refs #<prd#>, Parent #<prd#>>). Read #<prd#> for decisions.
-Start skill: 🧭 Design Grill → /grill-with-docs-codex · 🔬 Verify Spike → /verify-spike · 📐 Trade-off/Research → /decision-gate · AFK → /implement · HITL → /grill-me → /implement. Recommended model: <Model [Effort]>.
+Start skill: 🧭 Design Grill → /grill-with-docs-codex · 🔬 Verify Spike → /verify-spike · 📐 Trade-off/Research → /decision-gate · AFK → /implement · HITL → /grill-me → /implement.
+Routing intent: `routing-intent: <judgment | development | mechanical>` · `reasoning-intent: <deep | balanced | light>`. The dispatching surface resolves the current executable route; never persist that provider route here.
 Worktree: your project's worktree helper, or `git worktree add`
 Scope (<N> files) — REQUIRED FIELD, blast-radius estimate at cut time; the build session checks it against its own recon findings, >2x deviation → STOP:
 - <concrete file + change>
@@ -397,6 +444,12 @@ Live-verify: <user outcome, DB/UI value with comparison>
 PR: <closes #x | Part of #<prd#> — NEVER closes on the anchor>.
 ```
 <!-- mirror-xform:end -->
+
+At execution time, consume that provider-neutral intent only through
+`src/lib/routeDispatcher.mjs` and its shared spawn guard. The active Claude or
+Codex adapter must produce Dispatch receipt v2 with requested/applied route,
+model/effort enforcement, precedence, and catalog/access/policy revisions
+before an AFK subagent starts; the durable issue never claims that proof.
 </issue-template>
 
 **Blast-radius reconciliation (build session):** the stamped `**Blast-Radius:**` is the estimate *at the cut* — the build session compares it against its own recon finding. A real finding **> 2× the estimate → STOP + report** (re-cut at the anchor), do NOT keep building silently.
@@ -430,12 +483,17 @@ It asserts, for the rooted local graph:
 
 If the source was a `wave-stub` stub, briefly confirm the label is gone (the publish mechanic strips it automatically — see §5): `gh issue view <anchor-or-leaf#> --json labels -q '.labels[].name'` shows **no** `wave-stub`. (Not part of `execute-ready-check.py` — its own quick check.)
 
-`--mode audit` is **non-blocking** — a mismatch is a **loud warning** here; the **hard block** is `.claude/hooks/drift-guard.py` at handoff-creation. Emit a visible audit two-liner:
+`--mode audit` is **non-blocking** — a mismatch is a **loud warning** here; the
+**hard block** is `.claude/hooks/drift-guard.py` at handoff-creation. Emit a
+visible audit that names the selected facade mode:
 
 ```
-to-issues: anchor=#<X> mode=<promote|atomic> slices=<n> rev <old>→<new>
+to-issues: planning-mode=feature anchor=#<X> mode=<promote|atomic> slices=<n> rev <old>→<new>
   source=<draft-prd|raw-issue|external-prd|bundle>  synthesized=<marker-list | none>
   AFK=[#a #b] HITL=[#c] · drift=<none | …>  shape=<ok | warn:…>
 ```
 
+The Program graph engine emits `planning-mode=program` in its own counted audit
+after the complete preview gate; the facade relays that audit unchanged.
+
 Do NOT close or modify any parent issue beyond the promote stamp.

package/.claude/skills/to-waves/SKILL.md

@@ -1,17 +1,25 @@
 ---
 name: to-waves
 disable-model-invocation: true
-description: "Turn a Program-PRD's wave plan into fully planned, execute-ready wave anchors and slice leaves after one complete chat preview. Validates the graph, publishes every wave, runs the to-prd/spec-self-critique/to-issues maturity contract for each wave, models unresolved work as explicit gates, and audits counted readiness. Idempotent and crash-recoverable. Use on a Program-PRD over several waves. NOT for a single-wave feature (to-issues) or backlog clustering (board-to-waves)."
+description: "Internal Program graph engine behind the public to-issues Planning facade. Turns an explicitly identified Program-PRD into execute-ready wave anchors and slice leaves after one complete chat preview. Kept as a disabled compatibility entrypoint for existing explicit invocations; normal routing always selects to-issues."
 ---
 
-# to-waves — Unfold a Program-PRD's wave plan onto the board
+# to-waves — Internal Program graph engine
+
+This skill is an **Internal Program graph engine**, selected by `to-issues` only
+when the source carries explicit, coherent Program identity. It is not a second
+public Planning route. The disabled `/to-waves` invocation remains only as a
+compatibility entrypoint for existing callers and tests; it applies this same
+contract and should direct future normal use to `/to-issues`.
 
 Takes a **Program-PRD** — the native Sub-Issue anchor over a multi-wave program
 (Programm → Phase → Welle → Slice) — and turns its `## Wellenplan` chapter into
 **fully planned wave anchors + slice leaves** on the board. Pipeline position:
-`scale-check → grill → to-prd (program mode) → to-waves`, with the per-wave
-`to-prd → spec-self-critique → to-issues` maturity pass owned inside this run.
-The **grill and to-prd sit upstream**; to-waves runs once the Program-PRD exists.
+`scale-check → grill → to-prd (program mode) → to-issues`, with this internal
+engine owning the per-wave `to-prd → spec-self-critique → to-issues` maturity
+pass inside this run.
+The **grill and to-prd sit upstream**; the facade dispatches here once the
+Program-PRD exists and its identity is coherent.
 It **never invents structure** — it only unfolds what the plan already decided.
 
 <!-- readiness:required-preflight:start -->
@@ -24,8 +32,8 @@ node scripts/readiness.mjs check --skill to-waves --json
 ```
 
 - `verdict=ready`: continue with the existing workflow without announcing the check. **Ready is silent.**
-- `verdict=blocked`: `STOP` before any mutation. Report every required capability as `<capability>=<state>` so `issueTracker`, `managedBoard`, and `specCompleteness` failures — including distinct `missing`, `pending`, and `invalid` states — stay visible, then give exactly one recovery path: **Run `/setup-workflow`, then rerun `/to-waves`.** Do not fall back to bare tracker or board commands.
-- `managedBoard=not-applicable`: `STOP` and report that `/to-waves` is **inapplicable** for a project that deliberately has no managed board. This is a terminal project decision, not invalid evidence and not a partially active mode.
+- `verdict=blocked`: `STOP` before any mutation. Report every required capability as `<capability>=<state>` so `issueTracker`, `managedBoard`, and `specCompleteness` failures — including distinct `missing`, `pending`, and `invalid` states — stay visible, then give exactly one recovery path: **Run `/setup-workflow`, then rerun `/to-issues`.** Do not fall back to bare tracker or board commands.
+- `managedBoard=not-applicable`: `STOP` and report that Program planning through `/to-issues` is **inapplicable** for a project that deliberately has no managed board. This is a terminal project decision, not invalid evidence and not a partially active mode.
 <!-- readiness:required-preflight:end -->
 
 Board constants (project node, field/status IDs) + helpers live **consumer-side**:
@@ -43,10 +51,14 @@ is the parser.
 
 ## 1. Input — a Program-PRD
 
-The target is a Program-PRD issue: it carries the `<!-- prd: program -->` marker (or
-the program-type label) and a `## Wellenplan` table. Passed in / from context. If the
-issue is a plain feature-PRD or a Welle-Anchor, stop — a feature-PRD is `to-issues`'
-target, an anchor is already a single wave.
+The target is a Program-PRD issue: it carries both the
+`<!-- prd: program -->` marker and the configured Program-type label, plus a
+`## Wellenplan` table. Passed in from the facade or explicit compatibility
+invocation. If either identity half is missing, they disagree, or Feature
+identity is also present, stop before preview or write and return to
+`to-issues`; never infer Program mode from the table, prose, size, or model
+judgment. A plain Feature-PRD remains on the facade's Feature path; a
+Wave-Anchor is already a single wave.
 
 ## 2. Parse + validate — the graph preflight
 
@@ -316,7 +328,7 @@ python3 scripts/board-sync.py program-sync <prd#>
 ## Audit block (visible output)
 
 ```
-to-waves: prd=#<n> preview=<approved|rejected>
+to-issues: planning-mode=program engine=to-waves prd=#<n> preview=<approved|rejected>
   created=<stubs X von Y, leaves X von Y>  adopted=<#a #b … | none>
   stamped=<N von M Wave/Phase>  phase=<stamped | skipped (profile lacks fields.phase)>
   matured=<X von Y>  execute-ready=<X von Y Wellen ausführungsreif>

package/README.md

@@ -24,8 +24,10 @@ changes.
 Maintainers prepare releases with `/kit-release`. It derives the shipped delta
 from a fresh manifest, recommends Semver, applies only the confirmed target,
 regenerates the checked-in manifest, and runs the full test and pack gates.
-Landing remains owned by `/wrapup`; publishing the matching npm package and
-GitHub release happens only through the configured post-merge release flow.
+Landing remains owned by `/wrapup` and only integrates the prepared version.
+After a separate publication confirmation, a matching annotated `v<version>`
+tag on canonical `main` starts the trusted publish flow. Manual dispatch
+requires an explicit existing tag and only reconciles an incomplete release.
 
 These are the skills, helper scripts, and conventions one team actually uses to
 take work from a vague idea to a merged, verified PR with [Claude Code] and
@@ -85,9 +87,11 @@ into the *same shaped artefact*: a Draft-PRD that, once sliced, becomes either o
 atomic issue or a wave anchor with child slices. What counts downstream is the
 **shape of the artefact, never where it came from** — so each step can be entered
 cold and *extracts or synthesizes* what's missing instead of assuming an earlier
-step ran. The routing key is just *"is there an issue yet?"*: a loose artefact
+step ran. The entry key is just *"is there an issue yet?"*: a loose artefact
 (no issue) enters at `to-prd`; an existing issue or file-bundle enters at
-`to-issues` directly.
+`to-issues` directly. Inside that facade, the explicit PRD identity — Feature or
+Program — is the only mode selector; a cold source must establish one before a
+remote write.
 
 - **Grill as deep as the work deserves — it's optional.** `grill-me` /
   `grill-with-docs` interrogate the intent (and your domain docs) until the real
@@ -98,13 +102,15 @@ step ran. The routing key is just *"is there an issue yet?"*: a loose artefact
   Draft-PRD issue, *extracting* the template sections from what already exists. A
   required section it genuinely can't derive becomes an honest **Open points**
   block, never a silent "looks complete" placeholder.
-- **`to-issues`** slices the PRD into tracer-bullet verticals and picks the shape:
-  **1 slice → one atomic issue** the PR closes; **≥2 slices → a wave anchor** with
-  linked child slices. It re-derives readiness from the artefact itself, so it works
-  just as well started straight on a raw issue or file-bundle — any unresolved
-  *Open points* travel through as a build-blocking gate (the profile's
-  configurable `vorBau` heading, see [Configuration](#configuration)) that never
-  vanishes silently.
+- **`to-issues`** is the single public Planning facade. Explicit Feature
+  identity selects tracer-bullet decomposition and picks the shape: **1 slice →
+  one atomic issue** the PR closes; **≥2 slices → a wave anchor** with linked
+  child slices. Explicit Program identity selects the existing internal graph
+  engine and preserves its complete chat preview before any board write.
+  Missing or contradictory identity stops before a write; size, prose, and model
+  judgment never select the mode. Any unresolved *Open points* travel through as
+  a build-blocking gate (the profile's configurable `vorBau` heading, see
+  [Configuration](#configuration)) that never vanishes silently.
 - **`board-to-waves`** clusters an existing backlog into themed campaigns when you
   need to *find* the next wave rather than start fresh.
 - **`triage`** keeps the inbox sane with a consistent label vocabulary.
@@ -211,7 +217,8 @@ hands a well-defined object to the level below:
 
 Two roads lead to the same wave. **Top-down:** `scale-check` names the size in
 a few plain questions; a big undertaking gets grilled once into a Program PRD
-with a wave plan, and `to-waves` unfolds it into named waves after you approve
+with a wave plan, and `to-issues` selects its internal Program graph path from
+that explicit identity. It unfolds the plan into named waves after you approve
 a full preview in chat — zero board writes until you say yes. **Bottom-up:**
 `board-to-waves` clusters loose issues into a wave candidate, which earns a
 real number only when you promote it. Either road lands in the *identical*
@@ -222,7 +229,7 @@ When the slices are file-disjoint and their specs are locked, **`orchestrate-wav
 lands the whole anchor end-to-end — often AFK: it dispatches an implementer per
 slice into its own worktree, integrates serially, verifies centrally, and lands
 the wave. It's the execute-and-land node of the wave ladder (`scale-check` →
-`to-waves` / `board-to-waves` → `orchestrate-wave`); a single slice still just
+`to-issues` / `board-to-waves` → `orchestrate-wave`); a single slice still just
 goes to `implement`.
 
 ![The Program-to-Phase-to-Wave-to-Slice altitude ladder, and the two routes — a planned top-down Program route and a grown bottom-up board route — that both fund the same Wave-and-Slices build spine.](docs/methodology.svg)
@@ -380,6 +387,75 @@ the old way. Decision record:
 
 ## Release notes
 
+### 0.34.1
+
+- changed: `.agents/skills/kit-release/SKILL.md`
+- changed: `.claude/skills/kit-release/SKILL.md`
+- changed: `scripts/release-state.mjs`
+
+### 0.34.0
+
+- added: `src/commands/routing-policy-update.mjs`
+- added: `src/lib/agentSurfaceRegistry.mjs`
+- added: `src/lib/dispatchReceipt.mjs`
+- added: `src/lib/frontendWorkloads.mjs`
+- added: `src/lib/routeDispatcher.mjs`
+- added: `src/lib/routingAccessGraph.mjs`
+- added: `src/lib/routingAdapters/claude.mjs`
+- added: `src/lib/routingAdapters/codex.mjs`
+- added: `src/lib/routingCatalog.mjs`
+- added: `src/lib/routingEvidenceCache.mjs`
+- added: `src/lib/routingIntent.mjs`
+- added: `src/lib/routingPolicy.mjs`
+- added: `src/lib/routingProfile.mjs`
+- added: `src/lib/routingResolver.mjs`
+- added: `src/lib/routingSources/artificialAnalysis.mjs`
+- added: `src/lib/routingSources/benchlm.mjs`
+- added: `src/lib/routingSources/codeArena.mjs`
+- added: `src/lib/routingSources/deepswe.mjs`
+- added: `src/lib/routingSources/openhands.mjs`
+- added: `src/lib/routingSources/openhandsFrontend.mjs`
+- changed: `.agents/skills/ask-matt/SKILL.md`
+- changed: `.agents/skills/audit-skills/SKILL.md`
+- changed: `.agents/skills/board-to-waves/SKILL.md`
+- changed: `.agents/skills/code-review/SKILL.md`
+- changed: `.agents/skills/codebase-design/DESIGN-IT-TWICE.md`
+- changed: `.agents/skills/codex-adapter-sync/SKILL.md`
+- changed: `.agents/skills/improve-codebase-architecture/INTERFACE-DESIGN.md`
+- changed: `.agents/skills/improve-codebase-architecture/SKILL.md`
+- changed: `.agents/skills/kit-update/SKILL.md`
+- changed: `.agents/skills/orchestrate-wave/SKILL.md`
+- changed: `.agents/skills/orchestrate-wave/references/dispatch-subagents.md`
+- changed: `.agents/skills/orchestrate-wave/references/dispatch-workflow.md`
+- changed: `.agents/skills/research/SKILL.md`
+- changed: `.agents/skills/scale-check/SKILL.md`
+- changed: `.agents/skills/setup-workflow/SKILL.md`
+- changed: `.agents/skills/setup-workflow/board-sync.md`
+- changed: `.agents/skills/setup-workflow/workflow-overview.md`
+- changed: `.agents/skills/to-issues/SKILL.md`
+- changed: `.agents/skills/to-waves/SKILL.md`
+- changed: `.claude/skills/ask-matt/SKILL.md`
+- changed: `.claude/skills/audit-skills/SKILL.md`
+- changed: `.claude/skills/board-to-waves/SKILL.md`
+- changed: `.claude/skills/code-review/SKILL.md`
+- changed: `.claude/skills/codebase-design/DESIGN-IT-TWICE.md`
+- changed: `.claude/skills/improve-codebase-architecture/INTERFACE-DESIGN.md`
+- changed: `.claude/skills/improve-codebase-architecture/SKILL.md`
+- changed: `.claude/skills/kit-update/SKILL.md`
+- changed: `.claude/skills/orchestrate-wave/SKILL.md`
+- changed: `.claude/skills/orchestrate-wave/references/dispatch-subagents.md`
+- changed: `.claude/skills/orchestrate-wave/references/dispatch-workflow.md`
+- changed: `.claude/skills/research/SKILL.md`
+- changed: `.claude/skills/scale-check/SKILL.md`
+- changed: `.claude/skills/setup-workflow/SKILL.md`
+- changed: `.claude/skills/setup-workflow/board-sync.md`
+- changed: `.claude/skills/setup-workflow/workflow-overview.md`
+- changed: `.claude/skills/to-issues/SKILL.md`
+- changed: `.claude/skills/to-waves/SKILL.md`
+- changed: `docs/agents/wave-anchor-template.md`
+- changed: `scripts/codex-exec.sh`
+- changed: `src/lib/capabilityMatrix.mjs`
+
 ### 0.33.0
 
 - added: `.agents/skills/orchestrate-wave/references/dispatch-subagents.md`