@kici-dev/orchestrator 0.1.16 → 0.1.18

package/dist/cli/service/platform-detect.d.ts

@@ -37,6 +37,11 @@ export declare function isRoot(): boolean;
  *
  * Used by the instance index (`<kiciRoot>/instances.json`) which lives
  * outside any per-instance subdir, and as the base for {@link getConfigDir}.
+ *
+ * `KICI_CONFIG_ROOT` overrides the platform default for both privilege scopes.
+ * It exists so a test harness (or a sandboxed run) can point the instance index
+ * at an isolated directory instead of sharing the host's `~/.config/kici/` —
+ * which otherwise lets concurrent installs clobber each other's index.
  */
 export declare function kiciConfigRoot(isUserLevel: boolean): string;
 /**

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

@@ -5,7 +5,7 @@
  * journalctl, and loginctl commands. Supports both system-level
  * (/etc/systemd/system/) and user-level (~/.config/systemd/user/) services.
  */
-import type { DiscoveredInstance, ServiceConfig, ServiceManager, ServiceStatus, LogOptions } from './types.js';
+import type { DiscoveredInstance, ServiceConfig, ServiceManager, ServiceStatus, LogOptions, LaunchSpec } from './types.js';
 /**
  * Check whether linger is already enabled for a user.
  *
@@ -37,6 +37,7 @@ export declare class SystemdServiceManager implements ServiceManager {
     status(config: ServiceConfig): Promise<ServiceStatus>;
     logs(config: ServiceConfig, options: LogOptions): Promise<void>;
     isInstalled(config: ServiceConfig): Promise<boolean>;
+    readLaunchSpec(config: ServiceConfig): Promise<LaunchSpec | null>;
     list(isUserLevel: boolean): Promise<DiscoveredInstance[]>;
 }
 //# sourceMappingURL=systemd.d.ts.map

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

@@ -68,6 +68,28 @@ export interface ServiceConfig {
      * Optional during lifecycle ops that don't regenerate the unit; required on install.
      */
     component?: 'orchestrator' | 'agent';
+    /**
+     * The deploy folder that holds this instance's manifest. Embedded in the unit
+     * (X-KiCI-InstanceDir for systemd, KiCIInstanceDir for launchd,
+     * dev.kici.instance-dir for compose, a description suffix for Windows) so
+     * per-driver `list()` scans can recover the deploy folder straight from the
+     * init system — making the instance index a true rebuildable cache rather
+     * than the sole source of the name→folder mapping.
+     *
+     * Optional during lifecycle ops that don't regenerate the unit; set on install.
+     */
+    instanceDir?: string;
+}
+/**
+ * The launch command an installed init unit will actually execute, parsed
+ * back out of the unit/plist/service registration. `execPath` is the binary
+ * the init system runs (for a Node-launched server, the node binary); `args`
+ * are everything after it (for a Node-launched server, the resolved entry
+ * script path). Returned by {@link ServiceManager.readLaunchSpec}.
+ */
+export interface LaunchSpec {
+    execPath: string;
+    args: string[];
 }
 /** Current state of a service. */
 export type ServiceState = 'running' | 'stopped' | 'failed' | 'unknown';
@@ -101,6 +123,12 @@ export interface DiscoveredInstance {
     isUserLevel: boolean;
     /** The component this unit belongs to, decoded from the unit's KiCI marker. */
     component: 'orchestrator' | 'agent';
+    /**
+     * The deploy folder recovered from the unit's KiCI instance-dir marker, when
+     * the unit carries one. Undefined for units installed before the marker
+     * existed (the index cache remains the fallback for those).
+     */
+    instanceDir?: string;
 }
 /**
  * Interface that all platform-specific service managers must implement.
@@ -134,5 +162,14 @@ export interface ServiceManager {
      * (systemd, launchd); ignored on Windows/compose.
      */
     list(isUserLevel: boolean): Promise<DiscoveredInstance[]>;
+    /**
+     * Read the launch command the installed unit will actually execute, parsed
+     * back out of the init system's own record (systemd ExecStart, launchd
+     * ProgramArguments, windows service binPath). Returns null when the unit is
+     * not installed, its launch spec can't be parsed, or the platform has no
+     * node-launched entry to resolve (compose). Used by the npm-source upgrade to
+     * verify the version that will run before reporting success.
+     */
+    readLaunchSpec(config: ServiceConfig): Promise<LaunchSpec | null>;
 }
 //# sourceMappingURL=types.d.ts.map

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

@@ -6,7 +6,7 @@
  * dependency on first use. Service configuration (auto-start, recovery)
  * is handled via sc.exe.
  */
-import type { ServiceManager, ServiceConfig, ServiceStatus, LogOptions, DiscoveredInstance } from './types.js';
+import type { ServiceManager, ServiceConfig, ServiceStatus, LogOptions, DiscoveredInstance, LaunchSpec } from './types.js';
 export declare class WindowsServiceManager implements ServiceManager {
     install(config: ServiceConfig): Promise<void>;
     uninstall(config: ServiceConfig): Promise<void>;
@@ -17,5 +17,6 @@ export declare class WindowsServiceManager implements ServiceManager {
     logs(config: ServiceConfig, _options: LogOptions): Promise<void>;
     isInstalled(config: ServiceConfig): Promise<boolean>;
     list(isUserLevel: boolean): Promise<DiscoveredInstance[]>;
+    readLaunchSpec(config: ServiceConfig): Promise<LaunchSpec | null>;
 }
 //# sourceMappingURL=windows.d.ts.map