tina4-nodejs 3.13.119 → 3.13.121

package/types/cli/src/commands/generate.d.ts

@@ -23,6 +23,17 @@ export interface ResolutionInput {
     name: string;
     fields: string | null;
 }
+/**
+ * One `// tina4:edit …` marker found in a written (or would-be-written)
+ * template file. `file` is repo-relative POSIX (matches the rest of the
+ * envelope's paths); `line` is 1-based; `label` is the short imperative label
+ * that followed the marker on the same line.
+ */
+export interface EditHint {
+    file: string;
+    line: number;
+    label: string;
+}
 export interface ResolutionBody {
     class_name?: string;
     table_name?: string;
@@ -30,6 +41,8 @@ export interface ResolutionBody {
     migration_path?: string;
     routes?: string[];
     test_paths?: string[];
+    edit_hints?: EditHint[];
+    next?: string[];
     transformations: ResolutionTransformation[];
 }
 export interface ResolutionEnvelope {
@@ -45,8 +58,15 @@ export interface ResolutionEnvelope {
  * `resolution_contract.envelope` so the tina4 client (or any consumer) can
  * discover the exact contract this framework speaks. Bump when a breaking
  * key rename / removal lands; keep unchanged when new OPTIONAL keys are added.
+ *
+ * `generate_v1_1` (ADR-0063, 3.13.120) is a PURELY ADDITIVE superset of
+ * `generate_v1`: every v1 field is preserved, and two new optional arrays
+ * appear — `resolution.edit_hints[]` (one entry per `// tina4:edit` marker
+ * baked into a template) and `resolution.next[]` (curated per-verb actionable
+ * next steps). `resolution.test_paths[]` was already in v1; v1.1 surfaces it
+ * in the human stderr block too.
  */
-export declare const RESOLUTION_ENVELOPE_VERSION = "generate_v1";
+export declare const RESOLUTION_ENVELOPE_VERSION = "generate_v1_1";
 /** Read-only snapshot of the current resolution — exported for tests that
  * want to inspect it in-process (the CLI itself uses only the envelope). */
 export declare function currentResolution(): ResolutionEnvelope;
@@ -95,3 +115,19 @@ export interface GeneratorSpec {
 }
 export declare const GENERATORS: Record<string, GeneratorSpec>;
 export declare function generate(what: string, name: string, extraArgs?: string[]): Promise<void>;
+/**
+ * Programmatic entry point for in-process consumers (MCP tools, tests, hosted
+ * agents) — does everything `generate()` does EXCEPT print.
+ *
+ * Reset the resolution → dispatch to the requested generator → populate `next[]`
+ * → return the envelope. Files still land on disk (unless `--dry-run` is passed
+ * in `extraArgs`); only the human "Created …" per-file log and the
+ * `printResolution()` output are suppressed (via `jsonMode: true`, the same
+ * suppression `--json` uses on the CLI).
+ *
+ * Used by the MCP `migration_create` tool (packages/core/src/mcp.ts) so the
+ * ADR-0063 `generate_v1_1` envelope drives every surface (CLI, MCP, tests)
+ * without a subprocess round-trip.
+ */
+export declare function generateProgrammatic(what: string, name: string, extraArgs?: string[]): Promise<ResolutionEnvelope>;
+export declare function generateMigration(name: string, flags: Record<string, string | boolean>, fieldsOverride?: Array<[string, string]>, tableOverride?: string, emitTest?: boolean): void;

package/types/cli/src/commands/migrateCreate.d.ts

@@ -1 +1 @@
-export declare function createMigration(description?: string): Promise<void>;
+export declare function createMigration(args?: string[]): Promise<void>;