@dokebi/cli 0.4.1 → 0.4.26

package/dist/server.d.ts

@@ -75,6 +75,13 @@ export interface ProcessInfo {
  * be alive, so callers never treat that as a stale pid file.
  */
 export type ProcessReader = (pid: number) => Promise<ProcessInfo | undefined>;
+/**
+ * Whether a /proc read failed because the process is gone: ENOENT (no /proc/<pid>), or ESRCH,
+ * which Linux returns when the process exits while one of its files is open. Anything else
+ * (permissions, a changed /proc) is a failure. ESRCH was found by the v0.4.1 tag pipeline: an
+ * app that stopped during `stop`'s check ended as PROCESS_INFO_FAILED.
+ */
+export declare function procGone(error: unknown): boolean;
 export declare function status(root: string, 
 /** Tests replace how a process is read; the CLI uses ps (/proc on Linux). */
 read?: ProcessReader, 
@@ -96,6 +103,14 @@ export declare function proveInstance(root: string, record: Pick<PidRecord, 'tok
     tried: string[];
     reason?: string;
 }>;
+export declare function checkProject(root: string): Promise<string>;
+/**
+ * R1 T4 review: why a start failed, from the app log of this start only (after its last start
+ * mark): the first record with an error, as `<code>: <first line>` and, when the error has
+ * causes, `… <its last Caused by line>`. A START_FAILED said only "exited with code 1", and its
+ * tail began with an earlier start's lines. Undefined when no record says.
+ */
+export declare function startFailureCause(lines: readonly string[]): string | undefined;
 export interface LogOptions {
     /** Rotate app.log when it would pass this size (default 50 MB). */
     readonly logMaxBytes?: number;
@@ -178,12 +193,43 @@ export declare function stopStarted(root: string, started: Pick<StartResult, 'pi
 export declare function logs(root: string, lines?: number, follow?: boolean, write?: (text: string) => void, signal?: AbortSignal): Promise<void>;
 /** Runs the app in the foreground and forwards SIGINT/SIGTERM; resolves with its exit code. */
 export declare function foreground(root: string): Promise<number>;
+/** The installed version of a package, looked up like Node does (node_modules up the tree). */
+export declare function installedVersion(root: string, name: string): [number, number, number] | undefined;
 /**
  * Development loop: runs the app, restarts it (SIGTERM, drain, start) 300 ms after a change in
- * src/, dokebi.yaml or .env. With a Vite config, Inertia views come from the Vite dev server
- * (HMR, D-0045) when template-inertia supports it, otherwise from watch builds that restart the
- * app. With template-inertia 0.4.0 that Vite is one host process beside the app, shared by every
- * cluster worker and kept across app restarts (D-0045 addendum 3); older ones start it inside the app.
+ * src/, dokebi.yaml or .env (a path whose state differs from the recorded one, see dev-watch.ts).
+ * D-0154: a change of dokebi.yaml alone is first offered to the running app: when every changed
+ * option is reloadable it applies them and keeps running; an invalid file keeps the app as it is;
+ * anything else (an option that needs a restart, an app without reloads) restarts it.
+ * With a Vite config, Inertia views come from the Vite dev server (HMR, D-0045) when
+ * template-inertia supports it, otherwise from watch builds that restart the app. With
+ * template-inertia 0.4.0 that Vite is one host process beside the app, shared by every cluster
+ * worker and kept across app restarts (D-0045 addendum 3); older ones start it inside the app.
  * The first Ctrl+C drains everything; a second one kills.
  */
 export declare function dev(root: string, say: (line: string) => void): Promise<number>;
+/** What `dokebi reload` found and did (D-0154). */
+export interface ReloadResult {
+    readonly running: boolean;
+    readonly pid?: number;
+    /** `applied`, `unchanged`, or `unknown` (no outcome line within the timeout). */
+    readonly outcome?: 'applied' | 'unchanged' | 'unknown';
+    readonly code?: string;
+    /** The configuration revision after the reload, when the app said it. */
+    readonly revision?: number;
+    /** Changed option paths the app named (never values). */
+    readonly paths?: string[];
+    readonly ms?: number;
+    readonly proof?: Proof;
+    /** Who sent SIGHUP: this command, or the app's log writer (a sandbox per command). */
+    readonly via?: 'signal' | 'log-writer';
+    readonly warnings?: string[];
+}
+/**
+ * `dokebi reload` (D-0154): asks the background app to read dokebi.yaml again (SIGHUP to the pid
+ * `start` recorded, proven like `stop`; through its log writer when this shell may not signal
+ * it), then reads its outcome from .dokebi/run/app.log. Options marked reloadable apply without
+ * a restart; an option that needs one (`RELOAD_RESTART_REQUIRED`), an invalid file
+ * (`RELOAD_INVALID`) or a plugin that could not prepare (`RELOAD_FAILED`) change nothing.
+ */
+export declare function reload(root: string, timeoutMs?: number, read?: ProcessReader, kill?: ProcessSignaller): Promise<ReloadResult>;