@bakers-build/conductor 0.0.0-stage → 0.1.0-next.42

package/dist/src/config.d.ts

@@ -0,0 +1,109 @@
+import { type BbConnectionConfig } from '@bakers-build/core';
+import type { AgentCandidate } from './plugins/plugins.js';
+import type { ConductorEngineConfig, ConductorFileConfig } from './types.js';
+export { findBbDir, resolveConfigPath, } from '@bakers-build/core';
+/**
+ * Default agent prompt - the project instruction contract. One run works EXACTLY one state;
+ * the agent must stop instead of running the whole flow in one session. The run
+ * is closed automatically when the ticket state changes on the next claim - the
+ * agent does not release it. Run mechanics live here (not in the repo's
+ * WORKFLOW.md). The prompt points directly at the matching project-owned state
+ * section and does not prescribe an agent skill. A conductor config may override
+ * it via the `prompt` field.
+ *
+ * The ticket + its comments are NOT embedded (BB-112): embedding unbounded
+ * ticket content into a single typed pane line overran the PTY canonical line
+ * cap and truncated the dispatch command. Instead the prompt is a bounded,
+ * constant-size pointer and the agent reads the ticket + all comments at run
+ * start via `bakers dropsh read … --include comments`.
+ *
+ * herdr no longer types this into the pane: the launch command goes to a file
+ * that a short `sh '<file>'` line runs (BB-635), so its length is not bound
+ * by the tty canonical cap (macOS 1024 B, Linux 4096 B). The prompt is still
+ * kept single-line (BB-128 test).
+ * Placeholders: `{identifier}`, `{state}`, `{runUuid}` ({state} falls back to
+ * `qualification` for unclassified tickets).
+ *
+ * WHERE THE PROMPT SENDS THE AGENT, and why it no longer names a WORKFLOW.md
+ * section. This used to say `execute only its ordered "State: {state}" section`,
+ * which described the pre-BB-204 loader: WORKFLOW.md then carried one ordered
+ * `## State: <state>` section per state. BB-204 replaced that with a pure
+ * loader — WORKFLOW.md lists skills, each skill self-declares the
+ * `(work_type, workflow, step)` triple it owns, and the step's flow lives in the
+ * skill. No project's WORKFLOW.md has carried a `State:` section since.
+ *
+ * The prompt kept pointing at one anyway, and that is not cosmetic: a dispatched
+ * agent that reads the instruction literally finds no such section and STOPS.
+ * Observed on a fixture run — "WORKFLOW.md has no ordered State: spec section;
+ * it instead declares skill-based routing. Stopped at this configuration
+ * mismatch." Agents that completed runs were working around the prompt rather
+ * than following it, which is why this survived so long: it failed silently and
+ * only against the most literal readers.
+ */
+export declare const DEFAULT_AGENT_PROMPT: string;
+/**
+ * Resolve the `agent` slot into candidate(s), **preserving the authored shape**:
+ * a single descriptor/plugin/wrapper → a single `AgentCandidate`, an array →
+ * `AgentCandidate[]`. Each entry is either a bare descriptor/plugin or a
+ * `{ agent, priority? }` wrapper; the inner agent value is resolved through the
+ * same `agent` kind-guard as any slot, and a `priority` function is preserved
+ * verbatim (AC-1, AC-2). Normalization to a list happens at selection time.
+ */
+export declare function resolveAgents(raw: unknown, configPath: string): Promise<AgentCandidate | AgentCandidate[]>;
+/**
+ * Load the ENGINE half of a conductor config (BB-201 split model). Reads
+ * remote/executor/agent/workspace + project/states/machine_id/label/prompt/
+ * scheduler/hooks — and deliberately NOT `site` or the auth `plugins`, which now
+ * live in a `bakers.config.js` connection config. The conductor command composes
+ * the two via `composeConductorConfig`. A legacy `conductor.config.js` still
+ * carrying `site`/`plugins` loads fine — those two keys are simply ignored here
+ * (the connection loader reads them, back-compat).
+ */
+export declare function loadConductorConfig(configFile: string): Promise<ConductorEngineConfig>;
+/**
+ * Compose the full `ConductorFileConfig` the engine consumes from the engine
+ * half (`loadConductorConfig`) and the connection half (`loadBbConfig`). The
+ * connection supplies `site` + the auth `plugins`; `ensureAuthenticated` /
+ * `selectRemote` read them exactly as before — the fields just arrive from
+ * `bakers.config.js` now.
+ */
+export declare function composeConductorConfig(engine: ConductorEngineConfig, connection: Pick<BbConnectionConfig, 'site' | 'plugins'>): ConductorFileConfig;
+/**
+ * The conductor **stems** in a `.bakers/` dir — the file naming predicate of
+ * BB-137: exactly `conductor.config.js` (stem `conductor`) or
+ * `<variant>.conductor.config.js` (stem `<variant>`). The resolution itself
+ * lives in `@bakers-build/core` (re-exported above); this is the enumeration.
+ */
+export declare function configStems(bakersDir: string): string[];
+/** Map a conductor stem back to its file name. */
+export declare function fileForStem(stem: string): string;
+/**
+ * List the conductor-config **file names** in a `.bakers/` dir, using the same
+ * naming predicate the loader uses (`configStems`). This is the only supported
+ * enumeration for the `@bakers-build/upgrade-project` states-strip: it visits the
+ * default `conductor.config.js` + every `<variant>.conductor.config.js`, and
+ * never an unrelated JS config (`vite.config.js`, the near-miss
+ * `myconductor.config.js`).
+ */
+export declare function listConductorConfigFiles(bakersDir: string): string[];
+/**
+ * Remove the obsolete `states:` array property from a conductor-config JS
+ * source (BB-207 made `states` optional — empty ⇒ serve all claimable
+ * states — so `@bakers-build/upgrade-project` drops the now-dead key). Pure string
+ * transform: it strips the `states: [ ... ]` property (line form or inline in
+ * an object literal) with its trailing comma, and rewrites nothing else. A
+ * `substates:`/other key containing "states" is not matched.
+ */
+export declare function stripStatesFromConfigSource(source: string): string;
+/**
+ * Strip the `site:` and `plugins:` properties from an engine config's
+ * `export default { … }` (with their leading comment/whitespace), plus the
+ * now-orphaned connection preamble consts. Returns the rewritten source and the
+ * list of object keys removed (`[]` — source returned unchanged — when there is
+ * nothing connection-related to remove). remote/executor/agent/workspace/hooks/
+ * project/machine_id/loadLocal are left intact.
+ */
+export declare function stripLegacyConnectionFromConfigSource(source: string): {
+    text: string;
+    removed: string[];
+};