@codedrifters/configulator 0.0.255 → 0.0.257

package/lib/index.d.mts

@@ -970,6 +970,314 @@ interface PriorityRule {
      */
     readonly rationale: string;
 }
+/*******************************************************************************
+ *
+ * Focus Scoring
+ *
+ ******************************************************************************/
+/**
+ * Match predicate for a single focus area. At least one sub-field
+ * should be set; multiple sub-fields on the same match combine as a
+ * logical OR (any one matching contributes the focus area's weight).
+ *
+ * @see FocusArea
+ */
+interface FocusAreaMatch {
+    /** Any of these labels present on the issue matches. */
+    readonly labels?: ReadonlyArray<string>;
+    /**
+     * Case-insensitive substrings matched against the issue title.
+     * A hit on any single keyword fires the match.
+     */
+    readonly titleKeywords?: ReadonlyArray<string>;
+    /**
+     * Case-insensitive substrings matched against the issue body.
+     * A hit on any single keyword fires the match.
+     */
+    readonly bodyKeywords?: ReadonlyArray<string>;
+}
+/**
+ * A single scored focus area — a named customer, segment,
+ * organization, software product, regulation, or person the project
+ * cares about right now. Matching issues receive this area's
+ * `weight` as a priority boost at triage time.
+ *
+ * @see FocusConfig
+ * @see ./bundles/focus.ts#renderFocusSection
+ */
+interface FocusArea {
+    /** Human-readable name for the focus area (e.g. "Acme Corp"). */
+    readonly name: string;
+    /**
+     * Consuming-repo-defined vocabulary describing what kind of entity
+     * this focus area represents (e.g. `"customer"`, `"segment"`,
+     * `"organization"`, `"software"`, `"regulation"`, `"person"`).
+     * The `AgentExpansionRules.allowedTypes` /
+     * `AgentExpansionRules.forbiddenTypes` lists gate what values
+     * agents are permitted to introduce.
+     */
+    readonly type: string;
+    /**
+     * Provenance. `"human"` entries are curated by a maintainer;
+     * `"agent"` entries were appended by an agent under the
+     * agent-expansion rules and must carry a `discoveredIn` reference.
+     */
+    readonly source: "human" | "agent";
+    /**
+     * Issue reference (e.g. `"#123"`) that introduced the focus area.
+     * Required when `source` is `"agent"` so the provenance of every
+     * agent-appended entry is auditable; optional for human entries.
+     */
+    readonly discoveredIn?: string;
+    /** Match predicate that decides which issues this area applies to. */
+    readonly match: FocusAreaMatch;
+    /**
+     * Positive integer weight contributed to the issue's focus score
+     * when the match fires. Consuming repos typically cap this with
+     * `AgentExpansionRules.maxWeight` (default 8 in openhi's reference
+     * implementation).
+     */
+    readonly weight: number;
+}
+/**
+ * Guard-rails on what agents are allowed to append to `focus.json`
+ * without human review. The agent-expansion contract is append-only:
+ * agents never modify or remove existing entries.
+ */
+interface AgentExpansionRules {
+    /**
+     * Hard cap on the `weight` an agent may set on a newly appended
+     * focus area. Human curators may use higher weights.
+     */
+    readonly maxWeight: number;
+    /**
+     * Whitelist of `FocusArea.type` values agents are permitted to
+     * introduce. Any type outside this list must be added by a human.
+     */
+    readonly allowedTypes: ReadonlyArray<string>;
+    /**
+     * Explicit blocklist of `FocusArea.type` values agents must never
+     * introduce, even if the list accidentally overlaps
+     * `allowedTypes`. `forbiddenTypes` wins on conflict.
+     */
+    readonly forbiddenTypes: ReadonlyArray<string>;
+    /**
+     * Optional cap on the number of entries in each keyword array
+     * (`match.labels`, `match.titleKeywords`, `match.bodyKeywords`)
+     * on an agent-appended focus area. Prevents runaway keyword
+     * expansion. Human entries are not subject to this cap.
+     */
+    readonly maxKeywords?: number;
+}
+/**
+ * Top-level configuration for the focus-scoring engine. The schema
+ * and agent-expansion rules live in the configulator bundle; the
+ * actual `focus.json` file is authored and curated in the consuming
+ * repo.
+ *
+ * When supplied via `AgentConfigOptions.focus`, the `base` bundle
+ * appends a "Focus scoring" subsection to the
+ * `issue-label-conventions` rule that teaches agents how to read
+ * `focus.json`, how focus weight interacts with the
+ * `priority:*` taxonomy, and what they may and may not append to
+ * the file.
+ *
+ * @see FocusArea
+ * @see AgentExpansionRules
+ * @see ./bundles/focus.ts#renderFocusSection
+ */
+interface FocusConfig {
+    /**
+     * Path to the focus file relative to the repo root.
+     * @default ".claude/focus.json"
+     */
+    readonly focusFilePath?: string;
+    /**
+     * Schema version the consuming repo's `focus.json` conforms to.
+     * Bump when the schema changes in a backwards-incompatible way.
+     * @default 1
+     */
+    readonly schemaVersion?: number;
+    /**
+     * Cumulative focus-score thresholds that map into the
+     * `priority:*` taxonomy. An issue whose total focus score
+     * (sum of matched focus-area weights) reaches `high` is boosted
+     * to `priority:high`; reaching `medium` keeps it at
+     * `priority:medium`. Scores below `medium` do not affect the
+     * inferred priority.
+     *
+     * @remarks `high` and `medium` must be integers. The JSON schema
+     * at `schemas/focus.schema.json` enforces this for `focus.json`.
+     */
+    readonly thresholds?: {
+        readonly high: number;
+        readonly medium: number;
+    };
+    /**
+     * Guard-rails that govern what agents may append to `focus.json`.
+     * When omitted, the rendered rule documents that agents must
+     * **not** append to `focus.json` without human review.
+     */
+    readonly agentExpansionRules?: AgentExpansionRules;
+}
+/*******************************************************************************
+ *
+ * Meetings Config
+ *
+ ******************************************************************************/
+/**
+ * Scope classifier for a meeting type. Used by the `meeting-analysis`
+ * bundle to reason about where a given meeting belongs (internal vs
+ * external) and, for external meetings, the nature of the other party.
+ *
+ * - `internal-recurring` — recurring internal meeting (weekly standup,
+ *   team sync, planning cadence).
+ * - `internal-oneoff` — one-off internal meeting (brainstorm, kickoff,
+ *   retro).
+ * - `external-customer` — meeting with an existing paying customer.
+ * - `external-prospect` — meeting with a sales prospect not yet under
+ *   contract.
+ * - `external-partner` — meeting with a partner (integration, vendor,
+ *   channel).
+ * - `external-other` — any external meeting that does not fit the
+ *   customer / prospect / partner buckets.
+ */
+type MeetingScope = "internal-recurring" | "internal-oneoff" | "external-customer" | "external-prospect" | "external-partner" | "external-other";
+/**
+ * A single meeting-type taxonomy entry declared by the consuming repo.
+ * Each entry names a kind of meeting the project recognizes
+ * (`founders-weekly`, `customer-discovery`, etc.) and supplies the
+ * per-type metadata agents need to route, default, and template that
+ * meeting.
+ *
+ * When `AgentConfigOptions.meetings.meetingTypes` is non-empty, the
+ * `meeting-analysis` bundle renders a "Recognized meeting types"
+ * subsection listing every declared type so agents pick from the
+ * project's vocabulary rather than guessing.
+ *
+ * @see MeetingsConfig
+ * @see ./bundles/meeting-types.ts#renderMeetingTypesSection
+ */
+interface MeetingType {
+    /**
+     * Stable machine identifier for the meeting type. Used as the
+     * `meeting_type` frontmatter value on meeting notes and as the key
+     * that the future `agenda` bundle will look up when selecting a
+     * pre-meeting template.
+     * @example 'founders-weekly', 'customer-discovery', 'sprint-review'
+     */
+    readonly id: string;
+    /** Human-readable label shown in generated rule content. */
+    readonly label: string;
+    /**
+     * Scope classification — whether the meeting is internal (recurring
+     * or one-off) or external (customer / prospect / partner / other).
+     */
+    readonly scope: MeetingScope;
+    /**
+     * Default scheduled duration in minutes. Optional; agents may use
+     * this when proposing calendar holds or when validating a
+     * transcript's recorded duration against the type's expected
+     * duration.
+     */
+    readonly defaultDurationMinutes?: number;
+    /**
+     * Path to a pre-meeting agenda skeleton for this type, resolved
+     * relative to `MeetingsConfig.agendaTemplateRoot`. Optional — a
+     * type without a template simply has no canned agenda.
+     * @example 'founders-weekly.md', 'customer-discovery/v2.md'
+     */
+    readonly agendaTemplatePath?: string;
+    /**
+     * Human-readable cadence descriptor. Free-form text — agents
+     * surface the string verbatim rather than parsing it.
+     * @example 'weekly', 'every 2 weeks', 'one-off'
+     */
+    readonly cadence?: string;
+}
+/**
+ * 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.
+ *
+ * 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
+ * under `<docsRoot>/product/`.
+ *
+ * When `AgentConfigOptions.meetings.meetingAreas` is non-empty, the
+ * `meeting-analysis` bundle renders an "Area → doc-root mapping"
+ * subsection documenting every declared area and its resolved
+ * destination.
+ *
+ * @see MeetingsConfig
+ * @see ./bundles/meeting-types.ts#renderMeetingTypesSection
+ */
+interface MeetingArea {
+    /**
+     * Stable machine identifier for the area. Matches the `area`
+     * frontmatter value on meeting notes.
+     * @example 'product-engineering', 'go-to-market', 'operations'
+     */
+    readonly id: string;
+    /** Human-readable label shown in generated rule content. */
+    readonly label: string;
+    /**
+     * Destination folder for phase-4 direct edits on meeting notes
+     * carrying this area. Interpreted **relative to the resolved
+     * docs root** (`AgentPathsConfig.docsRoot`, default
+     * `docs/src/content/docs`). Do not include a leading slash.
+     * @example 'product', 'gtm', 'operations'
+     */
+    readonly docRoot: string;
+}
+/**
+ * Meeting-analysis injection points — the set of typed
+ * configurations agents consult when classifying, routing, and
+ * 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.
+ * - `agendaTemplateRoot` — where pre-meeting agenda skeletons live.
+ *
+ * When supplied, the `meeting-analysis` bundle conditionally renders
+ * two new subsections into the `meeting-processing-workflow` rule —
+ * "Recognized meeting types" (when `meetingTypes` is non-empty) and
+ * "Area → doc-root mapping" (when `meetingAreas` is non-empty).
+ *
+ * @see MeetingType
+ * @see MeetingArea
+ * @see ./bundles/meeting-types.ts#renderMeetingTypesSection
+ */
+interface MeetingsConfig {
+    /**
+     * Meeting-type taxonomy. An empty or missing list means the
+     * consuming repo does not classify meetings by type; the
+     * `meeting-analysis` bundle falls back to its generic 4-phase
+     * behaviour.
+     */
+    readonly meetingTypes?: ReadonlyArray<MeetingType>;
+    /**
+     * Meeting-area map. An empty or missing list means the consuming
+     * repo does not route meetings by area; phase-4 direct edits
+     * continue to land under the default meetings root.
+     */
+    readonly meetingAreas?: ReadonlyArray<MeetingArea>;
+    /**
+     * Root folder containing pre-meeting agenda-template skeletons.
+     * Resolved at issue-creation time by the (future) `agenda` bundle
+     * when selecting a template for a given `meeting_type`.
+     *
+     * When unset, the `meeting-analysis` bundle documents the default
+     * of `<meetingsRoot>/_agenda-templates` — consumers that wire a
+     * custom `AgentPathsConfig.meetingsRoot` inherit the override
+     * automatically.
+     * @default "<meetingsRoot>/_agenda-templates"
+     */
+    readonly agendaTemplateRoot?: string;
+}
 /*******************************************************************************
  *
  * AgentConfig Options
@@ -1082,6 +1390,46 @@ interface AgentConfigOptions {
      * @see ./bundles/priority-rules.ts#renderPriorityRulesSection
      */
     readonly priorityRules?: ReadonlyArray<PriorityRule>;
+    /**
+     * Focus-scoring configuration. Declares the path to the consuming
+     * repo's `focus.json` file, score thresholds, and the
+     * agent-expansion rules that govern what agents may append to the
+     * file.
+     *
+     * When set, the `base` bundle appends a "Focus scoring"
+     * subsection to the `issue-label-conventions` rule that teaches
+     * agents (a) how to read `focus.json`, (b) how focus weight
+     * interacts with the `priority:*` taxonomy, and (c) the
+     * agent-driven expansion contract. The actual `focus.json` file
+     * is authored and curated in the consuming repo — configulator
+     * ships the schema and agent instructions only.
+     *
+     * @see FocusConfig
+     * @see FocusArea
+     * @see AgentExpansionRules
+     * @see ./bundles/focus.ts#renderFocusSection
+     */
+    readonly focus?: FocusConfig;
+    /**
+     * Meeting-analysis injection points — typed configs the
+     * `meeting-analysis` bundle consults when classifying, routing, and
+     * templating meetings. Supplies the meeting-type taxonomy, the
+     * area → doc-root routing map, and the agenda-template root used
+     * by the (future) `agenda` bundle.
+     *
+     * When `meetingTypes` is non-empty, the `meeting-analysis` bundle
+     * appends a "Recognized meeting types" subsection to the
+     * `meeting-processing-workflow` rule. When `meetingAreas` is
+     * non-empty, it appends an "Area → doc-root mapping" subsection.
+     * When both are empty or unset, the generated rule content is
+     * unchanged from the no-config baseline.
+     *
+     * @see MeetingsConfig
+     * @see MeetingType
+     * @see MeetingArea
+     * @see ./bundles/meeting-types.ts#renderMeetingTypesSection
+     */
+    readonly meetings?: MeetingsConfig;
 }
 
 /**
@@ -1354,6 +1702,47 @@ declare const prReviewBundle: AgentRuleBundle;
  */
 declare const projenBundle: AgentRuleBundle;
 
+/**
+ * Render the markdown subsection appended to the
+ * `issue-label-conventions` rule when `AgentConfigOptions.focus` is
+ * supplied. Returns an empty string when `focus` is undefined so
+ * callers can unconditionally concatenate the result.
+ *
+ * The section documents three things for agents:
+ *
+ * 1. How to read `focus.json` at triage time
+ * 2. How focus weight interacts with the `priority:*` taxonomy
+ * 3. The agent-driven expansion contract (what agents may append)
+ *
+ * Configulator ships this rule content plus a JSON Schema that
+ * validates the `focus.json` file; the file itself is authored and
+ * curated in the consuming repo.
+ */
+declare function renderFocusSection(focus: FocusConfig | undefined): string;
+
+/**
+ * Render the markdown subsections appended to the
+ * `meeting-processing-workflow` rule when `AgentConfigOptions.meetings`
+ * is supplied. Returns an empty string when the supplied config has
+ * nothing to render (no meeting types and no meeting areas) so callers
+ * can unconditionally concatenate the result.
+ *
+ * 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`.
+ * 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.
+ *
+ * Bundles consume the rendered string by appending it to their own
+ * rule content. A caller that has no meeting types and no meeting
+ * areas receives an empty string and can safely concatenate.
+ */
+declare function renderMeetingTypesSection(meetings: MeetingsConfig | undefined): string;
+
 /**
  * Render the markdown subsection appended to the
  * `issue-label-conventions` rule when `AgentConfigOptions.priorityRules`
@@ -4088,4 +4477,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 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, DEFAULT_AGENT_PATHS, DEFAULT_PRIORITY_LABELS, DEFAULT_STATUS_LABELS, DEFAULT_TEARDOWN_BRANCH_PATTERNS, DEFAULT_TYPE_LABELS, type DeployWorkflowOptions, type DeploymentMetadata, 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 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 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, renderPriorityRulesSection, 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 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, 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 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, renderFocusSection, renderMeetingTypesSection, renderPriorityRulesSection, requirementsAnalystBundle, requirementsReviewerBundle, requirementsWriterBundle, researchPipelineBundle, resolveAgentPaths, resolveAstroProjectOutdir, resolveAwsCdkProjectOutdir, resolveModelAlias, resolveOutdirFromPackageName, resolveTemplateVariables, resolveTypeScriptProjectOutdir, slackBundle, softwareProfileBundle, turborepoBundle, typescriptBundle, validateMonorepoLayout, validateStarlightSingleton, vitestBundle };