@codedrifters/configulator 0.0.266 → 0.0.268

package/lib/index.d.mts

@@ -1461,235 +1461,1716 @@ interface AgentFeaturesConfig {
 }
 /*******************************************************************************
  *
- * AgentConfig Options
+ * Agent Tier Config
  *
  ******************************************************************************/
 /**
- * Options for the AgentConfig component.
+ * A single consumer-supplied agent-type → funnel-tier mapping.
+ *
+ * The `type` field is the GitHub `type:*` label value **without** the
+ * `type:` prefix (e.g. supply `"company-profile"`, not
+ * `"type:company-profile"`). The `tier` field is a funnel tier in the
+ * range **0–4**:
+ *
+ * - **0 — routing.** Unblocks other work. Picked first on a priority tie.
+ * - **1 — research.** Feeds downstream pipelines.
+ * - **2 — profiles.** Consumes research.
+ * - **3 — synthesis.** Produces deliverables.
+ * - **4 — support.** Important but not pipeline-critical.
+ *
+ * The `orchestrator` bundle validates this value at synth time and
+ * fails the build when the tier is outside 0–4 or when `type` is
+ * empty/whitespace.
+ *
+ * @see AgentTierConfig
+ * @see ./bundles/tiers.ts#renderAgentTierSection
  */
-interface AgentConfigOptions {
+interface AgentTierEntry {
     /**
-     * Target platforms to generate configuration for.
-     * @default [AGENT_PLATFORM.CURSOR, AGENT_PLATFORM.CLAUDE]
+     * GitHub `type:*` label value (without the `type:` prefix).
+     * @example 'research', 'company-profile', 'requirement'
      */
-    readonly platforms?: ReadonlyArray<AgentPlatform>;
+    readonly type: string;
     /**
-     * Additional agent rules to generate alongside auto-detected and bundled rules.
-     * Custom rules override bundled rules of the same name.
+     * Funnel tier 0–4. Lower tiers dispatch first when priority is tied.
      */
-    readonly rules?: ReadonlyArray<AgentRule>;
+    readonly tier: 0 | 1 | 2 | 3 | 4;
+}
+/**
+ * Funnel-tier configuration consumed by the `orchestrator` bundle.
+ *
+ * The orchestrator sorts eligible issues by
+ * **priority desc → tier asc → issue number asc**. Lower tier numbers
+ * win ties on priority so research work feeds downstream pipelines
+ * before synthesis consumes attention.
+ *
+ * Every field is optional. When the whole config is absent the
+ * orchestrator renders its built-in default tier table (matching the
+ * openhi `DISPATCHER.md` source). Two override knobs are supported:
+ *
+ * - `tiers` — **replace** the default list wholesale. Rare; reserved
+ *   for repos that want a bespoke taxonomy end-to-end.
+ * - `customTypes` — **extend** whichever list is in play. Entries
+ *   with a `type` that already exists in the default (or replacement)
+ *   list win — consumer overrides take precedence.
+ *
+ * @see AgentTierEntry
+ * @see ./bundles/tiers.ts#resolveAgentTiers
+ */
+interface AgentTierConfig {
     /**
-     * Additional skills to generate.
+     * Replacement tier list. When supplied, the built-in default list
+     * is discarded and this list is used as the base before
+     * `customTypes` are merged in. Supply an empty array is an error —
+     * omit the field to keep the defaults.
      */
-    readonly skills?: ReadonlyArray<AgentSkill>;
+    readonly tiers?: ReadonlyArray<AgentTierEntry>;
     /**
-     * Custom sub-agent definitions.
+     * Additional tier mappings merged on top of whatever list is in
+     * play (default or replacement). Later entries override earlier
+     * entries on `type` collision, so consumer-supplied mappings win
+     * over the built-in defaults.
      */
-    readonly subAgents?: ReadonlyArray<AgentSubAgent>;
+    readonly customTypes?: ReadonlyArray<AgentTierEntry>;
+}
+/*******************************************************************************
+ *
+ * Scope Gate Config
+ *
+ ******************************************************************************/
+/**
+ * Threshold pair describing the inclusive upper bounds of the `small` /
+ * `medium` scope classes. Any issue above `medium` is classified `large`
+ * and rejected by the scope gate.
+ *
+ * Every issue is scored on two signals read from the issue body:
+ *
+ * - **Acceptance criteria** — the count of checkbox lines
+ *   (`- [ ]` / `- [x]`) under the issue's `## Acceptance Criteria`
+ *   section.
+ * - **Sources** — the count of bullet list items under the issue's
+ *   `## Inputs` / `## References` / `## Sources` sections (whichever
+ *   exists; they're summed if multiple exist).
+ *
+ * `small` requires **both** counts to be at or below `smallMax`.
+ * `medium` requires **both** counts to be at or below `mediumMax`.
+ * Anything above `mediumMax` on either axis is `large`.
+ *
+ * @see ScopeGateConfig
+ * @see ./bundles/scope-gate.ts#classifyIssueScope
+ */
+interface ScopeGateThresholds {
     /**
-     * Custom procedure definitions (executable shell scripts).
+     * Inclusive upper bound on the `acceptance-criteria` / `sources`
+     * count for the **small** scope class.
      */
-    readonly procedures?: ReadonlyArray<AgentProcedure>;
+    readonly smallMax: number;
     /**
-     * MCP server configurations. Cross-platform — rendered to the appropriate
-     * config file for each platform.
+     * Inclusive upper bound on the `acceptance-criteria` / `sources`
+     * count for the **medium** scope class. Must be strictly greater
+     * than `smallMax`.
      */
-    readonly mcpServers?: Readonly<Record<string, McpServerConfig>>;
+    readonly mediumMax: number;
+}
+/**
+ * Scope-gate configuration consumed by the `orchestrator` bundle.
+ *
+ * The scope gate rejects oversized issues at dispatch time and
+ * instructs the orchestrator to decompose them into phased sub-issues
+ * instead of claiming a worker session for a multi-hour task. The
+ * gate reads the **issue body only** — it does not inspect the
+ * repository. Heuristics are deliberately repo-agnostic so any
+ * consuming repo can adopt the contract without customizing code.
+ *
+ * Two threshold dials control the classification:
+ *
+ * - `acceptanceCriteria` — counts of checkbox lines under the issue's
+ *   `## Acceptance Criteria` section.
+ * - `sources` — counts of bullet list items under the issue's
+ *   `## Inputs` / `## References` / `## Sources` sections.
+ *
+ * An issue is classified **small** when both counts are at or below
+ * the `small` thresholds, **medium** when both are at or below the
+ * `medium` thresholds, and **large** otherwise. Large issues are
+ * rejected — the orchestrator applies `status:needs-attention`,
+ * posts a decomposition proposal comment, and (when `autoFile` is
+ * true) files the proposed phased sub-issues automatically.
+ *
+ * Consumers may override the per-axis thresholds, the decomposition
+ * comment template, and the auto-file toggle. When the whole config
+ * is absent the orchestrator applies openhi's published defaults
+ * (small: ≤3 AC + ≤2 sources; medium: ≤6 AC + ≤5 sources).
+ *
+ * Malformed configs — thresholds that are negative, non-integer, or
+ * inverted (medium ≤ small) — fail the build at synth time via
+ * `validateScopeGateConfig`.
+ *
+ * @see ScopeGateThresholds
+ * @see ./bundles/scope-gate.ts#resolveScopeGate
+ * @see ./bundles/scope-gate.ts#validateScopeGateConfig
+ * @see ./bundles/scope-gate.ts#renderScopeGateSection
+ */
+interface ScopeGateConfig {
     /**
-     * Whether to automatically detect and include context-aware rule bundles
-     * based on project introspection.
-     * @default true
+     * Master switch for the scope gate. When `false`, the orchestrator
+     * dispatches issues of every size and no decomposition proposal is
+     * posted. Defaults to `true` — scope gating is on by default.
      */
-    readonly autoDetectBundles?: boolean;
+    readonly enabled?: boolean;
     /**
-     * Explicit list of bundle names to include, regardless of auto-detection.
-     * @example ['vitest', 'aws-cdk']
+     * Classification thresholds for **acceptance-criteria counts**
+     * (checkbox lines under `## Acceptance Criteria`).
+     * Defaults to `{ smallMax: 3, mediumMax: 6 }` — openhi's published
+     * heuristic.
      */
-    readonly includeBundles?: ReadonlyArray<string>;
+    readonly acceptanceCriteria?: ScopeGateThresholds;
     /**
-     * Bundle names to exclude even if auto-detection would include them.
-     * @example ['jest']
+     * Classification thresholds for **source counts** (bullet list
+     * items under the issue's `## Inputs` / `## References` /
+     * `## Sources` sections). Defaults to `{ smallMax: 2, mediumMax: 5 }`.
      */
-    readonly excludeBundles?: ReadonlyArray<string>;
+    readonly sources?: ScopeGateThresholds;
     /**
-     * Whether to include the base rule set (project-overview, general conventions).
-     * @default true
+     * When `true`, the orchestrator files the proposed phased
+     * sub-issues automatically after posting the decomposition
+     * proposal comment. When `false` (the default), it posts the
+     * proposal and stops — a human is expected to file the sub-issues.
+     *
+     * Autofile is **opt-in** because sub-issue creation permanently
+     * modifies the project state; repos that adopt the feature should
+     * validate the decomposition template first and graduate to
+     * autofile once they trust the output.
+     * @default false
      */
-    readonly includeBaseRules?: boolean;
+    readonly autoFile?: boolean;
     /**
-     * Names of individual rules to exclude from any source.
+     * Override for the decomposition-proposal comment body posted on
+     * a rejected `large` issue. When unset, the bundle ships a generic
+     * template that the orchestrator fills in with the classified axis
+     * (`acceptance-criteria` / `sources`), the observed counts, and a
+     * boilerplate `Phase 1 / Phase 2 / Phase 3` skeleton for the agent
+     * to refine.
+     *
+     * The override string may embed the following placeholders — the
+     * orchestrator substitutes them at comment-composition time:
+     *
+     * - `<AC_COUNT>` — observed acceptance-criteria count.
+     * - `<SOURCES_COUNT>` — observed sources count.
+     * - `<AC_LIMIT>` — the `acceptanceCriteria.mediumMax` threshold
+     *   the issue tripped.
+     * - `<SOURCES_LIMIT>` — the `sources.mediumMax` threshold the
+     *   issue tripped.
+     *
+     * Placeholders use the angle-bracketed uppercase-snake form — not
+     * `{{curly-brace}}` form — because `AgentConfig`'s template
+     * resolver claims the curly-brace namespace at rule generation
+     * time and would rewrite `{{acCount}}` to `<acCount>` before the
+     * agent ever saw it.
+     *
+     * Placeholder substitution is performed by the orchestrator at
+     * runtime — configulator emits the template verbatim.
      */
-    readonly excludeRules?: ReadonlyArray<string>;
+    readonly decompositionTemplate?: string;
+}
+/*******************************************************************************
+ *
+ * Run Ratio Config
+ *
+ ******************************************************************************/
+/**
+ * Run-ratio configuration consumed by the `orchestrator` bundle.
+ *
+ * The orchestrator keeps a persistent run counter and interleaves
+ * **dispatch runs** (pick the next ready issue, recommend a worker)
+ * with **housekeeping runs** (batch PR review + maintenance scan) on
+ * a configurable dispatch-to-housekeeping ratio. This mirrors
+ * openhi's `DISPATCHER.md` 4:1 cadence — four dispatch runs feed the
+ * worker queue, then one batched housekeeping run flushes the
+ * review backlog and runs maintenance triage so the pipeline never
+ * drifts.
+ *
+ * The counter persists in a small gitignored JSON state file
+ * (default `.claude/state/orchestrator-runs.json`). Every orchestrator
+ * invocation ticks the counter once and classifies the run based on
+ * `runCounter % (ratio + 1) == 0` — the `ratio + 1`th run in every
+ * cycle is a housekeeping run, all others dispatch.
+ *
+ * Every field is optional. When the whole config is absent the
+ * orchestrator ships with openhi's 4:1 defaults baked in (4 dispatch
+ * runs, 1 housekeeping run, state file at the default path,
+ * `opus` / `sonnet` recommended models).
+ *
+ * Malformed configs — non-integer or non-positive `ratio`, empty or
+ * absolute `stateFilePath` — fail the build at synth time via
+ * `validateRunRatioConfig`.
+ *
+ * @see ./bundles/run-ratio.ts#resolveRunRatio
+ * @see ./bundles/run-ratio.ts#validateRunRatioConfig
+ * @see ./bundles/run-ratio.ts#renderRunRatioSection
+ */
+interface RunRatioConfig {
     /**
-     * Additional content to append to existing rules (from bundles or custom rules).
-     * Keys are rule names, values are markdown content appended after a horizontal rule.
-     * Use this to supplement bundle rules with project-specific additions without
-     * replacing the entire rule.
-     *
-     * @example
-     * ```ts
-     * ruleExtensions: {
-     *   'typescript-conventions': '## Additional Conventions\n\n- Use branded types for IDs',
-     * }
-     * ```
+     * Master switch for the run-ratio pipeline. When `false`, every
+     * orchestrator run executes the full dispatch pipeline and no
+     * housekeeping batching is performed; PR review and maintenance
+     * remain manual invocations. Defaults to `true` — ratio-based
+     * batching is on by default.
      */
-    readonly ruleExtensions?: Readonly<Record<string, string>>;
+    readonly enabled?: boolean;
     /**
-     * Claude Code settings.json configuration.
-     * Generated to .claude/settings.json (committed, team-shared).
+     * Number of dispatch runs per housekeeping run. With `ratio = 4`,
+     * runs 1–4 dispatch and run 5 housekeeps; the counter then wraps.
+     * The cycle length is therefore `ratio + 1` runs.
+     *
+     * Must be a positive integer (`ratio >= 1`). Defaults to `4` —
+     * the openhi-published cadence.
      */
-    readonly claudeSettings?: ClaudeSettingsConfig;
+    readonly ratio?: number;
     /**
-     * Cursor-specific configuration. Generates .cursor/hooks.json for
-     * lifecycle hooks and .cursorignore / .cursorindexingignore for
-     * file visibility control.
+     * Path to the run-counter state file, relative to the repo root.
+     * The orchestrator reads, increments, and writes back this file on
+     * every invocation. The file is tiny JSON (`{ "run_counter": <n> }`)
+     * and is expected to be gitignored — each operator's orchestrator
+     * session maintains its own counter.
+     *
+     * Must be a non-empty relative path (no leading `/`). Defaults to
+     * `.claude/state/orchestrator-runs.json`.
      */
-    readonly cursorSettings?: CursorSettingsConfig;
+    readonly stateFilePath?: string;
     /**
-     * Overrides for the output-path roots used by agent bundles
-     * (requirements, BCM, profiles, meetings, research). Unset fields
-     * fall back to the defaults captured in
-     * `bundles/paths.ts#DEFAULT_AGENT_PATHS`.
+     * Human-readable label for the model recommended on dispatch runs.
+     * Rendered verbatim into the orchestrator-conventions rule so the
+     * operator knows which model to run each dispatch session against.
+     * Configulator does **not** set `model:` frontmatter on the
+     * sub-agent — the label is informational.
      *
-     * This option is the first of the Group A framework injection
-     * points from epic #414. Per-project propagation of these values
-     * into bundle rule content lands in a follow-up — setting it today
-     * does not yet alter generated rules.
+     * Defaults to `"opus"`.
      */
-    readonly paths?: AgentPathsConfig;
+    readonly dispatchModel?: string;
     /**
-     * Project-specific priority-detection rules. Each rule declares a
-     * match predicate (labels, title regex, body regex, or explicit
-     * issue numbers) and a target `priority:*` tier.
+     * Human-readable label for the model recommended on housekeeping
+     * runs. See `dispatchModel` for the rendering contract.
+     * Housekeeping is mechanical (batch PR review + maintenance scan)
+     * so a cheaper model is the documented recommendation.
      *
-     * When non-empty, the `base` bundle renders a "Project-specific
-     * priority rules" subsection into the `issue-label-conventions`
-     * rule. Precedence is **first match wins**; the bundle's default
-     * inference heuristics act as the fallback when no rule matches.
+     * Defaults to `"sonnet"`.
+     */
+    readonly housekeepingModel?: string;
+}
+/*******************************************************************************
+ *
+ * Pre-flight PR merge Config
+ *
+ ******************************************************************************/
+/**
+ * Pre-flight PR merge configuration consumed by the `orchestrator`
+ * bundle.
+ *
+ * The pre-flight step (vortex `CLAUDE.md` step 0b) runs **before** the
+ * orchestrator's triage walk so eligible PRs land before the unblock
+ * and queue-scan phases read dependency state. Without it, an issue
+ * whose only remaining blocker is an approved-but-not-yet-merged PR
+ * shows up as blocked on every dispatch cycle — the pipeline thrashes
+ * on stale dependency state.
+ *
+ * The sweep is idempotent: `gh pr merge` on an already-merged PR is a
+ * no-op, so re-running pre-flight on every orchestrator invocation
+ * (dispatch **and** housekeeping) is safe and cheap. Eligibility is
+ * read by the `check-blocked.sh preflight` subcommand and returned as
+ * one line per candidate PR for the orchestrator to act on.
+ *
+ * Every field is optional. When the whole config is absent the
+ * orchestrator ships with vortex's published defaults baked in
+ * (pre-flight enabled, delegated to the `pr-reviewer` sub-agent so the
+ * merge workflow runs on a cheaper model, squash merges, linked-issue
+ * keyword required).
+ *
+ * Malformed configs — unknown `mergeMethod`, empty / whitespace-only
+ * `eligibleLabels` entries — fail the build at synth time via
+ * `validatePreflightPrConfig`.
+ *
+ * @see ./bundles/preflight-pr.ts#resolvePreflightPr
+ * @see ./bundles/preflight-pr.ts#validatePreflightPrConfig
+ * @see ./bundles/preflight-pr.ts#renderPreflightPrSection
+ */
+interface PreflightPrConfig {
+    /**
+     * Master switch for the pre-flight sweep. When `false`, the
+     * orchestrator skips pre-flight entirely; PR merges land via the
+     * existing batch PR review step on housekeeping runs or via a
+     * human operator.
      *
-     * @see PriorityRule
-     * @see ./bundles/priority-rules.ts#renderPriorityRulesSection
+     * Defaults to `true` — pre-flight is on by default. Repos that
+     * want to keep merges manual should set this to `false` explicitly.
      */
-    readonly priorityRules?: ReadonlyArray<PriorityRule>;
+    readonly enabled?: boolean;
     /**
-     * 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.
+     * Whether the orchestrator delegates the pre-flight sweep to the
+     * `pr-reviewer` sub-agent. Mirrors vortex's step 0b contract:
+     * invoking the reviewer as a sub-agent lets the merge workflow run
+     * on its own (cheaper) model rather than on the orchestrator's
+     * more expensive model budget.
      *
-     * 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.
+     * Set to `false` to have the orchestrator merge eligible PRs inline
+     * without delegation (useful in pipelines that have not wired a
+     * `pr-reviewer` sub-agent).
      *
-     * @see FocusConfig
-     * @see FocusArea
-     * @see AgentExpansionRules
-     * @see ./bundles/focus.ts#renderFocusSection
+     * Defaults to `true`.
      */
-    readonly focus?: FocusConfig;
+    readonly delegateToPrReviewer?: boolean;
     /**
-     * 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.
+     * Merge method used when the orchestrator merges a PR inline
+     * (`delegateToPrReviewer = false`). Maps to the `gh pr merge`
+     * flags: `squash` → `--squash`, `merge` → `--merge`, `rebase`
+     * → `--rebase`.
      *
-     * @see MeetingsConfig
-     * @see MeetingType
-     * @see MeetingArea
-     * @see ./bundles/meeting-types.ts#renderMeetingTypesSection
+     * Defaults to `"squash"` — squash-and-merge matches every existing
+     * configulator consumer and keeps `main` free of
+     * branch-construction noise.
      */
-    readonly meetings?: MeetingsConfig;
+    readonly mergeMethod?: "squash" | "merge" | "rebase";
     /**
-     * Framework injection points for source-tier customization and
-     * custom doc sections.
+     * Whether pre-flight skips PRs that lack a
+     * `Closes/Fixes/Resolves #<n>` keyword in the body. Most pipelines
+     * require a linked issue so the dependency graph stays intact, so
+     * the safe default is `true` — pre-flight only merges PRs that
+     * cleanly complete a known issue.
      *
-     * - `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.
+     * Set to `false` in repos that accept human-authored PRs with no
+     * linked issue (docs-only changes, dependency bumps, etc.) and
+     * still want pre-flight to land them.
      *
-     * 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.
+     * Defaults to `true`.
+     */
+    readonly requireLinkedIssue?: boolean;
+    /**
+     * Optional allowlist of labels that, when present on a PR, gate
+     * eligibility. When the list is empty (the default) every open PR
+     * that otherwise satisfies the eligibility checks qualifies;
+     * supplying a non-empty list restricts pre-flight to PRs carrying
+     * at least one of the listed labels.
      *
-     * @see AgentFeaturesConfig
-     * @see SourceTierExamples
-     * @see CustomDocSection
-     * @see ./bundles/features.ts
+     * Use this to opt specific pipelines in — for example,
+     * `['origin:issue-worker']` restricts pre-flight to bot-authored
+     * PRs, leaving human-authored PRs for the normal review path.
+     *
+     * Every entry must be a non-empty string; empty / whitespace-only
+     * entries fail the build via `validatePreflightPrConfig`.
      */
-    readonly features?: AgentFeaturesConfig;
+    readonly eligibleLabels?: ReadonlyArray<string>;
 }
-
+/*******************************************************************************
+ *
+ * Unblock Dependents Config
+ *
+ ******************************************************************************/
 /**
- * Generates AI coding assistant configuration files from a common schema.
+ * Agent-driven unblocking configuration consumed by the `orchestrator`
+ * bundle.
  *
- * Supports Cursor and Claude Code (initial release), with Codex and Copilot
- * renderers planned for future issues. Rules, skills, and sub-agents are
- * defined once and rendered into the correct format for each target platform.
+ * After any agent applies `status:done` to an issue, it runs a
+ * targeted sweep against that issue's dependents — open issues whose
+ * body contains `Depends on: #<just-closed>`. Dependents whose full
+ * dependency list is now closed flip from `status:blocked` to
+ * `status:ready` immediately, without waiting for the next
+ * orchestrator dispatch cycle. The sweep is implemented by the
+ * shipped `.claude/procedures/unblock-dependents.sh` script.
  *
- * Follows the configulator component pattern: extends Component, static .of()
- * factory, options interface with JSDoc.
+ * Every field is optional. When the whole config is absent the
+ * orchestrator ships with the sweep **enabled** and a generic
+ * "Dependencies resolved by #<n> — unblocking." citation comment.
  *
- * @example
- * ```ts
- * new AgentConfig(project, {
- *   rules: [{
- *     name: 'my-rule',
- *     description: 'Project conventions',
- *     scope: AGENT_RULE_SCOPE.ALWAYS,
- *     content: '# My Rule\n\nFollow these conventions...',
- *   }],
- * });
- * ```
+ * Malformed configs — empty / whitespace-only `commentTemplate` or
+ * `partialUnblockCommentTemplate` — fail the build at synth time via
+ * `validateUnblockDependentsConfig`.
+ *
+ * @see ./bundles/unblock-dependents.ts#resolveUnblockDependents
+ * @see ./bundles/unblock-dependents.ts#validateUnblockDependentsConfig
+ * @see ./bundles/unblock-dependents.ts#renderUnblockDependentsSection
  */
-declare class AgentConfig extends Component {
+interface UnblockDependentsConfig {
     /**
-     * Find the AgentConfig component on a project.
+     * Master switch for the agent-driven unblock sweep. When `false`,
+     * agents skip the targeted sweep after applying `status:done`;
+     * dependents wait for the next orchestrator dispatch (Phase C) to
+     * pick up the resolved dependency.
+     *
+     * Defaults to `true` — the sweep is on by default. Repos that
+     * want to keep label transitions manual should set this to `false`
+     * explicitly.
      */
-    static of(project: Project$1): AgentConfig | undefined;
+    readonly enabled?: boolean;
     /**
-     * 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: [] }`.
+     * Override for the citation comment posted on each fully-unblocked
+     * dependent. The string is interpolated at runtime by the shipped
+     * shell script: `<CLOSED_ISSUE>` is replaced with the resolving
+     * issue's `#<n>` reference.
+     *
+     * The placeholder syntax deliberately avoids `{{curly-brace}}` —
+     * `AgentConfig`'s template resolver claims that namespace at rule
+     * generation time.
+     *
+     * Defaults to `"Dependencies resolved by <CLOSED_ISSUE> — unblocking."`.
      */
-    private static hasActiveTierExamples;
+    readonly commentTemplate?: string;
     /**
-     * Merges default Claude permissions with bundle and user-supplied settings.
+     * Whether to post a partial-unblock comment on a dependent whose
+     * full dependency list is **not** yet fully closed. When `true`,
+     * each intermediate dependency resolution leaves a trail of
+     * "still waiting on X" comments on the dependent — useful for
+     * operator visibility on long dependency chains. When `false`,
+     * partial resolutions are logged to the script's stdout only and
+     * the dependent issue stays silent until the final dep closes.
      *
-     * Merge order: defaults → bundle permissions → user-supplied entries.
-     * `defaultMode` defaults to `"dontAsk"` unless overridden.
+     * Defaults to `false` — keeps issue threads clean by default.
      */
-    private static mergeClaudeDefaults;
-    private readonly options;
-    constructor(project: Project$1, options?: AgentConfigOptions);
+    readonly flagPartialUnblockWithAttention?: boolean;
     /**
-     * Returns the bundles that are active for this project: auto-detected
-     * bundles (when `autoDetectBundles !== false`) plus force-included
-     * bundles, minus explicitly excluded bundles. Deduplicated by name.
+     * Override for the partial-unblock comment posted when
+     * `flagPartialUnblockWithAttention` is `true`. The string is
+     * interpolated at runtime: `<CLOSED_ISSUE>` is replaced with the
+     * just-resolved issue's `#<n>` reference, and `<OPEN_DEPS>` with
+     * the space-separated list of remaining open dependencies
+     * (e.g. `#45 #47`).
      *
-     * Exposed so sibling components (e.g. the sync-labels workflow) can
-     * consume bundle-contributed configuration.
+     * Defaults to `"Dependency <CLOSED_ISSUE> resolved, but still waiting on: <OPEN_DEPS>."`.
      */
-    get activeBundles(): ReadonlyArray<AgentRuleBundle>;
-    preSynthesize(): void;
-    private resolvePlatforms;
-    private resolveRules;
+    readonly partialUnblockCommentTemplate?: string;
+}
+/*******************************************************************************
+ *
+ * Progress Files Config
+ *
+ ******************************************************************************/
+/**
+ * Progress-file convention consumed by the `base` bundle and every
+ * phased-agent bundle (bcm-writer, research-pipeline, etc.).
+ *
+ * Every phased agent session writes a small progress file to disk as
+ * its first action after claiming an issue, updates it after each
+ * non-trivial step, and deletes it in the final commit that closes
+ * the issue. If the session crashes, the next session reads the
+ * progress file, confirms on-disk state matches reality, and resumes
+ * from the next uncompleted step rather than starting from scratch.
+ *
+ * The convention complements the stale-branch decision tree — clone
+ * recovery returns the checkout to the default branch; the progress
+ * file restores the *deliverable* to a partially-complete state so
+ * resumed work can build on it.
+ *
+ * Every field is optional. When the whole config is absent the
+ * convention ships **enabled** with JSON-formatted files stored under
+ * `.claude/state/<issue-number>-progress.json`.
+ *
+ * Malformed configs — empty / whitespace-only or absolute `stateDir`,
+ * empty / whitespace-only `filenamePattern`, `filenamePattern` missing
+ * the `<ISSUE_NUMBER>` placeholder, unknown `format`, non-positive
+ * `staleAfterHours` — fail the build at synth time via
+ * `validateProgressFilesConfig`.
+ *
+ * @see ./bundles/progress-files.ts#resolveProgressFiles
+ * @see ./bundles/progress-files.ts#validateProgressFilesConfig
+ * @see ./bundles/progress-files.ts#renderProgressFilesRuleContent
+ */
+interface ProgressFilesConfig {
+    /**
+     * Master switch for the progress-file convention. When `false`,
+     * the base bundle renders a short stub stating the project does not
+     * enforce progress files; phased-agent bundles skip the
+     * per-workflow "Progress File" injection. Partial-resume guidance
+     * still renders because it applies even without a progress file.
+     *
+     * Defaults to `true` — the convention is on by default.
+     */
+    readonly enabled?: boolean;
+    /**
+     * Root directory (relative to the repo root) where progress files
+     * are written. Must be a non-empty relative path (no leading `/`).
+     * The directory is added to the project's `.gitignore` at synth
+     * time so progress files never land on the default branch.
+     *
+     * Defaults to `.claude/state`.
+     */
+    readonly stateDir?: string;
+    /**
+     * Filename pattern for an individual progress file. The
+     * `<ISSUE_NUMBER>` placeholder is substituted at runtime with the
+     * numeric id of the issue the agent is working on (e.g.
+     * `479-progress.json`).
+     *
+     * Must contain the `<ISSUE_NUMBER>` placeholder and must not
+     * contain a `/` (use `stateDir` for the directory).
+     *
+     * The placeholder uses the angle-bracketed uppercase-snake form —
+     * not `{{curly-brace}}` form — because `AgentConfig`'s template
+     * resolver claims the curly-brace namespace at rule generation
+     * time.
+     *
+     * Defaults to `"<ISSUE_NUMBER>-progress.json"`.
+     */
+    readonly filenamePattern?: string;
+    /**
+     * Serialization format for the progress-file body.
+     *
+     * - `"json"` (default) — machine-parseable JSON with a typed
+     *   schema. Preferred when scripted resume logic reads the file.
+     * - `"markdown"` — human-readable markdown with a YAML frontmatter
+     *   block. Preferred for projects that treat the progress file as
+     *   an operator-visible log.
+     */
+    readonly format?: "json" | "markdown";
+    /**
+     * Whether the final commit that closes the issue must delete the
+     * progress file. When `true` (the default), progress files are a
+     * working-branch artefact and never land on the default branch.
+     * When `false`, progress files are retained as an audit trail.
+     *
+     * Defaults to `true`.
+     */
+    readonly cleanupOnComplete?: boolean;
+    /**
+     * Stale-threshold in hours for the stale-branch decision tree. A
+     * branch whose progress file's `last_updated` is older than this
+     * many hours **and** that has no matching open PR is considered
+     * abandoned. Rendered verbatim into the stale-branch documentation
+     * so operators have a single authoritative number.
+     *
+     * Must be a positive integer. Defaults to `72` — matches the
+     * orchestrator bundle's in-progress staleness threshold.
+     */
+    readonly staleAfterHours?: number;
+}
+/*******************************************************************************
+ *
+ * Shared Editing Config
+ *
+ ******************************************************************************/
+/**
+ * Shared-editing safety convention consumed by the `base` bundle and
+ * every phased-agent bundle that writes rows to a shared registry or
+ * feature-matrix file.
+ *
+ * Multiple concurrent agent sessions frequently need to edit the same
+ * index file — registry `README.md` / `index.md` row tables, category
+ * landing pages, feature matrices. Without a shared contract, parallel
+ * sessions conflict on the index even when their content contributions
+ * are independent, and the resolver may accidentally drop a row.
+ *
+ * The convention covers: pre-edit read-latest, single-entry
+ * deterministic-sort inserts, commit-path verification (read-back the
+ * committed file, assert the new row is present exactly once), and a
+ * scripted merge-conflict resolution recipe.
+ *
+ * Every field is optional. When the whole config is absent the
+ * convention ships **enabled** with the documented default set of
+ * shared index path patterns and the rebase-based conflict strategy.
+ *
+ * Malformed configs — empty `sharedIndexPaths`, empty /
+ * whitespace-only path entry, unknown `conflictStrategy` — fail the
+ * build at synth time via `validateSharedEditingConfig`.
+ *
+ * @see ./bundles/shared-editing.ts#resolveSharedEditing
+ * @see ./bundles/shared-editing.ts#validateSharedEditingConfig
+ * @see ./bundles/shared-editing.ts#renderSharedEditingRuleContent
+ */
+interface SharedEditingConfig {
+    /**
+     * Master switch for the shared-editing convention. When `false`,
+     * the base bundle renders a short stub stating the project does not
+     * enforce the convention; phased-agent bundles skip the
+     * per-workflow "Shared Index Editing" injection.
+     *
+     * Defaults to `true` — the convention is on by default.
+     */
+    readonly enabled?: boolean;
+    /**
+     * Path patterns (plain glob strings) that identify shared index
+     * files. Rendered verbatim into the rule body as a bullet list;
+     * agents match the file they are about to edit against the patterns
+     * to decide whether the contract applies.
+     *
+     * Must be a non-empty array of non-empty strings.
+     *
+     * Defaults to the configulator-wide set covering docs-site
+     * `index.md` / `README.md` registry tables and feature-matrix
+     * files.
+     */
+    readonly sharedIndexPaths?: ReadonlyArray<string>;
+    /**
+     * Whether the rendered convention includes the commit-path
+     * verification protocol (read-back the committed file, assert the
+     * new row is present exactly once). The verification step catches
+     * staging / path bugs that would otherwise silently drop a row.
+     *
+     * Defaults to `true` — verification is on by default.
+     */
+    readonly verifyCommit?: boolean;
+    /**
+     * Strategy the convention's merge-conflict recipe prescribes when
+     * two agents both add a row to the same shared index:
+     *
+     * - `"rebase"` (default) — `git pull --rebase` the branch, re-insert
+     *   the new row in sort order, resolve, `git rebase --continue`.
+     * - `"merge"` — `git pull` (fast-forward or merge commit), re-insert
+     *   the row, `git commit`. Use for projects that keep a merge-commit
+     *   history on feature branches.
+     */
+    readonly conflictStrategy?: "rebase" | "merge";
+    /**
+     * Whether the convention emits the
+     * `.claude/procedures/verify-index-row.sh` helper to disk. The
+     * helper implements the commit-path verification step in a single
+     * shell invocation; consumers that prefer the inline
+     * `git show HEAD:<path>` recipe can leave it disabled.
+     *
+     * Defaults to `false` — the helper is opt-in.
+     */
+    readonly emitHelper?: boolean;
+}
+/*******************************************************************************
+ *
+ * Skill Evals Config
+ *
+ ******************************************************************************/
+/**
+ * Skill eval harness convention consumed by the `base` bundle and
+ * every skill-owning bundle (requirements-writer, bcm-writer, etc.).
+ *
+ * Each skill under `<skillsRoot>/<skill-name>/` may ship a regression
+ * suite at `<skillsRoot>/<skill-name>/evals/evals.json`. Suites are
+ * declarative prompt / expected-output fixtures parameterised by a
+ * shared **product-context** fixture (by default
+ * `docs/src/content/docs/project-context.md`) so the same eval shape
+ * works across every project that depends on configulator — each
+ * consuming repo supplies its own `project-context.md`, not its own
+ * forked eval files.
+ *
+ * The convention is declarative: the optional runner script shipped
+ * by `emitRunner: true` walks the skills root, validates every
+ * `evals.json` against the schema, resolves the product-context
+ * fixture, and emits a JSON execution plan to stdout. It never
+ * invokes an LLM itself — the plan is consumed by whatever human or
+ * model actually replays the prompts against the skill.
+ *
+ * Every field is optional. When the whole config is absent the
+ * convention ships **enabled** with the documented default paths,
+ * product-context required, and the runner script opt-in.
+ *
+ * Malformed configs — empty / whitespace-only or absolute
+ * `skillsRoot`, empty / whitespace-only or absolute
+ * `productContextPath` — fail the build at synth time via
+ * `validateSkillEvalsConfig`.
+ *
+ * @see ./bundles/skill-evals.ts#resolveSkillEvals
+ * @see ./bundles/skill-evals.ts#validateSkillEvalsConfig
+ * @see ./bundles/skill-evals.ts#renderSkillEvalsRuleContent
+ */
+interface SkillEvalsConfig {
+    /**
+     * Master switch for the skill-eval harness convention. When `false`,
+     * the base bundle renders a short stub stating the project does not
+     * ship skill evals; skill-owning bundles skip their per-bundle
+     * "Skill Evals" injection and the optional runner script is not
+     * emitted even if `emitRunner: true`.
+     *
+     * Defaults to `true` — the convention is on by default.
+     */
+    readonly enabled?: boolean;
+    /**
+     * Root directory (relative to the repo root) under which skill
+     * SKILL.md files live. The runner walks this directory to discover
+     * eval suites at `<skillsRoot>/<skill-name>/evals/evals.json`.
+     *
+     * Must be a non-empty relative path (no leading `/`).
+     *
+     * Defaults to `.claude/skills`, which matches the path every
+     * configulator-managed project ships skills to on disk.
+     */
+    readonly skillsRoot?: string;
+    /**
+     * Path (relative to the repo root) to the product-context fixture
+     * every eval suite references by default. A per-suite
+     * `product_context` field in an `evals.json` overrides this value
+     * for that suite only.
+     *
+     * Must be a non-empty relative path (no leading `/`).
+     *
+     * Defaults to `docs/src/content/docs/project-context.md`, which is
+     * the file every configulator-managed agent already loads at
+     * session start.
+     */
+    readonly productContextPath?: string;
+    /**
+     * Whether the runner fails fast when the product-context fixture is
+     * missing. The default (`true`) is deliberately strict — an eval
+     * that silently runs without its fixture produces a false-positive
+     * pass. Projects bootstrapping a new consuming repo that has not
+     * yet authored its `project-context.md` can set this to `false`,
+     * at which point a missing fixture becomes a stderr warning rather
+     * than a hard failure.
+     *
+     * Defaults to `true`.
+     */
+    readonly requireProductContext?: boolean;
+    /**
+     * Whether the convention emits the
+     * `.claude/procedures/run-skill-evals.sh` helper to disk. The
+     * helper implements the full runner contract (discover, validate,
+     * resolve product-context, emit JSON plan) in a single shell
+     * invocation. Consumers that prefer to roll their own runner can
+     * leave it disabled and follow the inline recipe documented in the
+     * rule body.
+     *
+     * Defaults to `false` — the helper is opt-in.
+     */
+    readonly emitRunner?: boolean;
+}
+/*******************************************************************************
+ *
+ * Workflow Diagrams Config
+ *
+ ******************************************************************************/
+/**
+ * Workflow-diagrams convention consumed by the `base` bundle and
+ * every phased-agent bundle. Documents the single hand-authored
+ * Mermaid-based diagrams page that visualises every agent's phase
+ * graph and every cross-agent handoff, and enforces the
+ * **diagram-touched-when-bundle-touched** rule: a change set that
+ * modifies a bundle's phase graph must also update the matching
+ * section in the diagrams page.
+ *
+ * The convention is deliberately content-free — configulator cannot
+ * ship meaningful diagrams because each consuming repo enables a
+ * different subset of bundles and customises agent labels, paths,
+ * and taxonomies via the Group A injection points. Instead the
+ * bundle renders the rule (what to author, when to update it) and
+ * optionally emits a starter page + a checker script.
+ *
+ * Every field is optional. When the whole config is absent the
+ * convention ships **enabled** with the documented default diagrams
+ * path (`docs/src/content/docs/agents/workflows.md`), the default
+ * bundle-path patterns, the hard-requirement phrasing, the starter
+ * page opt-in, and the checker script opt-in.
+ *
+ * Malformed configs — empty / whitespace-only or absolute
+ * `diagramsPath`, empty `bundlePathPatterns`, empty /
+ * whitespace-only pattern entry — fail the build at synth time via
+ * `validateWorkflowDiagramsConfig`.
+ *
+ * @see ./bundles/workflow-diagrams.ts#resolveWorkflowDiagrams
+ * @see ./bundles/workflow-diagrams.ts#validateWorkflowDiagramsConfig
+ * @see ./bundles/workflow-diagrams.ts#renderWorkflowDiagramsRuleContent
+ */
+interface WorkflowDiagramsConfig {
+    /**
+     * Master switch for the workflow-diagrams convention. When `false`,
+     * the base bundle renders a short stub stating the project does not
+     * enforce the convention; phased-agent bundles skip the
+     * per-workflow "Workflow Diagram" injection and the optional helper
+     * script / starter page are not emitted even if their `emit*`
+     * flags are true.
+     *
+     * Defaults to `true` — the convention is on by default.
+     */
+    readonly enabled?: boolean;
+    /**
+     * Repo-relative path to the single workflow-diagrams page. The
+     * rendered rule cites this path as the on-disk home of every
+     * Mermaid diagram; the checker script uses it as the sentinel path
+     * that must appear in a change set when any bundle file is
+     * touched.
+     *
+     * Must be a non-empty relative path (no leading `/`).
+     *
+     * Defaults to `docs/src/content/docs/agents/workflows.md`, which
+     * matches the monorepo-wide singleton `/docs` Starlight site every
+     * configulator-managed repo ships.
+     */
+    readonly diagramsPath?: string;
+    /**
+     * Path patterns (bash-style globs) that identify "bundle files" —
+     * the source files whose edits require the workflow-diagrams page
+     * to be touched in the same change set. Rendered verbatim into
+     * the rule body as a bullet list and emitted into the checker
+     * script when `emitChecker: true`.
+     *
+     * Must be a non-empty array of non-empty strings.
+     *
+     * Defaults to the configulator-wide set covering in-tree bundle
+     * source files, `.claude/agents/**.md` agent prompts, and
+     * `.claude/skills/**.md` skill prompts.
+     */
+    readonly bundlePathPatterns?: ReadonlyArray<string>;
+    /**
+     * Whether the convention emits a minimal starter diagrams page to
+     * disk at `<diagramsPath>`. The starter carries the expected
+     * structure (master diagram placeholder, one example agent section,
+     * legend) so consumers adopting the convention on a green-field
+     * repo have a working template to extend.
+     *
+     * Disabled by default because the page is hand-authored — an
+     * emitted stub would conflict with existing content on repos
+     * adopting the convention late.
+     */
+    readonly emitStarterDiagram?: boolean;
+    /**
+     * Whether the convention emits the
+     * `.claude/procedures/check-workflow-diagrams.sh` helper to disk.
+     * The script walks a newline-separated list of changed files (from
+     * stdin or positional arguments) and fails non-zero when any file
+     * matches a bundle-path pattern but `<diagramsPath>` is not also
+     * in the list.
+     *
+     * Disabled by default — the helper is opt-in for repos that want a
+     * hard CI gate or pre-commit hook. Consumers that prefer to
+     * enforce the rule via review discipline alone can leave it off.
+     */
+    readonly emitChecker?: boolean;
+    /**
+     * Whether the rendered rule body phrases the diagram update as a
+     * **hard requirement** (`MUST`) or a **strong recommendation**
+     * (`SHOULD`). Defaults to `true` — the hard-requirement phrasing
+     * matches the "enforced via CI" posture the convention is
+     * designed for. Consumers that treat diagrams as aspirational can
+     * soften the phrasing by setting this to `false`.
+     */
+    readonly requireDiagramUpdate?: boolean;
+}
+/*******************************************************************************
+ *
+ * Issue Templates Config
+ *
+ ******************************************************************************/
+/**
+ * Issue-templates convention consumed by the `base` bundle and every
+ * phased-agent bundle that files downstream issues. Documents the
+ * single hand-authored reference page that carries one canonical
+ * `gh issue create` recipe per downstream phase label, and enforces
+ * the **reference-don't-inline** rule: bundle rules and agent prompts
+ * cite the matching section of that page instead of duplicating a
+ * full `gh issue create --title ... --label ... --body ...`
+ * invocation.
+ *
+ * The convention is deliberately content-free — configulator cannot
+ * ship meaningful templates because each consuming repo enables a
+ * different subset of bundles and customises phase labels, tier
+ * taxonomies, and body conventions via the Group A injection points.
+ * Instead the bundle renders the rule (what to author, when to cite
+ * it) and optionally emits a starter page + a lint script.
+ *
+ * Every field is optional. When the whole config is absent the
+ * convention ships **enabled** with the documented default templates
+ * path (`docs/src/content/docs/agents/issue-templates.md`), the
+ * default bundle-path patterns, the hard-requirement phrasing, and
+ * both the starter page and the lint script opt-in.
+ *
+ * Malformed configs — empty / whitespace-only or absolute
+ * `templatesPath`, empty `bundlePathPatterns`, empty /
+ * whitespace-only pattern entry — fail the build at synth time via
+ * `validateIssueTemplatesConfig`.
+ *
+ * @see ./bundles/issue-templates.ts#resolveIssueTemplates
+ * @see ./bundles/issue-templates.ts#validateIssueTemplatesConfig
+ * @see ./bundles/issue-templates.ts#renderIssueTemplatesRuleContent
+ */
+interface IssueTemplatesConfig {
+    /**
+     * Master switch for the issue-templates convention. When `false`,
+     * the base bundle renders a short stub stating the project does not
+     * enforce the convention; phased-agent bundles skip the per-workflow
+     * "Issue Templates" injection and the optional helper script /
+     * starter page are not emitted even if their `emit*` flags are
+     * true.
+     *
+     * Defaults to `true` — the convention is on by default.
+     */
+    readonly enabled?: boolean;
+    /**
+     * Repo-relative path to the single issue-templates reference page.
+     * The rendered rule cites this path as the on-disk home of every
+     * `gh issue create` recipe; the lint script uses it as the
+     * allow-listed sentinel path that is permitted to contain full
+     * recipes.
+     *
+     * Must be a non-empty relative path (no leading `/`).
+     *
+     * Defaults to `docs/src/content/docs/agents/issue-templates.md`,
+     * which matches the monorepo-wide singleton `/docs` Starlight site
+     * every configulator-managed repo ships.
+     */
+    readonly templatesPath?: string;
+    /**
+     * Path patterns (bash-style globs) that identify "bundle files" —
+     * the source files composing agent prompts and skill instructions.
+     * Rendered verbatim into the rule body as a bullet list and emitted
+     * into the lint script when `emitChecker: true`.
+     *
+     * Must be a non-empty array of non-empty strings.
+     *
+     * Defaults to the configulator-wide set covering in-tree bundle
+     * source files, `.claude/agents/**.md` agent prompts, and
+     * `.claude/skills/**.md` skill prompts.
+     */
+    readonly bundlePathPatterns?: ReadonlyArray<string>;
+    /**
+     * Whether the convention emits the
+     * `.claude/procedures/check-issue-templates.sh` lint to disk. The
+     * script walks a newline-separated list of changed files (from
+     * stdin or positional arguments) and fails non-zero when any file
+     * matches a bundle-path pattern and contains a multi-line
+     * `gh issue create ... --title` invocation.
+     *
+     * Disabled by default — the lint is opt-in for repos that want a
+     * hard CI gate or pre-commit hook. Consumers that prefer to
+     * enforce the rule via review discipline alone can leave it off.
+     */
+    readonly emitChecker?: boolean;
+    /**
+     * Whether the convention emits a minimal starter templates page to
+     * disk at `<templatesPath>`. The starter carries the expected
+     * structure (how-to-use preamble + one example
+     * `## Template: <phase-label>` section) so consumers adopting the
+     * convention on a green-field repo have a working template to
+     * extend.
+     *
+     * Disabled by default because the page is hand-authored — an
+     * emitted stub would conflict with existing content on repos
+     * adopting the convention late.
+     */
+    readonly emitStarterDoc?: boolean;
+    /**
+     * Whether the rendered rule body phrases the reference-don't-inline
+     * rule as a **hard requirement** (`MUST`) or a **strong
+     * recommendation** (`SHOULD`). Defaults to `true` — the
+     * hard-requirement phrasing matches the consolidation goal the
+     * convention is designed for. Consumers that treat consolidation
+     * as aspirational can soften the phrasing by setting this to
+     * `false`.
+     */
+    readonly requireReference?: boolean;
+}
+/*******************************************************************************
+ *
+ * Scheduled Tasks Config
+ *
+ ******************************************************************************/
+/**
+ * Partial override for a single default scheduled-task entry keyed by
+ * `taskId`. Every field is optional — only supplied fields replace the
+ * default. Use `enabled: true` to opt a task in without otherwise
+ * changing its shape.
+ *
+ * @see ScheduledTasksConfig
+ * @see ./bundles/scheduled-tasks.ts#DEFAULT_SCHEDULED_TASK_ENTRIES
+ */
+interface ScheduledTaskOverride {
+    /** Whether the task is emitted to disk. Defaults to the registry entry's value (normally `false`). */
+    readonly enabled?: boolean;
+    /**
+     * Cron expression. Set to `null` to mean manual-only. Default is
+     * manual-only; every configulator default entry ships without a cron.
+     */
+    readonly cron?: string | null;
+    /** Recommended model label surfaced on frontmatter and the rendered table. */
+    readonly recommendedModel?: "opus" | "sonnet" | "haiku";
+    /** One-line description for the rendered table and SKILL.md frontmatter. */
+    readonly description?: string;
+    /**
+     * Exact `type:*` label values (without the `type:` prefix) the
+     * worker should pick up. When set, replaces the default entry's
+     * single `typeLabel` with a multi-type filter (useful for the
+     * routing-bucket `worker-issue` which covers
+     * `feat/fix/chore/refactor/docs/release/hotfix`). Empty array not
+     * allowed; use `undefined` to keep the default.
+     */
+    readonly typeLabels?: ReadonlyArray<string>;
+    /**
+     * Exact phase-label values the worker filters on. When set, takes
+     * precedence over `phasePrefix` (prefix-match is dropped). Empty
+     * array not allowed; use `undefined` to keep the default.
+     */
+    readonly phaseLabels?: ReadonlyArray<string>;
+}
+/**
+ * Fully consumer-authored scheduled-task entry. Entries whose `taskId`
+ * collides with a built-in default **replace** the default outright;
+ * entries with a new `taskId` are appended to the registry.
+ *
+ * @see ScheduledTasksConfig
+ */
+interface ScheduledTaskEntry {
+    /**
+     * Unique task directory name. Emitted under
+     * `<root>/<taskId>/SKILL.md`. Every `taskId` must be unique within
+     * the resolved registry.
+     */
+    readonly taskId: string;
+    /** Target sub-agent name (filename stem under `.claude/agents/`). */
+    readonly agent: string;
+    /** Human-readable agent label for rendered tables / frontmatter. Defaults to `agent`. */
+    readonly agentLabel?: string;
+    /** GitHub `type:*` label value (without the `type:` prefix) that gates which issues this worker picks up. Ignored when `typeLabels` is set. */
+    readonly typeLabel: string;
+    /**
+     * Exact `type:*` label values (without the `type:` prefix) the
+     * worker picks up. When set, replaces the single `typeLabel` with
+     * a multi-type filter (e.g. the routing-bucket `worker-issue`
+     * covers `feat/fix/chore/refactor/docs/release/hotfix`). Empty
+     * array not allowed.
+     */
+    readonly typeLabels?: ReadonlyArray<string>;
+    /** Optional phase-label prefix (e.g. `research:`). When set, the worker filters on both `type:<typeLabel>` and any `<phasePrefix>*` label. Ignored when `phaseLabels` is set. */
+    readonly phasePrefix?: string;
+    /**
+     * Exact phase-label values the worker filters on (e.g.
+     * `["req:write"]` for a writer that only picks up issues whose
+     * phase label is exactly `req:write`). When set, takes precedence
+     * over `phasePrefix`. Empty array not allowed.
+     */
+    readonly phaseLabels?: ReadonlyArray<string>;
+    /** Recommended model label surfaced on frontmatter and the rendered table. */
+    readonly recommendedModel: "opus" | "sonnet" | "haiku";
+    /** Whether the task is emitted to disk. Defaults to `false` — opt-in. */
+    readonly enabled?: boolean;
+    /** Cron expression. Defaults to `null` (manual-only). */
+    readonly cron?: string | null;
+    /** One-line description for the rendered table and SKILL.md frontmatter. */
+    readonly description?: string;
+}
+/**
+ * Per-agent scheduled-task configuration consumed by the `orchestrator`
+ * bundle. Drives the per-agent worker layout at
+ * `<root>/<taskId>/SKILL.md` — one task per agent type with its own
+ * label filter, recommended model, and opt-in enablement.
+ *
+ * The pattern mirrors vortex-management's `.claude/scheduled-tasks/`
+ * layout: splitting workers by type lets expensive research agents run
+ * on a different cadence than cheap synthesis agents, and disabling a
+ * whole category is a one-line toggle instead of label surgery.
+ *
+ * Every task ships **disabled by default**. Consumers opt in
+ * explicitly; the generated repo contains no scheduled-task files
+ * unless at least one task is enabled.
+ *
+ * Every field is optional. When the whole config is absent the
+ * scheduled-tasks subsystem is enabled but no task is emitted (every
+ * default is disabled).
+ *
+ * Malformed configs — unknown model value, empty `taskId` / `agent` /
+ * `typeLabel`, duplicate `taskId` inside `tasks`, override referencing
+ * an unknown default `taskId` — fail the build at synth time via
+ * `validateScheduledTasksConfig`.
+ *
+ * @see ScheduledTaskEntry
+ * @see ScheduledTaskOverride
+ * @see ./bundles/scheduled-tasks.ts#resolveScheduledTasks
+ * @see ./bundles/scheduled-tasks.ts#validateScheduledTasksConfig
+ * @see ./bundles/scheduled-tasks.ts#renderScheduledTasksSection
+ */
+interface ScheduledTasksConfig {
+    /**
+     * Master switch for the scheduled-tasks subsystem. When `false`, no
+     * `<root>/<taskId>/SKILL.md` files are emitted regardless of
+     * individual task overrides. Defaults to `true` — the subsystem is
+     * on, but every default task is still disabled.
+     */
+    readonly enabled?: boolean;
+    /**
+     * Root directory (relative to the repo root) for emitted
+     * scheduled-task files. Each task renders to
+     * `<root>/<taskId>/SKILL.md`.
+     *
+     * Must be a non-empty relative path (no leading `/`). Defaults to
+     * `.claude/scheduled-tasks`.
+     */
+    readonly root?: string;
+    /**
+     * Per-task overrides keyed by the built-in `taskId`. Use this to
+     * flip the `enabled` toggle on one or more default tasks, override
+     * the cron expression, or change the recommended model without
+     * re-declaring the rest of the entry.
+     *
+     * Every key must match a built-in default `taskId`; unknown keys
+     * fail the build. Use `tasks` to append new entries.
+     */
+    readonly overrides?: Readonly<Record<string, ScheduledTaskOverride>>;
+    /**
+     * Fully consumer-authored task entries. Entries whose `taskId`
+     * matches a built-in default **replace** the default wholesale;
+     * entries with a new `taskId` are appended.
+     *
+     * Every `taskId` must be unique within this list (duplicate
+     * `taskId`s inside `tasks` fail the build). Use `overrides` to
+     * tweak a single field without re-declaring the rest of the entry.
+     */
+    readonly tasks?: ReadonlyArray<ScheduledTaskEntry>;
+}
+/*******************************************************************************
+ *
+ * AgentConfig Options
+ *
+ ******************************************************************************/
+/**
+ * Options for the AgentConfig component.
+ */
+interface AgentConfigOptions {
+    /**
+     * Target platforms to generate configuration for.
+     * @default [AGENT_PLATFORM.CURSOR, AGENT_PLATFORM.CLAUDE]
+     */
+    readonly platforms?: ReadonlyArray<AgentPlatform>;
+    /**
+     * Additional agent rules to generate alongside auto-detected and bundled rules.
+     * Custom rules override bundled rules of the same name.
+     */
+    readonly rules?: ReadonlyArray<AgentRule>;
+    /**
+     * Additional skills to generate.
+     */
+    readonly skills?: ReadonlyArray<AgentSkill>;
+    /**
+     * Custom sub-agent definitions.
+     */
+    readonly subAgents?: ReadonlyArray<AgentSubAgent>;
+    /**
+     * Custom procedure definitions (executable shell scripts).
+     */
+    readonly procedures?: ReadonlyArray<AgentProcedure>;
+    /**
+     * MCP server configurations. Cross-platform — rendered to the appropriate
+     * config file for each platform.
+     */
+    readonly mcpServers?: Readonly<Record<string, McpServerConfig>>;
+    /**
+     * Whether to automatically detect and include context-aware rule bundles
+     * based on project introspection.
+     * @default true
+     */
+    readonly autoDetectBundles?: boolean;
+    /**
+     * Explicit list of bundle names to include, regardless of auto-detection.
+     * @example ['vitest', 'aws-cdk']
+     */
+    readonly includeBundles?: ReadonlyArray<string>;
+    /**
+     * Bundle names to exclude even if auto-detection would include them.
+     * @example ['jest']
+     */
+    readonly excludeBundles?: ReadonlyArray<string>;
+    /**
+     * Whether to include the base rule set (project-overview, general conventions).
+     * @default true
+     */
+    readonly includeBaseRules?: boolean;
+    /**
+     * Names of individual rules to exclude from any source.
+     */
+    readonly excludeRules?: ReadonlyArray<string>;
+    /**
+     * Additional content to append to existing rules (from bundles or custom rules).
+     * Keys are rule names, values are markdown content appended after a horizontal rule.
+     * Use this to supplement bundle rules with project-specific additions without
+     * replacing the entire rule.
+     *
+     * @example
+     * ```ts
+     * ruleExtensions: {
+     *   'typescript-conventions': '## Additional Conventions\n\n- Use branded types for IDs',
+     * }
+     * ```
+     */
+    readonly ruleExtensions?: Readonly<Record<string, string>>;
+    /**
+     * Claude Code settings.json configuration.
+     * Generated to .claude/settings.json (committed, team-shared).
+     */
+    readonly claudeSettings?: ClaudeSettingsConfig;
+    /**
+     * Cursor-specific configuration. Generates .cursor/hooks.json for
+     * lifecycle hooks and .cursorignore / .cursorindexingignore for
+     * file visibility control.
+     */
+    readonly cursorSettings?: CursorSettingsConfig;
+    /**
+     * Overrides for the output-path roots used by agent bundles
+     * (requirements, BCM, profiles, meetings, research). Unset fields
+     * fall back to the defaults captured in
+     * `bundles/paths.ts#DEFAULT_AGENT_PATHS`.
+     *
+     * This option is the first of the Group A framework injection
+     * points from epic #414. Per-project propagation of these values
+     * into bundle rule content lands in a follow-up — setting it today
+     * does not yet alter generated rules.
+     */
+    readonly paths?: AgentPathsConfig;
+    /**
+     * Project-specific priority-detection rules. Each rule declares a
+     * match predicate (labels, title regex, body regex, or explicit
+     * issue numbers) and a target `priority:*` tier.
+     *
+     * When non-empty, the `base` bundle renders a "Project-specific
+     * priority rules" subsection into the `issue-label-conventions`
+     * rule. Precedence is **first match wins**; the bundle's default
+     * inference heuristics act as the fallback when no rule matches.
+     *
+     * @see PriorityRule
+     * @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;
+    /**
+     * 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;
+    /**
+     * Funnel-tier configuration consumed by the `orchestrator` bundle.
+     * Drives the multi-key dispatch sort (priority desc → tier asc →
+     * issue number asc) that keeps research feeders from starving.
+     *
+     * When the whole config is omitted the orchestrator ships its
+     * built-in default tier table. Supply `customTypes` to register
+     * additional agent types or override the tier of an existing entry;
+     * supply `tiers` to replace the default list wholesale.
+     *
+     * Malformed configs — tier outside 0–4, empty `type`, duplicate
+     * entries inside a single list — fail the build at synth time via
+     * the orchestrator bundle's tier validator.
+     *
+     * @see AgentTierConfig
+     * @see AgentTierEntry
+     * @see ./bundles/tiers.ts#resolveAgentTiers
+     * @see ./bundles/tiers.ts#validateAgentTierConfig
+     */
+    readonly tiers?: AgentTierConfig;
+    /**
+     * Scope-gate configuration consumed by the `orchestrator` bundle.
+     * Rejects oversized issues at dispatch and instructs the orchestrator
+     * to decompose them into phased sub-issues instead of claiming a
+     * worker session for a multi-hour task.
+     *
+     * When the whole config is omitted, the orchestrator ships with
+     * openhi's published defaults baked in (small: ≤3 AC + ≤2 sources;
+     * medium: ≤6 AC + ≤5 sources; auto-file off).
+     *
+     * Supply `acceptanceCriteria` / `sources` to override the
+     * per-axis thresholds, `decompositionTemplate` to customize the
+     * proposal comment body, or `autoFile: true` to have the
+     * orchestrator file the proposed sub-issues automatically.
+     *
+     * Malformed configs — negative or non-integer thresholds, or
+     * `mediumMax <= smallMax` — fail the build at synth time via
+     * `validateScopeGateConfig`.
+     *
+     * @see ScopeGateConfig
+     * @see ScopeGateThresholds
+     * @see ./bundles/scope-gate.ts#resolveScopeGate
+     * @see ./bundles/scope-gate.ts#validateScopeGateConfig
+     */
+    readonly scopeGate?: ScopeGateConfig;
+    /**
+     * Run-ratio configuration consumed by the `orchestrator` bundle.
+     * Drives the dispatch-to-housekeeping cadence — every `(ratio + 1)`th
+     * run batches PR review + maintenance scan instead of dispatching
+     * fresh issue work, preventing review and maintenance backlog drift
+     * on always-on agent pipelines.
+     *
+     * When the whole config is omitted, the orchestrator ships with
+     * openhi's published 4:1 defaults (four dispatch runs, one
+     * housekeeping run, state file at
+     * `.claude/state/orchestrator-runs.json`, `opus` / `sonnet`
+     * recommended models).
+     *
+     * Supply `ratio` to change the cadence, `stateFilePath` to move
+     * the counter file, `dispatchModel` / `housekeepingModel` to
+     * override the recommended-model labels rendered into the
+     * orchestrator-conventions rule, or `enabled: false` to disable
+     * run-ratio batching entirely.
+     *
+     * Malformed configs — non-integer or non-positive `ratio`, empty
+     * or absolute `stateFilePath` — fail the build at synth time via
+     * `validateRunRatioConfig`.
+     *
+     * @see RunRatioConfig
+     * @see ./bundles/run-ratio.ts#resolveRunRatio
+     * @see ./bundles/run-ratio.ts#validateRunRatioConfig
+     */
+    readonly runRatio?: RunRatioConfig;
+    /**
+     * Pre-flight PR merge configuration consumed by the `orchestrator`
+     * bundle. Drives the pre-flight sweep (vortex step 0b) that merges
+     * eligible PRs before the triage walk reads dependency state,
+     * preventing stale-dependency thrashing on always-on pipelines.
+     *
+     * When the whole config is omitted, the orchestrator ships with
+     * vortex's published defaults (pre-flight enabled, delegated to
+     * the `pr-reviewer` sub-agent, squash merges, linked-issue
+     * keyword required).
+     *
+     * Supply `enabled: false` to disable pre-flight entirely,
+     * `delegateToPrReviewer: false` to merge inline without delegation,
+     * `mergeMethod` to switch to merge-commit or rebase strategies,
+     * `requireLinkedIssue: false` to include PRs without a
+     * `Closes/Fixes/Resolves` keyword, or `eligibleLabels` to gate
+     * pre-flight on consumer-declared opt-in labels.
+     *
+     * Malformed configs — unknown `mergeMethod`, empty /
+     * whitespace-only `eligibleLabels` entries — fail the build at
+     * synth time via `validatePreflightPrConfig`.
+     *
+     * @see PreflightPrConfig
+     * @see ./bundles/preflight-pr.ts#resolvePreflightPr
+     * @see ./bundles/preflight-pr.ts#validatePreflightPrConfig
+     */
+    readonly preflightPr?: PreflightPrConfig;
+    /**
+     * Scheduled-tasks configuration consumed by the `orchestrator`
+     * bundle. Drives the per-agent worker layout at
+     * `<root>/<taskId>/SKILL.md` — one task per agent type with its own
+     * label filter, recommended model, and opt-in enablement.
+     *
+     * Every default task is **disabled by default**. Consumers opt in
+     * explicitly via `overrides.<taskId>.enabled = true`; the generated
+     * repo contains no scheduled-task files until at least one task is
+     * enabled.
+     *
+     * Supply `overrides` to flip `enabled`, cron, or model on a default
+     * task; supply `tasks` to add new entries or replace defaults
+     * wholesale; supply `root` to change the output directory; supply
+     * `enabled: false` on the whole config to disable the subsystem
+     * regardless of individual overrides.
+     *
+     * Malformed configs — unknown model, empty `taskId` / `agent` /
+     * `typeLabel`, duplicate `taskId` in `tasks`, override referencing
+     * an unknown default `taskId` — fail the build at synth time via
+     * `validateScheduledTasksConfig`.
+     *
+     * @see ScheduledTasksConfig
+     * @see ScheduledTaskEntry
+     * @see ScheduledTaskOverride
+     * @see ./bundles/scheduled-tasks.ts#resolveScheduledTasks
+     * @see ./bundles/scheduled-tasks.ts#validateScheduledTasksConfig
+     */
+    readonly scheduledTasks?: ScheduledTasksConfig;
+    /**
+     * Agent-driven unblocking configuration consumed by the
+     * `orchestrator` bundle. Controls the targeted sweep agents run
+     * after applying `status:done` — the sweep flips downstream
+     * `Depends on: #<just-closed>` issues from `status:blocked` to
+     * `status:ready` without waiting for the next orchestrator
+     * dispatch cycle.
+     *
+     * When the whole config is omitted, the orchestrator ships with
+     * the sweep **enabled** and a generic citation comment.
+     *
+     * Supply `enabled: false` to disable the sweep entirely,
+     * `commentTemplate` to override the unblock citation, or
+     * `flagPartialUnblockWithAttention: true` to have the sweep post a
+     * progress comment on dependents whose dependency list is not yet
+     * fully resolved.
+     *
+     * Malformed configs — empty / whitespace-only `commentTemplate` or
+     * `partialUnblockCommentTemplate` — fail the build at synth time
+     * via `validateUnblockDependentsConfig`.
+     *
+     * @see UnblockDependentsConfig
+     * @see ./bundles/unblock-dependents.ts#resolveUnblockDependents
+     * @see ./bundles/unblock-dependents.ts#validateUnblockDependentsConfig
+     */
+    readonly unblockDependents?: UnblockDependentsConfig;
+    /**
+     * Progress-file convention consumed by the `base` bundle and every
+     * phased-agent bundle (bcm-writer, research-pipeline, etc.). Every
+     * phased agent writes a small progress file when it claims an
+     * issue, updates it after each non-trivial step, and deletes it in
+     * the final commit that closes the issue. Crashed sessions are
+     * resumed by reading the file rather than starting over.
+     *
+     * When the whole config is omitted, the convention ships
+     * **enabled** with JSON-formatted files stored under
+     * `.claude/state/<issue-number>-progress.json` and a 72-hour
+     * staleness threshold.
+     *
+     * Supply `enabled: false` to disable the convention entirely,
+     * `format: "markdown"` to use the openhi-style markdown body,
+     * `stateDir` / `filenamePattern` to move or rename the on-disk
+     * artefact, `cleanupOnComplete: false` to retain progress files
+     * after the issue closes, or `staleAfterHours` to override the
+     * stale-branch threshold rendered into the documentation.
+     *
+     * Malformed configs — empty / whitespace-only or absolute
+     * `stateDir`, empty / whitespace-only `filenamePattern`,
+     * `filenamePattern` missing the `<ISSUE_NUMBER>` placeholder,
+     * unknown `format`, non-positive `staleAfterHours` — fail the
+     * build at synth time via `validateProgressFilesConfig`.
+     *
+     * @see ProgressFilesConfig
+     * @see ./bundles/progress-files.ts#resolveProgressFiles
+     * @see ./bundles/progress-files.ts#validateProgressFilesConfig
+     * @see ./bundles/progress-files.ts#renderProgressFilesRuleContent
+     */
+    readonly progressFiles?: ProgressFilesConfig;
+    /**
+     * Shared-editing safety convention consumed by the `base` bundle
+     * and every phased-agent bundle that writes rows to a shared
+     * registry or feature-matrix file. Documents the single-entry /
+     * deterministic-sort / verify-commit / re-sort-on-conflict protocol
+     * agents follow when touching an index file other sessions may also
+     * be editing concurrently.
+     *
+     * When the whole config is omitted, the convention ships
+     * **enabled** with the documented default set of shared-index path
+     * patterns, commit-path verification on, and the `rebase` conflict
+     * strategy.
+     *
+     * Supply `enabled: false` to disable the convention entirely,
+     * `sharedIndexPaths` to replace the default pattern list,
+     * `verifyCommit: false` to drop the commit-path verification
+     * protocol from the rendered rule, `conflictStrategy: "merge"` to
+     * switch the conflict recipe to the merge-commit flow, or
+     * `emitHelper: true` to ship the
+     * `.claude/procedures/verify-index-row.sh` helper script to disk.
+     *
+     * Malformed configs — empty `sharedIndexPaths`, empty /
+     * whitespace-only path entry, unknown `conflictStrategy` — fail
+     * the build at synth time via `validateSharedEditingConfig`.
+     *
+     * @see SharedEditingConfig
+     * @see ./bundles/shared-editing.ts#resolveSharedEditing
+     * @see ./bundles/shared-editing.ts#validateSharedEditingConfig
+     * @see ./bundles/shared-editing.ts#renderSharedEditingRuleContent
+     */
+    readonly sharedEditing?: SharedEditingConfig;
+    /**
+     * Skill eval harness convention consumed by the `base` bundle and
+     * every skill-owning bundle. Each skill under
+     * `<skillsRoot>/<skill-name>/` may ship a regression suite at
+     * `<skillsRoot>/<skill-name>/evals/evals.json`. Suites are
+     * declarative prompt / expected-output fixtures parameterised by a
+     * shared product-context fixture so the same eval shape works
+     * across every project that depends on configulator.
+     *
+     * When the whole config is omitted, the convention ships
+     * **enabled** with skills-root `.claude/skills`, product-context
+     * fixture `docs/src/content/docs/project-context.md`,
+     * product-context required, and the runner helper opt-in.
+     *
+     * Supply `enabled: false` to disable the convention entirely,
+     * `skillsRoot` or `productContextPath` to override the default
+     * paths, `requireProductContext: false` to downgrade missing
+     * product-context to a warning, or `emitRunner: true` to ship the
+     * `.claude/procedures/run-skill-evals.sh` helper to disk.
+     *
+     * Malformed configs — empty / whitespace-only or absolute
+     * `skillsRoot`, empty / whitespace-only or absolute
+     * `productContextPath` — fail the build at synth time via
+     * `validateSkillEvalsConfig`.
+     *
+     * @see SkillEvalsConfig
+     * @see ./bundles/skill-evals.ts#resolveSkillEvals
+     * @see ./bundles/skill-evals.ts#validateSkillEvalsConfig
+     * @see ./bundles/skill-evals.ts#renderSkillEvalsRuleContent
+     */
+    readonly skillEvals?: SkillEvalsConfig;
+    /**
+     * Workflow-diagrams convention consumed by the `base` bundle and
+     * every phased-agent bundle. Documents the single hand-authored
+     * Mermaid-based diagrams page that visualises every agent's phase
+     * graph and every cross-agent handoff, and enforces the
+     * diagram-touched-when-bundle-touched rule: a change set that
+     * modifies a bundle's phase graph must also update the matching
+     * section in the diagrams page.
+     *
+     * When the whole config is omitted, the convention ships
+     * **enabled** with the default diagrams path
+     * (`docs/src/content/docs/agents/workflows.md`), the default
+     * bundle-path patterns, the hard-requirement phrasing, and both
+     * the starter page and the checker script opt-in.
+     *
+     * Supply `enabled: false` to disable the convention entirely,
+     * `diagramsPath` to move the page, `bundlePathPatterns` to
+     * replace the default pattern list, `emitStarterDiagram: true`
+     * to seed a minimal starter page on disk, `emitChecker: true` to
+     * ship the `.claude/procedures/check-workflow-diagrams.sh`
+     * helper, or `requireDiagramUpdate: false` to soften the rule
+     * phrasing from MUST to SHOULD.
+     *
+     * Malformed configs — empty / whitespace-only or absolute
+     * `diagramsPath`, empty `bundlePathPatterns`, empty /
+     * whitespace-only pattern entry — fail the build at synth time
+     * via `validateWorkflowDiagramsConfig`.
+     *
+     * @see WorkflowDiagramsConfig
+     * @see ./bundles/workflow-diagrams.ts#resolveWorkflowDiagrams
+     * @see ./bundles/workflow-diagrams.ts#validateWorkflowDiagramsConfig
+     * @see ./bundles/workflow-diagrams.ts#renderWorkflowDiagramsRuleContent
+     */
+    readonly workflowDiagrams?: WorkflowDiagramsConfig;
+    /**
+     * Issue-templates convention consumed by the `base` bundle and
+     * every phased-agent bundle that files downstream issues.
+     * Documents the single hand-authored reference page that carries
+     * one canonical `gh issue create` recipe per downstream phase
+     * label, and enforces the reference-don't-inline rule: bundle
+     * rules and agent prompts cite the matching section of that page
+     * instead of duplicating a full `gh issue create` invocation.
+     *
+     * When the whole config is omitted, the convention ships
+     * **enabled** with the default templates path
+     * (`docs/src/content/docs/agents/issue-templates.md`), the default
+     * bundle-path patterns, the hard-requirement phrasing, and both
+     * the starter page and the lint script opt-in.
+     *
+     * Supply `enabled: false` to disable the convention entirely,
+     * `templatesPath` to move the page, `bundlePathPatterns` to
+     * replace the default pattern list, `emitStarterDoc: true` to
+     * seed a minimal starter page on disk, `emitChecker: true` to
+     * ship the `.claude/procedures/check-issue-templates.sh` helper,
+     * or `requireReference: false` to soften the rule phrasing from
+     * MUST to SHOULD.
+     *
+     * Malformed configs — empty / whitespace-only or absolute
+     * `templatesPath`, empty `bundlePathPatterns`, empty /
+     * whitespace-only pattern entry — fail the build at synth time
+     * via `validateIssueTemplatesConfig`.
+     *
+     * @see IssueTemplatesConfig
+     * @see ./bundles/issue-templates.ts#resolveIssueTemplates
+     * @see ./bundles/issue-templates.ts#validateIssueTemplatesConfig
+     * @see ./bundles/issue-templates.ts#renderIssueTemplatesRuleContent
+     */
+    readonly issueTemplates?: IssueTemplatesConfig;
+}
+
+/**
+ * Generates AI coding assistant configuration files from a common schema.
+ *
+ * Supports Cursor and Claude Code (initial release), with Codex and Copilot
+ * renderers planned for future issues. Rules, skills, and sub-agents are
+ * defined once and rendered into the correct format for each target platform.
+ *
+ * Follows the configulator component pattern: extends Component, static .of()
+ * factory, options interface with JSDoc.
+ *
+ * @example
+ * ```ts
+ * new AgentConfig(project, {
+ *   rules: [{
+ *     name: 'my-rule',
+ *     description: 'Project conventions',
+ *     scope: AGENT_RULE_SCOPE.ALWAYS,
+ *     content: '# My Rule\n\nFollow these conventions...',
+ *   }],
+ * });
+ * ```
+ */
+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.
+     *
+     * Merge order: defaults → bundle permissions → user-supplied entries.
+     * `defaultMode` defaults to `"dontAsk"` unless overridden.
+     */
+    private static mergeClaudeDefaults;
+    private readonly options;
+    private cachedBundles?;
+    private cachedPaths?;
+    constructor(project: Project$1, options?: AgentConfigOptions);
+    /**
+     * Resolved agent-path roots for this project. Consumer overrides on
+     * `AgentConfigOptions.paths` cascade into derived roots via
+     * `resolveAgentPaths()`. Memoized so repeated reads during synthesis
+     * do not re-run the resolver.
+     */
+    private get resolvedPaths();
+    /**
+     * Path-aware built-in bundles assembled with this project's
+     * resolved paths. Path-aware bundle factories (e.g.
+     * `buildResearchPipelineBundle`) receive the resolved struct so
+     * their rendered rule content reflects any consumer override.
+     * Bundles that do not read agent paths are passed through as-is
+     * from their default const exports.
+     */
+    private get pathAwareBundles();
+    /**
+     * Returns the bundles that are active for this project: auto-detected
+     * bundles (when `autoDetectBundles !== false`) plus force-included
+     * bundles, minus explicitly excluded bundles. Deduplicated by name.
+     *
+     * Exposed so sibling components (e.g. the sync-labels workflow) can
+     * consume bundle-contributed configuration.
+     */
+    get activeBundles(): ReadonlyArray<AgentRuleBundle>;
+    preSynthesize(): void;
+    private resolvePlatforms;
+    private resolveRules;
     /**
      * Return a bundle's rules with `filePatterns` narrowed to the projects
      * that actually matched the bundle's detection predicate (when the bundle
@@ -1699,253 +3180,1479 @@ declare class AgentConfig extends Component {
      * implement the hook are returned with only the custom-section
      * transformation (if any) applied.
      */
-    private bundleRulesFor;
-    private resolveSkills;
-    private resolveSubAgents;
-    private resolveProcedures;
+    private bundleRulesFor;
+    private resolveSkills;
+    private resolveSubAgents;
+    private resolveProcedures;
+    /**
+     * Resolves template variables in rule content using project metadata.
+     * Emits synthesis warnings for rules with unresolved variables.
+     */
+    private resolveTemplates;
+    /**
+     * Resolves template variables in skill instructions using project metadata.
+     */
+    private resolveSkillTemplates;
+    /**
+     * Resolves template variables in sub-agent prompts using project metadata.
+     */
+    private resolveSubAgentTemplates;
+    /**
+     * Resolves template variables in procedure content using project metadata.
+     */
+    private resolveProcedureTemplates;
+    /**
+     * Collects Claude permission entries from all active bundles.
+     */
+    private resolveBundlePermissions;
+}
+
+/**
+ * Fully-resolved agent output-path roots. Every property is required.
+ *
+ * This is the shape that bundle code consumes at module-eval time via
+ * `DEFAULT_AGENT_PATHS`, and the shape that `resolveAgentPaths()`
+ * returns when consumers supply a partial `AgentPathsConfig` override.
+ */
+interface ResolvedAgentPaths {
+    readonly docsRoot: string;
+    readonly researchRoot: string;
+    readonly profilesRoot: string;
+    readonly meetingsRoot: string;
+    readonly requirementsRoot: string;
+    readonly researchRequirementsRoot: string;
+    readonly bcmRoot: string;
+    readonly peopleRoot: string;
+    readonly companiesRoot: string;
+    readonly softwareRoot: string;
+    readonly industriesRoot: string;
+}
+/**
+ * Canonical default values for every agent path. These mirror the
+ * hardcoded paths that bundles used before `AgentPathsConfig` existed,
+ * so `DEFAULT_AGENT_PATHS.*` can be substituted into bundle rule
+ * content at module-eval time without changing the generated
+ * `.claude/rules/*.md` snapshot.
+ *
+ * Consumers override the defaults by passing an `AgentPathsConfig`
+ * through `AgentConfigOptions.paths` and resolving it with
+ * `resolveAgentPaths()`. Per-project propagation into bundle rule
+ * content is a follow-up — this export is the first step: interface +
+ * resolver land in this PR; the `AgentConfig.resolveRules` wiring lands
+ * next.
+ */
+declare const DEFAULT_AGENT_PATHS: ResolvedAgentPaths;
+/**
+ * Resolve a partial `AgentPathsConfig` into a fully-populated
+ * `ResolvedAgentPaths`. Unset fields cascade from their parent root:
+ *
+ * - `profilesRoot`, `meetingsRoot`, `requirementsRoot`, and `bcmRoot`
+ *   derive from `docsRoot` when not explicitly set.
+ * - `researchRequirementsRoot` derives from `researchRoot` when not
+ *   explicitly set.
+ * - `peopleRoot`, `companiesRoot`, `softwareRoot`, and `industriesRoot`
+ *   derive from the resolved `profilesRoot` when not explicitly set,
+ *   so that overriding `docsRoot` alone (or overriding `profilesRoot`
+ *   alone) propagates correctly through every dependent root.
+ */
+declare function resolveAgentPaths(paths?: AgentPathsConfig): ResolvedAgentPaths;
+
+/**
+ * Agenda bundle — enabled by default.
+ *
+ * Consuming projects can disable it with
+ * `excludeBundles: ["agenda"]`. `appliesWhen` always returns `true`
+ * (peer-present assumption, same pattern as the other workflow
+ * bundles).
+ *
+ * Provides a 2-phase pre-meeting agenda pipeline
+ * (draft → finalize), complementing the post-meeting pipeline in
+ * the `meeting-analysis` bundle. Ships a sub-agent, two user-
+ * invocable skills (`/draft-agenda`, `/finalize-agenda`), and
+ * `agenda:*` phase labels via the bundle `labels` mechanism so
+ * consuming projects automatically pick up the label taxonomy
+ * through the sync-labels workflow.
+ *
+ * Reuses the meeting-type taxonomy from
+ * `AgentConfigOptions.meetings.meetingTypes` — the same table the
+ * `meeting-analysis` bundle consumes for post-meeting extraction.
+ */
+declare const agendaBundle: AgentRuleBundle;
+
+/**
+ * AWS CDK bundle — auto-detected when `aws-cdk-lib` is in dependencies.
+ */
+declare const awsCdkBundle: AgentRuleBundle;
+
+/**
+ * Base bundle — always included unless `includeBaseRules: false`.
+ * Contains project-overview, interaction-style, and general-conventions rules.
+ */
+declare function buildBaseBundle(paths?: ResolvedAgentPaths): AgentRuleBundle;
+/**
+ * Default-paths instance of the base bundle, preserved for backward
+ * compatibility with consumers that import the const directly. The
+ * factory above is the canonical entry point when a consumer supplies
+ * `AgentConfigOptions.paths`.
+ */
+declare const baseBundle: AgentRuleBundle;
+
+/**
+ * Build the bcm-writer bundle with the supplied resolved paths.
+ *
+ * Every reference to a canonical agent path (bcm root, docs root, etc.)
+ * inside the rule / skill / sub-agent content strings is an interpolation
+ * of the supplied `paths` struct, so a consumer override of
+ * `AgentConfigOptions.paths` propagates to the rendered output.
+ *
+ * Consuming projects can disable it with `excludeBundles: ["bcm-writer"]`.
+ * `appliesWhen` always returns `true` per this batch's directive that
+ * bundles assume peers are present.
+ *
+ * Ships a single consolidated sub-agent (`bcm-writer`) with all 4 phase
+ * handlers in one prompt (outline, scaffold, context, connect), a
+ * user-invocable skill (`/write-bcm`), and `type:bcm-document` plus
+ * `bcm:*` phase labels.
+ *
+ * The bundle assumes the `people-profile`, `company-profile`, and
+ * `research-pipeline` bundles are also enabled so Phase 4 can hand off
+ * surfaced items via `people:research`, `company:research`, and
+ * `research:scope` issues.
+ */
+declare function buildBcmWriterBundle(paths?: ResolvedAgentPaths): AgentRuleBundle;
+/**
+ * Default-paths instance of the bcm-writer bundle, preserved for
+ * backward compatibility with consumers that import the const directly.
+ * The factory above is the canonical entry point when a consumer
+ * supplies `AgentConfigOptions.paths`.
+ */
+declare const bcmWriterBundle: AgentRuleBundle;
+
+/**
+ * Build the business-models bundle with the supplied resolved paths.
+ *
+ * Every reference to a canonical agent path (docs root, research root,
+ * etc.) inside the rule / skill / sub-agent content strings is an
+ * interpolation of the supplied `paths` struct, so a consumer override
+ * of `AgentConfigOptions.paths` propagates to the rendered output.
+ *
+ * The bundle sits between `industry-discovery` (upstream, selects
+ * verticals) and `bcm-writer` (downstream, models capabilities). It
+ * assumes `bcm-writer` is enabled so Phase 3 can hand off surfaced
+ * capabilities via `bcm:outline` issues, and it is read by
+ * `company-profile` via the shared `<BUSINESS_MODELS_ROOT>` default
+ * path (`<docsRoot>/industry-research/`).
+ */
+declare function buildBusinessModelsBundle(paths?: ResolvedAgentPaths): AgentRuleBundle;
+/**
+ * Default-paths instance of the business-models bundle, preserved for
+ * backward compatibility with consumers that import the const
+ * directly. The factory above is the canonical entry point when a
+ * consumer supplies `AgentConfigOptions.paths`.
+ */
+declare const businessModelsBundle: AgentRuleBundle;
+
+/**
+ * Build the company-profile bundle with the supplied resolved paths.
+ *
+ * Every reference to a canonical agent path (docs root, etc.) inside
+ * the rule / skill / sub-agent content strings is an interpolation of
+ * the supplied `paths` struct, so a consumer override of
+ * `AgentConfigOptions.paths` propagates to the rendered output.
+ *
+ * Ships a sub-agent (`company-profile-analyst`), four user-invocable
+ * skills (`/profile-company`, `/match-company`, `/refresh-company`,
+ * `/analyze-segment`), and `type:company-profile` plus `company:*`
+ * phase labels for the six phases.
+ */
+declare function buildCompanyProfileBundle(paths?: ResolvedAgentPaths): AgentRuleBundle;
+/**
+ * Default-paths instance of the company-profile bundle, preserved for
+ * backward compatibility with consumers that import the const
+ * directly. The factory above is the canonical entry point when a
+ * consumer supplies `AgentConfigOptions.paths`.
+ */
+declare const companyProfileBundle: AgentRuleBundle;
+
+/**
+ * Customer-profile bundle — enabled by default.
+ *
+ * Consuming projects can disable it with
+ * `excludeBundles: ["customer-profile"]`. `appliesWhen` always
+ * returns `true` per the workflow-bundle peer-present assumption.
+ *
+ * Ships a sub-agent (`customer-profile-analyst`), three
+ * user-invocable skills (`/discover-customers`, `/profile-customer`,
+ * `/analyze-customer-competitors`), a customer-profile-page template
+ * (emitted alongside the profile skill), and `type:customer-profile`
+ * plus `customer:*` phase labels.
+ *
+ * The bundle sits downstream of `meeting-analysis`,
+ * `industry-discovery`, and `research-pipeline` (which surface the
+ * need for customer-archetype research) and hands off unmet needs to
+ * the `requirements-analyst` bundle via `req:scan` issues, and
+ * canonical profiles to `company-profile` and `people-profile` for
+ * representative customer organizations, competitor organizations,
+ * and notable contacts.
+ *
+ * Distinct from `company-profile`: the `company-profile` bundle
+ * targets any company entity (competitor, vendor, partner, customer
+ * organization); this bundle targets **customer archetypes** (the
+ * reusable shape of a buyer/user segment) and closes the loop from
+ * unmet need to `req:scan` seed via the shared software-profile
+ * feature matrix.
+ */
+declare function buildCustomerProfileBundle(paths?: ResolvedAgentPaths): AgentRuleBundle;
+/**
+ * Default-paths instance of the customer-profile bundle, preserved
+ * for backward compatibility with consumers that import the const
+ * directly. The factory above is the canonical entry point when a
+ * consumer supplies `AgentConfigOptions.paths`.
+ */
+declare const customerProfileBundle: AgentRuleBundle;
+
+/**
+ * Render the shell body of the `.claude/procedures/extract-api.sh`
+ * helper. Exported so the docs-sync bundle can register it as an
+ * `AgentProcedure` and the bundles test suite can assert on the
+ * script's contents.
+ *
+ * The helper runs `@microsoft/api-extractor` end-to-end for a single
+ * package and writes the `.api.md` rollup to the scratch folder
+ * declared by that package's `api-extractor.json`. Rollups are
+ * **regenerate-on-scan** per the docs-sync epic resolved decision #3
+ * — the scan phase consumes the freshly-regenerated rollup in-memory
+ * rather than comparing against a committed baseline.
+ *
+ * Exit codes: `0` success, `1` usage / missing directory, `2` no
+ * `api-extractor.json` at the target path, `3` the extractor exited
+ * non-zero (compile error or extractor failure).
+ */
+declare function renderExtractApiProcedure(): string;
+/**
+ * `AgentProcedure` definition for `.claude/procedures/extract-api.sh`.
+ * Registered on the docs-sync bundle so it ships when the bundle is
+ * force-included — matches the packaging of other bundled procedures
+ * (see `orchestratorBundle.procedures`).
+ */
+declare const extractApiProcedure: AgentProcedure;
+/**
+ * Docs-sync bundle — scaffolding release.
+ *
+ * Opt-in via `includeBundles: ["docs-sync"]`. `appliesWhen` returns
+ * `false` by default so the scaffold ships disabled until a
+ * downstream child issue enables it across the monorepo.
+ *
+ * Provides the skeleton of a 2-phase drift-detection + audit pipeline
+ * (scan → fix) designed for monorepos that keep documentation inside
+ * a Starlight singleton. Ships a sub-agent, two user-invocable skills
+ * (`/docs-sync-pr`, `/docs-sync-audit`), five new labels
+ * (`type:docs-sync`, `docs-sync:scan`, `docs-sync:fix`,
+ * `docs-sync:advisory`, `docs-sync:blocking`), and a
+ * `Documentation Sync Workflow` rule rendered into CLAUDE.md so
+ * humans reading the file see the pipeline exists even while the
+ * behavior is still landing across child issues.
+ */
+declare function buildDocsSyncBundle(paths?: ResolvedAgentPaths): AgentRuleBundle;
+/**
+ * Default-paths instance of the docs-sync bundle, preserved for
+ * parity with other path-aware bundles in this directory. The factory
+ * above is the canonical entry point when a consumer supplies
+ * `AgentConfigOptions.paths`.
+ */
+declare const docsSyncBundle: AgentRuleBundle;
+
+/**
+ * GitHub workflow bundle — auto-detected when the project has a GitHub component.
+ */
+declare const githubWorkflowBundle: AgentRuleBundle;
+
+/**
+ * Build the industry-discovery bundle with the supplied resolved paths.
+ *
+ * Every reference to a canonical agent path (docs root, etc.) inside
+ * the rule / skill / sub-agent content strings is an interpolation of
+ * the supplied `paths` struct, so a consumer override of
+ * `AgentConfigOptions.paths` propagates to the rendered output.
+ */
+declare function buildIndustryDiscoveryBundle(paths?: ResolvedAgentPaths): AgentRuleBundle;
+/**
+ * Default-paths instance of the industry-discovery bundle, preserved
+ * for backward compatibility with consumers that import the const
+ * directly. The factory above is the canonical entry point when a
+ * consumer supplies `AgentConfigOptions.paths`.
+ */
+declare const industryDiscoveryBundle: AgentRuleBundle;
+
+/**
+ * Jest bundle — auto-detected when Jest is in dependencies.
+ */
+declare const jestBundle: AgentRuleBundle;
+
+/**
+ * Maintenance-audit bundle — enabled by default.
+ *
+ * Consuming projects can disable it with
+ * `excludeBundles: ["maintenance-audit"]`. `appliesWhen` always returns
+ * `true` per this batch's directive that bundles assume peers are
+ * present.
+ *
+ * Provides a 3-phase documentation-maintenance pipeline
+ * (scan → fix → verify) designed for any project with structured doc
+ * registries and cross-references. Ships a sub-agent, two user-
+ * invocable skills (`/audit-docs`, `/verify-audit`), and `maint:*`
+ * phase labels via the bundle `labels` mechanism so consuming projects
+ * automatically pick up the label taxonomy through the sync-labels
+ * workflow.
+ */
+declare function buildMaintenanceAuditBundle(paths?: ResolvedAgentPaths): AgentRuleBundle;
+/**
+ * Default-paths instance of the maintenance-audit bundle, preserved
+ * for backward compatibility with consumers that import the const
+ * directly. The factory above is the canonical entry point when a
+ * consumer supplies `AgentConfigOptions.paths`.
+ */
+declare const maintenanceAuditBundle: AgentRuleBundle;
+
+/**
+ * Meeting analysis bundle — included by default.
+ * Provides a 4-phase meeting transcript processing workflow.
+ */
+declare const meetingAnalysisBundle: AgentRuleBundle;
+
+/**
+ * Default for whether the orchestrator delegates the pre-flight merge
+ * sweep to the `pr-reviewer` sub-agent. Mirrors vortex's step 0b
+ * contract: invoking the reviewer as a sub-agent lets the merge
+ * workflow run on its own (cheaper) model rather than on the
+ * orchestrator's model. Set to `false` to have the orchestrator merge
+ * eligible PRs inline.
+ *
+ * @see PreflightPrConfig
+ */
+declare const DEFAULT_DELEGATE_TO_PR_REVIEWER = true;
+/**
+ * Default merge method used when the orchestrator merges a PR inline
+ * (`delegateToPrReviewer = false`). Squash-and-merge matches every
+ * existing configulator consumer and keeps `main` free of
+ * branch-construction noise.
+ *
+ * @see PreflightPrConfig
+ */
+declare const DEFAULT_MERGE_METHOD: PreflightMergeMethod;
+/**
+ * Default for whether pre-flight skips PRs lacking a
+ * `Closes/Fixes/Resolves #<n>` keyword in the body. Most pipelines
+ * require a linked issue, so the safe default is `true` — pre-flight
+ * only merges PRs that cleanly complete a known issue.
+ *
+ * @see PreflightPrConfig
+ */
+declare const DEFAULT_REQUIRE_LINKED_ISSUE = true;
+/**
+ * Merge-method values accepted on `PreflightPrConfig.mergeMethod`.
+ * Matches the `gh pr merge` flags: `--squash`, `--merge`, `--rebase`.
+ */
+declare const PREFLIGHT_MERGE_METHOD_VALUES: readonly ["squash", "merge", "rebase"];
+type PreflightMergeMethod = (typeof PREFLIGHT_MERGE_METHOD_VALUES)[number];
+/**
+ * Fully-resolved pre-flight PR merge settings. Every field is defaulted
+ * so downstream renderers can reason about a single canonical shape.
+ */
+interface ResolvedPreflightPr {
+    readonly enabled: boolean;
+    readonly delegateToPrReviewer: boolean;
+    readonly mergeMethod: PreflightMergeMethod;
+    readonly requireLinkedIssue: boolean;
+    readonly eligibleLabels: ReadonlyArray<string>;
+}
+/**
+ * Resolve a (possibly absent) `PreflightPrConfig` into a canonical
+ * `ResolvedPreflightPr` with every field filled in. Unset fields
+ * cascade from their documented defaults.
+ *
+ * Malformed configs (unknown `mergeMethod`, empty or whitespace-only
+ * `eligibleLabels` entry) throw a descriptive `Error` — callers should
+ * not need to guard against it at runtime.
+ */
+declare function resolvePreflightPr(config?: PreflightPrConfig): ResolvedPreflightPr;
+/**
+ * Synth-time validation hook. Throws a descriptive `Error` when the
+ * supplied `PreflightPrConfig` is malformed. Called by
+ * `AgentConfig.preSynthesize` before any rendering so a misconfigured
+ * pre-flight sweep fails the build instead of silently shipping a
+ * broken check-blocked.sh subcommand. Returns the resolved config
+ * unchanged so callers can write
+ * `const pf = validatePreflightPrConfig(config)` in one line.
+ *
+ * Malformed cases rejected here:
+ *
+ * - `mergeMethod` not one of `squash` / `merge` / `rebase`.
+ * - Any `eligibleLabels` entry that is empty or whitespace-only.
+ */
+declare function validatePreflightPrConfig(config?: PreflightPrConfig): ResolvedPreflightPr;
+/**
+ * Render the markdown subsection appended to the
+ * `orchestrator-conventions` rule. Always returns a non-empty string so
+ * the orchestrator rule documents the pre-flight contract even when the
+ * consumer relies on the defaults.
+ */
+declare function renderPreflightPrSection(pf: ResolvedPreflightPr): string;
+/**
+ * Render a shell-script snippet embedded in `check-blocked.sh`. The
+ * snippet declares a `cmd_preflight()` function that scans open PRs
+ * and echoes one eligibility line per PR in the canonical
+ * `PREFLIGHT_MERGE PR #<n> issue:#<m> branch:<b> — "<title>"` format
+ * (or `PREFLIGHT_SKIP PR #<n> — <reason> — "<title>"` on skip, or
+ * `NO_PREFLIGHT_PRS` when nothing is eligible).
+ *
+ * Returns the body of a shell function block (including the
+ * `cmd_preflight()` wrapper) so the surrounding script can splice it
+ * inline at the exact indent level it wants.
+ */
+declare function renderPreflightPrShellHelpers(pf: ResolvedPreflightPr): string;
+
+/**
+ * Default dispatch-to-housekeeping ratio — openhi's `DISPATCHER.md`
+ * ships a 4:1 ratio: four consecutive dispatch runs, then one
+ * housekeeping run, then the counter wraps. The ratio value stored
+ * here is the dispatch-run count per housekeeping run; with
+ * `ratio = 4`, runs 1–4 dispatch and run 5 housekeeps. The cycle
+ * length is therefore `ratio + 1`.
+ *
+ * @see RunRatioConfig
+ */
+declare const DEFAULT_DISPATCH_TO_HOUSEKEEPING_RATIO = 4;
+/**
+ * Default on-disk path for the orchestrator run-counter state file,
+ * relative to the repo root. The file is tiny JSON
+ * (`{ "run_counter": <n> }`) and is gitignored in most consumer repos
+ * because it's local-only — each operator's orchestrator session
+ * maintains its own counter.
+ *
+ * @see RunRatioConfig
+ */
+declare const DEFAULT_STATE_FILE_PATH = ".claude/state/orchestrator-runs.json";
+/**
+ * Default recommended model label for dispatch runs. Rendered into
+ * the orchestrator-conventions rule so agents and humans can read the
+ * model pairing at a glance; the string is purely informational and
+ * does not cause configulator to set `AGENT_MODEL` on the sub-agent.
+ *
+ * @see RunRatioConfig
+ */
+declare const DEFAULT_DISPATCH_MODEL = "opus";
+/**
+ * Default recommended model label for housekeeping runs. See
+ * `DEFAULT_DISPATCH_MODEL` for the rendering contract. Housekeeping
+ * runs are mechanical (batch PR review + maintenance scan), so a
+ * cheaper model like Sonnet is the documented recommendation.
+ *
+ * @see RunRatioConfig
+ */
+declare const DEFAULT_HOUSEKEEPING_MODEL = "sonnet";
+/**
+ * Fully-resolved run-ratio settings. Every field is defaulted so
+ * downstream renderers can reason about a single canonical shape.
+ */
+interface ResolvedRunRatio {
+    readonly enabled: boolean;
+    readonly ratio: number;
+    readonly stateFilePath: string;
+    readonly dispatchModel: string;
+    readonly housekeepingModel: string;
+}
+/**
+ * Resolve a (possibly absent) `RunRatioConfig` into a canonical
+ * `ResolvedRunRatio` with every field filled in. Unset fields
+ * cascade from their documented defaults.
+ *
+ * Malformed configs (non-integer or non-positive ratio, empty or
+ * whitespace-only state file path) throw a descriptive `Error` —
+ * callers should not need to guard against it at runtime.
+ */
+declare function resolveRunRatio(config?: RunRatioConfig): ResolvedRunRatio;
+/**
+ * Synth-time validation hook. Throws a descriptive `Error` when the
+ * supplied `RunRatioConfig` is malformed. Called by
+ * `AgentConfig.preSynthesize` before any rendering so a misconfigured
+ * ratio fails the build instead of silently shipping broken
+ * housekeeping cadence. Returns the resolved ratio unchanged so
+ * callers can write `const rr = validateRunRatioConfig(config)` in
+ * one line.
+ *
+ * Malformed cases rejected here:
+ *
+ * - `ratio` non-integer, zero, or negative.
+ * - `stateFilePath` empty / whitespace-only, or an absolute path
+ *   (the state file must live inside the repo).
+ */
+declare function validateRunRatioConfig(config?: RunRatioConfig): ResolvedRunRatio;
+/**
+ * Compute the run type (`"dispatch"` or `"housekeeping"`) for a
+ * given run counter value and resolved ratio. Used by the TypeScript
+ * side (tests, downstream consumers that want to reason about the
+ * cadence without shelling out). The shell helper produced by
+ * `renderRunRatioShellHelpers` implements the same logic.
+ *
+ * Every `(ratio + 1)`th run is a housekeeping run; all others
+ * dispatch. For `ratio = 4`, runs 1–4 dispatch and run 5
+ * housekeeps; run 6 is again dispatch; run 10 housekeeps.
+ */
+declare function classifyRun(runCounter: number, ratio: ResolvedRunRatio): "dispatch" | "housekeeping";
+/**
+ * Render the markdown subsection appended to the
+ * `orchestrator-conventions` rule. Always returns a non-empty string
+ * so the orchestrator rule documents the cadence even when the
+ * consumer relies on the defaults.
+ */
+declare function renderRunRatioSection(ratio: ResolvedRunRatio): string;
+/**
+ * Render a shell-script snippet embedded in `check-blocked.sh`. The
+ * snippet declares a `run_counter_tick()` function that:
+ *
+ * 1. Reads the state file (creating it with `run_counter: 1` if
+ *    missing or unparseable).
+ * 2. Increments the counter.
+ * 3. Writes the new counter back atomically (temp file + `mv`).
+ * 4. Echoes the post-increment counter and the classified run type
+ *    (`dispatch` or `housekeeping`) in the canonical
+ *    `run=<n> type=<dispatch|housekeeping>` format.
+ *
+ * Returns the body of a shell function block (including the
+ * `run_counter_tick()` wrapper) so the surrounding script can splice
+ * it inline at the exact indent level it wants.
+ */
+declare function renderRunRatioShellHelpers(ratio: ResolvedRunRatio): string;
+
+/**
+ * Recommended model labels surfaced on the scheduled-task SKILL.md
+ * frontmatter. The labels are **informational** — configulator does not
+ * pin a model per task (the Claude Code scheduled-task runtime does not
+ * support per-task model pinning yet). Operators choose the model at
+ * invocation time; splitting workers by type still gives independent
+ * cadence and clean opt-in/opt-out control.
+ *
+ * @see ScheduledTasksConfig
+ */
+declare const SCHEDULED_TASK_MODEL_VALUES: readonly ["opus", "sonnet", "haiku"];
+type ScheduledTaskModel = (typeof SCHEDULED_TASK_MODEL_VALUES)[number];
+/**
+ * Default root directory (relative to the repo root) for scheduled-task
+ * files. Mirrors the vortex layout — one directory per task at
+ * `.claude/scheduled-tasks/<taskId>/SKILL.md`.
+ *
+ * @see ScheduledTasksConfig
+ */
+declare const DEFAULT_SCHEDULED_TASKS_ROOT = ".claude/scheduled-tasks";
+/**
+ * Off-peak cron sample surfaced in the rendered documentation. Every
+ * 20 minutes during off-peak hours (before 08:00 and after 14:00
+ * local). Informational only — tasks ship disabled by default with
+ * no cron, so the consumer must opt in and set a cron explicitly.
+ *
+ * @see ScheduledTasksConfig
+ */
+declare const DEFAULT_OFF_PEAK_CRON_EXAMPLE = "3,23,43 0-7,14-23 * * *";
+/**
+ * A single fully-resolved scheduled-task entry. Returned by
+ * `resolveScheduledTasks()`; the rendered documentation section and
+ * the emitted `.claude/scheduled-tasks/<taskId>/SKILL.md` files are
+ * derived from this list.
+ */
+interface ResolvedScheduledTask {
+    /**
+     * Unique task directory name. Emitted under
+     * `<root>/<taskId>/SKILL.md`. Derived from the sub-agent name by
+     * default (e.g. `company-profile-analyst` → `worker-company-profile`).
+     */
+    readonly taskId: string;
     /**
-     * Resolves template variables in rule content using project metadata.
-     * Emits synthesis warnings for rules with unresolved variables.
+     * Target sub-agent name (e.g. `company-profile-analyst`). The task's
+     * rendered prompt points operators at `.claude/agents/<agent>.md`.
      */
-    private resolveTemplates;
+    readonly agent: string;
     /**
-     * Resolves template variables in skill instructions using project metadata.
+     * Human-readable agent label for rendered tables and frontmatter
+     * descriptions (e.g. `"Company Profile"`).
      */
-    private resolveSkillTemplates;
+    readonly agentLabel: string;
     /**
-     * Resolves template variables in sub-agent prompts using project metadata.
+     * Primary GitHub `type:*` label (without the `type:` prefix). When
+     * `typeLabels` is unset, this is the sole type filter; when
+     * `typeLabels` is set, it is the first element.
      */
-    private resolveSubAgentTemplates;
+    readonly typeLabel: string;
     /**
-     * Resolves template variables in procedure content using project metadata.
+     * Exact `type:*` label values (without the `type:` prefix) the
+     * worker picks up. When set (length >= 1), represents a
+     * multi-type filter (e.g. routing-bucket `worker-issue`). When
+     * unset, the `typeLabel` single-value filter applies.
      */
-    private resolveProcedureTemplates;
+    readonly typeLabels?: ReadonlyArray<string>;
+    /**
+     * Optional phase-label prefix (e.g. `company:`). When present and
+     * `phaseLabels` is unset, the task's SKILL.md instructs the worker
+     * to filter on both `type:<typeLabel>` **and** any `<phasePrefix>*`
+     * label. Ignored when `phaseLabels` is set.
+     */
+    readonly phasePrefix?: string;
+    /**
+     * Exact phase-label values the worker filters on (e.g.
+     * `["req:write"]`). When set (length >= 1), takes precedence over
+     * `phasePrefix`. When unset, the `phasePrefix` prefix-match
+     * applies.
+     */
+    readonly phaseLabels?: ReadonlyArray<string>;
+    /**
+     * Recommended model tier. Surfaced on the task's SKILL.md
+     * frontmatter and in the rendered documentation table.
+     */
+    readonly recommendedModel: ScheduledTaskModel;
+    /** Whether the task is emitted to disk. Default: `false`. */
+    readonly enabled: boolean;
+    /**
+     * Optional cron expression. When `null` the task is manual-only
+     * (runs only when an operator invokes it explicitly).
+     */
+    readonly cron: string | null;
+    /**
+     * Short one-line description for the rendered table and SKILL.md
+     * frontmatter.
+     */
+    readonly description: string;
+}
+/**
+ * Canonical default registry of scheduled-task entries. One entry per
+ * agent bundle that ships with configulator. Every entry is
+ * **disabled by default** — consumers must explicitly opt in via
+ * `ScheduledTasksConfig.overrides[taskId].enabled = true`.
+ *
+ * The registry mirrors the funnel-tier table in `tiers.ts` so the
+ * dispatch ordering, scheduled-task filter, and orchestrator queue
+ * scan all agree on the type-label taxonomy.
+ */
+declare const DEFAULT_SCHEDULED_TASK_ENTRIES: ReadonlyArray<ResolvedScheduledTask>;
+/**
+ * Fully-resolved scheduled-tasks settings. Every field is defaulted so
+ * downstream renderers can reason about a single canonical shape.
+ */
+interface ResolvedScheduledTasks {
+    readonly enabled: boolean;
+    readonly root: string;
+    readonly tasks: ReadonlyArray<ResolvedScheduledTask>;
+}
+/**
+ * Resolve a (possibly absent) `ScheduledTasksConfig` into a canonical
+ * `ResolvedScheduledTasks` with every field filled in. Unset fields
+ * cascade from their documented defaults.
+ *
+ * The resolver merges three sources in this order:
+ *
+ * 1. `DEFAULT_SCHEDULED_TASK_ENTRIES` — the built-in per-agent registry.
+ * 2. `config.overrides` — per-task consumer overrides keyed by `taskId`.
+ * 3. `config.tasks` — fully consumer-authored entries. Entries whose
+ *    `taskId` matches a default entry **replace** it; entries with a new
+ *    `taskId` are appended.
+ *
+ * Malformed configs (unknown model, empty taskId/agent/typeLabel,
+ * duplicate taskIds in a single supplied list) throw a descriptive
+ * `Error` — callers should not need to guard against it at runtime.
+ */
+declare function resolveScheduledTasks(config?: ScheduledTasksConfig): ResolvedScheduledTasks;
+/**
+ * Synth-time validation hook. Throws a descriptive `Error` when the
+ * supplied `ScheduledTasksConfig` is malformed. Called by
+ * `AgentConfig.preSynthesize` before any rendering so a misconfigured
+ * scheduled-tasks table fails the build instead of silently shipping
+ * broken worker prompts. Returns the resolved config unchanged so
+ * callers can write `const st = validateScheduledTasksConfig(config)` in
+ * one line.
+ *
+ * Malformed cases rejected here:
+ *
+ * - `root` empty, whitespace-only, or absolute.
+ * - `overrides[taskId]` referencing an unknown `taskId`.
+ * - Consumer-supplied `tasks` entry with unknown model, empty
+ *   `taskId` / `agent` / `typeLabel`, or cron string that is not a
+ *   plain string.
+ * - Duplicate `taskId` values within the supplied `tasks` list.
+ */
+declare function validateScheduledTasksConfig(config?: ScheduledTasksConfig): ResolvedScheduledTasks;
+/**
+ * Render the markdown subsection appended to the
+ * `orchestrator-conventions` rule. Always returns a non-empty string —
+ * the default registry is non-empty so the section documents the
+ * per-agent scheduled-task layout even when every task is disabled
+ * (the default).
+ */
+declare function renderScheduledTasksSection(resolved: ResolvedScheduledTasks): string;
+/**
+ * Render the body of a single scheduled-task `SKILL.md` file. The
+ * frontmatter carries the task name, description, and recommended
+ * model; the body teaches the worker which label filter to apply and
+ * which agent file to route issues to.
+ *
+ * The output is the full file contents — including the leading
+ * frontmatter delimiter — so callers can hand it straight to a
+ * `TextFile`.
+ */
+declare function renderScheduledTaskSkillFile(task: ResolvedScheduledTask): string;
+
+/**
+ * Classified scope size for a single issue. Drives the dispatch
+ * decision in the orchestrator — `small` / `medium` are dispatched,
+ * `large` is rejected and decomposed.
+ */
+declare const SCOPE_CLASS_VALUES: readonly ["small", "medium", "large"];
+type ScopeClass = (typeof SCOPE_CLASS_VALUES)[number];
+/**
+ * Default acceptance-criteria thresholds — openhi's published
+ * heuristic. An issue with at most 3 acceptance-criteria checkboxes
+ * is `small`; at most 6 is `medium`; more than 6 is `large`.
+ */
+declare const DEFAULT_AC_THRESHOLDS: ScopeGateThresholds;
+/**
+ * Default sources thresholds — openhi's published heuristic. An
+ * issue with at most 2 listed sources is `small`; at most 5 is
+ * `medium`; more than 5 is `large`.
+ */
+declare const DEFAULT_SOURCES_THRESHOLDS: ScopeGateThresholds;
+/**
+ * Default decomposition-proposal comment body. The orchestrator
+ * substitutes the following angle-bracketed uppercase-snake
+ * placeholders at comment-composition time:
+ *
+ * - `<AC_COUNT>` — observed acceptance-criteria count.
+ * - `<SOURCES_COUNT>` — observed sources count.
+ * - `<AC_LIMIT>` — the `acceptanceCriteria.mediumMax` threshold.
+ * - `<SOURCES_LIMIT>` — the `sources.mediumMax` threshold.
+ *
+ * The placeholder syntax deliberately avoids `{{curly-brace}}` form —
+ * `AgentConfig`'s template resolver claims that namespace at rule
+ * generation time, so a `{{acCount}}` placeholder would be rewritten
+ * to `<acCount>` before the agent ever saw it.
+ *
+ * This template is deliberately generic so every consuming repo
+ * can adopt it without customization — project-specific phrasing
+ * belongs in `ScopeGateConfig.decompositionTemplate`.
+ */
+declare const DEFAULT_DECOMPOSITION_TEMPLATE: string;
+/**
+ * Fully-resolved scope-gate settings. Every field is defaulted so
+ * downstream renderers can reason about a single canonical shape.
+ */
+interface ResolvedScopeGate {
+    readonly enabled: boolean;
+    readonly acceptanceCriteria: ScopeGateThresholds;
+    readonly sources: ScopeGateThresholds;
+    readonly autoFile: boolean;
+    readonly decompositionTemplate: string;
+}
+/**
+ * Resolve a (possibly absent) `ScopeGateConfig` into a canonical
+ * `ResolvedScopeGate` with every field filled in. Unset fields
+ * cascade from their documented defaults.
+ *
+ * Malformed configs (negative or non-integer thresholds, inverted
+ * ranges) throw a descriptive `Error` — callers should not need to
+ * guard against it at runtime.
+ */
+declare function resolveScopeGate(config?: ScopeGateConfig): ResolvedScopeGate;
+/**
+ * Synth-time validation hook. Throws a descriptive `Error` when the
+ * supplied `ScopeGateConfig` is malformed. Called by
+ * `AgentConfig.preSynthesize` before any rendering so a misconfigured
+ * gate fails the build instead of silently shipping broken dispatch
+ * thresholds. Returns the resolved gate unchanged so callers can
+ * write `const gate = validateScopeGateConfig(config)` in one line.
+ *
+ * Malformed cases rejected here:
+ *
+ * - Threshold values that are negative or non-integer.
+ * - Threshold ranges where `mediumMax <= smallMax` (the gate would
+ *   never classify an issue as `medium`).
+ */
+declare function validateScopeGateConfig(config?: ScopeGateConfig): ResolvedScopeGate;
+/**
+ * Classify a raw issue body against a resolved scope gate. Returns
+ * the scope class and the observed counts so the orchestrator can
+ * embed them in the decomposition-proposal comment.
+ *
+ * The parser is deliberately tolerant:
+ *
+ * - Acceptance-criteria checkboxes — lines matching `- [ ]` or
+ *   `- [x]` (case-insensitive) under a `## Acceptance Criteria`
+ *   heading (or any heading whose normalized text equals
+ *   `acceptance criteria`). Stops at the next heading.
+ * - Sources — bullet list items (`- ` or `* `) under any of
+ *   `## Inputs`, `## References`, `## Sources` (case-insensitive).
+ *   Counts from every matching section are summed, so an issue
+ *   that uses both `## Inputs` and `## References` has its sources
+ *   counted across both.
+ *
+ * An issue with **no** `## Acceptance Criteria` section produces an
+ * `acCount` of 0 and is classified `small` on the AC axis. An issue
+ * body that's pure prose with no recognizable sections classifies
+ * `small` — the gate never rejects an issue it can't read.
+ */
+declare function classifyIssueScope(body: string, gate: ResolvedScopeGate): {
+    readonly scope: ScopeClass;
+    readonly acCount: number;
+    readonly sourcesCount: number;
+};
+/**
+ * Render the markdown subsection appended to the
+ * `orchestrator-conventions` rule. Always returns a non-empty string
+ * so the orchestrator rule documents the scope gate even when the
+ * consumer relies on the defaults.
+ */
+declare function renderScopeGateSection(gate: ResolvedScopeGate): string;
+/**
+ * Render a shell-script snippet embedded in `check-blocked.sh`. The
+ * snippet declares a `scope_of()` function that reads an issue body
+ * (passed as `$1`) and echoes one of `small` / `medium` / `large`.
+ * Orchestrator-side bash hooks call this function before dispatch.
+ *
+ * Returns the body of a shell function block (including the
+ * `scope_of()` wrapper) so the surrounding script can splice it
+ * inline at the exact indent level it wants.
+ */
+declare function renderScopeGateShellHelpers(gate: ResolvedScopeGate): string;
+
+/**
+ * Valid funnel-tier values. Lower numbers dispatch first when priority
+ * is tied. See `DEFAULT_AGENT_TIERS` for the role of each tier.
+ */
+declare const AGENT_TIER_VALUES: readonly [0, 1, 2, 3, 4];
+type AgentTier = (typeof AGENT_TIER_VALUES)[number];
+/**
+ * Human-readable role name for each funnel tier. Rendered into the
+ * orchestrator-conventions rule and surfaced in generated `PICK` lines
+ * so agents and humans can read the sort key at a glance.
+ */
+declare const AGENT_TIER_ROLES: Readonly<Record<AgentTier, string>>;
+/**
+ * A single resolved agent-type → tier mapping. Returned by
+ * `resolveAgentTiers()`; the rendered table in the orchestrator rule
+ * content and the lookup table embedded in `check-blocked.sh` are
+ * derived from this list.
+ */
+interface ResolvedAgentTier {
     /**
-     * Collects Claude permission entries from all active bundles.
+     * GitHub `type:*` label value (e.g. `"feat"`, `"research"`,
+     * `"company-profile"`). The leading `type:` prefix is **not** part
+     * of the stored value — it is added when the resolver stringifies
+     * the lookup table.
      */
-    private resolveBundlePermissions;
+    readonly type: string;
+    /** Funnel tier 0–4 (lower dispatches first on a priority tie). */
+    readonly tier: AgentTier;
+    /** Human-readable tier role (routing / research / profiles / synthesis / support). */
+    readonly role: string;
 }
-
 /**
- * Agenda bundle — enabled by default.
+ * Canonical default mapping of GitHub `type:*` label values to funnel
+ * tiers. Mirrors openhi's `DISPATCHER.md` Dispatch Table plus the
+ * taxonomy documented in the Group D epic (#414, issue #473).
  *
- * Consuming projects can disable it with
- * `excludeBundles: ["agenda"]`. `appliesWhen` always returns `true`
- * (peer-present assumption, same pattern as the other workflow
- * bundles).
+ * - **Tier 0 — routing.** Unblocks other work. Picked first on a
+ *   priority tie. Covers the issue-worker's own type labels
+ *   (`feat`, `fix`, `chore`, `refactor`, `docs`, `release`,
+ *   `hotfix`) plus classification-style labels (`plan`, `review`,
+ *   `adr`).
+ * - **Tier 1 — research.** Feeds downstream pipelines.
+ * - **Tier 2 — profiles.** Consumes research.
+ * - **Tier 3 — synthesis.** Produces deliverables.
+ * - **Tier 4 — support.** Important but not pipeline-critical.
  *
- * Provides a 2-phase pre-meeting agenda pipeline
- * (draft → finalize), complementing the post-meeting pipeline in
- * the `meeting-analysis` bundle. Ships a sub-agent, two user-
- * invocable skills (`/draft-agenda`, `/finalize-agenda`), and
- * `agenda:*` phase labels via the bundle `labels` mechanism so
- * consuming projects automatically pick up the label taxonomy
- * through the sync-labels workflow.
+ * Consumers extend or override this list via
+ * `AgentConfigOptions.tiers` (see `resolveAgentTiers`). Every
+ * registered agent type must resolve to exactly one tier; unmapped
+ * types fail synth-time validation.
+ */
+declare const DEFAULT_AGENT_TIERS: ReadonlyArray<ResolvedAgentTier>;
+/**
+ * Fallback tier applied to issues whose `type:*` label does not match
+ * any entry in the resolved tier table. Using tier 0 (routing) means
+ * an unclassified or newly-introduced issue is dispatched **before**
+ * lower-tier work on a priority tie, which matches the openhi
+ * dispatcher's "routing unblocks other work" rule. The synth-time
+ * validator still rejects **registered** custom types that omit a
+ * tier assignment — the fallback exists only for unknown labels
+ * encountered at runtime.
+ */
+declare const UNKNOWN_TYPE_FALLBACK_TIER: AgentTier;
+/**
+ * Resolve a (possibly absent) consumer-supplied `AgentTierConfig` into
+ * a deduplicated list of `ResolvedAgentTier` entries.
  *
- * Reuses the meeting-type taxonomy from
- * `AgentConfigOptions.meetings.meetingTypes` — the same table the
- * `meeting-analysis` bundle consumes for post-meeting extraction.
+ * Precedence:
+ *
+ * 1. `config.tiers` fully **replaces** the default list when supplied.
+ *    This is the escape hatch for repos that want a bespoke taxonomy.
+ * 2. `config.customTypes` entries **extend** whatever list is in play
+ *    (default or replacement). Later entries override earlier ones on
+ *    `type` collision, so consumer overrides win over defaults.
+ *
+ * @throws `Error` when any entry references a tier outside 0–4, when a
+ *         `type` is empty/whitespace, or when `config.tiers` is an
+ *         empty array (use omission to mean "keep the defaults").
  */
-declare const agendaBundle: AgentRuleBundle;
-
+declare function resolveAgentTiers(config?: AgentTierConfig): ReadonlyArray<ResolvedAgentTier>;
 /**
- * AWS CDK bundle — auto-detected when `aws-cdk-lib` is in dependencies.
+ * Synth-time validation hook. Throws a descriptive `Error` when the
+ * resolved tier list is malformed. Called by `AgentConfig` before
+ * rendering so a misconfigured `AgentTierConfig` fails the build
+ * instead of silently shipping broken sort keys.
+ *
+ * Malformed cases rejected here:
+ *
+ * - Duplicate `type` values **within** the same supplied list (the
+ *   resolver dedupes between the default list and `customTypes`, so
+ *   those collisions are fine; duplicates inside one list are not).
+ * - Tier values outside 0–4.
+ * - Empty or whitespace-only `type` strings.
+ *
+ * Returns the validated list unchanged so callers can write
+ * `const tiers = validateAgentTierConfig(config)` in one line.
  */
-declare const awsCdkBundle: AgentRuleBundle;
-
+declare function validateAgentTierConfig(config?: AgentTierConfig): ReadonlyArray<ResolvedAgentTier>;
 /**
- * Base bundle — always included unless `includeBaseRules: false`.
- * Contains project-overview, interaction-style, and general-conventions rules.
+ * Render the funnel-tier subsection appended to the
+ * `orchestrator-conventions` rule. Always returns a non-empty string
+ * because the default tier list is non-empty — the orchestrator
+ * always documents its sort order.
  */
-declare const baseBundle: AgentRuleBundle;
+declare function renderAgentTierSection(tiers: ReadonlyArray<ResolvedAgentTier>): string;
+/**
+ * Render a shell-script snippet that the `check-blocked.sh` procedure
+ * uses to look up a tier for a given `type:*` label. Emitted as a
+ * `case` statement so the generated script stays POSIX-shell
+ * compatible (no associative arrays).
+ *
+ * The function returns the body of a shell function, not the
+ * surrounding function wrapper, so bundle code can splice it inline
+ * at the exact indent level it wants.
+ */
+declare function renderAgentTierCaseStatement(tiers: ReadonlyArray<ResolvedAgentTier>): string;
 
 /**
- * BCM writer bundle — enabled by default for projects that adopt this
- * batch.
+ * Default for whether the unblock-dependents sweep runs at all. When
+ * the consumer omits `UnblockDependentsConfig`, the bundle ships with
+ * the sweep **enabled** so every `status:done` transition
+ * automatically propagates into the dependency graph.
  *
- * Consuming projects can disable it with `excludeBundles: ["bcm-writer"]`.
- * `appliesWhen` always returns `true` per this batch's directive that
- * bundles assume peers are present.
+ * @see UnblockDependentsConfig
+ */
+declare const DEFAULT_UNBLOCK_DEPENDENTS_ENABLED = true;
+/**
+ * Default comment body posted on a newly-unblocked issue. Variables
+ * are substituted at runtime by the `unblock-dependents.sh` script:
  *
- * Ships a single consolidated sub-agent (`bcm-writer`) with all 4 phase",
- * handlers in one prompt (outline, scaffold, context, connect), a
- * user-invocable skill (`/write-bcm`), and `type:bcm-document` plus
- * `bcm:*` phase labels.
+ * - `<CLOSED_ISSUE>` — the `#<n>` reference to the issue whose
+ *   closure triggered the sweep (e.g. `#123`).
  *
- * The bundle assumes the `people-profile`, `company-profile`, and
- * `research-pipeline` bundles are also enabled so Phase 4 can hand off
- * surfaced items via `people:research`, `company:research`, and
- * `research:scope` issues.
+ * The placeholder syntax deliberately avoids `{{curly-brace}}` form —
+ * `AgentConfig`'s template resolver claims that namespace at rule
+ * generation time, so a `{{closedIssue}}` placeholder would be
+ * rewritten before the agent ever saw it.
  */
-declare const bcmWriterBundle: AgentRuleBundle;
-
+declare const DEFAULT_UNBLOCK_COMMENT_TEMPLATE = "Dependencies resolved by <CLOSED_ISSUE> \u2014 unblocking.";
 /**
- * Business-models bundle — enabled by default.
+ * Default comment body posted on a dependent whose other dependencies
+ * are still open (partial unblock). Variables substituted at runtime:
  *
- * Consuming projects can disable it with
- * `excludeBundles: ["business-models"]`. `appliesWhen` always returns
- * `true` per the workflow-bundle peer-present assumption.
+ * - `<CLOSED_ISSUE>` — the just-closed issue (`#<n>`).
+ * - `<OPEN_DEPS>` — space-separated list of remaining open
+ *   dependencies (e.g. `#45 #47`).
  *
- * Ships a sub-agent (`business-models-analyst`), three user-invocable
- * skills (`/scan-business-models`, `/canvas-business-model`,
- * `/complete-business-model`), a canvas template (emitted alongside
- * the canvas skill), and `type:business-model` plus
- * `business-models:*` phase labels.
+ * Applied when `flagPartialUnblockWithAttention` is `true`; otherwise
+ * no comment is posted and the dependent is left untouched.
+ */
+declare const DEFAULT_PARTIAL_UNBLOCK_COMMENT_TEMPLATE = "Dependency <CLOSED_ISSUE> resolved, but still waiting on: <OPEN_DEPS>.";
+/**
+ * Fully-resolved unblock-dependents settings. Every field is defaulted
+ * so downstream renderers can reason about a single canonical shape.
+ */
+interface ResolvedUnblockDependents {
+    readonly enabled: boolean;
+    readonly commentTemplate: string;
+    readonly flagPartialUnblockWithAttention: boolean;
+    readonly partialUnblockCommentTemplate: string;
+}
+/**
+ * Resolve a (possibly absent) `UnblockDependentsConfig` into a canonical
+ * `ResolvedUnblockDependents` with every field filled in. Unset fields
+ * cascade from their documented defaults.
  *
- * The bundle sits between `industry-discovery` (upstream, selects
- * verticals) and `bcm-writer` (downstream, models capabilities). It
- * assumes `bcm-writer` is enabled so Phase 3 can hand off surfaced
- * capabilities via `bcm:outline` issues, and it is read by
- * `company-profile` via the shared `<BUSINESS_MODELS_ROOT>` default
- * path (`docs/src/content/docs/industry-research/`).
+ * Malformed configs (empty / whitespace-only `commentTemplate`) throw
+ * a descriptive `Error` — callers should not need to guard against it
+ * at runtime.
  */
-declare const businessModelsBundle: AgentRuleBundle;
+declare function resolveUnblockDependents(config?: UnblockDependentsConfig): ResolvedUnblockDependents;
+/**
+ * Synth-time validation hook. Throws a descriptive `Error` when the
+ * supplied `UnblockDependentsConfig` is malformed. Called by
+ * `AgentConfig.preSynthesize` before any rendering so a misconfigured
+ * sweep fails the build instead of silently shipping a broken
+ * procedure script. Returns the resolved config unchanged so callers
+ * can write `const ud = validateUnblockDependentsConfig(config)` in
+ * one line.
+ *
+ * Malformed cases rejected here:
+ *
+ * - `commentTemplate` empty or whitespace-only.
+ * - `partialUnblockCommentTemplate` empty or whitespace-only.
+ */
+declare function validateUnblockDependentsConfig(config?: UnblockDependentsConfig): ResolvedUnblockDependents;
+/**
+ * Render the markdown subsection appended to the
+ * `orchestrator-conventions` rule. Always returns a non-empty string
+ * so the orchestrator rule documents the contract even when the
+ * consumer relies on the defaults.
+ */
+declare function renderUnblockDependentsSection(ud: ResolvedUnblockDependents): string;
+/**
+ * Render the full `unblock-dependents.sh` script body for a given
+ * resolved unblock-dependents config. The script takes a single
+ * positional argument (the just-closed issue number) and emits one
+ * line per processed dependent in the canonical
+ * `UNBLOCKED` / `STILL_BLOCKED` / `NO_DEPENDENTS` format.
+ *
+ * Exported so `AgentConfig.preSynthesize` can emit the procedure
+ * alongside `check-blocked.sh`.
+ */
+declare function renderUnblockDependentsScript(ud: ResolvedUnblockDependents): string;
+
+/**
+ * Build the check-blocked.sh procedure definition for a given resolved
+ * tier table, scope gate, run-ratio, and pre-flight config.
+ * `AgentConfig.preSynthesize` calls this with the consumer's resolved
+ * configs so the emitted script's `tier_of()` lookup, `scope_of()`
+ * thresholds, `run_counter_tick()` cycle length, and `cmd_preflight()`
+ * eligibility filter match whatever the rendered
+ * orchestrator-conventions rule documents.
+ *
+ * Scope-gate settings default to the bundle's built-in defaults
+ * (small: ≤3 AC + ≤2 sources; medium: ≤6 AC + ≤5 sources;
+ * auto-file off) when the caller omits them. Run-ratio settings
+ * default to the openhi 4:1 cadence with the counter persisted at
+ * `.claude/state/orchestrator-runs.json`. Pre-flight settings default
+ * to vortex's step 0b contract (enabled, delegated to the
+ * `pr-reviewer` sub-agent, squash merges, linked-issue keyword
+ * required).
+ */
+declare function buildCheckBlockedProcedure(tiers: ReadonlyArray<ResolvedAgentTier>, scopeGate?: ResolvedScopeGate, runRatio?: ResolvedRunRatio, preflight?: ResolvedPreflightPr): AgentProcedure;
+/*******************************************************************************
+ *
+ * unblock-dependents.sh — Targeted post-close dependency sweep.
+ *
+ * Called by every agent that applies `status:done` to an issue. The
+ * script searches open issues for `Depends on: #<just-closed>` and
+ * flips fully-resolved dependents from `status:blocked` to
+ * `status:ready`.
+ *
+ * `buildUnblockDependentsProcedure()` is the factory that parameterises
+ * the rendered script with a resolved `ResolvedUnblockDependents`;
+ * `unblockDependentsProcedure` (declared below) is the default
+ * instance that ships when the consumer supplies no override.
+ *
+ ******************************************************************************/
+declare function buildUnblockDependentsProcedure(unblockDependents?: ResolvedUnblockDependents): AgentProcedure;
+/**
+ * Build the orchestrator-conventions rule content for a given resolved
+ * tier table, scope gate, run-ratio, pre-flight, scheduled-tasks, and
+ * unblock-dependents config. The preamble is constant; each section
+ * below it is rendered from the supplied values so consumer overrides
+ * propagate into the generated rule.
+ *
+ * Every optional parameter defaults to the bundle's built-in default
+ * when the caller omits it.
+ */
+declare function buildOrchestratorConventionsContent(tiers: ReadonlyArray<ResolvedAgentTier>, scopeGate?: ResolvedScopeGate, runRatio?: ResolvedRunRatio, preflight?: ResolvedPreflightPr, scheduledTasks?: ResolvedScheduledTasks, unblockDependents?: ResolvedUnblockDependents): string;
+/**
+ * Resolve the orchestrator-conventions rule content and the
+ * check-blocked.sh procedure content for a given (possibly absent)
+ * consumer-supplied tier config, scope-gate config, run-ratio config,
+ * pre-flight config, and scheduled-tasks config. Called by
+ * `AgentConfig.preSynthesize`.
+ *
+ * Returns the resolved tier table, scope gate, run ratio, pre-flight,
+ * and scheduled-tasks config alongside both rendered artifacts so
+ * callers can splice them into their rule map and procedure map in a
+ * single pass.
+ */
+declare function resolveOrchestratorAssets(tierConfig?: AgentTierConfig, scopeGateConfig?: ScopeGateConfig, runRatioConfig?: RunRatioConfig, preflightPrConfig?: PreflightPrConfig, scheduledTasksConfig?: ScheduledTasksConfig, unblockDependentsConfig?: UnblockDependentsConfig): {
+    readonly tiers: ReadonlyArray<ResolvedAgentTier>;
+    readonly scopeGate: ResolvedScopeGate;
+    readonly runRatio: ResolvedRunRatio;
+    readonly preflight: ResolvedPreflightPr;
+    readonly scheduledTasks: ResolvedScheduledTasks;
+    readonly unblockDependents: ResolvedUnblockDependents;
+    readonly conventionsContent: string;
+    readonly procedure: AgentProcedure;
+    readonly unblockDependentsProcedure: AgentProcedure;
+};
+/*******************************************************************************
+ *
+ * Bundle definition
+ *
+ ******************************************************************************/
+declare const orchestratorBundle: AgentRuleBundle;
 
 /**
- * Company-profile bundle — enabled by default.
+ * People-profile bundle — enabled by default.
  *
  * Consuming projects can disable it with
- * `excludeBundles: ["company-profile"]`. `appliesWhen` always returns
+ * `excludeBundles: ["people-profile"]`. `appliesWhen` always returns
  * `true` per the operating-system directive that bundles assume peers
  * are present — in Phase 3 this bundle hands work off to
- * `people-profile` (via `people:research`) and `software-profile` (via
- * `software:research`).
+ * `company-profile` (via `company:research`) and `software-profile`
+ * (via `software:research`).
  *
- * Ships a sub-agent (`company-profile-analyst`), four user-invocable
- * skills (`/profile-company`, `/match-company`, `/refresh-company`,
- * `/analyze-segment`), and `type:company-profile` plus `company:*`
- * phase labels for the six phases.
+ * Ships a sub-agent (`people-profile-analyst`), two user-invocable
+ * skills (`/profile-person`, `/refresh-person`), and `type:people-profile`
+ * plus `people:*` phase labels for the four phases.
  */
-declare const companyProfileBundle: AgentRuleBundle;
+declare function buildPeopleProfileBundle(paths?: ResolvedAgentPaths): AgentRuleBundle;
+/**
+ * Default-paths instance of the people-profile bundle, preserved for
+ * backward compatibility with consumers that import the const
+ * directly. The factory above is the canonical entry point when a
+ * consumer supplies `AgentConfigOptions.paths`.
+ */
+declare const peopleProfileBundle: AgentRuleBundle;
 
 /**
- * GitHub workflow bundle — auto-detected when the project has a GitHub component.
+ * PNPM bundle — auto-detected when the PnpmWorkspace component is present.
  */
-declare const githubWorkflowBundle: AgentRuleBundle;
+declare const pnpmBundle: AgentRuleBundle;
 
 /**
- * Industry-discovery bundle — enabled by default.
+ * Default master switch for the issue-templates convention. When no
+ * config is supplied the convention ships **enabled** so every
+ * configulator-consuming repo carries the canonical `gh issue create`
+ * template reference in its rendered `CLAUDE.md`.
  *
- * Consuming projects can disable it with
- * `excludeBundles: ["industry-discovery"]`. `appliesWhen` always returns
- * `true` per this batch's directive that bundles assume peers are
- * present.
+ * @see IssueTemplatesConfig
+ */
+declare const DEFAULT_ISSUE_TEMPLATES_ENABLED = true;
+/**
+ * Default repo-relative path for the consolidated issue-templates
+ * documentation page. Matches the singleton `/docs` site layout every
+ * configulator-managed repo ships: a single Starlight docs site at
+ * `/docs` with agent reference pages under
+ * `docs/src/content/docs/agents/`.
  *
- * Ships a sub-agent (`industry-discovery-analyst`), a user-invocable
- * skill (`/discover-industries`), and `type:industry-discovery` plus
- * `industry:*` phase labels.
+ * The file is never generated by configulator unless `emitStarterDoc`
+ * is set — the canonical list of templates is repo-specific and grows
+ * whenever a new phase label is minted, so consumers author and evolve
+ * the page themselves. The starter doc is opt-in.
  *
- * The bundle assumes the `research-pipeline` bundle is also enabled so
- * Phase 3 can hand off cleared verticals via `research:scope` issues.
+ * @see IssueTemplatesConfig
  */
-declare const industryDiscoveryBundle: AgentRuleBundle;
-
+declare const DEFAULT_ISSUE_TEMPLATES_PATH = "docs/src/content/docs/agents/issue-templates.md";
 /**
- * Jest bundle — auto-detected when Jest is in dependencies.
+ * Default list of glob patterns that identify "bundle files" — the
+ * source files that compose agent prompts and skill instructions.
+ * These are the locations the optional lint walks when checking that
+ * `gh issue create` snippets are **referenced** rather than inlined.
+ *
+ * The defaults cover the two canonical locations bundle-like content
+ * lives in a configulator-consuming repo:
+ *
+ * - `packages/@codedrifters/configulator/src/agent/bundles/**.ts` —
+ *   the bundle authoring sites inside configulator itself.
+ * - `.claude/agents/**.md` / `.claude/skills/**` — agent and skill
+ *   prompts in consuming repos that don't re-export configulator
+ *   bundles.
+ *
+ * Consumers can replace the list outright via `bundlePathPatterns`
+ * when their agent sources live elsewhere.
+ *
+ * @see IssueTemplatesConfig
  */
-declare const jestBundle: AgentRuleBundle;
-
+declare const DEFAULT_ISSUE_TEMPLATES_BUNDLE_PATH_PATTERNS: ReadonlyArray<string>;
 /**
- * Maintenance-audit bundle — enabled by default.
+ * Default for whether the convention emits the
+ * `.claude/procedures/check-issue-templates.sh` lint to disk. The
+ * script greps the provided files (stdin or positional args) for
+ * inline `gh issue create` invocations and fails non-zero when any
+ * are found outside a fenced example block that cites the canonical
+ * templates doc.
  *
- * Consuming projects can disable it with
- * `excludeBundles: ["maintenance-audit"]`. `appliesWhen` always returns
- * `true` per this batch's directive that bundles assume peers are
- * present.
+ * Disabled by default because many consumers prefer to enforce the
+ * rule via review discipline and the rendered guidance alone; the
+ * script is opt-in for repos that want a hard CI gate or pre-commit
+ * hook.
  *
- * Provides a 3-phase documentation-maintenance pipeline
- * (scan → fix → verify) designed for any project with structured doc
- * registries and cross-references. Ships a sub-agent, two user-
- * invocable skills (`/audit-docs`, `/verify-audit`), and `maint:*`
- * phase labels via the bundle `labels` mechanism so consuming projects
- * automatically pick up the label taxonomy through the sync-labels
- * workflow.
+ * @see IssueTemplatesConfig
  */
-declare const maintenanceAuditBundle: AgentRuleBundle;
-
+declare const DEFAULT_ISSUE_TEMPLATES_EMIT_CHECKER = false;
 /**
- * Meeting analysis bundle — included by default.
- * Provides a 4-phase meeting transcript processing workflow.
+ * Default for whether the convention emits a minimal starter
+ * issue-templates page to disk at `<templatesPath>`. The starter
+ * carries the expected structure (one `## Template: <phase-label>`
+ * heading per known phase plus a placeholder body) so consumers
+ * adopting the convention on a green-field repo have a working
+ * template to extend.
+ *
+ * Disabled by default because the page is hand-authored and most
+ * repos adopt the convention after they already maintain their own
+ * ad-hoc notes — an emitted stub would conflict with existing
+ * content.
+ *
+ * @see IssueTemplatesConfig
  */
-declare const meetingAnalysisBundle: AgentRuleBundle;
-
-/*******************************************************************************
+declare const DEFAULT_ISSUE_TEMPLATES_EMIT_STARTER = false;
+/**
+ * Default for whether the rendered rule body asserts that every
+ * `gh issue create` recipe in a bundle or agent prompt **MUST** cite
+ * the canonical templates doc rather than inline a full template.
  *
- * Bundle definition
+ * Defaults to `true` — the whole point of consolidation is that
+ * templates live in one place, so the MUST phrasing is the correct
+ * default. Consumers that treat consolidation as aspirational can
+ * soften the phrasing by setting this to `false`.
  *
- ******************************************************************************/
-declare const orchestratorBundle: AgentRuleBundle;
+ * @see IssueTemplatesConfig
+ */
+declare const DEFAULT_ISSUE_TEMPLATES_REQUIRE_REFERENCE = true;
+/**
+ * Fully-resolved issue-templates settings. Every field is defaulted
+ * so downstream renderers can reason about a single canonical shape.
+ */
+interface ResolvedIssueTemplates {
+    readonly enabled: boolean;
+    readonly templatesPath: string;
+    readonly bundlePathPatterns: ReadonlyArray<string>;
+    readonly emitChecker: boolean;
+    readonly emitStarterDoc: boolean;
+    readonly requireReference: boolean;
+}
+/**
+ * Resolve a (possibly absent) `IssueTemplatesConfig` into a canonical
+ * `ResolvedIssueTemplates` with every field filled in. Unset fields
+ * cascade from their documented defaults.
+ *
+ * Malformed configs — empty / whitespace-only or absolute
+ * `templatesPath`, empty `bundlePathPatterns`, empty /
+ * whitespace-only path entry — throw a descriptive `Error`.
+ */
+declare function resolveIssueTemplates(config?: IssueTemplatesConfig): ResolvedIssueTemplates;
+/**
+ * Synth-time validation hook. Throws a descriptive `Error` when the
+ * supplied `IssueTemplatesConfig` is malformed. Called by
+ * `AgentConfig.preSynthesize` before any rendering so a misconfigured
+ * convention fails the build instead of silently shipping broken
+ * guidance. Returns the resolved config unchanged so callers can
+ * write `const it = validateIssueTemplatesConfig(config)` in one line.
+ *
+ * Malformed cases rejected here:
+ *
+ * - `templatesPath` empty, whitespace-only, or absolute.
+ * - `bundlePathPatterns` not an array, empty, or contains an empty /
+ *   whitespace-only entry.
+ */
+declare function validateIssueTemplatesConfig(config?: IssueTemplatesConfig): ResolvedIssueTemplates;
+/**
+ * Render the full body for the `issue-templates-convention` rule
+ * shipped by the `base` bundle. The rule documents:
+ *
+ * - Why the convention exists (drift between duplicated
+ *   `gh issue create` snippets across bundles).
+ * - The on-disk contract — a single hand-authored page at
+ *   `<templatesPath>` with one `## Template: <phase-label>` section
+ *   per downstream issue kind.
+ * - The **reference-don't-inline** rule, phrased as a hard
+ *   requirement or a strong recommendation per `requireReference`.
+ * - The set of paths the rule applies to.
+ * - The optional lint script (cross-referenced only when emitted).
+ *
+ * When the convention is disabled, the rule renders a short stub.
+ */
+declare function renderIssueTemplatesRuleContent(it: ResolvedIssueTemplates): string;
+/**
+ * Render the short issue-templates hook section injected into a
+ * phased-agent bundle's workflow rule. The section cites the full
+ * contract documented in the base bundle's
+ * `issue-templates-convention` rule so individual bundles stay DRY.
+ *
+ * When the convention is disabled, the function returns an empty
+ * string so callers can no-op their append path.
+ */
+declare function renderIssueTemplatesBundleHook(it: ResolvedIssueTemplates, bundleLabel: string): string;
+/**
+ * Render a minimal starter issue-templates page — a top-level
+ * heading, the "How to use" preamble, and a single example template
+ * section. Exported so `AgentConfig` can emit it to disk when the
+ * consumer opts in via `emitStarterDoc: true`.
+ *
+ * The starter is deliberately sparse: it documents the expected
+ * structure without committing the consumer to a particular phase
+ * label list. Repos that already maintain a hand-authored templates
+ * page should leave `emitStarterDoc` off — the emission would
+ * overwrite their content.
+ */
+declare function renderIssueTemplatesStarterPage(_it: ResolvedIssueTemplates): string;
+/**
+ * Render the `.claude/procedures/check-issue-templates.sh` helper
+ * script. Exported so `AgentConfig` can register it as an
+ * `AgentProcedure` when the consumer opts in via `emitChecker: true`.
+ *
+ * The script accepts the list of changed files as either:
+ *
+ * 1. Positional arguments (one file per arg).
+ * 2. Newline-separated entries on stdin (when no args supplied) —
+ *    pipe `git diff --name-only` directly into it.
+ *
+ * It fails non-zero when any changed file matches a bundle-path
+ * pattern and contains a multi-line `gh issue create ... --title`
+ * invocation that isn't in the configured allow list (the templates
+ * page itself and the `create-issue-workflow` rule source).
+ */
+declare function renderIssueTemplatesCheckerScript(it: ResolvedIssueTemplates): string;
 
 /**
- * Fully-resolved agent output-path roots. Every property is required.
+ * Default master switch for the progress-file convention. When no
+ * config is supplied, the convention ships **enabled** so every phased
+ * agent writes a progress file on claim and reads it on resume.
  *
- * This is the shape that bundle code consumes at module-eval time via
- * `DEFAULT_AGENT_PATHS`, and the shape that `resolveAgentPaths()`
- * returns when consumers supply a partial `AgentPathsConfig` override.
+ * @see ProgressFilesConfig
  */
-interface ResolvedAgentPaths {
-    readonly docsRoot: string;
-    readonly researchRoot: string;
-    readonly profilesRoot: string;
-    readonly meetingsRoot: string;
-    readonly requirementsRoot: string;
-    readonly researchRequirementsRoot: string;
-    readonly bcmRoot: string;
-    readonly peopleRoot: string;
-    readonly companiesRoot: string;
-    readonly softwareRoot: string;
-    readonly industriesRoot: string;
+declare const DEFAULT_PROGRESS_FILES_ENABLED = true;
+/**
+ * Default on-disk root for progress files, relative to the repo root.
+ * Every progress file resolves to
+ * `<stateDir>/<filename>` where `<filename>` is produced from
+ * `filenamePattern` at runtime.
+ *
+ * @see ProgressFilesConfig
+ */
+declare const DEFAULT_PROGRESS_FILES_STATE_DIR = ".claude/state";
+/**
+ * Default filename pattern for a progress file. The `<ISSUE_NUMBER>`
+ * placeholder is substituted at runtime with the numeric id of the
+ * issue the agent is working on (e.g. `479-progress.json`).
+ *
+ * The placeholder uses the angle-bracketed uppercase-snake form — not
+ * `{{curly-brace}}` form — because `AgentConfig`'s template resolver
+ * claims the curly-brace namespace at rule generation time.
+ *
+ * @see ProgressFilesConfig
+ */
+declare const DEFAULT_PROGRESS_FILES_FILENAME_PATTERN = "<ISSUE_NUMBER>-progress.json";
+/**
+ * Default serialization format for a progress file body. JSON is the
+ * default because it is trivially machine-parseable (e.g. for scripted
+ * resume logic) while still remaining human-readable when opened.
+ * Consumers that prefer the openhi-style markdown body can override.
+ *
+ * @see ProgressFilesConfig
+ */
+declare const DEFAULT_PROGRESS_FILES_FORMAT: "json" | "markdown";
+/**
+ * Default stale-threshold (hours) for branches carrying a progress
+ * file. When the orchestrator's stale-branch decision tree finds a
+ * progress file older than this many hours **and** no matching open
+ * PR, it treats the branch as abandoned and resets the issue to
+ * `status:ready`. Mirrors the 72-hour in-progress threshold used by
+ * the orchestrator bundle's triage walk.
+ *
+ * @see ProgressFilesConfig
+ */
+declare const DEFAULT_PROGRESS_FILES_STALE_AFTER_HOURS = 72;
+/**
+ * Allowed values for `ProgressFilesConfig.format`. Exported so
+ * consumers can reference the canonical set without hard-coding
+ * literals.
+ */
+declare const PROGRESS_FILES_FORMAT_VALUES: readonly ["json", "markdown"];
+/**
+ * Fully-resolved progress-file settings. Every field is defaulted so
+ * downstream renderers can reason about a single canonical shape.
+ */
+interface ResolvedProgressFiles {
+    readonly enabled: boolean;
+    readonly stateDir: string;
+    readonly filenamePattern: string;
+    readonly format: "json" | "markdown";
+    readonly cleanupOnComplete: boolean;
+    readonly staleAfterHours: number;
 }
 /**
- * Canonical default values for every agent path. These mirror the
- * hardcoded paths that bundles used before `AgentPathsConfig` existed,
- * so `DEFAULT_AGENT_PATHS.*` can be substituted into bundle rule
- * content at module-eval time without changing the generated
- * `.claude/rules/*.md` snapshot.
+ * Resolve a (possibly absent) `ProgressFilesConfig` into a canonical
+ * `ResolvedProgressFiles` with every field filled in. Unset fields
+ * cascade from their documented defaults.
  *
- * Consumers override the defaults by passing an `AgentPathsConfig`
- * through `AgentConfigOptions.paths` and resolving it with
- * `resolveAgentPaths()`. Per-project propagation into bundle rule
- * content is a follow-up — this export is the first step: interface +
- * resolver land in this PR; the `AgentConfig.resolveRules` wiring lands
- * next.
+ * Malformed configs — empty / whitespace-only `stateDir`, absolute
+ * `stateDir`, empty / whitespace-only `filenamePattern`, `filenamePattern`
+ * missing the `<ISSUE_NUMBER>` placeholder, unknown `format` value,
+ * non-positive `staleAfterHours` — throw a descriptive `Error`.
  */
-declare const DEFAULT_AGENT_PATHS: ResolvedAgentPaths;
+declare function resolveProgressFiles(config?: ProgressFilesConfig): ResolvedProgressFiles;
 /**
- * Resolve a partial `AgentPathsConfig` into a fully-populated
- * `ResolvedAgentPaths`. Unset fields cascade from their parent root:
+ * Synth-time validation hook. Throws a descriptive `Error` when the
+ * supplied `ProgressFilesConfig` is malformed. Called by
+ * `AgentConfig.preSynthesize` before any rendering so a misconfigured
+ * convention fails the build instead of silently shipping broken
+ * resume semantics. Returns the resolved config unchanged so callers
+ * can write `const pf = validateProgressFilesConfig(config)` in
+ * one line.
+ *
+ * Malformed cases rejected here:
+ *
+ * - `stateDir` empty, whitespace-only, or absolute.
+ * - `filenamePattern` empty, whitespace-only, or missing the
+ *   `<ISSUE_NUMBER>` placeholder.
+ * - `format` not one of `"json"` / `"markdown"`.
+ * - `staleAfterHours` non-integer, zero, or negative.
+ */
+declare function validateProgressFilesConfig(config?: ProgressFilesConfig): ResolvedProgressFiles;
+/**
+ * Resolve the runtime filename for a progress file given an issue
+ * number and a resolved config. `<ISSUE_NUMBER>` placeholders in the
+ * pattern are substituted; the returned value is **just** the filename
+ * (no directory prefix).
  *
- * - `profilesRoot`, `meetingsRoot`, `requirementsRoot`, and `bcmRoot`
- *   derive from `docsRoot` when not explicitly set.
- * - `researchRequirementsRoot` derives from `researchRoot` when not
- *   explicitly set.
- * - `peopleRoot`, `companiesRoot`, `softwareRoot`, and `industriesRoot`
- *   derive from the resolved `profilesRoot` when not explicitly set,
- *   so that overriding `docsRoot` alone (or overriding `profilesRoot`
- *   alone) propagates correctly through every dependent root.
+ * Exported so consumer-side scripts (or the `partial-resume-protocol`
+ * rule renderer) can compute the on-disk path deterministically.
  */
-declare function resolveAgentPaths(paths?: AgentPathsConfig): ResolvedAgentPaths;
-
+declare function renderProgressFileName(pf: ResolvedProgressFiles, issueNumber: number | string): string;
 /**
- * People-profile bundle — enabled by default.
+ * Resolve the runtime path (directory + filename) for a progress file
+ * given an issue number and a resolved config.
+ */
+declare function renderProgressFilePath(pf: ResolvedProgressFiles, issueNumber: number | string): string;
+/**
+ * Render the full body for the `progress-file-convention` rule shipped
+ * by the `base` bundle. The rule documents:
  *
- * Consuming projects can disable it with
- * `excludeBundles: ["people-profile"]`. `appliesWhen` always returns
- * `true` per the operating-system directive that bundles assume peers
- * are present — in Phase 3 this bundle hands work off to
- * `company-profile` (via `company:research`) and `software-profile`
- * (via `software:research`).
+ * - The progress-file schema and on-disk path contract.
+ * - The partial-resume protocol (read-before-write + acceptance
+ *   criteria replay).
+ * - The stale-branch decision tree (clone-level recovery) that every
+ *   worker runs at session start.
+ * - The `[BLOCKED]` structured comment format used when an agent
+ *   cannot proceed.
  *
- * Ships a sub-agent (`people-profile-analyst`), two user-invocable
- * skills (`/profile-person`, `/refresh-person`), and `type:people-profile`
- * plus `people:*` phase labels for the four phases.
+ * When the convention is disabled, the rule renders a short stub that
+ * tells agents the project does not enforce progress files and they
+ * must pick up work from scratch on every session.
  */
-declare const peopleProfileBundle: AgentRuleBundle;
-
+declare function renderProgressFilesRuleContent(pf: ResolvedProgressFiles): string;
 /**
- * PNPM bundle — auto-detected when the PnpmWorkspace component is present.
+ * Render the short progress-file hook section injected into a
+ * phased-agent bundle's workflow rule (bcm-writer, research-pipeline,
+ * etc.). The section cites the full contract documented in the base
+ * bundle's `progress-file-convention` rule so individual bundles stay
+ * DRY.
+ *
+ * When the convention is disabled, the function returns an empty
+ * string so callers can no-op their append path.
  */
-declare const pnpmBundle: AgentRuleBundle;
+declare function renderProgressFilesBundleHook(pf: ResolvedProgressFiles, bundleLabel: string): string;
 
 /*******************************************************************************
  *
@@ -1961,6 +4668,36 @@ declare const prReviewBundle: AgentRuleBundle;
  */
 declare const projenBundle: AgentRuleBundle;
 
+/**
+ * Regulatory-research bundle — enabled by default.
+ *
+ * Consuming projects can disable it with
+ * `excludeBundles: ["regulatory-research"]`. `appliesWhen` always
+ * returns `true` per the workflow-bundle peer-present assumption.
+ *
+ * Ships a sub-agent (`regulatory-research-analyst`), three
+ * user-invocable skills (`/scan-regulatory-landscape`,
+ * `/research-regulation`, `/impact-regulation`), a regulation-page
+ * template (emitted alongside the research skill), and
+ * `type:regulatory-research` plus `regulatory:*` phase labels.
+ *
+ * The bundle sits downstream of `research-pipeline`,
+ * `industry-discovery`, and `standards-research` (which surface the
+ * need for regulatory research) and hands off actionable obligations
+ * to the `requirements-analyst` bundle via `req:scan` issues that
+ * become SEC (security & compliance) requirements in the writer
+ * pipeline, and canonical profiles to `company-profile` and
+ * `people-profile` for enforcement bodies and regulatory leaders.
+ */
+declare function buildRegulatoryResearchBundle(paths?: ResolvedAgentPaths): AgentRuleBundle;
+/**
+ * Default-paths instance of the regulatory-research bundle, preserved
+ * for backward compatibility with consumers that import the const
+ * directly. The factory above is the canonical entry point when a
+ * consumer supplies `AgentConfigOptions.paths`.
+ */
+declare const regulatoryResearchBundle: AgentRuleBundle;
+
 /**
  * Inject domain-specific source-tier examples into the content of the
  * base bundle's "Source Quality & Verification" rule.
@@ -2060,15 +4797,481 @@ declare function renderMeetingTypesSection(meetings: MeetingsConfig | undefined)
 declare function renderPriorityRulesSection(rules: ReadonlyArray<PriorityRule>): string;
 
 /**
- * Requirements-analyst bundle — opt-in via `includeBundles: [\"requirements-analyst\"]`.
+ * Default master switch for the shared-editing convention. When no
+ * config is supplied, the convention ships **enabled** so every agent
+ * that edits an index file follows the single-entry / verify /
+ * re-sort protocol.
+ *
+ * @see SharedEditingConfig
+ */
+declare const DEFAULT_SHARED_EDITING_ENABLED = true;
+/**
+ * Default list of path patterns considered "shared index files". The
+ * patterns are plain glob strings rendered verbatim into the rule body
+ * — agents match against them when deciding whether the shared-editing
+ * contract applies to the file they are about to edit.
+ *
+ * The defaults cover the registry / index files every configulator
+ * consumer ships by convention:
+ *
+ * - A monorepo-wide docs site at `/docs` with one or more `index.md` /
+ *   `README.md` registry tables.
+ * - Category landing pages under `docs/src/content/docs/**` that list
+ *   every profile, requirement, or capability in their category.
+ * - Feature matrices produced by the `software-profile` bundle.
+ *
+ * Consumers can replace the list outright via `sharedIndexPaths` or
+ * append project-specific registries.
+ *
+ * @see SharedEditingConfig
+ */
+declare const DEFAULT_SHARED_INDEX_PATHS: ReadonlyArray<string>;
+/**
+ * Default conflict-resolution strategy rendered into the rule body.
+ * `rebase` matches the `git pull --rebase` workflow every
+ * configulator-managed repo already uses for feature branches; the
+ * alternative (`merge`) is documented for projects that keep a
+ * merge-commit-only history.
+ *
+ * @see SharedEditingConfig
+ */
+declare const DEFAULT_SHARED_EDITING_CONFLICT_STRATEGY: "rebase" | "merge";
+/**
+ * Default for whether the convention renders the commit-path
+ * verification protocol (read-back + single-row assertion). The
+ * verification step is cheap, catches staging / path bugs that would
+ * otherwise land on the branch, and is the core safety net the openhi
+ * reference promotes — so it ships **on** by default.
+ *
+ * @see SharedEditingConfig
+ */
+declare const DEFAULT_SHARED_EDITING_VERIFY_COMMIT = true;
+/**
+ * Default for whether the convention emits the
+ * `.claude/procedures/verify-index-row.sh` helper to disk. The helper
+ * is opt-in because many consumers prefer to do the verification
+ * inline via the documented `git show HEAD:<path>` recipe rather than
+ * shell out to a dedicated script. Consumers that want the script
+ * available to sub-agents enable the emission explicitly.
+ *
+ * @see SharedEditingConfig
+ */
+declare const DEFAULT_SHARED_EDITING_EMIT_HELPER = false;
+/**
+ * Allowed values for `SharedEditingConfig.conflictStrategy`. Exported
+ * so consumers can reference the canonical set without hard-coding
+ * literals.
+ */
+declare const SHARED_EDITING_CONFLICT_STRATEGY_VALUES: readonly ["rebase", "merge"];
+/**
+ * Fully-resolved shared-editing settings. Every field is defaulted so
+ * downstream renderers can reason about a single canonical shape.
+ */
+interface ResolvedSharedEditing {
+    readonly enabled: boolean;
+    readonly sharedIndexPaths: ReadonlyArray<string>;
+    readonly verifyCommit: boolean;
+    readonly conflictStrategy: "rebase" | "merge";
+    readonly emitHelper: boolean;
+}
+/**
+ * Resolve a (possibly absent) `SharedEditingConfig` into a canonical
+ * `ResolvedSharedEditing` with every field filled in. Unset fields
+ * cascade from their documented defaults.
+ *
+ * Malformed configs — empty / whitespace-only `sharedIndexPaths`
+ * entry, unknown `conflictStrategy` — throw a descriptive `Error`.
+ */
+declare function resolveSharedEditing(config?: SharedEditingConfig): ResolvedSharedEditing;
+/**
+ * Synth-time validation hook. Throws a descriptive `Error` when the
+ * supplied `SharedEditingConfig` is malformed. Called by
+ * `AgentConfig.preSynthesize` before any rendering so a misconfigured
+ * convention fails the build instead of silently shipping broken
+ * shared-editing guidance. Returns the resolved config unchanged so
+ * callers can write `const se = validateSharedEditingConfig(config)`
+ * in one line.
+ *
+ * Malformed cases rejected here:
+ *
+ * - `sharedIndexPaths` contains an empty / whitespace-only entry, or
+ *   the array is supplied but empty.
+ * - `conflictStrategy` is not one of `"rebase"` / `"merge"`.
+ */
+declare function validateSharedEditingConfig(config?: SharedEditingConfig): ResolvedSharedEditing;
+/**
+ * Render the full body for the `shared-editing-safety` rule shipped
+ * by the `base` bundle. The rule documents:
+ *
+ * - The catalog of shared index files the contract applies to.
+ * - The pre-edit read-latest protocol (pull + re-read before editing).
+ * - The single-entry, deterministic-sort row-insert rule.
+ * - The commit-path verification step (read-back + count assertion).
+ * - The merge-conflict resolution recipe (rebase, re-sort, re-verify).
+ *
+ * When the convention is disabled, the rule renders a short stub that
+ * tells agents the project does not enforce the convention and that
+ * concurrent edits to shared index files may require manual conflict
+ * resolution.
+ */
+declare function renderSharedEditingRuleContent(se: ResolvedSharedEditing): string;
+/**
+ * Render the short shared-editing hook section injected into a
+ * phased-agent bundle's workflow rule (company-profile,
+ * people-profile, software-profile, etc.). The section cites the
+ * full contract documented in the base bundle's
+ * `shared-editing-safety` rule so individual bundles stay DRY.
+ *
+ * When the convention is disabled, the function returns an empty
+ * string so callers can no-op their append path.
+ */
+declare function renderSharedEditingBundleHook(se: ResolvedSharedEditing, bundleLabel: string): string;
+/**
+ * Render the `.claude/procedures/verify-index-row.sh` helper script.
+ * Exported so `AgentConfig` can register it as an `AgentProcedure`
+ * when the consumer opts in via `emitHelper: true`.
+ *
+ * The script takes two positional arguments:
+ *
+ * 1. `<index-path>` — repo-relative path to the shared index file.
+ * 2. `<row-unique-marker>` — substring unique to the new row.
+ *
+ * It exits non-zero on any of the following:
+ *
+ * - Wrong argument count.
+ * - Index file is not present in `HEAD` (i.e. not staged).
+ * - The unique-marker substring appears zero times (row missing)
+ *   or more than once (duplicate row from a mis-merged conflict).
+ */
+declare function renderSharedEditingHelperScript(_se: ResolvedSharedEditing): string;
+
+/**
+ * Default master switch for the skill-eval harness convention. When no
+ * config is supplied, the convention ships **enabled** so every skill
+ * that ships an `evals/evals.json` file has a documented schema,
+ * runner entry-point, and product-context injection contract.
+ *
+ * @see SkillEvalsConfig
+ */
+declare const DEFAULT_SKILL_EVALS_ENABLED = true;
+/**
+ * Default root directory (relative to the repo root) that holds every
+ * skill's SKILL.md. The harness contract says that any skill SKILL.md
+ * under this root may ship an `evals/evals.json` file alongside it —
+ * the runner discovers eval suites by walking
+ * `<skillsRoot>/<skill-name>/evals/evals.json`.
+ *
+ * Defaults to `.claude/skills`, which matches the location every
+ * configulator-managed project ships skills to on disk.
+ *
+ * @see SkillEvalsConfig
+ */
+declare const DEFAULT_SKILL_EVALS_SKILLS_ROOT = ".claude/skills";
+/**
+ * Default path to the product-context fixture consumed by every eval
+ * suite. Configulator ships with a `docs/src/content/docs/project-context.md`
+ * file that every agent already loads at session start; the eval harness
+ * re-uses that file so eval prompts are parameterised by the consuming
+ * project's domain vocabulary, in-scope capabilities, and stakeholders
+ * without the evals needing per-project forks.
+ *
+ * @see SkillEvalsConfig
+ */
+declare const DEFAULT_PRODUCT_CONTEXT_PATH = "docs/src/content/docs/project-context.md";
+/**
+ * Default policy for whether the harness should **require** a
+ * product-context file to be present before running the suite.
+ *
+ * `true` (default) — the runner fails fast when the file is missing,
+ * because an eval that silently runs without its product-context
+ * fixture is a false-positive waiting to happen.
+ *
+ * `false` — the runner emits a warning to stderr but still runs the
+ * suite. Useful for bootstrapping a new consuming repo that has not
+ * yet authored its `project-context.md`.
+ *
+ * @see SkillEvalsConfig
+ */
+declare const DEFAULT_REQUIRE_PRODUCT_CONTEXT = true;
+/**
+ * Default for whether the convention emits the
+ * `.claude/procedures/run-skill-evals.sh` helper to disk. The helper
+ * is opt-in because many consumers run evals from CI or ad-hoc from
+ * their own scripts rather than through the bundled harness; consumers
+ * who want a ready-to-invoke runner flip this to `true`.
+ *
+ * @see SkillEvalsConfig
+ */
+declare const DEFAULT_SKILL_EVALS_EMIT_RUNNER = false;
+/**
+ * Fully-resolved skill-evals settings. Every field is defaulted so
+ * downstream renderers can reason about a single canonical shape.
+ */
+interface ResolvedSkillEvals {
+    readonly enabled: boolean;
+    readonly skillsRoot: string;
+    readonly productContextPath: string;
+    readonly requireProductContext: boolean;
+    readonly emitRunner: boolean;
+}
+/**
+ * Resolve a (possibly absent) `SkillEvalsConfig` into a canonical
+ * `ResolvedSkillEvals` with every field filled in. Unset fields
+ * cascade from their documented defaults.
+ *
+ * Malformed configs — empty / whitespace-only or absolute `skillsRoot`,
+ * empty / whitespace-only or absolute `productContextPath` — throw a
+ * descriptive `Error`.
+ */
+declare function resolveSkillEvals(config?: SkillEvalsConfig): ResolvedSkillEvals;
+/**
+ * Synth-time validation hook. Throws a descriptive `Error` when the
+ * supplied `SkillEvalsConfig` is malformed. Called by
+ * `AgentConfig.preSynthesize` before any rendering so a misconfigured
+ * convention fails the build instead of silently shipping a broken
+ * eval harness. Returns the resolved config unchanged so callers can
+ * write `const se = validateSkillEvalsConfig(config)` in one line.
+ *
+ * Malformed cases rejected here:
+ *
+ * - `skillsRoot` empty, whitespace-only, or absolute.
+ * - `productContextPath` empty, whitespace-only, or absolute.
+ */
+declare function validateSkillEvalsConfig(config?: SkillEvalsConfig): ResolvedSkillEvals;
+/**
+ * Render the full body for the `skill-evals` rule shipped by the
+ * `base` bundle. The rule documents:
+ *
+ * - The on-disk contract (where `evals/evals.json` lives).
+ * - The JSON schema every eval file follows.
+ * - The product-context injection protocol (how evals reference and
+ *   interpolate the repo's `project-context.md` without forking).
+ * - The runner entry-point (`run-skill-evals.sh` when opted in, or
+ *   the inline `jq`-driven recipe when not).
+ *
+ * When the convention is disabled, the rule renders a short stub that
+ * tells agents the project does not ship skill evals and that skill
+ * changes ride on review alone.
+ */
+declare function renderSkillEvalsRuleContent(se: ResolvedSkillEvals): string;
+/**
+ * Render the short skill-evals hook section injected into a skill's
+ * owning bundle rule (requirements-writer, bcm-writer, etc.). The
+ * section cites the full contract documented in the base bundle's
+ * `skill-evals` rule so individual bundles stay DRY.
+ *
+ * When the convention is disabled, the function returns an empty
+ * string so callers can no-op their append path.
+ */
+declare function renderSkillEvalsBundleHook(se: ResolvedSkillEvals, skillLabel: string): string;
+/**
+ * Render the `.claude/procedures/run-skill-evals.sh` helper script.
+ * Exported so `AgentConfig` can register it as an `AgentProcedure`
+ * when the consumer opts in via `emitRunner: true`.
+ *
+ * The script takes zero or one positional arguments:
+ *
+ * 1. `[<skill-name>]` — optional, restricts the run to one skill.
+ *
+ * It exits non-zero on any of the following:
+ *
+ * - `jq` is not available on `PATH`.
+ * - A discovered `evals.json` is malformed or missing required fields.
+ * - `skill_name` inside the file does not match the parent directory.
+ * - The product-context fixture is missing and `requireProductContext`
+ *   is `true` in the resolved config.
+ */
+declare function renderSkillEvalsRunnerScript(se: ResolvedSkillEvals): string;
+
+/**
+ * Default master switch for the workflow-diagrams convention. When no
+ * config is supplied the convention ships **enabled** so every
+ * configulator-consuming repo carries the "diagram-touched-when-bundle-
+ * touched" rule in its rendered `CLAUDE.md`.
+ *
+ * @see WorkflowDiagramsConfig
+ */
+declare const DEFAULT_WORKFLOW_DIAGRAMS_ENABLED = true;
+/**
+ * Default repo-relative path for the workflow-diagrams page. Matches
+ * the singleton `/docs` site layout the monorepo contract assumes: a
+ * single Starlight docs site at `/docs` with sub-project agent pages
+ * under `docs/src/content/docs/agents/`.
+ *
+ * The file is never generated by configulator (the convention is
+ * explicit: diagrams are hand-authored for readability). Consumers
+ * opt into the starter stub via `emitStarterDiagram: true`.
+ *
+ * @see WorkflowDiagramsConfig
+ */
+declare const DEFAULT_WORKFLOW_DIAGRAMS_PATH = "docs/src/content/docs/agents/workflows.md";
+/**
+ * Default list of glob patterns that identify "bundle files" — the
+ * source files whose edits require the workflow-diagrams page to be
+ * touched in the same change set.
+ *
+ * The defaults cover the two canonical locations bundle-like content
+ * lives in a configulator-consuming repo:
+ *
+ * - `packages/@codedrifters/configulator/src/agent/bundles/**.ts` —
+ *   the bundle authoring sites inside configulator itself.
+ * - `.claude/agents/**.md` / `.claude/skills/**` — agent and skill
+ *   prompts in consuming repos that don't re-export configulator
+ *   bundles.
+ *
+ * Consumers can replace the list outright via `bundlePathPatterns`
+ * when their agent sources live elsewhere (e.g. a monorepo that keeps
+ * agents under `tools/agents/`).
+ *
+ * @see WorkflowDiagramsConfig
+ */
+declare const DEFAULT_WORKFLOW_DIAGRAMS_BUNDLE_PATH_PATTERNS: ReadonlyArray<string>;
+/**
+ * Default for whether the convention emits a starter workflow-diagrams
+ * page to disk at `<diagramsPath>`. Disabled by default because the
+ * page is hand-authored — an emitted stub would conflict with
+ * existing content on repos adopting the convention late.
+ *
+ * @see WorkflowDiagramsConfig
+ */
+declare const DEFAULT_WORKFLOW_DIAGRAMS_EMIT_STARTER = false;
+/**
+ * Default for whether the convention emits the
+ * `.claude/procedures/check-workflow-diagrams.sh` checker script. The
+ * script walks the staged / changed-file set and fails when a bundle
+ * file is touched without the diagrams page being touched too.
+ *
+ * Disabled by default because many consumers prefer to enforce the
+ * rule via review discipline and the rendered documentation alone;
+ * the script is opt-in for repos that want a hard CI gate or
+ * pre-commit hook.
+ *
+ * @see WorkflowDiagramsConfig
+ */
+declare const DEFAULT_WORKFLOW_DIAGRAMS_EMIT_CHECKER = false;
+/**
+ * Default for whether the rendered rule body asserts the diagram
+ * update as a **hard requirement** vs. a **strong recommendation**.
+ * Defaults to `true` — the whole point of the convention is that
+ * diagrams stay in sync, so the hard-requirement phrasing is the
+ * correct default. Consumers that treat diagrams as aspirational can
+ * soften the phrasing by setting this to `false`.
+ *
+ * @see WorkflowDiagramsConfig
+ */
+declare const DEFAULT_WORKFLOW_DIAGRAMS_REQUIRE_UPDATE = true;
+/**
+ * Fully-resolved workflow-diagrams settings. Every field is defaulted
+ * so downstream renderers can reason about a single canonical shape.
+ */
+interface ResolvedWorkflowDiagrams {
+    readonly enabled: boolean;
+    readonly diagramsPath: string;
+    readonly bundlePathPatterns: ReadonlyArray<string>;
+    readonly emitStarterDiagram: boolean;
+    readonly emitChecker: boolean;
+    readonly requireDiagramUpdate: boolean;
+}
+/**
+ * Resolve a (possibly absent) `WorkflowDiagramsConfig` into a
+ * canonical `ResolvedWorkflowDiagrams` with every field filled in.
+ * Unset fields cascade from their documented defaults.
+ *
+ * Malformed configs — empty / whitespace-only or absolute
+ * `diagramsPath`, empty `bundlePathPatterns`, empty /
+ * whitespace-only path entry — throw a descriptive `Error`.
+ */
+declare function resolveWorkflowDiagrams(config?: WorkflowDiagramsConfig): ResolvedWorkflowDiagrams;
+/**
+ * Synth-time validation hook. Throws a descriptive `Error` when the
+ * supplied `WorkflowDiagramsConfig` is malformed. Called by
+ * `AgentConfig.preSynthesize` before any rendering so a misconfigured
+ * convention fails the build instead of silently shipping broken
+ * workflow-diagrams guidance. Returns the resolved config unchanged
+ * so callers can write
+ * `const wd = validateWorkflowDiagramsConfig(config)` in one line.
+ *
+ * Malformed cases rejected here:
+ *
+ * - `diagramsPath` empty, whitespace-only, or absolute.
+ * - `bundlePathPatterns` not an array, empty, or contains an empty /
+ *   whitespace-only entry.
+ */
+declare function validateWorkflowDiagramsConfig(config?: WorkflowDiagramsConfig): ResolvedWorkflowDiagrams;
+/**
+ * Render the full body for the `workflow-diagrams-convention` rule
+ * shipped by the `base` bundle. The rule documents:
+ *
+ * - Why the convention exists (diagram / prose drift).
+ * - The on-disk contract — a single Mermaid-based page at
+ *   `<diagramsPath>` with one diagram per agent + a master
+ *   cross-agent diagram.
+ * - The **diagram-touched-when-bundle-touched** rule, phrased as a
+ *   hard requirement or a strong recommendation per
+ *   `requireDiagramUpdate`.
+ * - The set of paths the rule applies to.
+ * - The optional checker script (cross-referenced only when emitted).
+ *
+ * When the convention is disabled, the rule renders a short stub.
+ */
+declare function renderWorkflowDiagramsRuleContent(wd: ResolvedWorkflowDiagrams): string;
+/**
+ * Render the short workflow-diagrams hook section injected into a
+ * phased-agent bundle's workflow rule. The section cites the full
+ * contract documented in the base bundle's
+ * `workflow-diagrams-convention` rule so individual bundles stay DRY.
+ *
+ * When the convention is disabled, the function returns an empty
+ * string so callers can no-op their append path.
+ */
+declare function renderWorkflowDiagramsBundleHook(wd: ResolvedWorkflowDiagrams, bundleLabel: string): string;
+/**
+ * Render a minimal starter workflow-diagrams page — a top-level
+ * heading, the master-diagram placeholder, and a single example
+ * agent section. Exported so `AgentConfig` can emit it to disk when
+ * the consumer opts in via `emitStarterDiagram: true`.
+ *
+ * The starter is deliberately sparse: it documents the expected
+ * structure without committing the consumer to a particular agent
+ * list. Repos that already maintain a hand-authored diagrams page
+ * should leave `emitStarterDiagram` off — the emission would
+ * overwrite their content.
+ */
+declare function renderWorkflowDiagramsStarterPage(_wd: ResolvedWorkflowDiagrams): string;
+/**
+ * Render the `.claude/procedures/check-workflow-diagrams.sh` helper
+ * script. Exported so `AgentConfig` can register it as an
+ * `AgentProcedure` when the consumer opts in via `emitChecker: true`.
+ *
+ * The script accepts the list of changed files as either:
+ *
+ * 1. Positional arguments (one file per arg).
+ * 2. Newline-separated entries on stdin (when no args supplied) —
+ *    pipe `git diff --name-only` directly into it.
+ *
+ * It fails non-zero when any changed file matches a bundle-path
+ * pattern and the configured diagrams path is not also in the list.
+ * It exits `0` when no bundle files were touched or when the
+ * diagrams page was touched alongside them.
+ */
+declare function renderWorkflowDiagramsCheckerScript(wd: ResolvedWorkflowDiagrams): string;
+
+/**
+ * Build the requirements-analyst bundle with the supplied resolved
+ * paths.
  *
- * Provides a 2-phase requirements gap-discovery pipeline
- * (scan → draft-trace) designed for projects using the BCM (Business
- * Capability Model) framework. Ships a sub-agent, a user-invocable
- * skill, and `req:*` phase labels via the bundle `labels` mechanism so
- * consuming projects automatically pick up the label taxonomy through
- * the sync-labels workflow. See ADR-009 for the rationale behind
- * collapsing the draft and trace phases.
+ * Every reference to a canonical agent path (docs root, requirements
+ * root, bcm root, etc.) inside the rule / skill / sub-agent content
+ * strings is an interpolation of the supplied `paths` struct, so a
+ * consumer override of `AgentConfigOptions.paths` propagates to the
+ * rendered output.
+ */
+declare function buildRequirementsAnalystBundle(paths?: ResolvedAgentPaths): AgentRuleBundle;
+/**
+ * Default-paths instance of the requirements-analyst bundle, preserved
+ * for backward compatibility with consumers that import the const
+ * directly. The factory above is the canonical entry point when a
+ * consumer supplies `AgentConfigOptions.paths`.
  */
 declare const requirementsAnalystBundle: AgentRuleBundle;
 
@@ -2103,6 +5306,13 @@ declare const requirementsAnalystBundle: AgentRuleBundle;
  * phase label so they share the same queue and triage flow as the
  * rest of the requirements pipeline.
  */
+declare function buildRequirementsReviewerBundle(paths?: ResolvedAgentPaths): AgentRuleBundle;
+/**
+ * Default-paths instance of the requirements-reviewer bundle, preserved
+ * for backward compatibility with consumers that import the const
+ * directly. The factory above is the canonical entry point when a
+ * consumer supplies `AgentConfigOptions.paths`.
+ */
 declare const requirementsReviewerBundle: AgentRuleBundle;
 
 /**
@@ -2139,18 +5349,29 @@ declare const REQUIREMENTS_WRITER_PATHS: {
  * `type:requirement` is intentionally **not** declared here — it is
  * already declared by the `requirements-analyst` bundle and reused.
  */
+declare function buildRequirementsWriterBundle(paths?: ResolvedAgentPaths): AgentRuleBundle;
+/**
+ * Default-paths instance of the requirements-writer bundle, preserved
+ * for backward compatibility with consumers that import the const
+ * directly. The factory above is the canonical entry point when a
+ * consumer supplies `AgentConfigOptions.paths`.
+ */
 declare const requirementsWriterBundle: AgentRuleBundle;
 
 /**
- * Research-pipeline bundle — enabled by default.
- *
- * Consuming projects can disable it with
- * `excludeBundles: ["research-pipeline"]`. `appliesWhen` always returns
- * `true` per this batch's directive that bundles assume peers are
- * present.
+ * Build the research-pipeline bundle with the supplied resolved paths.
  *
- * Ships a sub-agent (`research-analyst`), a user-invocable skill
- * (`/research`), and `type:research` plus `research:*` phase labels.
+ * Every reference to a canonical agent path (research root, docs root,
+ * etc.) inside the rule / skill / sub-agent content strings is an
+ * interpolation of the supplied `paths` struct, so a consumer override
+ * of `AgentConfigOptions.paths` propagates to the rendered output.
+ */
+declare function buildResearchPipelineBundle(paths?: ResolvedAgentPaths): AgentRuleBundle;
+/**
+ * Default-paths instance of the research-pipeline bundle, preserved
+ * for backward compatibility with consumers that import the const
+ * directly. The factory above is the canonical entry point when a
+ * consumer supplies `AgentConfigOptions.paths`.
  */
 declare const researchPipelineBundle: AgentRuleBundle;
 
@@ -2168,6 +5389,13 @@ declare const researchPipelineBundle: AgentRuleBundle;
 declare const slackBundle: AgentRuleBundle;
 
 /**
+ * Build the software-profile bundle with the supplied resolved paths.
+ *
+ * Every reference to a canonical agent path (docs root, bcm root)
+ * inside the rule / skill / sub-agent content strings is an
+ * interpolation of the supplied `paths` struct, so a consumer override
+ * of `AgentConfigOptions.paths` propagates to the rendered output.
+ *
  * Software-profile bundle — enabled by default.
  *
  * Consuming projects can disable it with
@@ -2182,8 +5410,49 @@ declare const slackBundle: AgentRuleBundle;
  * skills (`/profile-software` and `/map-software`), and
  * `type:software-profile` plus `software:*` phase labels.
  */
+declare function buildSoftwareProfileBundle(paths?: ResolvedAgentPaths): AgentRuleBundle;
+/**
+ * Default-paths instance of the software-profile bundle, preserved
+ * for backward compatibility with consumers that import the const
+ * directly. The factory above is the canonical entry point when a
+ * consumer supplies `AgentConfigOptions.paths`.
+ */
 declare const softwareProfileBundle: AgentRuleBundle;
 
+/**
+ * Build the standards-research bundle with the supplied resolved paths.
+ *
+ * Every reference to a canonical agent path (docs root, research root,
+ * etc.) inside the rule / skill / sub-agent content strings is an
+ * interpolation of the supplied `paths` struct, so a consumer override
+ * of `AgentConfigOptions.paths` propagates to the rendered output.
+ *
+ * Consuming projects can disable it with
+ * `excludeBundles: ["standards-research"]`. `appliesWhen` always
+ * returns `true` per the workflow-bundle peer-present assumption.
+ *
+ * Ships a sub-agent (`standards-research-analyst`), five user-invocable
+ * skills (`/scope-standards-research`, `/research-standard`,
+ * `/compare-standards`, `/extension-standard`,
+ * `/organizations-standard`), a comparison-grid template (emitted
+ * alongside the compare skill), and `type:standards-research` plus
+ * `standards:*` phase labels.
+ *
+ * The bundle sits downstream of `research-pipeline` and
+ * `industry-discovery` (which surface the need for standards research)
+ * and hands off canonical profiles to `company-profile` and
+ * `people-profile`, extension ADRs to `requirements-writer`, and
+ * domain-entity mappings to `bcm-writer`.
+ */
+declare function buildStandardsResearchBundle(paths?: ResolvedAgentPaths): AgentRuleBundle;
+/**
+ * Default-paths instance of the standards-research bundle, preserved
+ * for backward compatibility with consumers that import the const
+ * directly. The factory above is the canonical entry point when a
+ * consumer supplies `AgentConfigOptions.paths`.
+ */
+declare const standardsResearchBundle: AgentRuleBundle;
+
 /**
  * Turborepo bundle — auto-detected when the TurboRepo component is present.
  */
@@ -2200,13 +5469,26 @@ declare const typescriptBundle: AgentRuleBundle;
 declare const vitestBundle: AgentRuleBundle;
 
 /**
- * Built-in rule bundles that ship with configulator.
- * Each bundle is auto-detected based on project introspection.
+ * Build the full list of built-in rule bundles with the supplied
+ * resolved agent paths. Every path-aware bundle accepts a
+ * `ResolvedAgentPaths` and threads it through its rule / skill /
+ * sub-agent content, so a consumer override of
+ * `AgentConfigOptions.paths` propagates into the rendered output.
  *
  * Order matters: base is first so its rules can be overridden by
  * more specific bundles. The base bundle's `appliesWhen` always
  * returns true; it is filtered by the `includeBaseRules` option
  * in AgentConfig.
+ *
+ * Bundles that do not read any agent path (typescript, jest,
+ * pnpm, etc.) stay as const exports and are referenced unchanged.
+ */
+declare function buildBuiltInBundles(paths?: ResolvedAgentPaths): ReadonlyArray<AgentRuleBundle>;
+/**
+ * Built-in rule bundles assembled with the default agent paths.
+ * Preserved for backward compatibility with tests and consumers
+ * that import the array directly. Prefer `buildBuiltInBundles(paths)`
+ * when consumer overrides are in scope.
  */
 declare const BUILT_IN_BUNDLES: ReadonlyArray<AgentRuleBundle>;
 
@@ -2471,6 +5753,150 @@ interface TemplateResolveResult {
  */
 declare function resolveTemplateVariables(template: string, metadata: ResolvedProjectMetadata | undefined): TemplateResolveResult;
 
+/**
+ * Options for the `.api.md` rollup slot produced by API Extractor.
+ */
+interface ApiExtractorReportOptions {
+    /**
+     * Folder (relative to the package root) where the `.api.md` rollup
+     * is written when the extractor runs. Treated as a scratch/temp
+     * location because rollups are **regenerated on scan** rather than
+     * committed to git (per docs-sync epic #448 resolved decision #3).
+     *
+     * The parent `ApiExtractor` component adds this folder to the
+     * package's `.gitignore` so rollups never land on the default branch.
+     *
+     * @default ".api-extractor/"
+     */
+    readonly reportFolder?: string;
+    /**
+     * Filename of the generated rollup, relative to `reportFolder`.
+     * Accepts the `<unscopedPackageName>` placeholder API Extractor
+     * expands at runtime.
+     *
+     * @default "<unscopedPackageName>.api.md"
+     */
+    readonly reportFileName?: string;
+}
+/**
+ * Options for the `ApiExtractor` projen component.
+ */
+interface ApiExtractorOptions {
+    /**
+     * Path to the TypeScript `.d.ts` rollup produced by the package's
+     * compile step, relative to the package root. Used as the
+     * extractor's `mainEntryPointFilePath`.
+     *
+     * Defaults to `<projectFolder>/lib/index.d.ts` — matches the
+     * `TypeScriptProject` default layout.
+     *
+     * @default "<projectFolder>/lib/index.d.ts"
+     */
+    readonly mainEntryPointFilePath?: string;
+    /**
+     * Path to the generated `api-extractor.json` config file (relative
+     * to the package root).
+     *
+     * @default "api-extractor.json"
+     */
+    readonly configFilePath?: string;
+    /**
+     * Rollup report options (where the `.api.md` lands).
+     */
+    readonly report?: ApiExtractorReportOptions;
+    /**
+     * Override the version of `@microsoft/api-extractor` that is added
+     * to the package's devDeps. Defaults to `VERSION.API_EXTRACTOR_VERSION`.
+     */
+    readonly apiExtractorVersion?: string;
+    /**
+     * When `true`, the extractor's `.api.md` rollup is treated as the
+     * committed baseline and diff-checked in-place. The docs-sync epic
+     * deliberately sets this to `false` — rollups are regenerate-on-scan
+     * and not committed to git.
+     *
+     * @default false
+     */
+    readonly commitApiReport?: boolean;
+}
+/**
+ * Default folder where `.api.md` rollups are written. Gitignored by
+ * the component so rollups never land in a commit.
+ */
+declare const DEFAULT_API_EXTRACTOR_REPORT_FOLDER = ".api-extractor/";
+/**
+ * Default filename template for rollups. The `<unscopedPackageName>`
+ * placeholder is expanded by `@microsoft/api-extractor` at run time.
+ */
+declare const DEFAULT_API_EXTRACTOR_REPORT_FILENAME = "<unscopedPackageName>.api.md";
+/**
+ * Default path (relative to the package root) to the TypeScript
+ * `.d.ts` rollup the extractor consumes. Matches the
+ * `TypeScriptProject` default output layout.
+ */
+declare const DEFAULT_API_EXTRACTOR_ENTRY_POINT = "<projectFolder>/lib/index.d.ts";
+/**
+ * Default path (relative to the package root) to the generated
+ * `api-extractor.json` config file.
+ */
+declare const DEFAULT_API_EXTRACTOR_CONFIG_FILE = "api-extractor.json";
+/**
+ * Wires `@microsoft/api-extractor` into a TypeScript project so the
+ * docs-sync pipeline can detect public-API drift introduced by a
+ * diff.
+ *
+ * The component adds the extractor devDep, synthesizes an
+ * `api-extractor.json` under the package root, and gitignores the
+ * generated `.api.md` rollup. Rollups are **regenerated on scan**
+ * (never committed to git) per docs-sync epic #448 resolved
+ * decision #3 — the in-repo helper at
+ * `.claude/procedures/extract-api.sh` runs the extractor end-to-end
+ * and writes the rollup to the scratch folder for the scan phase
+ * to consume in-memory.
+ *
+ * Callers normally do not construct this directly — the
+ * `TypeScriptProject` constructor creates one automatically.
+ */
+declare class ApiExtractor extends Component {
+    readonly project: NodeProject;
+    /**
+     * Find the ApiExtractor component on a project.
+     */
+    static of(project: NodeProject): ApiExtractor | undefined;
+    /**
+     * Generated config file path, relative to the package root.
+     */
+    readonly configFilePath: string;
+    /**
+     * Entry-point path supplied to the extractor.
+     */
+    readonly mainEntryPointFilePath: string;
+    /**
+     * Folder where `.api.md` rollups are written.
+     */
+    readonly reportFolder: string;
+    /**
+     * Filename (or filename template) of the rollup.
+     */
+    readonly reportFileName: string;
+    /**
+     * Pinned version of `@microsoft/api-extractor`.
+     */
+    readonly apiExtractorVersion: string;
+    /**
+     * Whether the generated report is committed alongside source.
+     * `false` by default — rollups regenerate on scan.
+     */
+    readonly commitApiReport: boolean;
+    constructor(project: NodeProject, options?: ApiExtractorOptions);
+    /**
+     * Render the JSON body of the generated `api-extractor.json`. Kept
+     * as a public method so tests can assert the shape without going
+     * through `synthSnapshot`.
+     */
+    renderConfig(): Record<string, unknown>;
+}
+
 /**
  * Astro output mode.
  *
@@ -2923,16 +6349,24 @@ interface AwsOrganization {
 declare function getLatestEligibleVersion(packageName: string, minimumReleaseAgeMinutes: number): Promise<string | null>;
 
 declare const VERSION: {
+    /**
+     * Version of `@microsoft/api-extractor` to pin for the docs-sync
+     * public-API drift detection runner. Used by the `ApiExtractor`
+     * component (wired into every `TypeScriptProject`) and the shared
+     * helper at `.claude/procedures/extract-api.sh`. See docs-sync
+     * epic child issue #513.
+     */
+    readonly API_EXTRACTOR_VERSION: "7.58.7";
     /**
      * Version of Astro to pin for AstroProject scaffolding.
      */
-    readonly ASTRO_VERSION: "6.1.8";
+    readonly ASTRO_VERSION: "6.1.9";
     /**
      * CDK CLI for workflows and command line operations.
      *
      * CLI and lib are versioned separately, so this is the CLI version.
      */
-    readonly AWS_CDK_CLI_VERSION: "2.1118.2";
+    readonly AWS_CDK_CLI_VERSION: "2.1119.0";
     /**
      * CDK Version to use for construct projects.
      *
@@ -2955,11 +6389,11 @@ declare const VERSION: {
     /**
      * Version of PNPM to use in workflows at github actions.
      */
-    readonly PNPM_VERSION: "10.33.0";
+    readonly PNPM_VERSION: "10.33.2";
     /**
      * Version of Projen to use.
      */
-    readonly PROJEN_VERSION: "0.99.51";
+    readonly PROJEN_VERSION: "0.99.52";
     /**
      * Version of `actions/setup-node` to use in GitHub workflows.
      * Tracks the version projen currently emits (see node_modules/projen/lib/github/workflows.js).
@@ -2973,7 +6407,7 @@ declare const VERSION: {
     /**
      * Version of @astrojs/starlight to pin for StarlightProject scaffolding.
      */
-    readonly STARLIGHT_VERSION: "0.38.3";
+    readonly STARLIGHT_VERSION: "0.38.4";
     /**
      * What version of the turborepo library should we use?
      */
@@ -3514,6 +6948,16 @@ interface TypeScriptProjectOptions extends Omit<typescript.TypeScriptProjectOpti
      * @default false
      */
     readonly agentConfig?: AgentConfigOptions | boolean;
+    /**
+     * Configure the `@microsoft/api-extractor` runner used by the
+     * docs-sync pipeline for public-API drift detection. When omitted
+     * the extractor is enabled with default options (rollups write to
+     * `.api-extractor/` and are gitignored). Set to `false` to opt a
+     * package out of drift detection entirely.
+     *
+     * @default {}
+     */
+    readonly apiExtractor?: ApiExtractorOptions | false;
 }
 declare class TypeScriptProject extends typescript.TypeScriptProject {
     constructor(userOptions: TypeScriptProjectOptions);
@@ -4784,4 +8228,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 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, agendaBundle, awsCdkBundle, baseBundle, bcmWriterBundle, businessModelsBundle, 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, AGENT_TIER_ROLES, AGENT_TIER_VALUES, 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 AgentTier, type AgentTierConfig, type AgentTierEntry, ApiExtractor, type ApiExtractorOptions, type ApiExtractorReportOptions, 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_AC_THRESHOLDS, DEFAULT_AGENT_PATHS, DEFAULT_AGENT_TIERS, DEFAULT_API_EXTRACTOR_CONFIG_FILE, DEFAULT_API_EXTRACTOR_ENTRY_POINT, DEFAULT_API_EXTRACTOR_REPORT_FILENAME, DEFAULT_API_EXTRACTOR_REPORT_FOLDER, DEFAULT_DECOMPOSITION_TEMPLATE, DEFAULT_DELEGATE_TO_PR_REVIEWER, DEFAULT_DISPATCH_MODEL, DEFAULT_DISPATCH_TO_HOUSEKEEPING_RATIO, DEFAULT_HOUSEKEEPING_MODEL, DEFAULT_ISSUE_TEMPLATES_BUNDLE_PATH_PATTERNS, DEFAULT_ISSUE_TEMPLATES_EMIT_CHECKER, DEFAULT_ISSUE_TEMPLATES_EMIT_STARTER, DEFAULT_ISSUE_TEMPLATES_ENABLED, DEFAULT_ISSUE_TEMPLATES_PATH, DEFAULT_ISSUE_TEMPLATES_REQUIRE_REFERENCE, DEFAULT_MERGE_METHOD, DEFAULT_OFF_PEAK_CRON_EXAMPLE, DEFAULT_PARTIAL_UNBLOCK_COMMENT_TEMPLATE, DEFAULT_PRIORITY_LABELS, DEFAULT_PRODUCT_CONTEXT_PATH, DEFAULT_PROGRESS_FILES_ENABLED, DEFAULT_PROGRESS_FILES_FILENAME_PATTERN, DEFAULT_PROGRESS_FILES_FORMAT, DEFAULT_PROGRESS_FILES_STALE_AFTER_HOURS, DEFAULT_PROGRESS_FILES_STATE_DIR, DEFAULT_REQUIRE_LINKED_ISSUE, DEFAULT_REQUIRE_PRODUCT_CONTEXT, DEFAULT_SCHEDULED_TASKS_ROOT, DEFAULT_SCHEDULED_TASK_ENTRIES, DEFAULT_SHARED_EDITING_CONFLICT_STRATEGY, DEFAULT_SHARED_EDITING_EMIT_HELPER, DEFAULT_SHARED_EDITING_ENABLED, DEFAULT_SHARED_EDITING_VERIFY_COMMIT, DEFAULT_SHARED_INDEX_PATHS, DEFAULT_SKILL_EVALS_EMIT_RUNNER, DEFAULT_SKILL_EVALS_ENABLED, DEFAULT_SKILL_EVALS_SKILLS_ROOT, DEFAULT_SOURCES_THRESHOLDS, DEFAULT_STATE_FILE_PATH, DEFAULT_STATUS_LABELS, DEFAULT_TEARDOWN_BRANCH_PATTERNS, DEFAULT_TYPE_LABELS, DEFAULT_UNBLOCK_COMMENT_TEMPLATE, DEFAULT_UNBLOCK_DEPENDENTS_ENABLED, DEFAULT_WORKFLOW_DIAGRAMS_BUNDLE_PATH_PATTERNS, DEFAULT_WORKFLOW_DIAGRAMS_EMIT_CHECKER, DEFAULT_WORKFLOW_DIAGRAMS_EMIT_STARTER, DEFAULT_WORKFLOW_DIAGRAMS_ENABLED, DEFAULT_WORKFLOW_DIAGRAMS_PATH, DEFAULT_WORKFLOW_DIAGRAMS_REQUIRE_UPDATE, type DeployWorkflowOptions, type DeploymentMetadata, type FocusArea, type FocusAreaMatch, type FocusConfig, type GitBranch, type GitHubBoardMetadata, type GitHubProjectMetadata, type GitHubSprintMetadata, type IDependencyResolver, type IssueTemplatesConfig, 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, PREFLIGHT_MERGE_METHOD_VALUES, PROD_DEPLOY_NAME, PROGRESS_FILES_FORMAT_VALUES, PnpmWorkspace, type PnpmWorkspaceOptions, type PreflightMergeMethod, type PreflightPrConfig, type PriorityRule, type ProgressFilesConfig, ProjectMetadata, type ProjectMetadataOptions, REQUIREMENTS_WRITER_PATHS, ROOT_CI_TASK_NAME, ROOT_TURBO_TASK_NAME, type RemoteCacheOptions, type RepositoryMetadata, ResetTask, type ResetTaskOptions, type ResolvedAgentPaths, type ResolvedAgentTier, type ResolvedIssueTemplates, type ResolvedPreflightPr, type ResolvedProgressFiles, type ResolvedProjectMetadata, type ResolvedRunRatio, type ResolvedScheduledTask, type ResolvedScheduledTasks, type ResolvedScopeGate, type ResolvedSharedEditing, type ResolvedSkillEvals, type ResolvedUnblockDependents, type ResolvedWorkflowDiagrams, type RunRatioConfig, SCHEDULED_TASK_MODEL_VALUES, SCOPE_CLASS_VALUES, SHARED_EDITING_CONFLICT_STRATEGY_VALUES, STARLIGHT_ROLE, type ScheduledTaskEntry, type ScheduledTaskModel, type ScheduledTaskOverride, type ScheduledTasksConfig, type ScopeClass, type ScopeGateConfig, type ScopeGateThresholds, type SharedEditingConfig, type SkillEvalsConfig, 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, UNKNOWN_TYPE_FALLBACK_TIER, type UnblockDependentsConfig, VERSION, VERSION_KEYS_SKIP, VERSION_NPM_PACKAGES, VSCodeConfig, type VersionKey, Vitest, type VitestConfigOptions, type VitestOptions, type WorkflowDiagramsConfig, addApproveMergeUpgradeWorkflow, addBuildCompleteJob, addSyncLabelsWorkflow, agendaBundle, awsCdkBundle, baseBundle, bcmWriterBundle, buildBaseBundle, buildBcmWriterBundle, buildBuiltInBundles, buildBusinessModelsBundle, buildCheckBlockedProcedure, buildCompanyProfileBundle, buildCustomerProfileBundle, buildDocsSyncBundle, buildIndustryDiscoveryBundle, buildMaintenanceAuditBundle, buildOrchestratorConventionsContent, buildPeopleProfileBundle, buildRegulatoryResearchBundle, buildRequirementsAnalystBundle, buildRequirementsReviewerBundle, buildRequirementsWriterBundle, buildResearchPipelineBundle, buildSoftwareProfileBundle, buildStandardsResearchBundle, buildUnblockDependentsProcedure, businessModelsBundle, classifyIssueScope, classifyRun, companyProfileBundle, customerProfileBundle, docsSyncBundle, extractApiProcedure, formatLayoutViolation, formatStarlightSingletonViolation, getLatestEligibleVersion, githubWorkflowBundle, industryDiscoveryBundle, jestBundle, maintenanceAuditBundle, meetingAnalysisBundle, orchestratorBundle, peopleProfileBundle, pnpmBundle, prReviewBundle, projenBundle, regulatoryResearchBundle, renderAgentTierCaseStatement, renderAgentTierSection, renderCustomDocSectionBlock, renderCustomDocSections, renderExtractApiProcedure, renderFocusSection, renderIssueTemplatesBundleHook, renderIssueTemplatesCheckerScript, renderIssueTemplatesRuleContent, renderIssueTemplatesStarterPage, renderMeetingTypesSection, renderPreflightPrSection, renderPreflightPrShellHelpers, renderPriorityRulesSection, renderProgressFileName, renderProgressFilePath, renderProgressFilesBundleHook, renderProgressFilesRuleContent, renderRunRatioSection, renderRunRatioShellHelpers, renderScheduledTaskSkillFile, renderScheduledTasksSection, renderScopeGateSection, renderScopeGateShellHelpers, renderSharedEditingBundleHook, renderSharedEditingHelperScript, renderSharedEditingRuleContent, renderSkillEvalsBundleHook, renderSkillEvalsRuleContent, renderSkillEvalsRunnerScript, renderSourceTierExamples, renderUnblockDependentsScript, renderUnblockDependentsSection, renderWorkflowDiagramsBundleHook, renderWorkflowDiagramsCheckerScript, renderWorkflowDiagramsRuleContent, renderWorkflowDiagramsStarterPage, requirementsAnalystBundle, requirementsReviewerBundle, requirementsWriterBundle, researchPipelineBundle, resolveAgentPaths, resolveAgentTiers, resolveAstroProjectOutdir, resolveAwsCdkProjectOutdir, resolveIssueTemplates, resolveModelAlias, resolveOrchestratorAssets, resolveOutdirFromPackageName, resolvePreflightPr, resolveProgressFiles, resolveRunRatio, resolveScheduledTasks, resolveScopeGate, resolveSharedEditing, resolveSkillEvals, resolveTemplateVariables, resolveTypeScriptProjectOutdir, resolveUnblockDependents, resolveWorkflowDiagrams, slackBundle, softwareProfileBundle, standardsResearchBundle, turborepoBundle, typescriptBundle, validateAgentTierConfig, validateIssueTemplatesConfig, validateMonorepoLayout, validatePreflightPrConfig, validateProgressFilesConfig, validateRunRatioConfig, validateScheduledTasksConfig, validateScopeGateConfig, validateSharedEditingConfig, validateSkillEvalsConfig, validateStarlightSingleton, validateUnblockDependentsConfig, validateWorkflowDiagramsConfig, vitestBundle };