@codedrifters/configulator 0.0.256 → 0.0.258

package/lib/index.d.mts

@@ -1120,6 +1120,302 @@ interface FocusConfig {
      */
     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;
+}
+/*******************************************************************************
+ *
+ * Agent Features Config
+ *
+ ******************************************************************************/
+/**
+ * Per-tier lists of domain-specific source examples injected into the
+ * base bundle's "Source Quality & Verification" rule under each of the
+ * T1 / T2 / T3 / T4 headings.
+ *
+ * Every field is optional. When a field is set, the `base` bundle
+ * renders a bullet list of the supplied examples beneath the
+ * corresponding tier heading; when a field is unset, the tier heading
+ * renders with its generic examples only.
+ *
+ * The examples are emitted verbatim — supply fully-formed descriptive
+ * strings ("FHIR R4 capability statements", "SEC EDGAR filings").
+ *
+ * @see AgentFeaturesConfig
+ * @see ./bundles/features.ts#renderSourceTierExamples
+ */
+interface SourceTierExamples {
+    /**
+     * Primary living sources — T1. Examples that update when reality
+     * changes (official product docs, company about/leadership pages,
+     * live government registries).
+     */
+    readonly t1?: ReadonlyArray<string>;
+    /**
+     * Primary snapshot sources — T2. Examples that capture a moment in
+     * time from the authoritative party (press releases, earnings
+     * transcripts, regulatory filings, conference presentations).
+     */
+    readonly t2?: ReadonlyArray<string>;
+    /**
+     * Secondary sources — T3. Examples that interpret primary material
+     * (news articles, trade press, analyst reports, industry databases).
+     */
+    readonly t3?: ReadonlyArray<string>;
+    /**
+     * Self-reported or marketing sources — T4. Examples that require
+     * corroboration before any factual claim rides on them (vendor
+     * comparison pages, testimonials, social posts, job listings,
+     * Wikipedia).
+     */
+    readonly t4?: ReadonlyArray<string>;
+}
+/**
+ * A single consumer-supplied doc-section template injected into a
+ * bundle's rule content at rule-generation time.
+ *
+ * The configulator framework is deliberately generic here — it
+ * matches by `bundleName` and appends `body` verbatim under a new
+ * `## <sectionTitle>` heading after the first rule in the target
+ * bundle whose content contains `## <afterSection>`. Named feature
+ * toggles (stealth-mode, consortium-model, etc.) belong in downstream
+ * consumer repos that compose the primitive this interface exposes.
+ *
+ * Placeholder substitution (`{{foo}}`) is **not** performed at
+ * rule-generation time — the `body` string is emitted verbatim.
+ * Any templating is the agent's responsibility at document-authoring
+ * time, not configulator's.
+ *
+ * @see AgentFeaturesConfig
+ * @see ./bundles/features.ts#renderCustomDocSection
+ */
+interface CustomDocSection {
+    /**
+     * Target bundle id. Must match an `AgentRuleBundle.name` that is
+     * active in the project. If no active bundle has this name, the
+     * section is silently dropped.
+     * @example 'company-profile', 'meeting-analysis', 'bcm-writer'
+     */
+    readonly bundleName: string;
+    /**
+     * Heading text (without any leading `#` characters) of the existing
+     * section this custom section is inserted after. The framework
+     * searches every rule in the target bundle for a heading line at
+     * any level (`#` through `######`) whose text equals `afterSection`;
+     * the first rule that contains such a heading is the insertion site.
+     * Matching any level lets consumers hook into single-`#` bundle-rule
+     * titles (e.g. `# Company Profile Workflow`) as well as nested `##` /
+     * `###` subsections. If no rule contains a matching heading, the
+     * section is silently dropped.
+     *
+     * Multiple entries targeting the same heading render in supplied
+     * order — the first entry lands directly beneath the target heading
+     * block, the second below it, and so on.
+     * @example 'Company Profile Workflow', 'Company Type Taxonomy', 'Output Boundaries'
+     */
+    readonly afterSection: string;
+    /**
+     * Heading text for the injected section, rendered as
+     * `## <sectionTitle>`.
+     * @example 'Consortium Membership', 'Vortex Relevance'
+     */
+    readonly sectionTitle: string;
+    /**
+     * Markdown body emitted verbatim beneath the `## <sectionTitle>`
+     * heading. Trailing newlines are trimmed before rendering.
+     */
+    readonly body: string;
+}
+/**
+ * Framework injection points for source-tier customization and
+ * custom doc sections. Supplied via `AgentConfigOptions.features`.
+ *
+ * - `sourceTierExamples` — per-tier domain-specific examples that get
+ *   listed under each tier in the base bundle's "Source Quality &
+ *   Verification" rule.
+ * - `customDocSections` — per-bundle section templates that render
+ *   verbatim after an existing section heading in the target bundle's
+ *   rule content.
+ *
+ * Named feature toggles (`consortium-model`, `stealth-mode`, etc.)
+ * are deliberately **not** part of this config surface. They belong
+ * in downstream consumer repos built on top of the generic
+ * `customDocSections` primitive.
+ *
+ * @see SourceTierExamples
+ * @see CustomDocSection
+ * @see ./bundles/features.ts
+ */
+interface AgentFeaturesConfig {
+    /**
+     * Per-tier lists of domain-specific source examples injected under
+     * T1 / T2 / T3 / T4 in the base bundle's "Source Quality &
+     * Verification" rule.
+     */
+    readonly sourceTierExamples?: SourceTierExamples;
+    /**
+     * Custom doc-section templates to inject into active bundles at
+     * rule-generation time. Each entry names the target bundle, the
+     * section heading to insert after, the injected section's title,
+     * and the body to emit verbatim.
+     */
+    readonly customDocSections?: ReadonlyArray<CustomDocSection>;
+}
 /*******************************************************************************
  *
  * AgentConfig Options
@@ -1252,6 +1548,47 @@ interface AgentConfigOptions {
      * @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;
+    /**
+     * Framework injection points for source-tier customization and
+     * custom doc sections.
+     *
+     * - `sourceTierExamples` — domain-specific examples injected under
+     *   T1 / T2 / T3 / T4 in the base bundle's "Source Quality &
+     *   Verification" rule.
+     * - `customDocSections` — consumer-supplied section templates that
+     *   render verbatim after an existing section heading in a target
+     *   bundle's rule content.
+     *
+     * Named feature toggles (`consortium-model`, `stealth-mode`, etc.)
+     * are intentionally out of scope here — build those on top of
+     * `customDocSections` inside the consuming repo's projen config.
+     *
+     * @see AgentFeaturesConfig
+     * @see SourceTierExamples
+     * @see CustomDocSection
+     * @see ./bundles/features.ts
+     */
+    readonly features?: AgentFeaturesConfig;
 }
 
 /**
@@ -1281,6 +1618,14 @@ declare class AgentConfig extends Component {
      * Find the AgentConfig component on a project.
      */
     static of(project: Project$1): AgentConfig | undefined;
+    /**
+     * Returns `true` when at least one tier array on the supplied
+     * `SourceTierExamples` is non-empty, signalling that the consuming
+     * repo has opted into rendering the base bundle's
+     * `source-quality-verification` rule. Returns `false` for
+     * `undefined`, `{}`, or a fully-empty `{ t1: [], t2: [], t3: [], t4: [] }`.
+     */
+    private static hasActiveTierExamples;
     /**
      * Merges default Claude permissions with bundle and user-supplied settings.
      *
@@ -1305,8 +1650,11 @@ declare class AgentConfig extends Component {
     /**
      * Return a bundle's rules with `filePatterns` narrowed to the projects
      * that actually matched the bundle's detection predicate (when the bundle
-     * provides `findApplicableProjects`). Rules with `ALWAYS` scope and rules
-     * on bundles that don't implement the hook are returned unchanged.
+     * provides `findApplicableProjects`) and any project-specified
+     * `features.customDocSections` entries injected into the matching rule
+     * content. Rules with `ALWAYS` scope and rules on bundles that don't
+     * implement the hook are returned with only the custom-section
+     * transformation (if any) applied.
      */
     private bundleRulesFor;
     private resolveSkills;
@@ -1524,6 +1872,51 @@ declare const prReviewBundle: AgentRuleBundle;
  */
 declare const projenBundle: AgentRuleBundle;
 
+/**
+ * Inject domain-specific source-tier examples into the content of the
+ * base bundle's "Source Quality & Verification" rule.
+ *
+ * For every tier whose examples array is non-empty, a
+ * `**Project-specific examples:**` line followed by a bullet list of
+ * the supplied strings is appended immediately beneath the tier's
+ * `### T<n> — ...` heading paragraph block. Tiers whose examples array
+ * is missing or empty are left untouched.
+ *
+ * Returns the original `content` verbatim when the supplied config is
+ * undefined or has no non-empty tier arrays, so callers can
+ * unconditionally pipe content through this function.
+ */
+declare function renderSourceTierExamples(content: string, examples: SourceTierExamples | undefined): string;
+/**
+ * Apply every {@link CustomDocSection} that targets `bundle.name` to
+ * the bundle's rules, returning a new bundle whose matched rules have
+ * the section bodies appended after the configured `afterSection`
+ * heading. Entries that reference a bundle name other than
+ * `bundle.name`, or whose `afterSection` cannot be located in any
+ * rule in the bundle, are silently dropped.
+ *
+ * Entries that target the same `afterSection` heading render in
+ * supplied order — the first supplied entry appears immediately
+ * beneath the target heading block, the second below that, and so on.
+ * This is achieved by advancing the insertion anchor to each
+ * just-injected section's `## <sectionTitle>` heading; the next
+ * same-target entry then lands at the end of that newly-opened
+ * section, which places it immediately after the previous entry
+ * regardless of the original heading's level.
+ *
+ * Returns `bundle` unchanged when `sections` is empty or no entries
+ * match, so callers can unconditionally pipe bundles through this
+ * function without penalty.
+ */
+declare function renderCustomDocSections(bundle: AgentRuleBundle, sections: ReadonlyArray<CustomDocSection>): AgentRuleBundle;
+/**
+ * Render a {@link CustomDocSection} into the markdown block that
+ * `renderCustomDocSections` splices after the target heading block.
+ * Exposed for tests that exercise the renderer directly without
+ * touching a full bundle.
+ */
+declare function renderCustomDocSectionBlock(section: CustomDocSection): string;
+
 /**
  * Render the markdown subsection appended to the
  * `issue-label-conventions` rule when `AgentConfigOptions.focus` is
@@ -1542,6 +1935,29 @@ declare const projenBundle: AgentRuleBundle;
  */
 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`
@@ -4276,4 +4692,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 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 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, 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 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 };