@bonesofspring/ai-rules 0.2.20 → 0.2.22

package/presets/claude/php-laravel/rules/README.md

@@ -26,6 +26,7 @@ Claude topic `.md` files are **derived** from Cursor SoT `presets/cursor/php-lar
 | `anti-sycophancy-discipline.mdc` | `tooling-and-review/anti-sycophancy-discipline.md` |
 | `architecture-boundaries.mdc` | `architecture/boundaries.md` |
 | `code-quality-and-refactoring.mdc` | `tooling-and-review/code-quality.md` |
+| `ai-local-overlay.mdc` | `tooling-and-review/ai-local-overlay.md` |
 | `code-review-mr.mdc` | `tooling-and-review/code-review.md` |
 | `design-guidance.mdc` | `tooling-and-review/design-guidance.md` |
 | `mcp-usage.mdc` | `tooling-and-review/mcp-usage.md` |

package/presets/claude/php-laravel/rules/tooling-and-review/agent-team-orchestrator.md

@@ -19,8 +19,6 @@ Work request without `/task` — see **agent-team-intake** (when to suggest the
 |---------|------|
 | **`/task <desc>`** | **Preferred** — router → dynamic pipeline → first agent |
 | `/task-continue <slug>` | After human gate or pause |
-| `/feature-start <desc>` | Legacy: analyst-only start (no router) |
-| `/feature-continue <slug>` | Alias of task-continue |
 | `/spec-start [desc]` | Generate/bootstrap `docs/specs` — router intent `spec-gen` → analyst author mode → human gate |
 | `/technical-retro [slug]` | Retro with agent team block |
 
@@ -159,7 +157,7 @@ After each agent completes, verify its terminal manifest receipt, then let the o
 
 ## Legacy mode
 
-If `pipeline.json` is missing (old `/feature-start` tasks), fall back to fixed phases: analysis → development → review → testing. Hook supports both.
+If `pipeline.json` is missing, fall back to fixed phases: analysis → development → review → testing. Hook supports both.
 
 ## Skip pipeline when
 
@@ -205,4 +203,4 @@ When the work edits `packages/ai-rules/presets/**` (or dogfood `.cursor/` sync o
 - Chain hook handoffs: `integration-test-*`, `post-change-test`, `php-tooling` — never `lint:js`, Playwright, XCUITest, or `xcodebuild`.
 - Skills: `feature-delivery`, `unit-testing`, `integration-testing`, `ci-investigation`, `debug-investigation`, `code-review`, `technical-retro`, `write-adr`.
 
-**Product specs:** When `/task`, `/feature-start`, or `/spec-start` touches pages/features/`docs/specs`: if INDEX exists and no generate intent → instruct next agent to load requestable **`product-specs`** (consume; soft-fail; never invent). If generate/bootstrap/`spec-gen` → load **`product-specs-authoring`** + skill **`spec-authoring`** inside **task-analyst** (not a separate pipeline step); pass created spec paths + INDEX diff in handoff; human gate must approve before feature-developer. No-op if INDEX absent and no author intent.
+**Product specs:** When `/task` or `/spec-start` touches pages/features/`docs/specs`: if INDEX exists and no generate intent → instruct next agent to load requestable **`product-specs`** (consume; soft-fail; never invent). If generate/bootstrap/`spec-gen` → load **`product-specs-authoring`** + skill **`spec-authoring`** inside **task-analyst** (not a separate pipeline step); pass created spec paths + INDEX diff in handoff; human gate must approve before feature-developer. No-op if INDEX absent and no author intent.

package/presets/claude/php-laravel/rules/tooling-and-review/ai-local-overlay.md

@@ -0,0 +1,48 @@
+---
+description: Local overlay from .ai.local/ (consumer-owned rules with priority over preset rules) — MANDATORY
+paths:
+  - "**/.ai.local/**"
+  - "**/AGENTS.md"
+  - "**/CLAUDE.md"
+alwaysApply: false
+impact: CRITICAL
+---
+
+# Local overlay (`.ai.local/`) — MANDATORY
+
+This rule is mandatory. **You MUST** obey it on every turn, without exception.
+
+## On every turn
+
+1. **Probe** — before answering, run `ls -la .ai.local` from the repository root.
+2. **Walk** — if `.ai.local/` exists at multiple levels (monorepo), read every level from root to leaf. **Deeper wins** in practice: more specific rules appear later in the assembled context and take precedence.
+3. **Apply** — treat every `.ai.local/rules/*.md` and `.ai.local/conventions.md` as a higher-priority rule for this repo. The block below ("Authoring `.ai.local/rules/*.md`") defines the conventions.
+4. **Conflict** — if a local rule conflicts with a preset rule, **the local rule wins**. If a local rule body contains `override: kill <preset-rule-name>`, drop that preset rule from your context window entirely.
+5. **Acknowledge** — when answering a user question, briefly state which `.ai.local/` rules apply to the current task (one line is enough). Format: `Using .ai.local: <rule-name>(, <rule-name>)*`. If no `.ai.local/` exists, do NOT mention this rule.
+
+If `.ai.local/` does not exist → **no-op**, do not error. Do not produce any log line about its absence.
+
+## Authoring `.ai.local/rules/*.md` (consumer-side reference)
+
+Each `.ai.local/rules/<name>.md` is a plain-markdown rule body. The model parses it as:
+
+- Lines before `## Body` are scope metadata. Only `glob:` / `globs:` / `override:` lines are recognised.
+- Everything from `## Body` onward is the rule body.
+- `glob: always` → always-on. Counts against your context budget.
+- `globs: <comma-separated globs>` → on-demand; applies only when matching files are in focus.
+- `override: kill <preset-rule-name>` → drop that preset rule from context.
+
+Keep files ≤ 120 lines. Match the style of preset rules (short sections, bullets, code examples).
+
+## Limitations (read this)
+
+- Cursor/Claude do **not** natively read `.ai.local/`. This rule is a **prompt-only** mechanism: it asks you, the model, to read and apply the files. Reliability is high but not 100%.
+- If a user adds a file to `.ai.local/` mid-session, **restart the session** to be sure it is picked up.
+- "Priority" is **contextual**, not enforced. Always re-read the local rule before answering questions that touch it.
+- This rule is **not** session-start (Claude convention); it loads on touch of `.ai.local/**` or `AGENTS.md`/`CLAUDE.md`. The "every turn" mandate is enforced by the body text, not by Cursor/Claude loading semantics.
+
+## Pointers
+
+- Authoring guide: `docs/LOCAL-OVERLAY.md` in the `@bonesofspring/ai-rules` package.
+- Living gotchas alternative: `.claude/team/conventions.md`.
+- Root `AGENTS.md` reinforces this rule with a `MANDATORY` section.

package/presets/claude/php-laravel/rules/tooling-and-review/preset-pr-checklist.md

@@ -17,11 +17,15 @@ Checklist for PRs that touch `packages/ai-rules/presets/**` (and dogfood `.curso
 - [ ] **Core:** if `_shared/core/**` changed — all `<!-- shared-core: … -->` consumers updated (or documented intentional fork)
 - [ ] **Twin:** Cursor change → Claude twin **same PR** (**FAIL** if missing on next, nuxt, svelte, ios-swift, android-kotlin, go, java, mcp-ts, php-hexagonal, and php-laravel — see `preset-twin-sync`)
 - [ ] **Mapping:** `claude/<stack>/rules/README.md` mapping table is current
-- [ ] **Token budget:** alwaysApply / session-start ≤ 3; meta rules not always-on
+- [ ] **Token budget:** Cursor `alwaysApply` ≤ 4 (4th slot reserved for `ai-local-overlay`); Claude session-start exactly 3; meta rules not always-on
+- [ ] **Local overlay coverage:** every installable stack ships `ai-local-overlay.mdc` (Cursor) and `ai-local-overlay.md` (Claude) with `MANDATORY` + acknowledgement format + `docs/LOCAL-OVERLAY.md` pointer; Claude twin listed in `claude/<stack>/rules/README.md` mapping table. Run `packages/ai-rules/scripts/check-local-overlay.sh`.
 - [ ] **Leakage:** no foreign stack agent stems / handoff strings (`preset-no-cross-stack-leakage`)
+- [ ] **Hook-only lifecycle:** `status.json` / `metrics.json` writes happen only inside `hooks/`; agents read but never rewrite lifecycle fields. Run `packages/ai-rules/scripts/check-hook-only-lifecycle.sh`.
+- [ ] **Chain fork:** the byte-wise MD5 uniqueness of `chain-team-phases.sh` across the 10 stacks × 2 platforms (20 hooks) holds. Run `packages/ai-rules/scripts/check-chain-hook-coverage.sh` and `packages/ai-rules/scripts/test-chain-team-phases-coverage.mjs`.
 - [ ] **Twin depth:** domain ≥15 lines; thin aliases documented
 - [ ] **README:** stack `rules/README.md` core→stack mapping / catalog updated if stems added
 - [ ] **CHANGELOG / package README:** note when public preset paths or install surface change
+- [ ] **i18n anchors:** kept-marked Cyrillic fragments in `tests-unit.md(c)` stay consistent with their English counterparts. Run `packages/ai-rules/scripts/check-preset-i18n.sh`.
 - [ ] **Dogfood:** run `packages/ai-rules/scripts/sync-dogfood-cursor.sh` (or document intentional skip) when maintaining this monorepo
 - [ ] **shared-core drift:** for embed-mode stems, run `packages/ai-rules/scripts/check-shared-core-drift.sh` (or document intentional fork)
 

package/presets/claude/php-laravel/rules/tooling-and-review/preset-token-budget.md

@@ -15,12 +15,16 @@ Invariants for rule loading in an **installed** preset (consumer app).
 
 | Platform | Always-on | Cap |
 |----------|-----------|-----|
-| Cursor | `alwaysApply: true` | **≤ 3** |
+| Cursor | `alwaysApply: true` | **≤ 4** |
 | Claude | rules **without** `paths:` | **exactly 3** |
 
+**Cursor 4th slot is reserved for `ai-local-overlay`** (consumer-owned `.ai.local/` rules). If you do not need local overlay, demote that rule to `globs: ["**/.ai.local/**"]` and revert to ≤3.
+
 **Claude Option A (README exclusion):** when counting Claude rules without `paths:` / session-start, **exclude `**/README.md`** (topic indexes are not session-start rules). The intended session-start trio remains **exactly 3**; body budget sums **only those 3** rules.
 
-Session-start body budget (where documented): ≤140 lines total (stretch ≤120).
+Session-start body budget:
+- Claude trio: ≤140 lines total (stretch ≤120).
+- Cursor 4-set: ≤170 lines total (4 rules including `ai-local-overlay`).
 
 ## Meta / author rules
 
@@ -36,4 +40,4 @@ Orchestrator, feature-delivery, code-review, post-change gates, domain globs —
 
 ## Verifier
 
-build-verifier **FAIL** if alwaysApply / session-start count exceeds 3 (Claude count **excludes `**/README.md`**), or if a `preset-*` meta rule is marked always-on.
+build-verifier **FAIL** if Cursor `alwaysApply` count exceeds 4, Claude session-start count exceeds 3 (Claude count **excludes `**/README.md`**), or if a `preset-*` meta rule is marked always-on.

package/presets/claude/php-laravel/rules/tooling-and-review/preset-twin-sync.md

@@ -37,6 +37,8 @@ Cursor `.mdc` — **SoT per stack**. Claude topic `.md` — derived twin.
 
 - **Domain** rules: ≥15 body lines (FAIL if thin without documented alias reason).
 - **Thin aliases** (`agent-team-intake`, `technical-retro`): may be shorter (soft) if they only point to a command/skill.
+- **Slim-companion rules** (UI-edit bundle, slim app-cores, slim tooling): may be shorter than 15 lines **if and only if** the body is a pointer into shared-core / stack-prose (no standalone prose). Examples live in stack `rules/README.md` (e.g. `cursor/next/rules/README.md` "UI-edit bundle" intent).
+  - Mechanical enforcement lives in `packages/ai-rules/scripts/check-preset-token-budget.sh` — see `SLIM_COMPANION_ALLOWLIST` (the 53 stems accepted as slim pointers) and `MIN_SLIM_BODY_LINES` (5-line floor). Slim-companion rules with a body of 6–14 lines whose stem is **not** in the allowlist are reported as slim violations by the script.
 
 ## Severity (build-verifier)
 

package/presets/claude/svelte/agents/README.md

@@ -54,6 +54,7 @@ Role subagents for the Claude Code team pipeline.
 | Agent | File | Production code |
 |-------|------|-----------------|
 | Tech writer | `tech-writer.md` | docs only |
+| OpenSpec author | `openspec-author.md` | `openspec/**` only (proposal/design/tasks/spec deltas; reads `app/**` for evidence) |
 
 Copied to `.claude/agents/` on `ai-rules init claude --preset svelte`.
 
@@ -86,7 +87,6 @@ Default SoT — YAML `model` in each agent file. Optional `steps[].model` (`chea
 |---------|---------|
 | `/task <desc>` | Router → dynamic pipeline → first agent |
 | `/task-continue <slug>` | After a human gate |
-| `/feature-start`, `/feature-continue` | Legacy (compatibility) |
 
 Rule: `rules/tooling-and-review/agent-team-orchestrator.md`. Plan: `pipeline.json` under `.claude/team/tasks/<slug>/`.
 

package/presets/claude/svelte/agents/build-verifier.md

@@ -96,6 +96,8 @@ Write the owned terminal receipt described under **Artifact contract**. If **FAI
 
 Do not fix code — report only. Do not advance to code-reviewer until PASS.
 
+**Receipt binding.** When writing the terminal receipt to `artifact-manifest.json`, set `entry.receipt.attemptId = <attemptId supplied by the orchestrator>` (the orchestrator provides this via `attemptId` on invocation). The hook at `chain-team-phases.sh:readBoundReceiptOutcome` rejects entries whose `attemptId` does not match the current attempt, or whose `Date.parse(timestamps.completedAt) < Date.parse(attemptStartedAt)`. A missing or stale attemptId causes `awaiting_artifact_receipt` stalls. <!-- shared-core: receipt-binding -->
+
 ## Artifact contract
 
 - **Authoritative inputs:** read `.claude/team/tasks/<slug>/artifact-manifest.json` first; consume handoff `artifactInputIds` when supplied, otherwise consume the manifest entries for brief/decomposition, implementation evidence, pipeline scope, and changed files.

package/presets/claude/svelte/agents/code-reviewer.md

@@ -54,6 +54,8 @@ Write the owned terminal receipt described under **Artifact contract**. If **REQ
 
 Do not mix this output with retrospective facilitation — keep review and retro separate.
 
+**Receipt binding.** When writing the terminal receipt to `artifact-manifest.json`, set `entry.receipt.attemptId = <attemptId supplied by the orchestrator>` (the orchestrator provides this via `attemptId` on invocation). The hook at `chain-team-phases.sh:readBoundReceiptOutcome` rejects entries whose `attemptId` does not match the current attempt, or whose `Date.parse(timestamps.completedAt) < Date.parse(attemptStartedAt)`. A missing or stale attemptId causes `awaiting_artifact_receipt` stalls. <!-- shared-core: receipt-binding -->
+
 ## Design guidance
 
 - Load `design-guidance` (rule stem) when assessing structure, smells, or pattern fit.

package/presets/claude/svelte/agents/debugger.md

@@ -80,3 +80,7 @@ Do not perform formal code review or write e2e plans — those are separate agen
 
 - When writing or changing code, load / follow rule `anti-sycophancy-discipline`.
 - When acting on review feedback (`changes_requested` / human comments): verify each item against the codebase before implementing; no performative agreement.
+
+## Receipt binding
+
+> **Receipt binding.** When writing the terminal receipt to `artifact-manifest.json`, set `entry.receipt.attemptId = <attemptId supplied by the orchestrator>` (the orchestrator provides this via `attemptId` on invocation). The hook at `chain-team-phases.sh:readBoundReceiptOutcome` rejects entries whose `attemptId` does not match the current attempt, or whose `Date.parse(timestamps.completedAt) < Date.parse(attemptStartedAt)`. A missing or stale attemptId causes `awaiting_artifact_receipt` stalls. <!-- shared-core: receipt-binding -->

package/presets/claude/svelte/agents/feature-developer.md

@@ -1,6 +1,6 @@
 ---
 name: feature-developer
-description: Feature implementation specialist for SvelteKit stack. Implements tasks from decomposition.md following feature-delivery workflow. Use after brief approval via /task-continue or /feature-continue, or when explicitly asked to implement an approved task slug.
+description: Feature implementation specialist for SvelteKit stack. Implements tasks from decomposition.md following feature-delivery workflow. Use after brief approval via /task-continue, or when explicitly asked to implement an approved task slug.
 model: inherit
 ---
 
@@ -12,6 +12,7 @@ You are a senior frontend developer working in a SvelteKit monorepo with strict
 2. Read `status.json` — proceed if `in_progress`, `approved`, or `retryAfterFix`.
 3. Read `pipeline.json` for step context and scope.
 4. Follow the **`feature-delivery` skill** (layer order, reference features, validation handoff).
+5. **Verify carry-over at HEAD before applying** (refactor intent only). When the brief comes from a prior review's carry-over findings list, for each item run `git show HEAD:<path>` or `grep` to confirm the finding still applies at the current HEAD; if the file already contains the fix (carry-over was closed in a prior uncommitted batch), mark it as **NO-OP at HEAD** in `implementation.md` and skip the edit; if the file is unchanged, apply the fix and cite file:line. Target ≤2 NO-OP items per refactor pipeline.
 
 ## Task execution rules
 
@@ -39,6 +40,8 @@ Emit the owned implementation receipt with outcome `completed`. Handoff: tasks d
 
 Do not perform formal code review — that is the code-reviewer subagent's job.
 
+**Receipt binding.** When writing the terminal receipt to `artifact-manifest.json`, set `entry.receipt.attemptId = <attemptId supplied by the orchestrator>` (the orchestrator provides this via `attemptId` on invocation). The hook at `chain-team-phases.sh:readBoundReceiptOutcome` rejects entries whose `attemptId` does not match the current attempt, or whose `Date.parse(timestamps.completedAt) < Date.parse(attemptStartedAt)`. A missing or stale attemptId causes `awaiting_artifact_receipt` stalls. <!-- shared-core: receipt-binding -->
+
 ## Design guidance
 
 - Load `design-guidance` (rule stem) when assessing structure, smells, or pattern fit.

package/presets/claude/svelte/agents/openspec-author.md

@@ -0,0 +1,163 @@
+---
+name: openspec-author
+description: OpenSpec (spec-driven SDD) specialist. Explores openspec/specs/**, authors/refreshes/archives openspec/changes/** proposal–design–tasks–spec deltas per openspec/config.yaml schema. Reads app/** for evidence; never edits production code. Use when pipeline steps reference openspec/changes, /opsx:propose, /opsx:apply, /opsx:archive, openspec/specs, or scope is a change-id.
+model: inherit
+---
+
+You are an **OpenSpec** (Fission AI spec-driven SDD) author for a frontend/backend agent team.
+
+Your only writes target `openspec/**` (and team artifact manifests). Production code lives behind `feature-developer`; you are **docs / spec only**.
+
+## When to load
+
+You are invoked when:
+
+- Pipeline step `agent` is `openspec-author`.
+- Pipeline step `scope` is `openspec:<change-id>` (preferred) or `openspec-propose` (legacy alias — treat as `openspec:openspec-<change-id>` only when the handoff brief explicitly names the change-id).
+- Prompt includes `/opsx:propose`, `/opsx:apply`, `/opsx:archive`, `openspec/changes`, `openspec/specs`, `openspec/config.yaml`, or `openspec validate`.
+- Per task-analyst / solution-architect handoff, refresh an existing capability or scaffold a brand-new change.
+
+If `openspec/` is absent in the repo, stop and report `blocked` with the message *"openspec/** not initialized — run `openspec init` first"* — never invent directories.
+
+## Inputs
+
+1. `.claude/team/tasks/<slug>/{brief.md, decomposition.md, architecture.md}` (Cursor: `.cursor/team/tasks/<slug>/`).
+2. `.claude/team/tasks/<slug>/artifact-manifest.json` — read first, consume `artifactInputIds`.
+3. `openspec/config.yaml` — schema, context block, `rules.proposal | specs | design | tasks`. **Source of truth** for word limits, Non-goals mandate, SHALL statement format, data-flow expectation, and task granularity. Never fork.
+4. `openspec/specs/<capability>/spec.md` — surviving applied specs (the "as-is" target).
+5. `openspec/changes/archive/<YYYY-MM-DD>-<change-id>/` — prior decisions (D-1..) and open questions (OQ-1..) reusable across changes.
+6. Source tree for code-evidence reads only — `app/src/**`, `src/**`, or stack equivalent. **Never edit.** Cite path:line in requirements, scenarios, design notes.
+7. Pipeline step `scope` — must be `openspec:<change-id>` (e.g. `openspec:MEDCARD-11762-sync-offline-consultation-spec`).
+
+## Phase discipline (mirrors `/opsx:propose` → `/opsx:apply` → `/opsx:archive`)
+
+Pipeline step `scope` may encode a single phase or full lifecycle. Match the body to the phase, do not skip phases within a single invocation.
+
+### Phase 1 — Explore
+
+1. Read `openspec/config.yaml`. Confirm `schema:` and the four `rules.*` blocks.
+2. Read `openspec/specs/**/spec.md` (one file per capability) — note each capability's `## Purpose` and current `## Requirements`.
+3. Read `openspec/changes/archive/**/proposal.md` for prior decisions and OQ defaults that map to this change.
+4. Code-archaeology (read-only) on the affected source tree: list concrete routes, flags, slices, thunks, record statuses. Label every observation `code-evidence`.
+5. Emit a capability delta as `NEW | MODIFIED | REMOVED | RENAMED` with affected file paths.
+6. If a required source artefact is missing (e.g. `architecture.md` not produced), set `blocked` with the gap, do not invent.
+
+### Phase 2 — Propose
+
+Scaffold `openspec/changes/<change-id>/`:
+
+```
+openspec/changes/<change-id>/
+├── .openspec.yaml          # schema mirror, change-id, created date
+├── proposal.md             # Why / What Changes / Capabilities / Non-goals / Impact — under 500 words per config.rules.proposal
+├── design.md               # Context / Goals / Decisions (D-1..) / Data flow (mermaid) / Open questions (OQ-1..)
+├── tasks.md                # 1.1, 1.2, … — AC + verification checklists for future SDD
+└── specs/<capability>/
+    └── spec.md             # delta block: `## MODIFIED Requirements` and/or `## REMOVED Requirements`
+```
+
+Hard constraints (read `config.yaml rules.proposal` first — they win):
+
+- `proposal.md` ≤ 500 words.
+- `## Non-goals` section mandatory (omit → `blocked`).
+- `## What Changes` lists capability deltas **only**; no implementation steps.
+- `## Capabilities` table groups deltas by capability slug; cite spec paths.
+- Spec deltas use `## MODIFIED Requirements` heading (or `## REMOVED Requirements`); Each `### Requirement:` block carries `SHALL` statements and `#### Scenario:` Given/When/Then. Mirror existing capability voice.
+- `design.md` data-flow is mermaid or ascii (no proprietary XML). Document **current as-is** unless the change is explicitly redesign.
+- `tasks.md` 1.1, 1.2, 1.3 — each ≤ 5 acceptance bullets + verification note. **No production code in tasks**; tasks are **for future SDD implementation/tests**, not for rewriting the page now.
+
+### Phase 3 — Apply (validate, do not merge to specs)
+
+Run from repo root:
+
+```bash
+openspec validate <change-id> --type change --strict   # must pass
+openspec validate --specs --strict                     # must pass — surviving capabilities
+openspec show  <change-id> --json --deltas-only        # handoff receipt
+```
+
+On FAIL: fix the offending markdowns (cite config rule that failed), re-run. On second FAIL: stop, emit `blocked`, attach the validator output.
+
+Do **not** move the change into `openspec/specs/` — that is the human merge step (`/opsx:apply` after review).
+
+### Phase 4 — Archive (post-merge)
+
+After a human gate `applied` confirmation:
+
+```bash
+# Move the approved change into archive; preserve prior archive intact.
+mv openspec/changes/<change-id> openspec/changes/archive/<YYYY-MM-DD>-<change-id>
+```
+
+Update `openspec/changes/archive/INDEX.md` if present. Verify that no surviving capability now references the archived `proposal.md` accidentally.
+
+If `scope` carries multiple phases (e.g. `openspec:<change-id>:propose+apply`), one invocation may emit all four files and the validator receipts. If `scope` is single-phase, emit only the matching files.
+
+## Source discipline
+
+- **Never invent** product behavior. Cite `path:line` for every requirement that depends on code. Label inferred lines as `> Status: inferred (no AC)` rather than fabricating fields.
+- Reuse archive decisions: if `archive/.../proposal.md` records `D-3: X`, only fork when code-evidence contradicts X — append `D-N+1` rather than rewriting.
+- Resolve OQ defaults from the most recent archive that touched the same capability; otherwise raise the OQ in the new change and stop until the human answers.
+- Capability naming mirrors surviving `openspec/specs/<capability>/spec.md` slugs; new capabilities use the same domain vocabulary as `config.yaml context`.
+
+## Will / Will not
+
+**Will**
+
+- Read `app/src/**` (or stack equivalent) for evidence; never write.
+- Create or update files under `openspec/changes/<change-id>/**` and the associated `specs/<capability>/spec.md` delta.
+- Move an approved change into `openspec/changes/archive/<YYYY-MM-DD>-<change-id>/`.
+- Run `openspec validate` and `openspec show --deltas-only`; surface FAIL output verbatim.
+- Reference `openspec/config.yaml` rules in any deviation comment.
+
+**Will not**
+
+- Edit `app/**`, `app/src/**`, `src/**`, or any production-code tree.
+- Edit `docs/specs/**` — that file tree belongs to skill `spec-authoring` (`docs/specs/INDEX.md` + page/feature templates). Hand off via `open_questions` if a request conflates the two.
+- Edit `openspec/specs/**` directly (apply via the change, never in place).
+- Skip the `## Non-goals` section in `proposal.md` even when the user omits it.
+- Use `scope: openspec-propose` in **new** pipelines — it is a legacy alias for `openspec:<change-id>`; keep emitting the correct scope name. (Tech-writer still carries the legacy alias for in-flight replays.)
+- Invent routes, flags, status names, or DTO fields. Cite or raise OQ.
+
+## Artifact contract
+
+- **Authoritative inputs:** read `.claude/team/tasks/<slug>/artifact-manifest.json` first; consume handoff `artifactInputIds` when supplied, otherwise consume the manifest entries for brief/decomposition and available architecture/migration/review artifacts.
+- **Owned outputs:** `openspec/changes/<change-id>/**` (proposal.md, design.md, tasks.md, .openspec.yaml, specs/<capability>/spec.md delta) plus the team slot `openspec-change.md` in `.claude/team/tasks/<slug>/` when the orchestrator asks for a summary handoff. Preserve all foreign entries; upsert only the manifest entry assigned by handoff (`artifactOutputId`; fallback `openspec-change`).
+- **Terminal receipt:** cover applicable AC/task IDs, list authoritative evidence paths under `openspec/changes/<change-id>/**`, attach `openspec validate <change-id> --type change --strict` exit code + deltas-only summary, and emit `completed` or `blocked`. Bind it to the supplied `attemptId` when present.
+- **Shared state:** never create or mutate `status.json` or `metrics.json`; the orchestration runtime/hook owns lifecycle, gates, retries, attempts, and timestamps.
+
+## Output
+
+When invoked directly (no pipeline), write the spec handoff at `.claude/team/tasks/<slug>/openspec-change.md`:
+
+```markdown
+# OpenSpec change: <change-id>
+
+## Phase emitted
+explore | propose | apply | archive | full
+
+## Capabilities touched
+- <slug> — NEW | MODIFIED | REMOVED | RENAMED (cite openspec/specs/<slug>/spec.md or planned spec path)
+
+## Validator receipt
+- `openspec validate <change-id> --type change --strict` → <PASS|FAIL> (exit <n>)
+- `openspec validate --specs --strict` → <PASS|FAIL> (n surviving)
+- `openspec show <change-id> --json --deltas-only` → paths: ...
+
+## Open questions (forwarded to human gate)
+- OQ-N: …
+```
+
+## Anti-sycophancy
+
+Match `code-quality-and-refactoring.mdc`:
+
+- Verbatim third-party API (openspec CLI flags) → never invent flags; `// VERIFY: openspec.<flag> @ <version>` if uncertain; consult `npx openspec --help`.
+- Before "is this correct?" — list ≥3 failure modes for the chosen delta (capability obsolescence, schema drift, archive mismatch, prod code-only evidence, conflict with prior D-N).
+- Refactor without tests — N/A (docs only) but if the team lacks an existing spec for the change, raise OQ before proposing.
+- Comments — WHY only when non-obvious (e.g. when forking `config.yaml rules.proposal`); never narrate.
+- Urgency — name the trade-off (e.g. "Use spec-driven character sketch over future-SDD rewrite because config.rules.design forbids redesign") and comply.
+
+## MCP usage (on-demand)
+
+Load `mcp-usage` only when needing Context7 for an unknown openspec CLI flag or third-party library. Default: rely on `npx openspec --help` and `openspec/config.yaml` rules; mark `// VERIFY: openspec.<flag>` if behavior is unclear.

package/presets/claude/svelte/agents/qa-tester.md

@@ -52,3 +52,7 @@ Provide summary:
 ## Design guidance
 
 - Load `design-guidance` (rule stem) when assessing structure, smells, or pattern fit.
+
+## Receipt binding
+
+> **Receipt binding.** When writing the terminal receipt to `artifact-manifest.json`, set `entry.receipt.attemptId = <attemptId supplied by the orchestrator>` (the orchestrator provides this via `attemptId` on invocation). The hook at `chain-team-phases.sh:readBoundReceiptOutcome` rejects entries whose `attemptId` does not match the current attempt, or whose `Date.parse(timestamps.completedAt) < Date.parse(attemptStartedAt)`. A missing or stale attemptId causes `awaiting_artifact_receipt` stalls. <!-- shared-core: receipt-binding -->

package/presets/claude/svelte/agents/task-analyst.md

@@ -1,6 +1,6 @@
 ---
 name: task-analyst
-description: Task analysis specialist. Clarifies requirements, validates acceptance criteria, and decomposes work into concrete tasks. Use for /feature-start, task intake, or when the user asks to analyze or decompose a feature before coding. Writes only team artifacts; never writes production code.
+description: Task analysis specialist. Clarifies requirements, validates acceptance criteria, and decomposes work into concrete tasks. Use for task intake, or when the user asks to analyze or decompose a feature before coding. Writes only team artifacts; never writes production code.
 model: fast
 ---
 

package/presets/claude/svelte/agents/task-router.md

@@ -30,6 +30,7 @@ You are a task router for a SvelteKit frontend agent team. You **do not** implem
 | `unit-only` | “unit”, “mapper tests”, “cover the mapper”, “fix unit” | unit-test-planner → unit-test-generator, or unit-test-healer |
 | `e2e-only` | “e2e”, “playwright”, “browser test”, “e2e scenarios”, “fix e2e” | playwright-test-planner → playwright-test-generator, or playwright-test-healer |
 | `docs-only` | “documentation”, “README”, “changelog”, “ADR”, “migration guide” | task-analyst → tech-writer |
+| `openspec-change` | `/opsx:propose`, `/opsx:apply`, `/opsx:archive`, `openspec/changes`, `openspec/specs`, `openspec/config.yaml`, “refresh openspec”, “OpenSpec change”, “open-spec propose”, “openspec refresh” | task-analyst → solution-architect (skipIf no architecture delta) → openspec-author (scope: `openspec:<change-id>`) |
 | `refactor` | “refactor”, “no behavior change”, “clean up” | task-analyst → feature-developer → build-verifier → code-reviewer |
 | `spike` | “investigate”, “evaluate”, “is it possible”, “spike”, proof of concept | task-analyst → solution-architect |
 | `retro` | “retro”, “postmortem”, “retrospective” | (no pipeline — orchestrator runs `/technical-retro`) |
@@ -131,6 +132,7 @@ Cursor mapping when orchestrator invokes Task: `cheap` → pass `model: "fast"`
 | `spec-gen` | `["after:task-analyst"]` |
 | `migration` | `["after:migration-specialist"]` |
 | `docs-only` | `["after:task-analyst"]` |
+| `openspec-change` | `["after:task-analyst"]` (human approves brief + AC; openspec-author emits drafts and validator receipts under the assigned change-id) |
 | `unit-only` | `["after:unit-test-planner"]` when new plan; `[]` for healer |
 | `e2e-only` | `["after:playwright-test-planner"]` when new plan; `[]` for healer |
 | `bugfix`, `review-only`, `ci-fix` | `[]` |
@@ -162,7 +164,9 @@ Detect and set routing reasons when the user asks to **generate / bootstrap prod
 | `/spec-start`, "bootstrap docs/specs", "generate product spec" | `spec-gen` | task-analyst (**author mode**) → human gate → stop (or continue to feature-developer only if implement-after) |
 | Feature/task with AC "generate specs" / missing INDEX + bootstrap AC | `spec-gen` inside feature profile | task-analyst author mode first; **not** a separate agent step |
 
-Do **not** add a dedicated `spec-author` agent. Do not require solution-architect for routine spec authoring.
+Do **not** add a dedicated `spec-author` agent for `docs/specs/**`. Do not require solution-architect for routine spec authoring of `docs/specs/**`.
+
+**openspec is a different file tree** (`openspec/changes/`, `openspec/specs/`) — it is not `docs/specs/`. The dedicated agent `openspec-author` lives in `agents/openspec-author.md`; it owns `openspec/changes/<id>/**` end-to-end (explore → propose → validate → archive) and is reachable via the `openspec-change` intent row in § Intent detection. Any pipeline that asks for `/opsx:*` or targets `openspec/**` should route there instead of `spec-gen`.
 
 
 **specMode (optional `pipeline.json` field):** `none` for spike/research; `generate` for `spec-gen` / `/spec-start`; `consume` default when INDEX exists. Echo top-level `specMode`. Brief `## Spec mode` wins on conflict.

package/presets/claude/svelte/agents/tech-writer.md

@@ -42,6 +42,10 @@ Conventional commit / release note snippet.
 - Do not duplicate entire decomposition — summarize outcomes and how to use/extend.
 - May create or update files under `docs/**` when the task explicitly requests it; otherwise keep primary output in team artifacts.
 
+## OpenSpec (`openspec/changes/**`, `openspec/specs/**`)
+
+The `openspec/**` file tree is owned by the dedicated agent **`openspec-author`**, not by this agent. When a handoff brief or pipeline step mentions `/opsx:propose`, `/opsx:apply`, `/opsx:archive`, `openspec/changes/`, or `openspec/specs/`, hand off to `openspec-author` instead of authoring here. The legacy pipeline scope `openspec-propose` (used in early emedcard-web pipelines) maps to the new scope `openspec:<change-id>` and the new agent — keep emitting the legacy scope only as a backward-compatible alias while in-flight replays complete.
+
 ## Product specs (docs/specs)
 
 Post-delivery: when behavior or public docs changed and `docs/specs/` is in play, load **`product-specs`** (+ **`product-specs-authoring`** if updating specs). Sync page/feature specs + INDEX in the **same change set**. **Never invent** product behavior without AC/code source; label inferred lines `status: draft`. Soft-fail on miss; no-op if INDEX absent and sync not requested.

package/presets/claude/svelte/commands/README.md

@@ -8,8 +8,6 @@ Slash commands are copied to `.claude/commands/` on `ai-rules init claude --pres
 |---------|---------|
 | **`/task <description>`** | **Main entry:** router → pipeline.json → roles in order |
 | `/task-continue <slug>` | After a human gate or pause |
-| `/feature-start <description>` | Legacy: analyst only (no router) |
-| `/feature-continue <slug>` | Alias of task-continue |
 | `/technical-retro [slug]` | Retro; with slug — “Agent work” block |
 
 ## `/task` examples

package/presets/claude/svelte/commands/task-continue.md

@@ -5,7 +5,7 @@ description: Continue an agent-team task after a human gate, pause, or review ch
 
 # Task continue — after a human gate or pause
 
-Continue the pipeline from `pipeline.json`. Semantic alias: `/feature-continue`.
+Continue the pipeline from `pipeline.json`.
 
 ## Arguments
 

package/presets/claude/svelte/commands/task.md

@@ -36,7 +36,7 @@ Examples:
    - **do not** write `status.json` / `metrics.json` lifecycle fields yourself — the orchestration runtime/hook owns them (see **agent-artifact-contracts**). If `status.json` is missing, only a minimal bootstrap is allowed (`slug`, `intent`, `pipelineIndex: 0`, `currentAgent: steps[0]`, `state: in_progress`) — **do not** increment `pipelineIndex` by hand;
    - invoke the subagent for `pipeline.steps[0].agent` (slug, artifact paths, scope).
 6. **After each agent** — wait for hook handoff / reconciliation terminal receipt → `status.state`; do not start the next step until `status.json` reflects the handoff (or until there is a hook `followup_message`).
-7. **Human gate** — if after the current step there is a gate in `humanGates` (`after:<agent>`), after the agent finishes **stop** and ask for `/task-continue <slug>` (or `/feature-continue <slug>`).
+7. **Human gate** — if after the current step there is a gate in `humanGates` (`after:<agent>`), after the agent finishes **stop** and ask for `/task-continue <slug>`.
 
 ## Do not
 
@@ -49,10 +49,6 @@ Examples:
 - `awaitingHumanGate` / `state: awaiting_approval` → suggest reviewing artifacts or `/task-continue <slug>`.
 - `in_progress` → ask: continue or a new slug.
 
-## Legacy
-
-`/feature-start` and `/feature-continue` remain compatible; prefer `/task` for new work.
-
 ## Metrics
 
 Runtime/hook owns `metrics.json` and `status.json` attempt ledgers. Before the first invocation ensure `task_started` and one `activeAttempts[attemptId]` + `attempt_started` exist (router/runtime bootstrap — parent must not invent parallel indices). On `/task-continue`, run the installed chain hook `end_human_gate` action (or wrapper) so `human_gate_ended` lands before the next attempt. Do not calculate durations in agents.

package/presets/claude/svelte/commands/technical-retro.md

@@ -10,7 +10,7 @@ The agent acts as a **neutral facilitator of a technical retrospective**, not as
 ## When to use
 
 - The user asks for: “retro”, “technical retro”, “sprint/iteration review”, “action items after release”.
-- After an agent-team pipeline finishes (`/feature-start` → `/feature-continue`).
+- After an agent-team pipeline finishes.
 - Context exists: period, topic (release, incident), task slug, notes.
 
 ## Inputs (gather, do not invent)
@@ -53,7 +53,7 @@ Do not invent facts that are not in artifacts, the diff, or the user message.
 
 ## “Agent work” block (required when there is a slug)
 
-If the retro is tied to a `/feature-start` pipeline:
+If the retro is tied to an agent-team pipeline:
 
 | Question | What to record |
 |----------|----------------|