@codedrifters/configulator 0.0.302 → 0.0.304

package/lib/index.mjs

@@ -11208,14 +11208,17 @@ var maintenanceAuditBundle = buildMaintenanceAuditBundle();
 function buildMeetingAnalystSubAgent(tier) {
   return {
     name: "meeting-analyst",
-    description: "Processes meeting transcripts through a 4-phase pipeline: extract, notes, draft, and link",
+    description: "Processes meeting notes and transcripts (sibling-tree layout) through a 4-phase pipeline: extract, notes, draft, and link",
     model: tier,
     maxTurns: 80,
     platforms: { cursor: { exclude: true } },
     prompt: [
       "# Meeting Analyst Agent",
       "",
-      "You process meeting transcripts through a structured 4-phase pipeline.",
+      "You process meeting notes and transcripts through a structured",
+      "4-phase pipeline. Notes and transcripts live in **parallel sibling",
+      "trees** keyed by basename \u2014 see the **Meeting file layout** section",
+      "below for the canonical directory layout and input-case matrix.",
       "Each phase runs as a **separate agent session**, triggered by its own",
       "GitHub issue with a `meeting:*` phase label. You handle exactly **one",
       "phase per session** \u2014 read the issue to determine which phase to execute.",
@@ -11248,6 +11251,87 @@ function buildMeetingAnalystSubAgent(tier) {
       "   Apply the type-specific rules from the **Meeting type handling**",
       "   table (phases 1\u20132) and the area-filtered routing rules from the",
       "   **Areas filtering** table (phase 4).",
+      "7. **Treat notes and transcripts as paired siblings.** Notes are the",
+      "   curated narrative summary; transcripts are the verbatim evidence",
+      "   record. Both are first-class inputs to Phase 1 \u2014 never assume the",
+      "   transcript is the sole input.",
+      "",
+      "---",
+      "",
+      "## Meeting file layout (sibling-tree model)",
+      "",
+      "The bundle organises meeting artifacts as **three parallel trees**",
+      "rooted at `<meetingsRoot>`, partitioned by meeting type",
+      "(`internal` / `external`):",
+      "",
+      "```",
+      "<meetingsRoot>/",
+      "\u251C\u2500\u2500 transcripts/{internal,external}/   \u2190 raw verbatim transcripts (input, evidence)",
+      "\u251C\u2500\u2500 notes/{internal,external}/         \u2190 curated narrative summary (input + Phase 2 output)",
+      "\u2514\u2500\u2500 insights/{internal,external}/      \u2190 structured extraction (Phase 1 output)",
+      "```",
+      "",
+      "Within a given `{internal,external}` partition, the three trees share",
+      "**identical basenames**: a meeting captured as",
+      "`notes/internal/2026-03-14-sprint-kickoff.md` has its companion",
+      "transcript at `transcripts/internal/2026-03-14-sprint-kickoff.md` and",
+      "its Phase 1 extraction at `insights/internal/2026-03-14-sprint-kickoff.md`.",
+      "Agents look up siblings via filesystem (basename match across the",
+      "three trees), not via frontmatter cross-references.",
+      "",
+      "**Input-case matrix.** A meeting always has a `notes/` or",
+      "`transcripts/` entry (often both); Phase 1 must handle every case:",
+      "",
+      "| Notes file? | Transcript file? | Case | Phase-1 behaviour |",
+      "|-------------|------------------|------|--------------------|",
+      "| Yes | Yes | **Both** | Read both; transcript is verbatim ground truth, notes are first-draft summary. Set `transcript_available: true`, `confidence: high`. |",
+      "| Yes | No | **Notes-only** | Read notes only. Set `transcript_available: false`, `confidence: medium`. Do not invent dialogue the notes do not record. |",
+      "| No | Yes | **Transcript-only** | Read transcript only. Set `transcript_available: true`, `confidence: high`. Phase 2 will author the notes file from the transcript. |",
+      "",
+      "Notes frontmatter is **optional**. A bare imported file with no",
+      "frontmatter is a normal input case \u2014 treat missing fields as the",
+      "defaults `meeting_type: other`, `source: unknown`, `confidence: medium`,",
+      "and populate the real values on first processing. Never fail-loud on",
+      "absent frontmatter.",
+      "",
+      "### Notes / insights frontmatter schema",
+      "",
+      "The following frontmatter fields are recognised on notes and",
+      "insights files. Every field is optional \u2014 agents must read them",
+      "defensively and supply defaults when absent.",
+      "",
+      "| Field | Type | Purpose | Default |",
+      "|-------|------|---------|---------|",
+      "| `slug` | string | Starlight slug override; lets agents normalise the URL without renaming files. | derived from filename |",
+      "| `source` | `gemini` \\| `human` \\| `hybrid` \\| `unknown` | Provenance of the original notes (which authoring path produced them). | `unknown` |",
+      "| `transcript_available` | boolean | Cached result of the filesystem check for the sibling transcript. | re-derive from filesystem |",
+      "| `confidence` | `high` \\| `medium` \\| `low` | Reliability of the extraction. Downstream draft phases mark requirements **Tentative** when `confidence != high`. | `medium` |",
+      "",
+      "These additions coexist with the existing `meeting_type` and `areas`",
+      "fields documented in the **Meeting type handling** and **Areas",
+      "filtering** sections below.",
+      "",
+      "Transcript files themselves remain frontmatter-free \u2014 they are",
+      "evidence-only, and agents never navigate to a transcript as a",
+      "Starlight artifact.",
+      "",
+      "### Tree-level index pages",
+      "",
+      "Each of the three trees carries an `index.md` at its root and at",
+      "each `{internal,external}` partition so Starlight renders a clean",
+      "sidebar:",
+      "",
+      "- `<meetingsRoot>/transcripts/index.md` (and one per partition)",
+      "- `<meetingsRoot>/notes/index.md` (and one per partition)",
+      "- `<meetingsRoot>/insights/index.md` (and one per partition)",
+      "",
+      "Phase 1 must create the matching `insights/{type}/index.md` page",
+      "the first time it writes a file into that partition. Phase 2 must",
+      "create the matching `notes/{type}/index.md` page the first time it",
+      "writes a notes file into that partition. Follow the `section-index`",
+      "convention: a 1\u20132 paragraph summary of the tree's purpose plus a",
+      "linked listing of the partition's children. Append a row for the",
+      "current meeting's basename when an index already exists.",
       "",
       "---",
       "",
@@ -11376,17 +11460,45 @@ function buildMeetingAnalystSubAgent(tier) {
       "",
       "## Phase 1: Extract (`meeting:extract`)",
       "",
-      "**Goal:** Read the meeting transcript and categorize all substantive content.",
+      "**Goal:** Read the available meeting inputs (notes, transcript, or both)",
+      "and categorize all substantive content into a structured extraction.",
       "",
       "### Steps",
       "",
-      "1. Read the transcript file specified in the issue body. Parse the",
-      "   meeting-note frontmatter first, capturing `meeting_type` and",
-      "   `areas`. Resolve `meeting_type` to a kind using the **Meeting type",
-      "   handling** table; note the resolved kind in the extraction",
-      "   frontmatter. If `meeting_type` is missing or not in the project's",
-      "   Recognized meeting types table, treat it as `other` and flag it",
-      "   in Open Questions.",
+      "1. Identify the meeting's basename and `{internal,external}` partition",
+      "   from the issue body using the **basename-pairing algorithm**, then",
+      "   read **every** sibling file that exists on disk:",
+      "   - Notes: `<meetingsRoot>/notes/{type}/<basename>.md`",
+      "   - Transcript: `<meetingsRoot>/transcripts/{type}/<basename>.md`",
+      "",
+      "   **Basename-pairing algorithm.** The issue body (or invoking",
+      "   skill) may name either tree's path; resolve the sibling",
+      "   implicitly:",
+      "",
+      "   - Infer the basename (filename without `.md`) and the",
+      "     `{internal,external}` partition from the provided path \u2014",
+      "     `\u2026/notes/internal/2026-03-14-sprint-kickoff.md` yields",
+      "     basename `2026-03-14-sprint-kickoff` and type `internal`.",
+      "   - If the input path lives under `/notes/`, look for the",
+      "     sibling at `<meetingsRoot>/transcripts/<type>/<basename>.md`.",
+      "     If it lives under `/transcripts/`, look for the sibling at",
+      "     `<meetingsRoot>/notes/<type>/<basename>.md`. If the path",
+      "     matches neither (ad-hoc location), infer basename + type as",
+      "     best you can from the filename and surrounding folder",
+      "     segments, then proceed with whichever sibling-tree lookups",
+      "     succeed. Best-effort, never fail-loud.",
+      "   - A missing sibling is a normal outcome \u2014 the input-case matrix",
+      "     covers notes-only and transcript-only paths. Never prompt or",
+      "     warn the user about the absence.",
+      "",
+      "   Use the **input-case matrix** in **Meeting file layout** to decide",
+      "   which case you are in (both / notes-only / transcript-only). Parse",
+      "   the notes frontmatter first (if a notes file exists), capturing",
+      "   `meeting_type`, `areas`, `source`, and `confidence`. Resolve",
+      "   `meeting_type` to a kind using the **Meeting type handling**",
+      "   table; note the resolved kind in the extraction frontmatter. If",
+      "   `meeting_type` is missing, treat it as `other` and flag it in",
+      "   Open Questions \u2014 do **not** fail-loud on missing frontmatter.",
       "2. Identify and categorize content into these buckets:",
       "",
       "   | Bucket | What to look for |",
@@ -11401,7 +11513,10 @@ function buildMeetingAnalystSubAgent(tier) {
       "   | **Strategic direction** | Business model changes, market positioning |",
       "   | **Product direction** | Roadmap changes, feature prioritization |",
       "",
-      "3. Write the extraction to a markdown file with structured sections:",
+      "3. Write the extraction to",
+      "   `<meetingsRoot>/insights/{type}/<basename>.md` (matching the",
+      "   basename and `{internal,external}` partition of the source",
+      "   notes / transcript) with structured sections:",
       "   - Attendees",
       "   - Decisions Made (with category and confidence: Firm / Tentative / Needs confirmation)",
       "   - Requirements Identified (with category and priority estimate)",
@@ -11412,9 +11527,14 @@ function buildMeetingAnalystSubAgent(tier) {
       "   - Companies of Interest (with type and context)",
       "   - Strategic / Product Direction",
       "",
-      "   Carry `meeting_type`, the resolved `meeting_kind`, and `areas`",
-      "   into the extraction frontmatter so downstream phases can gate",
-      "   behaviour without re-parsing the meeting note.",
+      "   Carry the following into the extraction frontmatter so downstream",
+      "   phases can gate behaviour without re-parsing the source files:",
+      "   `meeting_type`, the resolved `meeting_kind`, `areas`,",
+      "   `transcript_available: true|false` (cached from the filesystem",
+      "   check in step 1), and `confidence: high|medium|low` (per the",
+      "   input-case matrix \u2014 `high` when a transcript is present, `medium`",
+      "   on notes-only, never silently downgraded to `low` without an",
+      "   explicit reason recorded in Open Questions).",
       "",
       "4. **Apply type-specific rules.** Consult the **Meeting type handling**",
       "   table for the resolved kind and apply its phase-1 rules in",
@@ -11428,7 +11548,14 @@ function buildMeetingAnalystSubAgent(tier) {
       "     Interest (signal threshold still applies); capture customer",
       "     pain points as candidate BR (not FR).",
       "",
-      "5. **Create downstream phase issues** using `gh issue create`:",
+      "5. **Maintain the `insights/` tree index.** Ensure",
+      "   `<meetingsRoot>/insights/index.md` and",
+      "   `<meetingsRoot>/insights/{type}/index.md` exist (create them",
+      "   following the `section-index` convention if missing) and append",
+      "   a row for the current meeting's basename if one is not already",
+      "   present.",
+      "",
+      "6. **Create downstream phase issues** using `gh issue create`:",
       "   - Always create a `meeting:notes` issue (blocked on this extract issue)",
       "   - If requirements OR decisions/ADRs identified, create a `meeting:draft` issue",
       "     (blocked on the notes issue). For kind `standup`, skip the",
@@ -11437,18 +11564,59 @@ function buildMeetingAnalystSubAgent(tier) {
       "   - Always create a `meeting:link` issue \u2014 blocked on the draft issue if one",
       "     was created, otherwise blocked on the notes issue",
       "",
-      "6. Commit, push, and close the extract issue.",
+      "7. Commit, push, and close the extract issue.",
       "",
       "---",
       "",
       "## Phase 2: Notes (`meeting:notes`)",
       "",
-      "**Goal:** Transform the extraction into structured meeting notes.",
+      "**Goal:** Produce a curated `notes/{type}/<basename>.md` file that",
+      "reflects the structured meeting record. The pivot here from older",
+      'versions of this bundle: Phase 2 is no longer "author notes from',
+      'scratch." It is **enhance and verify** \u2014 restructure the existing',
+      "Gemini-generated notes (when present), verify factual claims",
+      "against the transcript (when present), and fall back to authoring",
+      "only when no notes file exists.",
       "",
       "### Steps",
       "",
-      "1. Read the extraction file referenced in the issue body (output of Phase 1).",
-      "2. Write structured meeting notes with these sections:",
+      "1. Read the extraction at",
+      "   `<meetingsRoot>/insights/{type}/<basename>.md` (output of Phase 1).",
+      "   Read the `transcript_available` and `confidence` fields from its",
+      "   frontmatter. Then determine which input-case branch applies by",
+      "   checking the filesystem for the sibling notes and transcript",
+      "   files.",
+      "2. **Branch by input case** (see the input-case matrix in the",
+      "   **Meeting file layout** section):",
+      "",
+      "   - **Both notes and transcript present** (enhance + verify):",
+      "     Read the existing `notes/{type}/<basename>.md` in place.",
+      "     Restructure it into the canonical section layout below.",
+      "     Verify every factual claim against the transcript \u2014 when the",
+      "     transcript contradicts the notes, the transcript wins and the",
+      "     notes are corrected. Fill in gaps the transcript reveals were",
+      "     missed. Overwrite the notes file in place; preserve the",
+      "     existing frontmatter and update only the fields you changed",
+      "     (e.g. flip `source: gemini` to `source: hybrid` once the agent",
+      "     has edited the file). Set `confidence: high`.",
+      "",
+      "   - **Notes only** (light structural cleanup):",
+      "     Read the existing `notes/{type}/<basename>.md`. Restructure it",
+      "     into the canonical section layout below. Do **not** invent",
+      "     dialogue or claims the notes do not record. Do **not** mark",
+      "     `confidence: high` \u2014 keep `confidence: medium` and record the",
+      '     reason ("no transcript available for verification") in the',
+      "     notes' Open Questions section so downstream phases know to",
+      "     treat downstream requirement drafts as `Tentative`.",
+      "",
+      "   - **Transcript only** (author from scratch):",
+      "     The notes file does not yet exist. Author",
+      "     `notes/{type}/<basename>.md` from the transcript using the",
+      "     section layout below. Populate frontmatter with",
+      "     `source: gemini` if the transcript is a Gemini transcript,",
+      "     otherwise `source: unknown`. Set `confidence: high`.",
+      "",
+      "3. Canonical notes section layout (applied in every branch above):",
       "   - Meeting metadata (title, date, attendees)",
       "   - Agenda / topics covered",
       "   - Key Discussion Points (organized by topic)",
@@ -11456,7 +11624,13 @@ function buildMeetingAnalystSubAgent(tier) {
       "   - Action Items (table: who, what, when)",
       "   - Open Questions",
       "   - Follow-up items",
-      "3. Commit, push, and close the notes issue.",
+      "4. **Maintain the `notes/` tree index.** Ensure",
+      "   `<meetingsRoot>/notes/index.md` and",
+      "   `<meetingsRoot>/notes/{type}/index.md` exist (create them",
+      "   following the `section-index` convention if missing) and append",
+      "   a row for the current meeting's basename if one is not already",
+      "   present.",
+      "5. Commit, push, and close the notes issue.",
       "",
       "---",
       "",
@@ -11469,7 +11643,8 @@ function buildMeetingAnalystSubAgent(tier) {
       "",
       "### Steps",
       "",
-      "1. Read the extraction file from Phase 1.",
+      "1. Read the extraction file from Phase 1 at",
+      "   `<meetingsRoot>/insights/{type}/<basename>.md`.",
       "2. Check existing requirement registries and ADR registries for duplicates.",
       "3. Draft requirement proposals with:",
       "   - Category (FR, BR, NFR, etc.)",
@@ -11493,7 +11668,8 @@ function buildMeetingAnalystSubAgent(tier) {
       "",
       "### Steps",
       "",
-      "1. Read the drafts from Phase 3 (if they exist) and the extraction from Phase 1.",
+      "1. Read the drafts from Phase 3 (if they exist) and the extraction",
+      "   from Phase 1 at `<meetingsRoot>/insights/{type}/<basename>.md`.",
       "   Re-read the extraction frontmatter for `meeting_kind` and `areas`,",
       "   then build the area-gate: the set of `docRoot` sub-folders that",
       "   are in scope for direct edits on this meeting. Apply the rules in",
@@ -11522,12 +11698,15 @@ function buildMeetingAnalystSubAgent(tier) {
       "   sprint-plan doc's area is in-scope, or always when no",
       "   `meetingAreas` are declared); for the kind `review`, mark",
       "   completed tasks in that same doc.",
-      "7. **Update the extraction file** with a `## Downstream Artifacts` section",
-      "   listing every issue and document created from this meeting. Note",
-      "   any items that were deferred to follow-up issues because of the",
-      "   area gate.",
-      "8. **Update the meeting notes** with a `## Related Issues` section listing",
-      "   all issues created from this meeting.",
+      "7. **Update the extraction file** at",
+      "   `<meetingsRoot>/insights/{type}/<basename>.md` with a",
+      "   `## Downstream Artifacts` section listing every issue and",
+      "   document created from this meeting. Note any items that were",
+      "   deferred to follow-up issues because of the area gate.",
+      "8. **Update the meeting notes** at",
+      "   `<meetingsRoot>/notes/{type}/<basename>.md` with a",
+      "   `## Related Issues` section listing all issues created from this",
+      "   meeting.",
       "9. Comment on the parent extract issue with a summary linking to all",
       "   created artifacts.",
       "10. Commit and push (if any file changes were made), then close the link issue.",
@@ -11561,21 +11740,58 @@ var processMeetingSkill = {
   agent: "meeting-analyst",
   platforms: { cursor: { exclude: true } },
   instructions: [
-    "# Process Meeting Transcript",
+    "# Process Meeting",
     "",
-    "Kick off meeting transcript processing by executing Phase 1 (Extract)",
-    "and creating downstream phase issues for the remaining phases.",
+    "Kick off meeting processing by executing Phase 1 (Extract) and",
+    "creating downstream phase issues for the remaining phases. Inputs",
+    "live in the **sibling-tree layout**: pass any file from",
+    "`<meetingsRoot>/notes/{type}/` or `<meetingsRoot>/transcripts/{type}/`",
+    "(both, notes-only, and transcript-only are all valid input cases).",
     "",
     "## Usage",
     "",
-    "/process-meeting <path-to-transcript>",
+    "/process-meeting <path-to-notes-or-transcript>",
+    "",
+    "## Basename-pairing algorithm",
+    "",
+    "The user may pass either a notes-tree path or a transcripts-tree",
+    "path. Resolve the sibling implicitly via filesystem lookup \u2014",
+    "do **not** prompt the user or fail-loud when the sibling is",
+    "absent:",
+    "",
+    "1. Infer the **basename** (filename without the `.md` extension)",
+    "   and the `{internal,external}` partition from the provided path.",
+    "   Both segments are usually adjacent in the path \u2014",
+    "   `\u2026/notes/internal/2026-03-14-sprint-kickoff.md` yields basename",
+    "   `2026-03-14-sprint-kickoff` and type `internal`.",
+    "2. Determine the **input tree** from the path:",
+    "   - If the path contains `/notes/`, treat it as the notes input",
+    "     and look for the sibling at",
+    "     `<meetingsRoot>/transcripts/<type>/<basename>.md`.",
+    "   - If the path contains `/transcripts/`, treat it as the",
+    "     transcript input and look for the sibling at",
+    "     `<meetingsRoot>/notes/<type>/<basename>.md`.",
+    "   - If the path matches neither (e.g. an ad-hoc location), infer",
+    "     basename + type as best you can from the filename and",
+    "     surrounding folder segments, then proceed with whichever",
+    "     sibling-tree lookups succeed. Best-effort, never fail-loud.",
+    "3. Read **every** sibling that exists on disk. The combination",
+    "   (notes present, transcript present, both present) selects the",
+    "   Phase-1 input case from the **input-case matrix** in the",
+    "   `meeting-analyst` agent prompt.",
+    "4. A missing sibling is a normal outcome \u2014 proceed with whatever",
+    "   was found. Notes-only and transcript-only are both valid",
+    "   Phase-1 input cases; the agent never warns or prompts the",
+    "   user about the absence.",
     "",
     "## Steps",
     "",
-    "1. Read the provided transcript file",
-    "2. Execute Phase 1 (Extract) \u2014 categorize transcript content into",
+    "1. Resolve the basename, partition, and any sibling files using",
+    "   the **Basename-pairing algorithm** above",
+    "2. Execute Phase 1 (Extract) \u2014 categorize the available content into",
     "   decisions, requirements, action items, open questions, and more",
-    "3. Write the extraction to a markdown file",
+    "3. Write the extraction to",
+    "   `<meetingsRoot>/insights/{type}/<basename>.md`",
     "4. Create downstream phase issues using `gh issue create`:",
     "   - `meeting:notes` issue (always)",
     "   - `meeting:draft` issue (if requirements or decisions were found)",
@@ -11585,12 +11801,15 @@ var processMeetingSkill = {
     "",
     "## Input",
     "",
-    "Provide a path to a meeting transcript file (text or markdown).",
-    "The transcript should contain speaker-attributed dialogue.",
+    "Provide a path to a file in either `notes/` or `transcripts/`. The",
+    "agent will look up the sibling automatically via basename match. A",
+    "missing sibling is a normal case (notes-only or transcript-only) \u2014",
+    "the agent handles all three input cases.",
     "",
     "## Output",
     "",
-    "- An extraction markdown file with categorized meeting content",
+    "- A structured extraction at",
+    "  `<meetingsRoot>/insights/{type}/<basename>.md`",
     "- Phase issues with `meeting:*` labels for downstream agent sessions",
     "  to pick up (notes, draft, link)"
   ].join("\n")
@@ -11608,11 +11827,30 @@ function buildMeetingAnalysisBundle(tier = AGENT_MODEL.BALANCED) {
         content: [
           "# Meeting Processing Workflow",
           "",
-          "Use `/process-meeting <path>` to process a meeting transcript through a",
+          "Use `/process-meeting <path>` to process a meeting through a",
           "4-phase pipeline (extract \u2192 notes \u2192 draft \u2192 link). Each phase runs as a",
           "separate agent session tracked by a GitHub issue with a `meeting:*` label.",
           "See the `meeting-analyst` agent definition for full workflow details.",
           "",
+          "Meeting artifacts live in **three parallel trees** rooted at the",
+          "project's meetings root:",
+          "",
+          "- `transcripts/{internal,external}/` \u2014 verbatim transcripts (evidence)",
+          "- `notes/{internal,external}/` \u2014 curated narrative summary",
+          "  (input + Phase 2 output)",
+          "- `insights/{internal,external}/` \u2014 structured extraction (Phase 1 output)",
+          "",
+          "The three trees share identical basenames so a meeting's siblings",
+          "are looked up by filename, not by frontmatter cross-references.",
+          "Phase 1 accepts every input case (notes + transcript, notes only,",
+          "or transcript only) and Phase 2 enhances the notes file in place",
+          "rather than authoring it from scratch.",
+          "",
+          "Notes and insights files may carry optional frontmatter fields",
+          "`slug`, `source`, `transcript_available`, and `confidence`",
+          "alongside the existing `meeting_type` and `areas` fields. Missing",
+          "frontmatter is treated as a normal input case \u2014 never fail-loud.",
+          "",
           "Meeting notes may declare a `meeting_type` (one of the project's",
           "recognized types) and an `areas: [...]` list. The `meeting_type`",
           "resolves to a generic kind \u2014 `planning` / `review` / `brainstorm` /",