@kici-dev/orchestrator 0.1.10 → 0.1.11

package/dist/agent/dispatcher.d.ts

@@ -91,7 +91,7 @@ export declare class Dispatcher {
         /** Optional hook called when no agent matches the job's labels.
          *  When set, receives the per-job `resources` so the scaler can apply
          *  per-scaler / per-orchestrator / per-machine caps before spawning. */
-        onNoMatchingAgent?: (labels: string[], jobId: string, excludeLabels: string[], resources?: ResourceRequest) => Promise<ScaleResult>;
+        onNoMatchingAgent?: (labels: string[], jobId: string, runId: string, excludeLabels: string[], resources?: ResourceRequest) => Promise<ScaleResult>;
         /** Max reconnection delay from agent config (default 60s). Used to derive grace period. */
         maxReconnectDelayMs?: number;
         /** Callback when a recovery timer expires and the job is permanently failed. */

package/dist/cli/service/types.d.ts

@@ -36,6 +36,19 @@ export interface ServiceConfig {
      * (e.g. `["/opt/kici/dist/server.js"]`); empty for a self-launching binary.
      */
     args?: string[];
+    /**
+     * Node bin dir to guarantee on the generated unit's PATH.
+     *
+     * The bare-metal scaler spawns the kici-agent node script, so `node` must be
+     * findable on the orchestrator's PATH. When the service is installed with an
+     * explicit `--binary` (a wrapper script), {@link executablePath} points at the
+     * wrapper, not node — so its dirname is the wrong directory. The install path
+     * sets this to `path.dirname(process.execPath)` (the node actually running the
+     * install command), which is the correct node bin dir regardless of `--binary`.
+     * Optional: lifecycle commands that don't regenerate the unit leave it unset,
+     * and the unit generators fall back to `dirname(executablePath)`.
+     */
+    nodeBinDir?: string;
     /** Path to the environment file (.env). */
     envFilePath: string;
     /** Working directory for the service process. */