@event4u/agent-config 5.10.1 → 6.0.0

package/.agent-src/contexts/contracts/artifact-engagement-flow.md

@@ -1,259 +0,0 @@
----
-stability: beta
----
-
-# Artifact Engagement — Flow & Recording Contract
-
-> Cross-cutting reference for the artifact-engagement telemetry system.
-> The schema, CLI, and engine ship first; the agent-side hooks (this
-> document) ship after.
->
-> - **Created:** 2026-04-30
-> - **Status:** schema, engine, recording, aggregator, renderer, and
->   redaction validator are in place. Dogfooding next.
-
-This document is the stable reference for **what gets recorded, when, and
-under which constraints**. The roadmap tracks phased delivery; the rule
-([`artifact-engagement-recording`](../../.agent-src.uncondensed/rules/artifact-engagement-recording.md))
-tells the agent when to fire; this doc explains the contract every
-recording must honour.
-
-## What this is
-
-A measurement layer that tells maintainers which **skills, rules,
-commands, guidelines and personas** the agent actually consults and
-applies during a `/implement-ticket` or `/work` run. The output (a local
-JSONL log) becomes the input to the Phase 4 aggregator + report renderer.
-
-## What this is *not*
-
-- Token-spend tracking — handled separately by the cost-profile system.
-- Tool-call telemetry — out of scope.
-- A retirement decision-maker — Phase 4's report surfaces signal; humans
-  decide what to retire.
-- A consumer-facing analytics product — local-only, opt-in, never
-  uploaded.
-
-## Threat model in one paragraph
-
-Engagement data is **observation**, not delivery. A missed event is
-cheap. A leaked prompt, a leaked path, or a leaked secret is not. Every
-field in the schema is **id-only**: no free-text, no payloads, no paths.
-The CLI rejects oversized strings on the input boundary; the agent must
-not even attempt to write content.
-
-## When the agent records
-
-Two granularities, one per task or one per phase-step:
-
-```
-refine → memory → analyze → plan → implement → test → verify → report
-                          ↑
-            granularity: phase-step → 1 record per arrow crossed
-            granularity: task        → 1 record on terminal state only
-```
-
-The setting lives at `telemetry.artifact_engagement.granularity` in
-`.agent-settings.yml`. Default `task`. Both flows
-([`/implement-ticket`](../../.agent-src.uncondensed/commands/implement-ticket.md)
-and [`/work`](../../.agent-src.uncondensed/commands/work.md)) use the
-same eight-step contract from
-[`implement-ticket-flow.md`](implement-ticket-flow.md).
-
-### Boundary semantics
-
-A boundary is **closed** when:
-
-- The dispatcher returns `SUCCESS`, `BLOCKED`, or `PARTIAL` for the
-  current step (phase-step granularity), or
-- The full eight-step flow reaches a terminal state (task granularity).
-
-A boundary is **never** closed by:
-
-- An error inside the agent's tool call (the user's task is paramount;
-  see "failure modes" below).
-- A model-side exception or timeout.
-- Settings reload mid-flow — settings are read once per task and cached.
-
-Within a single boundary, repeated `consulted` / `applied` mentions of
-the same `<kind>:<id>` pair **dedupe**. Reading `php-coder` three times
-records once.
-
-## What counts as consulted vs applied
-
-| Term | Meaning | Examples |
-|---|---|---|
-| **`consulted`** | The agent **read** the artefact this boundary | Opened `SKILL.md`, scanned a rule body, looked at a guideline, checked persona contract, cited the artefact id in reasoning |
-| **`applied`** | The artefact **influenced the output** this boundary | A skill's procedure produced the code; a rule's gate halted a flow; a guideline's pattern shaped the diff |
-
-`applied` is a strict subset of `consulted`. When in doubt → record as
-`consulted` only. Over-recording `applied` inflates the engagement
-signal and defeats the whole point of the system.
-
-## Forbidden — what NEVER goes into a record
-
-The privacy contract is enforced at **four** layers — schema (write
-gate), aggregator (read gate via `parse_event`), renderer (export gate),
-and CLI (surface gate). Each layer rejects the same set of shapes;
-defense in depth means a leak has to bypass all four to escape:
-
-- File paths — any string containing `/`, `\`, or a control character.
-- File extensions — trailing `.md`, `.py`, `.json`, `.yaml`, `.yml`,
-  `.php`, `.ts`, `.js`, etc. Detected by
-  `re.compile(r"\.[a-z0-9]{1,10}$", re.IGNORECASE)` in
-  `telemetry.engagement.check_id_redaction`.
-- Source code, prompts, ticket bodies, AC text, comments.
-- Branch names, commit shas, PR numbers, URLs.
-- Secrets, env vars, credentials, customer data.
-- Free-text strings longer than 200 chars.
-- Leading or trailing whitespace, tabs, newlines.
-- Empty strings.
-
-The id namespaces are stable and bounded:
-
-| Kind | Source | Example |
-|---|---|---|
-| `skills` | `.agent-src/skills/<id>/SKILL.md` | `php-coder`, `eloquent` |
-| `rules` | `.agent-src/rules/<id>.md` | `scope-control`, `language-and-tone` |
-| `commands` | `.agent-src/commands/<id>.md` | `commit`, `create-pr` |
-| `guidelines` | `docs/guidelines/<path>/<id>.md` | `agent-interaction-and-decision-quality` |
-| `personas` | `.agent-src/personas/<id>.md` | `qa`, `senior-engineer` |
-
-`task_id` is the ticket key (`PROJ-123`) for `/implement-ticket` or a
-short opaque slug derived from the prompt for `/work`. Branch names,
-file paths, and free-text titles are forbidden in `task_id` — see the
-schema's `EngagementSchemaError` cases.
-
-### The four enforcement layers
-
-1. **Schema (write gate)** — `EngagementEvent.validate()` in
-   `telemetry/engagement.py` runs `check_id_redaction` over `task_id`
-   and every `consulted` / `applied` artefact id. The CLI exits `1`
-   when this fires; nothing reaches the JSONL.
-2. **Aggregator (read gate)** — `aggregator._iter_events` calls
-   `parse_event`, which re-runs the same validator. A pre-validator
-   line (e.g. an archived snapshot from before the validator landed)
-   is **skipped** and counted in `result.skipped_lines`. The renderer
-   never sees it.
-3. **Renderer (export gate)** — `_stat_to_dict` (JSON) and the
-   markdown row builder both call `check_id_redaction` again before
-   emitting any id. If a caller bypasses `parse_event` and hand-builds
-   an `AggregateResult`, the renderer raises `EngagementSchemaError`
-   instead of producing the row.
-4. **CLI (surface gate)** — `telemetry_report.main` catches
-   `EngagementSchemaError` from the renderer and exits `2` with a
-   `redaction validator refused report` message. A bad row is never
-   written to stdout, never piped to a teammate.
-
-A leak would have to defeat all four layers — write the JSONL outside
-the CLI, parse it outside `parse_event`, render it outside the
-project's renderer, and ship it to a teammate without the CLI in the
-loop. The contract treats that as out of scope.
-
-## How the agent records
-
-```bash
-./agent-config telemetry:record \
-  --task-id "$TASK_ID" \
-  --boundary task \
-  --consulted skills:php-coder \
-  --consulted rules:scope-control \
-  --applied skills:php-coder
-```
-
-Exit codes (the agent must read these):
-
-| Exit | Meaning | Action |
-|---|---|---|
-| `0` | Recorded, or telemetry disabled (silent no-op) | Continue |
-| `1` | Schema validation failed | Log internally, **continue** the user's task — do not halt |
-| `2` | IO failure (lock contention, disk full) | Same — observation, not delivery |
-
-Schema-rejection messages go to stderr; the agent reads them once and
-moves on. The user's task always takes priority.
-
-## Failure modes — DO NOT block the user's task
-
-- Telemetry is **observation**, not a delivery requirement.
-- A missing event is cheap; a halted task because telemetry can't write
-  is a critical failure mode that defeats the whole opt-in property.
-- The only error the agent surfaces to the user: when the user asked
-  for telemetry (`telemetry:status` confirms enabled) but no event
-  reached the log over a full task — that is a real bug.
-
-## Cost floor — what "default-off" means
-
-When `telemetry.artifact_engagement.enabled: false` (or section absent):
-
-- The rule is `auto` and the description does not match a typical
-  conversation; the rule never loads. Cost floor: 0 tokens.
-- The CLI exits `0` with no output and no file IO.
-- The engine (`work_engine.dispatcher`, `work_engine.cli`) does not
-  import any `telemetry.*` module — locked by
-  [`tests/telemetry/test_cost_floor.py`](../../tests/telemetry/test_cost_floor.py).
-- On cloud surfaces (Claude.ai Web, Skills API), the rule's
-  `cloud_safe: noop` marker keeps the rule inert regardless of settings.
-
-## Where the JSONL lives
-
-Default path: `.agent-engagement.jsonl` in the consumer repo root.
-Configurable via `telemetry.artifact_engagement.output.path`. The path
-is **always** added to the consumer's `.gitignore` block by the
-installer (Phase 1 wiring). Verify locally:
-
-```
-$ grep agent-engagement .gitignore
-.agent-engagement.jsonl
-```
-
-## How to audit a JSONL by hand
-
-The fastest path is the project's own validator — it enforces every
-rule listed above:
-
-```bash
-# Validate every line against the schema + redaction floor
-python3 -c '
-import pathlib, sys
-sys.path.insert(0, ".agent-src.uncondensed/templates/scripts")
-from telemetry.engagement import EngagementSchemaError, parse_event
-log = pathlib.Path(".agent-engagement.jsonl")
-ok = bad = 0
-for i, line in enumerate(log.read_text().splitlines(), 1):
-    if not line.strip():
-        continue
-    try:
-        parse_event(line + "\n")
-        ok += 1
-    except EngagementSchemaError as e:
-        bad += 1
-        print(f"line {i}: {e}", file=sys.stderr)
-print(f"{ok} valid, {bad} rejected")
-'
-
-# A bad-line spot-check that does not depend on the validator
-python3 -c '
-import json, pathlib, re
-forbidden = re.compile(r"[/\\\\]|\.[a-z0-9]{1,10}$", re.IGNORECASE)
-for line in pathlib.Path(".agent-engagement.jsonl").read_text().splitlines():
-    if not line.strip():
-        continue
-    obj = json.loads(line)
-    for kind in ("consulted", "applied"):
-        for ids in obj.get(kind, {}).values():
-            for v in ids:
-                if forbidden.search(v) or len(v) > 200:
-                    print("LEAK:", v)
-'
-```
-
-Either recipe is safe to run on a co-worker's archived JSONL — neither
-writes anything, both surface the same shapes the four enforcement
-layers reject.
-
-## See also
-
-- [`artifact-engagement-recording`](../../.agent-src.uncondensed/rules/artifact-engagement-recording.md) — agent-side trigger
-- [`implement-ticket-flow`](implement-ticket-flow.md) — the eight-step contract this rule observes
-- [`scripts/telemetry/`](../../.agent-src.uncondensed/templates/scripts/telemetry/) — schema, boundary session, settings reader
-- [`tests/telemetry/`](../../tests/telemetry/) — contract enforcement (schema, settings, aggregator, renderer, CLI, cost-floor, redaction)

package/.agent-src/contexts/contracts/consumer-agents-md-guide.md

@@ -1,127 +0,0 @@
-# Consumer `AGENTS.md` — fill-out guide
-
-> Outboard target for the placeholder sections that used to live verbatim
-> in the consumer-template `AGENTS.md`. The template is now Thin-Root; this
-> guide carries the prose / examples / `<!-- … -->` hints that the
-> consumer copies in only when they need them.
-
-After installing `event4u/agent-config`, the consumer project gets:
-
-- `AGENTS.md` at project root — Thin-Root, points here.
-- `.augment/`, `.agent-src/`, `.claude/`, `.cursor/`, `.clinerules/`,
-  `.windsurfrules` — installed artifacts, never hand-edited.
-- `agents/` — project docs / roadmaps / sessions / overrides.
-- `.agent-settings.yml` — project config consumed by skills.
-
-## Recommended `AGENTS.md` shape
-
-The installed Thin-Root carries: project name + description, layer table,
-five-question emergency triage block, pointers to this guide. Copy any of
-the sections below into AGENTS.md only when the project actually needs
-the content there (e.g. an unusual stack note that no `agents/` doc
-covers). Default: leave AGENTS.md thin and put detail under `agents/`.
-
-## Tech-stack section (optional copy-in)
-
-```markdown
-## Tech Stack
-
-- **Language:** {{primary_language}}
-- **Framework:** {{framework}}        # Laravel 11 / Next.js 15 / Rails 7 / Django 5
-- **Database:** {{database}}          # PostgreSQL / MySQL / MariaDB / SQLite
-- **Testing:** {{test_framework}}     # Pest / PHPUnit / Jest / Vitest / pytest
-- **Code style:** {{code_style_tool}} # ECS / PHPStan / Ruff / ESLint
-```
-
-## Development-setup section (optional copy-in)
-
-```markdown
-## Development Setup
-
-​```bash
-{{dev_start_command}}    # make start / docker compose up / npm run dev / php artisan serve
-{{dev_test_command}}     # make test / docker compose exec app bash / npm test / php artisan test
-​```
-
-### Environment files
-
-| File | Purpose |
-|---|---|
-| `.env` | Main environment |
-| `.env.local` | Local overrides |
-| `.env.testing` | Testing environment |
-```
-
-## Project-structure section (optional copy-in)
-
-```markdown
-## Project Structure
-
-{{project_structure_notes}}   # Where new features go, module/component
-                              # boundaries, namespace conventions.
-```
-
-## Testing section (optional copy-in)
-
-```markdown
-## Testing
-
-{{testing_notes}}             # Framework quirks, how to run all/targeted
-                              # tests, test data strategy (seeders /
-                              # factories / fixtures), performance-critical
-                              # suites.
-```
-
-## Quality-tools section (optional copy-in)
-
-```markdown
-## Quality Tools
-
-{{quality_tools_notes}}       # Which linters/formatters run, whether
-                              # they auto-fix or report only, CI
-                              # enforcement level.
-```
-
-## Recommended entry flow
-
-Two entrypoints share the same engine and Option-A loop; pick by input shape:
-
-| You have | Command | Envelope |
-|---|---|---|
-| Ticket id, URL, or pasted ticket payload | [`/implement-ticket`](.augment/commands/implement-ticket.md) | `input.kind="ticket"` |
-| Free-form goal, no ticket | [`/work`](.augment/commands/work.md) | `input.kind="prompt"` |
-
-Both drive the linear flow `refine → memory → analyze → plan → implement
-→ test → verify → report` with block-on-ambiguity semantics and no
-auto-git.
-
-`/work` adds a confidence-band gate at `refine`: the
-[`refine-prompt`](.augment/skills/refine-prompt/SKILL.md) skill scores
-the prompt on five dimensions and the engine proceeds **silently** on
-`high`, halts with an **assumptions report** on `medium`, or halts with
-**one clarifying question** on `low` (per the `ask-when-uncertain` Iron
-Law). UI-shaped prompts route through the product UI track (`directive_set`
-`ui` / `ui-trivial` / `mixed`) — `audit → design → apply → review →
-polish` with a hard audit gate before any `apply`.
-
-Persona comes from `.agent-settings.yml` (`roles.active_role`). Use
-`/commit` and `/create-pr` explicitly after the delivery report. The
-two flows are mutually exclusive at the state-file level: one
-`.work-state.json` carries one envelope at a time; the engine refuses to
-switch mid-flight.
-
-## Multi-agent support
-
-| Tool | Rules | Skills | How |
-|---|---|---|---|
-| **Augment Code** | `.augment/rules/` | `.augment/skills/` | Native (source) |
-| **Claude Code** | `.claude/rules/` | `.claude/skills/` | Symlinks + Agent Skills standard |
-| **Cursor** | `.cursor/rules/` | — | Symlinks |
-| **Cline** | `.clinerules/` | — | Symlinks |
-| **Windsurf** | `.windsurfrules` | — | Concatenated file |
-| **Gemini CLI** | `GEMINI.md` | — | Symlink → AGENTS.md |
-
-Reinstall agent-config: `composer update event4u/agent-config` (PHP) or
-`npm update @event4u/agent-config` (JS). Don't run package-internal
-`task` commands from a consumer project; they only work in the
-agent-config repo itself.

package/.agent-src/contexts/contracts/emergency-triage-block.md

@@ -1,53 +0,0 @@
-# Emergency Triage Block — canonical source
-
-> Canonical content of the **Emergency Triage** block referenced by the
-> `agents-md-thin-root` skill. Both the package-root `AGENTS.md` and
-> `.agent-src.uncondensed/templates/AGENTS.md` (consumer template)
-> embed this block verbatim. Drift is caught by the `lint-agents-md`
-> task in the package's CI pipeline.
-
-The block exists so a host agent can answer five basic questions from
-the root file alone when network access, context-engine retrieval, or
-linked-file fetches are degraded. Each answer fits on one line.
-
-## Package-root variant
-
-Use this variant in `AGENTS.md` at the package root.
-
-```
-## Emergency triage — read this when nothing else is reachable
-
-1. **What is this repo?** — `event4u/agent-config`, a governed skill / rule / command suite for AI coding tools (no application runtime).
-2. **What language?** — All `.md` content is English; agents mirror the user's language at runtime.
-3. **Where do I edit?** — `.agent-src.uncondensed/` only. Never `.agent-src/`, `.augment/`, `.claude/`, `.cursor/`, `.clinerules/`, `.windsurfrules`.
-4. **Lint / test / sync entry point?** — `task ci` (full pipeline). Subsets: `task sync`, `task generate-tools`, `task lint-skills`, `task test`.
-5. **Where do the always-active rules live?** — `.agent-src/rules/` (kernel = 9 Iron-Law rules; tier-1 / tier-2 routed via `.agent-src/router.json`).
-```
-
-## Consumer-template variant
-
-Use this variant in `.agent-src.uncondensed/templates/AGENTS.md`. The
-consumer's `AGENTS.md` lands at the consumer-project root after install.
-
-```
-## Emergency triage — read this when nothing else is reachable
-
-1. **What is this repo?** — Consumer project; agent-config is installed as a shared skill / rule / command suite at `.augment/` and `.agent-src/`.
-2. **What language?** — Project-specific; agents mirror the user's language at runtime.
-3. **Where do I edit agent-config?** — Do not edit `.augment/` or `.agent-src/` here; they are installed artifacts. Project edits live in `agents/` and project source.
-4. **Lint / test / sync entry point?** — Project-specific (see project README); agent-config itself reinstalls via `composer update event4u/agent-config` or `npm update @event4u/agent-config`.
-5. **Where do the always-active rules live?** — `.agent-src/rules/` (kernel = 9 Iron-Law rules; tier-1 / tier-2 routed via `.agent-src/router.json`).
-```
-
-## Why two variants
-
-The package-root and the consumer template answer the same five
-questions but in different repos:
-
-- The package-root variant points at this repo's authoring layer
-  (`.agent-src.uncondensed/`) and the package's CI entry point.
-- The consumer variant tells the agent it is in a **consumer** project
-  where `.augment/` is an installed artifact and editing it is wrong.
-
-The questions stay identical so a host agent can recognise the block
-visually regardless of which repo it landed in.

package/.agent-src/personas/README.md

@@ -1,114 +0,0 @@
-# Personas
-
-> Reusable **review lenses** as a first-class primitive. A persona
-> declares a *voice*: focus, mindset, unique questions, output
-> expectations. Skills cite personas in a `personas:` frontmatter key.
-> Users invoke them via `--personas=<id>`.
-
-> For end-user-of-the-software lenses (galabau field crew, truck
-> driver, metalworking shop), see the parallel
-> [`user-types/`](../user-types/README.md) axis — personas describe
-> **how** we review (methodology), user-types describe **who** we
-> simulate (end user). They compose orthogonally on the CLI:
-> `--personas=qa --user-type=truck-driver`. No existing persona moves
-> to `user-types/`.
-
-## Why this directory exists
-
-Before personas, every multi-lens skill (`adversarial-review`,
-`judge-*`, `review-changes`, any future `refine-ticket`) reinvented
-its own cast of reviewers. The taxonomies drifted, output became
-untraceable, and new lenses were copy-pasted instead of reused.
-
-Personas fix that: one definition, many skills.
-
-## What a persona is — and is not
-
-- **Is**: a small Markdown file declaring a voice. Passive reference
-  content, loaded on demand by the skill that cites it.
-- **Is not**: a skill. Personas never trigger by description. They
-  do not appear in `<available_skills>`.
-- **Is not**: a role-mode. Role-modes (see `role-contracts.md`) own
-  the *workflow closing contract* axis. Personas own the *voice* axis.
-  They coexist; a persona may declare an advisory `mode:` link.
-
-## Schema
-
-Locked in [`../../docs/contracts/persona-schema.md`](../../docs/contracts/persona-schema.md).
-Two-tier hybrid (council iter-1 A-OQ1 verdict (c)):
-
-- **Core** — 5 sections (Focus · Mindset · Unique Questions · Output
-  Expectations · Anti-Patterns), ≤ 120 lines. Always-loaded cast.
-- **Specialist** — 7 sections (Core-5 + Critical Rules + Workflows),
-  ≤ 100 lines. Opt-in lens.
-
-Frontmatter is uniform across tiers: `id · role · description · tier
-· mode · version · source`. See the contract for full details and
-the linter check list.
-
-## The Core-6 (always-loaded cast, v1)
-
-| ID | Tier | Focus |
-|---|---|---|
-| `developer` | core | implementation reality |
-| `senior-engineer` | core | architecture impact, long-term risk |
-| `product-owner` | core | outcome, testable AC, scope |
-| `stakeholder` | core | business value, relevance |
-| `critical-challenger` | core | fake clarity, hidden complexity |
-| `ai-agent` | core | automation-readiness, safe execution |
-
-## Specialists (opt-in)
-
-| ID | Tier | Focus |
-|---|---|---|
-| `qa` | specialist | testability, failure scenarios |
-| `hollywood-director` | specialist | live-action cinematic prompts — lens, lighting, blocking, negative constraints |
-| `ai-video-technical-director` | specialist | provider tuning — Veo / Kling / OpenAI / Higgsfield / Sora grammar, token caps, audio flags |
-
-More specialists may land in v1.1+ — each must pass the
-Unique-Questions heuristic before being drafted. Removed personas
-are deleted in-commit (no soak window) per
-[`persona-governance § Deprecation path`](../rules/persona-governance.md).
-
-## How skills use personas
-
-Cite them in frontmatter:
-
-```yaml
----
-name: adversarial-review
-personas: [critical-challenger]
----
-```
-
-Or accept a CLI-style override:
-
-```
-/refine-ticket --personas=po,senior-engineer
-```
-
-If `personas:` is omitted, the skill uses its documented default
-cast (usually Core-6 for review skills, empty for others).
-
-## Authoring rules
-
-- Every persona is drafted via the `artifact-drafting-protocol` rule.
-- Every persona must pass the Unique-Questions heuristic.
-- Project-specific personas live in the consumer repo
-  (`.agent-src/personas/` overrides), never in this package.
-- **Core** template: [`../templates/persona.md`](../templates/persona.md) (5 sections, ≤ 120 lines).
-- **Specialist** template: [`./_template-specialist/persona.md`](./_template-specialist/persona.md) (7 sections, ≤ 100 lines).
-
-## Related
-
-- [`../../docs/contracts/persona-schema.md`](../../docs/contracts/persona-schema.md) — locked schema (Core / Specialist)
-- [`../../docs/guidelines/agent-infra/role-contracts.md`](../../docs/guidelines/agent-infra/role-contracts.md) — workflow modes personas compose with
-- [`../rules/artifact-drafting-protocol.md`](../rules/artifact-drafting-protocol.md) — mandatory per new persona
-
-## See also — sibling voice primitives
-
-Personas are one of three voice primitives. Same shape (Markdown +
-frontmatter), distinct purpose — **no folding, no shared schema**:
-
-- [`../../docs/contracts/agent-user-schema.md`](../../docs/contracts/agent-user-schema.md) — `.agent-user.md`, the maintainer's own voice (`/post-as:me`, no disclosure footer).
-- [`../../docs/contracts/ghostwriter-schema.md`](../../docs/contracts/ghostwriter-schema.md) — `agents/reference/ghostwriter/<slug>.md`, captured public-figure voice (`/ghostwriter:write` / `/post-as:ghostwriter`, mandatory disclosure footer).

package/.agent-src/profiles/agency.yml

@@ -1,27 +0,0 @@
-# Seed profile — agency
-# Schema: docs/contracts/profile-system.md
-profile:
-  id: agency
-  audience:
-    label: "Multi-client delivery shop"
-    readme_anchor: "agency"
-  defaults:
-    preset_id: strict
-    personas:
-      - reviewer
-      - product-strategist
-      - editor
-    skills_hint:
-      - doc-coauthoring
-      - decision-record
-      - refine-ticket
-      - estimate-ticket
-      - perf-feedback-craft
-  surface:
-    commands_hint:
-      - work
-      - implement-ticket
-      - refine-ticket
-      - feature
-      - roadmap
-    docs_first_pointer: "docs/getting-started-by-role.md#agency"

package/.agent-src/profiles/content_creator.yml

@@ -1,30 +0,0 @@
-# Seed profile — content_creator
-# Schema: docs/contracts/profile-system.md
-profile:
-  id: content_creator
-  audience:
-    label: "Writers, ghostwriters, marketers"
-    readme_anchor: "content_creator"
-  defaults:
-    preset_id: balanced
-    personas:
-      - editor
-      - brand-voice
-    skills_hint:
-      - voice-and-tone-design
-      - messaging-architecture
-      - editorial-calendar
-      - release-comms
-      - prompt-engineering-patterns
-      - character-consistency
-  surface:
-    commands_hint:
-      - work
-      - post-as
-      - ghostwriter
-      - optimize-prompt
-      - video:from-script
-      - video:storyboard
-      - video:scene
-      - video:stitch
-    docs_first_pointer: "docs/getting-started-by-role.md#content_creator"

package/.agent-src/profiles/developer.yml

@@ -1,26 +0,0 @@
-# Seed profile — developer
-# Schema: docs/contracts/profile-system.md
-profile:
-  id: developer
-  audience:
-    label: "IC engineer"
-    readme_anchor: "developer"
-  defaults:
-    preset_id: balanced
-    personas:
-      - reviewer
-      - security
-    skills_hint:
-      - developer-like-execution
-      - verify-completion-evidence
-      - minimal-safe-diff
-      - systematic-debugging
-      - test-driven-development
-  surface:
-    commands_hint:
-      - work
-      - implement-ticket
-      - review-changes
-      - fix
-      - commit
-    docs_first_pointer: "docs/getting-started-by-role.md#developer"

package/.agent-src/profiles/finance.yml

@@ -1,24 +0,0 @@
-# Seed profile — finance
-# Schema: docs/contracts/profile-system.md
-profile:
-  id: finance
-  audience:
-    label: "CFO / fractional finance / FP&A"
-    readme_anchor: "finance"
-  defaults:
-    preset_id: strict
-    personas:
-      - finance-partner
-      - reviewer
-    skills_hint:
-      - dcf-modeling
-      - forecasting
-      - scenario-modeling
-      - unit-economics-modeling
-      - runway-cognition
-  surface:
-    commands_hint:
-      - work
-      - council
-      - challenge-me
-    docs_first_pointer: "docs/getting-started-by-role.md#finance"