@gaia-ai/conductor 0.5.5 → 0.6.1

package/dist/src/config.d.ts

@@ -1,14 +1,15 @@
-import type { AgentCandidate, ConductorFileConfig } from '@gaia-ai/core';
+import { type GaiaConnectionConfig } from '@gaia-ai/core';
+import type { AgentCandidate } from './plugins/plugins.js';
+import type { ConductorEngineConfig, ConductorFileConfig } from './types.js';
+export { findGaiaDir, resolveConfigPath, } from '@gaia-ai/core';
 /**
- * Default agent prompt - the GAIA run contract. One run works EXACTLY one state;
+ * 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 routes through the gaia skill (`ticket:run`) rather
- * than pointing at WORKFLOW.md directly (GAIA-125): the intake line + state
- * engine are a skill mechanic, so a bare "follow WORKFLOW.md" pointer left the
- * intake line unprinted unless an external skill-forcing hook happened to fire. A
- * conductor config may override via the `prompt` field.
+ * 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 (GAIA-112): embedding unbounded
  * ticket content into a single typed pane line overran the PTY canonical line
@@ -31,7 +32,7 @@ import type { AgentCandidate, ConductorFileConfig } from '@gaia-ai/core';
  * wrapper, GAIA-118, was the thing that re-inflated the line past the cap and
  * truncated it mid-quote).
  * Placeholders: `{identifier}`, `{state}`, `{runUuid}` ({state} falls back to
- * `triage` for unclassified tickets).
+ * `qualification` for unclassified tickets).
  */
 export declare const DEFAULT_AGENT_PROMPT: string;
 /**
@@ -44,19 +45,59 @@ export declare const DEFAULT_AGENT_PROMPT: string;
  */
 export declare function resolveAgents(raw: unknown, configPath: string): Promise<AgentCandidate | AgentCandidate[]>;
 /**
- * Resolve the conductor config path from `cwd`.
- *
- * 1. An explicit `--config` / `$GAIA_CONDUCTOR_CONFIG` wins verbatim (no walk).
- * 2. Otherwise walk root-ward to the nearest `.gaia/` dir holding a conductor config
- *    — so any subdirectory of a project/worktree resolves the same dir.
- *    - A `--conductor <name>` / `$GAIA_CONDUCTOR` selector resolves the stem's
- *      file (`conductor` → `conductor.config.js`, else
- *      `<name>.conductor.config.js`; error listing the stems if absent).
- *    - No selector: `conductor.config.js` present → it is the default; else
- *      exactly one config → use it (back-compat); else → error naming the
- *      stems + the selector.
- * 3. No `.gaia/` config anywhere up the tree → an actionable `gaia init` error
- *    (never leak a raw "Cannot find module" from a later import()).
- */
-export declare function resolveConfigPath(override?: string, cwd?: string, conductorName?: string): string;
-export declare function loadConductorConfig(configFile: string): Promise<ConductorFileConfig>;
+ * Load the ENGINE half of a conductor config (GAIA-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 `gaia.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 (`loadGaiaConfig`). The
+ * connection supplies `site` + the auth `plugins`; `ensureAuthenticated` /
+ * `selectRemote` read them exactly as before — the fields just arrive from
+ * `gaia.config.js` now.
+ */
+export declare function composeConductorConfig(engine: ConductorEngineConfig, connection: Pick<GaiaConnectionConfig, 'site' | 'plugins'>): ConductorFileConfig;
+/**
+ * The conductor **stems** in a `.gaia/` dir — the file naming predicate of
+ * GAIA-137: exactly `conductor.config.js` (stem `conductor`) or
+ * `<variant>.conductor.config.js` (stem `<variant>`). The resolution itself
+ * lives in `@gaia-ai/core` (re-exported above); this is the enumeration.
+ */
+export declare function configStems(gaiaDir: 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 `.gaia/` dir, using the same
+ * naming predicate the loader uses (`configStems`). This is the only supported
+ * enumeration for the `@gaia/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(gaiaDir: string): string[];
+/**
+ * Remove the obsolete `states:` array property from a conductor-config JS
+ * source (GAIA-207 made `states` optional — empty ⇒ serve all claimable
+ * states — so `@gaia/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[];
+};