@event4u/agent-config 6.1.0 → 7.0.0

package/docs/migration/divergences/src-scripts-spotcheck_thin_root.md

@@ -0,0 +1,60 @@
+# Divergence: spotcheck_thin_root
+
+## Script
+
+- Python: `src/scripts/spotcheck_thin_root.py`
+- TypeScript: `src/scripts/spotcheck_thin_root.ts`
+
+## Symptom
+
+The entire `main()` is a **live AI-council call** (Anthropic `claude-sonnet-4-5`
++ OpenAI `gpt-4o`) that requires API keys + network access and produces a
+**non-deterministic** report — per-call `latency_ms` and `tokens_in/out` vary
+every run, and the model prose is not reproducible. There is therefore no
+golden-parity path: python3 vs tsx output cannot be byte-compared, and the
+script cannot run inside CI.
+
+- Affected channel(s): written files (`thin-root-platform-spotcheck.md` /
+  `.json`) + stderr (`Running …`, `✅  Wrote …`).
+
+## Root cause
+
+The Python original imports three still-Python `ai_council` modules with no TS
+twin in this wave:
+
+- `ai_council.clients` — `AnthropicClient`, `OpenAIClient`,
+  `load_anthropic_key`, `load_openai_key` (~1,385 lines, network clients).
+- `ai_council.orchestrator` — `CostBudget`, `CouncilQuestion`, `consult`
+  (~1,206 lines).
+- `ai_council.pricing` — `load_prices` (ported as `ai_council/pricing.ts`).
+
+A `.ts` cannot import a `.py`, and the "PORT + import, never inline the
+un-ported logic" rule forbids re-implementing those ~2,800 lines of
+network-calling code inside this twin. Per the established precedent for
+un-ported Python deps (`check_discovery_determinism.ts` runs its un-ported
+scanner via `python3`; `smoke_quickstart.ts` Step 3 imports `decision_engine`
+via a `python3` shim), the TS twin delegates the live `consult(...)` call to a
+`python3` shim that imports the real Python modules. The deterministic parts —
+artefact assembly, the `json.dumps(indent=2)` writer, the Markdown report
+layout, the stderr lines — are ported faithfully in TS.
+
+## Verdict
+
+`intentional-improvement` — both behaviors are defensible; the TS twin
+preserves the byte-shape of the written report and the stderr surface while
+running the unportable, non-deterministic, network-bound council step through
+the still-Python modules. Porting the two large network clients is out of this
+wave's scope and tracked separately.
+
+## Evidence
+
+`tests/scripts/spotcheck_thin_root.test.ts` asserts the module imports without
+a top-level throw and exposes the `main` entry point (the deterministic CLI
+surface). The live council path (network + keys) is excluded from CI by
+construction — there is no fixture that could pin a non-deterministic
+LLM-latency report.
+
+## Approval
+
+- Reviewer: <pending — porting subagent, Wave 8h>
+- Date: 2026-06-13

package/docs/migration/divergences/src-scripts-validate_agent_settings.md

@@ -0,0 +1,58 @@
+# Divergence: validate_agent_settings
+
+## Script
+
+- Python: `src/scripts/validate_agent_settings.py`
+- TypeScript: `src/scripts/validate_agent_settings.ts`
+
+## Symptom
+
+Only the **error-message prose** of a schema violation can differ. The exit
+code, the GitHub `::error file=…::<loc>:` location prefix, the violation
+count, the summary line, and the clean-pass line are byte-identical.
+
+- **Python output (violation):** `::error file=…::rule_loading_tier: 'lean' is not one of ['minimal', 'balanced', 'full', 'custom']`
+  — the trailing clause is produced verbatim by the `jsonschema` library and
+  is Python-version-dependent.
+- **TS output (violation):** same `::error file=…::rule_loading_tier:` prefix
+  and field path; the enum/type clause is reproduced by a minimal Draft-07
+  validator (`_iter_errors`) and may differ in exact wording from a given
+  `jsonschema` release.
+- Affected channel(s): stdout (only the prose tail of a violation line).
+
+## Root cause
+
+The Python script delegates message text to `jsonschema.Draft7Validator`,
+whose `ValidationError.message` wording is not a stable contract (it has
+changed across `jsonschema` releases). The package ships no `ajv`/jsonschema
+dependency for the TS side and `package.json` is frozen for this wave, so the
+twin implements the exact constraint subset the shared schema uses (`type`
+object/string, string `enum`, `properties`, permissive `additionalProperties:
+true`) and approximates the message text. Per ADR-200 §4 the parity contract
+for schema-validation findings is **exit code + flagged field-paths**, not
+byte-exact jsonschema prose.
+
+## Verdict
+
+`formatting-only` — the constraint set, the violating field path, the error
+location prefix, the violation count, and both summary lines match exactly;
+only the human-readable enum/type clause may differ, with no semantic or
+consumer impact (CI greps the `::error file=…::<loc>:` location, not the tail).
+
+## Evidence
+
+- `tests/scripts/validate_agent_settings.test.ts` asserts: every valid
+  `rule_loading_tier` accepted; an out-of-enum value rejected **at the
+  `['rule_loading_tier']` path** with a message naming the allowed values;
+  the legacy `cost_profile` key tolerated (shipped reality); nested enums
+  (`memory.cadence`, `model.auto_switch`, `worktrees.mode`) enforced at the
+  correct paths.
+- Golden parity: the same test runs `python3 validate_agent_settings.py` vs
+  `tsx validate_agent_settings.ts` on the real repo and asserts stdout, stderr,
+  and exit code are byte-identical (the clean repo never triggers a violation
+  line, so the only golden-parity surface is the OK summary — byte-identical).
+
+## Approval
+
+- Reviewer: <pending — porting subagent, ADR-200 Phase 4 / Wave 4c>
+- Date: 2026-06-11

package/docs/migration/node-floor.md

@@ -0,0 +1,86 @@
+# Node Floor Audit
+
+> Phase 1 Step 12 of `agents/roadmaps/road-to-typescript-only-scripts.md`.
+> Decision: which Node.js floor the TS-only script suite supports, where it is
+> enforced, and what CI tests.
+
+## Facts (as audited 2026-06-11, branch feat/py2ts-phase1-infra)
+
+| Surface | Value | Source |
+|---|---|---|
+| `engines.node` | `>=20.11.0` | `package.json:53-55` |
+| tsconfig target | `ES2022` (`module: ESNext`, `moduleResolution: Bundler`) | `tsconfig.json:3-5` |
+| tsconfig lib | `ES2022` (+ `DOM` in `tsconfig.ui.json:4`, `tsconfig.test.json:6`) | tsconfig files |
+| CI — tests.yml | Node `20` | `.github/workflows/tests.yml:241` |
+| CI — release-drift.yml | Node `20` | `.github/workflows/release-drift.yml:44` |
+| CI — publish-npm.yml | Node `20` | `.github/workflows/publish-npm.yml:48` |
+| CI — smoke-public-install.yml | matrix `node: ['20', '22']` × 3 OS | `smoke-public-install.yml:78-80` |
+| CI — deploy-mcp-worker.yml | Node `22` | `deploy-mcp-worker.yml:68` |
+| `engine-strict` | not set (no `.npmrc`) — `engines` is advisory only | repo root |
+| Installer Node check | none today (Python installer never inspects `process.version`) | grep of `src/scripts/install*`, `setup.sh` |
+
+Feature scan of `src/` TypeScript (sampled, not exhaustive):
+
+- `node:` protocol imports — 34 files (Node ≥ 16; trivially within floor).
+- Global `fetch` in Node-side code — `src/server/token.ts` (stable without flag
+  since Node 18, marked stable in 21; fine on ≥ 20.11).
+- No hits for `structuredClone`, top-of-module top-level `await`,
+  `Array.prototype.at(-…)`, `Object.hasOwn`, `findLast` in `src/` TS.
+- Browser-only `fetch` usage (`src/ui/api.ts`) is covered by the `DOM` lib, not
+  the Node floor.
+
+Conclusion of the scan: nothing in the current TS code requires more than
+Node 18; the ES2022 compile target is the binding constraint and is fully
+served by every Node ≥ 18.12. The floor question is therefore a **support
+lifecycle** decision, not a syntax one.
+
+## Recommendation
+
+**Raise the floor to Node `>=22.0.0` as part of the TS-only migration; test
+22 (minimum) and 24 (current LTS) in CI.** Keep `>=20.11.0` only until the
+first major/breaking release of the migration lands, then flip — the bump is a
+semver-major signal per the package's versioning policy.
+
+## Rationale
+
+- **Node 20 is end-of-life.** Its maintenance window ended April 2026. A
+  migration that will ship through 2026/27 should not anchor its floor on a
+  line that no longer receives security fixes; keeping it implies supporting
+  consumers on an unpatched runtime.
+- **Node 22 (maintenance LTS) and 24 (active LTS) are the 2026 reality.** CI
+  already runs 22 in two workflows; the smoke matrix already proves installs
+  on 22. Raising the floor to 22 costs no code changes (the feature scan shows
+  no >ES2022 usage to add or remove) and removes a dead line from the matrix.
+- **Consumer compatibility risk is low and visible.** The package is a dev-time
+  tool invoked via `npx`/global install, not a production runtime dependency.
+  Consumers still on Node 20 get a clear, immediate failure at install time
+  (see Enforcement) rather than a latent one.
+- **Why not 24 as the floor:** 24 only entered LTS in late 2025; many CI images
+  and corporate baselines still pin 22. Floor = oldest non-EOL LTS (22),
+  matrix-test up to current LTS (24).
+
+## Enforcement points
+
+1. **`package.json` `engines`** — flip to `">=22.0.0"` at the breaking release.
+   Advisory only without `engine-strict`; npm prints a warning, pnpm/yarn fail
+   harder. Do **not** set `engine-strict` repo-wide (it would also bind
+   maintainers); rely on point 2 for the hard gate.
+2. **TS installer runtime check (the hard gate).** Phase 3 Step 2 already
+   requires "Node-version check with a clear error": the TS installer must
+   compare `process.versions.node` against the floor on startup and fail with
+   an actionable message before writing anything. This is the enforcement the
+   Python installer never had — it must land with the TS installer.
+3. **CI matrix** — pin the floor and the current LTS:
+   - `smoke-public-install.yml`: `node: ['22', '24']` (replacing `['20', '22']`).
+   - `tests.yml` / `release-drift.yml` / `publish-npm.yml`: bump single-version
+     jobs `20` → `22`; add a `24` leg to `tests.yml` if budget allows.
+4. **Docs** — README Quickstart and `docs/getting-started.md` state the floor
+   explicitly ("requires Node 22+"); CHANGELOG `### Breaking` entry +
+   `BREAKING_CHANGES.md` index the bump per the versioning policy.
+
+## Decision status
+
+Recommended here; the `engines` flip itself is release-gated (semver-major)
+and should ride the first breaking release of the TS migration, not this
+infra PR. Until then `>=20.11.0` stays in `package.json`, and CI keeps one
+Node 20 leg solely to honor the published floor.

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

@@ -0,0 +1,163 @@
+# YAML Round-Trip Spike — Verdict
+
+> Phase 1 Step 7 of `agents/roadmaps/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/personas.md

@@ -24,7 +24,7 @@ Removed personas are deleted in-commit (no soak window) — see
 
 Note: `product-owner` was reclassified to **specialist** at v2.0 — see below.
 
-## Catalog — Specialists (opt-in, 18 active)
+## Catalog — Specialists (opt-in, 20 active)
 
 | ID | Role | Wing | Owner | Lens summary |
 |---|---|---|---|---|
@@ -39,6 +39,8 @@ Note: `product-owner` was reclassified to **specialist** at v2.0 — see below.
 | `discovery-lead` | Discovery Lead | — | package | Switch events, falsifiable hypotheses, theme ranking. |
 | `hollywood-director` | Hollywood Director (`ai-video`) | — | package | Live-action lens, lighting, blocking, negative constraints. |
 | `ai-video-technical-director` | AI Video Technical Director (`ai-video`) | — | package | Provider tuning — Veo / Kling / Sora / Higgsfield / OpenAI grammar. |
+| `brand-strategist` | Brand Strategist (`design`) | — | package | Positioning, archetype, voice, messaging; challenges weak briefs. |
+| `design-director` | Design Director (`design`) | — | package | Art-direction and brand-aligned visual judgment; composition, hierarchy, vector-vs-raster. |
 | `cmo` | CMO | 3 | package | Positioning anchored, messaging stacked, launches sequenced. |
 | `growth-pm` | Growth PM | 3 | package | Leaky-bucket vs growth-loop classified, activation correlated. |
 | `customer-success-lead` | Customer Success Lead | 3 | package | TTFV falsifiable, churn cause split, expansion pulled, NRR. |
@@ -53,6 +55,7 @@ Note: `product-owner` was reclassified to **specialist** at v2.0 — see below.
 | Domain | Active specialists | Within cap |
 |---|---|---|
 | `ai-video` | `hollywood-director`, `ai-video-technical-director` | ✅ 2/2 |
+| `design` | `brand-strategist`, `design-director` | ✅ 2/2 |
 | GTM (Wing 3) | `cmo`, `growth-pm`, `customer-success-lead`, `revops` | ✅ (wing, not domain) |
 | Ops / Money (Wing 4) | `engineering-manager`, `people-strategist`, `finance-partner`, `strategist` | ✅ (wing, not domain) |
 | Backend | `backend-architect`, `eloquent-tamer` | ✅ 2/2 |
@@ -131,6 +134,8 @@ slot. Current cite map:
 | `eloquent-tamer` | `eloquent`, `database` |
 | `security-engineer` | `judge-security-auditor`, `threat-modeling`, `authz-review` |
 | `frontend-engineer` | `existing-ui-audit`, `fe-design` |
+| `brand-strategist` | `brand`, `brand-strategy` |
+| `design-director` | `brand-identity`, `logo-generation`, `brand-asset-generation` |
 
 Add a citation by appending `personas: [<id>]` to the skill's
 frontmatter — never overwrite an existing list, append.

package/docs/role-experiences.md

@@ -0,0 +1,19 @@
+# Role experiences — taglines at a glance
+
+> **Generated** by `scripts/generate_role_experiences_catalog.py` from
+> `agents/roles/<role>/index.md` — do NOT hand-edit. Taglines are the
+> existing role-level strings (validated by `lint_role_experiences.py`,
+> rendered in the GUI workspace); this page surfaces them in a catalog.
+
+Each row links to the full role experience (persona · three first tasks ·
+packs). The catalog never duplicates the body — see
+[`docs/contracts/role-experience.md`](contracts/role-experience.md).
+
+| Role | Tagline | Status |
+|---|---|---|
+| [Consultant / advisor](../agents/roles/consultant/index.md) | Client briefs, investor memos, and deck outlines — refined before the meeting, not rewritten after. | `beta-internal` |
+| [Content creator](../agents/roles/content-creator/index.md) | From a one-line idea to a stitched short — voice-locked, character-locked, provider-agnostic. | `beta-internal` |
+| [Galabau owner](../agents/roles/galabau/index.md) | Drafting customer offers and project briefs without a project manager between you and the document. | `beta-internal` |
+| [Team leader](../agents/roles/leadership/index.md) | Summarise weekly status, write the risk memo, structure the decision before the meeting. | `beta-internal` |
+| [Sales rep](../agents/roles/sales/index.md) | Answer customer questions, draft offers, and prep discovery calls — voice-locked, structured, fast. | `beta-internal` |
+| [Support agent](../agents/roles/support/index.md) | Summarise the ticket, draft the reply, flag the escalation — without rewriting the customer's words. | `beta-internal` |

package/docs/setup/per-ide/windsurf.md

@@ -99,7 +99,7 @@ should match `ls .windsurf/workflows/`.
 | Rules not picked up | Windsurf < 1.0 — upgrade or rely on `.windsurfrules`. |
 | Workflow not in Cascade panel | Reload window after `task generate-tools`. |
 | Global workflows missing | Check `~/.codeium/windsurf/global_workflows/` exists. |
-| Frontmatter parse error | Re-run `python3 scripts/condense.py --generate-tools`. |
+| Frontmatter parse error | Re-run `./scripts-run src/scripts/condense --generate-tools`. |
 
 ## Cross-references
 

package/docs/skills-catalog.md

@@ -1,6 +1,6 @@
 # Skills Catalog
 
-All **230 skills** available in this package, in alphabetical order.
+All **251 skills** available in this package, in alphabetical order.
 Click a skill name to open its SKILL.md and read the full guidance.
 
 > **Regenerate:** `python3 scripts/generate_catalog.py`
@@ -27,7 +27,14 @@ Click a skill name to open its SKILL.md and read the full guidance.
 | [`authz-review`](../dist/agent-src/skills/authz-review/SKILL.md) | Use when reviewing authorization end-to-end — route → gate → policy → query scope → response filter — before changes to permissions, tenants, ownership, or admin flows. |
 | [`aws-infrastructure`](../dist/agent-src/skills/aws-infrastructure/SKILL.md) | Use when working with AWS resources — ECS Fargate, ECR, EFS, Secrets Manager, gomplate templates, multi-env deployments — even when the user says 'deploy to staging' without naming AWS. |
 | [`blade-ui`](../dist/agent-src/skills/blade-ui/SKILL.md) | Use when the project's frontend stack is Blade — dispatched by `directives/ui/{apply,review,polish}.py`. Covers views, components, partials, layouts, and view logic. |
+| [`blameless-post-mortem`](../dist/agent-src/skills/blameless-post-mortem/SKILL.md) | Use after an incident or outage is resolved — blame-free facilitation, root cause, corrective actions, memory write-back — even for a near-miss. Consumes the incident-commander skeleton. |
 | [`blast-radius-analyzer`](../dist/agent-src/skills/blast-radius-analyzer/SKILL.md) | Use BEFORE editing shared code — enumerates every call site, event consumer, queue worker, API client, migration, and test that a planned change will touch, with a file:line citation per dependency. |
+| [`brand`](../dist/agent-src/skills/brand/SKILL.md) | Grounded brand decisions from a curated corpus — archetype, voice, naming, colour psychology, logo-style fit, messaging frameworks, archetype→type mapping. Use to ground brand strategy and identity. |
+| [`brand-asset-generation`](../dist/agent-src/skills/brand-asset-generation/SKILL.md) | Generate brand assets — banners, social cards, CIP elements — with brand-token injection + provider routing. Use when generating a banner / social image / branded asset. |
+| [`brand-audit`](../dist/agent-src/skills/brand-audit/SKILL.md) | Audit how a brand is currently expressed across touchpoints and flag drift from its defined tokens, voice, and strategy. Use to inventory and critique an existing brand before changing it. |
+| [`brand-identity`](../dist/agent-src/skills/brand-identity/SKILL.md) | Define a brand identity constraint set from a confirmed strategy — colour story, type story, logo direction, imagery direction. Defines the tokens that token emission and asset generation consume. |
+| [`brand-strategy`](../dist/agent-src/skills/brand-strategy/SKILL.md) | Ground a brand strategy from the corpus — archetype, opposable positioning, voice and tone, messaging framework. Use to decide who a brand is for, what it stands for, and how it sounds. |
+| [`brand-to-tokens`](../dist/agent-src/skills/brand-to-tokens/SKILL.md) | Derive a DTCG .tokens.json source of truth from confirmed brand decisions, emit CSS vars + Tailwind via design-tokens, and export locked brand deck templates. Use to turn a brand identity into tokens. |
 | [`bug-analyzer`](../dist/agent-src/skills/bug-analyzer/SKILL.md) | Use when the user shares a Sentry error, Jira bug ticket, or error description and wants root cause analysis. Also for proactive bug hunting and code audits for hidden bugs. |
 | [`build-buy-partner`](../dist/agent-src/skills/build-buy-partner/SKILL.md) | Use when deciding insource vs outsource vs acquire — integration-cost analysis, dependency-risk, optionality preservation. Triggers on 'should we build', 'buy vs partner'. |
 | [`canvas-design`](../dist/agent-src/skills/canvas-design/SKILL.md) | Use when creating static visual art — posters, marketing visuals, brand assets, PDF/PNG design pieces — even if the user just says 'design a poster' or 'mach uns ein Visual'. |
@@ -59,7 +66,8 @@ Click a skill name to open its SKILL.md and read the full guidance.
 | [`database`](../dist/agent-src/skills/database/SKILL.md) | Use when working with database architecture, MariaDB/MySQL tuning, indexing strategies, slow queries, or multi-connection patterns — even when the user just says 'this query is slow'. |
 | [`dcf-modeling`](../dist/agent-src/skills/dcf-modeling/SKILL.md) | Wing-4 valuation cognition for a CFO / finance-partner. Use when a deal, internal investment, or board ask names DCF, intrinsic value, WACC, terminal value, or 'what's it worth on a 5-year hold'. |
 | [`deal-qualification-meddic`](../dist/agent-src/skills/deal-qualification-meddic/SKILL.md) | Use when qualifying or disqualifying a single deal — MEDDIC slots with evidence, inversion test, disqualification heuristic. Triggers on 'is this deal real', 'should we walk away'. |
-| [`decision-record`](../dist/agent-src/skills/decision-record/SKILL.md) | Use when locking a trade-off, structuring an ADR draft, or wiring supersession chains — frames options · trade-offs · consequences before the file is written by `adr-create`. |
+| [`decision-record`](../dist/agent-src/skills/decision-record/SKILL.md) | Use when choosing between alternatives with trade-offs — X-or-Y decisions (pattern vs pattern, strategy vs strategy) — frames options · trade-offs · consequences; ADR draft via `adr-create`. |
+| [`decision-review`](../dist/agent-src/skills/decision-review/SKILL.md) | Use to audit a past architectural decision — did the chosen option hold up, what assumptions drifted, should the ADR be superseded? Backward review only; does not lock new choices. |
 | [`deep-reading-analyst`](../dist/agent-src/skills/deep-reading-analyst/SKILL.md) | Deep analysis of articles/long-form via thinking frameworks (SCQA, mental models, inversion) — 'analyze article', 'deep dive', 'extract insights', URL/text wanting depth not summary. |
 | [`defense-in-depth`](../dist/agent-src/skills/defense-in-depth/SKILL.md) | Use when validation needs entry, business-logic, environment, and instrumentation guards so a bad value cannot reach the failure point — turns a local bug fix into a structural one. |
 | [`dependency-upgrade`](../dist/agent-src/skills/dependency-upgrade/SKILL.md) | Use when upgrading dependencies — 'update framework X', 'bump runtime version', or 'upgrade packages'. Covers changelog review, breaking-change detection, and verification. Stack-agnostic. |
@@ -74,6 +82,7 @@ Click a skill name to open its SKILL.md and read the full guidance.
 | [`docker`](../dist/agent-src/skills/docker/SKILL.md) | Use when working with Docker — Dockerfile edits, docker-compose services, containers, or the dual-container (fast + Xdebug) setup — even when the user just says 'my container won't start'. |
 | [`editorial-calendar`](../dist/agent-src/skills/editorial-calendar/SKILL.md) | Use when shaping cadence — evergreen / campaign / reactive split, beat-mapping across channel stages, content-debt management. Triggers on 'plan our content cadence', 'what should we publish'. |
 | [`eloquent`](../dist/agent-src/skills/eloquent/SKILL.md) | Use when writing Eloquent models, relationships, scopes, or queries via Model:: — 'fetch users with their orders'. NOT for PHPStan output, non-Eloquent services, or raw SQL questions. |
+| [`emit-tickets`](../dist/agent-src/skills/emit-tickets/SKILL.md) | Use when materialising a roadmap into a ticket bundle — 'turn this roadmap into tickets', 'materialise tickets', 'mach Tickets aus der Roadmap', 'emit tickets for this plan'. |
 | [`error-handling-patterns`](../dist/agent-src/skills/error-handling-patterns/SKILL.md) | Use when picking a failure-reporting strategy — exceptions vs Result types, recoverable vs not, retry / circuit-breaker / graceful degradation — decision framework only, catalogues externalized. |
 | [`"estimate-ticket"`](../dist/agent-src/skills/"estimate-ticket"/SKILL.md) | Estimate a Jira/Linear ticket — 'estimate PROJ-123', 'wie groß ist das?', 'should we split this?' — size + risk + split + uncertainty, sibling of /refine-ticket, close-prompt. |
 | [`existing-ui-audit`](../dist/agent-src/skills/existing-ui-audit/SKILL.md) | Use BEFORE writing or editing any non-trivial UI — inventories components, design tokens, shadcn primitives, and reusable patterns into state.ui_audit. Hard gate for the ui directive set. |
@@ -94,8 +103,12 @@ Click a skill name to open its SKILL.md and read the full guidance.
 | [`gtm-launch`](../dist/agent-src/skills/gtm-launch/SKILL.md) | Use when sequencing a launch — alpha / beta / GA waves, audience-by-wave logic, narrative beats per wave, engineering-readiness gates. Triggers on 'plan the launch', 'sequence GA'. |
 | [`guideline-writing`](../dist/agent-src/skills/guideline-writing/SKILL.md) | Use when creating or editing a guideline in docs/guidelines/ — reference material cited by skills, no auto-triggers — even when the user just says 'write up our naming conventions'. |
 | [`hiring-loop-design`](../dist/agent-src/skills/hiring-loop-design/SKILL.md) | Use when shaping an engineering hiring loop — stages, take-home vs live, calibration, bar-raiser, signal-vs-noise audit. Triggers on 'design our interview loop', 'audit our hiring bar'. |
+| [`iconography`](../dist/agent-src/skills/iconography/SKILL.md) | Resolve an icon request to a concrete Iconify name and emit the embedding for the project's stack. Use when adding icons, picking an icon set, or wiring Lucide/Heroicons/Phosphor/Tabler. |
 | [`image-analyser`](../dist/agent-src/skills/image-analyser/SKILL.md) | Use to analyse a character image down to the smallest mole and diff against a canon — per-feature spec, OCR-reads tattoo text, flags drift. Triggers 'analyse this image', 'match the canon'. |
 | [`image-creator`](../dist/agent-src/skills/image-creator/SKILL.md) | Use to generate a character image to spec — max-fidelity reproducible prompt from a Canon Spec, anchors-first, provider/governance-gated. Triggers 'generate this character', 'render to spec'. |
+| [`image-editing`](../dist/agent-src/skills/image-editing/SKILL.md) | Edit an existing image — inpaint, background swap, variation — via providers that support it. Use when editing/modifying/inpainting an image or making variations. |
+| [`image-generation`](../dist/agent-src/skills/image-generation/SKILL.md) | Generate an image from a brief — provider-agnostic blueprint then provider-specific translation, with ref-image/seed reuse for consistency. Use when generating/creating an image. |
+| [`image-provider-routing`](../dist/agent-src/skills/image-provider-routing/SKILL.md) | Select the right image-generation provider from job shape — text-in-image to Ideogram, photoreal to Flux, vector/logo to Recraft, general to Gemini/GPT. |
 | [`incident-commander`](../dist/agent-src/skills/incident-commander/SKILL.md) | Use during or right after an incident — frames severity, sets comms cadence, drafts the post-mortem skeleton — even when the user just says 'production is down' or 'wir haben einen Vorfall'. |
 | [`jira-integration`](../dist/agent-src/skills/jira-integration/SKILL.md) | Use when the user says \"check Jira\", \"create ticket\", \"update issue\", or needs JQL queries, ticket transitions, or branch-to-ticket linking. |
 | [`jobs-events`](../dist/agent-src/skills/jobs-events/SKILL.md) | Use when creating Laravel jobs, queued workflows, events, or listeners. Covers clear responsibilities, safe serialization, and retry/failure handling. |
@@ -123,6 +136,7 @@ Click a skill name to open its SKILL.md and read the full guidance.
 | [`livewire`](../dist/agent-src/skills/livewire/SKILL.md) | Use when the project's frontend stack is Livewire — dispatched by `directives/ui/{apply,review,polish}.py`. Covers reactive state, events, lifecycle hooks, and component/view separation. |
 | [`livewire-architect`](../dist/agent-src/skills/livewire-architect/SKILL.md) | Use when shaping a Livewire component before code — full-page vs partial, parent/child split, event flow, state-vs-props boundary, hydration cost — even on 'add this Livewire component'. |
 | [`logging-monitoring`](../dist/agent-src/skills/logging-monitoring/SKILL.md) | Use when working with logging or monitoring — Sentry error tracking, Grafana/Loki log aggregation, structured logging channels, or monitoring helpers. |
+| [`logo-generation`](../dist/agent-src/skills/logo-generation/SKILL.md) | Generate a logo or brand mark — structured prompt + provider routing, with a true-vector path via a vector-native provider or LLM-authored SVG for simple marks. Use for logo or brand mark generation. |
 | [`market-entry-analysis`](../dist/agent-src/skills/market-entry-analysis/SKILL.md) | Use when sequencing market entry — geo / segment / vertical, beachhead selection, regulatory-delta. Triggers on 'should we enter market X', 'which segment first'. |
 | [`markitdown`](../dist/agent-src/skills/markitdown/SKILL.md) | Use when converting PDF, DOCX, XLSX, PPTX, EPUB, images, or audio to Markdown for LLM ingestion via the upstream markitdown-mcp server — 'extract this PDF', 'OCR this image', 'transcribe this audio'. |
 | [`mcp`](../dist/agent-src/skills/mcp/SKILL.md) | Use when working with MCP (Model Context Protocol) servers — their tools, capabilities, and best practices for effective agent workflows. |
@@ -160,6 +174,7 @@ Click a skill name to open its SKILL.md and read the full guidance.
 | [`po-discovery`](../dist/agent-src/skills/po-discovery/SKILL.md) | Use when shaping a fuzzy product ask into a refined backlog item — problem framing, user-story rewrite, AC tightening — even if the user just says 'help me write this ticket'. |
 | [`positioning-strategy`](../dist/agent-src/skills/positioning-strategy/SKILL.md) | Use when locking the market frame — category, segment, alternative, point-of-view — before messaging, launch, or pricing rides on it. Triggers on 'who are we for', 'opposable audit'. |
 | [`prediction-pool-optimizer`](../dist/agent-src/skills/prediction-pool-optimizer/SKILL.md) | Optimize prediction-pool tips (kicktipp etc.): rules + multi-book consensus odds → expected-points-max answer for every question, scores AND bonus. Triggers 'optimize my pool tips', 'predict'. |
+| [`premortem`](../dist/agent-src/skills/premortem/SKILL.md) | Use before committing to a heavy or irreversible plan — imagine it's 6 months later and this failed; enumerate why, score each mode, derive early-warning signals and preventive guardrails. |
 | [`privacy-review`](../dist/agent-src/skills/privacy-review/SKILL.md) | Use when reviewing data flows, support macros, refund templates for GDPR/CCPA/HIPAA fit — regime, consent, PII redaction (email, order-id), breach triage. Triggers 'is this GDPR-safe', 'PII redact'. |
 | [`project-analysis-core`](../dist/agent-src/skills/project-analysis-core/SKILL.md) | Raw discovery primitives — project discovery, version resolution, docs loading, architecture mapping, execution flow. Called by `universal-project-analysis`. Single-pass scan → `project-analyzer`. |
 | [`project-analysis-hypothesis-driven`](../dist/agent-src/skills/project-analysis-hypothesis-driven/SKILL.md) | Use when a bug has multiple plausible causes across layers — competing hypotheses, validation loops, evidence-based conclusions — even when the user just says 'why is this happening?'. |
@@ -171,6 +186,7 @@ Click a skill name to open its SKILL.md and read the full guidance.
 | [`project-analysis-zend-laminas`](../dist/agent-src/skills/project-analysis-zend-laminas/SKILL.md) | Use for deep Zend Framework or Laminas project analysis: bootstrap, config merge order, service manager, MVC flow, data layer, and migration-specific risks. |
 | [`project-analyzer`](../dist/agent-src/skills/project-analyzer/SKILL.md) | ONLY when user asks for single-pass tech-stack detection or `agents/evidence/analysis/` write-up. Deep multi-pass audit → `universal-project-analysis`. Raw primitives → `project-analysis-core`. |
 | [`project-docs`](../dist/agent-src/skills/project-docs/SKILL.md) | Use when looking for project-specific documentation. Knows which docs exist in agents/reference/docs/ and agents/settings/contexts/ and maps work areas to relevant docs. |
+| [`prompt-engineering-image`](../dist/agent-src/skills/prompt-engineering-image/SKILL.md) | Translate an image brief into provider-specific prompt grammar per model. Use when writing or refining an image-generation prompt for Ideogram, Flux, Gemini, GPT Image 2, or Recraft. |
 | [`prompt-engineering-patterns`](../dist/agent-src/skills/prompt-engineering-patterns/SKILL.md) | Use when designing production-LLM prompts — few-shot, chain-of-thought, system prompts, templates, self-verification — distinct from prompt-optimizer and refine-prompt. |
 | [`prompt-optimizer`](../dist/agent-src/skills/prompt-optimizer/SKILL.md) | Use when the user wants a prompt optimized for ChatGPT, Claude, Gemini, or another AI — 'make this prompt better', 'optimize for ChatGPT', 'rewrite my prompt' — even without saying 'optimize'. |
 | [`prompt-validator`](../dist/agent-src/skills/prompt-validator/SKILL.md) | Pre-spend contradiction gate for AI-video runs: checks every prompt in the batch, blocks on style / character / physics mismatch. Triggers 'validate the prompts', 'check the storyboard'. |
@@ -180,7 +196,7 @@ Click a skill name to open its SKILL.md and read the full guidance.
 | [`readme-reviewer`](../dist/agent-src/skills/readme-reviewer/SKILL.md) | Use when reviewing a README for accuracy, usability, and alignment with the actual repository. Detects invented content, broken setup steps, and structural issues. |
 | [`readme-writing`](../dist/agent-src/skills/readme-writing/SKILL.md) | Use when creating, rewriting, or significantly improving a README based on the actual repository structure, commands, and intended audience. |
 | [`readme-writing-package`](../dist/agent-src/skills/readme-writing-package/SKILL.md) | Use when creating or rewriting a README for a reusable package or library. Focus on installability, minimal usage example, compatibility, and developer onboarding. |
-| [`reasoning-orchestrator`](../dist/agent-src/skills/reasoning-orchestrator/SKILL.md) | Use for complex / ambiguous / long-horizon work — coordinate the reasoning chain ground→intent→notes→gather→audit→verify; composes existing skills, never duplicates them. |
+| [`reasoning-orchestrator`](../dist/agent-src/skills/reasoning-orchestrator/SKILL.md) | Use for multi-step / ambiguous / end-to-end work — refactor a whole module, drive a vague ticket to a verified result, plan+build+verify a migration; coordinates the reasoning chain across skills. |
 | [`receiving-code-review`](../dist/agent-src/skills/receiving-code-review/SKILL.md) | Use when processing code review feedback (bot or human) before changing anything — triages, verifies, and pushes back with technical reasoning — even when the user just says 'fix the comments'. |
 | [`"refine-prompt"`](../dist/agent-src/skills/"refine-prompt"/SKILL.md) | Reconstruct a free-form prompt into actionable AC + assumptions + confidence band before the engine plans — '/work \"…\"', 'baue X', 'ist der Prompt klar genug für die Engine?'. |
 | [`"refine-ticket"`](../dist/agent-src/skills/"refine-ticket"/SKILL.md) | Refine a Jira/Linear ticket before planning — 'refine ticket', 'tighten AC on PROJ-123', 'ist das Ticket klar?' — rewritten ticket, Top-5 risks, persona voices, sub-skills orchestrated, close-prompt. |
@@ -193,6 +209,7 @@ Click a skill name to open its SKILL.md and read the full guidance.
 | [`risk-officer`](../dist/agent-src/skills/risk-officer/SKILL.md) | Use when surfacing and prioritising risk before commit — blast-radius framing, mitigations, residual-risk verdict — even if the user just says 'what could go wrong here?'. |
 | [`roadmap-management`](../dist/agent-src/skills/roadmap-management/SKILL.md) | Use when the user says \"create roadmap\", \"show roadmap\", or \"execute roadmap\". Creates, reads, and manages roadmap files with phase tracking. |
 | [`roadmap-writing`](../dist/agent-src/skills/roadmap-writing/SKILL.md) | Use when authoring or rewriting a roadmap in agents/roadmaps/ — phase prose, goal sentence, acceptance criteria, council notes — even when the user just says 'write a plan for X' or 'draft a roadmap'. |
+| [`root-cause-frameworks`](../dist/agent-src/skills/root-cause-frameworks/SKILL.md) | Use when tracing the root cause of a resolved incident or recurring bug — 5-whys chain, fishbone categorisation, contributing-factors split — even if the user says 'why does this keep breaking?'. |
 | [`rtk-output-filtering`](../dist/agent-src/skills/rtk-output-filtering/SKILL.md) | Use when running verbose CLI commands — wraps them with rtk (Rust Token Killer) for 60-90% token savings. Covers installation, configuration, and usage patterns. |
 | [`rule-refactor`](../dist/agent-src/skills/rule-refactor/SKILL.md) | Use when the rule set is over the Augment budget, when a new rule would breach it, or when asked to audit / merge / prune rules — runs the audit pipeline and proposes a verdict per rule. |
 | [`rule-writing`](../dist/agent-src/skills/rule-writing/SKILL.md) | Use when creating or editing a rule in src/rules/ — trigger wording, always vs auto classification, size budget — even when the user just says 'add a rule for X'. |
@@ -210,8 +227,10 @@ Click a skill name to open its SKILL.md and read the full guidance.
 | [`skill-reviewer`](../dist/agent-src/skills/skill-reviewer/SKILL.md) | Use when reviewing, auditing, or optimizing skills — validates against the 7 Skill Killers checklist and produces fix recommendations. |
 | [`skill-writing`](../dist/agent-src/skills/skill-writing/SKILL.md) | Use when deciding 'should this be a skill or a rule?', creating/improving/reviewing agent skills, SKILL.md frontmatter, or procedure sections — even without saying 'skill-writing'. |
 | [`song-to-script`](../dist/agent-src/skills/song-to-script/SKILL.md) | Turn an audio track into a timed `## Scene N` script: song sections → per-scene durations, auto mode adds mood + lip-sync lines. Triggers 'music video', 'from the song', 'cut to the beat'. |
+| [`source-discovery`](../dist/agent-src/skills/source-discovery/SKILL.md) | Use BEFORE planning/coding against a DB schema, API/GraphQL shape, DTO/Model/Entity, or vendor package — read the real source, emit an Evidence Report, stop inventing fields. |
 | [`sql-writing`](../dist/agent-src/skills/sql-writing/SKILL.md) | Use when writing raw SQL — MariaDB/MySQL syntax, parameterization, raw migrations, seeders with `DB::statement` — even when the user just pastes a query and asks 'why is this slow' without naming SQL. |
 | [`stakeholder-tradeoff`](../dist/agent-src/skills/stakeholder-tradeoff/SKILL.md) | Use when stakeholders pull a decision in different directions — frames each lens, builds a trade-off matrix, surfaces the cost of every choice — even if the user just says 'PO and ops disagree'. |
+| [`standards-from-config`](../dist/agent-src/skills/standards-from-config/SKILL.md) | Use when you need this project's coding standards (line length, quotes, import order, naming, commit format) — derive them from the REAL tooling config as a pointer + digest, never a guessed claim. |
 | [`subagent-orchestration`](../dist/agent-src/skills/subagent-orchestration/SKILL.md) | Use when orchestrating implementer/judge subagents — seven modes (do-and-judge ±two-stage, do-in-steps/parallel/worktrees, do-competitively, judge-with-debate) — models from .agent-settings.yml. |
 | [`symfony-workflow`](../dist/agent-src/skills/symfony-workflow/SKILL.md) | Writes Symfony PHP — DI container, bundles, Doctrine, Messenger, Security voters, console commands. For Laravel / Eloquent / Artisan use `laravel`. For framework-free PHP use `php-coder`. |
 | [`systematic-debugging`](../dist/agent-src/skills/systematic-debugging/SKILL.md) | Use when hitting a bug, test failure, crash, or unexpected behavior — enforces reproduce → isolate → hypothesize → verify before any fix — even when the user just says 'this is broken' or 'quick fix'. |
@@ -227,6 +246,7 @@ Click a skill name to open its SKILL.md and read the full guidance.
 | [`throughput-vs-morale-tradeoff`](../dist/agent-src/skills/throughput-vs-morale-tradeoff/SKILL.md) | Use when balancing eng-team velocity vs quality vs burnout — on-call load, focus fragmentation, reorg shock. Triggers on 'team is burning out', 'why is velocity dropping'. |
 | [`token-optimizer`](../dist/agent-src/skills/token-optimizer/SKILL.md) | Use BEFORE any verbose CLI run, large file read, doc conversion, or near-context handoff — single decision tree keyed by intent that cites the canonical token-saving asset. Consult before the action. |
 | [`traefik`](../dist/agent-src/skills/traefik/SKILL.md) | Use when setting up Traefik as a local reverse proxy — real domains on 127.0.0.1, trusted HTTPS via mkcert, automatic service discovery, and multi-project routing. |
+| [`typography-system`](../dist/agent-src/skills/typography-system/SKILL.md) | Derive a type system from a style constraint — query curated font pairings, set scale/line-height/weights, emit DTCG tokens via design-tokens. Use when choosing fonts or building a typographic scale. |
 | [`ui-component-architect`](../dist/agent-src/skills/ui-component-architect/SKILL.md) | Use when shaping a UI component tree — composition vs inheritance, slot patterns, prop API design, controlled vs uncontrolled, polymorphic — even on 'split this component'. |
 | [`unit-economics-modeling`](../dist/agent-src/skills/unit-economics-modeling/SKILL.md) | Use when modeling CAC, LTV, payback, contribution margin, or burn-multiple per customer — SaaS, marketplace, or transactional. Triggers on 'are we unit-economic', 'what is our LTV/CAC'. |
 | [`universal-project-analysis`](../dist/agent-src/skills/universal-project-analysis/SKILL.md) | ONLY when user asks for deep multi-pass codebase audit — orchestrator routing to `project-analysis-core` + framework-specific `project-analysis-*`. Single-pass scan → `project-analyzer`. |
@@ -234,6 +254,7 @@ Click a skill name to open its SKILL.md and read the full guidance.
 | [`using-git-worktrees`](../dist/agent-src/skills/using-git-worktrees/SKILL.md) | Use when starting parallel work in isolation from the current branch — spawn a git worktree with ignore-safety checks and a clean test baseline — even when the user says 'try this on the side'. |
 | [`"validate-feature-fit"`](../dist/agent-src/skills/"validate-feature-fit"/SKILL.md) | Validate whether a feature request fits the existing codebase — check for duplicates, contradictions, scope creep, and architectural misfit |
 | [`verify-completion-evidence`](../dist/agent-src/skills/verify-completion-evidence/SKILL.md) | Use when claiming 'done', suggesting a commit, push, or PR — runs the evidence gate so completion claims come from fresh output in this message, not memory or earlier runs. |
+| [`verify-repair-loop`](../dist/agent-src/skills/verify-repair-loop/SKILL.md) | Use to iterate a change until tests/quality checks pass — bounded run→revise→re-run gated by a numeric threshold, then a judge confirms. Triggers 'iterate to green', 'keep fixing until tests pass'. |
 | [`video-director`](../dist/agent-src/skills/video-director/SKILL.md) | Use when turning a scene idea into the 11-block cinematic prompt for live-action AI video — lens, lighting, blocking, motion, negatives. Triggers 'cinematic prompt', 'film-grade scene'. |
 | [`vision-articulation`](../dist/agent-src/skills/vision-articulation/SKILL.md) | Use when articulating internal vision — where we're going / why now / why us, founder-mode anchor, distinct from fundraising pitch. Triggers on 'what's our vision', 'why are we doing this'. |
 | [`voc-extract`](../dist/agent-src/skills/voc-extract/SKILL.md) | Use when extracting Voice-of-Customer themes from existing artefacts — GH issues, PR threads, Sentry patterns. Triggers on 'what are users saying', 'recurring complaints', 'top themes'. |