@codedrifters/configulator 0.0.262 → 0.0.263

package/lib/index.d.mts

@@ -1143,6 +1143,33 @@ interface FocusConfig {
  *   customer / prospect / partner buckets.
  */
 type MeetingScope = "internal-recurring" | "internal-oneoff" | "external-customer" | "external-prospect" | "external-partner" | "external-other";
+/**
+ * Generic meeting-kind taxonomy. Each recognized meeting type maps to
+ * one of these kinds, which the `meeting-analysis` bundle uses to
+ * apply type-specific extraction rules in phases 1–2.
+ *
+ * The kind captures the **family** of meeting (how it should be
+ * extracted), independent of the concrete project-specific `id`. For
+ * example a repo may declare `founders-weekly` and `sprint-planning`
+ * as two distinct `id`s that both map to `kind: 'planning'`.
+ *
+ * - `planning` — sprint or project planning. Focus on tasks, goals,
+ *   and assignments. Produces direct sprint-plan edits and task
+ *   issues.
+ * - `review` — sprint review, retrospective, or decision review.
+ *   Captures retro learnings, status updates, and follow-ups.
+ * - `brainstorm` — open-ended ideation. Lower bar for Open Questions
+ *   and Future Features; higher bar for requirement/ADR creation
+ *   (only Firm items).
+ * - `standup` — short status meeting. Action items, blockers, sprint
+ *   status. Phase 3 (Draft) is almost always skipped.
+ * - `external` — customer, prospect, partner, or conference debrief.
+ *   Emphasizes people/company profiles, customer pain points (as BR
+ *   candidates, not FR), and competitive intel.
+ * - `other` — general meeting with no type-specific handling; the
+ *   default workflow applies.
+ */
+type MeetingTypeKind = "planning" | "review" | "brainstorm" | "standup" | "external" | "other";
 /**
  * A single meeting-type taxonomy entry declared by the consuming repo.
  * Each entry names a kind of meeting the project recognizes
@@ -1174,6 +1201,18 @@ interface MeetingType {
      * or one-off) or external (customer / prospect / partner / other).
      */
     readonly scope: MeetingScope;
+    /**
+     * Generic meeting kind this type maps to. Drives which type-specific
+     * extraction rules (Meeting Type Handling table) the `meeting-analysis`
+     * bundle applies in phases 1–2. Optional — when omitted, the bundle
+     * falls back to `other` (no type-specific rules).
+     *
+     * Multiple concrete `id`s can share the same `kind` (e.g., both
+     * `founders-weekly` and `sprint-planning` may map to `planning`).
+     *
+     * @example 'planning', 'standup', 'external'
+     */
+    readonly kind?: MeetingTypeKind;
     /**
      * Default scheduled duration in minutes. Optional; agents may use
      * this when proposing calendar holds or when validating a
@@ -1197,14 +1236,17 @@ interface MeetingType {
 }
 /**
  * A single meeting-area entry. Meeting areas provide a coarse
- * routing map from an `area` frontmatter value on a meeting note to
- * the sub-tree of the docs root where phase-4 direct edits should
- * land.
+ * routing map from entries in an `areas:` frontmatter list on a
+ * meeting note to the sub-tree of the docs root where phase-4
+ * direct edits should land. A single meeting may declare multiple
+ * areas; every matching entry's `docRoot` is in-scope for direct
+ * edits on that meeting (see the `meeting-analyst` agent's
+ * **Areas filtering** section for the full gating contract).
  *
  * Example: declaring `{ id: 'product-engineering', label: 'Product &
  * Engineering', docRoot: 'product' }` tells the `meeting-analysis`
  * bundle that a meeting whose frontmatter carries
- * `area: product-engineering` should have its direct edits routed
+ * `areas: [product-engineering]` should have its direct edits routed
  * under `<docsRoot>/product/`.
  *
  * When `AgentConfigOptions.meetings.meetingAreas` is non-empty, the
@@ -1217,8 +1259,8 @@ interface MeetingType {
  */
 interface MeetingArea {
     /**
-     * Stable machine identifier for the area. Matches the `area`
-     * frontmatter value on meeting notes.
+     * Stable machine identifier for the area. Matches one of the
+     * entries in the `areas:` frontmatter list on meeting notes.
      * @example 'product-engineering', 'go-to-market', 'operations'
      */
     readonly id: string;
@@ -1239,7 +1281,8 @@ interface MeetingArea {
  * templating a meeting. Every field is optional.
  *
  * - `meetingTypes` — the set of meeting types the repo recognizes.
- * - `meetingAreas` — maps `area` frontmatter to doc-root sub-trees.
+ * - `meetingAreas` — maps entries in the `areas:` frontmatter list
+ *   to doc-root sub-trees.
  * - `agendaTemplateRoot` — where pre-meeting agenda skeletons live.
  *
  * When supplied, the `meeting-analysis` bundle conditionally renders
@@ -1947,9 +1990,9 @@ declare function renderFocusSection(focus: FocusConfig | undefined): string;
  * Two subsections are rendered, each gated on its own input array:
  *
  * 1. **Recognized meeting types** — rendered when `meetingTypes` is
- *    non-empty. Lists every declared type with its scope, optional
- *    cadence, default duration, and agenda template path. Also
- *    documents the resolved `agendaTemplateRoot`.
+ *    non-empty. Lists every declared type with its scope, kind,
+ *    optional cadence, default duration, and agenda template path.
+ *    Also documents the resolved `agendaTemplateRoot`.
  * 2. **Area → doc-root mapping** — rendered when `meetingAreas` is
  *    non-empty. Lists every declared area with its `id`, label, and
  *    docs-root-relative destination folder.
@@ -4695,4 +4738,4 @@ declare const COMPLETE_JOB_ID = "complete";
  */
 declare function addBuildCompleteJob(buildWorkflow: BuildWorkflow): void;
 
-export { AGENT_MODEL, AGENT_PLATFORM, AGENT_RULE_SCOPE, AgentConfig, type AgentConfigOptions, type AgentExpansionRules, type AgentFeaturesConfig, type AgentModel, type AgentPathsConfig, type AgentPlatform, type AgentPlatformOverrides, type AgentProcedure, type AgentRule, type AgentRuleBundle, type AgentRuleScope, type AgentSkill, type AgentSubAgent, type AgentSubAgentPlatformOverrides, type ApproveMergeUpgradeOptions, AstroConfig, type AstroConfigOptions, type AstroIntegrationSpec, AstroOutput, AstroProject, type AstroProjectOptions, type AwsAccount, AwsCdkProject, type AwsCdkProjectOptions, AwsDeployWorkflow, AwsDeploymentConfig, AwsDeploymentTarget, type AwsDeploymentTargetOptions, type AwsLocalDeploymentConfig, type AwsOrganization, type AwsRegion, AwsTeardownWorkflow, type AwsTeardownWorkflowOptions, BUILT_IN_BUNDLES, CLAUDE_RULE_TARGET, COMPLETE_JOB_ID, type CiDeploymentConfig, type ClassTypeOptions, type ClaudeAutoModeConfig, type ClaudeHookAction, type ClaudeHookEntry, type ClaudeHooksConfig, type ClaudePermissionsConfig, type ClaudeRuleTarget, type ClaudeSandboxConfig, type ClaudeSettingsConfig, type CopilotHandoff, type CursorHookAction, type CursorHooksConfig, type CursorSettingsConfig, type CustomDocSection, DEFAULT_AGENT_PATHS, DEFAULT_PRIORITY_LABELS, DEFAULT_STATUS_LABELS, DEFAULT_TEARDOWN_BRANCH_PATTERNS, DEFAULT_TYPE_LABELS, type DeployWorkflowOptions, type DeploymentMetadata, type FocusArea, type FocusAreaMatch, type FocusConfig, type GitBranch, type GitHubBoardMetadata, type GitHubProjectMetadata, type GitHubSprintMetadata, type IDependencyResolver, JsiiFaker, LAYOUT_ENFORCEMENT, LAYOUT_ROOT_BY_PROJECT_TYPE, type LabelDefinition, type LayoutEnforcement, type LayoutViolation, MCP_TRANSPORT, MERGE_METHODS, MIMIMUM_RELEASE_AGE, MINIMUM_RELEASE_AGE, MONOREPO_LAYOUT, type McpServerConfig, type McpTransport, type MeetingArea, type MeetingScope, type MeetingType, type MeetingsConfig, type MergeMethod, type MonorepoLayoutRoot, MonorepoProject, type MonorepoProjectOptions, type OrganizationMetadata, PROD_DEPLOY_NAME, PnpmWorkspace, type PnpmWorkspaceOptions, type PriorityRule, ProjectMetadata, type ProjectMetadataOptions, REQUIREMENTS_WRITER_PATHS, ROOT_CI_TASK_NAME, ROOT_TURBO_TASK_NAME, type RemoteCacheOptions, type RepositoryMetadata, ResetTask, type ResetTaskOptions, type ResolvedAgentPaths, type ResolvedProjectMetadata, STARLIGHT_ROLE, type SlackMetadata, type SourceTierExamples, type StarlightEditLink, type StarlightLogo, StarlightProject, type StarlightProjectOptions, type StarlightRole, type StarlightSidebarItem, type StarlightSingletonViolation, type StarlightSocialLink, type SyncLabelsOptions, type TemplateResolveResult, TestRunner, TurboRepo, type TurboRepoOptions, TurboRepoTask, type TurboRepoTaskOptions, TypeScriptConfig, TypeScriptProject, type TypeScriptProjectOptions, VERSION, VERSION_KEYS_SKIP, VERSION_NPM_PACKAGES, VSCodeConfig, type VersionKey, Vitest, type VitestConfigOptions, type VitestOptions, addApproveMergeUpgradeWorkflow, addBuildCompleteJob, addSyncLabelsWorkflow, awsCdkBundle, baseBundle, bcmWriterBundle, companyProfileBundle, formatLayoutViolation, formatStarlightSingletonViolation, getLatestEligibleVersion, githubWorkflowBundle, industryDiscoveryBundle, jestBundle, maintenanceAuditBundle, meetingAnalysisBundle, orchestratorBundle, peopleProfileBundle, pnpmBundle, prReviewBundle, projenBundle, renderCustomDocSectionBlock, renderCustomDocSections, renderFocusSection, renderMeetingTypesSection, renderPriorityRulesSection, renderSourceTierExamples, requirementsAnalystBundle, requirementsReviewerBundle, requirementsWriterBundle, researchPipelineBundle, resolveAgentPaths, resolveAstroProjectOutdir, resolveAwsCdkProjectOutdir, resolveModelAlias, resolveOutdirFromPackageName, resolveTemplateVariables, resolveTypeScriptProjectOutdir, slackBundle, softwareProfileBundle, turborepoBundle, typescriptBundle, validateMonorepoLayout, validateStarlightSingleton, vitestBundle };
+export { AGENT_MODEL, AGENT_PLATFORM, AGENT_RULE_SCOPE, AgentConfig, type AgentConfigOptions, type AgentExpansionRules, type AgentFeaturesConfig, type AgentModel, type AgentPathsConfig, type AgentPlatform, type AgentPlatformOverrides, type AgentProcedure, type AgentRule, type AgentRuleBundle, type AgentRuleScope, type AgentSkill, type AgentSubAgent, type AgentSubAgentPlatformOverrides, type ApproveMergeUpgradeOptions, AstroConfig, type AstroConfigOptions, type AstroIntegrationSpec, AstroOutput, AstroProject, type AstroProjectOptions, type AwsAccount, AwsCdkProject, type AwsCdkProjectOptions, AwsDeployWorkflow, AwsDeploymentConfig, AwsDeploymentTarget, type AwsDeploymentTargetOptions, type AwsLocalDeploymentConfig, type AwsOrganization, type AwsRegion, AwsTeardownWorkflow, type AwsTeardownWorkflowOptions, BUILT_IN_BUNDLES, CLAUDE_RULE_TARGET, COMPLETE_JOB_ID, type CiDeploymentConfig, type ClassTypeOptions, type ClaudeAutoModeConfig, type ClaudeHookAction, type ClaudeHookEntry, type ClaudeHooksConfig, type ClaudePermissionsConfig, type ClaudeRuleTarget, type ClaudeSandboxConfig, type ClaudeSettingsConfig, type CopilotHandoff, type CursorHookAction, type CursorHooksConfig, type CursorSettingsConfig, type CustomDocSection, DEFAULT_AGENT_PATHS, DEFAULT_PRIORITY_LABELS, DEFAULT_STATUS_LABELS, DEFAULT_TEARDOWN_BRANCH_PATTERNS, DEFAULT_TYPE_LABELS, type DeployWorkflowOptions, type DeploymentMetadata, type FocusArea, type FocusAreaMatch, type FocusConfig, type GitBranch, type GitHubBoardMetadata, type GitHubProjectMetadata, type GitHubSprintMetadata, type IDependencyResolver, JsiiFaker, LAYOUT_ENFORCEMENT, LAYOUT_ROOT_BY_PROJECT_TYPE, type LabelDefinition, type LayoutEnforcement, type LayoutViolation, MCP_TRANSPORT, MERGE_METHODS, MIMIMUM_RELEASE_AGE, MINIMUM_RELEASE_AGE, MONOREPO_LAYOUT, type McpServerConfig, type McpTransport, type MeetingArea, type MeetingScope, type MeetingType, type MeetingTypeKind, type MeetingsConfig, type MergeMethod, type MonorepoLayoutRoot, MonorepoProject, type MonorepoProjectOptions, type OrganizationMetadata, PROD_DEPLOY_NAME, PnpmWorkspace, type PnpmWorkspaceOptions, type PriorityRule, ProjectMetadata, type ProjectMetadataOptions, REQUIREMENTS_WRITER_PATHS, ROOT_CI_TASK_NAME, ROOT_TURBO_TASK_NAME, type RemoteCacheOptions, type RepositoryMetadata, ResetTask, type ResetTaskOptions, type ResolvedAgentPaths, type ResolvedProjectMetadata, STARLIGHT_ROLE, type SlackMetadata, type SourceTierExamples, type StarlightEditLink, type StarlightLogo, StarlightProject, type StarlightProjectOptions, type StarlightRole, type StarlightSidebarItem, type StarlightSingletonViolation, type StarlightSocialLink, type SyncLabelsOptions, type TemplateResolveResult, TestRunner, TurboRepo, type TurboRepoOptions, TurboRepoTask, type TurboRepoTaskOptions, TypeScriptConfig, TypeScriptProject, type TypeScriptProjectOptions, VERSION, VERSION_KEYS_SKIP, VERSION_NPM_PACKAGES, VSCodeConfig, type VersionKey, Vitest, type VitestConfigOptions, type VitestOptions, addApproveMergeUpgradeWorkflow, addBuildCompleteJob, addSyncLabelsWorkflow, awsCdkBundle, baseBundle, bcmWriterBundle, companyProfileBundle, formatLayoutViolation, formatStarlightSingletonViolation, getLatestEligibleVersion, githubWorkflowBundle, industryDiscoveryBundle, jestBundle, maintenanceAuditBundle, meetingAnalysisBundle, orchestratorBundle, peopleProfileBundle, pnpmBundle, prReviewBundle, projenBundle, renderCustomDocSectionBlock, renderCustomDocSections, renderFocusSection, renderMeetingTypesSection, renderPriorityRulesSection, renderSourceTierExamples, requirementsAnalystBundle, requirementsReviewerBundle, requirementsWriterBundle, researchPipelineBundle, resolveAgentPaths, resolveAstroProjectOutdir, resolveAwsCdkProjectOutdir, resolveModelAlias, resolveOutdirFromPackageName, resolveTemplateVariables, resolveTypeScriptProjectOutdir, slackBundle, softwareProfileBundle, turborepoBundle, typescriptBundle, validateMonorepoLayout, validateStarlightSingleton, vitestBundle };

package/lib/index.d.ts

@@ -1192,6 +1192,33 @@ interface FocusConfig {
  *   customer / prospect / partner buckets.
  */
 type MeetingScope = "internal-recurring" | "internal-oneoff" | "external-customer" | "external-prospect" | "external-partner" | "external-other";
+/**
+ * Generic meeting-kind taxonomy. Each recognized meeting type maps to
+ * one of these kinds, which the `meeting-analysis` bundle uses to
+ * apply type-specific extraction rules in phases 1–2.
+ *
+ * The kind captures the **family** of meeting (how it should be
+ * extracted), independent of the concrete project-specific `id`. For
+ * example a repo may declare `founders-weekly` and `sprint-planning`
+ * as two distinct `id`s that both map to `kind: 'planning'`.
+ *
+ * - `planning` — sprint or project planning. Focus on tasks, goals,
+ *   and assignments. Produces direct sprint-plan edits and task
+ *   issues.
+ * - `review` — sprint review, retrospective, or decision review.
+ *   Captures retro learnings, status updates, and follow-ups.
+ * - `brainstorm` — open-ended ideation. Lower bar for Open Questions
+ *   and Future Features; higher bar for requirement/ADR creation
+ *   (only Firm items).
+ * - `standup` — short status meeting. Action items, blockers, sprint
+ *   status. Phase 3 (Draft) is almost always skipped.
+ * - `external` — customer, prospect, partner, or conference debrief.
+ *   Emphasizes people/company profiles, customer pain points (as BR
+ *   candidates, not FR), and competitive intel.
+ * - `other` — general meeting with no type-specific handling; the
+ *   default workflow applies.
+ */
+type MeetingTypeKind = "planning" | "review" | "brainstorm" | "standup" | "external" | "other";
 /**
  * A single meeting-type taxonomy entry declared by the consuming repo.
  * Each entry names a kind of meeting the project recognizes
@@ -1223,6 +1250,18 @@ interface MeetingType {
      * or one-off) or external (customer / prospect / partner / other).
      */
     readonly scope: MeetingScope;
+    /**
+     * Generic meeting kind this type maps to. Drives which type-specific
+     * extraction rules (Meeting Type Handling table) the `meeting-analysis`
+     * bundle applies in phases 1–2. Optional — when omitted, the bundle
+     * falls back to `other` (no type-specific rules).
+     *
+     * Multiple concrete `id`s can share the same `kind` (e.g., both
+     * `founders-weekly` and `sprint-planning` may map to `planning`).
+     *
+     * @example 'planning', 'standup', 'external'
+     */
+    readonly kind?: MeetingTypeKind;
     /**
      * Default scheduled duration in minutes. Optional; agents may use
      * this when proposing calendar holds or when validating a
@@ -1246,14 +1285,17 @@ interface MeetingType {
 }
 /**
  * A single meeting-area entry. Meeting areas provide a coarse
- * routing map from an `area` frontmatter value on a meeting note to
- * the sub-tree of the docs root where phase-4 direct edits should
- * land.
+ * routing map from entries in an `areas:` frontmatter list on a
+ * meeting note to the sub-tree of the docs root where phase-4
+ * direct edits should land. A single meeting may declare multiple
+ * areas; every matching entry's `docRoot` is in-scope for direct
+ * edits on that meeting (see the `meeting-analyst` agent's
+ * **Areas filtering** section for the full gating contract).
  *
  * Example: declaring `{ id: 'product-engineering', label: 'Product &
  * Engineering', docRoot: 'product' }` tells the `meeting-analysis`
  * bundle that a meeting whose frontmatter carries
- * `area: product-engineering` should have its direct edits routed
+ * `areas: [product-engineering]` should have its direct edits routed
  * under `<docsRoot>/product/`.
  *
  * When `AgentConfigOptions.meetings.meetingAreas` is non-empty, the
@@ -1266,8 +1308,8 @@ interface MeetingType {
  */
 interface MeetingArea {
     /**
-     * Stable machine identifier for the area. Matches the `area`
-     * frontmatter value on meeting notes.
+     * Stable machine identifier for the area. Matches one of the
+     * entries in the `areas:` frontmatter list on meeting notes.
      * @example 'product-engineering', 'go-to-market', 'operations'
      */
     readonly id: string;
@@ -1288,7 +1330,8 @@ interface MeetingArea {
  * templating a meeting. Every field is optional.
  *
  * - `meetingTypes` — the set of meeting types the repo recognizes.
- * - `meetingAreas` — maps `area` frontmatter to doc-root sub-trees.
+ * - `meetingAreas` — maps entries in the `areas:` frontmatter list
+ *   to doc-root sub-trees.
  * - `agendaTemplateRoot` — where pre-meeting agenda skeletons live.
  *
  * When supplied, the `meeting-analysis` bundle conditionally renders
@@ -1996,9 +2039,9 @@ declare function renderFocusSection(focus: FocusConfig | undefined): string;
  * Two subsections are rendered, each gated on its own input array:
  *
  * 1. **Recognized meeting types** — rendered when `meetingTypes` is
- *    non-empty. Lists every declared type with its scope, optional
- *    cadence, default duration, and agenda template path. Also
- *    documents the resolved `agendaTemplateRoot`.
+ *    non-empty. Lists every declared type with its scope, kind,
+ *    optional cadence, default duration, and agenda template path.
+ *    Also documents the resolved `agendaTemplateRoot`.
  * 2. **Area → doc-root mapping** — rendered when `meetingAreas` is
  *    non-empty. Lists every declared area with its `id`, label, and
  *    docs-root-relative destination folder.
@@ -4745,4 +4788,4 @@ declare const COMPLETE_JOB_ID = "complete";
 declare function addBuildCompleteJob(buildWorkflow: BuildWorkflow): void;
 
 export { AGENT_MODEL, AGENT_PLATFORM, AGENT_RULE_SCOPE, AgentConfig, AstroConfig, AstroOutput, AstroProject, AwsCdkProject, AwsDeployWorkflow, AwsDeploymentConfig, AwsDeploymentTarget, AwsTeardownWorkflow, BUILT_IN_BUNDLES, CLAUDE_RULE_TARGET, COMPLETE_JOB_ID, DEFAULT_AGENT_PATHS, DEFAULT_PRIORITY_LABELS, DEFAULT_STATUS_LABELS, DEFAULT_TEARDOWN_BRANCH_PATTERNS, DEFAULT_TYPE_LABELS, JsiiFaker, LAYOUT_ENFORCEMENT, LAYOUT_ROOT_BY_PROJECT_TYPE, MCP_TRANSPORT, MERGE_METHODS, MIMIMUM_RELEASE_AGE, MINIMUM_RELEASE_AGE, MONOREPO_LAYOUT, MonorepoProject, PROD_DEPLOY_NAME, PnpmWorkspace, ProjectMetadata, REQUIREMENTS_WRITER_PATHS, ROOT_CI_TASK_NAME, ROOT_TURBO_TASK_NAME, ResetTask, STARLIGHT_ROLE, StarlightProject, TestRunner, TurboRepo, TurboRepoTask, TypeScriptConfig, TypeScriptProject, VERSION, VERSION_KEYS_SKIP, VERSION_NPM_PACKAGES, VSCodeConfig, Vitest, addApproveMergeUpgradeWorkflow, addBuildCompleteJob, addSyncLabelsWorkflow, awsCdkBundle, baseBundle, bcmWriterBundle, companyProfileBundle, formatLayoutViolation, formatStarlightSingletonViolation, getLatestEligibleVersion, githubWorkflowBundle, industryDiscoveryBundle, jestBundle, maintenanceAuditBundle, meetingAnalysisBundle, orchestratorBundle, peopleProfileBundle, pnpmBundle, prReviewBundle, projenBundle, renderCustomDocSectionBlock, renderCustomDocSections, renderFocusSection, renderMeetingTypesSection, renderPriorityRulesSection, renderSourceTierExamples, requirementsAnalystBundle, requirementsReviewerBundle, requirementsWriterBundle, researchPipelineBundle, resolveAgentPaths, resolveAstroProjectOutdir, resolveAwsCdkProjectOutdir, resolveModelAlias, resolveOutdirFromPackageName, resolveTemplateVariables, resolveTypeScriptProjectOutdir, slackBundle, softwareProfileBundle, turborepoBundle, typescriptBundle, validateMonorepoLayout, validateStarlightSingleton, vitestBundle };
-export type { AgentConfigOptions, AgentExpansionRules, AgentFeaturesConfig, AgentModel, AgentPathsConfig, AgentPlatform, AgentPlatformOverrides, AgentProcedure, AgentRule, AgentRuleBundle, AgentRuleScope, AgentSkill, AgentSubAgent, AgentSubAgentPlatformOverrides, ApproveMergeUpgradeOptions, AstroConfigOptions, AstroIntegrationSpec, AstroProjectOptions, AwsAccount, AwsCdkProjectOptions, AwsDeploymentTargetOptions, AwsLocalDeploymentConfig, AwsOrganization, AwsRegion, AwsTeardownWorkflowOptions, CiDeploymentConfig, ClassTypeOptions, ClaudeAutoModeConfig, ClaudeHookAction, ClaudeHookEntry, ClaudeHooksConfig, ClaudePermissionsConfig, ClaudeRuleTarget, ClaudeSandboxConfig, ClaudeSettingsConfig, CopilotHandoff, CursorHookAction, CursorHooksConfig, CursorSettingsConfig, CustomDocSection, DeployWorkflowOptions, DeploymentMetadata, FocusArea, FocusAreaMatch, FocusConfig, GitBranch, GitHubBoardMetadata, GitHubProjectMetadata, GitHubSprintMetadata, IDependencyResolver, LabelDefinition, LayoutEnforcement, LayoutViolation, McpServerConfig, McpTransport, MeetingArea, MeetingScope, MeetingType, MeetingsConfig, MergeMethod, MonorepoLayoutRoot, MonorepoProjectOptions, OrganizationMetadata, PnpmWorkspaceOptions, PriorityRule, ProjectMetadataOptions, RemoteCacheOptions, RepositoryMetadata, ResetTaskOptions, ResolvedAgentPaths, ResolvedProjectMetadata, SlackMetadata, SourceTierExamples, StarlightEditLink, StarlightLogo, StarlightProjectOptions, StarlightRole, StarlightSidebarItem, StarlightSingletonViolation, StarlightSocialLink, SyncLabelsOptions, TemplateResolveResult, TurboRepoOptions, TurboRepoTaskOptions, TypeScriptProjectOptions, VersionKey, VitestConfigOptions, VitestOptions };
+export type { AgentConfigOptions, AgentExpansionRules, AgentFeaturesConfig, AgentModel, AgentPathsConfig, AgentPlatform, AgentPlatformOverrides, AgentProcedure, AgentRule, AgentRuleBundle, AgentRuleScope, AgentSkill, AgentSubAgent, AgentSubAgentPlatformOverrides, ApproveMergeUpgradeOptions, AstroConfigOptions, AstroIntegrationSpec, AstroProjectOptions, AwsAccount, AwsCdkProjectOptions, AwsDeploymentTargetOptions, AwsLocalDeploymentConfig, AwsOrganization, AwsRegion, AwsTeardownWorkflowOptions, CiDeploymentConfig, ClassTypeOptions, ClaudeAutoModeConfig, ClaudeHookAction, ClaudeHookEntry, ClaudeHooksConfig, ClaudePermissionsConfig, ClaudeRuleTarget, ClaudeSandboxConfig, ClaudeSettingsConfig, CopilotHandoff, CursorHookAction, CursorHooksConfig, CursorSettingsConfig, CustomDocSection, DeployWorkflowOptions, DeploymentMetadata, FocusArea, FocusAreaMatch, FocusConfig, GitBranch, GitHubBoardMetadata, GitHubProjectMetadata, GitHubSprintMetadata, IDependencyResolver, LabelDefinition, LayoutEnforcement, LayoutViolation, McpServerConfig, McpTransport, MeetingArea, MeetingScope, MeetingType, MeetingTypeKind, MeetingsConfig, MergeMethod, MonorepoLayoutRoot, MonorepoProjectOptions, OrganizationMetadata, PnpmWorkspaceOptions, PriorityRule, ProjectMetadataOptions, RemoteCacheOptions, RepositoryMetadata, ResetTaskOptions, ResolvedAgentPaths, ResolvedProjectMetadata, SlackMetadata, SourceTierExamples, StarlightEditLink, StarlightLogo, StarlightProjectOptions, StarlightRole, StarlightSidebarItem, StarlightSingletonViolation, StarlightSocialLink, SyncLabelsOptions, TemplateResolveResult, TurboRepoOptions, TurboRepoTaskOptions, TypeScriptProjectOptions, VersionKey, VitestConfigOptions, VitestOptions };

package/lib/index.js

@@ -5285,6 +5285,86 @@ var meetingAnalystSubAgent = {
     "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`).",
     "",
     "---",
     "",
@@ -5342,7 +5422,13 @@ var meetingAnalystSubAgent = {
     "",
     "### Steps",
     "",
-    "1. Read the transcript file specified in the issue body.",
+    "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 |",
@@ -5368,14 +5454,32 @@ var meetingAnalystSubAgent = {
     "   - Companies of Interest (with type and context)",
     "   - Strategic / Product Direction",
     "",
-    "4. **Create downstream phase issues** using `gh issue create`:",
+    "   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)",
+    "     (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",
     "",
-    "5. Commit, push, and close the extract issue.",
+    "6. Commit, push, and close the extract issue.",
     "",
     "---",
     "",
@@ -5432,18 +5536,38 @@ var meetingAnalystSubAgent = {
     "### 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.",
+    "   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.",
+    "   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.",
-    "5. Cross-reference the meeting in any existing documents that were discussed.",
-    "6. Apply direct product/strategy doc updates for items flagged as **Firm**",
-    "   confidence in the extraction.",
+    "   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.",
+    "   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",
@@ -5527,7 +5651,17 @@ var meetingAnalysisBundle = {
         "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."
+        "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 }
@@ -16358,18 +16492,24 @@ function renderMeetingTypes(types, agendaTemplateRoot) {
     "This project declares a meeting-type taxonomy through",
     "`AgentConfigOptions.meetings.meetingTypes`. When classifying a",
     "meeting transcript, pick the `id` from this list that best fits the",
-    "meeting; do **not** invent new type identifiers. Agenda-template",
-    `paths below are resolved relative to \`${resolvedRoot}\`.`,
-    "",
-    "| ID | Label | Scope | Cadence | Default duration | Agenda template |",
-    "|----|-------|-------|---------|------------------|-----------------|"
+    "meeting; do **not** invent new type identifiers. The `Kind` column",
+    "maps each concrete `id` onto the generic meeting-kind taxonomy",
+    "(`planning` / `review` / `brainstorm` / `standup` / `external` /",
+    "`other`) documented in the **Meeting type handling** section \u2014",
+    "apply the type-specific rules listed there based on this kind.",
+    "Agenda-template paths below are resolved relative to",
+    `\`${resolvedRoot}\`.`,
+    "",
+    "| ID | Label | Kind | Scope | Cadence | Default duration | Agenda template |",
+    "|----|-------|------|-------|---------|------------------|-----------------|"
   ];
   for (const type of types) {
+    const kind = type.kind ? `\`${type.kind}\`` : "\u2014";
     const cadence = type.cadence ? `\`${type.cadence}\`` : "\u2014";
     const duration = type.defaultDurationMinutes !== void 0 ? `${type.defaultDurationMinutes} min` : "\u2014";
     const template = type.agendaTemplatePath ? `\`${type.agendaTemplatePath}\`` : "\u2014";
     lines.push(
-      `| \`${type.id}\` | ${type.label} | \`${type.scope}\` | ${cadence} | ${duration} | ${template} |`
+      `| \`${type.id}\` | ${type.label} | ${kind} | \`${type.scope}\` | ${cadence} | ${duration} | ${template} |`
     );
   }
   return lines.join("\n");
@@ -16380,10 +16520,12 @@ function renderMeetingAreas(areas) {
     "",
     "This project declares a meeting-area routing map through",
     "`AgentConfigOptions.meetings.meetingAreas`. When a meeting note's",
-    "frontmatter carries an `area:` value matching an `id` below, route",
-    "phase-4 direct edits into the corresponding sub-tree of the docs",
-    "root (`AgentPathsConfig.docsRoot`). Meetings whose `area` does not",
-    "match any declared entry fall back to the default meetings root.",
+    "frontmatter carries an `areas:` list, route phase-4 direct edits",
+    "into the corresponding sub-trees of the docs root",
+    "(`AgentPathsConfig.docsRoot`). See the **Areas filtering** section",
+    "of the `meeting-analyst` agent for the full gating contract.",
+    "Meetings whose `areas` list is empty or does not match any",
+    "declared entry fall back to the default meetings root.",
     "",
     "| Area ID | Label | Doc-root sub-folder |",
     "|---------|-------|---------------------|"