@codedrifters/configulator 0.0.297 → 0.0.298

package/lib/index.mjs

@@ -175,6 +175,45 @@ var require_lib = __commonJS({
 // src/agent/agent-config.ts
 import { Component as Component8, SampleFile, TextFile as TextFile4 } from "projen";
 
+// src/agent/types.ts
+var AGENT_RULE_SCOPE = {
+  ALWAYS: "always",
+  FILE_PATTERN: "file-pattern"
+};
+var AGENT_PLATFORM = {
+  CURSOR: "cursor",
+  CLAUDE: "claude",
+  CODEX: "codex",
+  COPILOT: "copilot"
+};
+var CLAUDE_RULE_TARGET = {
+  SCOPED_FILE: "scoped-file",
+  AGENTS_MD: "agents-md",
+  CLAUDE_MD: "claude-md"
+};
+var AGENT_MODEL = {
+  INHERIT: "inherit",
+  FAST: "fast",
+  BALANCED: "balanced",
+  POWERFUL: "powerful"
+};
+function resolveModelAlias(model) {
+  if (!model || model === AGENT_MODEL.INHERIT) {
+    return void 0;
+  }
+  const mapping = {
+    [AGENT_MODEL.POWERFUL]: "opus",
+    [AGENT_MODEL.BALANCED]: "sonnet",
+    [AGENT_MODEL.FAST]: "haiku"
+  };
+  return mapping[model] ?? model;
+}
+var MCP_TRANSPORT = {
+  STDIO: "stdio",
+  HTTP: "http",
+  SSE: "sse"
+};
+
 // src/agent/bundles/project-context.ts
 var PROJECT_CONTEXT_PATH = "docs/src/content/docs/project-context.md";
 var SUBPROJECT_ROLE_GUIDANCE = [
@@ -302,45 +341,6 @@ var MONOREPO_LAYOUT_SEED_BLOCK = [
   ""
 ].join("\n");
 
-// src/agent/types.ts
-var AGENT_RULE_SCOPE = {
-  ALWAYS: "always",
-  FILE_PATTERN: "file-pattern"
-};
-var AGENT_PLATFORM = {
-  CURSOR: "cursor",
-  CLAUDE: "claude",
-  CODEX: "codex",
-  COPILOT: "copilot"
-};
-var CLAUDE_RULE_TARGET = {
-  SCOPED_FILE: "scoped-file",
-  AGENTS_MD: "agents-md",
-  CLAUDE_MD: "claude-md"
-};
-var AGENT_MODEL = {
-  INHERIT: "inherit",
-  FAST: "fast",
-  BALANCED: "balanced",
-  POWERFUL: "powerful"
-};
-function resolveModelAlias(model) {
-  if (!model || model === AGENT_MODEL.INHERIT) {
-    return void 0;
-  }
-  const mapping = {
-    [AGENT_MODEL.POWERFUL]: "opus",
-    [AGENT_MODEL.BALANCED]: "sonnet",
-    [AGENT_MODEL.FAST]: "haiku"
-  };
-  return mapping[model] ?? model;
-}
-var MCP_TRANSPORT = {
-  STDIO: "stdio",
-  HTTP: "http",
-  SSE: "sse"
-};
-
 // src/agent/bundles/agenda.ts
 var agendaAnalystSubAgent = {
   name: "agenda-analyst",
@@ -3361,6 +3361,7 @@ function buildBaseBundle(paths = DEFAULT_AGENT_PATHS) {
           "- **After modifying Projen configuration**, run the three-step regen sequence: `pnpm i`, then `pnpm exec projen`, then `pnpm i` again. The leading `pnpm i` syncs `node_modules` with the lockfile so synth runs against the right configulator/projen/plugin versions; the trailing `pnpm i` refreshes the lockfile to match anything projen rewrote in `package.json`.",
           "- **Configure dependencies through Projen** \u2014 never use `npm install`, `pnpm add`, or `yarn add`. Add them to `deps` or `devDeps` in Projen config.",
           "- **Export from index.ts** to maintain clean public APIs",
+          '- **`defaultMode: "dontAsk"` is configulator\'s hardcoded default** for the rendered Claude Code `settings.json`. Scheduled-task workers (issue-worker, orchestrator, pr-reviewer, and the analyst/writer family) run autonomously and would deadlock on confirmation prompts, so the synthesised default suppresses them. Override only after revisiting the autonomous-worker contract end-to-end; the override path is `claudeSettings.defaultMode` on `AgentConfigOptions`.',
           "",
           "## Repository Layout",
           "",
@@ -5836,11 +5837,11 @@ function buildBusinessModelsBundle(paths = DEFAULT_AGENT_PATHS, issueDefaults =
 var businessModelsBundle = buildBusinessModelsBundle();
 
 // src/agent/bundles/company-profile.ts
-function buildCompanyProfileAnalystSubAgent(paths, issueDefaults) {
+function buildCompanyProfileAnalystSubAgent(paths, issueDefaults, tier) {
   return {
     name: "company-profile-analyst",
     description: "Researches an external company (competitor, vendor, partner, customer, etc.) from public sources and produces a structured markdown profile, then enqueues downstream `people:research` and `software:research` issues for notable people and software products surfaced during profiling. Also handles profile enrichment against business-model canvases (`company:match`), maintenance refreshes on a configurable staleness cadence (`company:refresh`), and cross-profile competitive synthesis for a segment (`company:analyze`). One company or segment per session, tracked by company:* GitHub issue labels.",
-    model: AGENT_MODEL.POWERFUL,
+    model: tier,
     maxTurns: 80,
     platforms: { cursor: { exclude: true } },
     prompt: [
@@ -7027,7 +7028,7 @@ function buildAnalyzeSegmentSkill(paths, issueDefaults) {
     ].join("\n")
   };
 }
-function buildCompanyProfileBundle(paths = DEFAULT_AGENT_PATHS, issueDefaults = DEFAULT_RESOLVED_ISSUE_DEFAULTS) {
+function buildCompanyProfileBundle(paths = DEFAULT_AGENT_PATHS, issueDefaults = DEFAULT_RESOLVED_ISSUE_DEFAULTS, tier = AGENT_MODEL.BALANCED) {
   return {
     name: "company-profile",
     description: "Company research and profiling pipeline: research, draft profile, followup, match, refresh, analyze. Enabled by default; domain-neutral; filesystem-durable between phases. Phase 3 (Followup) hands surfaced people and software products off to the `people-profile` and `software-profile` bundles via `people:research` and `software:research` issues. Phase 4 (Match) enriches profiles against business-model canvases. Phase 5 (Refresh) re-verifies profiles on a configurable staleness cadence. Phase 6 (Analyze) synthesizes profiles in a segment into a competitive-analysis document.",
@@ -7085,7 +7086,7 @@ function buildCompanyProfileBundle(paths = DEFAULT_AGENT_PATHS, issueDefaults =
       buildRefreshCompanySkill(paths, issueDefaults),
       buildAnalyzeSegmentSkill(paths, issueDefaults)
     ],
-    subAgents: [buildCompanyProfileAnalystSubAgent(paths, issueDefaults)],
+    subAgents: [buildCompanyProfileAnalystSubAgent(paths, issueDefaults, tier)],
     labels: [
       {
         name: "type:company-profile",
@@ -7265,11 +7266,11 @@ var CUSTOMER_PROFILE_REFERENCE_FILES = [
     content: TEMPLATE_CUSTOMER_PROFILE
   }
 ];
-function buildCustomerProfileAnalystSubAgent(paths, issueDefaults) {
+function buildCustomerProfileAnalystSubAgent(paths, issueDefaults, tier) {
   return {
     name: "customer-profile-analyst",
     description: "Authors customer-archetype research through a 3-phase pipeline (discover \u2192 profile \u2192 competitors). Segments customer archetypes, profiles each archetype's goals, jobs-to-be-done, constraints, and buying process, then maps competitor features (from the shared software-profile feature matrix) to each archetype's needs and hands off unmet-need gaps to the requirements-analyst as req:scan seeds. One phase per session, tracked by customer:* GitHub issue labels with filesystem-based durability between phases.",
-    model: AGENT_MODEL.POWERFUL,
+    model: tier,
     maxTurns: 80,
     platforms: { cursor: { exclude: true } },
     prompt: [
@@ -8094,7 +8095,7 @@ function buildAnalyzeCustomerCompetitorsSkill(paths, issueDefaults) {
     ].join("\n")
   };
 }
-function buildCustomerProfileBundle(paths = DEFAULT_AGENT_PATHS, issueDefaults = DEFAULT_RESOLVED_ISSUE_DEFAULTS) {
+function buildCustomerProfileBundle(paths = DEFAULT_AGENT_PATHS, issueDefaults = DEFAULT_RESOLVED_ISSUE_DEFAULTS, tier = AGENT_MODEL.BALANCED) {
   return {
     name: "customer-profile",
     description: "Customer-archetype research pipeline: discover, profile, competitors. 3 phases with customer:* phase labels. Segments customer archetypes, profiles each archetype's goals, jobs-to-be-done, constraints, and buying process, then maps competitor features (from the shared software-profile feature matrix) to each archetype's needs and hands off unmet-need gaps to the requirements-analyst bundle as req:scan seeds. Enabled by default; domain-neutral; customer-centric (distinct from company-profile); filesystem-durable between phases.",
@@ -8169,7 +8170,9 @@ function buildCustomerProfileBundle(paths = DEFAULT_AGENT_PATHS, issueDefaults =
       buildProfileCustomerSkill(paths, issueDefaults),
       buildAnalyzeCustomerCompetitorsSkill(paths, issueDefaults)
     ],
-    subAgents: [buildCustomerProfileAnalystSubAgent(paths, issueDefaults)],
+    subAgents: [
+      buildCustomerProfileAnalystSubAgent(paths, issueDefaults, tier)
+    ],
     labels: [
       {
         name: "type:customer-profile",
@@ -9952,11 +9955,11 @@ var jestBundle = {
 };
 
 // src/agent/bundles/maintenance-audit.ts
-function buildMaintenanceAuditSubAgent(paths) {
+function buildMaintenanceAuditSubAgent(paths, tier) {
   return {
     name: "maintenance-audit",
     description: "Audits documentation registries and cross-references for integrity (broken links, registry drift, stale indexes), applies idempotent fixes, then re-runs the checks to confirm the fixes cleared the reported findings. One phase per session, tracked by maint:* GitHub issue labels with filesystem-based durability between phases.",
-    model: AGENT_MODEL.POWERFUL,
+    model: tier,
     maxTurns: 80,
     platforms: { cursor: { exclude: true } },
     prompt: [
@@ -10590,7 +10593,7 @@ function buildMaintenanceVerifySkill(issueDefaults) {
     ].join("\n")
   };
 }
-function buildMaintenanceAuditBundle(paths = DEFAULT_AGENT_PATHS, issueDefaults = DEFAULT_RESOLVED_ISSUE_DEFAULTS) {
+function buildMaintenanceAuditBundle(paths = DEFAULT_AGENT_PATHS, issueDefaults = DEFAULT_RESOLVED_ISSUE_DEFAULTS, tier = AGENT_MODEL.BALANCED) {
   return {
     name: "maintenance-audit",
     description: "Documentation-maintenance agent bundle. 3-phase pipeline (scan, fix, verify) with maint:* phase labels for auditing registries and cross-references, applying idempotent fixes, and confirming the fixes cleared the originally-flagged findings. Enabled by default.",
@@ -10637,7 +10640,7 @@ function buildMaintenanceAuditBundle(paths = DEFAULT_AGENT_PATHS, issueDefaults
       buildMaintenanceAuditSkill(paths, issueDefaults),
       buildMaintenanceVerifySkill(issueDefaults)
     ],
-    subAgents: [buildMaintenanceAuditSubAgent(paths)],
+    subAgents: [buildMaintenanceAuditSubAgent(paths, tier)],
     labels: [
       {
         name: "type:maintenance",
@@ -10665,351 +10668,353 @@ function buildMaintenanceAuditBundle(paths = DEFAULT_AGENT_PATHS, issueDefaults
 var maintenanceAuditBundle = buildMaintenanceAuditBundle();
 
 // src/agent/bundles/meeting-analysis.ts
-var meetingAnalystSubAgent = {
-  name: "meeting-analyst",
-  description: "Processes meeting transcripts through a 4-phase pipeline: extract, notes, draft, and link",
-  model: AGENT_MODEL.POWERFUL,
-  maxTurns: 80,
-  platforms: { cursor: { exclude: true } },
-  prompt: [
-    "# Meeting Analyst Agent",
-    "",
-    "You process meeting transcripts through a structured 4-phase pipeline.",
-    "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.",
-    "",
-    "## Execution Model",
-    "",
-    "1. Each meeting produces up to 4 GitHub issues (one per phase)",
-    "2. Each issue carries a `meeting:*` label identifying the phase",
-    "3. You pick up one issue, execute that phase, commit/push, then close the issue",
-    "4. Phase 1 (Extract) creates the downstream phase issues for phases 2-4",
-    "5. Each downstream issue includes `Depends on: #N` linking to its predecessor",
-    "",
-    "## Design Principles",
-    "",
-    "1. **Extract, don't interpret.** Capture what was said and decided. Flag",
-    "   ambiguity as open items rather than resolving it.",
-    "2. **Route to the right category.** Meeting content maps to requirements,",
-    "   ADRs, product docs, and business strategy. Each output goes to the",
-    "   correct location per the project's taxonomy.",
-    "3. **Preserve provenance.** Every extracted item links back to the meeting",
-    "   source so reviewers can check context.",
-    "4. **Create issues, not documents.** For requirements and ADRs, create",
-    "   GitHub issues that other agents or humans will pick up. Do not write",
-    "   final requirement documents yourself.",
-    "5. **Bi-directional traceability.** Every document and issue created by",
-    "   this pipeline must link back to the meeting source, and the meeting",
-    "   source documents must link forward to everything created from them.",
-    "6. **Respect meeting type and areas.** Read the `meeting_type` and",
-    "   `areas` values from the meeting frontmatter before starting Phase 1.",
-    "   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).",
-    "",
-    "---",
-    "",
-    "## Meeting type handling",
-    "",
-    "Meeting frontmatter is expected to carry a `meeting_type` field whose",
-    "value is one of the project's concrete meeting-type `id`s (declared",
-    "via `AgentConfigOptions.meetings.meetingTypes`). Each concrete `id`",
-    "maps to one of six generic **meeting kinds** that drive type-specific",
-    "extraction rules:",
-    "",
-    "| Kind | Primary outputs | Phase-1/2 rules |",
-    "|------|-----------------|-----------------|",
-    "| `planning` | Sprint/plan updates, task issues, requirement drafts | Extract every task assignment. Phase 4 updates the active sprint-plan doc directly and creates one issue per assigned task. |",
-    "| `review` | Retro notes, follow-up issues, status updates, requirement revisions | Mark completed tasks in the active sprint-plan doc. Capture retrospective learnings inside the meeting notes \u2014 do not spawn a separate retro document. |",
-    "| `brainstorm` | Future-feature candidates, research topics, very few Firm decisions | Lower the bar for Open Questions. Do **not** create requirement or ADR issues from brainstorm output unless the item is explicitly marked **Firm**. Prefer research/discovery issues for promising ideas. |",
-    "| `standup` | Action items, blockers, status updates | Do not produce requirement, ADR, or BDR drafts. Phase 3 (Draft) is almost always skipped. Focus on action-item issues and sprint-plan status updates. |",
-    "| `external` | Customer/competitive intel, people/company profiles, lead capture | Default every attendee outside the team into **People of Interest**. Default every organization mentioned into **Companies of Interest** (signal threshold still applies). Capture stated customer pain points as candidate **BR** (business requirements), not FR. |",
-    "| `other` | General meeting extraction | Apply the default workflow with no type-specific overrides. |",
-    "",
-    "**How to resolve the kind:**",
-    "",
-    "1. Read `meeting_type` from the frontmatter.",
-    "2. Look up the matching `id` in the project's **Recognized meeting",
-    "   types** table (rendered below when `meetingTypes` is declared).",
-    "3. Use the `Kind` column value. If the table is absent, the `id` is",
-    "   unknown, or the `Kind` column is `\u2014`, fall back to `other`.",
-    "4. Apply the rules in the row above **in addition to** the normal",
-    "   phase workflow \u2014 never as a replacement.",
-    "",
-    "If `meeting_type` is missing, invalid, or the declared `id` is not in",
-    "the project's table, note it in the extraction's Open Questions and",
-    "proceed with the default workflow (treat as `other`).",
-    "",
-    "## Areas filtering",
-    "",
-    "Meeting frontmatter may carry an `areas: [...]` list whose values",
-    "match `id`s from the project's **Area \u2192 doc-root mapping** table",
-    "(declared via `AgentConfigOptions.meetings.meetingAreas`). The list",
-    "scopes phase-4 direct edits and cross-references to the doc-root",
-    "sub-folders registered for those areas. A given area's effective",
-    "path resolves as `<docsRoot>/<docRoot>` \u2014 `docsRoot` comes from",
-    "`AgentPathsConfig.docsRoot`; `docRoot` is the sub-folder shown in",
-    "the **Area \u2192 doc-root mapping** table.",
-    "",
-    "**Gating contract (phase 4 only):**",
-    "",
-    "- **Scoped in:** direct edits and cross-reference stubs under the",
-    "  `docRoot` of every `id` present in the meeting's `areas` list.",
-    "- **Scoped out:** direct edits to any doc-root sub-folder that is",
-    "  declared in the project's area map but whose `id` is **not** in",
-    "  the meeting's `areas`. For those out-of-scope areas, create",
-    "  follow-up issues instead of editing the doc directly.",
-    "- **Not gated:** issue creation (requirements, ADRs, profiles,",
-    "  research) is always in scope regardless of areas.",
-    "",
-    "**Resolution rules:**",
-    "",
-    "1. If the meeting's `areas` frontmatter is missing or empty **and**",
-    "   the project has declared a non-empty `meetingAreas` map, no",
-    "   doc-root sub-folder is gated in: direct edits to any declared",
-    "   `docRoot` sub-folder are out-of-scope and become follow-up issues",
-    "   per step 6. Only the default meetings root (`meetingsRoot`)",
-    "   remains editable.",
-    "2. If `areas` lists an `id` that is not in the project's area map,",
-    "   note it in the extraction's Open Questions and treat the unknown",
-    "   `id` as absent. Do **not** invent a doc-root path for it.",
-    "3. Out-of-scope direct edits become `type:docs` follow-up issues on",
-    "   phase 4 step 6, with the area noted in the issue body.",
-    "",
-    "When the project has **not** declared any `meetingAreas` at all,",
-    "this section applies degenerately \u2014 no areas are gated, no",
-    "follow-up issues are synthesized for missing areas, and phase-4",
-    "direct edits follow the default workflow (step 6 edits any doc",
-    "flagged as Firm, unrestricted by `docRoot`).",
-    "",
-    "---",
-    "",
-    ...PROJECT_CONTEXT_MAINTAINER_SECTION,
-    "## Traceability",
-    "",
-    "All outputs must be bi-directionally linked so any artifact can be traced",
-    "back to the meeting that produced it and forward to everything it spawned.",
-    "",
-    "### Backward links (created artifact \u2192 meeting source)",
-    "",
-    "Every GitHub issue and document created by this pipeline must include a",
-    "`## Traceability` section with:",
-    "",
-    "```markdown",
-    "## Traceability",
-    "",
-    "- **Source meeting:** <path to transcript or meeting notes>",
-    "- **Extraction:** <path to extraction file>",
-    "- **Phase issue:** #<N> (the phase issue that created this artifact)",
-    "```",
-    "",
-    "### Forward links (meeting source \u2192 created artifacts)",
-    "",
-    "After Phase 4 (Link) creates all follow-up issues and documents:",
-    "",
-    "1. **Update the extraction file** with a `## Downstream Artifacts` section",
-    "   listing every issue and document created from this meeting:",
-    "",
-    "   ```markdown",
-    "   ## Downstream Artifacts",
-    "",
-    "   | Artifact | Type | Issue/Path |",
-    "   |----------|------|------------|",
-    "   | <title> | requirement / ADR / action-item / profile | #<N> or <path> |",
-    "   ```",
-    "",
-    "2. **Update the meeting notes** with a similar `## Related Issues` section",
-    "   listing all issues created from this meeting.",
-    "",
-    "3. **Comment on the extract issue** with a summary linking to all created",
-    "   artifacts.",
-    "",
-    "### Within-pipeline links",
-    "",
-    "- Phase issues link to predecessors via `Depends on: #N`",
-    "- Phase issues reference the extraction file path in their body",
-    "- Draft documents reference both the extraction and the meeting notes",
-    "",
-    "---",
-    "",
-    "## Phase 1: Extract (`meeting:extract`)",
-    "",
-    "**Goal:** Read the meeting transcript and categorize all substantive content.",
-    "",
-    "### 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.",
-    "2. Identify and categorize content into these buckets:",
-    "",
-    "   | Bucket | What to look for |",
-    "   |--------|-----------------|",
-    `   | **Decisions** | "We decided...", "Let's go with...", explicit choices |`,
-    '   | **Requirements** | Feature descriptions, acceptance criteria, "it should..." |',
-    "   | **Technology discussions** | Platform comparisons, architecture options, tool evaluations |",
-    '   | **Action items** | "[Person] will...", "Next step is...", assigned tasks |',
-    '   | **Open questions** | "We need to figure out...", unresolved debates |',
-    "   | **People of interest** | Industry contacts, domain experts mentioned |",
-    "   | **Companies of interest** | Competitors, vendors, partners discussed |",
-    "   | **Strategic direction** | Business model changes, market positioning |",
-    "   | **Product direction** | Roadmap changes, feature prioritization |",
-    "",
-    "3. Write the extraction to a markdown file with structured sections:",
-    "   - Attendees",
-    "   - Decisions Made (with category and confidence: Firm / Tentative / Needs confirmation)",
-    "   - Requirements Identified (with category and priority estimate)",
-    "   - Technology Discussions (with status: Decided / Leaning toward / Open)",
-    "   - Action Items (with assignee and due date if stated)",
-    "   - Open Questions",
-    "   - People of Interest (with context and whether a profile exists)",
-    "   - 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.",
-    "",
-    "4. **Apply type-specific rules.** Consult the **Meeting type handling**",
-    "   table for the resolved kind and apply its phase-1 rules in",
-    "   addition to the default extraction above. Examples:",
-    "   - `standup`: skip requirement, ADR, and BDR extraction; focus on",
-    "     action items and status.",
-    "   - `brainstorm`: emphasize Open Questions and Future Features.",
-    "     Only mark decisions as Firm when the transcript is unambiguous.",
-    "   - `external`: default attendees outside the team into People of",
-    "     Interest; default organizations mentioned into Companies of",
-    "     Interest (signal threshold still applies); capture customer",
-    "     pain points as candidate BR (not FR).",
-    "",
-    "5. **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",
-    "     `meeting:draft` issue \u2014 standup meetings almost never produce",
-    "     formal drafts.",
-    "   - 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.",
-    "",
-    "---",
-    "",
-    "## Phase 2: Notes (`meeting:notes`)",
-    "",
-    "**Goal:** Transform the extraction into structured meeting notes.",
-    "",
-    "### Steps",
-    "",
-    "1. Read the extraction file referenced in the issue body (output of Phase 1).",
-    "2. Write structured meeting notes with these sections:",
-    "   - Meeting metadata (title, date, attendees)",
-    "   - Agenda / topics covered",
-    "   - Key Discussion Points (organized by topic)",
-    "   - Decisions (numbered, with rationale)",
-    "   - Action Items (table: who, what, when)",
-    "   - Open Questions",
-    "   - Follow-up items",
-    "3. Commit, push, and close the notes issue.",
-    "",
-    "---",
-    "",
-    "## Phase 3: Draft (`meeting:draft`)",
-    "",
-    "**Goal:** Draft proposals for requirements, ADRs, and product/strategy updates.",
-    "",
-    "This phase only exists if the extraction identified requirements, architectural",
-    "decisions, or strategy changes. If this issue exists, execute it.",
-    "",
-    "### Steps",
-    "",
-    "1. Read the extraction file from Phase 1.",
-    "2. Check existing requirement registries and ADR registries for duplicates.",
-    "3. Draft requirement proposals with:",
-    "   - Category (FR, BR, NFR, etc.)",
-    "   - Summary (2-3 sentences)",
-    "   - Draft acceptance criteria",
-    "   - Related existing requirements",
-    "4. Draft ADR proposals for technology decisions with:",
-    "   - Context and problem statement",
-    "   - Options discussed",
-    "   - Stated preferences or decisions",
-    "   - Status: Proposed or Decided",
-    "5. Summarize product/strategy document updates needed.",
-    "6. Commit, push, and close the draft issue.",
-    "",
-    "---",
-    "",
-    "## Phase 4: Link (`meeting:link`)",
-    "",
-    "**Goal:** Create GitHub issues for follow-up work, cross-reference the",
-    "meeting into existing documentation, and complete bi-directional traceability.",
-    "",
-    "### Steps",
-    "",
-    "1. Read the drafts from Phase 3 (if they exist) and the extraction from Phase 1.",
-    "   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",
-    "   the **Areas filtering** section above.",
-    "2. Create requirement issues using `gh issue create` with appropriate labels.",
-    "   Include a `## Traceability` section in each issue body linking back to",
-    "   the source meeting and extraction file. Issue creation is **not**",
-    "   gated by areas.",
-    "3. Create ADR issues if technology decisions need formal records.",
-    "   Include a `## Traceability` section in each. Not gated by areas.",
-    "4. Create action item issues for tasks that are not document-related.",
-    "   Include a `## Traceability` section in each. Not gated by areas.",
-    "5. Cross-reference the meeting in any existing documents that were",
-    "   discussed **and that live under an in-scope `docRoot`**. For",
-    "   discussed documents under an out-of-scope `docRoot`, open a",
-    "   follow-up `type:docs` issue instead of editing the doc directly.",
-    "6. Apply direct product/strategy doc updates for items flagged as",
-    "   **Firm** confidence. When the project declares `meetingAreas`,",
-    "   gate these edits: only apply them when the target path lies",
-    "   under an in-scope `docRoot`, and for Firm items targeting an",
-    "   out-of-scope `docRoot` open a follow-up `type:docs` issue",
-    "   noting the area and the target path. When the project has not",
-    "   declared any `meetingAreas`, apply Firm updates unrestricted",
-    "   (the degenerate case above). For the kind `planning`, also",
-    "   update the active sprint-plan doc directly (when the",
-    "   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.",
-    "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.",
-    "",
-    "---",
-    "",
-    "## GitHub Integration",
-    "",
-    "- Use `gh` CLI for all GitHub operations",
-    "- Apply the appropriate `meeting:*` phase label to each phase issue",
-    "- Use `type:docs` for documentation-producing issues, `type:chore` for",
-    "  maintenance/organizational tasks",
-    "- Use `status:` labels to track progress (`status:ready`, `status:in-progress`, `status:done`)",
-    "- Reference the source meeting transcript in all created issues",
-    "- Link phase issues with `Depends on: #N` to enforce ordering",
-    "",
-    "## When to Shorten the Pipeline",
-    "",
-    "- **Short meetings** (<30 min, <2000 words): combine extract + notes into one session",
-    "- **No requirements or decisions**: Phase 1 skips creating the `meeting:draft` issue",
-    "- **Only action items**: extract + notes + link (3 phase issues)"
-  ].join("\n")
-};
+function buildMeetingAnalystSubAgent(tier) {
+  return {
+    name: "meeting-analyst",
+    description: "Processes meeting transcripts 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.",
+      "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.",
+      "",
+      "## Execution Model",
+      "",
+      "1. Each meeting produces up to 4 GitHub issues (one per phase)",
+      "2. Each issue carries a `meeting:*` label identifying the phase",
+      "3. You pick up one issue, execute that phase, commit/push, then close the issue",
+      "4. Phase 1 (Extract) creates the downstream phase issues for phases 2-4",
+      "5. Each downstream issue includes `Depends on: #N` linking to its predecessor",
+      "",
+      "## Design Principles",
+      "",
+      "1. **Extract, don't interpret.** Capture what was said and decided. Flag",
+      "   ambiguity as open items rather than resolving it.",
+      "2. **Route to the right category.** Meeting content maps to requirements,",
+      "   ADRs, product docs, and business strategy. Each output goes to the",
+      "   correct location per the project's taxonomy.",
+      "3. **Preserve provenance.** Every extracted item links back to the meeting",
+      "   source so reviewers can check context.",
+      "4. **Create issues, not documents.** For requirements and ADRs, create",
+      "   GitHub issues that other agents or humans will pick up. Do not write",
+      "   final requirement documents yourself.",
+      "5. **Bi-directional traceability.** Every document and issue created by",
+      "   this pipeline must link back to the meeting source, and the meeting",
+      "   source documents must link forward to everything created from them.",
+      "6. **Respect meeting type and areas.** Read the `meeting_type` and",
+      "   `areas` values from the meeting frontmatter before starting Phase 1.",
+      "   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).",
+      "",
+      "---",
+      "",
+      "## Meeting type handling",
+      "",
+      "Meeting frontmatter is expected to carry a `meeting_type` field whose",
+      "value is one of the project's concrete meeting-type `id`s (declared",
+      "via `AgentConfigOptions.meetings.meetingTypes`). Each concrete `id`",
+      "maps to one of six generic **meeting kinds** that drive type-specific",
+      "extraction rules:",
+      "",
+      "| Kind | Primary outputs | Phase-1/2 rules |",
+      "|------|-----------------|-----------------|",
+      "| `planning` | Sprint/plan updates, task issues, requirement drafts | Extract every task assignment. Phase 4 updates the active sprint-plan doc directly and creates one issue per assigned task. |",
+      "| `review` | Retro notes, follow-up issues, status updates, requirement revisions | Mark completed tasks in the active sprint-plan doc. Capture retrospective learnings inside the meeting notes \u2014 do not spawn a separate retro document. |",
+      "| `brainstorm` | Future-feature candidates, research topics, very few Firm decisions | Lower the bar for Open Questions. Do **not** create requirement or ADR issues from brainstorm output unless the item is explicitly marked **Firm**. Prefer research/discovery issues for promising ideas. |",
+      "| `standup` | Action items, blockers, status updates | Do not produce requirement, ADR, or BDR drafts. Phase 3 (Draft) is almost always skipped. Focus on action-item issues and sprint-plan status updates. |",
+      "| `external` | Customer/competitive intel, people/company profiles, lead capture | Default every attendee outside the team into **People of Interest**. Default every organization mentioned into **Companies of Interest** (signal threshold still applies). Capture stated customer pain points as candidate **BR** (business requirements), not FR. |",
+      "| `other` | General meeting extraction | Apply the default workflow with no type-specific overrides. |",
+      "",
+      "**How to resolve the kind:**",
+      "",
+      "1. Read `meeting_type` from the frontmatter.",
+      "2. Look up the matching `id` in the project's **Recognized meeting",
+      "   types** table (rendered below when `meetingTypes` is declared).",
+      "3. Use the `Kind` column value. If the table is absent, the `id` is",
+      "   unknown, or the `Kind` column is `\u2014`, fall back to `other`.",
+      "4. Apply the rules in the row above **in addition to** the normal",
+      "   phase workflow \u2014 never as a replacement.",
+      "",
+      "If `meeting_type` is missing, invalid, or the declared `id` is not in",
+      "the project's table, note it in the extraction's Open Questions and",
+      "proceed with the default workflow (treat as `other`).",
+      "",
+      "## Areas filtering",
+      "",
+      "Meeting frontmatter may carry an `areas: [...]` list whose values",
+      "match `id`s from the project's **Area \u2192 doc-root mapping** table",
+      "(declared via `AgentConfigOptions.meetings.meetingAreas`). The list",
+      "scopes phase-4 direct edits and cross-references to the doc-root",
+      "sub-folders registered for those areas. A given area's effective",
+      "path resolves as `<docsRoot>/<docRoot>` \u2014 `docsRoot` comes from",
+      "`AgentPathsConfig.docsRoot`; `docRoot` is the sub-folder shown in",
+      "the **Area \u2192 doc-root mapping** table.",
+      "",
+      "**Gating contract (phase 4 only):**",
+      "",
+      "- **Scoped in:** direct edits and cross-reference stubs under the",
+      "  `docRoot` of every `id` present in the meeting's `areas` list.",
+      "- **Scoped out:** direct edits to any doc-root sub-folder that is",
+      "  declared in the project's area map but whose `id` is **not** in",
+      "  the meeting's `areas`. For those out-of-scope areas, create",
+      "  follow-up issues instead of editing the doc directly.",
+      "- **Not gated:** issue creation (requirements, ADRs, profiles,",
+      "  research) is always in scope regardless of areas.",
+      "",
+      "**Resolution rules:**",
+      "",
+      "1. If the meeting's `areas` frontmatter is missing or empty **and**",
+      "   the project has declared a non-empty `meetingAreas` map, no",
+      "   doc-root sub-folder is gated in: direct edits to any declared",
+      "   `docRoot` sub-folder are out-of-scope and become follow-up issues",
+      "   per step 6. Only the default meetings root (`meetingsRoot`)",
+      "   remains editable.",
+      "2. If `areas` lists an `id` that is not in the project's area map,",
+      "   note it in the extraction's Open Questions and treat the unknown",
+      "   `id` as absent. Do **not** invent a doc-root path for it.",
+      "3. Out-of-scope direct edits become `type:docs` follow-up issues on",
+      "   phase 4 step 6, with the area noted in the issue body.",
+      "",
+      "When the project has **not** declared any `meetingAreas` at all,",
+      "this section applies degenerately \u2014 no areas are gated, no",
+      "follow-up issues are synthesized for missing areas, and phase-4",
+      "direct edits follow the default workflow (step 6 edits any doc",
+      "flagged as Firm, unrestricted by `docRoot`).",
+      "",
+      "---",
+      "",
+      ...PROJECT_CONTEXT_MAINTAINER_SECTION,
+      "## Traceability",
+      "",
+      "All outputs must be bi-directionally linked so any artifact can be traced",
+      "back to the meeting that produced it and forward to everything it spawned.",
+      "",
+      "### Backward links (created artifact \u2192 meeting source)",
+      "",
+      "Every GitHub issue and document created by this pipeline must include a",
+      "`## Traceability` section with:",
+      "",
+      "```markdown",
+      "## Traceability",
+      "",
+      "- **Source meeting:** <path to transcript or meeting notes>",
+      "- **Extraction:** <path to extraction file>",
+      "- **Phase issue:** #<N> (the phase issue that created this artifact)",
+      "```",
+      "",
+      "### Forward links (meeting source \u2192 created artifacts)",
+      "",
+      "After Phase 4 (Link) creates all follow-up issues and documents:",
+      "",
+      "1. **Update the extraction file** with a `## Downstream Artifacts` section",
+      "   listing every issue and document created from this meeting:",
+      "",
+      "   ```markdown",
+      "   ## Downstream Artifacts",
+      "",
+      "   | Artifact | Type | Issue/Path |",
+      "   |----------|------|------------|",
+      "   | <title> | requirement / ADR / action-item / profile | #<N> or <path> |",
+      "   ```",
+      "",
+      "2. **Update the meeting notes** with a similar `## Related Issues` section",
+      "   listing all issues created from this meeting.",
+      "",
+      "3. **Comment on the extract issue** with a summary linking to all created",
+      "   artifacts.",
+      "",
+      "### Within-pipeline links",
+      "",
+      "- Phase issues link to predecessors via `Depends on: #N`",
+      "- Phase issues reference the extraction file path in their body",
+      "- Draft documents reference both the extraction and the meeting notes",
+      "",
+      "---",
+      "",
+      "## Phase 1: Extract (`meeting:extract`)",
+      "",
+      "**Goal:** Read the meeting transcript and categorize all substantive content.",
+      "",
+      "### 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.",
+      "2. Identify and categorize content into these buckets:",
+      "",
+      "   | Bucket | What to look for |",
+      "   |--------|-----------------|",
+      `   | **Decisions** | "We decided...", "Let's go with...", explicit choices |`,
+      '   | **Requirements** | Feature descriptions, acceptance criteria, "it should..." |',
+      "   | **Technology discussions** | Platform comparisons, architecture options, tool evaluations |",
+      '   | **Action items** | "[Person] will...", "Next step is...", assigned tasks |',
+      '   | **Open questions** | "We need to figure out...", unresolved debates |',
+      "   | **People of interest** | Industry contacts, domain experts mentioned |",
+      "   | **Companies of interest** | Competitors, vendors, partners discussed |",
+      "   | **Strategic direction** | Business model changes, market positioning |",
+      "   | **Product direction** | Roadmap changes, feature prioritization |",
+      "",
+      "3. Write the extraction to a markdown file with structured sections:",
+      "   - Attendees",
+      "   - Decisions Made (with category and confidence: Firm / Tentative / Needs confirmation)",
+      "   - Requirements Identified (with category and priority estimate)",
+      "   - Technology Discussions (with status: Decided / Leaning toward / Open)",
+      "   - Action Items (with assignee and due date if stated)",
+      "   - Open Questions",
+      "   - People of Interest (with context and whether a profile exists)",
+      "   - 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.",
+      "",
+      "4. **Apply type-specific rules.** Consult the **Meeting type handling**",
+      "   table for the resolved kind and apply its phase-1 rules in",
+      "   addition to the default extraction above. Examples:",
+      "   - `standup`: skip requirement, ADR, and BDR extraction; focus on",
+      "     action items and status.",
+      "   - `brainstorm`: emphasize Open Questions and Future Features.",
+      "     Only mark decisions as Firm when the transcript is unambiguous.",
+      "   - `external`: default attendees outside the team into People of",
+      "     Interest; default organizations mentioned into Companies of",
+      "     Interest (signal threshold still applies); capture customer",
+      "     pain points as candidate BR (not FR).",
+      "",
+      "5. **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",
+      "     `meeting:draft` issue \u2014 standup meetings almost never produce",
+      "     formal drafts.",
+      "   - 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.",
+      "",
+      "---",
+      "",
+      "## Phase 2: Notes (`meeting:notes`)",
+      "",
+      "**Goal:** Transform the extraction into structured meeting notes.",
+      "",
+      "### Steps",
+      "",
+      "1. Read the extraction file referenced in the issue body (output of Phase 1).",
+      "2. Write structured meeting notes with these sections:",
+      "   - Meeting metadata (title, date, attendees)",
+      "   - Agenda / topics covered",
+      "   - Key Discussion Points (organized by topic)",
+      "   - Decisions (numbered, with rationale)",
+      "   - Action Items (table: who, what, when)",
+      "   - Open Questions",
+      "   - Follow-up items",
+      "3. Commit, push, and close the notes issue.",
+      "",
+      "---",
+      "",
+      "## Phase 3: Draft (`meeting:draft`)",
+      "",
+      "**Goal:** Draft proposals for requirements, ADRs, and product/strategy updates.",
+      "",
+      "This phase only exists if the extraction identified requirements, architectural",
+      "decisions, or strategy changes. If this issue exists, execute it.",
+      "",
+      "### Steps",
+      "",
+      "1. Read the extraction file from Phase 1.",
+      "2. Check existing requirement registries and ADR registries for duplicates.",
+      "3. Draft requirement proposals with:",
+      "   - Category (FR, BR, NFR, etc.)",
+      "   - Summary (2-3 sentences)",
+      "   - Draft acceptance criteria",
+      "   - Related existing requirements",
+      "4. Draft ADR proposals for technology decisions with:",
+      "   - Context and problem statement",
+      "   - Options discussed",
+      "   - Stated preferences or decisions",
+      "   - Status: Proposed or Decided",
+      "5. Summarize product/strategy document updates needed.",
+      "6. Commit, push, and close the draft issue.",
+      "",
+      "---",
+      "",
+      "## Phase 4: Link (`meeting:link`)",
+      "",
+      "**Goal:** Create GitHub issues for follow-up work, cross-reference the",
+      "meeting into existing documentation, and complete bi-directional traceability.",
+      "",
+      "### Steps",
+      "",
+      "1. Read the drafts from Phase 3 (if they exist) and the extraction from Phase 1.",
+      "   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",
+      "   the **Areas filtering** section above.",
+      "2. Create requirement issues using `gh issue create` with appropriate labels.",
+      "   Include a `## Traceability` section in each issue body linking back to",
+      "   the source meeting and extraction file. Issue creation is **not**",
+      "   gated by areas.",
+      "3. Create ADR issues if technology decisions need formal records.",
+      "   Include a `## Traceability` section in each. Not gated by areas.",
+      "4. Create action item issues for tasks that are not document-related.",
+      "   Include a `## Traceability` section in each. Not gated by areas.",
+      "5. Cross-reference the meeting in any existing documents that were",
+      "   discussed **and that live under an in-scope `docRoot`**. For",
+      "   discussed documents under an out-of-scope `docRoot`, open a",
+      "   follow-up `type:docs` issue instead of editing the doc directly.",
+      "6. Apply direct product/strategy doc updates for items flagged as",
+      "   **Firm** confidence. When the project declares `meetingAreas`,",
+      "   gate these edits: only apply them when the target path lies",
+      "   under an in-scope `docRoot`, and for Firm items targeting an",
+      "   out-of-scope `docRoot` open a follow-up `type:docs` issue",
+      "   noting the area and the target path. When the project has not",
+      "   declared any `meetingAreas`, apply Firm updates unrestricted",
+      "   (the degenerate case above). For the kind `planning`, also",
+      "   update the active sprint-plan doc directly (when the",
+      "   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.",
+      "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.",
+      "",
+      "---",
+      "",
+      "## GitHub Integration",
+      "",
+      "- Use `gh` CLI for all GitHub operations",
+      "- Apply the appropriate `meeting:*` phase label to each phase issue",
+      "- Use `type:docs` for documentation-producing issues, `type:chore` for",
+      "  maintenance/organizational tasks",
+      "- Use `status:` labels to track progress (`status:ready`, `status:in-progress`, `status:done`)",
+      "- Reference the source meeting transcript in all created issues",
+      "- Link phase issues with `Depends on: #N` to enforce ordering",
+      "",
+      "## When to Shorten the Pipeline",
+      "",
+      "- **Short meetings** (<30 min, <2000 words): combine extract + notes into one session",
+      "- **No requirements or decisions**: Phase 1 skips creating the `meeting:draft` issue",
+      "- **Only action items**: extract + notes + link (3 phase issues)"
+    ].join("\n")
+  };
+}
 var processMeetingSkill = {
   name: "process-meeting",
   description: "Process a meeting transcript through the 4-phase meeting analysis pipeline",
@@ -11053,64 +11058,67 @@ var processMeetingSkill = {
     "  to pick up (notes, draft, link)"
   ].join("\n")
 };
-var meetingAnalysisBundle = {
-  name: "meeting-analysis",
-  description: "Meeting transcript processing workflow with 4-phase pipeline (extract, notes, draft, link)",
-  appliesWhen: () => true,
-  rules: [
-    {
-      name: "meeting-processing-workflow",
-      description: "Describes the 4-phase meeting processing pipeline, extraction taxonomy, and labeling conventions",
-      scope: AGENT_RULE_SCOPE.ALWAYS,
-      content: [
-        "# Meeting Processing Workflow",
-        "",
-        "Use `/process-meeting <path>` to process a meeting transcript 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 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` /",
-        "`standup` / `external` / `other` \u2014 that drives type-specific",
-        "extraction rules in phases 1\u20132. The `areas` list scopes phase-4",
-        "direct edits to the doc-root sub-folders declared in the project's",
-        "**Area \u2192 doc-root mapping** table. When both fields are absent",
-        "the pipeline falls back to the default workflow (kind `other`,",
-        "no area gating)."
-      ].join("\n"),
-      platforms: {
-        cursor: { exclude: true }
+function buildMeetingAnalysisBundle(tier = AGENT_MODEL.BALANCED) {
+  return {
+    name: "meeting-analysis",
+    description: "Meeting transcript processing workflow with 4-phase pipeline (extract, notes, draft, link)",
+    appliesWhen: () => true,
+    rules: [
+      {
+        name: "meeting-processing-workflow",
+        description: "Describes the 4-phase meeting processing pipeline, extraction taxonomy, and labeling conventions",
+        scope: AGENT_RULE_SCOPE.ALWAYS,
+        content: [
+          "# Meeting Processing Workflow",
+          "",
+          "Use `/process-meeting <path>` to process a meeting transcript 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 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` /",
+          "`standup` / `external` / `other` \u2014 that drives type-specific",
+          "extraction rules in phases 1\u20132. The `areas` list scopes phase-4",
+          "direct edits to the doc-root sub-folders declared in the project's",
+          "**Area \u2192 doc-root mapping** table. When both fields are absent",
+          "the pipeline falls back to the default workflow (kind `other`,",
+          "no area gating)."
+        ].join("\n"),
+        platforms: {
+          cursor: { exclude: true }
+        },
+        tags: ["workflow"]
+      }
+    ],
+    skills: [processMeetingSkill],
+    subAgents: [buildMeetingAnalystSubAgent(tier)],
+    labels: [
+      {
+        name: "meeting:extract",
+        color: "C5DEF5",
+        description: "Phase 1: raw extraction from a meeting transcript"
       },
-      tags: ["workflow"]
-    }
-  ],
-  skills: [processMeetingSkill],
-  subAgents: [meetingAnalystSubAgent],
-  labels: [
-    {
-      name: "meeting:extract",
-      color: "C5DEF5",
-      description: "Phase 1: raw extraction from a meeting transcript"
-    },
-    {
-      name: "meeting:notes",
-      color: "BFDADC",
-      description: "Phase 2: curated notes derived from an extraction"
-    },
-    {
-      name: "meeting:draft",
-      color: "D4C5F9",
-      description: "Phase 3: draft follow-up issues proposed from notes"
-    },
-    {
-      name: "meeting:link",
-      color: "FEF2C0",
-      description: "Phase 4: linking/reconciling drafted issues with existing work"
-    }
-  ]
-};
+      {
+        name: "meeting:notes",
+        color: "BFDADC",
+        description: "Phase 2: curated notes derived from an extraction"
+      },
+      {
+        name: "meeting:draft",
+        color: "D4C5F9",
+        description: "Phase 3: draft follow-up issues proposed from notes"
+      },
+      {
+        name: "meeting:link",
+        color: "FEF2C0",
+        description: "Phase 4: linking/reconciling drafted issues with existing work"
+      }
+    ]
+  };
+}
+var meetingAnalysisBundle = buildMeetingAnalysisBundle();
 
 // src/agent/bundles/run-ratio.ts
 var DEFAULT_DISPATCH_TO_HOUSEKEEPING_RATIO = 4;
@@ -14523,6 +14531,69 @@ function resolveOrchestratorAssets(tierConfig, scopeGateConfig, runRatioConfig,
     )
   };
 }
+var orchestrateCommand = {
+  name: "orchestrate",
+  description: "Run one full orchestrator cycle: triage, queue scan, delegate to issue-worker.",
+  content: [
+    "# Orchestrate",
+    "",
+    "Invoke the `orchestrator` sub-agent and run **one full end-to-end",
+    "cycle**: triage / unblock \u2192 maintenance \u2192 queue scan \u2192 delegate the",
+    "picked issue to the `issue-worker` sub-agent \u2192 cleanup.",
+    "",
+    "Follow the contract in `.claude/agents/orchestrator.md`. Do **not**",
+    "implement code, create branches, push commits, or merge PRs \u2014 those",
+    "are the worker's and `pr-reviewer`'s jobs respectively.",
+    "",
+    "Run as a depth-0 (top-level) session so the orchestrator can spawn",
+    "the `issue-worker` sub-agent at depth-1 \u2014 Claude Code forbids nested",
+    "sub-agent dispatch.",
+    ""
+  ].join("\n")
+};
+var checkBlockedCommand = {
+  name: "check-blocked",
+  description: "Run .claude/procedures/check-blocked.sh and summarise the unblock candidates.",
+  content: [
+    "# Check Blocked",
+    "",
+    "Run the bundled triage helper and report what it found:",
+    "",
+    "```bash",
+    'bash .claude/procedures/check-blocked.sh "$@"',
+    "```",
+    "",
+    "Pass any extra arguments through verbatim. The script walks every",
+    "`status:blocked` issue, re-checks each `Depends on:` reference, and",
+    "prints `UNBLOCKED` / `STILL_BLOCKED` lines for issues that should",
+    "transition to `status:ready`.",
+    "",
+    "Summarise the output (counts, the first few candidates) \u2014 do **not**",
+    "transition labels yourself; that is the orchestrator's responsibility.",
+    ""
+  ].join("\n")
+};
+var scanCommand = {
+  name: "scan",
+  description: "Run the orchestrator queue scan only and report the next ready issue without dispatching.",
+  content: [
+    "# Scan",
+    "",
+    "Run the orchestrator's **queue scan only** (Phase E of the contract",
+    "in `.claude/agents/orchestrator.md`) and print the next ready issue,",
+    "the funnel-tier sort that put it on top, and the scope-gate result.",
+    "",
+    "Do **not** claim the issue, create a branch, or delegate to",
+    "`issue-worker`. This command exists for proactive review of what",
+    "the next `/orchestrate` invocation would pick up.",
+    "",
+    "Walk each `priority:*` bucket in turn (capped at 50 per bucket),",
+    "filter `Depends on:` references, and short-circuit on the first",
+    "bucket whose survivors clear the filter. Report the top candidate",
+    "and the number of survivors per bucket.",
+    ""
+  ].join("\n")
+};
 var orchestratorBundle = {
   name: "orchestrator",
   description: "Pipeline orchestrator agent for issue triage, PR review, and queue management",
@@ -14549,6 +14620,7 @@ var orchestratorBundle = {
   ],
   subAgents: [orchestratorSubAgent, issueWorkerSubAgent],
   procedures: [checkBlockedProcedure, unblockDependentsProcedure],
+  commands: [orchestrateCommand, checkBlockedCommand, scanCommand],
   claudePermissions: {
     allow: [
       // Allow executing the check-blocked.sh procedure
@@ -14558,11 +14630,11 @@ var orchestratorBundle = {
 };
 
 // src/agent/bundles/people-profile.ts
-function buildPeopleProfileAnalystSubAgent(paths, issueDefaults) {
+function buildPeopleProfileAnalystSubAgent(paths, issueDefaults, tier) {
   return {
     name: "people-profile-analyst",
     description: "Researches an individual person (colleague, customer contact, vendor contact, partner contact, industry expert, or connector) from public sources and produces a structured markdown profile cross-linked to companies, software, and meeting notes, then enqueues downstream `company:research` and `software:research` issues for unprofiled companies and software products surfaced during profiling. Also handles maintenance refreshes on a configurable staleness cadence (`people:refresh`). One person per session, tracked by people:* GitHub issue labels.",
-    model: AGENT_MODEL.POWERFUL,
+    model: tier,
     maxTurns: 80,
     platforms: { cursor: { exclude: true } },
     prompt: [
@@ -15392,7 +15464,7 @@ function buildRefreshPersonSkill(paths, issueDefaults) {
     ].join("\n")
   };
 }
-function buildPeopleProfileBundle(paths = DEFAULT_AGENT_PATHS, issueDefaults = DEFAULT_RESOLVED_ISSUE_DEFAULTS) {
+function buildPeopleProfileBundle(paths = DEFAULT_AGENT_PATHS, issueDefaults = DEFAULT_RESOLVED_ISSUE_DEFAULTS, tier = AGENT_MODEL.BALANCED) {
   return {
     name: "people-profile",
     description: "People research and profiling pipeline: research, draft profile, followup, refresh. Enabled by default; domain-neutral; filesystem-durable between phases. Cross-references existing companies, software, and meeting notes, and Phase 3 (Followup) hands unprofiled, genuinely-relevant companies and software products off to the `company-profile` and `software-profile` bundles via `company:research` and `software:research` issues. Phase 4 (Refresh) re-verifies profiles on a configurable staleness cadence.",
@@ -15440,7 +15512,7 @@ function buildPeopleProfileBundle(paths = DEFAULT_AGENT_PATHS, issueDefaults = D
       buildProfilePersonSkill(paths, issueDefaults),
       buildRefreshPersonSkill(paths, issueDefaults)
     ],
-    subAgents: [buildPeopleProfileAnalystSubAgent(paths, issueDefaults)],
+    subAgents: [buildPeopleProfileAnalystSubAgent(paths, issueDefaults, tier)],
     labels: [
       {
         name: "type:people-profile",
@@ -17015,7 +17087,19 @@ var prReviewBundle = {
         "to a PR's branch \u2014 it only reviews, decides, and orchestrates merge",
         "or comment. In loop mode, a failed review for one PR never stops",
         "the loop; the reviewer comments and moves on. See the `pr-reviewer`",
-        "agent definition for the full phase-by-phase contract.",
+        "agent definition for the full phase-by-phase contract."
+      ].join("\n"),
+      platforms: {
+        cursor: { exclude: true }
+      },
+      tags: ["workflow"]
+    },
+    {
+      name: "pr-review-feedback-protocol",
+      description: "Documents the human-in-the-loop feedback loop on PR review: reaction state machine, pushback resolution, fix-list comment format, sticky reviewer-notes comment, label glossary, and human-author opt-in flag.",
+      scope: AGENT_RULE_SCOPE.ALWAYS,
+      content: [
+        "# PR Review Feedback Protocol",
         "",
         "## Human-in-the-Loop Feedback Protocol",
         "",
@@ -23799,11 +23883,11 @@ var slackBundle = {
 };
 
 // src/agent/bundles/software-profile.ts
-function buildSoftwareProfileAnalystSubAgent(paths, issueDefaults) {
+function buildSoftwareProfileAnalystSubAgent(paths, issueDefaults, tier) {
   return {
     name: "software-profile-analyst",
     description: "Researches a software product (competitor, adjacent, incumbent, enabler, infrastructure, or ecosystem-tool) from public sources, produces a structured markdown profile, contributes rows to a shared feature matrix ranked against configurable segment-importance weights, maps features back to the BCM capability model and flags unmapped features, then enqueues downstream `bcm:outline`, `company:research`, and `people:research` issues for new sub-capabilities, the vendor company, and primary-attribution founders/leaders surfaced during profiling. One product per session, tracked by software:* GitHub issue labels.",
-    model: AGENT_MODEL.POWERFUL,
+    model: tier,
     maxTurns: 80,
     platforms: { cursor: { exclude: true } },
     prompt: [
@@ -24738,7 +24822,7 @@ function buildMapSoftwareSkill(paths, issueDefaults) {
     ].join("\n")
   };
 }
-function buildSoftwareProfileBundle(paths = DEFAULT_AGENT_PATHS, issueDefaults = DEFAULT_RESOLVED_ISSUE_DEFAULTS) {
+function buildSoftwareProfileBundle(paths = DEFAULT_AGENT_PATHS, issueDefaults = DEFAULT_RESOLVED_ISSUE_DEFAULTS, tier = AGENT_MODEL.BALANCED) {
   return {
     name: "software-profile",
     description: "Software research, profiling, feature-matrix, and capability-mapping pipeline: research, profile, matrix, map, followup. Enabled by default; domain-neutral; filesystem-durable between phases; ranks features against configurable segment-importance weights and maps features back to the BCM capability model. Phase 4 (Map) hands unmapped features off to the `bcm-writer` bundle via `bcm:outline` issues. Phase 5 (Followup) hands the vendor company and primary-attribution founders/leaders off to the `company-profile` and `people-profile` bundles via `company:research` and `people:research` issues.",
@@ -24795,7 +24879,9 @@ function buildSoftwareProfileBundle(paths = DEFAULT_AGENT_PATHS, issueDefaults =
       buildProfileSoftwareSkill(paths, issueDefaults),
       buildMapSoftwareSkill(paths, issueDefaults)
     ],
-    subAgents: [buildSoftwareProfileAnalystSubAgent(paths, issueDefaults)],
+    subAgents: [
+      buildSoftwareProfileAnalystSubAgent(paths, issueDefaults, tier)
+    ],
     labels: [
       {
         name: "type:software-profile",
@@ -27029,6 +27115,211 @@ var vitestBundle = {
   }
 };
 
+// src/agent/bundles/agent-registry.ts
+var AGENT_REGISTRY_ENTRIES = [
+  {
+    bundle: "agenda",
+    skill: "/draft-agenda",
+    agent: "agenda-analyst",
+    resolveOutputPath: (p) => `${p.meetingsRoot}/`,
+    purpose: "Pre-meeting agenda authoring (2-phase: draft, finalize). Reuses the project's meeting-type taxonomy.",
+    workflowRuleName: "meeting-agenda-workflow"
+  },
+  {
+    bundle: "bcm-writer",
+    skill: "/write-bcm",
+    agent: "bcm-writer",
+    resolveOutputPath: (p) => `${p.bcmRoot}/`,
+    purpose: "BCM capability-model documents (4-phase: outline, scaffold, context, connect). BIZBOK-aligned.",
+    workflowRuleName: "bcm-writer-workflow"
+  },
+  {
+    bundle: "business-models",
+    skill: "/scan-business-models",
+    agent: "business-models-analyst",
+    resolveOutputPath: (p) => `${p.docsRoot}/industry-research/`,
+    purpose: "Osterwalder business-model canvases per industry segment (3-phase: scan, canvas, complete).",
+    workflowRuleName: "business-models-workflow"
+  },
+  {
+    bundle: "company-profile",
+    skill: "/profile-company",
+    agent: "company-profile-analyst",
+    resolveOutputPath: (p) => `${p.companiesRoot}/`,
+    purpose: "Company profiles, notes, and segment competitive analyses (up to 6 phases incl. refresh).",
+    workflowRuleName: "company-profile-workflow"
+  },
+  {
+    bundle: "customer-profile",
+    skill: "/discover-customers",
+    agent: "customer-profile-analyst",
+    resolveOutputPath: (p) => `${p.profilesRoot}/customers/`,
+    purpose: "Customer-archetype discovery, profiles, and competitor feature-mapping (3-phase).",
+    workflowRuleName: "customer-profile-workflow"
+  },
+  {
+    bundle: "docs-sync",
+    skill: "/docs-sync-pr",
+    agent: "docs-sync",
+    resolveOutputPath: (p) => `${p.docsRoot}/`,
+    purpose: "Pre-PR drift detection and mechanical doc fixes (2-phase: scan, fix). Skeleton release.",
+    workflowRuleName: "docs-sync-workflow"
+  },
+  {
+    bundle: "industry-discovery",
+    skill: "/discover-industries",
+    agent: "industry-discovery-analyst",
+    resolveOutputPath: (p) => `${p.industriesRoot}/`,
+    purpose: "Industry-vertical discovery, fit-evaluation, and research planning (3-phase).",
+    workflowRuleName: "industry-discovery-workflow"
+  },
+  {
+    bundle: "maintenance-audit",
+    skill: "/audit-docs",
+    agent: "maintenance-audit",
+    resolveOutputPath: (p) => `${p.docsRoot}/`,
+    purpose: "Doc-registry audits with idempotent fixes (3-phase: scan, fix, verify). No new content.",
+    workflowRuleName: "maintenance-audit-workflow"
+  },
+  {
+    bundle: "meeting-analysis",
+    skill: "/process-meeting",
+    agent: "meeting-analyst",
+    resolveOutputPath: (p) => `${p.meetingsRoot}/`,
+    purpose: "Post-meeting transcript processing (4-phase: extract, notes, draft, link).",
+    workflowRuleName: "meeting-processing-workflow"
+  },
+  {
+    bundle: "people-profile",
+    skill: "/profile-person",
+    agent: "people-profile-analyst",
+    resolveOutputPath: (p) => `${p.peopleRoot}/`,
+    purpose: "Person profiles only (up to 4 phases incl. refresh). Hands off to company/software bundles.",
+    workflowRuleName: "people-profile-workflow"
+  },
+  {
+    bundle: "pr-review",
+    skill: "/review-pr",
+    agent: "pr-reviewer",
+    resolveOutputPath: () => "",
+    purpose: "PR review, auto-merge gating, and human-in-the-loop feedback orchestration.",
+    workflowRuleName: "pr-review-workflow"
+  },
+  {
+    bundle: "regulatory-research",
+    skill: "/scan-regulatory-landscape",
+    agent: "regulatory-research-analyst",
+    resolveOutputPath: (p) => `${p.docsRoot}/regulations/`,
+    purpose: "Regulation research, version pages, and impact analysis (3-phase). Documents, never interprets.",
+    workflowRuleName: "regulatory-research-workflow"
+  },
+  {
+    bundle: "requirements-analyst",
+    skill: "/scan-requirements",
+    agent: "requirements-analyst",
+    resolveOutputPath: (p) => `${p.researchRequirementsRoot}/`,
+    purpose: "Requirements gap discovery + draft proposals (2-phase: scan, draft-trace). Hands off to writer.",
+    workflowRuleName: "requirements-analyst-workflow"
+  },
+  {
+    bundle: "requirements-reviewer",
+    skill: "/review-requirements",
+    agent: "requirements-reviewer",
+    resolveOutputPath: (p) => `${p.requirementsRoot}/`,
+    purpose: "Requirements audit (12 checks) and narrow-edit deprecation. Never authors new requirement docs.",
+    workflowRuleName: "requirements-reviewer-workflow"
+  },
+  {
+    bundle: "requirements-writer",
+    skill: "/write-requirement",
+    agent: "requirements-writer",
+    resolveOutputPath: (p) => `${p.requirementsRoot}/`,
+    purpose: "Formal requirement document authoring across the 11-category taxonomy + four-tier classification.",
+    workflowRuleName: "requirements-writer-workflow"
+  },
+  {
+    bundle: "research-pipeline",
+    skill: "/research",
+    agent: "research-analyst",
+    resolveOutputPath: (p) => `${p.researchRoot}/`,
+    purpose: "Generic research micro-tasks (3-phase: scope, slice, verify). Notes-only output.",
+    workflowRuleName: "research-pipeline-workflow"
+  },
+  {
+    bundle: "software-profile",
+    skill: "/profile-software",
+    agent: "software-profile-analyst",
+    resolveOutputPath: (p) => `${p.softwareRoot}/`,
+    purpose: "Software profiles, shared feature matrix, and BCM-tree capability mapping (up to 5 phases).",
+    workflowRuleName: "software-profile-workflow"
+  },
+  {
+    bundle: "standards-research",
+    skill: "/scope-standards-research",
+    agent: "standards-research-analyst",
+    resolveOutputPath: (p) => `${p.docsRoot}/standards/`,
+    purpose: "Interoperability standards research (5-phase: scope, research, compare, extension, organizations).",
+    workflowRuleName: "standards-research-workflow"
+  }
+];
+var SUPPRESSED_WORKFLOW_RULE_NAMES = AGENT_REGISTRY_ENTRIES.map((e) => e.workflowRuleName);
+function isSuppressedWorkflowRule(name) {
+  return SUPPRESSED_WORKFLOW_RULE_NAMES.includes(name);
+}
+function bundleNameForWorkflowRule(ruleName) {
+  const entry = AGENT_REGISTRY_ENTRIES.find(
+    (e) => e.workflowRuleName === ruleName
+  );
+  return entry?.bundle;
+}
+function buildAgentRegistryRule(bundles, paths) {
+  const activeNames = new Set(bundles.map((b) => b.name));
+  const rows = AGENT_REGISTRY_ENTRIES.filter(
+    (e) => activeNames.has(e.bundle)
+  ).slice();
+  if (rows.length === 0) {
+    return void 0;
+  }
+  rows.sort((a, b) => a.bundle.localeCompare(b.bundle));
+  const lines = [
+    "# Agent Registry",
+    "",
+    "Each row below is the routing summary for one phased-agent",
+    "bundle: the user-invocable skill, the sub-agent that handles",
+    "the work, the output path the agent writes to, and a one-line",
+    "purpose. Use the table to answer *which agent handles X* \u2014",
+    "full agent prompts live in `.claude/agents/<name>.md` and only",
+    "load on delegation, so the table is the always-on routing",
+    "signal.",
+    "",
+    "Cross-cutting policies that apply to every agent below \u2014",
+    "Progress File Convention, Shared-Editing Safety, Issue",
+    "Templates, Skill Evals \u2014 are documented as their own top-level",
+    "sections elsewhere in this file. The registry only captures",
+    "routing; it does not duplicate convention prose.",
+    "",
+    "| Skill | Agent | Bundle | Output path | Purpose |",
+    "| --- | --- | --- | --- | --- |"
+  ];
+  for (const row of rows) {
+    const outputPath = row.resolveOutputPath(paths);
+    const pathCell = outputPath.length > 0 ? `\`${outputPath}\`` : "\u2014";
+    lines.push(
+      `| \`${row.skill}\` | \`${row.agent}\` | \`${row.bundle}\` | ${pathCell} | ${row.purpose} |`
+    );
+  }
+  return {
+    name: "agent-registry",
+    description: "Routing table mapping each phased-agent bundle to its primary skill, sub-agent, output path, and one-line purpose. Replaces the per-bundle workflow rules whose prose summaries duplicated the routing signal.",
+    scope: AGENT_RULE_SCOPE.ALWAYS,
+    content: lines.join("\n"),
+    platforms: {
+      cursor: { exclude: true }
+    },
+    tags: ["workflow"]
+  };
+}
+
 // src/agent/bundles/features.ts
 var SOURCE_TIER_HEADINGS = [
   { key: "t1", heading: "### T1 \u2014 Primary Living" },
@@ -27396,7 +27687,7 @@ function renderPriorityRulesSection(rules) {
 }
 
 // src/agent/bundles/index.ts
-function buildBuiltInBundles(paths = DEFAULT_AGENT_PATHS, issueDefaults = DEFAULT_RESOLVED_ISSUE_DEFAULTS) {
+function buildBuiltInBundles(paths = DEFAULT_AGENT_PATHS, issueDefaults = DEFAULT_RESOLVED_ISSUE_DEFAULTS, defaultAgentTier = AGENT_MODEL.BALANCED) {
   return [
     buildBaseBundle(paths),
     upstreamConfigulatorDocsBundle,
@@ -27409,7 +27700,7 @@ function buildBuiltInBundles(paths = DEFAULT_AGENT_PATHS, issueDefaults = DEFAUL
     projenBundle,
     githubWorkflowBundle,
     slackBundle,
-    meetingAnalysisBundle,
+    buildMeetingAnalysisBundle(defaultAgentTier),
     agendaBundle,
     orchestratorBundle,
     prReviewBundle,
@@ -27417,16 +27708,16 @@ function buildBuiltInBundles(paths = DEFAULT_AGENT_PATHS, issueDefaults = DEFAUL
     buildRequirementsWriterBundle(paths, issueDefaults),
     buildRequirementsReviewerBundle(paths, issueDefaults),
     buildResearchPipelineBundle(paths, issueDefaults),
-    buildCompanyProfileBundle(paths, issueDefaults),
-    buildCustomerProfileBundle(paths, issueDefaults),
-    buildPeopleProfileBundle(paths, issueDefaults),
-    buildSoftwareProfileBundle(paths, issueDefaults),
+    buildCompanyProfileBundle(paths, issueDefaults, defaultAgentTier),
+    buildCustomerProfileBundle(paths, issueDefaults, defaultAgentTier),
+    buildPeopleProfileBundle(paths, issueDefaults, defaultAgentTier),
+    buildSoftwareProfileBundle(paths, issueDefaults, defaultAgentTier),
     buildIndustryDiscoveryBundle(paths, issueDefaults),
     buildBusinessModelsBundle(paths, issueDefaults),
     buildBcmWriterBundle(paths, issueDefaults),
     buildStandardsResearchBundle(paths, issueDefaults),
     buildRegulatoryResearchBundle(paths, issueDefaults),
-    buildMaintenanceAuditBundle(paths, issueDefaults),
+    buildMaintenanceAuditBundle(paths, issueDefaults, defaultAgentTier),
     buildDocsSyncBundle(paths)
   ];
 }
@@ -27672,7 +27963,7 @@ var ClaudeRenderer = class _ClaudeRenderer {
   /**
    * Render all Claude Code configuration files.
    */
-  static render(component, rules, skills, subAgents, mcpServers, settings, procedures) {
+  static render(component, rules, skills, subAgents, mcpServers, settings, procedures, commands) {
     _ClaudeRenderer.renderClaudeMd(component, rules);
     _ClaudeRenderer.renderScopedRules(component, rules);
     _ClaudeRenderer.renderSettings(component, mcpServers, settings);
@@ -27681,6 +27972,9 @@ var ClaudeRenderer = class _ClaudeRenderer {
     if (procedures && procedures.length > 0) {
       _ClaudeRenderer.renderProcedures(component, procedures);
     }
+    if (commands && commands.length > 0) {
+      _ClaudeRenderer.renderCommands(component, commands);
+    }
   }
   static renderClaudeMd(component, rules) {
     const claudeMdRules = rules.filter((r) => {
@@ -28012,6 +28306,30 @@ var ClaudeRenderer = class _ClaudeRenderer {
       });
     }
   }
+  /**
+   * Renders user-invokable slash commands to `.claude/commands/<name>.md`.
+   *
+   * Each command file carries a YAML frontmatter block with the
+   * `description` (always present) and an optional `model` alias. The
+   * body is the {@link AgentCommand.content} written verbatim.
+   *
+   * @see https://docs.claude.com/en/docs/claude-code/slash-commands
+   */
+  static renderCommands(component, commands) {
+    for (const command of commands) {
+      const lines = [];
+      lines.push("---");
+      lines.push(`description: ${command.description}`);
+      const resolvedModel = resolveModelAlias(command.model);
+      if (resolvedModel) {
+        lines.push(`model: ${resolvedModel}`);
+      }
+      lines.push("---");
+      lines.push("");
+      lines.push(...command.content.split("\n"));
+      new TextFile3(component, `.claude/commands/${command.name}.md`, { lines });
+    }
+  }
   /**
    * Determine the default Claude rule target based on rule scope.
    * ALWAYS-scoped rules default to CLAUDE_MD; FILE_PATTERN rules default to SCOPED_FILE.
@@ -28034,6 +28352,17 @@ var CopilotRenderer = class {
 };
 
 // src/agent/agent-config.ts
+function resolveDefaultAgentTier(options) {
+  switch (options?.defaultAgentTier) {
+    case "powerful":
+      return AGENT_MODEL.POWERFUL;
+    case "fast":
+      return AGENT_MODEL.FAST;
+    case "balanced":
+    default:
+      return AGENT_MODEL.BALANCED;
+  }
+}
 var DEFAULT_CLAUDE_ALLOW = [
   // ── Git ──────────────────────────────────────────────────────────────
   "Bash(git add *)",
@@ -28138,6 +28467,45 @@ var DEFAULT_CLAUDE_DENY = [
   "Bash(export *)",
   "Bash(env *)"
 ];
+var DEFAULT_CLAUDE_PATH_DENY = [
+  "Read(./node_modules/**)",
+  "Read(./dist/**)",
+  "Read(./lib/**)",
+  "Read(./.astro/**)",
+  "Read(./.env)",
+  "Read(./.env.*)",
+  "Read(./*.lock)",
+  "Read(./pnpm-lock.yaml)",
+  "Read(./package-lock.json)"
+];
+var DEFAULT_USAGE_LOG_PATH = ".claude/usage.log";
+var DEFAULT_CLAUDE_ENV = {
+  ENABLE_TOOL_SEARCH: "1"
+};
+var DEFAULT_CLAUDE_HOOKS = {
+  Stop: [
+    {
+      matcher: "*",
+      hooks: [
+        {
+          type: "command",
+          command: `echo "$(date -u +%FT%TZ),\${CLAUDE_SESSION_ID:-unknown},\${CLAUDE_INPUT_TOKENS:-0},\${CLAUDE_OUTPUT_TOKENS:-0}" >> ${DEFAULT_USAGE_LOG_PATH}`
+        }
+      ]
+    }
+  ],
+  PostToolUse: [
+    {
+      matcher: "Edit|Write",
+      hooks: [
+        {
+          type: "command",
+          command: 'case "${CLAUDE_TOOL_INPUT_path:-}" in *docs/src/content/docs/*) if [ -x .claude/procedures/check-links.sh ]; then bash .claude/procedures/check-links.sh "$CLAUDE_TOOL_INPUT_path" 2>&1 | head -20; fi ;; esac'
+        }
+      ]
+    }
+  ]
+};
 var PROGRESS_FILE_BUNDLE_HOOKS = [
   ["bcm-writer-workflow", "bcm-writer"],
   ["business-models-workflow", "business-models"],
@@ -28212,10 +28580,30 @@ var AgentConfig = class _AgentConfig extends Component8 {
     return (examples.t1?.length ?? 0) > 0 || (examples.t2?.length ?? 0) > 0 || (examples.t3?.length ?? 0) > 0 || (examples.t4?.length ?? 0) > 0;
   }
   /**
-   * Merges default Claude permissions with bundle and user-supplied settings.
+   * Merges default Claude permissions and hooks with bundle and
+   * user-supplied settings.
+   *
+   * Permission merge order: defaults → bundle permissions → user-supplied
+   * entries. Both `allow` and `deny` are deduped via
+   * `Array.from(new Set(...))`; V8 `Set` iteration preserves insertion
+   * order, so the final ordering is defaults first, then bundle, then
+   * user, with duplicates removed (first-occurrence wins). `defaultMode`
+   * defaults to `"dontAsk"` unless overridden — see the inline comment
+   * on the literal below for the autonomous-worker rationale.
    *
-   * Merge order: defaults → bundle permissions → user-supplied entries.
-   * `defaultMode` defaults to `"dontAsk"` unless overridden.
+   * Hooks merge: consumer-supplied entries first, then default entries
+   * (Stop, PostToolUse), deduped by `(matcher, JSON-serialized hooks)`.
+   * Defaults are skipped entirely when `disableAllHooks: true` is set —
+   * the `disableAllHooks` flag passes through to the rendered file so
+   * Claude Code suppresses every project-level hook at runtime, and the
+   * defaults are dropped at synth time so the rendered file does not
+   * carry orphan entries that would re-fire if the operator later flipped
+   * the flag back off.
+   *
+   * Env merge: defaults from `DEFAULT_CLAUDE_ENV` (e.g.
+   * `ENABLE_TOOL_SEARCH=1`) layer first, then consumer-supplied
+   * `claudeSettings.env` entries override on key collision. Sibling keys
+   * from both sources land in the rendered file.
    */
   static mergeClaudeDefaults(userSettings, bundlePermissions) {
     const bundleAllow = bundlePermissions?.allow ?? [];
@@ -28224,14 +28612,80 @@ var AgentConfig = class _AgentConfig extends Component8 {
     const userDeny = userSettings?.permissions?.deny ?? [];
     return {
       ...userSettings,
+      // `defaultMode: "dontAsk"` is configulator's hardcoded default
+      // because scheduled-task workers (issue-worker, orchestrator,
+      // pr-reviewer, and the analyst/writer family) run autonomously
+      // and would deadlock on confirmation prompts. Any other value
+      // breaks the autonomous-worker contract — override only after
+      // revisiting that contract end-to-end. The override path for
+      // consumers is `claudeSettings.defaultMode` on
+      // `AgentConfigOptions`.
       defaultMode: userSettings?.defaultMode ?? "dontAsk",
       permissions: {
         ...userSettings?.permissions,
-        allow: [...DEFAULT_CLAUDE_ALLOW, ...bundleAllow, ...userAllow],
-        deny: [...DEFAULT_CLAUDE_DENY, ...bundleDeny, ...userDeny]
-      }
+        allow: Array.from(
+          /* @__PURE__ */ new Set([...DEFAULT_CLAUDE_ALLOW, ...bundleAllow, ...userAllow])
+        ),
+        deny: Array.from(
+          /* @__PURE__ */ new Set([
+            ...DEFAULT_CLAUDE_DENY,
+            ...DEFAULT_CLAUDE_PATH_DENY,
+            ...bundleDeny,
+            ...userDeny
+          ])
+        )
+      },
+      hooks: _AgentConfig.mergeClaudeHooks(userSettings),
+      env: { ...DEFAULT_CLAUDE_ENV, ...userSettings?.env ?? {} }
     };
   }
+  /**
+   * Merge default lifecycle hooks (Stop, PostToolUse) with consumer-
+   * supplied entries on `claudeSettings.hooks`. Consumer entries appear
+   * first so a downstream override that wires a faster lint/format hook
+   * runs ahead of the defaults; defaults are appended after.
+   *
+   * Returns `undefined` when neither defaults nor consumer entries
+   * remain — the renderer skips the `hooks` key entirely in that case
+   * so opt-out repos do not ship an empty `"hooks": {}` object.
+   *
+   * Defaults are gated on `disableAllHooks !== true`. When the flag is
+   * set we still pass through any consumer-supplied entries (the
+   * runtime-level `disableAllHooks: true` is what suppresses execution),
+   * but we never inject the bundle defaults. That keeps the disable-all
+   * escape hatch idempotent: flipping the flag drops the bundle's
+   * default surface area instead of leaving the entries on disk for a
+   * future re-enable.
+   */
+  static mergeClaudeHooks(userSettings) {
+    const userHooks = userSettings?.hooks;
+    const includeDefaults = userSettings?.disableAllHooks !== true;
+    const defaults = includeDefaults ? DEFAULT_CLAUDE_HOOKS : {};
+    const allEvents = /* @__PURE__ */ new Set([
+      ...Object.keys(userHooks ?? {}),
+      ...Object.keys(defaults)
+    ]);
+    const merged = {};
+    for (const event of allEvents) {
+      const userEntries = (userHooks ?? {})[event] ?? [];
+      const defaultEntries = defaults[event] ?? [];
+      const seen = /* @__PURE__ */ new Set();
+      const combined = [];
+      for (const entry of [...userEntries, ...defaultEntries]) {
+        const key = JSON.stringify({
+          matcher: entry.matcher,
+          hooks: entry.hooks
+        });
+        if (seen.has(key)) continue;
+        seen.add(key);
+        combined.push(entry);
+      }
+      if (combined.length > 0) {
+        merged[event] = combined;
+      }
+    }
+    return Object.keys(merged).length > 0 ? merged : void 0;
+  }
   constructor(project, options = {}) {
     super(project);
     this.options = options;
@@ -28260,7 +28714,8 @@ var AgentConfig = class _AgentConfig extends Component8 {
     if (!this.cachedBundles) {
       this.cachedBundles = buildBuiltInBundles(
         this.resolvedPaths,
-        resolveIssueDefaults(this.options.issueDefaults)
+        resolveIssueDefaults(this.options.issueDefaults),
+        resolveDefaultAgentTier(this.options)
       );
     }
     return this.cachedBundles;
@@ -28306,6 +28761,9 @@ var AgentConfig = class _AgentConfig extends Component8 {
     if (resolvedRunRatio.enabled) {
       this.project.gitignore.addPatterns(`/${resolvedRunRatio.stateFilePath}`);
     }
+    if (this.options.claudeSettings?.disableAllHooks !== true) {
+      this.project.gitignore.addPatterns(`/${DEFAULT_USAGE_LOG_PATH}`);
+    }
     validateUnblockDependentsConfig(this.options.unblockDependents);
     validateIssueDefaultsConfig(this.options.issueDefaults);
     const resolvedProgressFiles = validateProgressFilesConfig(
@@ -28370,6 +28828,7 @@ var AgentConfig = class _AgentConfig extends Component8 {
     const skills = this.resolveSkills();
     const subAgents = this.resolveSubAgents();
     const procedures = this.resolveProcedures();
+    const commands = this.resolveCommands();
     const mcpServers = this.options.mcpServers ?? {};
     const projectMetadata = ProjectMetadata.of(this.project);
     const metadata = projectMetadata?.metadata;
@@ -28405,7 +28864,8 @@ var AgentConfig = class _AgentConfig extends Component8 {
           this.options.claudeSettings,
           bundlePermissions
         ),
-        resolvedProcedures
+        resolvedProcedures,
+        commands
       );
     }
     if (platforms.includes(AGENT_PLATFORM.CODEX)) {
@@ -28544,6 +29004,7 @@ ${section}`
         }
       }
     }
+    const injectBundleHooks = this.options.claudeMd?.injectBundleHooks ?? true;
     const resolvedProgressFiles = resolveProgressFiles(
       this.options.progressFiles
     );
@@ -28561,7 +29022,7 @@ ${section}`
         }
       }
     }
-    if (resolvedProgressFiles.enabled) {
+    if (injectBundleHooks && resolvedProgressFiles.enabled) {
       for (const [ruleName, label] of PROGRESS_FILE_BUNDLE_HOOKS) {
         const existing = ruleMap.get(ruleName);
         if (!existing) {
@@ -28601,7 +29062,7 @@ ${hook}`
         }
       }
     }
-    if (resolvedSharedEditingForRules.enabled) {
+    if (injectBundleHooks && resolvedSharedEditingForRules.enabled) {
       for (const [ruleName, label] of SHARED_EDITING_BUNDLE_HOOKS) {
         const existing = ruleMap.get(ruleName);
         if (!existing) {
@@ -28641,7 +29102,7 @@ ${hook}`
         }
       }
     }
-    if (resolvedSkillEvalsForRules.enabled) {
+    if (injectBundleHooks && resolvedSkillEvalsForRules.enabled) {
       for (const [ruleName, label] of SKILL_EVALS_BUNDLE_HOOKS) {
         const existing = ruleMap.get(ruleName);
         if (!existing) {
@@ -28686,7 +29147,7 @@ ${hook}`
     if (!hasAnyDocsEmittingBundle(excludedBundleNames)) {
       ruleMap.delete("stub-index-convention");
     }
-    if (resolvedIssueTemplatesForRules.enabled && hasDownstreamBundles) {
+    if (injectBundleHooks && resolvedIssueTemplatesForRules.enabled && hasDownstreamBundles) {
       for (const [ruleName, label] of ISSUE_TEMPLATES_BUNDLE_HOOKS) {
         const existing = ruleMap.get(ruleName);
         if (!existing) {
@@ -28734,6 +29195,57 @@ ${hook}`
         }
       }
     }
+    const registryRule = buildAgentRegistryRule(
+      this.activeBundles,
+      this.resolvedPaths
+    );
+    if (registryRule) {
+      let registryContent = registryRule.content;
+      const meetingAnalysisActive = this.activeBundles.some(
+        (b) => b.name === "meeting-analysis"
+      );
+      if (this.options.meetings && meetingAnalysisActive) {
+        const meetingsSection = renderMeetingTypesSection(
+          this.options.meetings
+        );
+        if (meetingsSection.length > 0) {
+          registryContent = `${registryContent}
+
+---
+
+${meetingsSection}`;
+        }
+      }
+      ruleMap.set(registryRule.name, {
+        ...registryRule,
+        content: registryContent
+      });
+      const customSectionBundles = new Set(
+        (this.options.features?.customDocSections ?? []).map(
+          (s) => s.bundleName
+        )
+      );
+      for (const [ruleName, rule] of ruleMap) {
+        if (!isSuppressedWorkflowRule(ruleName)) {
+          continue;
+        }
+        const owningBundleName = bundleNameForWorkflowRule(ruleName);
+        if (owningBundleName !== void 0 && customSectionBundles.has(owningBundleName)) {
+          continue;
+        }
+        const existingClaude = rule.platforms?.claude ?? {};
+        if (existingClaude.exclude === true) {
+          continue;
+        }
+        ruleMap.set(ruleName, {
+          ...rule,
+          platforms: {
+            ...rule.platforms,
+            claude: { ...existingClaude, exclude: true }
+          }
+        });
+      }
+    }
     return [...ruleMap.values()].sort((a, b) => {
       if (a.name === "project-overview") return -1;
       if (b.name === "project-overview") return 1;
@@ -28882,6 +29394,49 @@ ${hook}`
     }
     return [...procMap.values()];
   }
+  /**
+   * Resolves the final list of slash commands by merging bundle-shipped
+   * defaults with consumer-supplied entries. Mirrors {@link resolveSkills}
+   * and {@link resolveSubAgents}: auto-detected bundles contribute first,
+   * force-included bundles overlay, and consumer commands override on
+   * name collision. Names listed in `excludeCommands` are dropped after
+   * the merge so consumers can opt out of a single default without
+   * disabling the whole bundle.
+   */
+  resolveCommands() {
+    const commandMap = /* @__PURE__ */ new Map();
+    if (this.options.autoDetectBundles !== false) {
+      for (const bundle of this.pathAwareBundles) {
+        if (this.options.excludeBundles?.includes(bundle.name)) continue;
+        if (bundle.appliesWhen(this.project) && bundle.commands) {
+          for (const command of bundle.commands) {
+            commandMap.set(command.name, command);
+          }
+        }
+      }
+    }
+    if (this.options.includeBundles) {
+      for (const bundleName of this.options.includeBundles) {
+        const bundle = this.pathAwareBundles.find((b) => b.name === bundleName);
+        if (bundle?.commands) {
+          for (const command of bundle.commands) {
+            commandMap.set(command.name, command);
+          }
+        }
+      }
+    }
+    if (this.options.commands) {
+      for (const command of this.options.commands) {
+        commandMap.set(command.name, command);
+      }
+    }
+    if (this.options.excludeCommands) {
+      for (const name of this.options.excludeCommands) {
+        commandMap.delete(name);
+      }
+    }
+    return [...commandMap.values()];
+  }
   /**
    * Resolves template variables in rule content using project metadata.
    * Emits synthesis warnings for rules with unresolved variables.
@@ -33326,6 +33881,7 @@ var TypeScriptConfig = class extends Component20 {
 export {
   AGENT_MODEL,
   AGENT_PLATFORM,
+  AGENT_REGISTRY_ENTRIES,
   AGENT_RULE_SCOPE,
   AGENT_TIER_ROLES,
   AGENT_TIER_VALUES,
@@ -33422,6 +33978,7 @@ export {
   SCOPE_CLASS_VALUES,
   SHARED_EDITING_CONFLICT_STRATEGY_VALUES,
   STARLIGHT_ROLE,
+  SUPPRESSED_WORKFLOW_RULE_NAMES,
   SampleLang,
   StarlightProject,
   TestRunner,
@@ -33447,6 +34004,7 @@ export {
   awsCdkBundle,
   baseBundle,
   bcmWriterBundle,
+  buildAgentRegistryRule,
   buildBaseBundle,
   buildBcmWriterBundle,
   buildBuiltInBundles,
@@ -33457,6 +34015,7 @@ export {
   buildDocsSyncBundle,
   buildIndustryDiscoveryBundle,
   buildMaintenanceAuditBundle,
+  buildMeetingAnalysisBundle,
   buildOrchestratorConventionsContent,
   buildPeopleProfileBundle,
   buildRegulatoryResearchBundle,
@@ -33468,6 +34027,7 @@ export {
   buildSoftwareProfileBundle,
   buildStandardsResearchBundle,
   buildUnblockDependentsProcedure,
+  bundleNameForWorkflowRule,
   businessModelsBundle,
   checkDocSamplesProcedure,
   checkLinksProcedure,
@@ -33494,6 +34054,7 @@ export {
   industryDiscoveryBundle,
   isPhaseLabelOwnedByExcluded,
   isScheduledTaskOwnedByExcluded,
+  isSuppressedWorkflowRule,
   isTypeLabelOwnedByExcluded,
   jestBundle,
   labelsForPhase,
@@ -33552,6 +34113,7 @@ export {
   resolveAgentTiers,
   resolveAstroProjectOutdir,
   resolveAwsCdkProjectOutdir,
+  resolveDefaultAgentTier,
   resolveIssueDefaults,
   resolveIssueTemplates,
   resolveModelAlias,