agent-templates 0.1.0 → 0.2.0

package/scripts/cli.mjs

@@ -1,52 +1,52 @@
-#!/usr/bin/env node
-// agent-templates CLI — the npx entry point (package.json "bin").
-// Dispatches to the catalog tooling; carries no logic of its own.
-//
-//   agent-templates list                                      show available patterns
-//   agent-templates adopt <pattern> <target-dir> [options]    install a pattern (see adopt.mjs)
-//
-// Without cloning the catalog:
-//   npx github:Ruihang2017/agent-templates list
-//   npx github:Ruihang2017/agent-templates adopt three-agent-architect-builder-reviewer .
-
-import { spawnSync } from 'node:child_process'
-import { existsSync, readdirSync } from 'node:fs'
-import { join } from 'node:path'
-import { fileURLToPath } from 'node:url'
-
-const ROOT = fileURLToPath(new URL('..', import.meta.url))
-const [cmd, ...rest] = process.argv.slice(2)
-
-if (cmd === 'adopt') {
-  const r = spawnSync(process.execPath, [join(ROOT, 'scripts', 'adopt.mjs'), ...rest], { stdio: 'inherit' })
-  process.exit(r.status === null ? 1 : r.status)
-}
-
-if (cmd === 'list') {
-  const dir = join(ROOT, 'patterns')
-  const patterns = existsSync(dir)
-    ? readdirSync(dir, { withFileTypes: true })
-        .filter((d) => d.isDirectory() && existsSync(join(dir, d.name, 'scaffold')))
-        .map((d) => d.name)
-    : []
-  console.log(patterns.length ? patterns.join('\n') : '(no patterns found)')
-  process.exit(0)
-}
-
-const usage = `agent-templates — multi-agent pattern catalog
-
-usage:
-  agent-templates list
-  agent-templates adopt <pattern> <target-dir> [--platform gh|glab] [--force]
-
-without cloning:
-  npx github:Ruihang2017/agent-templates list
-  npx github:Ruihang2017/agent-templates adopt three-agent-architect-builder-reviewer .
-
-docs: ADOPTING.md in the catalog root`
-if (!cmd) {
-  console.log(usage)
-  process.exit(0)
-}
-console.error(`unknown command: ${cmd}\n\n${usage}`)
-process.exit(1)
+#!/usr/bin/env node
+// agent-templates CLI — the npx entry point (package.json "bin").
+// Dispatches to the catalog tooling; carries no logic of its own.
+//
+//   agent-templates list                                      show available patterns
+//   agent-templates adopt <pattern> <target-dir> [options]    install a pattern (see adopt.mjs)
+//
+// Without cloning the catalog:
+//   npx github:Ruihang2017/agent-templates list
+//   npx github:Ruihang2017/agent-templates adopt three-agent-architect-builder-reviewer .
+
+import { spawnSync } from 'node:child_process'
+import { existsSync, readdirSync } from 'node:fs'
+import { join } from 'node:path'
+import { fileURLToPath } from 'node:url'
+
+const ROOT = fileURLToPath(new URL('..', import.meta.url))
+const [cmd, ...rest] = process.argv.slice(2)
+
+if (cmd === 'adopt') {
+  const r = spawnSync(process.execPath, [join(ROOT, 'scripts', 'adopt.mjs'), ...rest], { stdio: 'inherit' })
+  process.exit(r.status === null ? 1 : r.status)
+}
+
+if (cmd === 'list') {
+  const dir = join(ROOT, 'patterns')
+  const patterns = existsSync(dir)
+    ? readdirSync(dir, { withFileTypes: true })
+        .filter((d) => d.isDirectory() && existsSync(join(dir, d.name, 'scaffold')))
+        .map((d) => d.name)
+    : []
+  console.log(patterns.length ? patterns.join('\n') : '(no patterns found)')
+  process.exit(0)
+}
+
+const usage = `agent-templates — multi-agent pattern catalog
+
+usage:
+  agent-templates list
+  agent-templates adopt <pattern> <target-dir> [--platform gh|glab] [--force]
+
+without cloning:
+  npx github:Ruihang2017/agent-templates list
+  npx github:Ruihang2017/agent-templates adopt three-agent-architect-builder-reviewer .
+
+docs: ADOPTING.md in the catalog root`
+if (!cmd) {
+  console.log(usage)
+  process.exit(0)
+}
+console.error(`unknown command: ${cmd}\n\n${usage}`)
+process.exit(1)

package/templates/pattern-README.template.md

@@ -1,65 +1,65 @@
-# Pattern: <Human-Readable Pattern Name>
-
-<!-- Copy this file to patterns/<kebab-name>/README.md and fill EVERY section.
-     Format reference: patterns/three-agent-architect-builder-reviewer/README.md
-     Rules: CLAUDE.md "Grounding rules" — every model/effort claim carries a source label;
-     no training-data impressions; as-of date moves with every recommendation change. -->
-
-| Field | Value |
-|---|---|
-| **Pattern name** | `<kebab-name>` (= directory name) |
-| **Status** | `proposed` <!-- proposed → trialed → adopted → deprecated --> |
-| **As-of date** | YYYY-MM-DD |
-| **Expiry trigger** | First successor release to any listed model, or YYYY-MM-DD (+6 months), whichever comes first |
-| **Sign-off** | <name, role, date> |
-
-<One- or two-sentence summary of the agent topology: who does what, in what order.>
-
-## 1. When to use / when not to use
-
-**Use when:**
-- <concrete task shape>
-
-**Do not use when:**
-- <concrete task shape — every pattern has a floor below which its overhead dominates>
-
-## 2. Agent roles & boundaries
-
-| Agent | Does | Never does |
-|---|---|---|
-| **<Role>** | <responsibility> | <hard boundary> |
-
-<Who judges whom; which contexts must stay isolated; which boundaries are hard requirements vs tunable.
-State which agent owns unit / integration / E2E tests — agents own all three levels (repo testing policy);
-the human only smoke-tests at PRD completion.>
-
-## 3. Model + effort assignment (as of YYYY-MM-DD)
-
-| Role | Model | Effort | Reasoning | Source labels |
-|---|---|---|---|---|
-| <Role> | <exact model name> | <effort level> | <why this model/effort for this role> | <`[official]` / `[vendor-benchmark]` / `[third-party]` / `[internal]` / `[unverified]` / `[team-policy]` + link or "link not captured — attach at first re-verification"> |
-
-## 4. Known failure modes / pitfalls
-
-| Pitfall | Context | Mitigation | Recorded |
-|---|---|---|---|
-| <symptom> | <the specific harness/project/conditions it was observed in — or "design constraint (not a measured incident)"> | <mitigation> | YYYY-MM-DD |
-| Harness-specific failures for these exact model+effort combinations | **None recorded yet** (as of YYYY-MM-DD) | Record here with harness name, conditions, and date when observed | — |
-
-## 5. Upstream / downstream integration
-
-**Upstream (work intake):** <how work enters — master PRD → sub-PRD → ticket; which docs each agent reads; where ADRs come in.>
-
-**Downstream (deliverables):** <what leaves — PR, verdict, docs; what gates a merge.>
-
-**Human gates:** <where humans decide (e.g. the start signal), where they must NOT be needed, and the exception path that pulls a human back in.>
-
-## 6. Scaffold
-
-<List of files under scaffold/ and what each is for. Point to scaffold/INSTALL.md for install steps. Note the date the scaffold's config keys were last verified against Claude Code docs.>
-
-## 7. Provenance & change log
-
-| Date | Change | Basis | Author |
-|---|---|---|---|
-| YYYY-MM-DD | Initial entry | <source record / doc links> | <who> |
+# Pattern: <Human-Readable Pattern Name>
+
+<!-- Copy this file to patterns/<kebab-name>/README.md and fill EVERY section.
+     Format reference: patterns/three-agent-architect-builder-reviewer/README.md
+     Rules: CLAUDE.md "Grounding rules" — every model/effort claim carries a source label;
+     no training-data impressions; as-of date moves with every recommendation change. -->
+
+| Field | Value |
+|---|---|
+| **Pattern name** | `<kebab-name>` (= directory name) |
+| **Status** | `proposed` <!-- proposed → trialed → adopted → deprecated --> |
+| **As-of date** | YYYY-MM-DD |
+| **Expiry trigger** | First successor release to any listed model, or YYYY-MM-DD (+6 months), whichever comes first |
+| **Sign-off** | <name, role, date> |
+
+<One- or two-sentence summary of the agent topology: who does what, in what order.>
+
+## 1. When to use / when not to use
+
+**Use when:**
+- <concrete task shape>
+
+**Do not use when:**
+- <concrete task shape — every pattern has a floor below which its overhead dominates>
+
+## 2. Agent roles & boundaries
+
+| Agent | Does | Never does |
+|---|---|---|
+| **<Role>** | <responsibility> | <hard boundary> |
+
+<Who judges whom; which contexts must stay isolated; which boundaries are hard requirements vs tunable.
+State which agent owns unit / integration / E2E tests — agents own all three levels (repo testing policy);
+the human only smoke-tests at PRD completion.>
+
+## 3. Model + effort assignment (as of YYYY-MM-DD)
+
+| Role | Model | Effort | Reasoning | Source labels |
+|---|---|---|---|---|
+| <Role> | <exact model name> | <effort level> | <why this model/effort for this role> | <`[official]` / `[vendor-benchmark]` / `[third-party]` / `[internal]` / `[unverified]` / `[team-policy]` + link or "link not captured — attach at first re-verification"> |
+
+## 4. Known failure modes / pitfalls
+
+| Pitfall | Context | Mitigation | Recorded |
+|---|---|---|---|
+| <symptom> | <the specific harness/project/conditions it was observed in — or "design constraint (not a measured incident)"> | <mitigation> | YYYY-MM-DD |
+| Harness-specific failures for these exact model+effort combinations | **None recorded yet** (as of YYYY-MM-DD) | Record here with harness name, conditions, and date when observed | — |
+
+## 5. Upstream / downstream integration
+
+**Upstream (work intake):** <how work enters — master PRD → sub-PRD → ticket; which docs each agent reads; where ADRs come in.>
+
+**Downstream (deliverables):** <what leaves — PR, verdict, docs; what gates a merge.>
+
+**Human gates:** <where humans decide (e.g. the start signal), where they must NOT be needed, and the exception path that pulls a human back in.>
+
+## 6. Scaffold
+
+<List of files under scaffold/ and what each is for. Point to scaffold/INSTALL.md for install steps. Note the date the scaffold's config keys were last verified against Claude Code docs.>
+
+## 7. Provenance & change log
+
+| Date | Change | Basis | Author |
+|---|---|---|---|
+| YYYY-MM-DD | Initial entry | <source record / doc links> | <who> |

package/templates/ticket.template.md

@@ -1,104 +1,104 @@
-<!-- Universal ticket template — all patterns, plus the catalog repo itself.
-     Format distilled 2026-07-17 from the team's field-proven tickets: fx-eye-tracking
-     discipline, realtime-pilot PIL-15, MeritAI FND-9.
-     Copy to docs/prd/<NN-module>/tickets/<ID>-<slug>.md and fill every section.
-     Cold-start rule: a ticket is DEFECTIVE if executing it requires the planning
-     conversation. Inline the needed facts AND link their authoritative source.
-     The body below the frontmatter becomes the tracker issue body verbatim
-     (.claude/scripts/publish-tickets.mjs); the file stays the content source of truth. -->
----
-id: MOD-NN            # unique + stable; becomes the issue-title prefix "[MOD-NN]" (the dedupe key)
-title: Short imperative title
-module: NN-module     # = parent directory name under docs/prd/
-lane: NN-module       # parallel lane; lanes may run concurrently ONLY with disjoint file-scopes
-size: S               # S | M | L
-agent: builder        # primary executing stage; justify in the "Why" line below
-status: draft         # draft -> ready -> done
-date: YYYY-MM-DD
-blocked_by: []        # ticket ids this one cannot start before (machine-readable dependency DAG)
-blocks: []            # ticket ids waiting on this one
----
-
-# MOD-NN — Short imperative title
-
-Implements <PRD §X FR-Y> per <ADR-NNNN (status, owner, date, via PR #N)> — or: "No ADR —
-the decision is already made in <ref>; this is build ticket <n of m> against it."
-Parent sub-PRD: [NN-module README](../README.md). Master spec: [PRD](../../../PRD.md).
-Depends on: [MOD-NM — other ticket](MOD-NM-other-ticket.md) <!-- mirrors blocked_by; delete if none -->
-**Why `builder`:** <one line — the basis for the agent assignment, e.g. "a narrowly-scoped
-addition to an existing module, not a new subsystem">.
-
-## Background + basis
-
-<!-- Why this ticket exists. CITE every claim: PRD §, ADR section, stable decision ID, or a
-     merged PR — a conclusion may not appear from nowhere. QUOTE the load-bearing sentences
-     of the ADR/spec so the Builder does not re-derive intent.
-     Carry known caveats forward EXPLICITLY ("accepted for the pilot: X — documented, not
-     enforced, per PRD §Y") instead of re-litigating or silently dropping them. -->
-
-## Goal
-
-<!-- One paragraph: the artifact(s)/behavior to produce and where they land — stated so
-     completion is mechanically checkable. -->
-
-## Non-goals
-
-<!-- Bullet list. EACH exclusion names its owner or standing reason, so nobody guesses:
-     - No schema files — those are MOD-02.
-     - No init authentication — stays documented-not-enforced per PRD §9.4. Do not add it
-       as a side effect of this ticket. -->
-
-## File-scope (write-owns)
-
-<!-- Exact paths/globs this ticket may write, PLUS the explicit does-not-touch list.
-     State the serial-safety analysis: which tickets last touched these files, whether that
-     work is merged, and that no in-flight ticket contends for them. Must not overlap any
-     other in-flight ticket — disjoint file-scopes are what make parallel lanes safe.
-     Internal organization inside the scope is the Builder's choice. -->
-
-- <paths this ticket owns>
-- Does not touch: <paths owned elsewhere — name the owning ticket/module>
-
-## Deliverables
-
-<!-- Numbered, code-level precision: exact functions/exports, call sites, ordering
-     constraints ("directly after X and before Y"), naming conventions, and the behavioral
-     guarantee ("either fully visible or fully absent"). Fix the boundary AND the
-     load-bearing mechanics; leave internals free. -->
-
-1. <deliverable>
-
-## Acceptance checklist (classified)
-
-<!-- Every criterion is a checkbox with exactly one class tag. The tag VOCABULARY is
-     project-defined in the target repo's CLAUDE.md — defaults: [machine] runnable
-     code/logic check · [fixture] replay of recorded data · [human] irreducibly human
-     judgment. Field vocabularies in use: [offline]/[live-model] (realtime pilot),
-     [machine]/[fixture]/[hardware-human] (fx-eye-tracking).
-     Rules: cover the pyramid where applicable — unit / integration / E2E; agents own all
-     three levels, the human only smoke-tests at PRD completion. Include the standing
-     suite-green item. If the ticket must conclude an open question, make the WRITEBACK
-     itself an acceptance item. Mark optional orchestrator-owned live checks "not required
-     to merge". Declare absent classes explicitly ("No [human] criteria — pure logic"). -->
-
-- [ ] `[machine]` <criterion> (<cross-ref to AC/decision id>)
-- [ ] `[machine]` <project test-suite command> green
-
-## Test plan
-
-<!-- The exact steps the Reviewer runs. NAME the harness/mocks/fixtures and the existing
-     test file whose construction pattern to copy. Say what is asserted, on what. Every
-     [machine]/[fixture] row must be reproducible offline. -->
-
-## Feedback obligation
-
-<!-- The writeback protocol, made concrete — three layers:
-     1. General rule: if implementation falsifies this spec, update this ticket / the
-        sub-PRD / the ADR first (version +0.1, changelog line), then change code. Silent
-        divergence = incomplete.
-     2. ENUMERATE the foreseeable frictions, each with its exact writeback target and path:
-        "if X cannot be expressed as Y → update docs/design-Z.md and ADR-NNNN's
-        consequences section FIRST, before touching src/W — a bigger surface than this
-        ticket's goal must not change silently."
-     3. If a decided protocol is outright falsified: that overturns a team decision —
-        escalate for re-review; never swap the approach silently inside the ticket. -->
+<!-- Universal ticket template — all patterns, plus the catalog repo itself.
+     Format distilled 2026-07-17 from the team's field-proven tickets: fx-eye-tracking
+     discipline, realtime-pilot PIL-15, MeritAI FND-9.
+     Copy to docs/prd/<NN-module>/tickets/<ID>-<slug>.md and fill every section.
+     Cold-start rule: a ticket is DEFECTIVE if executing it requires the planning
+     conversation. Inline the needed facts AND link their authoritative source.
+     The body below the frontmatter becomes the tracker issue body verbatim
+     (.claude/scripts/publish-tickets.mjs); the file stays the content source of truth. -->
+---
+id: MOD-NN            # unique + stable; becomes the issue-title prefix "[MOD-NN]" (the dedupe key)
+title: Short imperative title
+module: NN-module     # = parent directory name under docs/prd/
+lane: NN-module       # parallel lane; lanes may run concurrently ONLY with disjoint file-scopes
+size: S               # S | M | L
+agent: builder        # primary executing stage; justify in the "Why" line below
+status: draft         # draft -> ready -> done
+date: YYYY-MM-DD
+blocked_by: []        # ticket ids this one cannot start before (machine-readable dependency DAG)
+blocks: []            # ticket ids waiting on this one
+---
+
+# MOD-NN — Short imperative title
+
+Implements <PRD §X FR-Y> per <ADR-NNNN (status, owner, date, via PR #N)> — or: "No ADR —
+the decision is already made in <ref>; this is build ticket <n of m> against it."
+Parent sub-PRD: [NN-module README](../README.md). Master spec: [PRD](../../../PRD.md).
+Depends on: [MOD-NM — other ticket](MOD-NM-other-ticket.md) <!-- mirrors blocked_by; delete if none -->
+**Why `builder`:** <one line — the basis for the agent assignment, e.g. "a narrowly-scoped
+addition to an existing module, not a new subsystem">.
+
+## Background + basis
+
+<!-- Why this ticket exists. CITE every claim: PRD §, ADR section, stable decision ID, or a
+     merged PR — a conclusion may not appear from nowhere. QUOTE the load-bearing sentences
+     of the ADR/spec so the Builder does not re-derive intent.
+     Carry known caveats forward EXPLICITLY ("accepted for the pilot: X — documented, not
+     enforced, per PRD §Y") instead of re-litigating or silently dropping them. -->
+
+## Goal
+
+<!-- One paragraph: the artifact(s)/behavior to produce and where they land — stated so
+     completion is mechanically checkable. -->
+
+## Non-goals
+
+<!-- Bullet list. EACH exclusion names its owner or standing reason, so nobody guesses:
+     - No schema files — those are MOD-02.
+     - No init authentication — stays documented-not-enforced per PRD §9.4. Do not add it
+       as a side effect of this ticket. -->
+
+## File-scope (write-owns)
+
+<!-- Exact paths/globs this ticket may write, PLUS the explicit does-not-touch list.
+     State the serial-safety analysis: which tickets last touched these files, whether that
+     work is merged, and that no in-flight ticket contends for them. Must not overlap any
+     other in-flight ticket — disjoint file-scopes are what make parallel lanes safe.
+     Internal organization inside the scope is the Builder's choice. -->
+
+- <paths this ticket owns>
+- Does not touch: <paths owned elsewhere — name the owning ticket/module>
+
+## Deliverables
+
+<!-- Numbered, code-level precision: exact functions/exports, call sites, ordering
+     constraints ("directly after X and before Y"), naming conventions, and the behavioral
+     guarantee ("either fully visible or fully absent"). Fix the boundary AND the
+     load-bearing mechanics; leave internals free. -->
+
+1. <deliverable>
+
+## Acceptance checklist (classified)
+
+<!-- Every criterion is a checkbox with exactly one class tag. The tag VOCABULARY is
+     project-defined in the target repo's CLAUDE.md — defaults: [machine] runnable
+     code/logic check · [fixture] replay of recorded data · [human] irreducibly human
+     judgment. Field vocabularies in use: [offline]/[live-model] (realtime pilot),
+     [machine]/[fixture]/[hardware-human] (fx-eye-tracking).
+     Rules: cover the pyramid where applicable — unit / integration / E2E; agents own all
+     three levels, the human only smoke-tests at PRD completion. Include the standing
+     suite-green item. If the ticket must conclude an open question, make the WRITEBACK
+     itself an acceptance item. Mark optional orchestrator-owned live checks "not required
+     to merge". Declare absent classes explicitly ("No [human] criteria — pure logic"). -->
+
+- [ ] `[machine]` <criterion> (<cross-ref to AC/decision id>)
+- [ ] `[machine]` <project test-suite command> green
+
+## Test plan
+
+<!-- The exact steps the Reviewer runs. NAME the harness/mocks/fixtures and the existing
+     test file whose construction pattern to copy. Say what is asserted, on what. Every
+     [machine]/[fixture] row must be reproducible offline. -->
+
+## Feedback obligation
+
+<!-- The writeback protocol, made concrete — three layers:
+     1. General rule: if implementation falsifies this spec, update this ticket / the
+        sub-PRD / the ADR first (version +0.1, changelog line), then change code. Silent
+        divergence = incomplete.
+     2. ENUMERATE the foreseeable frictions, each with its exact writeback target and path:
+        "if X cannot be expressed as Y → update docs/design-Z.md and ADR-NNNN's
+        consequences section FIRST, before touching src/W — a bigger surface than this
+        ticket's goal must not change silently."
+     3. If a decided protocol is outright falsified: that overturns a team decision —
+        escalate for re-review; never swap the approach silently inside the ticket. -->

package/templates/tracker/github/ISSUE_TEMPLATE/bug-report.md

@@ -1,28 +1,28 @@
----
-name: Bug report
-about: Report a defect. Nightly triage reads this — the more mechanical the reproduction, the likelier an overnight fix.
-title: ''
-labels: ''
-assignees: ''
----
-
-## Symptom
-
-<!-- What happens. Paste the exact error output / wrong value. -->
-
-## Reproduction
-
-<!-- Exact steps or commands; the smallest input that triggers it. -->
-
-## Expected
-
-<!-- What should happen instead, stated checkably. Cite the spec (PRD §/ADR) if you know it. -->
-
-## Affected area (best guess)
-
-<!-- Files/modules if you know them; leave empty if unsure — triage will trace it. -->
-
-## Acceptance
-
-<!-- What proves it fixed. Ideally a runnable check, e.g. "npm test stays green and f(x) returns y".
-     The pipeline turns this into the ticket's classified acceptance checklist. -->
+---
+name: Bug report
+about: Report a defect. Nightly triage reads this — the more mechanical the reproduction, the likelier an overnight fix.
+title: ''
+labels: ''
+assignees: ''
+---
+
+## Symptom
+
+<!-- What happens. Paste the exact error output / wrong value. -->
+
+## Reproduction
+
+<!-- Exact steps or commands; the smallest input that triggers it. -->
+
+## Expected
+
+<!-- What should happen instead, stated checkably. Cite the spec (PRD §/ADR) if you know it. -->
+
+## Affected area (best guess)
+
+<!-- Files/modules if you know them; leave empty if unsure — triage will trace it. -->
+
+## Acceptance
+
+<!-- What proves it fixed. Ideally a runnable check, e.g. "npm test stays green and f(x) returns y".
+     The pipeline turns this into the ticket's classified acceptance checklist. -->

package/templates/tracker/github/ISSUE_TEMPLATE/decision-record.md

@@ -1,25 +1,25 @@
----
-name: Decision record
-about: Records what was done and why — the durable memory that commits cannot carry. Used by agents and humans alike.
-title: 'Decision record: '
-labels: decision-record
-assignees: ''
----
-
-**What** (merged in <commit/PR/MR>, YYYY-MM-DD): <one paragraph — the change as shipped.>
-
-**Key decisions & why**
-
-<!-- One bullet per decision: the decision, its reason, and the rejected alternative when
-     one was seriously considered. Cite sources — official docs, ADRs, maintainer direction
-     with date — the same grounding discipline as everything else. -->
-
--
-
-**Evidence**
-
-<!-- Test results, verification records, links to the docs where each decision landed. -->
-
-**Links**
-
-<!-- Related issues / PRs / ADRs / tickets. -->
+---
+name: Decision record
+about: Records what was done and why — the durable memory that commits cannot carry. Used by agents and humans alike.
+title: 'Decision record: '
+labels: decision-record
+assignees: ''
+---
+
+**What** (merged in <commit/PR/MR>, YYYY-MM-DD): <one paragraph — the change as shipped.>
+
+**Key decisions & why**
+
+<!-- One bullet per decision: the decision, its reason, and the rejected alternative when
+     one was seriously considered. Cite sources — official docs, ADRs, maintainer direction
+     with date — the same grounding discipline as everything else. -->
+
+-
+
+**Evidence**
+
+<!-- Test results, verification records, links to the docs where each decision landed. -->
+
+**Links**
+
+<!-- Related issues / PRs / ADRs / tickets. -->

package/templates/tracker/github/ISSUE_TEMPLATE/task.md

@@ -1,36 +1,36 @@
----
-name: Task
-about: Request a bounded piece of work. Mirrors the pipeline's ticket format so triage can convert it mechanically.
-title: ''
-labels: ''
-assignees: ''
----
-
-## Traceability
-
-<!-- What this implements or follows from: PRD §/FR, an ADR, a discussion, an upstream
-     pattern — with links. If the decision is already made somewhere, say where. -->
-
-## Background + basis
-
-<!-- Why this is needed. Cite claims; quote the load-bearing sentences rather than
-     paraphrasing from memory. -->
-
-## Goal
-
-<!-- One paragraph: the artifact(s) to produce and where they land — checkable. -->
-
-## Non-goals
-
-<!-- Each exclusion names its owner or standing reason: "No X — that is MOD-02" /
-     "No Y — stays out of scope per PRD §Z; do not add it as a side effect." -->
-
-## Affected area (best guess)
-
-<!-- Files/modules if known; the Architect finalizes the file-scope and the
-     does-not-touch list. -->
-
-## Acceptance
-
-<!-- Checkable criteria, one per line, tagged with the repo's class vocabulary if you can
-     (defaults: [machine]/[fixture]/[human]). Prefer runnable checks ("command X exits 0"). -->
+---
+name: Task
+about: Request a bounded piece of work. Mirrors the pipeline's ticket format so triage can convert it mechanically.
+title: ''
+labels: ''
+assignees: ''
+---
+
+## Traceability
+
+<!-- What this implements or follows from: PRD §/FR, an ADR, a discussion, an upstream
+     pattern — with links. If the decision is already made somewhere, say where. -->
+
+## Background + basis
+
+<!-- Why this is needed. Cite claims; quote the load-bearing sentences rather than
+     paraphrasing from memory. -->
+
+## Goal
+
+<!-- One paragraph: the artifact(s) to produce and where they land — checkable. -->
+
+## Non-goals
+
+<!-- Each exclusion names its owner or standing reason: "No X — that is MOD-02" /
+     "No Y — stays out of scope per PRD §Z; do not add it as a side effect." -->
+
+## Affected area (best guess)
+
+<!-- Files/modules if known; the Architect finalizes the file-scope and the
+     does-not-touch list. -->
+
+## Acceptance
+
+<!-- Checkable criteria, one per line, tagged with the repo's class vocabulary if you can
+     (defaults: [machine]/[fixture]/[human]). Prefer runnable checks ("command X exits 0"). -->