@storystick/cli 0.0.0-stage → 0.2.0-rc.1

package/dist/cli.d.ts

@@ -0,0 +1,68 @@
+#!/usr/bin/env node
+/**
+ * Storystick CLI
+ *
+ * Phase 0: `storystick generate`
+ * Reads .story files, resolves composition, generates TypeScript types.
+ *
+ * Future: `storystick dev` will add file watching + incremental regeneration.
+ * The pipeline function below is designed to be callable from both.
+ */
+import type { GeneratedFile, Diagnostic, ResolvedStory } from '@storystick/core';
+import { type GenerationFaultPoint } from './generated-transaction.js';
+import { type ResolveResult } from './resolve.js';
+export { runResolve } from './resolve.js';
+export interface PipelineOptions {
+    /** Project root directory */
+    rootDir: string;
+    /** Directories to scan for .story files (relative to rootDir) */
+    storyDirs: string[];
+    /** Output directory for generated types (relative to rootDir) */
+    outputDir: string;
+    /** Path to core stories */
+    corePath: string;
+    /** Compare generated bytes without mutating the filesystem. */
+    check?: boolean;
+    /** @internal Test-only crash seam. */
+    generationFaultAt?: GenerationFaultPoint;
+}
+export interface PipelineResult {
+    /** Number of stories resolved */
+    storyCount: number;
+    /** All diagnostics */
+    diagnostics: Diagnostic[];
+    /** Whether the pipeline succeeded (no errors) */
+    success: boolean;
+    /** Generated file paths */
+    generatedFiles: string[];
+    /**
+     * Resolved stories, indexed by ID. Exposed so callers like `sync` can
+     * pipe straight into `serializeSchema` without re-resolving (ADR-072
+     * lock T9 — sync was double-resolving pre-ADR-072).
+     */
+    stories: Map<string, ResolvedStory>;
+}
+export interface PreparedPipelineResult extends ResolveResult {
+    /** Generated bytes held in memory until the caller commits them. */
+    generated: readonly GeneratedFile[];
+}
+/**
+ * Run the full pipeline: discover → parse → resolve → generate → write.
+ *
+ * ADR-072 §A1 (lock T3 / L7): writes are gated on `resolved.success`. A
+ * failed resolve no longer writes a partial / stale `dist/` to disk; init
+ * and link pick up the gap via `result.success === false` and surface
+ * "run manually" hints instead of silent half-bootstrapped projects.
+ */
+export declare function runPipeline(options: PipelineOptions): Promise<PipelineResult>;
+/**
+ * Resolve and generate entirely in memory. `init` and `sync` use this seam to
+ * prove the local project is viable before either a remote effect or a local
+ * generation pointer is published.
+ */
+export declare function preparePipeline(options: {
+    rootDir: string;
+    storyDirs: string[];
+    corePath: string;
+}): Promise<PreparedPipelineResult>;
+export declare function findCorePath(rootDir: string): string;