@bendyline/gilde 0.1.38 → 0.1.40

package/data/craftbook-templates/en/engineering-retrospective/versions/2.0.4/craftbook.json

@@ -0,0 +1,415 @@
+{
+  "id": "engineering-retrospective",
+  "name": "Engineering Retrospective",
+  "description": "Build a data-grounded engineering retrospective from git history: activity, hotspots, review patterns, and per-person growth notes for a given window.",
+  "basedOn": {
+    "name": "gstack",
+    "url": "https://github.com/garrytan/gstack"
+  },
+  "plan": "Build an engineering retrospective from reproducible repository evidence, not memory or a leaderboard. Use read-only `run_git` queries and workspace records, state the time window and identity mapping, preserve both counts and qualitative examples, and explain data limits. Interpret activity in context: commit volume is not productivity, review visibility is incomplete, and individual notes must be constructive growth observations rather than performance ratings.",
+  "entryStepId": "scope-retro",
+  "triggers": [
+    "weekly retro",
+    "what did we ship",
+    "engineering retrospective"
+  ],
+  "command": "engineering-retrospective",
+  "steps": [
+    {
+      "id": "scope-retro",
+      "name": "Define the retrospective window and evidence contract",
+      "description": "Lock the period, repositories, participants, questions, identity aliases, and privacy boundaries.",
+      "prompt": "Confirm the requested time window, repository scope, comparison baseline, participants, timezone, team events, and intended audience. Resolve obvious author aliases from read-only history and label ambiguous identities instead of merging them. Define the questions the retrospective should answer, the datasets required, exclusions, privacy rules, and known blind spots such as squash merges or off-platform reviews.\n\nObservable handoff: write the completed result to `retro/scope.md` in the workspace with `write_file`. Do not merely describe what the file would contain. Re-read it with `read_file` before finishing this phase and repair any incomplete sections.",
+      "suggestedRole": "engineering operations analyst",
+      "advanceWhen": {
+        "file": "retro/scope.md",
+        "minBytes": 700,
+        "sniff": "nonempty",
+        "requireChange": true,
+        "goto": "collect-evidence"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "retro/scope.md",
+            "bytes": 700
+          },
+          {
+            "kind": "sniff",
+            "file": "retro/scope.md",
+            "sniff": "nonempty"
+          },
+          {
+            "kind": "contains",
+            "file": "retro/scope.md",
+            "pattern": "^##\\s+Window",
+            "flags": "im",
+            "label": "Window section"
+          },
+          {
+            "kind": "contains",
+            "file": "retro/scope.md",
+            "pattern": "^##\\s+Repositories",
+            "flags": "im",
+            "label": "Repositories section"
+          },
+          {
+            "kind": "contains",
+            "file": "retro/scope.md",
+            "pattern": "^##\\s+Identity map",
+            "flags": "im",
+            "label": "Identity map section"
+          },
+          {
+            "kind": "contains",
+            "file": "retro/scope.md",
+            "pattern": "^##\\s+Questions",
+            "flags": "im",
+            "label": "Questions section"
+          },
+          {
+            "kind": "contains",
+            "file": "retro/scope.md",
+            "pattern": "^##\\s+Limits and privacy",
+            "flags": "im",
+            "label": "Limits and privacy section"
+          }
+        ],
+        "onReject": "scope-retro",
+        "maxAttempts": 3
+      },
+      "next": "collect-evidence"
+    },
+    {
+      "id": "collect-evidence",
+      "name": "Collect and reconcile the engineering evidence",
+      "description": "Gather reproducible activity, churn, hotspot, collaboration, and quality signals with caveats.",
+      "prompt": "Use read-only `run_git` calls for log, shortlog, show, and diff statistics within `retro/scope.md`; do not use shell pipelines. Preserve the exact query arguments and result counts. Reconcile totals across authors and date boundaries, sample the work behind the numbers, and identify hotspots, change concentration, review or pairing signals visible in history, rework, test activity, documentation, maintenance, and operational work. Compare with the chosen baseline where possible. Treat missing data as missing, not zero.\n\nObservable handoff: write the completed result to `retro/evidence.md` in the workspace with `write_file`. Do not merely describe what the file would contain. Re-read it with `read_file` before finishing this phase and repair any incomplete sections.",
+      "suggestedRole": "engineering data analyst",
+      "consumes": [
+        {
+          "file": "retro/scope.md"
+        }
+      ],
+      "advanceWhen": {
+        "file": "retro/evidence.md",
+        "minBytes": 1400,
+        "sniff": "nonempty",
+        "requireChange": true,
+        "goto": "synthesize-retro"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "retro/evidence.md",
+            "bytes": 1400
+          },
+          {
+            "kind": "sniff",
+            "file": "retro/evidence.md",
+            "sniff": "nonempty"
+          },
+          {
+            "kind": "contains",
+            "file": "retro/evidence.md",
+            "pattern": "^##\\s+Queries",
+            "flags": "im",
+            "label": "Queries section"
+          },
+          {
+            "kind": "contains",
+            "file": "retro/evidence.md",
+            "pattern": "^##\\s+Activity",
+            "flags": "im",
+            "label": "Activity section"
+          },
+          {
+            "kind": "contains",
+            "file": "retro/evidence.md",
+            "pattern": "^##\\s+Hotspots",
+            "flags": "im",
+            "label": "Hotspots section"
+          },
+          {
+            "kind": "contains",
+            "file": "retro/evidence.md",
+            "pattern": "^##\\s+Collaboration",
+            "flags": "im",
+            "label": "Collaboration section"
+          },
+          {
+            "kind": "contains",
+            "file": "retro/evidence.md",
+            "pattern": "^##\\s+Quality signals",
+            "flags": "im",
+            "label": "Quality signals section"
+          },
+          {
+            "kind": "contains",
+            "file": "retro/evidence.md",
+            "pattern": "^##\\s+Data limitations",
+            "flags": "im",
+            "label": "Data limitations section"
+          }
+        ],
+        "onReject": "collect-evidence",
+        "maxAttempts": 3
+      },
+      "next": "synthesize-retro"
+    },
+    {
+      "id": "synthesize-retro",
+      "name": "Write the engineering retrospective",
+      "description": "Turn the evidence into balanced lessons, growth notes, and owned experiments.",
+      "prompt": "Write a retrospective grounded in `retro/evidence.md`. Explain the period's goals and events before interpreting metrics. Highlight outcomes, strengths, bottlenecks, hotspots, recurring rework, review patterns, maintenance load, and changes from baseline, citing paths or examples. Include constructive per-person growth notes only when supported by multiple observations; name contributions and opportunities without ranking people or equating volume with value. End with three to five owned, measurable experiments and a date for checking results.\n\nObservable handoff: write the completed result to `retro/engineering-retrospective.md` in the workspace with `write_file`. Do not merely describe what the file would contain. Re-read it with `read_file` before finishing this phase and repair any incomplete sections.",
+      "suggestedRole": "engineering manager",
+      "consumes": [
+        {
+          "file": "retro/evidence.md"
+        }
+      ],
+      "advanceWhen": {
+        "file": "retro/engineering-retrospective.md",
+        "minBytes": 1600,
+        "sniff": "nonempty",
+        "requireChange": true,
+        "goto": "evaluate"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "retro/engineering-retrospective.md",
+            "bytes": 1600
+          },
+          {
+            "kind": "sniff",
+            "file": "retro/engineering-retrospective.md",
+            "sniff": "nonempty"
+          },
+          {
+            "kind": "contains",
+            "file": "retro/engineering-retrospective.md",
+            "pattern": "^##\\s+Period context",
+            "flags": "im",
+            "label": "Period context section"
+          },
+          {
+            "kind": "contains",
+            "file": "retro/engineering-retrospective.md",
+            "pattern": "^##\\s+What went well",
+            "flags": "im",
+            "label": "What went well section"
+          },
+          {
+            "kind": "contains",
+            "file": "retro/engineering-retrospective.md",
+            "pattern": "^##\\s+Friction and hotspots",
+            "flags": "im",
+            "label": "Friction and hotspots section"
+          },
+          {
+            "kind": "contains",
+            "file": "retro/engineering-retrospective.md",
+            "pattern": "^##\\s+Collaboration and growth",
+            "flags": "im",
+            "label": "Collaboration and growth section"
+          },
+          {
+            "kind": "contains",
+            "file": "retro/engineering-retrospective.md",
+            "pattern": "^##\\s+Experiments",
+            "flags": "im",
+            "label": "Experiments section"
+          },
+          {
+            "kind": "contains",
+            "file": "retro/engineering-retrospective.md",
+            "pattern": "^##\\s+Evidence limits",
+            "flags": "im",
+            "label": "Evidence limits section"
+          }
+        ],
+        "onReject": "synthesize-retro",
+        "maxAttempts": 3
+      },
+      "next": "evaluate"
+    },
+    {
+      "id": "evaluate",
+      "name": "Evaluate the deliverable",
+      "description": "Independently grade the observable deliverable and route it to finish, repair, or user escalation.",
+      "prompt": "Review `retro/engineering-retrospective.md`, `retro/scope.md`, `retro/evidence.md` against every criterion below. Inspect the underlying evidence files named by the workflow; do not grade from the author's summary alone.\n\n1. The time window, repository scope, baseline, identities, and evidence queries are reproducible.\n2. Counts reconcile or discrepancies are explained, and missing signals are not treated as zero.\n3. Every important conclusion traces to multiple observations, paths, or examples rather than activity volume alone.\n4. Strengths, friction, hotspots, maintenance, collaboration, and changes from baseline are balanced and contextualized.\n5. Individual notes are evidence-backed, constructive, privacy-conscious, and never framed as rankings or performance scores.\n6. Experiments have owners, measurable outcomes, and a review date.\n\nOpen `retro/engineering-retrospective.md`, `retro/scope.md`, `retro/evidence.md` with `read_file`. Write the evidence-backed review to `{{workPath}}/reviews/engineering-retrospective-review.md` in the artifacts drawer with `write_artifact`. Give each criterion a PASS or FAIL with a concrete path, excerpt, measurement, or observed behavior. End with exactly `Verdict: PASS` or `Verdict: REVISE`. Then use `advance_task_step` for the active task: PASS routes to `finish`; REVISE routes to `repair` for review rounds 1 through 2, and the 3th REVISE routes to `needs-user`. Never route to finish while a criterion is unmet.",
+      "suggestedRole": "engineering leadership reviewer",
+      "consumes": [
+        {
+          "file": "retro/engineering-retrospective.md"
+        },
+        {
+          "file": "retro/scope.md"
+        },
+        {
+          "file": "retro/evidence.md"
+        }
+      ],
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/reviews/engineering-retrospective-review.md",
+            "bytes": 400,
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "{{workPath}}/reviews/engineering-retrospective-review.md",
+            "pattern": "Verdict:\\s*(?:PASS|REVISE)",
+            "flags": "i",
+            "label": "explicit PASS or REVISE verdict",
+            "artifact": true
+          }
+        ],
+        "onReject": "evaluate",
+        "maxAttempts": 3
+      },
+      "next": "repair"
+    },
+    {
+      "id": "repair",
+      "name": "Repair the deliverable",
+      "description": "Fix only the concrete gaps from the latest independent review.",
+      "prompt": "Read `{{workPath}}/reviews/engineering-retrospective-review.md` with `read_artifact` and repair every failed criterion in `retro/engineering-retrospective.md`, `retro/scope.md`, `retro/evidence.md`. Make changes on each file's declared surface (`write_artifact` for artifact inputs, `write_file` for workspace inputs), not in task notes or a reply. Preserve evidence that already passed. Re-run or re-check anything the reviewer found unproven. Ensure `retro/engineering-retrospective.md` is genuinely updated this turn so the repair is observable, then hand it back for independent evaluation.",
+      "suggestedRole": "engineering manager",
+      "consumes": [
+        {
+          "file": "{{workPath}}/reviews/engineering-retrospective-review.md",
+          "artifact": true
+        },
+        {
+          "file": "retro/engineering-retrospective.md"
+        },
+        {
+          "file": "retro/scope.md"
+        },
+        {
+          "file": "retro/evidence.md"
+        }
+      ],
+      "advanceWhen": {
+        "file": "retro/engineering-retrospective.md",
+        "minBytes": 1600,
+        "sniff": "nonempty",
+        "requireChange": true,
+        "goto": "evaluate"
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "retro/engineering-retrospective.md",
+            "bytes": 1600
+          },
+          {
+            "kind": "sniff",
+            "file": "retro/engineering-retrospective.md",
+            "sniff": "nonempty"
+          },
+          {
+            "kind": "contains",
+            "file": "retro/engineering-retrospective.md",
+            "pattern": "^##\\s+Period context",
+            "flags": "im",
+            "label": "Period context section"
+          },
+          {
+            "kind": "contains",
+            "file": "retro/engineering-retrospective.md",
+            "pattern": "^##\\s+What went well",
+            "flags": "im",
+            "label": "What went well section"
+          },
+          {
+            "kind": "contains",
+            "file": "retro/engineering-retrospective.md",
+            "pattern": "^##\\s+Friction and hotspots",
+            "flags": "im",
+            "label": "Friction and hotspots section"
+          },
+          {
+            "kind": "contains",
+            "file": "retro/engineering-retrospective.md",
+            "pattern": "^##\\s+Collaboration and growth",
+            "flags": "im",
+            "label": "Collaboration and growth section"
+          },
+          {
+            "kind": "contains",
+            "file": "retro/engineering-retrospective.md",
+            "pattern": "^##\\s+Experiments",
+            "flags": "im",
+            "label": "Experiments section"
+          },
+          {
+            "kind": "contains",
+            "file": "retro/engineering-retrospective.md",
+            "pattern": "^##\\s+Evidence limits",
+            "flags": "im",
+            "label": "Evidence limits section"
+          }
+        ],
+        "onReject": "repair",
+        "maxAttempts": 3
+      },
+      "next": "evaluate"
+    },
+    {
+      "id": "finish",
+      "name": "Finish",
+      "description": "All deterministic and reviewer criteria passed.",
+      "prompt": "The independent review passed. Read `{{workPath}}/reviews/engineering-retrospective-review.md` with `read_artifact`, then use `write_task_note` to record a concise DONE summary with the final deliverable paths (`retro/engineering-retrospective.md`, `retro/scope.md`, `retro/evidence.md`) and the evidence that each acceptance criterion passed. Report DONE without starting new work.",
+      "suggestedRole": "project lead",
+      "consumes": [
+        {
+          "file": "{{workPath}}/reviews/engineering-retrospective-review.md",
+          "artifact": true
+        }
+      ],
+      "terminal": true
+    },
+    {
+      "id": "needs-user",
+      "name": "Escalate unresolved concerns",
+      "description": "The bounded repair loop ended without a defensible pass.",
+      "prompt": "The deliverable did not pass after 3 review rounds. Do not claim success. Read `{{workPath}}/reviews/engineering-retrospective-review.md` with `read_artifact`, then use `write_task_note` to record DONE_WITH_CONCERNS: the unmet criteria, what was attempted, the affected paths, and the smallest user decision or missing input needed to continue.",
+      "suggestedRole": "project lead",
+      "consumes": [
+        {
+          "file": "{{workPath}}/reviews/engineering-retrospective-review.md",
+          "artifact": true
+        }
+      ],
+      "terminal": true
+    }
+  ],
+  "version": "2.0.4",
+  "releasedAt": "2026-08-21T00:00:00Z",
+  "paramSchema": {
+    "type": "object",
+    "properties": {
+      "workPath": {
+        "type": "string",
+        "title": "Working folder",
+        "description": "Per-task working folder in the artifacts drawer. Defaults to this task's own folder so runs never collide; override with a stable name when you deliberately want runs to share files.",
+        "default": "{{task.dir}}"
+      }
+    }
+  },
+  "minGezelVersion": "1.26233"
+}

package/data/craftbook-templates/en/engineering-retrospective/versions/2.0.4/test.json

@@ -0,0 +1,194 @@
+{
+  "schemaVersion": 1,
+  "title": "Engineering Retrospective — queue reliability window",
+  "objective": "Exercise the Engineering Retrospective craftbook on a fixed exported history and require reconciled metrics, contextual interpretation, balanced growth notes, and owned experiments.",
+  "tags": [
+    "workflow",
+    "retrospective",
+    "engineering",
+    "corpus"
+  ],
+  "prompt": "Use the Engineering Retrospective craftbook for the fixed 2026-07-01 through 2026-07-14 window. This evaluation has no live git repository: `source/git-log.txt` and `source/numstat.tsv` are the authoritative read-only exports, and `source/team-events.md` supplies context. Do not treat unavailable live history as zero or ask for another window. Reconcile human activity, exclude the release bot, identify evidence-backed hotspots and quality/collaboration signals, and write the workflow artifacts ending at `retro/engineering-retrospective.md`. Include constructive notes for Alex Kim and Priya Shah without rankings or volume-as-productivity claims, then propose three to five owner-backed experiments with measurable outcomes and a review date.",
+  "setup": {
+    "projectName": "Queue reliability engineering retrospective",
+    "about": "A self-contained retrospective over exported repository evidence. The export and context files are complete; no network, live git repository, or personnel system is available.",
+    "missionObjectives": "Run the Engineering Retrospective craftbook as a real task, reconcile the fixed history, preserve evidence limits, and produce an actionable, fair retrospective.",
+    "files": [
+      {
+        "path": "source/git-log.txt",
+        "content": "# sha|date|author|email|subject\na1c001|2026-07-02|Alex Kim|alex@example.test|fix queue timeout classification\na1c002|2026-07-03|Priya Shah|priya@example.test|add queue retry metrics\na1c003|2026-07-06|Priya Shah|priya@example.test|document on-call queue recovery\na1c004|2026-07-09|Alex Kim|alex@example.test|cover refresh-token expiry\na1c005|2026-07-10|Alex Kim|alex@example.test|add queue timeout regression fixture\na1c006|2026-07-12|Priya Shah|priya@example.test|pin parser dependency after advisory review\na1c007|2026-07-14|release-bot|bot@example.test|release 2.8.0\n"
+      },
+      {
+        "path": "source/numstat.tsv",
+        "content": "sha\tadded\tdeleted\tpath\na1c001\t34\t12\tsrc/queue.ts\na1c001\t22\t0\ttests/queue.test.ts\na1c002\t28\t4\tsrc/queue.ts\na1c002\t40\t2\tsrc/metrics.ts\na1c003\t55\t3\tdocs/oncall.md\na1c004\t18\t7\tsrc/auth.ts\na1c004\t26\t0\ttests/auth.test.ts\na1c005\t12\t6\tsrc/queue.ts\na1c005\t31\t2\ttests/queue.test.ts\na1c006\t3\t3\tpackage.json\na1c006\t14\t14\tpnpm-lock.yaml\na1c007\t2\t2\tCHANGELOG.md\n"
+      },
+      {
+        "path": "source/team-events.md",
+        "content": "# Team context\n\n- Window: 2026-07-01 through 2026-07-14, UTC. Compare only within this window; no prior baseline export is available.\n- Queue retry incident on 2026-07-02 caused delayed job status for 41 minutes. Priya Shah was primary responder; Alex Kim traced the timeout classification the next morning.\n- Alex was on planned leave July 4-5.\n- Priya paired with Alex on the queue regression fixture; pairing is mentioned in commit a1c005 but the export cannot attribute line-level co-authorship.\n- Release-bot is automation and must not be included in human activity or growth notes.\n- Review comments, meetings, and off-repository operational work are not present in this export.\n- Experiments should be reviewed on 2026-07-28.\n"
+      }
+    ],
+    "craftbookParams": {
+      "workPath": "tasks/eval"
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "The real craftbook reconciles the exported history into a contextual, non-ranking retrospective with balanced growth notes and measurable experiments.",
+    "deliverables": [
+      {
+        "path": "retro/scope.md",
+        "kind": "markdown-notes",
+        "minBytes": 600,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "retro/scope.md",
+            "pattern": "2026-07-01[\\s\\S]*2026-07-14[\\s\\S]*(Alex Kim|alex@example\\.test)[\\s\\S]*(Priya Shah|priya@example\\.test)[\\s\\S]*(release-bot|automation)",
+            "flags": "i",
+            "label": "window, identity map, and bot exclusion"
+          }
+        ]
+      },
+      {
+        "path": "retro/evidence.md",
+        "kind": "markdown-report",
+        "minBytes": 1100,
+        "checks": [
+          {
+            "kind": "valueGrounding",
+            "file": "retro/evidence.md",
+            "facts": [
+              {
+                "id": "human-commits",
+                "label": "six human commits",
+                "required": [
+                  "6\\s+human\\s+commits?|six\\s+human\\s+commits?"
+                ]
+              },
+              {
+                "id": "bot-exclusion",
+                "label": "one excluded bot commit",
+                "required": [
+                  "1\\s+(?:bot|automated)|one\\s+(?:bot|automated)"
+                ]
+              },
+              {
+                "id": "alex-count",
+                "label": "three Alex commits",
+                "required": [
+                  "Alex(?: Kim)?[^\\n]{0,80}3"
+                ]
+              },
+              {
+                "id": "priya-count",
+                "label": "three Priya commits",
+                "required": [
+                  "Priya(?: Shah)?[^\\n]{0,80}3"
+                ]
+              },
+              {
+                "id": "hotspot",
+                "label": "queue file changed in three commits",
+                "required": [
+                  "src/queue\\.ts[^\\n]{0,100}3|3[^\\n]{0,100}src/queue\\.ts"
+                ]
+              }
+            ]
+          },
+          {
+            "kind": "citationsResolve",
+            "file": "retro/evidence.md",
+            "minCitations": 3
+          }
+        ]
+      },
+      {
+        "path": "retro/engineering-retrospective.md",
+        "kind": "markdown-report",
+        "minBytes": 1600,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "retro/engineering-retrospective.md",
+            "pattern": "^#{1,3}\\s+Period context\\b[\\s\\S]*^#{1,3}\\s+What went well\\b[\\s\\S]*^#{1,3}\\s+Friction and hotspots\\b[\\s\\S]*^#{1,3}\\s+Collaboration and growth\\b[\\s\\S]*^#{1,3}\\s+Experiments\\b[\\s\\S]*^#{1,3}\\s+Evidence limits\\b",
+            "flags": "im",
+            "label": "complete retrospective structure"
+          },
+          {
+            "kind": "contains",
+            "file": "retro/engineering-retrospective.md",
+            "pattern": "Alex Kim[\\s\\S]*Priya Shah|Priya Shah[\\s\\S]*Alex Kim",
+            "label": "balanced named growth notes"
+          },
+          {
+            "kind": "contains",
+            "file": "retro/engineering-retrospective.md",
+            "pattern": "2026-07-28[\\s\\S]*(owner|Alex|Priya)|(owner|Alex|Priya)[\\s\\S]*2026-07-28",
+            "flags": "i",
+            "label": "owned experiments with review date"
+          },
+          {
+            "kind": "notContains",
+            "file": "retro/engineering-retrospective.md",
+            "pattern": "top performer|bottom performer|most productive|least productive|performance score|rank(?:ed|ing)?\\s+(?:the\\s+)?(?:engineers|people|team)",
+            "flags": "i",
+            "label": "no personnel ranking or volume-as-productivity framing"
+          },
+          {
+            "kind": "citationsResolve",
+            "file": "retro/engineering-retrospective.md",
+            "minCitations": 3
+          }
+        ]
+      }
+    ],
+    "taskNotes": {
+      "minBytes": 180,
+      "checks": [
+        {
+          "kind": "contains",
+          "file": "task-notes.md",
+          "pattern": "\\bDONE\\b[\\s\\S]*retro/engineering-retrospective\\.md[\\s\\S]*(experiment|evidence)",
+          "flags": "i",
+          "label": "terminal note records the evidence-backed retrospective"
+        }
+      ],
+      "requireCraftbookTask": true
+    },
+    "taskGraph": {
+      "requireCraftbookTask": true,
+      "requireTerminalStep": true
+    },
+    "unchangedFixtures": [
+      "source/git-log.txt",
+      "source/numstat.tsv",
+      "source/team-events.md"
+    ]
+  },
+  "rubric": {
+    "artifact": {
+      "path": "retro/engineering-retrospective.md",
+      "kind": "markdown"
+    },
+    "axes": [
+      {
+        "name": "Evidence integrity",
+        "description": "Counts reconcile to the exports, bot activity is excluded, hotspots are traceable, and missing review or operational data is not treated as zero."
+      },
+      {
+        "name": "Context and fairness",
+        "description": "The incident, leave, pairing, and evidence limits shape interpretation; individual notes are constructive and do not rank people by volume."
+      },
+      {
+        "name": "Actionability",
+        "description": "The retrospective turns patterns into a small set of owner-backed, measurable experiments with a fixed review date."
+      }
+    ],
+    "contextNote": "The three source exports are the complete evidence set. Do not reward invented review metrics, cycle time, or off-repository work."
+  },
+  "qualityFocus": [
+    "Reconcile six human commits and exclude release automation",
+    "Explain the queue hotspot in incident context without equating volume with value",
+    "Give Alex and Priya balanced growth notes and measurable experiments"
+  ]
+}

package/data/craftbook-templates/ep/episode-plan/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "episode-plan",
   "role": "general",
+  "category": "media",
   "name": "Plan the Episode",
   "description": "Turn the idea backlog and last episode's loose threads into a locked plan for the next episode: a rundown with timed segments, what to prep, and a record date — so the show ships on rhythm instead of on adrenaline. Locks the episode goal and the acceptance checklist FIRST, then builds the timed rundown, then writes the brief with prep owners and the record date. Use for planning the next episode, episode rundowns, show planning, and 'what's the next episode'.",
   "tags": [