@adcp/sdk 16.1.0 → 16.3.0

package/dist/lib/testing/storyboard/runner.d.ts

@@ -5,6 +5,7 @@
  * - runStoryboard(): run all phases/steps sequentially
  * - runStoryboardStep(): run a single step (stateless, LLM-friendly)
  */
+import { PreparedStoryboardFixtures } from './prepared-fixtures';
 import type { RequiresCapabilityPredicate, Storyboard, StoryboardStep, StoryboardContext, StoryboardRunOptions, StoryboardResult, StoryboardPhaseResult, StoryboardStepResult, StoryboardStepPreview, StrictValidationSummary, SchemaValidationError } from './types';
 import type { TestStepResult } from '../types';
 export declare function applyStoryboardVersionOptions(storyboard: Storyboard, options: StoryboardRunOptions): StoryboardRunOptions;
@@ -161,6 +162,29 @@ export declare function signingCoverageUnverified(steps: readonly SigningCoverag
  * called from `runStoryboard` when discovery throws.
  */
 export declare function buildDiscoveryFailedResult(agentUrls: string[], storyboard: Storyboard, discoveryStep: TestStepResult): StoryboardResult;
+/**
+ * Resolve a storyboard's fixture graph once and return reusable, immutable
+ * prepared state.
+ *
+ * This is the public form of what `executeStoryboardPass` already does
+ * internally, promoted so the standalone step runner and hosted step routes
+ * stop falling back to literal authored handles. The returned state carries
+ * the pinned seller identities, the declaration-local captures from the
+ * SAME selected graph, the retained collection witnesses, the resolution
+ * evidence, any coverage gaps, and the terminal preparation disposition.
+ *
+ * The state is deliberately process-local: its trust is a live object
+ * identity, and its credential fingerprint is keyed by a per-process random
+ * HMAC key. It will not survive serialization, and it is not meant to — a
+ * frozen JSON snapshot carries no evidence that its grant is still live.
+ * Hosted multi-process reuse belongs behind an authenticated reference
+ * lookup with the authorizer hook. See `docs/guides/COLLECTION-FIXTURE-FOUNDATION.md`.
+ *
+ * A failed or unsatisfied preparation is returned, not thrown: the terminal
+ * disposition is part of the evidence and must be carried forward verbatim
+ * so a retry cannot hide it behind a freshly discovered alternative.
+ */
+export declare function prepareStoryboardFixtures(agentUrl: string | string[], storyboard: Storyboard, options?: StoryboardRunOptions): Promise<PreparedStoryboardFixtures>;
 /**
  * Walk every response_schema validation and aggregate the strict/lenient
  * delta. Always returns a summary; `observable: false` signals "run had