@plaintake/scenario 1.14.0 → 1.17.0

package/dist/index.js

@@ -1036,7 +1036,14 @@ var RunCommandResultSchema = z7.object({
   narratedCount: z7.number().int().nonnegative(),
   diagnostics: z7.array(z7.object({ code: z7.string(), cueId: z7.string(), detail: z7.string() })),
   assertions: z7.array(AssertionSchema),
-  outputs: z7.array(ArtifactRefSchema)
+  outputs: z7.array(ArtifactRefSchema),
+  /**
+   * The previous bundle this run replaced, archived as a `.<timestamp>` sibling rather
+   * than deleted. Absent when nothing occupied the output directory — the common first
+   * run — or when `--no-archive` asked for the old replace semantics. Optional and
+   * additive, so every result written before archives existed still parses.
+   */
+  archivedPath: DISPLAY_PATH.optional()
 });
 var CheckAssertionSchema = AssertionSchema.extend({ message: z7.string().optional() });
 var CheckCommandResultSchema = z7.object({
@@ -1045,9 +1052,10 @@ var CheckCommandResultSchema = z7.object({
   status: StatusSchema,
   assertions: z7.array(CheckAssertionSchema),
   /**
-   * Handoff notes only. Cue, chapter, cursor and camera diagnostics are all derived from a
-   * render plan that `check` never builds — fabricating them would report on capabilities
-   * this command cannot see.
+   * Handoff notes, plus a `speech.close` note when closing the narrator failed after
+   * capture. Cue, chapter, cursor and camera diagnostics are all derived from a render plan
+   * that `check` never builds — fabricating them would report on capabilities this command
+   * cannot see.
    */
   diagnostics: z7.array(z7.object({ code: z7.string(), cueId: z7.string(), detail: z7.string() }))
 });
@@ -1082,6 +1090,17 @@ var DiffCommandResultSchema = z7.object({
   identical: z7.boolean(),
   differences: z7.array(z7.object({ category: DifferenceCategorySchema, detail: z7.string() }))
 });
+var CompareCommandResultSchema = z7.object({
+  ...envelope("compare"),
+  bundleA: DISPLAY_PATH,
+  bundleB: DISPLAY_PATH,
+  checks: z7.array(z7.object({ name: z7.string(), ok: z7.boolean(), detail: z7.string() }))
+});
+var InitResultSchema = z7.object({
+  ...envelope("init"),
+  files: z7.array(DISPLAY_PATH),
+  validates: z7.boolean()
+});
 var PruneCandidateSchema = z7.object({
   path: DISPLAY_PATH,
   bytes: z7.number().int().nonnegative(),

package/dist/schema/results.d.ts

@@ -47,6 +47,7 @@ export declare const RunCommandResultSchema: z.ZodObject<{
         sha256: z.ZodString;
         bytes: z.ZodNumber;
     }, z.core.$strip>>;
+    archivedPath: z.ZodOptional<z.ZodString>;
     schema: z.ZodLiteral<"agent-demo.result/v1">;
     kind: z.ZodLiteral<"run">;
     ok: z.ZodBoolean;
@@ -257,6 +258,49 @@ export declare const DiffCommandResultSchema: z.ZodObject<{
     ok: z.ZodBoolean;
     problems: z.ZodArray<z.ZodString>;
 }, z.core.$strip>;
+/**
+ * `compare <bundleA> <bundleB>`'s result. Two `DISPLAY_PATH`s like `diff`, because it reads two
+ * bundles — but where `diff` is a *semantic* comparison of two different recordings and drift is
+ * never a fault, `compare` is a **render-determinism gate**: it re-hashes and re-decodes two
+ * renders that should be byte-for-byte identical, so a difference is a regression. `ok` therefore
+ * IS the verdict — the renders match — and a failing check names itself in `problems`, exactly the
+ * stance `verify` takes on a hash mismatch (unlike `diff`, whose `ok` is deliberately untied from
+ * its verdict). Exit 6, reusing `verify`'s and `diff`'s code, on drift or on a bundle whose
+ * rendered output could not be read back out. `checks` mirrors `compareRenders`'s own report so a
+ * caller sees every check, not only the failing ones. CLI-only: the MCP tool list is frozen at four.
+ */
+export declare const CompareCommandResultSchema: z.ZodObject<{
+    bundleA: z.ZodString;
+    bundleB: z.ZodString;
+    checks: z.ZodArray<z.ZodObject<{
+        name: z.ZodString;
+        ok: z.ZodBoolean;
+        detail: z.ZodString;
+    }, z.core.$strip>>;
+    schema: z.ZodLiteral<"agent-demo.result/v1">;
+    kind: z.ZodLiteral<"compare">;
+    ok: z.ZodBoolean;
+    problems: z.ZodArray<z.ZodString>;
+}, z.core.$strip>;
+/**
+ * `init [<name>]`'s result. The scaffold is a starting point that must validate by
+ * construction — its template pins the deterministic video contract and uses no clock,
+ * randomness, network or absolute paths — but `validates` is still reported separately from
+ * `ok`, on the same pattern as `import`'s field of the same name, because the two answer
+ * different questions: `ok` says files were written; `validates` says the generated scenario
+ * passed the same `loadScenario` validate runs. A `false` there means the template drifted
+ * from the contract, not that the command failed. `files` names everything written, relative
+ * to the working directory: the scenario plus, only when none existed, a starter
+ * `plaintake.config.json` — an existing config is never touched, so it never appears here.
+ */
+export declare const InitResultSchema: z.ZodObject<{
+    files: z.ZodArray<z.ZodString>;
+    validates: z.ZodBoolean;
+    schema: z.ZodLiteral<"agent-demo.result/v1">;
+    kind: z.ZodLiteral<"init">;
+    ok: z.ZodBoolean;
+    problems: z.ZodArray<z.ZodString>;
+}, z.core.$strip>;
 /**
  * `prune`'s result. Selection never touches disk by itself — `dryRun: true` (the default,
  * absent `--yes`) means `candidates` names what *would* be removed and every one of them is
@@ -475,13 +519,15 @@ export type RenderCommandResult = z.infer<typeof RenderCommandResultSchema>;
 export type VerificationReport = z.infer<typeof VerificationReportSchema>;
 export type WarmCommandResult = z.infer<typeof WarmCommandResultSchema>;
 export type DiffCommandResult = z.infer<typeof DiffCommandResultSchema>;
+export type CompareCommandResult = z.infer<typeof CompareCommandResultSchema>;
+export type InitResult = z.infer<typeof InitResultSchema>;
 export type PruneCommandResult = z.infer<typeof PruneCommandResultSchema>;
 export type ImportCommandResult = z.infer<typeof ImportCommandResultSchema>;
 export type InspectResult = z.infer<typeof InspectResultSchema>;
 export type DoctorResult = z.infer<typeof DoctorResultSchema>;
 export type ActivateResult = z.infer<typeof ActivateResultSchema>;
 export type LicenceResult = z.infer<typeof LicenceResultSchema>;
-export type DemoResult = ValidationResult | RunCommandResult | CheckCommandResult | RenderCommandResult | VerificationReport | WarmCommandResult | DiffCommandResult | PruneCommandResult | ImportCommandResult | InspectResult | DoctorResult | ActivateResult | LicenceResult;
+export type DemoResult = ValidationResult | RunCommandResult | CheckCommandResult | RenderCommandResult | VerificationReport | WarmCommandResult | DiffCommandResult | CompareCommandResult | InitResult | PruneCommandResult | ImportCommandResult | InspectResult | DoctorResult | ActivateResult | LicenceResult;
 /**
  * Renders a filesystem location for display in a result, relative to `root` when it
  * lies inside it.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@plaintake/scenario",
-  "version": "1.14.0",
+  "version": "1.17.0",
   "description": "Authoring SDK for PlainTake demo scenarios: defineDemo and the scenario DSL types. Install for editor autocomplete; the PlainTake binary ships a runtime fallback.",
   "license": "MIT",
   "type": "module",