@agimon-ai/po-workflow 0.0.0-alpha.91 → 0.0.0-alpha.93

package/dist/cli.cjs

@@ -528,6 +528,40 @@ function createHostRunCommand(dependencies = {}) {
 }
 const hostRunCommand = createHostRunCommand();
 //#endregion
+//#region src/bin/workflowCommands/flushStdout.ts
+/**
+* Stdout Flush Utility
+*
+* DESIGN PATTERNS:
+* - Small awaitable wrapper around a stream write callback
+*
+* CODING STANDARDS:
+* - Resolve rather than reject so a closed pipe cannot fail a successful command
+*
+* AVOID:
+* - Calling process.exit() straight after writing a large payload to stdout
+*/
+const EMPTY_CHUNK = "";
+/**
+* Wait for pending stdout writes to reach the OS before the process exits.
+*
+* Node buffers stdout asynchronously when it is a pipe (but writes synchronously
+* to files and TTYs). `process.exit()` discards whatever is still buffered, so a
+* command that writes a large payload and exits immediately silently truncates
+* its output at the pipe buffer size (64KB on macOS) and emits invalid JSON.
+* Writing an empty chunk and awaiting its flush callback guarantees every earlier
+* write has drained.
+*
+* A write error (for example EPIPE when the reader closed early, as `| head`
+* does) resolves instead of rejecting: the command already produced its output
+* and must not be reported as failed.
+*/
+async function flushStdout(stream = process.stdout) {
+	await new Promise((resolve) => {
+		stream.write(EMPTY_CHUNK, () => resolve());
+	});
+}
+//#endregion
 //#region src/bin/workflowCommands/inspectWorkflow.ts
 function parseFormat$1(value) {
 	if (value !== "json") throw new commander.InvalidArgumentError("Expected \"json\".");
@@ -564,6 +598,7 @@ function createInspectWorkflowCommand(dependencies = {}) {
 				definition,
 				jobOrder
 			})}\n`);
+			await flushStdout();
 			exit(0);
 		} catch (error) {
 			writeStderr(`Error inspecting workflow: ${error instanceof Error ? error.message : String(error)}\n`);
@@ -596,40 +631,6 @@ function createLaunchProcessCommand(dependencies = {}) {
 }
 const launchProcessCommand = createLaunchProcessCommand();
 //#endregion
-//#region src/bin/workflowCommands/flushStdout.ts
-/**
-* Stdout Flush Utility
-*
-* DESIGN PATTERNS:
-* - Small awaitable wrapper around a stream write callback
-*
-* CODING STANDARDS:
-* - Resolve rather than reject so a closed pipe cannot fail a successful command
-*
-* AVOID:
-* - Calling process.exit() straight after writing a large payload to stdout
-*/
-const EMPTY_CHUNK = "";
-/**
-* Wait for pending stdout writes to reach the OS before the process exits.
-*
-* Node buffers stdout asynchronously when it is a pipe (but writes synchronously
-* to files and TTYs). `process.exit()` discards whatever is still buffered, so a
-* command that writes a large payload and exits immediately silently truncates
-* its output at the pipe buffer size (64KB on macOS) and emits invalid JSON.
-* Writing an empty chunk and awaiting its flush callback guarantees every earlier
-* write has drained.
-*
-* A write error (for example EPIPE when the reader closed early, as `| head`
-* does) resolves instead of rejecting: the command already produced its output
-* and must not be reported as failed.
-*/
-async function flushStdout(stream = process.stdout) {
-	await new Promise((resolve) => {
-		stream.write(EMPTY_CHUNK, () => resolve());
-	});
-}
-//#endregion
 //#region src/bin/workflowCommands/listWorkflows.ts
 const DEFAULT_PAGE$1 = 1;
 const DEFAULT_PAGE_SIZE$1 = 20;