@codedrifters/configulator 0.0.406 → 0.0.408

package/lib/index.d.mts

@@ -3884,8 +3884,27 @@ declare class AgentConfig extends Component {
      * credential requirement when a remote cache actually exists. The
      * getter is lazy by design — `TurboRepo` must already be attached
      * to the project when the bundles are first read.
+     *
+     * Every **config-driven convention rule** is likewise resolved here
+     * and seeded into its owning bundle, so the rule enters the rule map
+     * already carrying the consumer's settings. Rewriting those rules
+     * after the map was assembled — the previous approach — silently
+     * discarded any `ruleExtensions` append or same-name `rules`
+     * override that had already been merged in.
      */
     private get pathAwareBundles();
+    /**
+     * Resolved settings for every config-driven convention rule, derived
+     * from this project's options. Consumed by `buildBuiltInBundles` so
+     * the `base` and `orchestrator` bundles seed final rule content.
+     *
+     * `excludeBundles` feeds two of these: the orchestrator's rendered
+     * tier table / scope-gate overrides / scheduled-tasks registry drop
+     * rows owned by excluded bundles, and the issue-templates rule falls
+     * back to its disabled stub once every downstream-issue-kind bundle
+     * has been excluded.
+     */
+    private get resolvedRuleConventions();
     /**
      * Returns the bundles that are active for this project: auto-detected
      * bundles (when `autoDetectBundles !== false`) plus force-included
@@ -3950,72 +3969,6 @@ declare class AgentConfig extends Component {
     private resolveBundlePermissions;
 }
 
-/**
- * Fully-resolved build policy for the consuming project.
- *
- * The generated agent guidance around `pnpm build:all` used to assert
- * unconditionally that the command "requires the user to be
- * authenticated to AWS on the prod account used for Turborepo remote
- * caching (`readonlyaccess-prod-525259625215-us-east-1` profile)".
- * Both halves of that sentence were wrong for most consumers:
- *
- *   1. The AWS-auth requirement only exists when a Turborepo **remote
- *      cache** is configured. Consumers running a local cache only
- *      (`turbo.json` with just a `cacheDir`) need no credentials at
- *      all, and agents that believed otherwise aborted mid-flow —
- *      three lost-work incidents in `codedrifters/openhi-planning`.
- *   2. The profile name was this repository's own profile, baked
- *      verbatim into every consumer's generated text.
- *
- * This struct carries the two facts the rule renderers need, derived
- * from the project's actual {@link TurboRepo} configuration, so the
- * guidance is true for whichever consumer it renders into.
- *
- * @see resolveBuildPolicy
- */
-interface ResolvedBuildPolicy {
-    /**
-     * Whether a Turborepo **remote** cache is configured on the project.
-     *
-     * `false` means either there is no {@link TurboRepo} component at
-     * all, or it was constructed without `remoteCacheOptions` — in both
-     * cases `pnpm build:all` needs no AWS credentials and the generated
-     * guidance must not claim otherwise.
-     */
-    readonly remoteCacheEnabled: boolean;
-    /**
-     * Local AWS profile name used to fetch the remote-cache endpoint and
-     * token, taken from `remoteCacheOptions.profileName`.
-     *
-     * `undefined` whenever {@link remoteCacheEnabled} is `false`. Never
-     * hard-code a profile name in rule content — read it from here so
-     * each consumer's generated text names its own profile.
-     */
-    readonly awsProfileName?: string;
-}
-/**
- * Build policy for a project with no Turborepo remote cache — the
- * zero-config default. Rule renderers that receive this omit the
- * AWS-authentication guidance entirely rather than asserting a
- * credential requirement that does not exist.
- */
-declare const DEFAULT_BUILD_POLICY: ResolvedBuildPolicy;
-/**
- * Derives the {@link ResolvedBuildPolicy} for a project by inspecting
- * its {@link TurboRepo} component.
- *
- * Auto-detection, not opt-in: `remoteCacheOptions` being `undefined`
- * *is* the "remote cache disabled" signal — `TurboRepo.renderRunArgs`
- * already branches on exactly the same condition when it decides
- * whether to emit `--api` / `--token` / `--team` flags. Consumers get
- * accurate guidance with no extra configuration.
- *
- * Call this lazily (at synthesis time), not from a constructor: the
- * `TurboRepo` component must already be attached to the project for
- * detection to succeed.
- */
-declare function resolveBuildPolicy(project: Project): ResolvedBuildPolicy;
-
 /**
  * Valid `status:*` values that may appear in an
  * `IssueDefaultsOverride.status`. The list mirrors the canonical
@@ -4111,1099 +4064,1450 @@ declare function validateIssueDefaultsConfig(config?: IssueDefaultsConfig): Reso
 declare function labelsForPhase(resolved: ResolvedIssueDefaults, phaseLabel: string): ResolvedIssueDefaultsEntry;
 
 /**
- * Fully-resolved requirement category subdirectory names, relative to
- * the requirements root. Every property is required.
- */
-interface ResolvedRequirementCategoryDirs {
-    readonly business: string;
-    readonly functional: string;
-    readonly nonFunctional: string;
-    readonly technical: string;
-    readonly architecturalDecisions: string;
-    readonly security: string;
-    readonly data: string;
-    readonly integration: string;
-    readonly operational: string;
-    readonly ux: string;
-    readonly multiTenancy: string;
-}
-/**
- * Fully-resolved agent output-path roots. Every property is required.
+ * The GitHub **issue type** vocabulary this convention assigns.
  *
- * 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;
-    readonly requirementCategoryDirs: ResolvedRequirementCategoryDirs;
-}
-/**
- * Canonical default subdirectory name for each requirement category.
- * These mirror the hardcoded `functional/`, `non-functional/`, … dirs
- * that the requirements bundles emitted before category dirs became
- * configurable, so the generated requirements snapshot is unchanged
- * unless a consumer overrides an entry.
- */
-declare const DEFAULT_REQUIREMENT_CATEGORY_DIRS: ResolvedRequirementCategoryDirs;
-/**
- * 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.
+ * An issue type is a first-class GitHub field (Epic / Feature / Bug /
+ * Task) and is a completely different axis from the `type:*` **label**
+ * taxonomy:
  *
- * Consumers override the defaults by passing an `AgentPathsConfig`
- * through `AgentConfigOptions.paths` and resolving it with
- * `resolveAgentPaths()`. Every path-aware bundle threads the resolved
- * struct through its rule / skill / sub-agent content, so an override
- * propagates into the rendered output.
+ * - `type:<bundle>` / `type:<conventional-commit>` — a *label*. Routing
+ *   and dedup signal. Owned by {@link BUNDLE_OWNERSHIP} and set with
+ *   `gh issue create --label`.
+ * - GitHub issue type — a *field*. Human triage, Epic-relationship
+ *   tracking, and reporting signal. `gh issue create` cannot set it, so
+ *   it is applied immediately after creation via the
+ *   `updateIssueIssueType` GraphQL mutation.
+ *
+ * Conflating the two is the single most common mistake in this area, so
+ * both this module and the prose it renders keep them explicitly apart.
  */
-declare const DEFAULT_AGENT_PATHS: ResolvedAgentPaths;
+declare const GITHUB_ISSUE_TYPES: readonly ["Epic", "Feature", "Bug", "Task"];
+type GithubIssueType = (typeof GITHUB_ISSUE_TYPES)[number];
 /**
- * Resolve a partial `AgentPathsConfig` into a fully-populated
- * `ResolvedAgentPaths`. Unset fields cascade from their parent root:
+ * The issue type every title prefix maps to unless it is one of the
+ * three explicit exceptions in {@link NON_DEFAULT_TITLE_PREFIX_TYPES}.
  *
- * - `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.
+ * Every bundle-phase prefix (`company:`, `req:`, `bcm:`, `software:`,
+ * …) lands here, which is why agent-enqueued downstream issues are
+ * almost always `Task` — the phased pipelines file work items, not
+ * features or bug reports.
  */
-declare function resolveAgentPaths(paths?: AgentPathsConfig): ResolvedAgentPaths;
-
+declare const DEFAULT_GITHUB_ISSUE_TYPE: GithubIssueType;
 /**
- * Default path globs that exempt a PR from the `human-required.size`
- * rule. The policy walks every changed path in the PR and skips
- * rule #6 (size threshold) when **every** path matches at least one
- * glob in this list. Doc-only PRs routinely exceed the 500-insertion
- * threshold (large migrations, bulk additions, refresh passes) but
- * carry no production risk that warrants forcing a human reviewer.
+ * Canonical issue-title-prefix → GitHub issue type map.
  *
- * The default exempts the entire `docs/**` tree — every consumer of
- * configulator places its Starlight docs site there. Consumers can
- * extend this list (e.g. add `docs/research/**` if doc-style research
- * notes live outside the Starlight tree) by passing
- * `prReviewPolicy.autoMerge.pathsExemptFromSize`.
+ * Derived from {@link CONVENTIONAL_COMMIT_TYPE_LABELS} — the shared
+ * conventional-commit vocabulary exported alongside the bundle
+ * ownership registry — so the prefix list can never drift from the
+ * label list the create-issue workflow stamps. Every conventional-commit
+ * prefix defaults to `Task`; the three exceptions are overlaid on top.
  *
- * @see PrReviewPolicyConfig
- * @see PrReviewAutoMergeConfig.pathsExemptFromSize
+ * Prefixes carry their trailing colon (`"feat:"`) to match the way the
+ * title conventions write them.
  */
-declare const DEFAULT_PATHS_EXEMPT_FROM_SIZE: ReadonlyArray<string>;
+declare const GITHUB_ISSUE_TYPE_BY_TITLE_PREFIX: Readonly<Record<string, GithubIssueType>>;
 /**
- * Fully-resolved PR review policy. Every field is defaulted so
- * downstream renderers can reason about a single canonical shape.
+ * Resolve an issue **title** to the GitHub issue type it must carry.
  *
- * Two sub-rules are configurable today: the doc-only carve-out
- * against the size threshold (`autoMerge.pathsExemptFromSize`) and
- * the CI-verification fallback's required-workflow list
- * (`ciVerification.requiredWorkflows`). Additional knobs for other
- * rules in the policy may be added in future versions of
- * `PrReviewPolicyConfig`.
+ * Anything that is not one of the four recognised non-default prefixes
+ * — including every bundle-phase prefix (`company:research: …`) and a
+ * title with no prefix at all — resolves to
+ * {@link DEFAULT_GITHUB_ISSUE_TYPE}.
  */
-interface ResolvedPrReviewPolicy {
-    readonly autoMerge: ResolvedPrReviewAutoMerge;
-    readonly ciVerification: ResolvedPrReviewCiVerification;
-}
+declare function githubIssueTypeForTitle(title: string): GithubIssueType;
 /**
- * Fully-resolved `auto-merge` half of the policy.
- *
- * `pathsExemptFromSize` is always populated — the default
- * (`["docs/**"]`) ships when the consumer omits the option.
+ * Path to the `set-issue-type.sh` helper the `github-workflow` bundle
+ * ships. Referenced (never assumed present) by the rendered prose — see
+ * {@link renderGithubIssueTypeSectionLines} for the fallback that keeps
+ * the recipe working for consumers who exclude that bundle.
  */
-interface ResolvedPrReviewAutoMerge {
-    readonly pathsExemptFromSize: ReadonlyArray<string>;
-}
+declare const SET_ISSUE_TYPE_HELPER_PATH = ".claude/procedures/set-issue-type.sh";
 /**
- * Fully-resolved `ci-verification` half of the policy.
+ * The two-step `updateIssueIssueType` GraphQL flow, rendered as shell.
  *
- * `requiredWorkflows` is always populated — the default (`[]`, i.e.
- * "treat every observed Actions run as required") ships when the
- * consumer omits the option.
+ * `set-issue-type.sh` wraps exactly this flow, but that helper ships
+ * **only** via the `github-workflow` bundle. Any recipe outside that
+ * bundle that cited the helper unconditionally would be broken for a
+ * consumer running `excludeBundles: ["github-workflow"]`, so the
+ * fallback is documented inline in an always-on base rule and every
+ * per-filing-site step points at it.
  */
-interface ResolvedPrReviewCiVerification {
-    readonly requiredWorkflows: ReadonlyArray<string>;
-}
+declare function renderSetIssueTypeFallbackLines(): Array<string>;
 /**
- * Resolve a (possibly absent) `PrReviewPolicyConfig` into a canonical
- * `ResolvedPrReviewPolicy` with every field filled in. Unset fields
- * cascade from their documented defaults.
+ * Render the **GitHub Issue Type** section of the always-on
+ * `issue-conventions` rule.
  *
- * Malformed configs (empty / whitespace-only path entries) throw a
- * descriptive `Error` — callers should not need to guard against it
- * at runtime.
- */
-declare function resolvePrReviewPolicy(config?: PrReviewPolicyConfig): ResolvedPrReviewPolicy;
-/**
- * Synth-time validation hook. Throws a descriptive `Error` when the
- * supplied `PrReviewPolicyConfig` is malformed. Called by
- * `AgentConfig.preSynthesize` before any rendering so a misconfigured
- * policy fails the build instead of silently shipping broken carve-out
- * globs. Returns the resolved policy unchanged so callers can write
- * `const policy = validatePrReviewPolicyConfig(config)` in one line.
+ * The section is the single canonical answer to "how does an agent set
+ * an issue's type?", and it is rendered into an `ALWAYS`-scoped base
+ * rule precisely so every downstream filing site can cite it in one
+ * line regardless of which optional bundles the consumer enabled.
  *
- * Malformed cases rejected here:
+ * It documents both paths deliberately:
  *
- * - `pathsExemptFromSize` entries that are empty or whitespace-only —
- *   such an entry would either silently match nothing or match every
- *   path, both of which are almost certainly a typo.
- * - `requiredWorkflows` entries that are empty or whitespace-only — a
- *   blank workflow name can never match an Actions-run `name`, so the
- *   intended gate would silently never fire.
+ * 1. The `set-issue-type.sh` one-liner, when `github-workflow` is
+ *    active.
+ * 2. The inline GraphQL fallback, when it is not.
  */
-declare function validatePrReviewPolicyConfig(config?: PrReviewPolicyConfig): ResolvedPrReviewPolicy;
-
+declare function renderGithubIssueTypeSectionLines(): Array<string>;
 /**
- * One row in the rendered agent registry table. Each phased-agent
- * bundle that previously shipped its own `<bundle>-workflow` rule
- * contributes exactly one entry here so the registry can answer
- * "which agent handles X" without rendering 18 prose summaries
- * into CLAUDE.md.
+ * Render the title-prefix → issue-type mapping as a markdown bullet
+ * list, for recipes that present it inline rather than as a table (the
+ * interactive create-issue workflow's step 3).
+ *
+ * Grouping matches the table in {@link renderGithubIssueTypeSectionLines}:
+ * one bullet per non-default prefix, then a single bullet collapsing
+ * every prefix that maps to {@link DEFAULT_GITHUB_ISSUE_TYPE}.
  */
-interface AgentRegistryEntry {
-    /** Bundle name as it appears in `buildBuiltInBundles`, e.g. `bcm-writer`. */
-    readonly bundle: string;
-    /** Primary user-invocable skill, with leading slash, e.g. `/write-bcm`. */
-    readonly skill: string;
-    /** Sub-agent name in `.claude/agents/`, e.g. `bcm-writer`. */
-    readonly agent: string;
+declare function renderTitlePrefixTypeBullets(indent?: string): Array<string>;
+/** String form of {@link renderGithubIssueTypeSectionLines}. */
+declare function renderGithubIssueTypeSection(): string;
+/** Options for {@link renderIssueTypeAssignmentStep}. */
+interface IssueTypeAssignmentStepOptions {
     /**
-     * Function that resolves the canonical output path for this
-     * bundle from the project's resolved agent-path roots. Returning
-     * an empty string signals "no filesystem output path" (used by
-     * pr-review). Path-aware so consumer overrides on
-     * `AgentConfigOptions.paths` propagate into the rendered table.
+     * Leading whitespace prepended to every rendered line so the step
+     * nests correctly under the numbered/bulleted filing recipe it
+     * follows. Defaults to the three spaces a top-level numbered list
+     * item continues with.
      */
-    readonly resolveOutputPath: (paths: ResolvedAgentPaths) => string;
+    readonly indent?: string;
     /**
-     * One-line purpose description. Lifted from the first prose
-     * sentence of the original `<bundle>-workflow` rule so consumers
-     * keep the same routing signal.
+     * The GitHub issue type the filed issue must carry. Defaults to
+     * {@link DEFAULT_GITHUB_ISSUE_TYPE}, which is correct for every
+     * bundle-phase-prefixed downstream issue.
      */
-    readonly purpose: string;
+    readonly issueType?: GithubIssueType;
     /**
-     * Name of the original `<bundle>-workflow` rule. Used by the
-     * registry helper to filter the resolved bundle list and assert
-     * (via the test suite) that no bundle still ships its workflow
-     * rule into the Claude platform output.
+     * Render the step as a markdown list item (`- …` with hanging
+     * continuation lines) instead of a paragraph. Used at the handful of
+     * filing recipes that specify the issue with a bullet list rather
+     * than numbered prose.
      */
-    readonly workflowRuleName: string;
+    readonly bullet?: boolean;
 }
 /**
- * Static registry of every phased-agent bundle that contributes a
- * routing row. Order is alphabetical by bundle name so the
- * rendered table is stable across runs and consumer-side diffs are
- * minimal. Adding a new phased-agent bundle requires appending one
- * row here and suppressing its `<bundle>-workflow` rule via
- * `platforms: { claude: { exclude: true } }`.
+ * Render the compact "now set the issue type" step appended to every
+ * bundle-shipped downstream filing recipe.
+ *
+ * Kept deliberately short: it appears at ~45 filing sites across the
+ * phased-pipeline bundles, so it names the concrete type, calls out that
+ * the `type:*` label is a different field, gives the command, and
+ * delegates the fallback to the always-on `issue-conventions` rule
+ * rather than re-inlining the GraphQL flow at every site.
  */
-declare const AGENT_REGISTRY_ENTRIES: ReadonlyArray<AgentRegistryEntry>;
+declare function renderIssueTypeAssignmentStep(options?: IssueTypeAssignmentStepOptions): Array<string>;
 /**
- * The set of `<bundle>-workflow` rule names that the registry
- * subsumes. Used both to suppress those rules from the Claude
- * platform output and to assert in tests that no bundle still
- * ships its prose summary into CLAUDE.md.
+ * Render the phase-wide variant of {@link renderIssueTypeAssignmentStep}
+ * for a workflow phase that files several kinds of issue across several
+ * steps, where repeating the per-recipe step at each one would bloat the
+ * prompt without adding information.
  */
-declare const SUPPRESSED_WORKFLOW_RULE_NAMES: ReadonlyArray<string>;
+declare function renderIssueTypeAssignmentBlanket(indent?: string, issueType?: GithubIssueType): Array<string>;
+
 /**
- * Returns `true` when the supplied rule name belongs to a
- * phased-agent `<bundle>-workflow` rule whose routing summary now
- * lives in the shared `agent-registry` rule.
+ * 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`.
+ *
+ * @see IssueTemplatesConfig
  */
-declare function isSuppressedWorkflowRule(name: string): boolean;
+declare const DEFAULT_ISSUE_TEMPLATES_ENABLED = true;
 /**
- * Reverse map from a `<bundle>-workflow` rule name to its owning
- * bundle name. Used by the registry consolidation loop to detect
- * when a consumer has targeted a bundle with a
- * `features.customDocSections` entry — those bundles keep
- * rendering their workflow rule into CLAUDE.md so the consumer-
- * supplied prose has somewhere to live. Returns `undefined` for
- * any rule name that is not in the registry's suppression list.
+ * 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/`.
+ *
+ * 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.
+ *
+ * @see IssueTemplatesConfig
  */
-declare function bundleNameForWorkflowRule(ruleName: string): string | undefined;
-declare function buildAgentRegistryRule(bundles: ReadonlyArray<AgentRuleBundle>, paths: ResolvedAgentPaths): AgentRule | undefined;
-
+declare const DEFAULT_ISSUE_TEMPLATES_PATH = "docs/src/content/docs/agents/issue-templates.md";
 /**
- * Agenda bundle — enabled by default.
+ * 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.
  *
- * Consuming projects can disable it with
- * `excludeBundles: ["agenda"]`. `appliesWhen` always returns `true`
- * (peer-present assumption, same pattern as the other workflow
- * bundles).
+ * The defaults cover the locations bundle-like content lives in a
+ * generic configulator-consuming repo:
  *
- * 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.
+ * - `.claude/agents/**.md` / `.claude/skills/**` — agent and skill
+ *   prompts in consuming repos that don't re-export configulator
+ *   bundles.
  *
- * Reuses the meeting-type taxonomy from
- * `AgentConfigOptions.meetings.meetingTypes` — the same table the
- * `meeting-analysis` bundle consumes for post-meeting extraction.
+ * Repos that **also** host configulator's own bundle source as a
+ * workspace package (only `codedrifters/packages` itself) should
+ * append `packages/@codedrifters/configulator/src/agent/bundles/**.ts`
+ * via `IssueTemplatesConfig.bundlePathPatterns` to lint those bundle
+ * sources too. The default omits that pattern because it is dead
+ * weight (matches nothing) in any other consumer.
+ *
+ * Consumers can replace the list outright via `bundlePathPatterns`
+ * when their agent sources live elsewhere.
+ *
+ * @see IssueTemplatesConfig
  */
-declare const agendaBundle: AgentRuleBundle;
-
+declare const DEFAULT_ISSUE_TEMPLATES_BUNDLE_PATH_PATTERNS: ReadonlyArray<string>;
 /**
- * AWS CDK bundle — auto-detected when `aws-cdk-lib` is in dependencies.
+ * 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.
+ *
+ * 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.
+ *
+ * @see IssueTemplatesConfig
  */
-declare const awsCdkBundle: AgentRuleBundle;
-
+declare const DEFAULT_ISSUE_TEMPLATES_EMIT_CHECKER = false;
 /**
- * Base bundle — always included unless `includeBaseRules: false`.
- * Contains project-overview, interaction-style, and general-conventions rules.
+ * Default for whether the convention emits the issue-templates
+ * scaffold to disk. The scaffold is two files:
+ *
+ * 1. A **write-once** starter page at `<templatesPath>` (projen
+ *    `SampleFile`) carrying the expected structure — the "How to use"
+ *    preamble and one example `## Template: <phase-label>` section —
+ *    which the consumer then fleshes out by hand.
+ * 2. An **always-regenerated** companion page at
+ *    {@link issueTemplatesGeneratedPath}, carrying one label-correct
+ *    recipe stub per phase label the consumer's active bundles emit.
+ *
+ * The split exists because a `SampleFile` never reaches a consumer
+ * whose page already exists: repos that adopted the convention on an
+ * older configulator would otherwise be frozen on whatever skeleton
+ * shipped that day. Hand-authored bodies stay in the write-once page;
+ * the generated label sets regenerate on every `projen` run so a new
+ * phase label reaches every consumer on their next upgrade.
+ *
+ * Disabled by default because the hand-authored page conflicts with
+ * the ad-hoc notes most repos already maintain when they adopt the
+ * convention.
+ *
+ * @see IssueTemplatesConfig
  */
-declare function buildBaseBundle(paths?: ResolvedAgentPaths): AgentRuleBundle;
+declare const DEFAULT_ISSUE_TEMPLATES_EMIT_STARTER = false;
 /**
- * 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`.
+ * Filename suffix appended to the templates page's stem to derive the
+ * always-regenerated companion page. Chosen so the companion can never
+ * collide with a hand-authored router layout that splits recipes into
+ * `<stem>/<child>.md` sibling pages.
  */
-declare const baseBundle: AgentRuleBundle;
-
+declare const ISSUE_TEMPLATES_GENERATED_SUFFIX = "-generated";
 /**
- * Hand-maintained registry mapping every bundle name to the cross-bundle
- * surface it owns: GitHub `type:*` labels, phase-label prefixes,
- * scheduled-task IDs, whether it emits Starlight docs, and whether it
- * declares any downstream issue kinds (i.e. files `gh issue create`
- * recipes via the issue-templates convention).
- *
- * The registry is consulted by renderers in other bundles whenever
- * `AgentConfigOptions.excludeBundles` is non-empty so cross-bundle
- * references to an excluded bundle's agents, type labels, phase labels,
- * or scheduled tasks disappear from the generated output.
- *
- * The map is **hand-maintained** rather than derived from each bundle's
- * runtime shape. The defining surfaces (the funnel-tier table in
- * `tiers.ts`, the per-phase scope-gate overrides in `scope-gate.ts`, and
- * the scheduled-tasks registry in `scheduled-tasks.ts`) live as flat
- * data tables that already get walked by their renderers — declaring the
- * ownership map alongside them keeps the relationship explicit and
- * readable without forcing every bundle to grow an "ownership"
- * descriptor.
- *
- * Bundles that ship no cross-bundle surface (e.g. `slack`, `typescript`,
- * `pnpm`, `vitest`, `jest`, `aws-cdk`, `projen`, `turborepo`,
- * `upstream-configulator-docs`) deliberately do not appear here —
- * excluding them is already a no-op since they own nothing other
- * bundles reference.
+ * Repo-relative path of the always-regenerated companion page for a
+ * given `templatesPath`: the stem gains
+ * {@link ISSUE_TEMPLATES_GENERATED_SUFFIX} and keeps its extension
+ * (`…/issue-templates.md` → `…/issue-templates-generated.md`).
  */
-interface BundleOwnership {
-    /**
-     * GitHub `type:*` label values (without the `type:` prefix) the
-     * bundle owns. The funnel-tier table in `tiers.ts` and any rendered
-     * tables that group agents by `type:*` label consult this list.
-     */
-    readonly typeLabels: ReadonlyArray<string>;
-    /**
-     * Phase-label prefixes (with trailing colon, e.g. `"company:"`) the
-     * bundle owns. Used by the scope-gate per-phase override table and
-     * any other renderer that groups by phase label. An entry without a
-     * trailing colon (e.g. `"req:write"`) is treated as an exact
-     * phase-label match instead of a prefix.
-     */
-    readonly phaseLabelPrefixes: ReadonlyArray<string>;
-    /**
-     * `taskId` values from `DEFAULT_SCHEDULED_TASK_ENTRIES` that target
-     * this bundle's sub-agent. The scheduled-tasks registry filter in
-     * `agent-config.ts` consults this list when pruning default entries
-     * for an excluded bundle.
-     */
-    readonly scheduledTaskIds: ReadonlyArray<string>;
-    /**
-     * Whether this bundle emits Starlight content roots — i.e. whether
-     * any of its workflows write files under `docs/src/content/docs/`
-     * (or the configured docs root). Drives the auto-suppression of the
-     * `section-index-pages` rule when no docs-emitting bundle is active.
-     */
-    readonly emitsDocs: boolean;
-    /**
-     * Whether this bundle dispatches downstream issues (i.e. its
-     * workflows file `gh issue create` recipes). Drives the
-     * auto-suppression of the `issue-templates-convention` rule when no
-     * such bundle is active.
-     */
-    readonly downstreamIssueKinds: boolean;
-}
+declare function issueTemplatesGeneratedPath(templatesPath: string): string;
 /**
- * Canonical ownership map. Only bundles that own at least one
- * cross-bundle surface appear here.
+ * Glob matching the sibling child pages of a router-style templates
+ * layout (`…/issue-templates.md` → `…/issue-templates/*.md`). The
+ * label-consistency lint walks these so a repo that split its recipes
+ * across child pages is checked against the same map.
  */
-declare const BUNDLE_OWNERSHIP: Readonly<Record<string, BundleOwnership>>;
+declare function issueTemplatesChildGlob(templatesPath: string): string;
 /**
- * GitHub `type:*` labels (WITH the `type:` prefix) that come from the
- * **conventional-commit** vocabulary rather than the bundle/routing
- * vocabulary. These are derived from an issue's title prefix by the
- * generic create-issue workflow (`feat:` → `type:feat`, `docs:` →
- * `type:docs`, …) and are the only `type:*` labels the phase-label
- * invariant is allowed to remove when it corrects a mislabeled issue.
- *
- * A bundle `type:*` label (e.g. `type:research`, `type:bcm-document`)
- * is deliberately **not** in this set: an issue carrying a phase label
- * from one bundle plus a `type:*` label owned by a *different* bundle
- * is genuinely ambiguous and gets flagged for a human rather than
- * silently rewritten.
- */
-declare const CONVENTIONAL_COMMIT_TYPE_LABELS: ReadonlyArray<string>;
-/**
- * Canonical phase-label matcher → `type:<bundle>` label map, derived
- * from {@link BUNDLE_OWNERSHIP}. This is the **single source of truth**
- * for the phase-label → type-label invariant: label registry
- * generation, the orchestrator's triage sweep, and the consumer-facing
- * label audit all read this map rather than re-deriving the pairing.
+ * 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.
  *
- * Keys are matchers in the same notation `BundleOwnership.phaseLabelPrefixes`
- * uses — an entry ending in a colon (`"company:"`) is a prefix match,
- * an entry without one (`"req:write"`) is an exact match. Values carry
- * the `type:` prefix.
+ * 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`.
  *
- * Co-ownership is fine as long as the co-owners agree on the type
- * label: all three requirements bundles declare `type:requirement`, so
- * `req:`, `req:write`, `req:review`, and `req:deprecate` all resolve to
- * the same value. A matcher that resolved to two *different* type
- * labels would be a registry bug and throws at module load.
+ * @see IssueTemplatesConfig
  */
-declare const PHASE_LABEL_TYPE_MAP: Readonly<Record<string, string>>;
+declare const DEFAULT_ISSUE_TEMPLATES_REQUIRE_REFERENCE = true;
 /**
- * Outcome of resolving a set of issue labels against
- * {@link PHASE_LABEL_TYPE_MAP}.
- *
- * - `"none"` — the labels carry no **recognised** phase label, so the
- *   invariant does not apply. Unrecognised `foo:bar` labels are
- *   consumer-specific and deliberately not policed.
- * - `"match"` — the recognised phase labels all imply one and the same
- *   `type:<bundle>` label, carried in `typeLabel`.
- * - `"ambiguous"` — the recognised phase labels imply two or more
- *   different `type:<bundle>` labels. Never auto-corrected; the caller
- *   flags the issue for human triage instead.
+ * Fully-resolved issue-templates settings. Every field is defaulted
+ * so downstream renderers can reason about a single canonical shape.
  */
-type PhaseLabelTypeOutcome = "none" | "match" | "ambiguous";
-/** Result of {@link resolveTypeLabelForLabels}. */
-interface PhaseLabelTypeResolution {
-    /** Which of the three outcomes applies. */
-    readonly outcome: PhaseLabelTypeOutcome;
-    /**
-     * The single implied `type:<bundle>` label (with the `type:` prefix)
-     * when `outcome` is `"match"`; `undefined` otherwise.
-     */
-    readonly typeLabel?: string;
-    /**
-     * Every distinct implied `type:<bundle>` label, sorted. Empty on
-     * `"none"`, one entry on `"match"`, two or more on `"ambiguous"`.
-     */
-    readonly candidateTypeLabels: ReadonlyArray<string>;
-    /**
-     * The subset of the input labels that matched a phase-label matcher,
-     * in input order. Empty on `"none"`.
-     */
-    readonly phaseLabels: ReadonlyArray<string>;
+interface ResolvedIssueTemplates {
+    readonly enabled: boolean;
+    readonly templatesPath: string;
+    readonly bundlePathPatterns: ReadonlyArray<string>;
+    readonly emitChecker: boolean;
+    readonly emitStarterDoc: boolean;
+    readonly requireReference: boolean;
 }
 /**
- * Resolve a single phase label to the `type:<bundle>` label its owning
- * bundle declares, or `undefined` when no bundle owns it.
+ * Resolve a (possibly absent) `IssueTemplatesConfig` into a canonical
+ * `ResolvedIssueTemplates` with every field filled in. Unset fields
+ * cascade from their documented defaults.
  *
- * Exact-match entries beat prefix entries: `req:write` is owned by
- * `requirements-writer` while the `req:` prefix is owned by
- * `requirements-analyst`. (Both currently declare `type:requirement`,
- * but the precedence is load-bearing for any future divergence.)
+ * Malformed configs — empty / whitespace-only or absolute
+ * `templatesPath`, empty `bundlePathPatterns`, empty /
+ * whitespace-only path entry — throw a descriptive `Error`.
  */
-declare function typeLabelForPhaseLabel(phaseLabel: string): string | undefined;
+declare function resolveIssueTemplates(config?: IssueTemplatesConfig): ResolvedIssueTemplates;
 /**
- * Resolve every label on an issue to the `type:<bundle>` label the
- * phase-label invariant requires it to carry.
+ * 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.
  *
- * The input is the issue's **full** label list — the resolver picks out
- * the recognised phase labels itself and ignores everything else
- * (`status:*`, `priority:*`, existing `type:*`, and any consumer label
- * that matches no bundle).
- */
-declare function resolveTypeLabelForLabels(labels: ReadonlyArray<string>): PhaseLabelTypeResolution;
-/**
- * Render the **Phase-label → `type:<bundle>` invariant** section of the
- * `orchestrator-conventions` rule. The matcher table is generated from
- * {@link PHASE_LABEL_TYPE_MAP}, so the documented pairing can never
- * drift from the pairing the sweep enforces.
+ * Malformed cases rejected here:
  *
- * Rows whose owning bundle appears in `excludeBundles` are dropped,
- * matching every other cross-bundle renderer.
+ * - `templatesPath` empty, whitespace-only, or absolute.
+ * - `bundlePathPatterns` not an array, empty, or contains an empty /
+ *   whitespace-only entry.
  */
-declare function renderPhaseTypeInvariantSection(excludeBundles?: ReadonlyArray<string>): string;
+declare function validateIssueTemplatesConfig(config?: IssueTemplatesConfig): ResolvedIssueTemplates;
 /**
- * Render the POSIX-shell half of the phase-label → `type:<bundle>`
- * invariant, derived from the same {@link PHASE_LABEL_TYPE_MAP} the
- * TypeScript accessors read. Emitted into `check-blocked.sh` so the
- * orchestrator's triage sweep and the consumer-runnable label audit
- * never carry a hand-copied second map.
+ * Render the full body for the `issue-templates-convention` rule
+ * shipped by the `base` bundle. The rule documents:
  *
- * Three functions are rendered:
+ * - 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).
  *
- * - `phase_label_type_of <label>` — echoes the `type:<bundle>` label a
- *   single phase label implies, or nothing. Exact-match branches are
- *   emitted before prefix branches so `case` ordering reproduces the
- *   exact-beats-prefix precedence.
- * - `phase_type_of` — reads an issue's labels (one per line) on stdin
- *   and emits `KEY=VALUE` assignments: `OUTCOME=none|match|ambiguous`,
- *   `TYPE_LABEL=` (match only), `CANDIDATE_TYPE_LABELS=` (ambiguous
- *   only), and `PHASE_LABELS=`.
- * - `is_conventional_type_label <label>` — returns 0 for a
- *   conventional-commit `type:*` label, i.e. the only labels the
- *   auto-correction is allowed to remove.
+ * When the convention is disabled, the rule renders a short stub.
  */
-declare function renderPhaseTypeInvariantShellHelpers(): string;
+declare function renderIssueTemplatesRuleContent(it: ResolvedIssueTemplates, hasDownstreamBundles?: boolean): string;
 /**
- * Return `true` when `typeLabel` (without the leading `type:` prefix)
- * is owned by any bundle in `excludedBundles`. Used by tier-table and
- * scheduled-task renderers to drop rows whose owning bundle has been
- * excluded.
+ * 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 isTypeLabelOwnedByExcluded(typeLabel: string, excludedBundles: ReadonlyArray<string>): boolean;
+declare function renderIssueTemplatesBundleHook(it: ResolvedIssueTemplates, bundleLabel: string): string;
 /**
- * Return `true` when `phaseLabel` is owned by any bundle in
- * `excludedBundles`. Matches against both prefix entries (with
- * trailing colon, e.g. `"company:"`) and exact-match entries (without
- * trailing colon, e.g. `"req:write"`). Used by the scope-gate
- * per-phase-override table renderer.
+ * Render the write-once starter issue-templates page — the frontmatter,
+ * the "How to use" preamble, a pointer at the always-regenerated
+ * label-set companion, and a single example template section. Exported
+ * so `AgentConfig` can emit it to disk when the consumer opts in via
+ * `emitStarterDoc: true`.
+ *
+ * The starter stays deliberately sparse on **bodies**: it documents the
+ * expected structure without committing the consumer to a particular
+ * body shape. The correct-by-construction **label sets** live in the
+ * companion page this one links to, which regenerates on every synth —
+ * so a write-once starter can never freeze a consumer on a stale label
+ * taxonomy.
  */
-declare function isPhaseLabelOwnedByExcluded(phaseLabel: string, excludedBundles: ReadonlyArray<string>): boolean;
+declare function renderIssueTemplatesStarterPage(it: ResolvedIssueTemplates): string;
+/*******************************************************************************
+ *
+ * Generated recipe stubs
+ *
+ ******************************************************************************/
 /**
- * Return `true` when the scheduled-task `taskId` is owned by any
- * bundle in `excludedBundles`. Used by the scheduled-tasks registry
- * filter to drop default entries pointing at an excluded bundle.
+ * One correct-by-construction recipe stub: a phase label plus every
+ * label the recipe must carry, all derived rather than hand-copied.
  */
-declare function isScheduledTaskOwnedByExcluded(taskId: string, excludedBundles: ReadonlyArray<string>): boolean;
+interface IssueTemplateRecipeStub {
+    /** The phase label the recipe files (e.g. `people:research`). */
+    readonly phaseLabel: string;
+    /** The `type:<bundle>` label the phase-label invariant requires. */
+    readonly typeLabel: string;
+    /** Bundle that contributes the phase label to `.github/labels.yml`. */
+    readonly bundleName: string;
+    /** The label's registry description, used as the section blurb. */
+    readonly description: string;
+    /** Effective `status:*` value for this phase. */
+    readonly status: IssueDefaultsStatus;
+    /** Effective `priority:*` value for this phase. */
+    readonly priority: IssueDefaultsPriority;
+    /** GitHub issue type the filed issue must be assigned. */
+    readonly issueType: GithubIssueType;
+}
 /**
- * Return `true` when at least one docs-emitting bundle is **not**
- * excluded. Used by the `section-index-pages` rule auto-suppression
- * gate — when this returns `false`, the rule is dropped from the
- * rendered rule map entirely.
+ * Derive one recipe stub per phase label the supplied bundles
+ * contribute to `.github/labels.yml`.
+ *
+ * A contributed label counts as a phase label exactly when
+ * `typeLabelForPhaseLabel` resolves it — i.e. when the canonical
+ * bundle-ownership map claims it. That is the *same* map that drives
+ * the label registry and the orchestrator's phase-label invariant, so
+ * a generated stub can never pair a phase label with the wrong
+ * `type:<bundle>` label. Consumer-specific labels no bundle owns are
+ * skipped rather than guessed at.
+ *
+ * Results are deduplicated by phase label (co-owned `req:*` labels are
+ * contributed by more than one requirements bundle) and sorted so the
+ * rendered page is stable across synth runs.
  */
-declare function hasAnyDocsEmittingBundle(excludedBundles: ReadonlyArray<string>): boolean;
+declare function collectIssueTemplateRecipeStubs(bundles: ReadonlyArray<AgentRuleBundle>, issueDefaults?: ResolvedIssueDefaults): ReadonlyArray<IssueTemplateRecipeStub>;
 /**
- * Return `true` when at least one downstream-issue-kind bundle is
- * **not** excluded. Used by the `issue-templates-convention`
- * auto-suppression gate — when this returns `false`, the rule body
- * renders the disabled-stub variant.
+ * Render the always-regenerated companion page that carries one
+ * label-correct `## Template: <phase-label>` stub per phase label the
+ * consumer's active bundles emit.
+ *
+ * Only the **label set** and the issue-type assignment are generated —
+ * title and body stay angle-bracket placeholders, so the page is a
+ * correct-by-construction starting point rather than a second source of
+ * truth for recipe bodies. Consumers move a stub into their
+ * hand-authored templates page and flesh out its body there; the
+ * label-consistency lint then holds both copies to the same pairing.
  */
-declare function hasAnyDownstreamIssueKindBundle(excludedBundles: ReadonlyArray<string>): boolean;
-
+declare function renderIssueTemplatesGeneratedPage(it: ResolvedIssueTemplates, stubs: ReadonlyArray<IssueTemplateRecipeStub>): string;
 /**
- * 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.
+ * 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`.
  *
- * Consuming projects can disable it with `excludeBundles: ["bcm-writer"]`.
- * `appliesWhen` always returns `true` per this batch's directive that
- * bundles assume peers are present.
+ * The script accepts the list of changed files as either:
  *
- * 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.
+ * 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.
  *
- * 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.
+ * 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 buildBcmWriterBundle(paths?: ResolvedAgentPaths, issueDefaults?: ResolvedIssueDefaults): AgentRuleBundle;
+declare function renderIssueTemplatesCheckerScript(it: ResolvedIssueTemplates): string;
 /**
- * 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;
+ * Render the `.claude/procedures/check-issue-template-labels.sh`
+ * companion lint. Exported so `AgentConfig` can emit it alongside the
+ * reference-don't-inline lint when the consumer opts in via
+ * `emitChecker: true`.
+ *
+ * Where `check-issue-templates.sh` polices *where* recipes live, this
+ * one polices *what they say*. For every
+ * `## Template: <phase-label>` section on the templates page, its
+ * router-style child pages, and the generated companion, it asserts:
+ *
+ * 1. The recipe passes `--label <phase-label>` — the heading and the
+ *    command agree.
+ * 2. It carries exactly one `type:*` label, and that label is the
+ *    `type:<bundle>` the phase-label invariant requires.
+ * 3. It carries a GitHub issue-type assignment step (the
+ *    `set-issue-type.sh` helper or the `updateIssueIssueType` GraphQL
+ *    flow it wraps) — an issue filed without one stays untyped forever.
+ *
+ * Sections whose heading matches no bundle-owned phase label are
+ * skipped, not failed: unrecognised `foo:bar` labels are
+ * consumer-specific and deliberately not policed, exactly as the
+ * orchestrator's invariant sweep treats them.
+ *
+ * The phase-label → type-label resolver is rendered from the same
+ * `PHASE_LABEL_TYPE_MAP` that drives the label registry and the
+ * orchestrator sweep, so the lint can never enforce a stale pairing.
+ */
+declare function renderIssueTemplateLabelsCheckerScript(it: ResolvedIssueTemplates): string;
 
 /**
- * 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/`).
+ * Fully-resolved requirement category subdirectory names, relative to
+ * the requirements root. Every property is required.
  */
-declare function buildBusinessModelsBundle(paths?: ResolvedAgentPaths, issueDefaults?: ResolvedIssueDefaults): 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;
-
+interface ResolvedRequirementCategoryDirs {
+    readonly business: string;
+    readonly functional: string;
+    readonly nonFunctional: string;
+    readonly technical: string;
+    readonly architecturalDecisions: string;
+    readonly security: string;
+    readonly data: string;
+    readonly integration: string;
+    readonly operational: string;
+    readonly ux: string;
+    readonly multiTenancy: string;
+}
 /**
- * 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.
+ * Fully-resolved agent output-path roots. Every property is required.
  *
- * 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.
+ * 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.
  */
-declare function buildCompanyProfileBundle(paths?: ResolvedAgentPaths, issueDefaults?: ResolvedIssueDefaults, tier?: AgentModel): AgentRuleBundle;
+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;
+    readonly requirementCategoryDirs: ResolvedRequirementCategoryDirs;
+}
 /**
- * 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`.
+ * Canonical default subdirectory name for each requirement category.
+ * These mirror the hardcoded `functional/`, `non-functional/`, … dirs
+ * that the requirements bundles emitted before category dirs became
+ * configurable, so the generated requirements snapshot is unchanged
+ * unless a consumer overrides an entry.
  */
-declare const companyProfileBundle: AgentRuleBundle;
-
+declare const DEFAULT_REQUIREMENT_CATEGORY_DIRS: ResolvedRequirementCategoryDirs;
 /**
- * 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.
+ * 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.
  *
- * 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.
+ * Consumers override the defaults by passing an `AgentPathsConfig`
+ * through `AgentConfigOptions.paths` and resolving it with
+ * `resolveAgentPaths()`. Every path-aware bundle threads the resolved
+ * struct through its rule / skill / sub-agent content, so an override
+ * propagates into the rendered output.
  */
-declare function buildCustomerProfileBundle(paths?: ResolvedAgentPaths, issueDefaults?: ResolvedIssueDefaults, tier?: AgentModel): AgentRuleBundle;
+declare const DEFAULT_AGENT_PATHS: ResolvedAgentPaths;
 /**
- * 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`.
+ * 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 const customerProfileBundle: AgentRuleBundle;
+declare function resolveAgentPaths(paths?: AgentPathsConfig): ResolvedAgentPaths;
 
 /**
- * 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.
+ * 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.
  *
- * 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).
+ * @see ProgressFilesConfig
  */
-declare function renderExtractApiProcedure(): string;
+declare const DEFAULT_PROGRESS_FILES_ENABLED = true;
 /**
- * `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`).
+ * 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.
+ *
+ * Lives at the top-level `.state/` directory so the path stays
+ * harness-neutral — any agent runtime (Claude Code, Cursor, a
+ * bespoke worker) can read and write the same progress files
+ * without having to scope under a harness-specific tree.
+ *
+ * @see ProgressFilesConfig
  */
-declare const extractApiProcedure: AgentProcedure;
+declare const DEFAULT_PROGRESS_FILES_STATE_DIR = ".state";
 /**
- * Render the shell body of the `.claude/procedures/check-links.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 wraps two external tools — `astro check` (internal
- * links) and `lychee` (external `https://…` URLs) — and normalizes
- * their per-finding output into a single JSON-array stream of
- * `{ url, docPath, line, kind, reason }` records on stdout. The
- * downstream docs-sync scan phase (#519/#520) consumes that stream
- * and decides which findings are advisory and which block the PR.
+ * 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`).
  *
- * Detection is **data**, not failure: the helper exits `0` whenever
- * a tool ran successfully, regardless of how many broken links it
- * reported. Non-zero exits are reserved for tool-level failures
- * (missing binary, config error, IO failure).
+ * 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.
  *
- * Exit codes: `0` success, `1` usage error or unreadable docs
- * root, `2` a required external tool is missing, `3` a tool ran
- * but exited non-zero for a reason other than broken-link
- * detection.
+ * @see ProgressFilesConfig
  */
-declare function renderCheckLinksProcedure(): string;
+declare const DEFAULT_PROGRESS_FILES_FILENAME_PATTERN = "<ISSUE_NUMBER>-progress.json";
 /**
- * `AgentProcedure` definition for `.claude/procedures/check-links.sh`.
- * Registered on the docs-sync bundle so it ships when the bundle is
- * force-included — matches the packaging of `extractApiProcedure`
- * above. Provides the link-integrity input the docs-sync scan phase
- * (#519/#520) consumes alongside API-extractor and TSDoc-coverage
- * findings.
+ * 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 checkLinksProcedure: AgentProcedure;
+declare const DEFAULT_PROGRESS_FILES_FORMAT: "json" | "markdown";
 /**
- * Render the shell body of the
- * `.claude/procedures/strip-tool-artifact-tags.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.
- *
- * Authoring agents intermittently leak tool-call wrapper *closing*
- * tags (`</content>`, `</invoke>`, occasionally `</parameter>`) as
- * trailing whole lines in the markdown they write. `astro check` and
- * CI link checks do not catch them. This helper strips those leaked
- * EOF artifact lines on write so they never reach the committed tree.
- *
- * Behaviour, mirroring `check-links.sh`'s defensive guards:
- *
- *   - Takes a single file-path argument.
- *   - Operates only when the file exists and its path is under
- *     `docs/src/content/docs/`. Any other path (or a missing file) is
- *     a silent no-op.
- *   - Removes **trailing whole lines** that are exactly `</content>`,
- *     `</invoke>`, or `</parameter>` (trailing whitespace on the line
- *     is tolerated), plus any blank lines that become trailing once
- *     the tags are removed, then leaves a single final newline.
- *   - Only whole-line EOF tags are stripped — legitimate inline
- *     `<...>` prose or fenced code is never touched.
- *   - Idempotent: a second run on an already-clean file changes
- *     nothing.
- *   - Never edits a file it did not need to change, and **always**
- *     exits 0 so a PostToolUse hook can never fail the tool call.
+ * 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.
  *
- * Exit code: always `0`. Diagnostics (if any) flow to stderr.
+ * @see ProgressFilesConfig
  */
-declare function renderStripToolArtifactTagsProcedure(): string;
+declare const DEFAULT_PROGRESS_FILES_STALE_AFTER_HOURS = 72;
 /**
- * `AgentProcedure` definition for
- * `.claude/procedures/strip-tool-artifact-tags.sh`. Registered on the
- * docs-sync bundle so it ships alongside `check-links.sh` when the
- * bundle is force-included, and chained into the base PostToolUse
- * Edit|Write hook so authored markdown is cleaned of leaked tool-call
- * artifact tags on write (#779).
+ * Allowed values for `ProgressFilesConfig.format`. Exported so
+ * consumers can reference the canonical set without hard-coding
+ * literals.
  */
-declare const stripToolArtifactTagsProcedure: AgentProcedure;
+declare const PROGRESS_FILES_FORMAT_VALUES: readonly ["json", "markdown"];
 /**
- * Render the shell body of the
- * `.claude/procedures/check-doc-samples.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 wraps the `compileFencedSamples` API exported from
- * `@codedrifters/configulator` (under `src/docs-sync/sample-compilation/`)
- * and emits a single JSON-array stream of failure records on stdout.
- * Detection is **data**, not failure: the helper exits `0` when the
- * compilation phase ran successfully, regardless of how many samples
- * failed to compile. Non-zero exits are reserved for tool-level
- * failures (missing binary, IO error, internal exception).
- *
- * Exit codes: `0` success, `1` usage error or unreadable docs root,
- * `2` a required binary is missing (`node` / `pnpm`), `3` the
- * compilation phase threw an unhandled exception.
+ * Fully-resolved progress-file settings. Every field is defaulted so
+ * downstream renderers can reason about a single canonical shape.
  */
-declare function renderCheckDocSamplesProcedure(): string;
+interface ResolvedProgressFiles {
+    readonly enabled: boolean;
+    readonly stateDir: string;
+    readonly filenamePattern: string;
+    readonly format: "json" | "markdown";
+    readonly cleanupOnComplete: boolean;
+    readonly staleAfterHours: number;
+}
 /**
- * `AgentProcedure` definition for
- * `.claude/procedures/check-doc-samples.sh`. Registered on the
- * docs-sync bundle so it ships when the bundle is force-included —
- * matches the packaging of `extractApiProcedure` and
- * `checkLinksProcedure` above. Provides the fenced-sample
- * compilation input the docs-sync scan phase (#520) consumes
- * alongside link integrity, API-extractor, TSDoc-coverage, and
- * doc-reference findings. Per the parent epic, fenced TS samples
- * that fail to compile are one of the two hard-block cases.
+ * Resolve a (possibly absent) `ProgressFilesConfig` into a canonical
+ * `ResolvedProgressFiles` with every field filled in. Unset fields
+ * cascade from their documented defaults.
+ *
+ * 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 checkDocSamplesProcedure: AgentProcedure;
+declare function resolveProgressFiles(config?: ProgressFilesConfig): ResolvedProgressFiles;
 /**
- * Docs-sync bundle — scaffolding release.
+ * 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.
  *
- * 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.
+ * Malformed cases rejected here:
  *
- * 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`.
+ * - `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 const docsSyncBundle: AgentRuleBundle;
-
+declare function validateProgressFilesConfig(config?: ProgressFilesConfig): ResolvedProgressFiles;
 /**
- * Builds the GitHub workflow bundle — auto-detected when the project
- * has a GitHub component.
+ * 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).
  *
- * The `build` policy conditions the PR-workflow build guidance on the
- * consuming project's Turborepo remote-cache configuration. When
- * omitted, the bundle ships the zero-remote-cache defaults
- * ({@link DEFAULT_BUILD_POLICY}), which emit no AWS-authentication
- * guidance at all.
+ * Exported so consumer-side scripts (or the `partial-resume-protocol`
+ * rule renderer) can compute the on-disk path deterministically.
  */
-declare function buildGithubWorkflowBundle(buildPolicy?: ResolvedBuildPolicy): AgentRuleBundle;
+declare function renderProgressFileName(pf: ResolvedProgressFiles, issueNumber: number | string): string;
 /**
- * `github-workflow` bundle built with the default (no remote cache)
- * build policy. Preserved for backward compatibility with tests and
- * consumers that import the const directly. Prefer
- * `buildGithubWorkflowBundle(buildPolicy)` when the consuming
- * project's Turborepo configuration is in scope.
+ * Resolve the runtime path (directory + filename) for a progress file
+ * given an issue number and a resolved config.
  */
-declare const githubWorkflowBundle: AgentRuleBundle;
-
+declare function renderProgressFilePath(pf: ResolvedProgressFiles, issueNumber: number | string): string;
 /**
- * Build the industry-discovery bundle with the supplied resolved paths.
+ * Render the full body for the `progress-file-convention` rule shipped
+ * by the `base` bundle. The rule documents:
  *
- * 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.
+ * - 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.
+ *
+ * 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 function buildIndustryDiscoveryBundle(paths?: ResolvedAgentPaths, issueDefaults?: ResolvedIssueDefaults): AgentRuleBundle;
+declare function renderProgressFilesRuleContent(pf: ResolvedProgressFiles): string;
 /**
- * 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`.
+ * 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 industryDiscoveryBundle: AgentRuleBundle;
+declare function renderProgressFilesBundleHook(pf: ResolvedProgressFiles, bundleLabel: string): string;
 
 /**
- * Jest bundle — auto-detected when Jest is in dependencies.
+ * 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 jestBundle: AgentRuleBundle;
-
+declare const DEFAULT_SHARED_EDITING_ENABLED = true;
 /**
- * Maintenance-audit bundle — enabled by default.
+ * 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.
  *
- * Consuming projects can disable it with
- * `excludeBundles: ["maintenance-audit"]`. `appliesWhen` always returns
- * `true` per this batch's directive that bundles assume peers are
- * present.
+ * The defaults cover the registry / index files every configulator
+ * consumer ships by convention:
  *
- * 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, issueDefaults?: ResolvedIssueDefaults, tier?: AgentModel): 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;
-
-/**
- * Build the meeting-analysis bundle with the supplied default sub-agent
- * model tier. The tier knob lets consumers globally demote the
- * `meeting-analyst` sub-agent to BALANCED (sonnet) — which is the
- * post-2026-05-08 default — without forking the bundle.
- */
-declare function buildMeetingAnalysisBundle(tier?: AgentModel): AgentRuleBundle;
-/**
- * Default-tier instance of the meeting-analysis 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.defaultAgentTier`.
+ * - 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 meetingAnalysisBundle: AgentRuleBundle;
-
+declare const DEFAULT_SHARED_INDEX_PATHS: ReadonlyArray<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`.
+ * 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 RunRatioConfig
+ * @see SharedEditingConfig
  */
-declare const DEFAULT_DISPATCH_TO_HOUSEKEEPING_RATIO = 4;
+declare const DEFAULT_SHARED_EDITING_CONFLICT_STRATEGY: "rebase" | "merge";
 /**
- * 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.
+ * 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 RunRatioConfig
+ * @see SharedEditingConfig
  */
-declare const DEFAULT_STATE_FILE_PATH = ".state/orchestrator-runs.json";
+declare const DEFAULT_SHARED_EDITING_VERIFY_COMMIT = true;
 /**
- * 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.
+ * 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 RunRatioConfig
+ * @see SharedEditingConfig
  */
-declare const DEFAULT_DISPATCH_MODEL = "opus";
+declare const DEFAULT_SHARED_EDITING_EMIT_HELPER = false;
 /**
- * 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
+ * Allowed values for `SharedEditingConfig.conflictStrategy`. Exported
+ * so consumers can reference the canonical set without hard-coding
+ * literals.
  */
-declare const DEFAULT_HOUSEKEEPING_MODEL = "sonnet";
+declare const SHARED_EDITING_CONFLICT_STRATEGY_VALUES: readonly ["rebase", "merge"];
 /**
- * Fully-resolved run-ratio settings. Every field is defaulted so
+ * Fully-resolved shared-editing settings. Every field is defaulted so
  * downstream renderers can reason about a single canonical shape.
  */
-interface ResolvedRunRatio {
+interface ResolvedSharedEditing {
     readonly enabled: boolean;
-    readonly ratio: number;
-    readonly stateFilePath: string;
-    readonly dispatchModel: string;
-    readonly housekeepingModel: string;
+    readonly sharedIndexPaths: ReadonlyArray<string>;
+    readonly verifyCommit: boolean;
+    readonly conflictStrategy: "rebase" | "merge";
+    readonly emitHelper: boolean;
 }
 /**
- * Resolve a (possibly absent) `RunRatioConfig` into a canonical
- * `ResolvedRunRatio` with every field filled in. Unset fields
+ * Resolve a (possibly absent) `SharedEditingConfig` into a canonical
+ * `ResolvedSharedEditing` 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.
+ * Malformed configs — empty / whitespace-only `sharedIndexPaths`
+ * entry, unknown `conflictStrategy` — throw a descriptive `Error`.
  */
-declare function resolveRunRatio(config?: RunRatioConfig): ResolvedRunRatio;
+declare function resolveSharedEditing(config?: SharedEditingConfig): ResolvedSharedEditing;
 /**
  * Synth-time validation hook. Throws a descriptive `Error` when the
- * supplied `RunRatioConfig` is malformed. Called by
+ * supplied `SharedEditingConfig` 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.
+ * 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:
  *
- * - `ratio` non-integer, zero, or negative.
- * - `stateFilePath` empty / whitespace-only, or an absolute path
- *   (the state file must live inside the repo).
+ * - `sharedIndexPaths` contains an empty / whitespace-only entry, or
+ *   the array is supplied but empty.
+ * - `conflictStrategy` is not one of `"rebase"` / `"merge"`.
  */
-declare function validateRunRatioConfig(config?: RunRatioConfig): ResolvedRunRatio;
+declare function validateSharedEditingConfig(config?: SharedEditingConfig): ResolvedSharedEditing;
 /**
- * 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.
+ * Render the full body for the `shared-editing-safety` rule shipped
+ * by the `base` bundle. The rule documents:
  *
- * 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.
+ * - 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 classifyRun(runCounter: number, ratio: ResolvedRunRatio): "dispatch" | "housekeeping";
+declare function renderSharedEditingRuleContent(se: ResolvedSharedEditing): string;
 /**
- * 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.
+ * 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 renderRunRatioSection(ratio: ResolvedRunRatio): string;
+declare function renderSharedEditingBundleHook(se: ResolvedSharedEditing, bundleLabel: string): string;
 /**
- * Render a shell-script snippet embedded in `check-blocked.sh`. The
- * snippet declares a `run_counter_tick()` function that:
+ * 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`.
  *
- * 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.
+ * The script takes two positional arguments:
  *
- * 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.
+ * 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 renderRunRatioShellHelpers(ratio: ResolvedRunRatio): string;
+declare function renderSharedEditingHelperScript(_se: ResolvedSharedEditing): 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.
+ * 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 ScheduledTasksConfig
- */
-declare const SCHEDULED_TASK_MODEL_VALUES: readonly ["opus", "sonnet", "haiku"];
-type ScheduledTaskModel = (typeof SCHEDULED_TASK_MODEL_VALUES)[number];
-/**
- * Valid `kind` values for a scheduled-task entry. See
- * `ScheduledTaskEntry.kind` for semantics.
+ * @see SkillEvalsConfig
  */
-declare const SCHEDULED_TASK_KIND_VALUES: readonly ["issue-worker", "pipeline"];
-type ScheduledTaskKind = (typeof SCHEDULED_TASK_KIND_VALUES)[number];
+declare const DEFAULT_SKILL_EVALS_ENABLED = true;
 /**
- * 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`.
+ * 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`.
  *
- * @see ScheduledTasksConfig
+ * Defaults to `.claude/skills`, which matches the location every
+ * configulator-managed project ships skills to on disk.
+ *
+ * @see SkillEvalsConfig
  */
-declare const DEFAULT_SCHEDULED_TASKS_ROOT = ".claude/scheduled-tasks";
+declare const DEFAULT_SKILL_EVALS_SKILLS_ROOT = ".claude/skills";
 /**
- * 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.
+ * 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 ScheduledTasksConfig
+ * @see SkillEvalsConfig
  */
-declare const DEFAULT_OFF_PEAK_CRON_EXAMPLE = "3,23,43 0-7,14-23 * * *";
+declare const DEFAULT_PRODUCT_CONTEXT_PATH = "docs/src/content/docs/project-context.md";
 /**
- * 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.
+ * 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
  */
-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;
-    /**
-     * Target sub-agent name (e.g. `company-profile-analyst`). The task's
-     * rendered prompt points operators at `.claude/agents/<agent>.md`.
-     */
-    readonly agent: string;
-    /**
-     * Human-readable agent label for rendered tables and frontmatter
-     * descriptions (e.g. `"Company Profile"`).
-     */
-    readonly agentLabel: string;
-    /**
-     * 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.
-     */
-    readonly typeLabel: string;
-    /**
-     * 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.
-     */
-    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;
-    /**
-     * Discriminator controlling how the SKILL.md body and the registered-
-     * tasks table cell are rendered. `"issue-worker"` (default) emits the
-     * standard delegate-to-issue-worker prompt; `"pipeline"` emits a
-     * pipeline-manager prompt that points the operator at the target
-     * sub-agent's full workflow and renders `_(none — pipeline manager)_`
-     * for the type-label cell.
-     */
-    readonly kind: ScheduledTaskKind;
-}
+declare const DEFAULT_REQUIRE_PRODUCT_CONTEXT = true;
 /**
- * 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`.
+ * 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`.
  *
- * 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.
+ * @see SkillEvalsConfig
  */
-declare const DEFAULT_SCHEDULED_TASK_ENTRIES: ReadonlyArray<ResolvedScheduledTask>;
+declare const DEFAULT_SKILL_EVALS_EMIT_RUNNER = false;
 /**
- * Fully-resolved scheduled-tasks settings. Every field is defaulted so
+ * Fully-resolved skill-evals settings. Every field is defaulted so
  * downstream renderers can reason about a single canonical shape.
  */
-interface ResolvedScheduledTasks {
+interface ResolvedSkillEvals {
     readonly enabled: boolean;
-    readonly root: string;
-    readonly tasks: ReadonlyArray<ResolvedScheduledTask>;
+    readonly skillsRoot: string;
+    readonly productContextPath: string;
+    readonly requireProductContext: boolean;
+    readonly emitRunner: boolean;
 }
 /**
- * Resolve a (possibly absent) `ScheduledTasksConfig` into a canonical
- * `ResolvedScheduledTasks` with every field filled in. Unset fields
+ * Resolve a (possibly absent) `SkillEvalsConfig` into a canonical
+ * `ResolvedSkillEvals` with every field filled in. Unset fields
  * cascade from their documented defaults.
  *
- * The resolver merges three sources in this order:
+ * 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 temporal-framing convention. When no
+ * config is supplied the convention ships **enabled** so every
+ * configulator-consuming repo's analyst agents apply the
+ * "as of [date]" qualifier rule.
+ *
+ * @see TemporalFramingConfig
+ */
+declare const DEFAULT_TEMPORAL_FRAMING_ENABLED = true;
+/**
+ * Default path globs the rule applies to — every Markdown file under
+ * the profile / research subtrees of a repo's Starlight docs site.
+ * Consumers may override the list when their content layout differs.
+ *
+ * Out-of-scope locations (meeting notes, requirements, the
+ * project-context page) are excluded by design: their own dating
+ * conventions (file-name date prefix, version frontmatter, living
+ * snapshot under direct human review) already anchor the temporal
+ * meaning of their content.
+ *
+ * @see TemporalFramingConfig
+ */
+declare const DEFAULT_TEMPORAL_FRAMING_PATHS: ReadonlyArray<string>;
+/**
+ * The five canonical time-sensitive claim categories surfaced by the
+ * May 2026 sampled drift audit. The category names are shipped as the
+ * key set for `TemporalFramingConfig.cadences` so consumers can dial
+ * the per-category refresh cadence without inventing their own
+ * category names.
+ */
+declare const TEMPORAL_FRAMING_CATEGORY_VALUES: readonly ["ownership", "company-leadership", "regulatory-status", "litigation", "dated-metrics"];
+type TemporalFramingCategory = (typeof TEMPORAL_FRAMING_CATEGORY_VALUES)[number];
+/**
+ * Default per-category refresh cadences (in days). Fast-decay claims
+ * (regulatory status, litigation) carry a 30-day cadence because a
+ * single press release can invalidate them between scheduled refresh
+ * passes. Slow-decay claims (ownership, dated metrics from press
+ * releases or filings) carry a 180-day cadence — material changes
+ * still happen but rarely outpace a half-yearly refresh. Leadership
+ * tenure sits in the middle at 90 days.
+ *
+ * Consumers may override any subset of categories via
+ * `TemporalFramingConfig.cadences`; unspecified entries fall through
+ * to these defaults.
+ */
+declare const DEFAULT_TEMPORAL_FRAMING_CADENCES: {
+    readonly [K in TemporalFramingCategory]: number;
+};
+/**
+ * Default for whether the convention emits the
+ * `.claude/procedures/check-temporal-framing.sh` lint script to disk.
+ * Disabled by default — consumers opt in when they want a hard
+ * pre-commit or CI gate. The rule body itself ships unconditionally
+ * regardless of the lint script.
+ *
+ * @see TemporalFramingConfig
+ */
+declare const DEFAULT_TEMPORAL_FRAMING_EMIT_CHECKER = false;
+/**
+ * Fully-resolved temporal-framing settings. Every field is defaulted
+ * so downstream renderers can reason about a single canonical shape.
+ */
+interface ResolvedTemporalFraming {
+    readonly enabled: boolean;
+    readonly paths: ReadonlyArray<string>;
+    readonly cadences: {
+        readonly [K in TemporalFramingCategory]: number;
+    };
+    readonly emitChecker: boolean;
+}
+/**
+ * Resolve a (possibly absent) `TemporalFramingConfig` into a canonical
+ * `ResolvedTemporalFraming` with every field filled in. Unset fields
+ * cascade from their documented defaults.
+ *
+ * Malformed configs throw a descriptive `Error`:
+ *
+ * - `paths` containing empty / whitespace-only entries.
+ * - `cadences` containing non-integer or non-positive values.
+ */
+declare function resolveTemporalFraming(config?: TemporalFramingConfig): ResolvedTemporalFraming;
+/**
+ * Synth-time validation hook. Throws a descriptive `Error` when the
+ * supplied `TemporalFramingConfig` is malformed. Called by
+ * `AgentConfig.preSynthesize` before any rendering so a misconfigured
+ * convention fails the build instead of silently shipping broken
+ * paths or cadences. Returns the resolved config unchanged so callers
+ * can write `const tf = validateTemporalFramingConfig(config)` in
+ * one line.
+ *
+ * Malformed cases rejected here:
+ *
+ * - `paths` containing empty or whitespace-only entries.
+ * - `cadences` containing non-integer or non-positive values.
+ */
+declare function validateTemporalFramingConfig(config?: TemporalFramingConfig): ResolvedTemporalFraming;
+/**
+ * Render the body for the `temporal-framing-convention` rule shipped
+ * by the `base` bundle. The rule documents:
+ *
+ * - The "as of [date]" qualifier requirement on time-sensitive claims.
+ * - The five canonical time-sensitive claim categories.
+ * - Refresh-agent behaviour (grep for `as of `, re-verify against the
+ *   category-specific cadence).
+ * - The scope of applicability (profile / research sections only).
+ *
+ * When the convention is disabled, the rule renders a short stub that
+ * tells agents the project does not enforce explicit temporal
+ * qualifiers and that staleness is caught by review alone.
+ */
+declare function renderTemporalFramingRuleContent(tf: ResolvedTemporalFraming): string;
+/**
+ * Render the `.claude/procedures/check-temporal-framing.sh` helper
+ * script. Exported so `AgentConfig` can register it 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 configured path
+ * pattern and contains time-sensitive framing (present-tense forms of
+ * the canonical category triggers) but lacks an `as of ` qualifier
+ * anywhere in the file. The lint is intentionally coarse — file-level
+ * not line-level — so the cost of running it on every PR stays low.
+ */
+declare function renderTemporalFramingCheckerScript(tf: ResolvedTemporalFraming): string;
+
+/**
+ * Fully-resolved settings for the five config-driven convention rules
+ * the base bundle owns. Every field is already resolved, so
+ * `buildBaseBundle` can seed each rule's final content up front rather
+ * than shipping default content that a later pass has to rewrite.
+ *
+ * Seeding before the rule map exists is what lets `ruleExtensions`
+ * appends and consumer-supplied same-name `rules` entries compose with
+ * a consumer's convention overrides instead of being clobbered by
+ * them. This mirrors the `pr-review-policy` rule, which has always
+ * resolved its policy inside `buildPrReviewBundle`.
+ */
+interface ResolvedBaseConventions {
+    readonly progressFiles: ResolvedProgressFiles;
+    readonly sharedEditing: ResolvedSharedEditing;
+    readonly temporalFraming: ResolvedTemporalFraming;
+    readonly skillEvals: ResolvedSkillEvals;
+    readonly issueTemplates: ResolvedIssueTemplates;
+    /**
+     * Whether any bundle contributing a downstream issue kind survived
+     * `excludeBundles`. When false the issue-templates rule renders its
+     * disabled stub — the convention has nothing left to enforce.
+     */
+    readonly hasDownstreamIssueKindBundles: boolean;
+}
+/**
+ * The convention settings the base bundle ships when the consumer
+ * supplies no override. Exported so callers can spread a partial
+ * override over the documented defaults.
+ */
+declare const DEFAULT_BASE_CONVENTIONS: ResolvedBaseConventions;
+/**
+ * Base bundle — always included unless `includeBaseRules: false`.
+ * Contains project-overview, interaction-style, and general-conventions rules.
+ */
+declare function buildBaseBundle(paths?: ResolvedAgentPaths, conventions?: ResolvedBaseConventions): 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;
+
+/**
+ * Fully-resolved build policy for the consuming project.
+ *
+ * The generated agent guidance around `pnpm build:all` used to assert
+ * unconditionally that the command "requires the user to be
+ * authenticated to AWS on the prod account used for Turborepo remote
+ * caching (`readonlyaccess-prod-525259625215-us-east-1` profile)".
+ * Both halves of that sentence were wrong for most consumers:
+ *
+ *   1. The AWS-auth requirement only exists when a Turborepo **remote
+ *      cache** is configured. Consumers running a local cache only
+ *      (`turbo.json` with just a `cacheDir`) need no credentials at
+ *      all, and agents that believed otherwise aborted mid-flow —
+ *      three lost-work incidents in `codedrifters/openhi-planning`.
+ *   2. The profile name was this repository's own profile, baked
+ *      verbatim into every consumer's generated text.
+ *
+ * This struct carries the two facts the rule renderers need, derived
+ * from the project's actual {@link TurboRepo} configuration, so the
+ * guidance is true for whichever consumer it renders into.
+ *
+ * @see resolveBuildPolicy
+ */
+interface ResolvedBuildPolicy {
+    /**
+     * Whether a Turborepo **remote** cache is configured on the project.
+     *
+     * `false` means either there is no {@link TurboRepo} component at
+     * all, or it was constructed without `remoteCacheOptions` — in both
+     * cases `pnpm build:all` needs no AWS credentials and the generated
+     * guidance must not claim otherwise.
+     */
+    readonly remoteCacheEnabled: boolean;
+    /**
+     * Local AWS profile name used to fetch the remote-cache endpoint and
+     * token, taken from `remoteCacheOptions.profileName`.
+     *
+     * `undefined` whenever {@link remoteCacheEnabled} is `false`. Never
+     * hard-code a profile name in rule content — read it from here so
+     * each consumer's generated text names its own profile.
+     */
+    readonly awsProfileName?: string;
+}
+/**
+ * Build policy for a project with no Turborepo remote cache — the
+ * zero-config default. Rule renderers that receive this omit the
+ * AWS-authentication guidance entirely rather than asserting a
+ * credential requirement that does not exist.
+ */
+declare const DEFAULT_BUILD_POLICY: ResolvedBuildPolicy;
+/**
+ * Derives the {@link ResolvedBuildPolicy} for a project by inspecting
+ * its {@link TurboRepo} component.
+ *
+ * Auto-detection, not opt-in: `remoteCacheOptions` being `undefined`
+ * *is* the "remote cache disabled" signal — `TurboRepo.renderRunArgs`
+ * already branches on exactly the same condition when it decides
+ * whether to emit `--api` / `--token` / `--team` flags. Consumers get
+ * accurate guidance with no extra configuration.
+ *
+ * Call this lazily (at synthesis time), not from a constructor: the
+ * `TurboRepo` component must already be attached to the project for
+ * detection to succeed.
+ */
+declare function resolveBuildPolicy(project: Project): ResolvedBuildPolicy;
+
+/**
+ * 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 = ".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];
+/**
+ * Valid `kind` values for a scheduled-task entry. See
+ * `ScheduledTaskEntry.kind` for semantics.
+ */
+declare const SCHEDULED_TASK_KIND_VALUES: readonly ["issue-worker", "pipeline"];
+type ScheduledTaskKind = (typeof SCHEDULED_TASK_KIND_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;
+    /**
+     * Target sub-agent name (e.g. `company-profile-analyst`). The task's
+     * rendered prompt points operators at `.claude/agents/<agent>.md`.
+     */
+    readonly agent: string;
+    /**
+     * Human-readable agent label for rendered tables and frontmatter
+     * descriptions (e.g. `"Company Profile"`).
+     */
+    readonly agentLabel: string;
+    /**
+     * 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.
+     */
+    readonly typeLabel: string;
+    /**
+     * 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.
+     */
+    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;
+    /**
+     * Discriminator controlling how the SKILL.md body and the registered-
+     * tasks table cell are rendered. `"issue-worker"` (default) emits the
+     * standard delegate-to-issue-worker prompt; `"pipeline"` emits a
+     * pipeline-manager prompt that points the operator at the target
+     * sub-agent's full workflow and renders `_(none — pipeline manager)_`
+     * for the type-label cell.
+     */
+    readonly kind: ScheduledTaskKind;
+}
+/**
+ * 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`.
@@ -5846,1143 +6150,1056 @@ declare function buildCheckBlockedProcedure(tiers: ReadonlyArray<ResolvedAgentTi
  * `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, 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.
- *
- * The `runRatio` parameter is retained for API compatibility but is
- * no longer rendered into the conventions content — the orchestrator
- * runs a single linear cycle on every invocation, so the
- * dispatch/housekeeping ratio convention was retired. See Phase B
- * (PR review sweep) in `.claude/agents/orchestrator.md` for the
- * replacement workflow.
- */
-declare function buildOrchestratorConventionsContent(tiers: ReadonlyArray<ResolvedAgentTier>, scopeGate?: ResolvedScopeGate, _runRatio?: ResolvedRunRatio, scheduledTasks?: ResolvedScheduledTasks, unblockDependents?: ResolvedUnblockDependents, excludeBundles?: ReadonlyArray<string>): 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,
- * and scheduled-tasks config. Called by `AgentConfig.preSynthesize`.
- *
- * Returns the resolved tier table, scope gate, run ratio, and
- * scheduled-tasks config alongside both rendered artifacts so callers
- * can splice them into their rule map and procedure map in a single
- * pass.
- *
- * The `runRatio` parameter is retained for API compatibility but no
- * longer feeds the rendered conventions content or the
- * `check-blocked.sh` script — the orchestrator runs a single linear
- * cycle on every invocation, so the run-counter / `tick` subcommand
- * were retired.
- */
-declare function resolveOrchestratorAssets(tierConfig?: AgentTierConfig, scopeGateConfig?: ScopeGateConfig, runRatioConfig?: RunRatioConfig, scheduledTasksConfig?: ScheduledTasksConfig, unblockDependentsConfig?: UnblockDependentsConfig, excludeBundles?: ReadonlyArray<string>): {
-    readonly tiers: ReadonlyArray<ResolvedAgentTier>;
-    readonly scopeGate: ResolvedScopeGate;
-    readonly runRatio: ResolvedRunRatio;
-    readonly scheduledTasks: ResolvedScheduledTasks;
-    readonly unblockDependents: ResolvedUnblockDependents;
-    readonly conventionsContent: string;
-    readonly procedure: AgentProcedure;
-    readonly unblockDependentsProcedure: AgentProcedure;
-};
-/*******************************************************************************
- *
- * Bundle definition
- *
- ******************************************************************************/
-declare const orchestratorBundle: AgentRuleBundle;
-
-/**
- * People-profile bundle — enabled by default.
- *
- * 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`).
- *
- * 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 function buildPeopleProfileBundle(paths?: ResolvedAgentPaths, issueDefaults?: ResolvedIssueDefaults, tier?: AgentModel): 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;
-
-/**
- * PNPM bundle — auto-detected when the PnpmWorkspace component is present.
- */
-declare const pnpmBundle: AgentRuleBundle;
-
-/**
- * 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`.
- *
- * @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/`.
- *
- * 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.
- *
- * @see IssueTemplatesConfig
- */
-declare const DEFAULT_ISSUE_TEMPLATES_PATH = "docs/src/content/docs/agents/issue-templates.md";
-/**
- * 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 locations bundle-like content lives in a
- * generic configulator-consuming repo:
- *
- * - `.claude/agents/**.md` / `.claude/skills/**` — agent and skill
- *   prompts in consuming repos that don't re-export configulator
- *   bundles.
- *
- * Repos that **also** host configulator's own bundle source as a
- * workspace package (only `codedrifters/packages` itself) should
- * append `packages/@codedrifters/configulator/src/agent/bundles/**.ts`
- * via `IssueTemplatesConfig.bundlePathPatterns` to lint those bundle
- * sources too. The default omits that pattern because it is dead
- * weight (matches nothing) in any other consumer.
- *
- * Consumers can replace the list outright via `bundlePathPatterns`
- * when their agent sources live elsewhere.
- *
- * @see IssueTemplatesConfig
- */
-declare const DEFAULT_ISSUE_TEMPLATES_BUNDLE_PATH_PATTERNS: ReadonlyArray<string>;
-/**
- * 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.
- *
- * 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.
- *
- * @see IssueTemplatesConfig
- */
-declare const DEFAULT_ISSUE_TEMPLATES_EMIT_CHECKER = false;
-/**
- * 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 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.
- *
- * 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`.
- *
- * @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:
+ ******************************************************************************/
+declare function buildUnblockDependentsProcedure(unblockDependents?: ResolvedUnblockDependents): AgentProcedure;
+/**
+ * Build the orchestrator-conventions rule content for a given resolved
+ * tier table, scope gate, 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.
  *
- * - `templatesPath` empty, whitespace-only, or absolute.
- * - `bundlePathPatterns` not an array, empty, or contains an empty /
- *   whitespace-only entry.
+ * Every optional parameter defaults to the bundle's built-in default
+ * when the caller omits it.
+ *
+ * The `runRatio` parameter is retained for API compatibility but is
+ * no longer rendered into the conventions content — the orchestrator
+ * runs a single linear cycle on every invocation, so the
+ * dispatch/housekeeping ratio convention was retired. See Phase B
+ * (PR review sweep) in `.claude/agents/orchestrator.md` for the
+ * replacement workflow.
  */
-declare function validateIssueTemplatesConfig(config?: IssueTemplatesConfig): ResolvedIssueTemplates;
+declare function buildOrchestratorConventionsContent(tiers: ReadonlyArray<ResolvedAgentTier>, scopeGate?: ResolvedScopeGate, _runRatio?: ResolvedRunRatio, scheduledTasks?: ResolvedScheduledTasks, unblockDependents?: ResolvedUnblockDependents, excludeBundles?: ReadonlyArray<string>): string;
 /**
- * Render the full body for the `issue-templates-convention` rule
- * shipped by the `base` bundle. The rule documents:
+ * 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,
+ * and scheduled-tasks config. Called by `AgentConfig.preSynthesize`.
  *
- * - 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).
+ * Returns the resolved tier table, scope gate, run ratio, and
+ * scheduled-tasks config alongside both rendered artifacts so callers
+ * can splice them into their rule map and procedure map in a single
+ * pass.
  *
- * When the convention is disabled, the rule renders a short stub.
+ * The `runRatio` parameter is retained for API compatibility but no
+ * longer feeds the rendered conventions content or the
+ * `check-blocked.sh` script — the orchestrator runs a single linear
+ * cycle on every invocation, so the run-counter / `tick` subcommand
+ * were retired.
  */
-declare function renderIssueTemplatesRuleContent(it: ResolvedIssueTemplates, hasDownstreamBundles?: boolean): string;
+declare function resolveOrchestratorAssets(tierConfig?: AgentTierConfig, scopeGateConfig?: ScopeGateConfig, runRatioConfig?: RunRatioConfig, scheduledTasksConfig?: ScheduledTasksConfig, unblockDependentsConfig?: UnblockDependentsConfig, excludeBundles?: ReadonlyArray<string>): {
+    readonly tiers: ReadonlyArray<ResolvedAgentTier>;
+    readonly scopeGate: ResolvedScopeGate;
+    readonly runRatio: ResolvedRunRatio;
+    readonly scheduledTasks: ResolvedScheduledTasks;
+    readonly unblockDependents: ResolvedUnblockDependents;
+    readonly conventionsContent: string;
+    readonly procedure: AgentProcedure;
+    readonly unblockDependentsProcedure: AgentProcedure;
+};
 /**
- * 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.
+ * Fully-resolved settings that feed the `orchestrator-conventions`
+ * rule. Every field is already resolved, so `buildOrchestratorBundle`
+ * can seed the rule's final content up front rather than shipping
+ * default content that a later pass has to rewrite.
  */
-declare function renderIssueTemplatesBundleHook(it: ResolvedIssueTemplates, bundleLabel: string): string;
+interface ResolvedOrchestratorConventions {
+    readonly tiers: ReadonlyArray<ResolvedAgentTier>;
+    readonly scopeGate: ResolvedScopeGate;
+    readonly runRatio: ResolvedRunRatio;
+    readonly scheduledTasks: ResolvedScheduledTasks;
+    readonly unblockDependents: ResolvedUnblockDependents;
+    /**
+     * Bundle names the consumer excluded. Rows owned by an excluded
+     * bundle are dropped from the rendered tier table, scope-gate
+     * overrides, and scheduled-tasks registry.
+     */
+    readonly excludeBundles: ReadonlyArray<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.
+ * The orchestrator-conventions settings the bundle ships when the
+ * consumer supplies no override.
  */
-declare function renderIssueTemplatesStarterPage(_it: ResolvedIssueTemplates): string;
+declare const DEFAULT_ORCHESTRATOR_CONVENTIONS: ResolvedOrchestratorConventions;
 /**
- * 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:
+ * Build the `orchestrator` bundle with the consumer's resolved tier,
+ * scope-gate, run-ratio, scheduled-tasks, and unblock-dependents
+ * settings already baked into the `orchestrator-conventions` rule
+ * content.
  *
- * 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.
+ * Resolving here — rather than rewriting the rule after the rule map
+ * has been assembled — is what lets a consumer's
+ * `ruleExtensions["orchestrator-conventions"]` append (or a same-name
+ * `agentConfig.rules` entry) survive alongside a tier / scope-gate /
+ * scheduled-tasks override. The two features compose because the rule
+ * enters the map already carrying the consumer's resolved settings.
  *
- * 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).
+ * When the argument is omitted the bundle ships with the documented
+ * defaults baked in, identical to the `orchestratorBundle` const below.
  */
-declare function renderIssueTemplatesCheckerScript(it: ResolvedIssueTemplates): string;
+declare function buildOrchestratorBundle(conventions?: ResolvedOrchestratorConventions): AgentRuleBundle;
+/**
+ * Default-config instance of the orchestrator bundle, preserved for
+ * backward compatibility with consumers that import the const
+ * directly. The factory above is the canonical entry point when a
+ * consumer supplies tier / scope-gate / scheduled-tasks overrides.
+ */
+declare const orchestratorBundle: AgentRuleBundle;
 
 /**
- * The GitHub **issue type** vocabulary this convention assigns.
- *
- * An issue type is a first-class GitHub field (Epic / Feature / Bug /
- * Task) and is a completely different axis from the `type:*` **label**
- * taxonomy:
+ * Default path globs that exempt a PR from the `human-required.size`
+ * rule. The policy walks every changed path in the PR and skips
+ * rule #6 (size threshold) when **every** path matches at least one
+ * glob in this list. Doc-only PRs routinely exceed the 500-insertion
+ * threshold (large migrations, bulk additions, refresh passes) but
+ * carry no production risk that warrants forcing a human reviewer.
  *
- * - `type:<bundle>` / `type:<conventional-commit>` — a *label*. Routing
- *   and dedup signal. Owned by {@link BUNDLE_OWNERSHIP} and set with
- *   `gh issue create --label`.
- * - GitHub issue type — a *field*. Human triage, Epic-relationship
- *   tracking, and reporting signal. `gh issue create` cannot set it, so
- *   it is applied immediately after creation via the
- *   `updateIssueIssueType` GraphQL mutation.
+ * The default exempts the entire `docs/**` tree — every consumer of
+ * configulator places its Starlight docs site there. Consumers can
+ * extend this list (e.g. add `docs/research/**` if doc-style research
+ * notes live outside the Starlight tree) by passing
+ * `prReviewPolicy.autoMerge.pathsExemptFromSize`.
  *
- * Conflating the two is the single most common mistake in this area, so
- * both this module and the prose it renders keep them explicitly apart.
+ * @see PrReviewPolicyConfig
+ * @see PrReviewAutoMergeConfig.pathsExemptFromSize
  */
-declare const GITHUB_ISSUE_TYPES: readonly ["Epic", "Feature", "Bug", "Task"];
-type GithubIssueType = (typeof GITHUB_ISSUE_TYPES)[number];
+declare const DEFAULT_PATHS_EXEMPT_FROM_SIZE: ReadonlyArray<string>;
 /**
- * The issue type every title prefix maps to unless it is one of the
- * three explicit exceptions in {@link NON_DEFAULT_TITLE_PREFIX_TYPES}.
+ * Fully-resolved PR review policy. Every field is defaulted so
+ * downstream renderers can reason about a single canonical shape.
  *
- * Every bundle-phase prefix (`company:`, `req:`, `bcm:`, `software:`,
- * …) lands here, which is why agent-enqueued downstream issues are
- * almost always `Task` — the phased pipelines file work items, not
- * features or bug reports.
+ * Two sub-rules are configurable today: the doc-only carve-out
+ * against the size threshold (`autoMerge.pathsExemptFromSize`) and
+ * the CI-verification fallback's required-workflow list
+ * (`ciVerification.requiredWorkflows`). Additional knobs for other
+ * rules in the policy may be added in future versions of
+ * `PrReviewPolicyConfig`.
  */
-declare const DEFAULT_GITHUB_ISSUE_TYPE: GithubIssueType;
+interface ResolvedPrReviewPolicy {
+    readonly autoMerge: ResolvedPrReviewAutoMerge;
+    readonly ciVerification: ResolvedPrReviewCiVerification;
+}
 /**
- * Canonical issue-title-prefix → GitHub issue type map.
- *
- * Derived from {@link CONVENTIONAL_COMMIT_TYPE_LABELS} — the shared
- * conventional-commit vocabulary exported alongside the bundle
- * ownership registry — so the prefix list can never drift from the
- * label list the create-issue workflow stamps. Every conventional-commit
- * prefix defaults to `Task`; the three exceptions are overlaid on top.
+ * Fully-resolved `auto-merge` half of the policy.
  *
- * Prefixes carry their trailing colon (`"feat:"`) to match the way the
- * title conventions write them.
+ * `pathsExemptFromSize` is always populated — the default
+ * (`["docs/**"]`) ships when the consumer omits the option.
  */
-declare const GITHUB_ISSUE_TYPE_BY_TITLE_PREFIX: Readonly<Record<string, GithubIssueType>>;
+interface ResolvedPrReviewAutoMerge {
+    readonly pathsExemptFromSize: ReadonlyArray<string>;
+}
 /**
- * Resolve an issue **title** to the GitHub issue type it must carry.
+ * Fully-resolved `ci-verification` half of the policy.
  *
- * Anything that is not one of the four recognised non-default prefixes
- * — including every bundle-phase prefix (`company:research: …`) and a
- * title with no prefix at all — resolves to
- * {@link DEFAULT_GITHUB_ISSUE_TYPE}.
- */
-declare function githubIssueTypeForTitle(title: string): GithubIssueType;
-/**
- * Path to the `set-issue-type.sh` helper the `github-workflow` bundle
- * ships. Referenced (never assumed present) by the rendered prose — see
- * {@link renderGithubIssueTypeSectionLines} for the fallback that keeps
- * the recipe working for consumers who exclude that bundle.
+ * `requiredWorkflows` is always populated — the default (`[]`, i.e.
+ * "treat every observed Actions run as required") ships when the
+ * consumer omits the option.
  */
-declare const SET_ISSUE_TYPE_HELPER_PATH = ".claude/procedures/set-issue-type.sh";
+interface ResolvedPrReviewCiVerification {
+    readonly requiredWorkflows: ReadonlyArray<string>;
+}
 /**
- * The two-step `updateIssueIssueType` GraphQL flow, rendered as shell.
+ * Resolve a (possibly absent) `PrReviewPolicyConfig` into a canonical
+ * `ResolvedPrReviewPolicy` with every field filled in. Unset fields
+ * cascade from their documented defaults.
  *
- * `set-issue-type.sh` wraps exactly this flow, but that helper ships
- * **only** via the `github-workflow` bundle. Any recipe outside that
- * bundle that cited the helper unconditionally would be broken for a
- * consumer running `excludeBundles: ["github-workflow"]`, so the
- * fallback is documented inline in an always-on base rule and every
- * per-filing-site step points at it.
+ * Malformed configs (empty / whitespace-only path entries) throw a
+ * descriptive `Error` — callers should not need to guard against it
+ * at runtime.
  */
-declare function renderSetIssueTypeFallbackLines(): Array<string>;
+declare function resolvePrReviewPolicy(config?: PrReviewPolicyConfig): ResolvedPrReviewPolicy;
 /**
- * Render the **GitHub Issue Type** section of the always-on
- * `issue-conventions` rule.
- *
- * The section is the single canonical answer to "how does an agent set
- * an issue's type?", and it is rendered into an `ALWAYS`-scoped base
- * rule precisely so every downstream filing site can cite it in one
- * line regardless of which optional bundles the consumer enabled.
+ * Synth-time validation hook. Throws a descriptive `Error` when the
+ * supplied `PrReviewPolicyConfig` is malformed. Called by
+ * `AgentConfig.preSynthesize` before any rendering so a misconfigured
+ * policy fails the build instead of silently shipping broken carve-out
+ * globs. Returns the resolved policy unchanged so callers can write
+ * `const policy = validatePrReviewPolicyConfig(config)` in one line.
  *
- * It documents both paths deliberately:
+ * Malformed cases rejected here:
  *
- * 1. The `set-issue-type.sh` one-liner, when `github-workflow` is
- *    active.
- * 2. The inline GraphQL fallback, when it is not.
+ * - `pathsExemptFromSize` entries that are empty or whitespace-only —
+ *   such an entry would either silently match nothing or match every
+ *   path, both of which are almost certainly a typo.
+ * - `requiredWorkflows` entries that are empty or whitespace-only — a
+ *   blank workflow name can never match an Actions-run `name`, so the
+ *   intended gate would silently never fire.
  */
-declare function renderGithubIssueTypeSectionLines(): Array<string>;
+declare function validatePrReviewPolicyConfig(config?: PrReviewPolicyConfig): ResolvedPrReviewPolicy;
+
 /**
- * Render the title-prefix → issue-type mapping as a markdown bullet
- * list, for recipes that present it inline rather than as a table (the
- * interactive create-issue workflow's step 3).
- *
- * Grouping matches the table in {@link renderGithubIssueTypeSectionLines}:
- * one bullet per non-default prefix, then a single bullet collapsing
- * every prefix that maps to {@link DEFAULT_GITHUB_ISSUE_TYPE}.
+ * One row in the rendered agent registry table. Each phased-agent
+ * bundle that previously shipped its own `<bundle>-workflow` rule
+ * contributes exactly one entry here so the registry can answer
+ * "which agent handles X" without rendering 18 prose summaries
+ * into CLAUDE.md.
  */
-declare function renderTitlePrefixTypeBullets(indent?: string): Array<string>;
-/** String form of {@link renderGithubIssueTypeSectionLines}. */
-declare function renderGithubIssueTypeSection(): string;
-/** Options for {@link renderIssueTypeAssignmentStep}. */
-interface IssueTypeAssignmentStepOptions {
+interface AgentRegistryEntry {
+    /** Bundle name as it appears in `buildBuiltInBundles`, e.g. `bcm-writer`. */
+    readonly bundle: string;
+    /** Primary user-invocable skill, with leading slash, e.g. `/write-bcm`. */
+    readonly skill: string;
+    /** Sub-agent name in `.claude/agents/`, e.g. `bcm-writer`. */
+    readonly agent: string;
     /**
-     * Leading whitespace prepended to every rendered line so the step
-     * nests correctly under the numbered/bulleted filing recipe it
-     * follows. Defaults to the three spaces a top-level numbered list
-     * item continues with.
+     * Function that resolves the canonical output path for this
+     * bundle from the project's resolved agent-path roots. Returning
+     * an empty string signals "no filesystem output path" (used by
+     * pr-review). Path-aware so consumer overrides on
+     * `AgentConfigOptions.paths` propagate into the rendered table.
      */
-    readonly indent?: string;
+    readonly resolveOutputPath: (paths: ResolvedAgentPaths) => string;
     /**
-     * The GitHub issue type the filed issue must carry. Defaults to
-     * {@link DEFAULT_GITHUB_ISSUE_TYPE}, which is correct for every
-     * bundle-phase-prefixed downstream issue.
+     * One-line purpose description. Lifted from the first prose
+     * sentence of the original `<bundle>-workflow` rule so consumers
+     * keep the same routing signal.
      */
-    readonly issueType?: GithubIssueType;
+    readonly purpose: string;
     /**
-     * Render the step as a markdown list item (`- …` with hanging
-     * continuation lines) instead of a paragraph. Used at the handful of
-     * filing recipes that specify the issue with a bullet list rather
-     * than numbered prose.
+     * Name of the original `<bundle>-workflow` rule. Used by the
+     * registry helper to filter the resolved bundle list and assert
+     * (via the test suite) that no bundle still ships its workflow
+     * rule into the Claude platform output.
      */
-    readonly bullet?: boolean;
+    readonly workflowRuleName: string;
 }
 /**
- * Render the compact "now set the issue type" step appended to every
- * bundle-shipped downstream filing recipe.
- *
- * Kept deliberately short: it appears at ~45 filing sites across the
- * phased-pipeline bundles, so it names the concrete type, calls out that
- * the `type:*` label is a different field, gives the command, and
- * delegates the fallback to the always-on `issue-conventions` rule
- * rather than re-inlining the GraphQL flow at every site.
+ * Static registry of every phased-agent bundle that contributes a
+ * routing row. Order is alphabetical by bundle name so the
+ * rendered table is stable across runs and consumer-side diffs are
+ * minimal. Adding a new phased-agent bundle requires appending one
+ * row here and suppressing its `<bundle>-workflow` rule via
+ * `platforms: { claude: { exclude: true } }`.
  */
-declare function renderIssueTypeAssignmentStep(options?: IssueTypeAssignmentStepOptions): Array<string>;
+declare const AGENT_REGISTRY_ENTRIES: ReadonlyArray<AgentRegistryEntry>;
 /**
- * Render the phase-wide variant of {@link renderIssueTypeAssignmentStep}
- * for a workflow phase that files several kinds of issue across several
- * steps, where repeating the per-recipe step at each one would bloat the
- * prompt without adding information.
+ * The set of `<bundle>-workflow` rule names that the registry
+ * subsumes. Used both to suppress those rules from the Claude
+ * platform output and to assert in tests that no bundle still
+ * ships its prose summary into CLAUDE.md.
  */
-declare function renderIssueTypeAssignmentBlanket(indent?: string, issueType?: GithubIssueType): Array<string>;
-
+declare const SUPPRESSED_WORKFLOW_RULE_NAMES: ReadonlyArray<string>;
 /**
- * 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.
- *
- * @see ProgressFilesConfig
+ * Returns `true` when the supplied rule name belongs to a
+ * phased-agent `<bundle>-workflow` rule whose routing summary now
+ * lives in the shared `agent-registry` rule.
  */
-declare const DEFAULT_PROGRESS_FILES_ENABLED = true;
+declare function isSuppressedWorkflowRule(name: string): boolean;
 /**
- * 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.
+ * Reverse map from a `<bundle>-workflow` rule name to its owning
+ * bundle name. Used by the registry consolidation loop to detect
+ * when a consumer has targeted a bundle with a
+ * `features.customDocSections` entry — those bundles keep
+ * rendering their workflow rule into CLAUDE.md so the consumer-
+ * supplied prose has somewhere to live. Returns `undefined` for
+ * any rule name that is not in the registry's suppression list.
+ */
+declare function bundleNameForWorkflowRule(ruleName: string): string | undefined;
+declare function buildAgentRegistryRule(bundles: ReadonlyArray<AgentRuleBundle>, paths: ResolvedAgentPaths): AgentRule | undefined;
+
+/**
+ * Agenda bundle — enabled by default.
  *
- * Lives at the top-level `.state/` directory so the path stays
- * harness-neutral — any agent runtime (Claude Code, Cursor, a
- * bespoke worker) can read and write the same progress files
- * without having to scope under a harness-specific tree.
+ * Consuming projects can disable it with
+ * `excludeBundles: ["agenda"]`. `appliesWhen` always returns `true`
+ * (peer-present assumption, same pattern as the other workflow
+ * bundles).
  *
- * @see ProgressFilesConfig
+ * 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 DEFAULT_PROGRESS_FILES_STATE_DIR = ".state";
+declare const agendaBundle: AgentRuleBundle;
+
 /**
- * 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`).
+ * AWS CDK bundle — auto-detected when `aws-cdk-lib` is in dependencies.
+ */
+declare const awsCdkBundle: AgentRuleBundle;
+
+/**
+ * Hand-maintained registry mapping every bundle name to the cross-bundle
+ * surface it owns: GitHub `type:*` labels, phase-label prefixes,
+ * scheduled-task IDs, whether it emits Starlight docs, and whether it
+ * declares any downstream issue kinds (i.e. files `gh issue create`
+ * recipes via the issue-templates convention).
  *
- * 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.
+ * The registry is consulted by renderers in other bundles whenever
+ * `AgentConfigOptions.excludeBundles` is non-empty so cross-bundle
+ * references to an excluded bundle's agents, type labels, phase labels,
+ * or scheduled tasks disappear from the generated output.
  *
- * @see ProgressFilesConfig
+ * The map is **hand-maintained** rather than derived from each bundle's
+ * runtime shape. The defining surfaces (the funnel-tier table in
+ * `tiers.ts`, the per-phase scope-gate overrides in `scope-gate.ts`, and
+ * the scheduled-tasks registry in `scheduled-tasks.ts`) live as flat
+ * data tables that already get walked by their renderers — declaring the
+ * ownership map alongside them keeps the relationship explicit and
+ * readable without forcing every bundle to grow an "ownership"
+ * descriptor.
+ *
+ * Bundles that ship no cross-bundle surface (e.g. `slack`, `typescript`,
+ * `pnpm`, `vitest`, `jest`, `aws-cdk`, `projen`, `turborepo`,
+ * `upstream-configulator-docs`) deliberately do not appear here —
+ * excluding them is already a no-op since they own nothing other
+ * bundles reference.
  */
-declare const DEFAULT_PROGRESS_FILES_FILENAME_PATTERN = "<ISSUE_NUMBER>-progress.json";
+interface BundleOwnership {
+    /**
+     * GitHub `type:*` label values (without the `type:` prefix) the
+     * bundle owns. The funnel-tier table in `tiers.ts` and any rendered
+     * tables that group agents by `type:*` label consult this list.
+     */
+    readonly typeLabels: ReadonlyArray<string>;
+    /**
+     * Phase-label prefixes (with trailing colon, e.g. `"company:"`) the
+     * bundle owns. Used by the scope-gate per-phase override table and
+     * any other renderer that groups by phase label. An entry without a
+     * trailing colon (e.g. `"req:write"`) is treated as an exact
+     * phase-label match instead of a prefix.
+     */
+    readonly phaseLabelPrefixes: ReadonlyArray<string>;
+    /**
+     * `taskId` values from `DEFAULT_SCHEDULED_TASK_ENTRIES` that target
+     * this bundle's sub-agent. The scheduled-tasks registry filter in
+     * `agent-config.ts` consults this list when pruning default entries
+     * for an excluded bundle.
+     */
+    readonly scheduledTaskIds: ReadonlyArray<string>;
+    /**
+     * Whether this bundle emits Starlight content roots — i.e. whether
+     * any of its workflows write files under `docs/src/content/docs/`
+     * (or the configured docs root). Drives the auto-suppression of the
+     * `section-index-pages` rule when no docs-emitting bundle is active.
+     */
+    readonly emitsDocs: boolean;
+    /**
+     * Whether this bundle dispatches downstream issues (i.e. its
+     * workflows file `gh issue create` recipes). Drives the
+     * auto-suppression of the `issue-templates-convention` rule when no
+     * such bundle is active.
+     *
+     * Not an exhaustive enumerator of issue-filing bundles. Only bundles
+     * that own a cross-bundle surface appear in {@link BUNDLE_OWNERSHIP}
+     * at all, so a bundle can file issues and still be absent — the
+     * `upstream-configulator-docs` bundle files into a *foreign* repo
+     * (`codedrifters/packages`) and is deliberately not registered.
+     * Treat a `true` here as "this bundle's phase labels need the
+     * templates convention", not as "these are all the filing sites".
+     */
+    readonly downstreamIssueKinds: boolean;
+}
 /**
- * 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
+ * Canonical ownership map. Only bundles that own at least one
+ * cross-bundle surface appear here.
  */
-declare const DEFAULT_PROGRESS_FILES_FORMAT: "json" | "markdown";
+declare const BUNDLE_OWNERSHIP: Readonly<Record<string, BundleOwnership>>;
 /**
- * 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.
+ * GitHub `type:*` labels (WITH the `type:` prefix) that come from the
+ * **conventional-commit** vocabulary rather than the bundle/routing
+ * vocabulary. These are derived from an issue's title prefix by the
+ * generic create-issue workflow (`feat:` → `type:feat`, `docs:` →
+ * `type:docs`, …) and are the only `type:*` labels the phase-label
+ * invariant is allowed to remove when it corrects a mislabeled issue.
  *
- * @see ProgressFilesConfig
+ * A bundle `type:*` label (e.g. `type:research`, `type:bcm-document`)
+ * is deliberately **not** in this set: an issue carrying a phase label
+ * from one bundle plus a `type:*` label owned by a *different* bundle
+ * is genuinely ambiguous and gets flagged for a human rather than
+ * silently rewritten.
  */
-declare const DEFAULT_PROGRESS_FILES_STALE_AFTER_HOURS = 72;
+declare const CONVENTIONAL_COMMIT_TYPE_LABELS: ReadonlyArray<string>;
 /**
- * Allowed values for `ProgressFilesConfig.format`. Exported so
- * consumers can reference the canonical set without hard-coding
- * literals.
+ * Canonical phase-label matcher → `type:<bundle>` label map, derived
+ * from {@link BUNDLE_OWNERSHIP}. This is the **single source of truth**
+ * for the phase-label → type-label invariant: label registry
+ * generation, the orchestrator's triage sweep, and the consumer-facing
+ * label audit all read this map rather than re-deriving the pairing.
+ *
+ * Keys are matchers in the same notation `BundleOwnership.phaseLabelPrefixes`
+ * uses — an entry ending in a colon (`"company:"`) is a prefix match,
+ * an entry without one (`"req:write"`) is an exact match. Values carry
+ * the `type:` prefix.
+ *
+ * Co-ownership is fine as long as the co-owners agree on the type
+ * label: all three requirements bundles declare `type:requirement`, so
+ * `req:`, `req:write`, `req:review`, and `req:deprecate` all resolve to
+ * the same value. A matcher that resolved to two *different* type
+ * labels would be a registry bug and throws at module load.
  */
-declare const PROGRESS_FILES_FORMAT_VALUES: readonly ["json", "markdown"];
+declare const PHASE_LABEL_TYPE_MAP: Readonly<Record<string, string>>;
 /**
- * Fully-resolved progress-file settings. Every field is defaulted so
- * downstream renderers can reason about a single canonical shape.
+ * Outcome of resolving a set of issue labels against
+ * {@link PHASE_LABEL_TYPE_MAP}.
+ *
+ * - `"none"` — the labels carry no **recognised** phase label, so the
+ *   invariant does not apply. Unrecognised `foo:bar` labels are
+ *   consumer-specific and deliberately not policed.
+ * - `"match"` — the recognised phase labels all imply one and the same
+ *   `type:<bundle>` label, carried in `typeLabel`.
+ * - `"ambiguous"` — the recognised phase labels imply two or more
+ *   different `type:<bundle>` labels. Never auto-corrected; the caller
+ *   flags the issue for human triage instead.
  */
-interface ResolvedProgressFiles {
-    readonly enabled: boolean;
-    readonly stateDir: string;
-    readonly filenamePattern: string;
-    readonly format: "json" | "markdown";
-    readonly cleanupOnComplete: boolean;
-    readonly staleAfterHours: number;
+type PhaseLabelTypeOutcome = "none" | "match" | "ambiguous";
+/** Result of {@link resolveTypeLabelForLabels}. */
+interface PhaseLabelTypeResolution {
+    /** Which of the three outcomes applies. */
+    readonly outcome: PhaseLabelTypeOutcome;
+    /**
+     * The single implied `type:<bundle>` label (with the `type:` prefix)
+     * when `outcome` is `"match"`; `undefined` otherwise.
+     */
+    readonly typeLabel?: string;
+    /**
+     * Every distinct implied `type:<bundle>` label, sorted. Empty on
+     * `"none"`, one entry on `"match"`, two or more on `"ambiguous"`.
+     */
+    readonly candidateTypeLabels: ReadonlyArray<string>;
+    /**
+     * The subset of the input labels that matched a phase-label matcher,
+     * in input order. Empty on `"none"`.
+     */
+    readonly phaseLabels: ReadonlyArray<string>;
 }
 /**
- * Resolve a (possibly absent) `ProgressFilesConfig` into a canonical
- * `ResolvedProgressFiles` with every field filled in. Unset fields
- * cascade from their documented defaults.
+ * Resolve a single phase label to the `type:<bundle>` label its owning
+ * bundle declares, or `undefined` when no bundle owns it.
  *
- * 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`.
+ * Exact-match entries beat prefix entries: `req:write` is owned by
+ * `requirements-writer` while the `req:` prefix is owned by
+ * `requirements-analyst`. (Both currently declare `type:requirement`,
+ * but the precedence is load-bearing for any future divergence.)
  */
-declare function resolveProgressFiles(config?: ProgressFilesConfig): ResolvedProgressFiles;
+declare function typeLabelForPhaseLabel(phaseLabel: string): string | undefined;
 /**
- * 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:
+ * Resolve every label on an issue to the `type:<bundle>` label the
+ * phase-label invariant requires it to carry.
  *
- * - `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.
+ * The input is the issue's **full** label list — the resolver picks out
+ * the recognised phase labels itself and ignores everything else
+ * (`status:*`, `priority:*`, existing `type:*`, and any consumer label
+ * that matches no bundle).
  */
-declare function validateProgressFilesConfig(config?: ProgressFilesConfig): ResolvedProgressFiles;
+declare function resolveTypeLabelForLabels(labels: ReadonlyArray<string>): PhaseLabelTypeResolution;
 /**
- * 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).
+ * Render the **Phase-label → `type:<bundle>` invariant** section of the
+ * `orchestrator-conventions` rule. The matcher table is generated from
+ * {@link PHASE_LABEL_TYPE_MAP}, so the documented pairing can never
+ * drift from the pairing the sweep enforces.
  *
- * Exported so consumer-side scripts (or the `partial-resume-protocol`
- * rule renderer) can compute the on-disk path deterministically.
- */
-declare function renderProgressFileName(pf: ResolvedProgressFiles, issueNumber: number | string): string;
-/**
- * Resolve the runtime path (directory + filename) for a progress file
- * given an issue number and a resolved config.
+ * Rows whose owning bundle appears in `excludeBundles` are dropped,
+ * matching every other cross-bundle renderer.
  */
-declare function renderProgressFilePath(pf: ResolvedProgressFiles, issueNumber: number | string): string;
+declare function renderPhaseTypeInvariantSection(excludeBundles?: ReadonlyArray<string>): string;
 /**
- * Render the full body for the `progress-file-convention` rule shipped
- * by the `base` bundle. The rule documents:
- *
- * - 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.
+ * Render the POSIX-shell half of the phase-label → `type:<bundle>`
+ * invariant, derived from the same {@link PHASE_LABEL_TYPE_MAP} the
+ * TypeScript accessors read. Emitted into `check-blocked.sh` so the
+ * orchestrator's triage sweep and the consumer-runnable label audit
+ * never carry a hand-copied second map.
  *
- * 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 function renderProgressFilesRuleContent(pf: ResolvedProgressFiles): string;
-/**
- * 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.
+ * Three functions are rendered:
  *
- * When the convention is disabled, the function returns an empty
- * string so callers can no-op their append path.
+ * - `phase_label_type_of <label>` — echoes the `type:<bundle>` label a
+ *   single phase label implies, or nothing. Exact-match branches are
+ *   emitted before prefix branches so `case` ordering reproduces the
+ *   exact-beats-prefix precedence.
+ * - `phase_type_of` — reads an issue's labels (one per line) on stdin
+ *   and emits `KEY=VALUE` assignments: `OUTCOME=none|match|ambiguous`,
+ *   `TYPE_LABEL=` (match only), `CANDIDATE_TYPE_LABELS=` (ambiguous
+ *   only), and `PHASE_LABELS=`.
+ * - `is_conventional_type_label <label>` — returns 0 for a
+ *   conventional-commit `type:*` label, i.e. the only labels the
+ *   auto-correction is allowed to remove.
  */
-declare function renderProgressFilesBundleHook(pf: ResolvedProgressFiles, bundleLabel: string): string;
-
-/*******************************************************************************
- *
- * Bundle definition — opt-in. Consumers must include via `includeBundles`
- * (or it auto-detects through the appliesWhen below). No hardcoded
- * domain-specific content.
- *
- ******************************************************************************/
+declare function renderPhaseTypeInvariantShellHelpers(): string;
 /**
- * Build the `pr-review` bundle with the supplied (possibly absent)
- * PR review policy override.
- *
- * The bundle is mostly static — the agent prompt, the feedback-
- * protocol prose, the skills, the sub-agent, and the labels are all
- * fixed across consumers. The one dynamic surface is the rendered
- * `pr-review-policy` rule's YAML block and precedence walk, which
- * reflect the resolved `pathsExemptFromSize` carve-out so consumers
- * tuning the doc-only carve-out see their override land in the
- * rendered CLAUDE.md.
- *
- * When `policy` is omitted, the bundle ships with the documented
- * defaults baked in (`pathsExemptFromSize: ["docs/**"]`).
+ * Return `true` when `typeLabel` (without the leading `type:` prefix)
+ * is owned by any bundle in `excludedBundles`. Used by tier-table and
+ * scheduled-task renderers to drop rows whose owning bundle has been
+ * excluded.
  */
-declare function buildPrReviewBundle(policy?: ResolvedPrReviewPolicy): AgentRuleBundle;
+declare function isTypeLabelOwnedByExcluded(typeLabel: string, excludedBundles: ReadonlyArray<string>): boolean;
 /**
- * `pr-review` bundle built with the default policy. Preserved for
- * backward compatibility with tests and consumers that import the
- * const directly. Prefer `buildPrReviewBundle(policy)` when consumer
- * overrides are in scope.
+ * Return `true` when `phaseLabel` is owned by any bundle in
+ * `excludedBundles`. Matches against both prefix entries (with
+ * trailing colon, e.g. `"company:"`) and exact-match entries (without
+ * trailing colon, e.g. `"req:write"`). Used by the scope-gate
+ * per-phase-override table renderer.
  */
-declare const prReviewBundle: AgentRuleBundle;
-
+declare function isPhaseLabelOwnedByExcluded(phaseLabel: string, excludedBundles: ReadonlyArray<string>): boolean;
 /**
- * Projen bundle — auto-detected when `projen` is in dependencies.
+ * Return `true` when the scheduled-task `taskId` is owned by any
+ * bundle in `excludedBundles`. Used by the scheduled-tasks registry
+ * filter to drop default entries pointing at an excluded bundle.
  */
-declare const projenBundle: AgentRuleBundle;
-
+declare function isScheduledTaskOwnedByExcluded(taskId: string, excludedBundles: ReadonlyArray<string>): boolean;
 /**
- * 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.
+ * Return `true` when at least one docs-emitting bundle is **not**
+ * excluded. Used by the `section-index-pages` rule auto-suppression
+ * gate — when this returns `false`, the rule is dropped from the
+ * rendered rule map entirely.
  */
-declare function buildRegulatoryResearchBundle(paths?: ResolvedAgentPaths, issueDefaults?: ResolvedIssueDefaults): AgentRuleBundle;
+declare function hasAnyDocsEmittingBundle(excludedBundles: ReadonlyArray<string>): boolean;
 /**
- * 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`.
+ * Return `true` when at least one downstream-issue-kind bundle is
+ * **not** excluded. Used by the `issue-templates-convention`
+ * auto-suppression gate — when this returns `false`, the rule body
+ * renders the disabled-stub variant.
  */
-declare const regulatoryResearchBundle: AgentRuleBundle;
+declare function hasAnyDownstreamIssueKindBundle(excludedBundles: ReadonlyArray<string>): boolean;
 
 /**
- * Inject domain-specific source-tier examples into the content of the
- * base bundle's "Source Quality & Verification" rule.
+ * Build the bcm-writer bundle with the supplied resolved paths.
  *
- * For every tier whose examples array is non-empty, a
- * `**Project-specific examples:**` line followed by a bullet list of
- * the supplied strings is appended immediately beneath the tier's
- * `### T<n> — ...` heading paragraph block. Tiers whose examples array
- * is missing or empty are left untouched.
+ * 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.
  *
- * Returns the original `content` verbatim when the supplied config is
- * undefined or has no non-empty tier arrays, so callers can
- * unconditionally pipe content through this function.
- */
-declare function renderSourceTierExamples(content: string, examples: SourceTierExamples | undefined): string;
-/**
- * Apply every {@link CustomDocSection} that targets `bundle.name` to
- * the bundle's rules, returning a new bundle whose matched rules have
- * the section bodies appended after the configured `afterSection`
- * heading. Entries that reference a bundle name other than
- * `bundle.name`, or whose `afterSection` cannot be located in any
- * rule in the bundle, are silently dropped.
+ * Consuming projects can disable it with `excludeBundles: ["bcm-writer"]`.
+ * `appliesWhen` always returns `true` per this batch's directive that
+ * bundles assume peers are present.
  *
- * Entries that target the same `afterSection` heading render in
- * supplied order — the first supplied entry appears immediately
- * beneath the target heading block, the second below that, and so on.
- * This is achieved by advancing the insertion anchor to each
- * just-injected section's `## <sectionTitle>` heading; the next
- * same-target entry then lands at the end of that newly-opened
- * section, which places it immediately after the previous entry
- * regardless of the original heading's level.
+ * 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.
  *
- * Returns `bundle` unchanged when `sections` is empty or no entries
- * match, so callers can unconditionally pipe bundles through this
- * function without penalty.
- */
-declare function renderCustomDocSections(bundle: AgentRuleBundle, sections: ReadonlyArray<CustomDocSection>): AgentRuleBundle;
-/**
- * Render a {@link CustomDocSection} into the markdown block that
- * `renderCustomDocSections` splices after the target heading block.
- * Exposed for tests that exercise the renderer directly without
- * touching a full bundle.
+ * 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 renderCustomDocSectionBlock(section: CustomDocSection): string;
-
+declare function buildBcmWriterBundle(paths?: ResolvedAgentPaths, issueDefaults?: ResolvedIssueDefaults): AgentRuleBundle;
 /**
- * Render the markdown subsection appended to the
- * `issue-label-conventions` rule when `AgentConfigOptions.focus` is
- * supplied. Returns an empty string when `focus` is undefined so
- * callers can unconditionally concatenate the result.
- *
- * The section documents three things for agents:
- *
- * 1. How to read `focus.json` at triage time
- * 2. How focus weight interacts with the `priority:*` taxonomy
- * 3. The agent-driven expansion contract (what agents may append)
- *
- * Configulator ships this rule content plus a JSON Schema that
- * validates the `focus.json` file; the file itself is authored and
- * curated in the consuming repo.
+ * 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 function renderFocusSection(focus: FocusConfig | undefined): string;
+declare const bcmWriterBundle: AgentRuleBundle;
 
 /**
- * Render the markdown subsections appended to the
- * `meeting-processing-workflow` rule when `AgentConfigOptions.meetings`
- * is supplied. Returns an empty string when the supplied config has
- * nothing to render (no meeting types and no meeting areas) so callers
- * can unconditionally concatenate the result.
- *
- * Two subsections are rendered, each gated on its own input array:
+ * Build the business-models bundle with the supplied resolved paths.
  *
- * 1. **Recognized meeting types** — rendered when `meetingTypes` is
- *    non-empty. Lists every declared type with its scope, kind,
- *    optional cadence, default duration, and agenda template path.
- *    Also documents the resolved `agendaTemplateRoot`.
- * 2. **Area → doc-root mapping** — rendered when `meetingAreas` is
- *    non-empty. Lists every declared area with its `id`, label, and
- *    docs-root-relative destination folder.
+ * 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.
  *
- * Bundles consume the rendered string by appending it to their own
- * rule content. A caller that has no meeting types and no meeting
- * areas receives an empty string and can safely concatenate.
+ * 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 renderMeetingTypesSection(meetings: MeetingsConfig | undefined): string;
-
+declare function buildBusinessModelsBundle(paths?: ResolvedAgentPaths, issueDefaults?: ResolvedIssueDefaults): AgentRuleBundle;
 /**
- * Render the markdown subsection appended to the
- * `issue-label-conventions` rule when `AgentConfigOptions.priorityRules`
- * is non-empty. Returns an empty string when the supplied array is
- * empty so callers can unconditionally concatenate the result.
- *
- * Precedence is **first match wins** — rules render in the order
- * supplied. The bundle's default inference heuristics act as the
- * fallback when no rule matches.
+ * 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 function renderPriorityRulesSection(rules: ReadonlyArray<PriorityRule>): string;
+declare const businessModelsBundle: AgentRuleBundle;
 
 /**
- * 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.
+ * Build the company-profile bundle with the supplied resolved paths.
  *
- * @see SharedEditingConfig
+ * 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 const DEFAULT_SHARED_EDITING_ENABLED = true;
+declare function buildCompanyProfileBundle(paths?: ResolvedAgentPaths, issueDefaults?: ResolvedIssueDefaults, tier?: AgentModel): AgentRuleBundle;
 /**
- * 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.
+ * 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.
  *
- * The defaults cover the registry / index files every configulator
- * consumer ships by convention:
+ * Consuming projects can disable it with
+ * `excludeBundles: ["customer-profile"]`. `appliesWhen` always
+ * returns `true` per the workflow-bundle peer-present assumption.
  *
- * - 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.
+ * 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.
  *
- * Consumers can replace the list outright via `sharedIndexPaths` or
- * append project-specific registries.
+ * 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.
  *
- * @see SharedEditingConfig
+ * 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 const DEFAULT_SHARED_INDEX_PATHS: ReadonlyArray<string>;
+declare function buildCustomerProfileBundle(paths?: ResolvedAgentPaths, issueDefaults?: ResolvedIssueDefaults, tier?: AgentModel): AgentRuleBundle;
 /**
- * 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
+ * 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 DEFAULT_SHARED_EDITING_CONFLICT_STRATEGY: "rebase" | "merge";
+declare const customerProfileBundle: AgentRuleBundle;
+
 /**
- * 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.
+ * 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.
  *
- * @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.
+ * 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.
  *
- * @see SharedEditingConfig
+ * 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 const DEFAULT_SHARED_EDITING_EMIT_HELPER = false;
+declare function renderExtractApiProcedure(): string;
 /**
- * Allowed values for `SharedEditingConfig.conflictStrategy`. Exported
- * so consumers can reference the canonical set without hard-coding
- * literals.
+ * `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 SHARED_EDITING_CONFLICT_STRATEGY_VALUES: readonly ["rebase", "merge"];
+declare const extractApiProcedure: AgentProcedure;
 /**
- * Fully-resolved shared-editing settings. Every field is defaulted so
- * downstream renderers can reason about a single canonical shape.
+ * Render the shell body of the `.claude/procedures/check-links.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 wraps two external tools — `astro check` (internal
+ * links) and `lychee` (external `https://…` URLs) — and normalizes
+ * their per-finding output into a single JSON-array stream of
+ * `{ url, docPath, line, kind, reason }` records on stdout. The
+ * downstream docs-sync scan phase (#519/#520) consumes that stream
+ * and decides which findings are advisory and which block the PR.
+ *
+ * Detection is **data**, not failure: the helper exits `0` whenever
+ * a tool ran successfully, regardless of how many broken links it
+ * reported. Non-zero exits are reserved for tool-level failures
+ * (missing binary, config error, IO failure).
+ *
+ * Exit codes: `0` success, `1` usage error or unreadable docs
+ * root, `2` a required external tool is missing, `3` a tool ran
+ * but exited non-zero for a reason other than broken-link
+ * detection.
  */
-interface ResolvedSharedEditing {
-    readonly enabled: boolean;
-    readonly sharedIndexPaths: ReadonlyArray<string>;
-    readonly verifyCommit: boolean;
-    readonly conflictStrategy: "rebase" | "merge";
-    readonly emitHelper: boolean;
-}
+declare function renderCheckLinksProcedure(): string;
 /**
- * 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`.
+ * `AgentProcedure` definition for `.claude/procedures/check-links.sh`.
+ * Registered on the docs-sync bundle so it ships when the bundle is
+ * force-included — matches the packaging of `extractApiProcedure`
+ * above. Provides the link-integrity input the docs-sync scan phase
+ * (#519/#520) consumes alongside API-extractor and TSDoc-coverage
+ * findings.
  */
-declare function resolveSharedEditing(config?: SharedEditingConfig): ResolvedSharedEditing;
+declare const checkLinksProcedure: AgentProcedure;
 /**
- * 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.
+ * Render the shell body of the
+ * `.claude/procedures/strip-tool-artifact-tags.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.
  *
- * Malformed cases rejected here:
+ * Authoring agents intermittently leak tool-call wrapper *closing*
+ * tags (`</content>`, `</invoke>`, occasionally `</parameter>`) as
+ * trailing whole lines in the markdown they write. `astro check` and
+ * CI link checks do not catch them. This helper strips those leaked
+ * EOF artifact lines on write so they never reach the committed tree.
  *
- * - `sharedIndexPaths` contains an empty / whitespace-only entry, or
- *   the array is supplied but empty.
- * - `conflictStrategy` is not one of `"rebase"` / `"merge"`.
+ * Behaviour, mirroring `check-links.sh`'s defensive guards:
+ *
+ *   - Takes a single file-path argument.
+ *   - Operates only when the file exists and its path is under
+ *     `docs/src/content/docs/`. Any other path (or a missing file) is
+ *     a silent no-op.
+ *   - Removes **trailing whole lines** that are exactly `</content>`,
+ *     `</invoke>`, or `</parameter>` (trailing whitespace on the line
+ *     is tolerated), plus any blank lines that become trailing once
+ *     the tags are removed, then leaves a single final newline.
+ *   - Only whole-line EOF tags are stripped — legitimate inline
+ *     `<...>` prose or fenced code is never touched.
+ *   - Idempotent: a second run on an already-clean file changes
+ *     nothing.
+ *   - Never edits a file it did not need to change, and **always**
+ *     exits 0 so a PostToolUse hook can never fail the tool call.
+ *
+ * Exit code: always `0`. Diagnostics (if any) flow to stderr.
+ */
+declare function renderStripToolArtifactTagsProcedure(): string;
+/**
+ * `AgentProcedure` definition for
+ * `.claude/procedures/strip-tool-artifact-tags.sh`. Registered on the
+ * docs-sync bundle so it ships alongside `check-links.sh` when the
+ * bundle is force-included, and chained into the base PostToolUse
+ * Edit|Write hook so authored markdown is cleaned of leaked tool-call
+ * artifact tags on write (#779).
  */
-declare function validateSharedEditingConfig(config?: SharedEditingConfig): ResolvedSharedEditing;
+declare const stripToolArtifactTagsProcedure: AgentProcedure;
 /**
- * Render the full body for the `shared-editing-safety` rule shipped
- * by the `base` bundle. The rule documents:
+ * Render the shell body of the
+ * `.claude/procedures/check-doc-samples.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 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).
+ * The helper wraps the `compileFencedSamples` API exported from
+ * `@codedrifters/configulator` (under `src/docs-sync/sample-compilation/`)
+ * and emits a single JSON-array stream of failure records on stdout.
+ * Detection is **data**, not failure: the helper exits `0` when the
+ * compilation phase ran successfully, regardless of how many samples
+ * failed to compile. Non-zero exits are reserved for tool-level
+ * failures (missing binary, IO error, internal exception).
  *
- * 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.
+ * Exit codes: `0` success, `1` usage error or unreadable docs root,
+ * `2` a required binary is missing (`node` / `pnpm`), `3` the
+ * compilation phase threw an unhandled exception.
  */
-declare function renderSharedEditingRuleContent(se: ResolvedSharedEditing): string;
+declare function renderCheckDocSamplesProcedure(): 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.
+ * `AgentProcedure` definition for
+ * `.claude/procedures/check-doc-samples.sh`. Registered on the
+ * docs-sync bundle so it ships when the bundle is force-included —
+ * matches the packaging of `extractApiProcedure` and
+ * `checkLinksProcedure` above. Provides the fenced-sample
+ * compilation input the docs-sync scan phase (#520) consumes
+ * alongside link integrity, API-extractor, TSDoc-coverage, and
+ * doc-reference findings. Per the parent epic, fenced TS samples
+ * that fail to compile are one of the two hard-block cases.
  */
-declare function renderSharedEditingBundleHook(se: ResolvedSharedEditing, bundleLabel: string): string;
+declare const checkDocSamplesProcedure: AgentProcedure;
 /**
- * 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.
+ * Docs-sync bundle — scaffolding release.
  *
- * It exits non-zero on any of the following:
+ * 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.
  *
- * - 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).
+ * 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 renderSharedEditingHelperScript(_se: ResolvedSharedEditing): string;
+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;
 
 /**
- * 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.
+ * Builds the GitHub workflow bundle — auto-detected when the project
+ * has a GitHub component.
  *
- * @see SkillEvalsConfig
+ * The `build` policy conditions the PR-workflow build guidance on the
+ * consuming project's Turborepo remote-cache configuration. When
+ * omitted, the bundle ships the zero-remote-cache defaults
+ * ({@link DEFAULT_BUILD_POLICY}), which emit no AWS-authentication
+ * guidance at all.
  */
-declare const DEFAULT_SKILL_EVALS_ENABLED = true;
+declare function buildGithubWorkflowBundle(buildPolicy?: ResolvedBuildPolicy): AgentRuleBundle;
 /**
- * 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
+ * `github-workflow` bundle built with the default (no remote cache)
+ * build policy. Preserved for backward compatibility with tests and
+ * consumers that import the const directly. Prefer
+ * `buildGithubWorkflowBundle(buildPolicy)` when the consuming
+ * project's Turborepo configuration is in scope.
  */
-declare const DEFAULT_SKILL_EVALS_SKILLS_ROOT = ".claude/skills";
+declare const githubWorkflowBundle: AgentRuleBundle;
+
 /**
- * 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.
+ * Build the industry-discovery bundle with the supplied resolved paths.
  *
- * @see SkillEvalsConfig
+ * 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 const DEFAULT_PRODUCT_CONTEXT_PATH = "docs/src/content/docs/project-context.md";
+declare function buildIndustryDiscoveryBundle(paths?: ResolvedAgentPaths, issueDefaults?: ResolvedIssueDefaults): AgentRuleBundle;
 /**
- * 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
+ * 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 DEFAULT_REQUIRE_PRODUCT_CONTEXT = true;
+declare const industryDiscoveryBundle: AgentRuleBundle;
+
 /**
- * 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`.
+ * Jest bundle — auto-detected when Jest is in dependencies.
+ */
+declare const jestBundle: AgentRuleBundle;
+
+/**
+ * Maintenance-audit bundle — enabled by default.
  *
- * @see SkillEvalsConfig
+ * 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 const DEFAULT_SKILL_EVALS_EMIT_RUNNER = false;
+declare function buildMaintenanceAuditBundle(paths?: ResolvedAgentPaths, issueDefaults?: ResolvedIssueDefaults, tier?: AgentModel): AgentRuleBundle;
 /**
- * Fully-resolved skill-evals settings. Every field is defaulted so
- * downstream renderers can reason about a single canonical shape.
+ * 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`.
  */
-interface ResolvedSkillEvals {
-    readonly enabled: boolean;
-    readonly skillsRoot: string;
-    readonly productContextPath: string;
-    readonly requireProductContext: boolean;
-    readonly emitRunner: boolean;
-}
+declare const maintenanceAuditBundle: AgentRuleBundle;
+
 /**
- * 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`.
+ * Build the meeting-analysis bundle with the supplied default sub-agent
+ * model tier. The tier knob lets consumers globally demote the
+ * `meeting-analyst` sub-agent to BALANCED (sonnet) — which is the
+ * post-2026-05-08 default — without forking the bundle.
  */
-declare function resolveSkillEvals(config?: SkillEvalsConfig): ResolvedSkillEvals;
+declare function buildMeetingAnalysisBundle(tier?: AgentModel): AgentRuleBundle;
 /**
- * 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.
+ * Default-tier instance of the meeting-analysis 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.defaultAgentTier`.
  */
-declare function validateSkillEvalsConfig(config?: SkillEvalsConfig): ResolvedSkillEvals;
+declare const meetingAnalysisBundle: AgentRuleBundle;
+
 /**
- * Render the full body for the `skill-evals` rule shipped by the
- * `base` bundle. The rule documents:
+ * People-profile bundle — enabled by default.
  *
- * - 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).
+ * 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`).
  *
- * 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.
+ * 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 function renderSkillEvalsRuleContent(se: ResolvedSkillEvals): string;
+declare function buildPeopleProfileBundle(paths?: ResolvedAgentPaths, issueDefaults?: ResolvedIssueDefaults, tier?: AgentModel): AgentRuleBundle;
 /**
- * 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.
+ * 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 function renderSkillEvalsBundleHook(se: ResolvedSkillEvals, skillLabel: string): string;
+declare const peopleProfileBundle: AgentRuleBundle;
+
 /**
- * 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`.
+ * PNPM bundle — auto-detected when the PnpmWorkspace component is present.
+ */
+declare const pnpmBundle: AgentRuleBundle;
+
+/*******************************************************************************
  *
- * The script takes zero or one positional arguments:
+ * Bundle definition — opt-in. Consumers must include via `includeBundles`
+ * (or it auto-detects through the appliesWhen below). No hardcoded
+ * domain-specific content.
  *
- * 1. `[<skill-name>]` — optional, restricts the run to one skill.
+ ******************************************************************************/
+/**
+ * Build the `pr-review` bundle with the supplied (possibly absent)
+ * PR review policy override.
  *
- * It exits non-zero on any of the following:
+ * The bundle is mostly static — the agent prompt, the feedback-
+ * protocol prose, the skills, the sub-agent, and the labels are all
+ * fixed across consumers. The one dynamic surface is the rendered
+ * `pr-review-policy` rule's YAML block and precedence walk, which
+ * reflect the resolved `pathsExemptFromSize` carve-out so consumers
+ * tuning the doc-only carve-out see their override land in the
+ * rendered CLAUDE.md.
  *
- * - `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.
+ * When `policy` is omitted, the bundle ships with the documented
+ * defaults baked in (`pathsExemptFromSize: ["docs/**"]`).
  */
-declare function renderSkillEvalsRunnerScript(se: ResolvedSkillEvals): string;
+declare function buildPrReviewBundle(policy?: ResolvedPrReviewPolicy): AgentRuleBundle;
+/**
+ * `pr-review` bundle built with the default policy. Preserved for
+ * backward compatibility with tests and consumers that import the
+ * const directly. Prefer `buildPrReviewBundle(policy)` when consumer
+ * overrides are in scope.
+ */
+declare const prReviewBundle: AgentRuleBundle;
 
 /**
- * Default master switch for the temporal-framing convention. When no
- * config is supplied the convention ships **enabled** so every
- * configulator-consuming repo's analyst agents apply the
- * "as of [date]" qualifier rule.
- *
- * @see TemporalFramingConfig
+ * Projen bundle — auto-detected when `projen` is in dependencies.
  */
-declare const DEFAULT_TEMPORAL_FRAMING_ENABLED = true;
+declare const projenBundle: AgentRuleBundle;
+
 /**
- * Default path globs the rule applies to — every Markdown file under
- * the profile / research subtrees of a repo's Starlight docs site.
- * Consumers may override the list when their content layout differs.
+ * Regulatory-research bundle — enabled by default.
  *
- * Out-of-scope locations (meeting notes, requirements, the
- * project-context page) are excluded by design: their own dating
- * conventions (file-name date prefix, version frontmatter, living
- * snapshot under direct human review) already anchor the temporal
- * meaning of their content.
+ * Consuming projects can disable it with
+ * `excludeBundles: ["regulatory-research"]`. `appliesWhen` always
+ * returns `true` per the workflow-bundle peer-present assumption.
  *
- * @see TemporalFramingConfig
+ * 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 const DEFAULT_TEMPORAL_FRAMING_PATHS: ReadonlyArray<string>;
+declare function buildRegulatoryResearchBundle(paths?: ResolvedAgentPaths, issueDefaults?: ResolvedIssueDefaults): AgentRuleBundle;
 /**
- * The five canonical time-sensitive claim categories surfaced by the
- * May 2026 sampled drift audit. The category names are shipped as the
- * key set for `TemporalFramingConfig.cadences` so consumers can dial
- * the per-category refresh cadence without inventing their own
- * category names.
+ * 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 TEMPORAL_FRAMING_CATEGORY_VALUES: readonly ["ownership", "company-leadership", "regulatory-status", "litigation", "dated-metrics"];
-type TemporalFramingCategory = (typeof TEMPORAL_FRAMING_CATEGORY_VALUES)[number];
+declare const regulatoryResearchBundle: AgentRuleBundle;
+
 /**
- * Default per-category refresh cadences (in days). Fast-decay claims
- * (regulatory status, litigation) carry a 30-day cadence because a
- * single press release can invalidate them between scheduled refresh
- * passes. Slow-decay claims (ownership, dated metrics from press
- * releases or filings) carry a 180-day cadence — material changes
- * still happen but rarely outpace a half-yearly refresh. Leadership
- * tenure sits in the middle at 90 days.
+ * Inject domain-specific source-tier examples into the content of the
+ * base bundle's "Source Quality & Verification" rule.
  *
- * Consumers may override any subset of categories via
- * `TemporalFramingConfig.cadences`; unspecified entries fall through
- * to these defaults.
+ * For every tier whose examples array is non-empty, a
+ * `**Project-specific examples:**` line followed by a bullet list of
+ * the supplied strings is appended immediately beneath the tier's
+ * `### T<n> — ...` heading paragraph block. Tiers whose examples array
+ * is missing or empty are left untouched.
+ *
+ * Returns the original `content` verbatim when the supplied config is
+ * undefined or has no non-empty tier arrays, so callers can
+ * unconditionally pipe content through this function.
  */
-declare const DEFAULT_TEMPORAL_FRAMING_CADENCES: {
-    readonly [K in TemporalFramingCategory]: number;
-};
+declare function renderSourceTierExamples(content: string, examples: SourceTierExamples | undefined): string;
 /**
- * Default for whether the convention emits the
- * `.claude/procedures/check-temporal-framing.sh` lint script to disk.
- * Disabled by default — consumers opt in when they want a hard
- * pre-commit or CI gate. The rule body itself ships unconditionally
- * regardless of the lint script.
+ * Apply every {@link CustomDocSection} that targets `bundle.name` to
+ * the bundle's rules, returning a new bundle whose matched rules have
+ * the section bodies appended after the configured `afterSection`
+ * heading. Entries that reference a bundle name other than
+ * `bundle.name`, or whose `afterSection` cannot be located in any
+ * rule in the bundle, are silently dropped.
  *
- * @see TemporalFramingConfig
+ * Entries that target the same `afterSection` heading render in
+ * supplied order — the first supplied entry appears immediately
+ * beneath the target heading block, the second below that, and so on.
+ * This is achieved by advancing the insertion anchor to each
+ * just-injected section's `## <sectionTitle>` heading; the next
+ * same-target entry then lands at the end of that newly-opened
+ * section, which places it immediately after the previous entry
+ * regardless of the original heading's level.
+ *
+ * Returns `bundle` unchanged when `sections` is empty or no entries
+ * match, so callers can unconditionally pipe bundles through this
+ * function without penalty.
  */
-declare const DEFAULT_TEMPORAL_FRAMING_EMIT_CHECKER = false;
+declare function renderCustomDocSections(bundle: AgentRuleBundle, sections: ReadonlyArray<CustomDocSection>): AgentRuleBundle;
 /**
- * Fully-resolved temporal-framing settings. Every field is defaulted
- * so downstream renderers can reason about a single canonical shape.
+ * Render a {@link CustomDocSection} into the markdown block that
+ * `renderCustomDocSections` splices after the target heading block.
+ * Exposed for tests that exercise the renderer directly without
+ * touching a full bundle.
  */
-interface ResolvedTemporalFraming {
-    readonly enabled: boolean;
-    readonly paths: ReadonlyArray<string>;
-    readonly cadences: {
-        readonly [K in TemporalFramingCategory]: number;
-    };
-    readonly emitChecker: boolean;
-}
+declare function renderCustomDocSectionBlock(section: CustomDocSection): string;
+
 /**
- * Resolve a (possibly absent) `TemporalFramingConfig` into a canonical
- * `ResolvedTemporalFraming` with every field filled in. Unset fields
- * cascade from their documented defaults.
- *
- * Malformed configs throw a descriptive `Error`:
+ * Render the markdown subsection appended to the
+ * `issue-label-conventions` rule when `AgentConfigOptions.focus` is
+ * supplied. Returns an empty string when `focus` is undefined so
+ * callers can unconditionally concatenate the result.
  *
- * - `paths` containing empty / whitespace-only entries.
- * - `cadences` containing non-integer or non-positive values.
- */
-declare function resolveTemporalFraming(config?: TemporalFramingConfig): ResolvedTemporalFraming;
-/**
- * Synth-time validation hook. Throws a descriptive `Error` when the
- * supplied `TemporalFramingConfig` is malformed. Called by
- * `AgentConfig.preSynthesize` before any rendering so a misconfigured
- * convention fails the build instead of silently shipping broken
- * paths or cadences. Returns the resolved config unchanged so callers
- * can write `const tf = validateTemporalFramingConfig(config)` in
- * one line.
+ * The section documents three things for agents:
  *
- * Malformed cases rejected here:
+ * 1. How to read `focus.json` at triage time
+ * 2. How focus weight interacts with the `priority:*` taxonomy
+ * 3. The agent-driven expansion contract (what agents may append)
  *
- * - `paths` containing empty or whitespace-only entries.
- * - `cadences` containing non-integer or non-positive values.
+ * Configulator ships this rule content plus a JSON Schema that
+ * validates the `focus.json` file; the file itself is authored and
+ * curated in the consuming repo.
  */
-declare function validateTemporalFramingConfig(config?: TemporalFramingConfig): ResolvedTemporalFraming;
+declare function renderFocusSection(focus: FocusConfig | undefined): string;
+
 /**
- * Render the body for the `temporal-framing-convention` rule shipped
- * by the `base` bundle. The rule documents:
+ * Render the markdown subsections appended to the
+ * `meeting-processing-workflow` rule when `AgentConfigOptions.meetings`
+ * is supplied. Returns an empty string when the supplied config has
+ * nothing to render (no meeting types and no meeting areas) so callers
+ * can unconditionally concatenate the result.
  *
- * - The "as of [date]" qualifier requirement on time-sensitive claims.
- * - The five canonical time-sensitive claim categories.
- * - Refresh-agent behaviour (grep for `as of `, re-verify against the
- *   category-specific cadence).
- * - The scope of applicability (profile / research sections only).
+ * Two subsections are rendered, each gated on its own input array:
  *
- * When the convention is disabled, the rule renders a short stub that
- * tells agents the project does not enforce explicit temporal
- * qualifiers and that staleness is caught by review alone.
+ * 1. **Recognized meeting types** — rendered when `meetingTypes` is
+ *    non-empty. Lists every declared type with its scope, kind,
+ *    optional cadence, default duration, and agenda template path.
+ *    Also documents the resolved `agendaTemplateRoot`.
+ * 2. **Area → doc-root mapping** — rendered when `meetingAreas` is
+ *    non-empty. Lists every declared area with its `id`, label, and
+ *    docs-root-relative destination folder.
+ *
+ * Bundles consume the rendered string by appending it to their own
+ * rule content. A caller that has no meeting types and no meeting
+ * areas receives an empty string and can safely concatenate.
  */
-declare function renderTemporalFramingRuleContent(tf: ResolvedTemporalFraming): string;
+declare function renderMeetingTypesSection(meetings: MeetingsConfig | undefined): string;
+
 /**
- * Render the `.claude/procedures/check-temporal-framing.sh` helper
- * script. Exported so `AgentConfig` can register it 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.
+ * Render the markdown subsection appended to the
+ * `issue-label-conventions` rule when `AgentConfigOptions.priorityRules`
+ * is non-empty. Returns an empty string when the supplied array is
+ * empty so callers can unconditionally concatenate the result.
  *
- * It fails non-zero when any changed file matches a configured path
- * pattern and contains time-sensitive framing (present-tense forms of
- * the canonical category triggers) but lacks an `as of ` qualifier
- * anywhere in the file. The lint is intentionally coarse — file-level
- * not line-level — so the cost of running it on every PR stays low.
+ * Precedence is **first match wins** — rules render in the order
+ * supplied. The bundle's default inference heuristics act as the
+ * fallback when no rule matches.
  */
-declare function renderTemporalFramingCheckerScript(tf: ResolvedTemporalFraming): string;
+declare function renderPriorityRulesSection(rules: ReadonlyArray<PriorityRule>): string;
 
 /**
  * Build the requirements-analyst bundle with the supplied resolved
@@ -7291,6 +7508,30 @@ declare const upstreamConfigulatorDocsBundle: AgentRuleBundle;
  */
 declare const vitestBundle: AgentRuleBundle;
 
+/**
+ * Resolved settings for every **config-driven convention rule** — a
+ * bundle rule whose body is derived from consumer configuration rather
+ * than being fixed prose.
+ *
+ * These rules used to ship default content from their bundle and get
+ * rewritten late in `AgentConfig.resolveRules()`, which silently
+ * discarded any `ruleExtensions` append or same-name `rules` override
+ * that had already been merged into the map. Passing the resolved
+ * settings down to the bundle factories instead keeps the rule map a
+ * pure composition surface: seed once, then extend / override / exclude
+ * on top.
+ */
+interface ResolvedRuleConventions {
+    /** Settings for the five convention rules the `base` bundle owns. */
+    readonly base: ResolvedBaseConventions;
+    /** Settings for the `orchestrator-conventions` rule. */
+    readonly orchestrator: ResolvedOrchestratorConventions;
+}
+/**
+ * Convention settings applied when the consumer configures none of the
+ * config-driven conventions.
+ */
+declare const DEFAULT_RULE_CONVENTIONS: ResolvedRuleConventions;
 /**
  * Build the full list of built-in rule bundles with the supplied
  * resolved agent paths. Every path-aware bundle accepts a
@@ -7316,10 +7557,19 @@ declare const vitestBundle: AgentRuleBundle;
  * returns true; it is filtered by the `includeBaseRules` option
  * in AgentConfig.
  *
+ * Bundles that own a **config-driven convention rule** (`base`,
+ * `orchestrator`) accept their resolved convention settings via
+ * `conventions` so each rule's content is final the moment it enters
+ * the rule map. Seeding resolved content up front — instead of
+ * rewriting the rule after the map is assembled — is what lets
+ * `AgentConfigOptions.ruleExtensions` appends and consumer-supplied
+ * same-name `rules` entries compose with a convention override rather
+ * than being clobbered by it.
+ *
  * 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, issueDefaults?: ResolvedIssueDefaults, defaultAgentTier?: AgentModel, bundleAgentTiers?: ReadonlyMap<string, AgentModel>, prReviewPolicy?: ResolvedPrReviewPolicy, buildPolicy?: ResolvedBuildPolicy): ReadonlyArray<AgentRuleBundle>;
+declare function buildBuiltInBundles(paths?: ResolvedAgentPaths, issueDefaults?: ResolvedIssueDefaults, defaultAgentTier?: AgentModel, bundleAgentTiers?: ReadonlyMap<string, AgentModel>, prReviewPolicy?: ResolvedPrReviewPolicy, buildPolicy?: ResolvedBuildPolicy, conventions?: ResolvedRuleConventions): ReadonlyArray<AgentRuleBundle>;
 /**
  * Built-in rule bundles assembled with the default agent paths.
  * Preserved for backward compatibility with tests and consumers
@@ -13871,4 +14121,4 @@ declare function pinPnpmActionSetup(project: Project$1): void;
  */
 declare function pinSetupNodeVersion(project: Project$1): void;
 
-export { AGENT_MODEL, AGENT_PLATFORM, AGENT_REGISTRY_ENTRIES, AGENT_RULE_SCOPE, AGENT_TIER_ROLES, AGENT_TIER_VALUES, AUDIT_CATEGORY_ORDER, type ActionItemFilingConfig, type ActivateBranchNameEnvVarOptions, type AddStorybookOptions, type AgentCommand, AgentConfig, type AgentConfigOptions, type AgentExpansionRules, type AgentFeaturesConfig, type AgentModel, type AgentPathsConfig, type AgentPlatform, type AgentPlatformOverrides, type AgentProcedure, type AgentRegistryEntry, type AgentRule, type AgentRuleBundle, type AgentRuleScope, type AgentSkill, type AgentSubAgent, type AgentSubAgentPlatformOverrides, type AgentTier, type AgentTierConfig, type AgentTierEntry, type AnalyzeTsDocCoverageOptions, type ApiDiffCheckOptions, type ApiDiffFinding, type ApiDiffResult, ApiExtractor, type ApiExtractorOptions, type ApiExtractorReportOptions, type ApiSurfaceEntry, type ApproveMergeUpgradeOptions, AstroConfig, type AstroConfigOptions, type AstroIntegrationSpec, AstroOutput, AstroProject, type AstroProjectOptions, AuditCategory, type AuditCheckRunner, type AuditCheckRunnerContext, type AuditFinding, type AuditFindingBase, type AuditLocation, AuditMode, type AuditReport, AuditSeverity, type AwsAccount, AwsCdkProject, type AwsCdkProjectOptions, AwsDeployWorkflow, AwsDeploymentConfig, AwsDeploymentTarget, type AwsDeploymentTargetOptions, type AwsLocalDeploymentConfig, type AwsOrganization, type AwsRegion, AwsTeardownWorkflow, type AwsTeardownWorkflowOptions, BUILT_IN_BUNDLES, BUNDLE_OWNERSHIP, type BundleOwnership, CDK_BOOTSTRAP_DEFAULTS_BY_STAGE, CDK_DEPLOY_DEFAULTS_BY_STAGE, CDK_DEPLOY_METHOD, CDK_DESTROY_DEFAULTS_BY_STAGE, CDK_DIFF_DEFAULTS_BY_STAGE, CDK_DIFF_METHOD, CDK_GC_ACTION, CDK_GC_TYPE, CDK_INIT_LANGUAGE, CDK_INIT_TEMPLATE, CDK_PROGRESS, CDK_REQUIRE_APPROVAL, CDK_SYNTH_DEFAULTS_BY_STAGE, CDK_WATCH_DEFAULTS_BY_STAGE, CLAUDE_RULE_TARGET, COMPLETE_JOB_ID, CONVENTIONAL_COMMIT_TYPE_LABELS, type CdkAcknowledgeOptions, type CdkBootstrapOptions, CdkCli, type CdkCliOptions, type CdkContextOptions, type CdkDeployMethod, type CdkDeployOptions, type CdkDestroyOptions, type CdkDiffMethod, type CdkDiffOptions, type CdkDocsOptions, type CdkDoctorOptions, type CdkDriftOptions, type CdkFlagsOptions, type CdkGcAction, type CdkGcOptions, type CdkGcType, type CdkGlobalOptions, type CdkImportOptions, type CdkInitLanguage, type CdkInitOptions, type CdkInitTemplate, type CdkListOptions, type CdkMetadataOptions, type CdkMigrateOptions, type CdkNoticesOptions, type CdkOrphanOptions, type CdkProgress, type CdkPublishAssetsOptions, type CdkRefactorOptions, type CdkRequireApproval, type CdkRollbackOptions, type CdkSynthOptions, type CdkTargetOverrides, type CdkWatchOptions, type CiDeploymentConfig, type ClassTypeOptions, type ClaudeAutoModeConfig, type ClaudeHookAction, type ClaudeHookEntry, type ClaudeHooksConfig, type ClaudeMdConfig, type ClaudePermissionsConfig, type ClaudeRuleTarget, type ClaudeSandboxConfig, type ClaudeSettingsConfig, type CompileFencedSamplesOptions, 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_AUDIT_REPORT_DIR, DEFAULT_BUILD_POLICY, DEFAULT_BUNDLE_OVERRIDES, DEFAULT_DECOMPOSITION_TEMPLATE, DEFAULT_DISPATCH_MODEL, DEFAULT_DISPATCH_TO_HOUSEKEEPING_RATIO, DEFAULT_GITHUB_ISSUE_TYPE, DEFAULT_HOUSEKEEPING_MODEL, DEFAULT_ISSUE_PRIORITY, DEFAULT_ISSUE_STATUS, 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_OFF_PEAK_CRON_EXAMPLE, DEFAULT_PARTIAL_UNBLOCK_COMMENT_TEMPLATE, DEFAULT_PATHS_EXEMPT_FROM_SIZE, 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_REQUIREMENT_CATEGORY_DIRS, DEFAULT_REQUIRE_PRODUCT_CONTEXT, DEFAULT_RESOLVED_ISSUE_DEFAULTS, DEFAULT_SAMPLE_COMPILER_OPTIONS, 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_TEMPORAL_FRAMING_CADENCES, DEFAULT_TEMPORAL_FRAMING_EMIT_CHECKER, DEFAULT_TEMPORAL_FRAMING_ENABLED, DEFAULT_TEMPORAL_FRAMING_PATHS, DEFAULT_TYPE_LABELS, DEFAULT_UNBLOCK_COMMENT_TEMPLATE, DEFAULT_UNBLOCK_DEPENDENTS_ENABLED, DEFAULT_UPSTREAM_CONFIGULATOR_ENABLED, DOCS_SYNC_AUDIT_SCHEMA_VERSION, type DeployWorkflowOptions, type DeploymentMetadata, type DocReferenceRecord, type EffectiveScopeThresholds, type ExtractDocReferencesOptions, type ExtractFencedSamplesOptions, type FencedSampleRecord, type FocusArea, type FocusAreaMatch, type FocusConfig, GITHUB_ISSUE_TYPES, GITHUB_ISSUE_TYPE_BY_TITLE_PREFIX, type GitBranch, type GitHubBoardMetadata, type GitHubProjectMetadata, type GitHubSprintMetadata, type GithubIssueType, type IDependencyResolver, type IssueDefaultsConfig, type IssueDefaultsOverride, type IssueDefaultsPriority, type IssueDefaultsStatus, type IssueTemplatesConfig, type IssueTypeAssignmentStepOptions, JsiiFaker, LAYOUT_ENFORCEMENT, LAYOUT_ROOT_BY_PROJECT_TYPE, type LabelDefinition, type LayoutEnforcement, type LayoutViolation, type LinkFailureFinding, MAX_LABEL_DESCRIPTION_LENGTH, 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, type MonorepoPnpmOptions, MonorepoProject, type MonorepoProjectOptions, Nvmrc, type OrganizationMetadata, PHASE_LABEL_TYPE_MAP, PROD_DEPLOY_NAME, PROGRESS_FILES_FORMAT_VALUES, type PhaseLabelTypeOutcome, type PhaseLabelTypeResolution, PnpmWorkspace, type PnpmWorkspaceOptions, type PrReviewAutoMergeConfig, type PrReviewCiVerificationConfig, type PrReviewPolicyConfig, type PriorityRule, type ProgressFilesConfig, ProjectMetadata, type ProjectMetadataOptions, REQUIREMENTS_WRITER_PATHS, ROOT_CI_TASK_NAME, ROOT_TURBO_TASK_NAME, ReactViteSiteProject, type ReactViteSiteProjectOptions, type ReferenceMismatchCheckOptions, type ReferenceMismatchFinding, type RemoteCacheOptions, type RepositoryMetadata, type RequirementBlockFields, type RequirementCategoryDirsConfig, RequirementIssueTemplate, type RequirementIssueTemplateOptions, ResetTask, type ResetTaskOptions, type ResolvedAgentPaths, type ResolvedAgentTier, type ResolvedBuildPolicy, type ResolvedIssueDefaults, type ResolvedIssueDefaultsEntry, type ResolvedIssueTemplates, type ResolvedPrReviewAutoMerge, type ResolvedPrReviewPolicy, type ResolvedProgressFiles, type ResolvedProjectMetadata, type ResolvedRequirementCategoryDirs, type ResolvedRunRatio, type ResolvedScheduledTask, type ResolvedScheduledTasks, type ResolvedScopeGate, type ResolvedScopeGateBundleOverride, type ResolvedSharedEditing, type ResolvedSkillEvals, type ResolvedTemporalFraming, type ResolvedUnblockDependents, type RunRatioConfig, type RunScanOptions, type RunScanResult, SCHEDULED_TASK_MODEL_VALUES, SCOPE_CLASS_VALUES, SET_ISSUE_TYPE_HELPER_PATH, SHARED_EDITING_CONFLICT_STRATEGY_VALUES, STARLIGHT_ROLE, SUPPRESSED_WORKFLOW_RULE_NAMES, type SampleCompilationFailure, type SampleFailureFinding, SampleLang, type ScheduledTaskEntry, type ScheduledTaskModel, type ScheduledTaskOverride, type ScheduledTasksConfig, type ScopeClass, type ScopeGateBundleOverride, 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, TEMPORAL_FRAMING_CATEGORY_VALUES, TURBO_RUN_CONTINUE, TURBO_RUN_DRY_RUN, TURBO_RUN_LOG_ORDER, TURBO_RUN_LOG_PREFIX, TURBO_RUN_OUTPUT_LOGS, type TemplateResolveResult, type TemporalFramingCategory, type TemporalFramingConfig, TestRunner, TsDocCoverageKind, type TsDocCoverageRecord, TsdocConfig, type TsdocConfigOptions, type TsdocCoverageCheckOptions, type TsdocCoverageFinding, TurboRepo, type TurboRepoOptions, TurboRepoTask, type TurboRepoTaskOptions, type TurboRunContinue, type TurboRunDryRun, type TurboRunLogOrder, type TurboRunLogPrefix, type TurboRunOptions, type TurboRunOutputLogs, TypeScriptConfig, TypeScriptProject, type TypeScriptProjectOptions, UNKNOWN_TYPE_FALLBACK_TIER, type UnblockDependentsConfig, type UpstreamConfigulatorConfig, VALID_PRIORITY_VALUES, VALID_STATUS_VALUES, VERSION, VERSION_KEYS_SKIP, VERSION_NPM_PACKAGES, VSCodeConfig, type VersionKey, Vitest, type VitestConfigOptions, type VitestOptions, addApproveMergeUpgradeWorkflow, addBuildCompleteJob, addPlaywright, addStorybook, addSyncLabelsWorkflow, agendaBundle, analyzeTsDocCoverage, auditReportJsonSchema, awsCdkBundle, baseBundle, bcmWriterBundle, buildAgentRegistryRule, buildBaseBundle, buildBcmWriterBundle, buildBuiltInBundles, buildBusinessModelsBundle, buildCheckBlockedProcedure, buildCompanyProfileBundle, buildCustomerProfileBundle, buildDocsSyncBundle, buildGithubWorkflowBundle, buildIndustryDiscoveryBundle, buildMaintenanceAuditBundle, buildMeetingAnalysisBundle, buildOrchestratorConventionsContent, buildPeopleProfileBundle, buildPrReviewBundle, buildRegulatoryResearchBundle, buildReport, buildRequirementsAnalystBundle, buildRequirementsReviewerBundle, buildRequirementsWriterBundle, buildResearchPipelineBundle, buildSoftwareProfileBundle, buildStandardsResearchBundle, buildTurborepoBundle, buildUnblockDependentsProcedure, bundleNameForWorkflowRule, businessModelsBundle, checkDocSamplesProcedure, checkLinksProcedure, classifyIssueScope, classifyRun, companyProfileBundle, compileFencedSamples, createApiDiffCheck, createReferenceMismatchCheck, createTsdocCoverageCheck, customerProfileBundle, diffApiRollups, docsSyncBundle, emptyCategoryBuckets, extractApiProcedure, extractDocReferences, extractFencedSamples, formatLayoutViolation, formatStarlightSingletonViolation, getLatestEligibleVersion, githubIssueTypeForTitle, githubWorkflowBundle, hasAnyDocsEmittingBundle, hasAnyDownstreamIssueKindBundle, includeHiddenFilesInBuildArtifact, industryDiscoveryBundle, isPhaseLabelOwnedByExcluded, isScheduledTaskOwnedByExcluded, isSuppressedWorkflowRule, isTypeLabelOwnedByExcluded, jestBundle, labelsForPhase, maintenanceAuditBundle, meetingAnalysisBundle, mergeCdkOptions, nextRequirementIdProcedure, orchestratorBundle, parseApiRollup, peopleProfileBundle, persistAuditReport, pinPnpmActionSetup, pinSetupNodeVersion, pnpmBundle, prReviewBundle, projenBundle, referenceRecordToFinding, regulatoryResearchBundle, renderAgentTierCaseStatement, renderAgentTierSection, renderCdkAcknowledge, renderCdkBootstrap, renderCdkContext, renderCdkDeploy, renderCdkDestroy, renderCdkDiff, renderCdkDocs, renderCdkDoctor, renderCdkDrift, renderCdkFlags, renderCdkGc, renderCdkImport, renderCdkInit, renderCdkList, renderCdkMetadata, renderCdkMigrate, renderCdkNotices, renderCdkOrphan, renderCdkPublishAssets, renderCdkRefactor, renderCdkRollback, renderCdkSynth, renderCdkWatch, renderCheckDocSamplesProcedure, renderCheckLinksProcedure, renderCustomDocSectionBlock, renderCustomDocSections, renderExtractApiProcedure, renderFocusSection, renderGithubIssueTypeSection, renderGithubIssueTypeSectionLines, renderIssueTemplatesBundleHook, renderIssueTemplatesCheckerScript, renderIssueTemplatesRuleContent, renderIssueTemplatesStarterPage, renderIssueTypeAssignmentBlanket, renderIssueTypeAssignmentStep, renderMeetingTypesSection, renderNextRequirementIdProcedure, renderPhaseTypeInvariantSection, renderPhaseTypeInvariantShellHelpers, renderPriorityRulesSection, renderProgressFileName, renderProgressFilePath, renderProgressFilesBundleHook, renderProgressFilesRuleContent, renderRequirementBlock, renderRunRatioSection, renderRunRatioShellHelpers, renderScheduledTaskSkillFile, renderScheduledTasksSection, renderScopeGateSection, renderScopeGateShellHelpers, renderSetIssueTypeFallbackLines, renderSharedEditingBundleHook, renderSharedEditingHelperScript, renderSharedEditingRuleContent, renderSkillEvalsBundleHook, renderSkillEvalsRuleContent, renderSkillEvalsRunnerScript, renderSourceTierExamples, renderStripToolArtifactTagsProcedure, renderTemporalFramingCheckerScript, renderTemporalFramingRuleContent, renderTitlePrefixTypeBullets, renderUnblockDependentsScript, renderUnblockDependentsSection, requirementsAnalystBundle, requirementsReviewerBundle, requirementsWriterBundle, researchPipelineBundle, resolveAgentPaths, resolveAgentTiers, resolveAstroProjectOutdir, resolveAwsCdkProjectOutdir, resolveBuildPolicy, resolveIssueDefaults, resolveIssueTemplates, resolveModelAlias, resolveOrchestratorAssets, resolveOutdirFromPackageName, resolveOverrideForLabels, resolvePrReviewPolicy, resolveProgressFiles, resolveReactViteSiteProjectOutdir, resolveRunRatio, resolveScheduledTasks, resolveScopeGate, resolveSharedEditing, resolveSkillEvals, resolveTemplateVariables, resolveTemporalFraming, resolveTypeLabelForLabels, resolveTypeScriptProjectOutdir, resolveUnblockDependents, runScan, slackBundle, softwareProfileBundle, standardsResearchBundle, stripToolArtifactTagsProcedure, tsdocRecordToFindings, turborepoBundle, typeLabelForPhaseLabel, typescriptBundle, upstreamConfigulatorDocsBundle, validateAgentTierConfig, validateIssueDefaultsConfig, validateIssueTemplatesConfig, validateMonorepoLayout, validatePrReviewPolicyConfig, validateProgressFilesConfig, validateRunRatioConfig, validateScheduledTasksConfig, validateScopeGateConfig, validateSharedEditingConfig, validateSkillEvalsConfig, validateStarlightSingleton, validateTemporalFramingConfig, validateUnblockDependentsConfig, vitestBundle };
+export { AGENT_MODEL, AGENT_PLATFORM, AGENT_REGISTRY_ENTRIES, AGENT_RULE_SCOPE, AGENT_TIER_ROLES, AGENT_TIER_VALUES, AUDIT_CATEGORY_ORDER, type ActionItemFilingConfig, type ActivateBranchNameEnvVarOptions, type AddStorybookOptions, type AgentCommand, AgentConfig, type AgentConfigOptions, type AgentExpansionRules, type AgentFeaturesConfig, type AgentModel, type AgentPathsConfig, type AgentPlatform, type AgentPlatformOverrides, type AgentProcedure, type AgentRegistryEntry, type AgentRule, type AgentRuleBundle, type AgentRuleScope, type AgentSkill, type AgentSubAgent, type AgentSubAgentPlatformOverrides, type AgentTier, type AgentTierConfig, type AgentTierEntry, type AnalyzeTsDocCoverageOptions, type ApiDiffCheckOptions, type ApiDiffFinding, type ApiDiffResult, ApiExtractor, type ApiExtractorOptions, type ApiExtractorReportOptions, type ApiSurfaceEntry, type ApproveMergeUpgradeOptions, AstroConfig, type AstroConfigOptions, type AstroIntegrationSpec, AstroOutput, AstroProject, type AstroProjectOptions, AuditCategory, type AuditCheckRunner, type AuditCheckRunnerContext, type AuditFinding, type AuditFindingBase, type AuditLocation, AuditMode, type AuditReport, AuditSeverity, type AwsAccount, AwsCdkProject, type AwsCdkProjectOptions, AwsDeployWorkflow, AwsDeploymentConfig, AwsDeploymentTarget, type AwsDeploymentTargetOptions, type AwsLocalDeploymentConfig, type AwsOrganization, type AwsRegion, AwsTeardownWorkflow, type AwsTeardownWorkflowOptions, BUILT_IN_BUNDLES, BUNDLE_OWNERSHIP, type BundleOwnership, CDK_BOOTSTRAP_DEFAULTS_BY_STAGE, CDK_DEPLOY_DEFAULTS_BY_STAGE, CDK_DEPLOY_METHOD, CDK_DESTROY_DEFAULTS_BY_STAGE, CDK_DIFF_DEFAULTS_BY_STAGE, CDK_DIFF_METHOD, CDK_GC_ACTION, CDK_GC_TYPE, CDK_INIT_LANGUAGE, CDK_INIT_TEMPLATE, CDK_PROGRESS, CDK_REQUIRE_APPROVAL, CDK_SYNTH_DEFAULTS_BY_STAGE, CDK_WATCH_DEFAULTS_BY_STAGE, CLAUDE_RULE_TARGET, COMPLETE_JOB_ID, CONVENTIONAL_COMMIT_TYPE_LABELS, type CdkAcknowledgeOptions, type CdkBootstrapOptions, CdkCli, type CdkCliOptions, type CdkContextOptions, type CdkDeployMethod, type CdkDeployOptions, type CdkDestroyOptions, type CdkDiffMethod, type CdkDiffOptions, type CdkDocsOptions, type CdkDoctorOptions, type CdkDriftOptions, type CdkFlagsOptions, type CdkGcAction, type CdkGcOptions, type CdkGcType, type CdkGlobalOptions, type CdkImportOptions, type CdkInitLanguage, type CdkInitOptions, type CdkInitTemplate, type CdkListOptions, type CdkMetadataOptions, type CdkMigrateOptions, type CdkNoticesOptions, type CdkOrphanOptions, type CdkProgress, type CdkPublishAssetsOptions, type CdkRefactorOptions, type CdkRequireApproval, type CdkRollbackOptions, type CdkSynthOptions, type CdkTargetOverrides, type CdkWatchOptions, type CiDeploymentConfig, type ClassTypeOptions, type ClaudeAutoModeConfig, type ClaudeHookAction, type ClaudeHookEntry, type ClaudeHooksConfig, type ClaudeMdConfig, type ClaudePermissionsConfig, type ClaudeRuleTarget, type ClaudeSandboxConfig, type ClaudeSettingsConfig, type CompileFencedSamplesOptions, 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_AUDIT_REPORT_DIR, DEFAULT_BASE_CONVENTIONS, DEFAULT_BUILD_POLICY, DEFAULT_BUNDLE_OVERRIDES, DEFAULT_DECOMPOSITION_TEMPLATE, DEFAULT_DISPATCH_MODEL, DEFAULT_DISPATCH_TO_HOUSEKEEPING_RATIO, DEFAULT_GITHUB_ISSUE_TYPE, DEFAULT_HOUSEKEEPING_MODEL, DEFAULT_ISSUE_PRIORITY, DEFAULT_ISSUE_STATUS, 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_OFF_PEAK_CRON_EXAMPLE, DEFAULT_ORCHESTRATOR_CONVENTIONS, DEFAULT_PARTIAL_UNBLOCK_COMMENT_TEMPLATE, DEFAULT_PATHS_EXEMPT_FROM_SIZE, 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_REQUIREMENT_CATEGORY_DIRS, DEFAULT_REQUIRE_PRODUCT_CONTEXT, DEFAULT_RESOLVED_ISSUE_DEFAULTS, DEFAULT_RULE_CONVENTIONS, DEFAULT_SAMPLE_COMPILER_OPTIONS, 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_TEMPORAL_FRAMING_CADENCES, DEFAULT_TEMPORAL_FRAMING_EMIT_CHECKER, DEFAULT_TEMPORAL_FRAMING_ENABLED, DEFAULT_TEMPORAL_FRAMING_PATHS, DEFAULT_TYPE_LABELS, DEFAULT_UNBLOCK_COMMENT_TEMPLATE, DEFAULT_UNBLOCK_DEPENDENTS_ENABLED, DEFAULT_UPSTREAM_CONFIGULATOR_ENABLED, DOCS_SYNC_AUDIT_SCHEMA_VERSION, type DeployWorkflowOptions, type DeploymentMetadata, type DocReferenceRecord, type EffectiveScopeThresholds, type ExtractDocReferencesOptions, type ExtractFencedSamplesOptions, type FencedSampleRecord, type FocusArea, type FocusAreaMatch, type FocusConfig, GITHUB_ISSUE_TYPES, GITHUB_ISSUE_TYPE_BY_TITLE_PREFIX, type GitBranch, type GitHubBoardMetadata, type GitHubProjectMetadata, type GitHubSprintMetadata, type GithubIssueType, type IDependencyResolver, ISSUE_TEMPLATES_GENERATED_SUFFIX, type IssueDefaultsConfig, type IssueDefaultsOverride, type IssueDefaultsPriority, type IssueDefaultsStatus, type IssueTemplateRecipeStub, type IssueTemplatesConfig, type IssueTypeAssignmentStepOptions, JsiiFaker, LAYOUT_ENFORCEMENT, LAYOUT_ROOT_BY_PROJECT_TYPE, type LabelDefinition, type LayoutEnforcement, type LayoutViolation, type LinkFailureFinding, MAX_LABEL_DESCRIPTION_LENGTH, 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, type MonorepoPnpmOptions, MonorepoProject, type MonorepoProjectOptions, Nvmrc, type OrganizationMetadata, PHASE_LABEL_TYPE_MAP, PROD_DEPLOY_NAME, PROGRESS_FILES_FORMAT_VALUES, type PhaseLabelTypeOutcome, type PhaseLabelTypeResolution, PnpmWorkspace, type PnpmWorkspaceOptions, type PrReviewAutoMergeConfig, type PrReviewCiVerificationConfig, type PrReviewPolicyConfig, type PriorityRule, type ProgressFilesConfig, ProjectMetadata, type ProjectMetadataOptions, REQUIREMENTS_WRITER_PATHS, ROOT_CI_TASK_NAME, ROOT_TURBO_TASK_NAME, ReactViteSiteProject, type ReactViteSiteProjectOptions, type ReferenceMismatchCheckOptions, type ReferenceMismatchFinding, type RemoteCacheOptions, type RepositoryMetadata, type RequirementBlockFields, type RequirementCategoryDirsConfig, RequirementIssueTemplate, type RequirementIssueTemplateOptions, ResetTask, type ResetTaskOptions, type ResolvedAgentPaths, type ResolvedAgentTier, type ResolvedBaseConventions, type ResolvedBuildPolicy, type ResolvedIssueDefaults, type ResolvedIssueDefaultsEntry, type ResolvedIssueTemplates, type ResolvedOrchestratorConventions, type ResolvedPrReviewAutoMerge, type ResolvedPrReviewPolicy, type ResolvedProgressFiles, type ResolvedProjectMetadata, type ResolvedRequirementCategoryDirs, type ResolvedRuleConventions, type ResolvedRunRatio, type ResolvedScheduledTask, type ResolvedScheduledTasks, type ResolvedScopeGate, type ResolvedScopeGateBundleOverride, type ResolvedSharedEditing, type ResolvedSkillEvals, type ResolvedTemporalFraming, type ResolvedUnblockDependents, type RunRatioConfig, type RunScanOptions, type RunScanResult, SCHEDULED_TASK_MODEL_VALUES, SCOPE_CLASS_VALUES, SET_ISSUE_TYPE_HELPER_PATH, SHARED_EDITING_CONFLICT_STRATEGY_VALUES, STARLIGHT_ROLE, SUPPRESSED_WORKFLOW_RULE_NAMES, type SampleCompilationFailure, type SampleFailureFinding, SampleLang, type ScheduledTaskEntry, type ScheduledTaskModel, type ScheduledTaskOverride, type ScheduledTasksConfig, type ScopeClass, type ScopeGateBundleOverride, 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, TEMPORAL_FRAMING_CATEGORY_VALUES, TURBO_RUN_CONTINUE, TURBO_RUN_DRY_RUN, TURBO_RUN_LOG_ORDER, TURBO_RUN_LOG_PREFIX, TURBO_RUN_OUTPUT_LOGS, type TemplateResolveResult, type TemporalFramingCategory, type TemporalFramingConfig, TestRunner, TsDocCoverageKind, type TsDocCoverageRecord, TsdocConfig, type TsdocConfigOptions, type TsdocCoverageCheckOptions, type TsdocCoverageFinding, TurboRepo, type TurboRepoOptions, TurboRepoTask, type TurboRepoTaskOptions, type TurboRunContinue, type TurboRunDryRun, type TurboRunLogOrder, type TurboRunLogPrefix, type TurboRunOptions, type TurboRunOutputLogs, TypeScriptConfig, TypeScriptProject, type TypeScriptProjectOptions, UNKNOWN_TYPE_FALLBACK_TIER, type UnblockDependentsConfig, type UpstreamConfigulatorConfig, VALID_PRIORITY_VALUES, VALID_STATUS_VALUES, VERSION, VERSION_KEYS_SKIP, VERSION_NPM_PACKAGES, VSCodeConfig, type VersionKey, Vitest, type VitestConfigOptions, type VitestOptions, addApproveMergeUpgradeWorkflow, addBuildCompleteJob, addPlaywright, addStorybook, addSyncLabelsWorkflow, agendaBundle, analyzeTsDocCoverage, auditReportJsonSchema, awsCdkBundle, baseBundle, bcmWriterBundle, buildAgentRegistryRule, buildBaseBundle, buildBcmWriterBundle, buildBuiltInBundles, buildBusinessModelsBundle, buildCheckBlockedProcedure, buildCompanyProfileBundle, buildCustomerProfileBundle, buildDocsSyncBundle, buildGithubWorkflowBundle, buildIndustryDiscoveryBundle, buildMaintenanceAuditBundle, buildMeetingAnalysisBundle, buildOrchestratorBundle, buildOrchestratorConventionsContent, buildPeopleProfileBundle, buildPrReviewBundle, buildRegulatoryResearchBundle, buildReport, buildRequirementsAnalystBundle, buildRequirementsReviewerBundle, buildRequirementsWriterBundle, buildResearchPipelineBundle, buildSoftwareProfileBundle, buildStandardsResearchBundle, buildTurborepoBundle, buildUnblockDependentsProcedure, bundleNameForWorkflowRule, businessModelsBundle, checkDocSamplesProcedure, checkLinksProcedure, classifyIssueScope, classifyRun, collectIssueTemplateRecipeStubs, companyProfileBundle, compileFencedSamples, createApiDiffCheck, createReferenceMismatchCheck, createTsdocCoverageCheck, customerProfileBundle, diffApiRollups, docsSyncBundle, emptyCategoryBuckets, extractApiProcedure, extractDocReferences, extractFencedSamples, formatLayoutViolation, formatStarlightSingletonViolation, getLatestEligibleVersion, githubIssueTypeForTitle, githubWorkflowBundle, hasAnyDocsEmittingBundle, hasAnyDownstreamIssueKindBundle, includeHiddenFilesInBuildArtifact, industryDiscoveryBundle, isPhaseLabelOwnedByExcluded, isScheduledTaskOwnedByExcluded, isSuppressedWorkflowRule, isTypeLabelOwnedByExcluded, issueTemplatesChildGlob, issueTemplatesGeneratedPath, jestBundle, labelsForPhase, maintenanceAuditBundle, meetingAnalysisBundle, mergeCdkOptions, nextRequirementIdProcedure, orchestratorBundle, parseApiRollup, peopleProfileBundle, persistAuditReport, pinPnpmActionSetup, pinSetupNodeVersion, pnpmBundle, prReviewBundle, projenBundle, referenceRecordToFinding, regulatoryResearchBundle, renderAgentTierCaseStatement, renderAgentTierSection, renderCdkAcknowledge, renderCdkBootstrap, renderCdkContext, renderCdkDeploy, renderCdkDestroy, renderCdkDiff, renderCdkDocs, renderCdkDoctor, renderCdkDrift, renderCdkFlags, renderCdkGc, renderCdkImport, renderCdkInit, renderCdkList, renderCdkMetadata, renderCdkMigrate, renderCdkNotices, renderCdkOrphan, renderCdkPublishAssets, renderCdkRefactor, renderCdkRollback, renderCdkSynth, renderCdkWatch, renderCheckDocSamplesProcedure, renderCheckLinksProcedure, renderCustomDocSectionBlock, renderCustomDocSections, renderExtractApiProcedure, renderFocusSection, renderGithubIssueTypeSection, renderGithubIssueTypeSectionLines, renderIssueTemplateLabelsCheckerScript, renderIssueTemplatesBundleHook, renderIssueTemplatesCheckerScript, renderIssueTemplatesGeneratedPage, renderIssueTemplatesRuleContent, renderIssueTemplatesStarterPage, renderIssueTypeAssignmentBlanket, renderIssueTypeAssignmentStep, renderMeetingTypesSection, renderNextRequirementIdProcedure, renderPhaseTypeInvariantSection, renderPhaseTypeInvariantShellHelpers, renderPriorityRulesSection, renderProgressFileName, renderProgressFilePath, renderProgressFilesBundleHook, renderProgressFilesRuleContent, renderRequirementBlock, renderRunRatioSection, renderRunRatioShellHelpers, renderScheduledTaskSkillFile, renderScheduledTasksSection, renderScopeGateSection, renderScopeGateShellHelpers, renderSetIssueTypeFallbackLines, renderSharedEditingBundleHook, renderSharedEditingHelperScript, renderSharedEditingRuleContent, renderSkillEvalsBundleHook, renderSkillEvalsRuleContent, renderSkillEvalsRunnerScript, renderSourceTierExamples, renderStripToolArtifactTagsProcedure, renderTemporalFramingCheckerScript, renderTemporalFramingRuleContent, renderTitlePrefixTypeBullets, renderUnblockDependentsScript, renderUnblockDependentsSection, requirementsAnalystBundle, requirementsReviewerBundle, requirementsWriterBundle, researchPipelineBundle, resolveAgentPaths, resolveAgentTiers, resolveAstroProjectOutdir, resolveAwsCdkProjectOutdir, resolveBuildPolicy, resolveIssueDefaults, resolveIssueTemplates, resolveModelAlias, resolveOrchestratorAssets, resolveOutdirFromPackageName, resolveOverrideForLabels, resolvePrReviewPolicy, resolveProgressFiles, resolveReactViteSiteProjectOutdir, resolveRunRatio, resolveScheduledTasks, resolveScopeGate, resolveSharedEditing, resolveSkillEvals, resolveTemplateVariables, resolveTemporalFraming, resolveTypeLabelForLabels, resolveTypeScriptProjectOutdir, resolveUnblockDependents, runScan, slackBundle, softwareProfileBundle, standardsResearchBundle, stripToolArtifactTagsProcedure, tsdocRecordToFindings, turborepoBundle, typeLabelForPhaseLabel, typescriptBundle, upstreamConfigulatorDocsBundle, validateAgentTierConfig, validateIssueDefaultsConfig, validateIssueTemplatesConfig, validateMonorepoLayout, validatePrReviewPolicyConfig, validateProgressFilesConfig, validateRunRatioConfig, validateScheduledTasksConfig, validateScopeGateConfig, validateSharedEditingConfig, validateSkillEvalsConfig, validateStarlightSingleton, validateTemporalFramingConfig, validateUnblockDependentsConfig, vitestBundle };