@bonesofspring/ai-rules 0.2.12 → 0.2.14

package/presets/claude/svelte/skills/svelte-performance/SKILL.md

@@ -0,0 +1,52 @@
+---
+name: svelte-performance
+description: SvelteKit performance checklist for implementers — bundle, lazy routes, dynamic import, load waterfalls, hydration, Core Web Vitals. Use while coding a svelte feature; not a substitute for the performance-auditor agent when the user asks for an audit report.
+---
+
+# Svelte performance (SvelteKit)
+
+On-demand checklist for **implementers** shipping SvelteKit UI. For a formal diff audit report, use the **`performance-auditor`** agent instead — this skill does not replace it.
+
+**No RSC model** — SvelteKit uses SSR/CSR/hydration; do not apply Next Server Component guidance. Do not apply Vue/Nuxt payload APIs as defaults.
+
+## Bundle
+
+- Prefer route-level code-splitting (file routes) and dynamic `import()` for heavy UI (charts, editors).
+- Avoid importing large libraries into root `+layout` that run globally; keep client entry points small.
+- Check that barrel files do not re-export heavy modules into every consumer.
+
+## Lazy routes & dynamic import
+
+- Heavy feature UI: lazy via dynamic `import()` or a separate route.
+- Do not eagerly import large optional widgets into the root layout.
+- Prefer patterns already used in the repo over inventing a second loader.
+
+## Load & data waterfalls
+
+- Avoid sequential `await` chains in `load` that could be parallel (`Promise.all`) when independent.
+- Prefer shared services/mappers in `$lib/api`; dedupe with existing keys/invalidation patterns.
+- Stores/runes for client-mutable state — do not invent a second cache layer.
+
+## Hydration
+
+- Keep SSR markup consistent with client first paint; avoid `window` in universal modules without client guards.
+- Prefer client-only mount patterns already in the repo for browser-only widgets.
+- Do not ship large client-only state into the critical SSR path without need.
+
+## Reactivity discipline
+
+- Do **not** add derived/memo wrappers by default for trivial state.
+- Prefer fixing state placement and `{#each}` keys over blanket memoization.
+- Follow Svelte 5 runes / store patterns used by neighbors (`store-svelte`).
+
+## Core Web Vitals (quick)
+
+| Metric | Implementer checks |
+|--------|--------------------|
+| LCP | Hero/media not blocked by unnecessary client JS; sensible image sizing |
+| INP | Click handlers lean; avoid long sync work on the main thread |
+| CLS | Reserve space for images/skeleton; stable fonts |
+
+## Handoff
+
+If the user asks for a **performance audit report** of a diff/deliverable, route to **`performance-auditor`** (readonly `perf-report.md`), not this skill alone.

package/presets/claude/svelte/skills/technical-retro/SKILL.md

@@ -0,0 +1,54 @@
+---
+name: technical-retro
+description: Facilitates technical retrospectives for tasks, sprints, incidents, releases, and agent-team pipelines. Use when the user asks for retro, postmortem, process review, or action items after delivery.
+---
+
+# Technical Retro
+
+## Inputs
+
+Ask for missing period, focus, task slug, participants, or format constraints. If a slug is provided, read `.claude/team/tasks/<slug>/` artifacts and local git status/diff. Do not invent facts not present in artifacts or the user's message.
+
+## Facilitation Principles
+
+- Focus on process and system behavior, not blame.
+- Separate facts, interpretations, and proposed actions.
+- Balance what worked with what slowed delivery.
+- Keep action items concrete, owned, and measurable.
+
+## Default Structure
+
+1. Goal and scope.
+2. Timeline or factual observations.
+3. What worked.
+4. What hurt quality, speed, or confidence.
+5. Root causes for the top one or two issues.
+6. Experiments and action items.
+
+## Agent Team Block
+
+For `/task` pipelines, include router, analyst, developer, **build-verifier**, reviewer, QA/e2e, hooks, and rules.
+
+## Wrong-turn taxonomy (optional)
+
+When artifacts or the user mention agent mistakes, tag incidents:
+
+| Kind | Signal |
+|------|--------|
+| `correction` | User pushback («no», «don't», «actually») |
+| `retry` | Same tool/approach 2+ times before success |
+| `waste` | Many searches before the right file |
+| `reversal` | Edit then revert / delete |
+| `dead-end` | Env/tool failure (missing binary, wrong path) |
+
+Severity: **high** (explicit correction / large waste) · **med** · **low**. Confidence 0–100 — be honest; low-confidence items are optional.
+
+## Preset feedback loop
+
+If the same issue appeared in **2+** tasks (or **3+** for packaging a new rule/skill — Rule of Three), add section **Preset updates**:
+
+- Proposed change to `.claude/rules/`, `.claude/agents/`, `.claude/skills/`, or **`.claude/team/conventions.md`** (prefer conventions for project gotchas)
+- One concrete snippet or file path
+- Whether it belongs in session-start vs `paths:` vs skill vs conventions (see `PRESET-CONTRIBUTION` → Building blocks)
+
+Do not apply preset or conventions changes without user approval.

package/presets/claude/svelte/skills/unit-testing/SKILL.md

@@ -0,0 +1,32 @@
+---
+name: unit-testing
+description: Plans, generates, and heals unit tests for mappers, Svelte stores/runes actions, HTTP client behavior, and Svelte components using colocated *.spec.ts files and tests-unit rules. Use for unit test planning, generation, or fixing failing unit tests.
+---
+
+# Unit Testing
+
+## Project Layout
+
+- Specs colocated with source: `*.spec.ts` next to the module under test.
+- Legacy `*.test.ts` — do not rename without a separate task.
+- Runner: Jest or Vitest as configured in the target repo; components use `@testing-library/svelte`.
+
+Follow **`rules/testing/tests-unit.md`**.
+
+## Planner
+
+Write or update `.claude/team/tasks/<slug>/unit-test-plan.md`.
+
+Each scenario needs a Russian `it()` title (capital letter after each sentence). Cover mappers, Svelte stores/runes actions, client behavior branches, and component interactions per AC.
+
+## Generator
+
+Implement specs from `unit-test-plan.md`. Reuse project test-store, HTTP mocks, and existing test utilities. Do not change production code.
+
+## Healer
+
+Fix mocks, async timing, selectors, and setup — preserve business assertions. Use `unit-test-plan.md` and `brief.md` as the behavior contract.
+
+## Validation
+
+Run affected unit tests from repository root when feasible. Report command, pass/fail, and remaining gaps vs plan.

package/presets/claude/svelte/skills/write-adr/SKILL.md

@@ -0,0 +1,41 @@
+---
+name: write-adr
+description: Author an Architecture Decision Record (ADR) with Context, Decision, Consequences, and Links. Use when capturing a durable technical choice for the team.
+---
+
+# Write ADR
+
+On-demand skill for durable architecture decisions. Stack-agnostic sections — fill with project-specific paths and links.
+
+## When to use
+
+- Choosing between non-trivial alternatives (storage, layering, library, API shape).
+- Recording a decision that future agents/humans should not silently reverse.
+- User asks for an ADR, decision log, or “why did we pick X”.
+
+## Template
+
+Create (or append) a short markdown ADR in the repo’s agreed location (e.g. `docs/adr/`, `.cursor/team/`, wiki). Suggested filename: `NNNN-short-title.md`.
+
+```markdown
+# ADR NNNN: <Title>
+
+## Context
+What problem / constraint / force requires a decision?
+
+## Decision
+What we chose (one clear option). Include rejected alternatives briefly if useful.
+
+## Consequences
+Positive and negative outcomes; follow-up work; what becomes harder.
+
+## Links
+Related PRs, issues, rules, prior ADRs, diagrams.
+```
+
+## Guidelines
+
+- Prefer one decision per ADR.
+- Keep Context factual; Decision imperative and short.
+- Link living gotchas to `team/conventions.md` when the decision becomes a recurring local pattern.
+- Do not put ADR bodies only in root `AGENTS.md` (overwrite on init).

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

@@ -0,0 +1,136 @@
+# Agent team artifacts
+
+Каталог артефактов пайплайна «команда агентов» Claude.
+
+## Layout
+
+```
+.claude/team/
+  active-task.json
+  fixtures/                  # pipeline profile examples (feature-full, feature-light, bugfix-standard)
+  tasks/
+    <slug>/
+      pipeline.json
+      status.json
+      metrics.json             # schema-v1 append-only event ledger (see Local metrics ledger)
+      brief.md
+      decomposition.md
+      debug-report.md          # fixApplied: true/false
+      validation-report.md     # build-verifier: PASS | FAIL
+      architecture.md
+      migration-plan.md
+      ci-report.md
+      a11y-review.md
+      perf-report.md
+      security-review.md
+      api-contract-review.md
+      unit-test-plan.md
+      documentation.md
+      review.md
+```
+
+## pipeline.json schema
+
+```json
+{
+  "slug": "order-history-date-filter",
+  "intent": "feature",
+  "summary": "Add date filter to Order History",
+  "steps": [
+    { "agent": "task-analyst", "label": "Clarify and decompose" },
+    { "agent": "feature-developer", "label": "Implement + unit tests", "scope": "unit-in-dev" },
+    { "agent": "build-verifier", "label": "Validation gate" },
+    { "agent": "code-reviewer", "label": "Code review" },
+    { "agent": "qa-tester", "label": "E2E", "scope": "e2e-only" }
+  ],
+  "humanGates": ["after:task-analyst"],
+  "autoChain": true,
+  "skipped": []
+}
+```
+
+### Step fields
+
+| Field | Description |
+|-------|-------------|
+| `agent` | kebab-case name or array when `parallel: true` |
+| `label` | Human-readable step name |
+| `scope` | Passed to agents (e.g. `unit-in-dev`, `e2e-only`) |
+| `skipIf` | `debugger.fixed` \| `ci-investigator.resolved` |
+| `parallel` | Invoke all `agent` values in one parent turn |
+
+## status.json (pipeline mode)
+
+```json
+{
+  "slug": "order-history-date-filter",
+  "intent": "feature",
+  "pipelineIndex": 0,
+  "currentAgent": "task-analyst",
+  "phase": "executing",
+  "state": "in_progress",
+  "awaitingHumanGate": false,
+  "retryAfterFix": null,
+  "activeAttempts": {},
+  "lastCompletedAttempt": null,
+  "parallelCompleted": [],
+  "parallelOutcomes": {},
+  "updatedAt": "2026-05-29T12:00:00.000Z"
+}
+```
+
+### phase
+
+Prefer **`executing`** for pipeline mode. Legacy: `analysis`, `development`, `review`, `testing`, `done`.
+
+### state
+
+| Value | Description |
+|-------|-------------|
+| `in_progress` | Current step running |
+| `completed` | Current step finished |
+| `awaiting_approval` | Human gate; use `/task-continue` |
+| `changes_requested` | Reviewer requires fixes |
+| `validation_failed` | build-verifier failed |
+| `approved` | Legacy continue |
+
+## Workflow entry
+
+```bash
+/task <описание задачи>
+/task-continue <slug>
+/technical-retro <slug>
+```
+
+Legacy: `/feature-start`, `/feature-continue`.
+
+## Git
+
+Commit task artifacts if you want them to survive `ai-rules clean claude`. Or copy finished tasks to `docs/agent-workflow/tasks/<slug>/`.
+
+## Artifact manifest and receipts
+
+Each slug stores one context index at `.claude/team/tasks/<slug>/artifact-manifest.json`. Schema v1 is defined by shared core `agent-team/agent-artifact-contracts.md`: every entry declares its producer, status, authoritative paths, acceptance-criteria IDs, decomposition task IDs, timestamps, and a terminal completion receipt.
+
+Producer/consumer rules:
+
+- Read the manifest first and use only the authoritative inputs needed by the current step; fall back to `brief.md`, `decomposition.md`, and `pipeline.json` when it is missing or stale, and report that gap.
+- Producers upsert only their stable entry IDs, preserve foreign entries, and finish with `completed`, `blocked`, `changes_requested`, or `validation_failed` receipt evidence.
+- The router owns `pipeline.json` and its routing entry; analyst, developer, verifier, and reviewer own their named outputs and receipts. Consumers do not edit another producer's receipt.
+- Agents do not mutate `status.json` or `metrics.json`. The orchestration runtime/hook is their single writer. Parallel receipt merges are serialized by the parent/orchestrator.
+
+## Local metrics ledger
+
+`metrics.json` is an append-only schema-v1 event ledger for one task run. It contains only allowlisted IDs, task dimensions, timestamps, outcomes, and attribution confidence—never prompts, secrets, file paths, or contents. Policy SoT: `presets/_shared/core/agent-team/agent-task-metrics.md`. The orchestration runtime writes `task_started` / `attempt_started`; the hook records host-clock completion and human-gate edges under a per-task lock with temp-and-rename.
+
+`status.json.activeAttempts` is a transient timing bridge keyed by `attemptId`; `lastCompletedAttempt` is diagnostic; `parallelOutcomes` holds per-agent outcomes for the current parallel join until the step advances. For parallel stops, the hook must use a stable payload identity or the sole active attempt. Otherwise an explicit `.metrics-receipts.json` receipt is fallback data marked `source: agent`, `attributionConfidence: fallback`; it must never guess from `currentAgent`.
+
+After a human gate, `/task-continue` closes wait via the installed hook (do not hand-edit `pipelineIndex` first):
+
+```bash
+printf '%s\n' '{"status":"completed","action":"end_human_gate","activateNext":true}' | bash .claude/hooks/chain-team-phases.sh
+```
+
+That appends `human_gate_ended` before the next `attempt_started`. Cursor twin uses the same payload against `.cursor/hooks/chain-team-phases.sh`. Other installable stacks ship the same ledger contract in their `team/README.md`.
+
+Aggregate with `node packages/ai-rules/scripts/aggregate-agent-task-metrics.mjs --team-root .claude/team`. It reports role/agent count, completed count, total/average duration, distinct completed run IDs, separate human-gate wait, and incomplete artifacts. For retros, see `/technical-retro` → **Metrics evidence**.

package/presets/claude/svelte/team/conventions.md

@@ -0,0 +1,21 @@
+# Living conventions (team)
+
+Consumer-owned store for post-init gotchas, patterns, and decisions. **Not** always-on. Fill after `ai-rules init`. Root `AGENTS.md` only points here.
+
+## Gotchas
+
+<!-- e.g. fragile flows, “never do X in this repo” -->
+
+-
+
+## Patterns
+
+<!-- local patterns beyond reference-features table -->
+
+-
+
+## Decisions
+
+<!-- short pointers to ADRs / product choices that affect code -->
+
+-

package/presets/claude/svelte/team/fixtures/artifact-manifest.example.json

@@ -0,0 +1,61 @@
+{
+  "schemaVersion": 1,
+  "slug": "order-history-date-filter",
+  "updatedAt": "2026-07-31T12:20:00.000Z",
+  "artifacts": [
+    {
+      "id": "routing",
+      "producer": "task-router",
+      "status": "completed",
+      "authoritativePaths": ["pipeline.json"],
+      "acceptanceCriteriaIds": [],
+      "taskIds": [],
+      "timestamps": {
+        "createdAt": "2026-07-31T12:00:00.000Z",
+        "updatedAt": "2026-07-31T12:00:00.000Z",
+        "completedAt": "2026-07-31T12:00:00.000Z"
+      },
+      "receipt": {
+        "outcome": "completed",
+        "summary": "The feature pipeline and routing evidence are authoritative.",
+        "evidencePaths": ["pipeline.json"]
+      }
+    },
+    {
+      "id": "analysis",
+      "producer": "task-analyst",
+      "status": "completed",
+      "authoritativePaths": ["brief.md", "decomposition.md"],
+      "acceptanceCriteriaIds": ["AC-1", "AC-2"],
+      "taskIds": ["T1", "T2"],
+      "timestamps": {
+        "createdAt": "2026-07-31T12:01:00.000Z",
+        "updatedAt": "2026-07-31T12:05:00.000Z",
+        "completedAt": "2026-07-31T12:05:00.000Z"
+      },
+      "receipt": {
+        "outcome": "completed",
+        "summary": "The acceptance criteria and implementation tasks are ready.",
+        "evidencePaths": ["brief.md", "decomposition.md"]
+      }
+    },
+    {
+      "id": "implementation",
+      "producer": "feature-developer",
+      "status": "completed",
+      "authoritativePaths": ["implementation.md"],
+      "acceptanceCriteriaIds": ["AC-1", "AC-2"],
+      "taskIds": ["T1", "T2"],
+      "timestamps": {
+        "createdAt": "2026-07-31T12:06:00.000Z",
+        "updatedAt": "2026-07-31T12:20:00.000Z",
+        "completedAt": "2026-07-31T12:20:00.000Z"
+      },
+      "receipt": {
+        "outcome": "completed",
+        "summary": "Implementation and focused unit coverage are complete.",
+        "evidencePaths": ["implementation.md"]
+      }
+    }
+  ]
+}

package/presets/claude/svelte/team/fixtures/bugfix-standard.json

@@ -0,0 +1,25 @@
+{
+  "slug": "example-bugfix-standard",
+  "intent": "bugfix",
+  "profile": "standard",
+  "routingDecision": {
+    "complexity": "moderate",
+    "riskFlags": ["behavior-regression"],
+    "routingReasons": [
+      "The regression needs root-cause evidence before deciding whether a separate fix pass is necessary.",
+      "The bounded behavior change still requires validation and independent review."
+    ],
+    "estimatedWorkPackages": 1,
+    "openDecisionCount": 0
+  },
+  "summary": "Regression fix with review",
+  "steps": [
+    { "agent": "debugger", "label": "Root cause" },
+    { "agent": "feature-developer", "label": "Fix if needed", "skipIf": "debugger.fixed" },
+    { "agent": "build-verifier", "label": "Validation gate" },
+    { "agent": "code-reviewer", "label": "Code review" }
+  ],
+  "humanGates": [],
+  "autoChain": true,
+  "skipped": []
+}

package/presets/claude/svelte/team/fixtures/feature-full.json

@@ -0,0 +1,28 @@
+{
+  "slug": "example-feature-full",
+  "intent": "feature",
+  "profile": "full",
+  "routingDecision": {
+    "complexity": "high",
+    "riskFlags": ["cross-layer", "public-contract", "broad-test-surface"],
+    "routingReasons": [
+      "The feature spans UI, state, and API boundaries, so architecture and implementation checkpoints are required.",
+      "The public contract and e2e acceptance surface require independent validation and review."
+    ],
+    "estimatedWorkPackages": 2,
+    "openDecisionCount": 1
+  },
+  "summary": "Multi-layer feature with e2e coverage",
+  "steps": [
+    { "agent": "task-analyst", "label": "Clarify and decompose" },
+    { "agent": "solution-architect", "label": "Design boundaries", "model": "strong" },
+    { "agent": "feature-developer", "label": "Implement + unit tests", "scope": "unit-in-dev" },
+    { "agent": "build-verifier", "label": "Validation gate", "model": "cheap" },
+    { "agent": "security-reviewer", "label": "Security review", "model": "strong" },
+    { "agent": "code-reviewer", "label": "Code review", "model": "cheap" },
+    { "agent": "qa-tester", "label": "E2E", "scope": "e2e-only" }
+  ],
+  "humanGates": ["after:task-analyst"],
+  "autoChain": true,
+  "skipped": []
+}

package/presets/claude/svelte/team/fixtures/feature-light.json

@@ -0,0 +1,27 @@
+{
+  "slug": "example-feature-light",
+  "intent": "feature",
+  "profile": "light",
+  "routingDecision": {
+    "complexity": "low",
+    "riskFlags": [],
+    "routingReasons": [
+      "The request has explicit acceptance criteria and a reversible single-file scope.",
+      "No public contract, cross-layer coordination, or open decision requires analysis or architecture."
+    ],
+    "estimatedWorkPackages": 1,
+    "openDecisionCount": 0
+  },
+  "summary": "Trivial single-file change with explicit AC",
+  "steps": [
+    { "agent": "feature-developer", "label": "Implement", "model": "cheap" },
+    { "agent": "build-verifier", "label": "Validation gate", "model": "cheap" }
+  ],
+  "humanGates": [],
+  "autoChain": true,
+  "skipped": [
+    { "agent": "task-analyst", "reason": "Explicit AC and single-file scope" },
+    { "agent": "code-reviewer", "reason": "Light profile — non-trivial app changes should use standard" },
+    { "agent": "qa-tester", "reason": "No e2e AC" }
+  ]
+}

package/presets/claude/svelte/team/tasks/.gitkeep

@@ -0,0 +1 @@
+# Keep the task artifact directory in the published preset.

package/presets/cursor/go/agents/build-verifier.md

@@ -13,7 +13,7 @@ You are the build verifier for **Go hexagonal** services (and for **ai-rules pre
 2. If present: `golangci-lint` / `staticcheck` per repo docs (`go-tooling`, `post-change-test`).
 3. Optional `-race` when concurrency touched.
 4. Write `.cursor/team/tasks/<slug>/validation-report.md` with commands + results.
-5. On failure: set status `validation_failed` — do **not** patch production code (developer retries).
+5. On failure: emit receipt outcome `validation_failed` — do **not** patch production code (developer retries).
 
 **Never** require Playwright, XCUITest, `lint:js`/`lint:css`, or `xcodebuild`/`SwiftLint` as the Go gate.
 
@@ -29,7 +29,14 @@ Hard gates: twin-map (stacks include **go**), token-budget (alwaysApply/session-
 
 Document PASS/FAIL in `validation-report.md`.
 
-1. **Root AGENTS template:** each installable preset (`cursor|claude` × `next|ios-swift|go|java|mcp-ts|php-hexagonal`) must ship `REPO_AGENTS.md` when validating preset packaging → **FAIL** if missing.
+1. **Root AGENTS template:** each installable preset (`cursor|claude` × `next|nuxt|svelte|ios-swift|go|java|mcp-ts|php-hexagonal|php-laravel`) must ship `REPO_AGENTS.md` when validating preset packaging → **FAIL** if missing.
 2. **Hooks cookbook:** default `hooks.json` must **not** reference `hooks/examples/` → **FAIL** if it does.
 3. **No react-performance on ios/go/java:** skill directory / required handoff must be absent under ios-swift, go, java, mcp-ts, php-hexagonal, and php-laravel → **FAIL** (leakage). Prefer `check:preset-leakage`.
 4. **Rule eval (WARN):** `scripts/check-rule-eval.mjs` / `yarn check:rule-eval` should exist for maintainers; smoke optional. Hard fail only when the opt-in eval job runs — not part of default `check:preset-structure`.
+
+## Artifact contract
+
+- **Authoritative inputs:** read `.cursor/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.
+- **Owned outputs:** `validation-report.md`; upsert only the manifest entry assigned by handoff (`artifactOutputId`; fallback `validation`) and preserve all foreign entries.
+- **Terminal receipt:** cover applicable AC/task IDs, list authoritative evidence paths, and emit `completed` or `validation_failed`. 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.

package/presets/cursor/go/agents/code-reviewer.md

@@ -33,8 +33,15 @@ Apply skill `code-review` and `code-review-mr.mdc`. Weigh `architecture-boundari
 
 ## Artifact
 
-Write `.cursor/team/tasks/<slug>/review.md` with verdict APPROVE | REQUEST_CHANGES, findings by severity, AC coverage. Update `status.json` accordingly.
+Write `.cursor/team/tasks/<slug>/review.md` with verdict APPROVE | REQUEST_CHANGES, findings by severity, AC coverage. Update the owned terminal receipt accordingly.
 
 ## Design guidance
 
 - Load `design-guidance` (rule stem) when assessing structure, smells, or pattern fit.
+
+## Artifact contract
+
+- **Authoritative inputs:** read `.cursor/team/tasks/<slug>/artifact-manifest.json` first; consume handoff `artifactInputIds` when supplied, otherwise consume the manifest entries for brief/decomposition, implementation, validation evidence, and the scoped git diff.
+- **Owned outputs:** `review.md`; upsert only the manifest entry assigned by handoff (`artifactOutputId`; fallback `review`) and preserve all foreign entries.
+- **Terminal receipt:** cover applicable AC/task IDs, list authoritative evidence paths, and emit `completed` or `changes_requested`. 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.

package/presets/cursor/go/agents/feature-developer.md

@@ -36,7 +36,7 @@ Implement Go features following hexagonal boundaries.
 
 When editing ai-rules `presets/**/go/**`, keep Cursor/Claude twins in sync and preserve chain fork ≠ next/ios-swift.
 
-Update `.cursor/team/tasks/<slug>/implementation.md` and `status.json`.
+Update `.cursor/team/tasks/<slug>/implementation.md` and the owned implementation receipt.
 
 ## Design guidance
 
@@ -45,3 +45,10 @@ Update `.cursor/team/tasks/<slug>/implementation.md` and `status.json`.
 ## Anti-sycophancy discipline
 
 - When writing or changing code, load / follow rule `anti-sycophancy-discipline`.
+
+## Artifact contract
+
+- **Authoritative inputs:** read `.cursor/team/tasks/<slug>/artifact-manifest.json` first; consume handoff `artifactInputIds` when supplied, otherwise consume the manifest entries for `brief.md`, `decomposition.md`, current scope, and applicable prior findings.
+- **Owned outputs:** `implementation.md` plus changed implementation/test paths; upsert only the manifest entry assigned by handoff (`artifactOutputId`; fallback `implementation`) and preserve all foreign entries.
+- **Terminal receipt:** cover applicable AC/task IDs, list authoritative evidence paths, 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.

package/presets/cursor/go/agents/task-analyst.md

@@ -18,8 +18,15 @@ Use domain, application/ports, driving/driven adapters, composition root — not
 
 ## Gates
 
-Set `awaiting_approval` when humanGates require it after analysis.
+Emit an analysis receipt; the runtime applies any configured human gate.
 
 ## Design guidance (optional)
 
 - Optional: Load `design-guidance` (rule stem) when assessing structure, smells, or pattern fit — only when decomposing refactor/architecture tasks (not default).
+
+## Artifact contract
+
+- **Authoritative inputs:** read `.cursor/team/tasks/<slug>/artifact-manifest.json` first; consume `pipeline.json`, the manifest routing entry, user-approved decisions, and any authoritative architecture/approval entries.
+- **Owned outputs:** `brief.md` and `decomposition.md`; upsert only the manifest entry assigned by handoff (`artifactOutputId`; fallback `analysis`) and preserve all foreign entries.
+- **Terminal receipt:** cover applicable AC/task IDs, list authoritative evidence paths, 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.

package/presets/cursor/go/agents/task-router.md

@@ -39,6 +39,27 @@ You are a task router for a **Go hexagonal backend** agent team. You **do not**
 
 **Never skip `build-verifier`** after developer when Go sources changed.
 
+## Routing decision rubric
+
+Keep top-level `profile` and emit this top-level object in every new `pipeline.json`:
+
+```json
+"routingDecision": {
+  "complexity": "low | moderate | high",
+  "riskFlags": [],
+  "routingReasons": ["Concrete request signal and its routing consequence."],
+  "estimatedWorkPackages": 1,
+  "openDecisionCount": 0
+}
+```
+
+- `low`: one bounded layer/file set, explicit AC, reversible, no risk flags/open decisions → `light` when verification policy permits.
+- `moderate`: adjacent concerns or a regression/refactor with known boundaries → usually `standard`.
+- `high`: cross-layer/public contract, security, migration/destructive or concurrency/state risk, broad integration-test surface, unclear AC, or multiple work packages → usually `full`.
+- Use concrete flags: `public-contract`, `cross-layer`, `security-sensitive`, `migration`, `destructive`, `concurrency-state`, `external-dependency`, `unclear-acceptance-criteria`, `broad-test-surface`, `behavior-regression`.
+- `routingReasons` must be non-empty and explain profile, gates, specialists, skips, or checkpoints; never write “standard by default.”
+- `estimatedWorkPackages` is an integer ≥1; `openDecisionCount` is an integer ≥0. Do not lower complexity because implementation is familiar.
+
 ## Model tiers (`steps[].model`)
 
 Optional: `"model": "cheap" | "standard" | "strong"`. Same policy as other presets:
@@ -62,12 +83,19 @@ Fixtures: `.cursor/team/fixtures/` (feature-full, feature-light, bugfix-standard
 
 ## Output
 
-Write `.cursor/team/tasks/<slug>/pipeline.json` and initial `status.json` via the **Write** tool (creates parents; do not Shell-`mkdir`); set `.cursor/team/active-task.json`.
+Write `.cursor/team/tasks/<slug>/pipeline.json` and initialize the routing entry in `artifact-manifest.json`; set `.cursor/team/active-task.json`. The orchestration runtime creates and owns `status.json`.
 
 ## Handoff
 
 Intent + steps table + skipped + gates → invoke `steps[0].agent` (unless retro).
 
-## Metrics initialization
+## Runtime initialization
+
+Return the routing receipt to the orchestrator. The orchestration runtime/hook exclusively initializes and updates `status.json`, `metrics.json`, attempt identities, and gate lifecycle; the router does not write those shared runtime files.
+
+## Artifact contract
 
-Alongside `pipeline.json` and `status.json`, create `metrics.json` with `schemaVersion: 1`, immutable task dimensions, `task_started`, and a generated `runId`. Before the parent invokes each agent, append `attempt_started` and set `status.activeAttempts[attemptId]` with agent, step index, attempt number, and host-clock `startedAt`. For parallel work create one entry per agent; do not use `currentAgent` to identify their completion.
+- **Authoritative inputs:** read `.cursor/team/tasks/<slug>/artifact-manifest.json` first; consume the user request and any existing authoritative task/decision entries.
+- **Owned outputs:** `pipeline.json` and the routing manifest entry; upsert only the manifest entry assigned by handoff (`artifactOutputId`; fallback `routing`) and preserve all foreign entries.
+- **Terminal receipt:** cover applicable AC/task IDs, list authoritative evidence paths, 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.