@greatwait/contracts 0.1.0-alpha.2 → 0.1.0-alpha.3

package/dist/authority.d.ts

@@ -215,3 +215,60 @@ export declare const SESSION_AUTHORITY_HEADERS: {
     readonly environment: "Greatwait-Environment";
     readonly project: "Greatwait-Project";
 };
+/**
+ * The authority a presented credential carries, answered back to its holder.
+ *
+ * **Why this exists at all.** The authority tuple is fixed at issue for a key
+ * and at consent for a grant — and until W10-01 nothing published it. A holder
+ * could act, and could not ask what it was acting *on*. The gap is invisible
+ * to a browser, which resolves its own project from a session it can see, and
+ * invisible to a documentation page, which tells a reader to substitute values
+ * they already know. It is not invisible to a command-line client: after
+ * `login` it holds a working token and cannot tell the person in front of it
+ * which project it is in, or whether the schedule they are about to create is
+ * a `test` one or a `live` one. Both were observable only by listing something
+ * the project already owned, which a new project does not have.
+ *
+ * **No organization, following every other `/v1` response.** Tenancy above the
+ * project is not a name this surface publishes, and a caller that cannot name
+ * an organization anywhere has no use for one here.
+ *
+ * **`scopes` is what was granted, not what was asked for and not what it
+ * implies.** A grant is capped by the consenting member's role and a key by
+ * what the issuer chose, so this is narrower than any request; it is also the
+ * *raw* list rather than `effectiveScopes`, which expands a write into its
+ * read. Publishing the expansion would make this answer disagree with the
+ * credential's own row in `credentials.list` and with what the consent screen
+ * showed the member — three places, two answers — and a caller that needs to
+ * know whether a scope is implied can apply the same published expansion the
+ * service does.
+ */
+export declare const credentialContextSchema: z.ZodObject<{
+    environmentKind: z.ZodEnum<{
+        test: "test";
+        live: "live";
+    }>;
+    principal: z.ZodEnum<{
+        "api-credential": "api-credential";
+        oauth: "oauth";
+    }>;
+    project: z.ZodString;
+    scopes: z.ZodArray<z.ZodEnum<{
+        "credentials:administer": "credentials:administer";
+        "credentials:read": "credentials:read";
+        "credentials:write": "credentials:write";
+        "endpoints:read": "endpoints:read";
+        "endpoints:write": "endpoints:write";
+        "forecast:read": "forecast:read";
+        "grants:read": "grants:read";
+        "grants:write": "grants:write";
+        "occurrences:read": "occurrences:read";
+        "occurrences:redeliver": "occurrences:redeliver";
+        "projects:read": "projects:read";
+        "projects:write": "projects:write";
+        "schedules:read": "schedules:read";
+        "schedules:write": "schedules:write";
+        "usage:read": "usage:read";
+    }>>;
+}, z.core.$strip>;
+export type CredentialContext = z.infer<typeof credentialContextSchema>;

package/dist/authority.js

@@ -259,3 +259,38 @@ export const SESSION_AUTHORITY_HEADERS = {
     environment: "Greatwait-Environment",
     project: "Greatwait-Project",
 };
+/**
+ * The authority a presented credential carries, answered back to its holder.
+ *
+ * **Why this exists at all.** The authority tuple is fixed at issue for a key
+ * and at consent for a grant — and until W10-01 nothing published it. A holder
+ * could act, and could not ask what it was acting *on*. The gap is invisible
+ * to a browser, which resolves its own project from a session it can see, and
+ * invisible to a documentation page, which tells a reader to substitute values
+ * they already know. It is not invisible to a command-line client: after
+ * `login` it holds a working token and cannot tell the person in front of it
+ * which project it is in, or whether the schedule they are about to create is
+ * a `test` one or a `live` one. Both were observable only by listing something
+ * the project already owned, which a new project does not have.
+ *
+ * **No organization, following every other `/v1` response.** Tenancy above the
+ * project is not a name this surface publishes, and a caller that cannot name
+ * an organization anywhere has no use for one here.
+ *
+ * **`scopes` is what was granted, not what was asked for and not what it
+ * implies.** A grant is capped by the consenting member's role and a key by
+ * what the issuer chose, so this is narrower than any request; it is also the
+ * *raw* list rather than `effectiveScopes`, which expands a write into its
+ * read. Publishing the expansion would make this answer disagree with the
+ * credential's own row in `credentials.list` and with what the consent screen
+ * showed the member — three places, two answers — and a caller that needs to
+ * know whether a scope is implied can apply the same published expansion the
+ * service does.
+ */
+export const credentialContextSchema = z.object({
+    environmentKind: environmentKindSchema,
+    /** How this credential authenticated. Never `session`: see the operation. */
+    principal: z.enum(["api-credential", "oauth"]),
+    project: projectIdSchema,
+    scopes: z.array(scopeSchema).min(1),
+});

package/dist/first-value-journey.d.ts

@@ -303,3 +303,159 @@ export declare function resolveJourneyReferences<T>(value: T, resolve: (name: st
  * value the reader supplies from one an earlier call handed them.
  */
 export declare function journeyCapturedVariables(): readonly string[];
+/**
+ * The website's rendering of the same journey.
+ *
+ * **Declared here rather than in the dashboard, because it is the *binding*
+ * between two things that already exist and neither of them may own it.** The
+ * dashboard has a four-step onboarding flow derived from what a member's
+ * project contains; this file has a nine-step sequence derived from the
+ * operation registry. Left unrelated they answered the same question with
+ * different words and different examples, and the website's answer was the one
+ * that went stale: its "Schedule a one-shot" step rendered the registry's
+ * `schedules.create` example, which is a **recurring cron** — a live dashboard
+ * action showing a reader the one thing the step promises it is not.
+ *
+ * So a website step names journey steps, and never a body, a title or a
+ * sentence of its own. What the browser prints is what the curl page prints,
+ * because it is the same declaration rendered twice.
+ *
+ * **`verified` maps to nothing, deliberately.** The ownership challenge is
+ * optional and off by default since W4-09, so the journey does not perform it;
+ * a deployment that turns it on gets the step from
+ * `endpoints.verify`'s own snippet. Mapping it to a journey step that does not
+ * exist would be worse than mapping it to none.
+ */
+export declare const WEBSITE_JOURNEY_STEP_KEYS: Readonly<Record<string, readonly string[]>>;
+/** The journey steps a website step renders, resolved against the sequence. */
+export declare function websiteJourneySteps(step: string): readonly JourneyStep[];
+/**
+ * The bounded wait the website inherits, rather than one it chose.
+ *
+ * W9-01's fourth criterion asks the browser to bound outcome polling and to
+ * leave a recovery action on timeout. The journey already declares both numbers
+ * on `await-occurrence`, and the curl and JavaScript quickstarts already wait
+ * exactly that long — so a browser that picked its own interval would be a
+ * third answer to a question with one published answer, and the reader who
+ * followed both would be told two different things about how long to wait.
+ */
+export declare function journeyPoll(key: string): JourneyPoll;
+/**
+ * What the reader has to bring, in the words the quickstarts already use.
+ *
+ * The website used to write its own: "anything that can take an HTTP POST. A
+ * webhook playground is fine for a first look." That sentence steered a new
+ * customer to paste their first callback into a third-party inspection service,
+ * which is the thing this project's receiver decision exists to refuse, and it
+ * disagreed with the curl page on the same screenful of product.
+ *
+ * The operator's decision on W9-01 was that the *invitation* says none of this
+ * — a prerequisite stated before somebody has any context is noise they cannot
+ * act on. It is said here instead, at the step that needs it.
+ */
+export declare function journeyPrerequisite(id: string): JourneyPrerequisite;
+/**
+ * How long a website step took, as a bucket and never as a number.
+ *
+ * Coarser than `MCP_ACTIVATION_DURATIONS`, because these measure different
+ * things: a connection test is a handshake and finishes in seconds, and a
+ * person adding a destination and scheduling a callback is doing minutes of
+ * work. Reusing the millisecond buckets would put every website step in
+ * `over_30s` and record nothing.
+ */
+export declare const JOURNEY_ACTIVATION_DURATIONS: readonly ["under_1m", "under_5m", "under_15m", "over_15m"];
+export type JourneyActivationDuration = (typeof JOURNEY_ACTIVATION_DURATIONS)[number];
+export declare function journeyActivationDuration(elapsedMs: number): JourneyActivationDuration;
+/** Every way a website step can end, drawn from a closed list. */
+export declare const JOURNEY_ACTIVATION_OUTCOMES: readonly ["reached", "refused", "timed_out", "failed"];
+export type JourneyActivationOutcome = (typeof JOURNEY_ACTIVATION_OUTCOMES)[number];
+/** The website steps an activation fact may name. */
+export declare const WEBSITE_JOURNEY_STEPS: readonly ["destination", "verified", "scheduled", "delivered"];
+/**
+ * What is recorded when somebody moves through the website journey, and the
+ * only thing that is.
+ *
+ * **Modelled on `mcpActivationEventSchema` down to the `strictObject`, and for
+ * the same reason.** Every field is drawn from a closed set: there is no
+ * free-text field, no identifier, no address, no URL and no measurement finer
+ * than a bucket, so an event of this shape cannot carry an account, an
+ * organization, a project, an invitation link, a token, a destination or a
+ * payload however carelessly it is constructed.
+ *
+ * Strict rather than merely typed. An ordinary object schema *strips* what it
+ * does not know, so an emitter that added `project` would look like it was
+ * recording one while the field silently vanished — safe and dishonest at once.
+ * The MCP schema learned that from a test and this one inherits the lesson
+ * rather than rediscovering it.
+ */
+export declare const websiteActivationEventSchema: z.ZodObject<{
+    duration: z.ZodEnum<{
+        under_1m: "under_1m";
+        under_5m: "under_5m";
+        under_15m: "under_15m";
+        over_15m: "over_15m";
+    }>;
+    outcome: z.ZodEnum<{
+        failed: "failed";
+        timed_out: "timed_out";
+        refused: "refused";
+        reached: "reached";
+    }>;
+    step: z.ZodEnum<{
+        verified: "verified";
+        delivered: "delivered";
+        destination: "destination";
+        scheduled: "scheduled";
+    }>;
+    type: z.ZodLiteral<"website.journey_step">;
+}, z.core.$strict>;
+export type WebsiteActivationEvent = z.infer<typeof websiteActivationEventSchema>;
+/**
+ * Parses an activation fact before it leaves the browser.
+ *
+ * The parse is the control, exactly as it is on the MCP side: a caller hands
+ * this an object and the schema refuses anything the closed sets do not admit,
+ * so the mistake surfaces where it was made rather than as a field that quietly
+ * disappeared.
+ */
+export declare function parseWebsiteActivationEvent(value: unknown): WebsiteActivationEvent;
+/**
+ * A path parameter's name, as the journey's variables spell it.
+ *
+ * **Published because a machine consumer cannot run the journey without it.**
+ * A step names its operation and the variables it needs — `read-schedule` says
+ * `/v1/schedules/{scheduleId}` and, separately, `GREATWAIT_SCHEDULEID` — and
+ * the rule joining the two lived in `scripts/first-value-projection.ts`, which
+ * is not published. A documentation page never notices: it renders both halves
+ * as text and a human joins them by eye. A command-line client has to *fill*
+ * the parameter, and had to re-derive the convention by guessing at it.
+ *
+ * The transformation is deliberately total and lossy in the safe direction:
+ * every non-alphanumeric character becomes `_`, so a parameter that differs
+ * from another only in punctuation would collide. `journeyPathVariables` is
+ * where that would surface, and `first-value-journey.test.ts` holds the
+ * journey's own parameters to distinct names.
+ */
+export declare function journeyVariableName(parameter: string): string;
+/** Every `{parameter}` in a path, in the order the path names them. */
+export declare function pathParameterNames(path: string): readonly string[];
+/**
+ * The variables a step's path parameters are filled from, in path order.
+ *
+ * Order is the contract: a client filling positional arguments — which is what
+ * the generated client takes — needs them in the order the path names them,
+ * and `attempts.list` has two.
+ */
+export declare function journeyPathVariables(step: JourneyStep): readonly string[];
+/**
+ * Everything a step must be given before it can be performed.
+ *
+ * **Published because it is a join, and a join is where a second consumer
+ * invents its own copy.** A step's inputs come from three places — the
+ * operation's path parameters, the `{{…}}` references in its body, query and
+ * headers — and stitching them is the kind of two-line rule every consumer gets
+ * *nearly* right. The machine-readable artifact's own `variables` field is this
+ * function, so a client reading the artifact and a client reading this module
+ * cannot disagree about what a step needs.
+ */
+export declare function journeyStepVariables(step: JourneyStep): readonly string[];

package/dist/first-value-journey.js

@@ -1,4 +1,5 @@
 import { z } from "zod";
+import { findOperation } from "./operations.js";
 /**
  * One thing that can go wrong at a step, and the next move.
  *
@@ -464,3 +465,215 @@ export function resolveJourneyReferences(value, resolve) {
 export function journeyCapturedVariables() {
     return FIRST_VALUE_STEPS.flatMap((step) => (step.capture ?? []).map((capture) => capture.variable));
 }
+/**
+ * The website's rendering of the same journey.
+ *
+ * **Declared here rather than in the dashboard, because it is the *binding*
+ * between two things that already exist and neither of them may own it.** The
+ * dashboard has a four-step onboarding flow derived from what a member's
+ * project contains; this file has a nine-step sequence derived from the
+ * operation registry. Left unrelated they answered the same question with
+ * different words and different examples, and the website's answer was the one
+ * that went stale: its "Schedule a one-shot" step rendered the registry's
+ * `schedules.create` example, which is a **recurring cron** — a live dashboard
+ * action showing a reader the one thing the step promises it is not.
+ *
+ * So a website step names journey steps, and never a body, a title or a
+ * sentence of its own. What the browser prints is what the curl page prints,
+ * because it is the same declaration rendered twice.
+ *
+ * **`verified` maps to nothing, deliberately.** The ownership challenge is
+ * optional and off by default since W4-09, so the journey does not perform it;
+ * a deployment that turns it on gets the step from
+ * `endpoints.verify`'s own snippet. Mapping it to a journey step that does not
+ * exist would be worse than mapping it to none.
+ */
+export const WEBSITE_JOURNEY_STEP_KEYS = {
+    delivered: ["await-occurrence", "read-attempt"],
+    destination: ["create-destination"],
+    scheduled: ["create-one-shot"],
+    verified: [],
+};
+/** The journey steps a website step renders, resolved against the sequence. */
+export function websiteJourneySteps(step) {
+    const keys = WEBSITE_JOURNEY_STEP_KEYS[step] ?? [];
+    return keys.map((key) => {
+        const found = FIRST_VALUE_STEPS.find((entry) => entry.key === key);
+        if (found === undefined) {
+            // Not reachable from the constant above, and that is exactly why it
+            // throws: the map is hand-written and the sequence is not, so a step
+            // renamed in `FIRST_VALUE_STEPS` must fail loudly here rather than
+            // silently render one fewer call than the page promises.
+            throw new Error(`website journey names unknown step ${key}`);
+        }
+        return found;
+    });
+}
+/**
+ * The bounded wait the website inherits, rather than one it chose.
+ *
+ * W9-01's fourth criterion asks the browser to bound outcome polling and to
+ * leave a recovery action on timeout. The journey already declares both numbers
+ * on `await-occurrence`, and the curl and JavaScript quickstarts already wait
+ * exactly that long — so a browser that picked its own interval would be a
+ * third answer to a question with one published answer, and the reader who
+ * followed both would be told two different things about how long to wait.
+ */
+export function journeyPoll(key) {
+    const step = FIRST_VALUE_STEPS.find((entry) => entry.key === key);
+    if (step?.poll === undefined) {
+        throw new Error(`journey step ${key} declares no bounded wait`);
+    }
+    return step.poll;
+}
+/**
+ * What the reader has to bring, in the words the quickstarts already use.
+ *
+ * The website used to write its own: "anything that can take an HTTP POST. A
+ * webhook playground is fine for a first look." That sentence steered a new
+ * customer to paste their first callback into a third-party inspection service,
+ * which is the thing this project's receiver decision exists to refuse, and it
+ * disagreed with the curl page on the same screenful of product.
+ *
+ * The operator's decision on W9-01 was that the *invitation* says none of this
+ * — a prerequisite stated before somebody has any context is noise they cannot
+ * act on. It is said here instead, at the step that needs it.
+ */
+export function journeyPrerequisite(id) {
+    const found = FIRST_VALUE_PREREQUISITES.find((entry) => entry.id === id);
+    if (found === undefined) {
+        throw new Error(`journey declares no prerequisite ${id}`);
+    }
+    return found;
+}
+/**
+ * How long a website step took, as a bucket and never as a number.
+ *
+ * Coarser than `MCP_ACTIVATION_DURATIONS`, because these measure different
+ * things: a connection test is a handshake and finishes in seconds, and a
+ * person adding a destination and scheduling a callback is doing minutes of
+ * work. Reusing the millisecond buckets would put every website step in
+ * `over_30s` and record nothing.
+ */
+export const JOURNEY_ACTIVATION_DURATIONS = [
+    "under_1m",
+    "under_5m",
+    "under_15m",
+    "over_15m",
+];
+export function journeyActivationDuration(elapsedMs) {
+    if (elapsedMs < 60_000)
+        return "under_1m";
+    if (elapsedMs < 300_000)
+        return "under_5m";
+    if (elapsedMs < 900_000)
+        return "under_15m";
+    return "over_15m";
+}
+/** Every way a website step can end, drawn from a closed list. */
+export const JOURNEY_ACTIVATION_OUTCOMES = [
+    "reached",
+    "refused",
+    "timed_out",
+    "failed",
+];
+/** The website steps an activation fact may name. */
+export const WEBSITE_JOURNEY_STEPS = [
+    "destination",
+    "verified",
+    "scheduled",
+    "delivered",
+];
+/**
+ * What is recorded when somebody moves through the website journey, and the
+ * only thing that is.
+ *
+ * **Modelled on `mcpActivationEventSchema` down to the `strictObject`, and for
+ * the same reason.** Every field is drawn from a closed set: there is no
+ * free-text field, no identifier, no address, no URL and no measurement finer
+ * than a bucket, so an event of this shape cannot carry an account, an
+ * organization, a project, an invitation link, a token, a destination or a
+ * payload however carelessly it is constructed.
+ *
+ * Strict rather than merely typed. An ordinary object schema *strips* what it
+ * does not know, so an emitter that added `project` would look like it was
+ * recording one while the field silently vanished — safe and dishonest at once.
+ * The MCP schema learned that from a test and this one inherits the lesson
+ * rather than rediscovering it.
+ */
+export const websiteActivationEventSchema = z.strictObject({
+    duration: z.enum(JOURNEY_ACTIVATION_DURATIONS),
+    outcome: z.enum(JOURNEY_ACTIVATION_OUTCOMES),
+    step: z.enum(WEBSITE_JOURNEY_STEPS),
+    type: z.literal("website.journey_step"),
+});
+/**
+ * Parses an activation fact before it leaves the browser.
+ *
+ * The parse is the control, exactly as it is on the MCP side: a caller hands
+ * this an object and the schema refuses anything the closed sets do not admit,
+ * so the mistake surfaces where it was made rather than as a field that quietly
+ * disappeared.
+ */
+export function parseWebsiteActivationEvent(value) {
+    return websiteActivationEventSchema.parse(value);
+}
+/**
+ * A path parameter's name, as the journey's variables spell it.
+ *
+ * **Published because a machine consumer cannot run the journey without it.**
+ * A step names its operation and the variables it needs — `read-schedule` says
+ * `/v1/schedules/{scheduleId}` and, separately, `GREATWAIT_SCHEDULEID` — and
+ * the rule joining the two lived in `scripts/first-value-projection.ts`, which
+ * is not published. A documentation page never notices: it renders both halves
+ * as text and a human joins them by eye. A command-line client has to *fill*
+ * the parameter, and had to re-derive the convention by guessing at it.
+ *
+ * The transformation is deliberately total and lossy in the safe direction:
+ * every non-alphanumeric character becomes `_`, so a parameter that differs
+ * from another only in punctuation would collide. `journeyPathVariables` is
+ * where that would surface, and `first-value-journey.test.ts` holds the
+ * journey's own parameters to distinct names.
+ */
+export function journeyVariableName(parameter) {
+    return `GREATWAIT_${parameter.toUpperCase().replace(/[^A-Z0-9]/gu, "_")}`;
+}
+/** Every `{parameter}` in a path, in the order the path names them. */
+export function pathParameterNames(path) {
+    return [...path.matchAll(/\{([^}]+)\}/gu)].map((match) => match[1]);
+}
+/**
+ * The variables a step's path parameters are filled from, in path order.
+ *
+ * Order is the contract: a client filling positional arguments — which is what
+ * the generated client takes — needs them in the order the path names them,
+ * and `attempts.list` has two.
+ */
+export function journeyPathVariables(step) {
+    const operation = findOperation(step.operationId);
+    if (operation === undefined) {
+        throw new Error(`the first-value journey names ${step.operationId}, which is not an operation`);
+    }
+    return pathParameterNames(operation.path).map(journeyVariableName);
+}
+/**
+ * Everything a step must be given before it can be performed.
+ *
+ * **Published because it is a join, and a join is where a second consumer
+ * invents its own copy.** A step's inputs come from three places — the
+ * operation's path parameters, the `{{…}}` references in its body, query and
+ * headers — and stitching them is the kind of two-line rule every consumer gets
+ * *nearly* right. The machine-readable artifact's own `variables` field is this
+ * function, so a client reading the artifact and a client reading this module
+ * cannot disagree about what a step needs.
+ */
+export function journeyStepVariables(step) {
+    return [
+        ...new Set([
+            ...journeyPathVariables(step),
+            ...journeyReferences(step.request),
+            ...journeyReferences(step.query),
+            ...journeyReferences(step.requestHeaders),
+        ]),
+    ];
+}

package/dist/identity.d.ts

@@ -57,8 +57,8 @@ export type ExternalMembershipId = z.infer<typeof externalMembershipIdSchema>;
  */
 export declare const MEMBERSHIP_ROLES: readonly ["admin", "member"];
 export declare const membershipRoleSchema: z.ZodEnum<{
-    admin: "admin";
     member: "member";
+    admin: "admin";
 }>;
 export type MembershipRole = z.infer<typeof membershipRoleSchema>;
 /**
@@ -99,8 +99,8 @@ export declare const membershipSchema: z.ZodObject<{
     id: z.ZodString;
     organization: z.ZodString;
     role: z.ZodEnum<{
-        admin: "admin";
         member: "member";
+        admin: "admin";
     }>;
     status: z.ZodEnum<{
         removed: "removed";
@@ -140,8 +140,8 @@ export declare const membershipChangeSchema: z.ZodObject<{
     id: z.ZodString;
     organization: z.ZodString;
     role: z.ZodEnum<{
-        admin: "admin";
         member: "member";
+        admin: "admin";
     }>;
     status: z.ZodEnum<{
         removed: "removed";
@@ -164,8 +164,8 @@ export declare const sessionMembershipSchema: z.ZodObject<{
     assertedAt: z.ZodNumber;
     organization: z.ZodString;
     role: z.ZodEnum<{
-        admin: "admin";
         member: "member";
+        admin: "admin";
     }>;
     user: z.ZodString;
 }, z.core.$strip>;

package/dist/index.d.ts

@@ -1,6 +1,6 @@
 export { ANY_ID_PATTERN, ID_ALPHABET, ID_PREFIXES, apiCredentialEventIdSchema, apiCredentialIdSchema, attemptIdSchema, authorizationRequestIdSchema, callbackSigningKeyIdSchema, deliveryIdSchema, endpointIdSchema, environmentIdSchema, eventIdSchema, idPattern, idSchema, newId, oauthClientIdSchema, oauthGrantEventIdSchema, oauthGrantIdSchema, occurrenceIdSchema, organizationIdSchema, projectIdSchema, resourceOf, scheduleIdSchema, testSinkDeliveryIdSchema, testSinkIdSchema, type ApiCredentialEventId, type ApiCredentialId, type AttemptId, type AuthorizationRequestId, type CallbackSigningKeyId, type DeliveryId, type EndpointId, type EnvironmentId, type IdResource, type OAuthClientId, type OAuthGrantEventId, type OAuthGrantId, type OccurrenceId, type OrganizationId, type RandomBytes, type ProjectId, type ScheduleId, type TestSinkDeliveryId, type TestSinkId, } from "./identifiers.js";
 export { durationSecondsSchema, timeZoneSchema, timestampSchema, toTimestamp, type DurationSeconds, type TimeZone, type Timestamp, } from "./time.js";
-export { ENVIRONMENT_KINDS_IN_ORDER, PRINCIPAL_KINDS, SCOPES, SESSION_AUTHORITY_HEADERS, authoritySchema, decideAccess, decideEnvironmentIntent, effectiveScopes, problemCodeForRefusal, environmentKindSchema, principalKindSchema, principalSchema, scopeSchema, type AccessDecision, type AccessRefusal, type AccessRequest, type Authority, type EnvironmentIntentDecision, type EnvironmentKind, type Principal, type PrincipalKind, type Scope, } from "./authority.js";
+export { ENVIRONMENT_KINDS_IN_ORDER, PRINCIPAL_KINDS, SCOPES, SESSION_AUTHORITY_HEADERS, authoritySchema, credentialContextSchema, decideAccess, decideEnvironmentIntent, effectiveScopes, problemCodeForRefusal, environmentKindSchema, principalKindSchema, principalSchema, scopeSchema, type AccessDecision, type AccessRefusal, type AccessRequest, type Authority, type CredentialContext, type EnvironmentIntentDecision, type EnvironmentKind, type Principal, type PrincipalKind, type Scope, } from "./authority.js";
 export { PROBLEM_CATEGORIES, PROBLEM_CODES, fieldErrorSchema, isRetryable, problem, problemCategorySchema, problemCodeSchema, problemSchema, type FieldError, type Problem, type ProblemCategory, type ProblemCode, type ProblemOptions, } from "./problems.js";
 export { CONCURRENCY_HEADERS, PAGE_SIZE, canonicalRequest, classifyIdempotency, conditionalRequestHeaderSchema, decodeCursor, encodeCursor, etagSchema, freshnessSchema, projectedFreshnessSchema, fromETag, idempotencyKeySchema, idempotencyReplayResponseHeaderSchema, idempotencyRequestHeaderSchema, idempotencyReceiptSchema, idempotencyScopeSchema, pageRequestSchema, pageSchema, parsePageRequest, replayedResponseHeaderSchema, requiredIdempotencyRequestHeaderSchema, requestFingerprint, toETag, versionResponseHeaderSchema, versionSchema, type Freshness, type ProjectedFreshness, type IdempotencyKey, type IdempotencyOutcome, type IdempotencyReceipt, type IdempotencyScope, type PagePosition, type PageRequest, type PageRequestParse, type Version, } from "./protocol.js";
 export { CALLBACK_CONTENT_TYPE, CALLBACK_DELIVERY_PROTOCOL, CALLBACK_DELIVERY_PROTOCOL_VERSION, CALLBACK_ENVELOPE_VERSION, CALLBACK_ENVELOPE_VERSION_2026_07_01, CALLBACK_ENVELOPE_VERSION_2026_08_08, CALLBACK_ENVELOPE_VERSION_CHANGE, CALLBACK_ENVELOPE_VERSIONS, CALLBACK_HEADERS, SIGNATURE_SCHEME, SIGNATURE_TOLERANCE_SECONDS, callbackDeferredCompletionSchema, callbackDeliveryTestVectors, callbackEnvelopeSchema, callbackEnvelopeTrigger, callbackHeadersSchema, callbackRun, callbackTriggerSchema, classifyOutcome, classifyStatus, formatSignature, extractCanonicalEnvelopeIds, isTimestampFresh, signatureHeaderSchema, serializeCallbackEnvelope, signingInput, trySigningInput, type AttemptOutcome, type CallbackDeferredCompletion, type CallbackDeliveryTestVector, type CallbackEnvelope, type CallbackRun, type CallbackTrigger, type ResponseClass, } from "./signatures.js";
@@ -10,7 +10,7 @@ export { EVENT_TYPES, eventEnvelopeSchema, eventTypeSchema, genericEventSchema,
 export { MEMBERSHIP_ROLES, MEMBERSHIP_STATUSES, externalMembershipIdSchema, externalOrganizationIdSchema, externalUserIdSchema, grantsAccess, leastRole, leastStatus, membershipChangeSchema, membershipRoleSchema, membershipSchema, membershipStatusSchema, organizationTombstoneSchema, sessionMembershipSchema, type ExternalMembershipId, type ExternalOrganizationId, type ExternalUserId, type Membership, type MembershipChange, type MembershipRole, type MembershipStatus, type OrganizationTombstone, type SessionMembership, } from "./identity.js";
 export { CHANGE_KINDS, CHANGE_OPERATIONS, CHANGE_SUBJECTS, CONTRACT_VERSION, assess, changeKindSchema, classifyChange, contractVersionSchema, type ChangeKind, type ChangeOperation, type ChangeSubject, type CompatibilityVerdict, type ContractChange, } from "./compatibility.js";
 export { WORKSPACE_LAYERS, scaffoldProblemSchema, scaffoldVersionSchema, toolDescriptorSchema, toolListSchema, workspaceIdentitySchema, workspaceLayerSchema, workspaceScaffoldSchema, type ScaffoldProblem, type ScaffoldVersion, type ToolDescriptor, type ToolList, type WorkspaceIdentity, type WorkspaceLayer, type WorkspaceScaffold, } from "./workspace.js";
-export { MOCK_BEHAVIORS, MOCK_HEADERS, OPERATIONS, UNIVERSAL_PROBLEMS, AUTHENTICATED_PROBLEMS, findOperation, fixtureListSchema, mockBehaviorSchema, mockScenarioRequestSchema, mockScenarioResponseSchema, operationsFor, problemsFor, requestSchemaFor, responseSchemaFor, successStatusFor, type FixtureList, type McpDisposition, type MockBehavior, type MockScenarioRequest, type MockScenarioResponse, type OperationDefinition, type OperationId, type OperationSurface, } from "./operations.js";
+export { MOCK_BEHAVIORS, MOCK_HEADERS, OPERATIONS, UNIVERSAL_PROBLEMS, AUTHENTICATED_PROBLEMS, SCOPED_PROBLEMS, findOperation, fixtureListSchema, mockBehaviorSchema, mockScenarioRequestSchema, mockScenarioResponseSchema, operationsFor, problemsFor, requestSchemaFor, responseSchemaFor, successStatusFor, type FixtureList, type McpDisposition, type MockBehavior, type MockScenarioRequest, type MockScenarioResponse, type OperationDefinition, type OperationId, type OperationSurface, } from "./operations.js";
 export { PROJECT_LIST_LIMIT, PROJECT_STATUSES, environmentSchema, organizationSchema, projectCreateRequestSchema, projectListSchema, projectNameSchema, projectSchema, projectStatusSchema, projectSummarySchema, provisionedProjectSchema, type Environment, type Organization, type Project, type ProjectCreateRequest, type ProjectList, type ProjectStatus, type ProjectSummary, type ProvisionedProject, } from "./tenancy.js";
 export { ATTEMPT_DURATION_MAX_MS, ATTEMPT_FAILURE_SNIPPET_MAX_LENGTH, ATTEMPT_REMEDIATIONS, ATTEMPT_RESPONSE_HEADER_MAX_LENGTH, ATTEMPT_STATES, CRON_EXPRESSION_MAX_LENGTH, LATENCY_CLASSES, OCCURRENCE_STATES, PARTITION_KEY_MAX_LENGTH, RECURRENCE_REQUEST_FIELDS, SCHEDULE_STATUSES, SCHEDULING_BOUNDS, TERMINAL_OCCURRENCE_STATES, attemptFailureSnippetSchema, attemptResponseHeaderSchema, attemptSchema, attemptDiagnosticSchema, attemptPageSchema, attemptRemediationSchema, attemptStateForResponse, attemptStateSchema, attemptTriggerSchema, attemptViewSchema, cronExpressionSchema, DELIVERY_COMPLETION_MODES, DELIVERY_DURATION_TIERS, DELIVERY_OVERLAP_POLICIES, DEFAULT_DELIVERY_DURATION_SECONDS, DEFAULT_DELIVERY_OVERLAP_POLICY, FREE_DELIVERY_DURATION_SECONDS, isLongRunningDuration, deliveryCompletionModeSchema, deliveryDurationSecondsSchema, deliveryOverlapPolicySchema, type DeliveryCompletionMode, type DeliveryOverlapPolicy, deriveDeliverySettings, deriveLatencyClass, generationSchema, isTerminalOccurrenceState, latencyClassSchema, occurrenceSchema, occurrencePageSchema, occurrenceStateSchema, occurrenceViewSchema, partitionKeySchema, remediationForAttempt, recurrenceSchema, schedulePageSchema, scheduleRequestSchema, scheduleSchema, scheduleStatusSchema, scheduleViewSchema, type Attempt, type AttemptFailureSnippet, type AttemptResponseHeader, type AttemptDiagnostic, type AttemptPage, type AttemptRemediation, type AttemptState, type AttemptTrigger, type AttemptView, type CronExpression, type Generation, type DeliverySettings, type LatencyClass, type Occurrence, type OccurrencePage, type OccurrenceState, type OccurrenceView, type PartitionKey, type Recurrence, type Schedule, type SchedulePage, type ScheduleRequest, type ScheduleStatus, type ScheduleView, } from "./scheduling.js";
 export { portableAttemptRecordSchema, portableEncryptedPayloadRecordSchema, portableOccurrenceRecordSchema, portableReceiptRecordSchema, portableScheduleRecordSchema, portableSchedulingRecordSetSchema, type PortableAttemptRecord, type PortableEncryptedPayloadRecord, type PortableOccurrenceRecord, type PortableReceiptRecord, type PortableScheduleRecord, type PortableSchedulingRecordSet, } from "./scheduling-records.js";
@@ -21,6 +21,6 @@ export { CALLBACK_OWNERSHIP_POLICIES, DEFAULT_CALLBACK_OWNERSHIP_POLICY, readCal
 export { CALLBACK_ENDPOINT_SECRET_PATTERN, CALLBACK_URL_REJECTION_REASONS, evaluateCallbackUrl, isPublicCallbackAddress, type CallbackUrlRejectionReason, } from "./callback-safety.js";
 export { CALLBACK_ENDPOINT_LIMIT_PER_ENVIRONMENT, CALLBACK_ENDPOINT_STATUSES, CALLBACK_SIGNING_KEY_ROTATION_OVERLAP_SECONDS, CALLBACK_VERIFICATION_FAILURES, CALLBACK_VERIFICATION_HEADERS, CALLBACK_VERIFICATION_PROTOCOL, CALLBACK_VERIFICATION_PROTOCOL_VERSION, CALLBACK_VERIFICATION_RATE_LIMITS, CALLBACK_VERIFICATION_RESPONSE_BYTES, CALLBACK_VERIFICATION_TIMEOUT_MILLISECONDS, CALLBACK_VERIFICATION_TYPE, callbackEndpointCreatedSchema, callbackEndpointPageSchema, callbackEndpointRequestSchema, callbackEndpointRotatedSchema, callbackEndpointSchema, callbackEndpointStatusSchema, callbackSigningKeyRotationRequestSchema, callbackSigningKeysSchema, callbackVerificationChallengeSchema, callbackVerificationFailureSchema, type CallbackEndpoint, type CallbackEndpointCreated, type CallbackEndpointPage, type CallbackEndpointRequest, type CallbackEndpointRotated, type CallbackEndpointStatus, type CallbackSigningKeyRotationRequest, type CallbackSigningKeys, type CallbackVerificationChallenge, type CallbackVerificationFailure, } from "./endpoints.js";
 export { FORECAST_BOUNDS, FORECAST_BREAKDOWNS, FORECAST_COMPATIBILITY, FORECAST_RULES, FORECAST_WINDOW_VERSION, decideForecastAnswer, forecastBreakdownSchema, forecastBucketSchema, forecastBucketStartMs, forecastLatencyCountsSchema, forecastRequestSchema, forecastSchema, forecastViolations, forecastWindowBucketSchema, forecastWindowViolations, forecastWindowsSchema, mergeForecastBuckets, parseForecastRequest, resolveForecastWindow, topPartitionKeys, type Forecast, type ForecastAnswerDecision, type ForecastAnswerRefusal, type ForecastBreakdown, type ForecastBucket, type ForecastMergedBucket, type ForecastShardAnswer, type ForecastLatencyCounts, type ForecastRequest, type ForecastRequestParse, type ForecastWindow, type ForecastWindowBucket, type ForecastWindowRefusal, type ForecastWindowResolution, type ForecastWindows, } from "./forecast.js";
-export { CURL_JOURNEY_TOOLS, FIRST_VALUE_JOURNEY, FIRST_VALUE_PREREQUISITES, FIRST_VALUE_STEPS, FIRST_VALUE_VARIABLES, JOURNEY_CONDITIONS, MINIMUM_CURL_VERSION, journeyCapturedVariables, journeyReferences, journeyStepSchema, journeyVariable, journeyVariableSchema, resolveJourneyReferences, type FirstValueJourney, type JourneyCapture, type JourneyCondition, type JourneyExpectation, type JourneyPoll, type JourneyPrerequisite, type JourneyRecovery, type JourneyStep, type JourneyVariable, } from "./first-value-journey.js";
+export { CURL_JOURNEY_TOOLS, FIRST_VALUE_JOURNEY, FIRST_VALUE_PREREQUISITES, FIRST_VALUE_STEPS, FIRST_VALUE_VARIABLES, JOURNEY_ACTIVATION_DURATIONS, JOURNEY_ACTIVATION_OUTCOMES, JOURNEY_CONDITIONS, MINIMUM_CURL_VERSION, WEBSITE_JOURNEY_STEPS, WEBSITE_JOURNEY_STEP_KEYS, journeyActivationDuration, journeyCapturedVariables, journeyPathVariables, journeyPoll, journeyPrerequisite, journeyReferences, journeyStepSchema, journeyStepVariables, journeyVariable, journeyVariableName, journeyVariableSchema, parseWebsiteActivationEvent, pathParameterNames, resolveJourneyReferences, websiteActivationEventSchema, websiteJourneySteps, type FirstValueJourney, type JourneyActivationDuration, type JourneyActivationOutcome, type JourneyCapture, type JourneyCondition, type JourneyExpectation, type JourneyPoll, type JourneyPrerequisite, type JourneyRecovery, type JourneyStep, type JourneyVariable, type WebsiteActivationEvent, } from "./first-value-journey.js";
 export { BILLABLE_TERMINAL_STATES, USAGE_BOUNDS, USAGE_WINDOW_REASONS, billableTerminalStateSchema, parseUsageRequest, resolveUsageWindow, usageDaySchema, usageRequestSchema, usageSchema, utcMidnightMs, type BillableTerminalStateName, type ResolvedUsageWindow, type UsageDayView, type UsageRequest, type UsageRequestParse, type UsageView, type UsageWindowRefusal, } from "./usage.js";
 export { CALLBACK_RECEIVER_DISPOSITIONS, CALLBACK_RECEIVER_PROTOCOL, CALLBACK_RECEIVER_STATUS, TEST_SINK_BEHAVIORS, TEST_SINK_BEHAVIOR_FACTS, TEST_SINK_BOUNDS, TEST_SINK_CLIENT_ERROR_STATUSES, TEST_SINK_DISPOSITIONS, TEST_SINK_PROTOCOL_VERSION, TEST_SINK_SERVER_ERROR_STATUSES, callbackReceiverAcknowledgementSchema, callbackReceiverDispositionSchema, resolveTestSinkAction, testSinkBehaviorSchema, testSinkCreateRequestSchema, testSinkDeliveryBodySchema, testSinkDispositionSchema, testSinkDeliveryPageSchema, testSinkDeliverySchema, testSinkPageSchema, testSinkProgramSchema, testSinkSchema, type CallbackReceiverAcknowledgement, type CallbackReceiverDisposition, type TestSink, type TestSinkAction, type TestSinkBehavior, type TestSinkCreateRequest, type TestSinkDelivery, type TestSinkDeliveryBody, type TestSinkDeliveryPage, type TestSinkDisposition, type TestSinkPage, type TestSinkProgram, } from "./test-sink.js";

package/dist/index.js

@@ -1,6 +1,6 @@
 export { ANY_ID_PATTERN, ID_ALPHABET, ID_PREFIXES, apiCredentialEventIdSchema, apiCredentialIdSchema, attemptIdSchema, authorizationRequestIdSchema, callbackSigningKeyIdSchema, deliveryIdSchema, endpointIdSchema, environmentIdSchema, eventIdSchema, idPattern, idSchema, newId, oauthClientIdSchema, oauthGrantEventIdSchema, oauthGrantIdSchema, occurrenceIdSchema, organizationIdSchema, projectIdSchema, resourceOf, scheduleIdSchema, testSinkDeliveryIdSchema, testSinkIdSchema, } from "./identifiers.js";
 export { durationSecondsSchema, timeZoneSchema, timestampSchema, toTimestamp, } from "./time.js";
-export { ENVIRONMENT_KINDS_IN_ORDER, PRINCIPAL_KINDS, SCOPES, SESSION_AUTHORITY_HEADERS, authoritySchema, decideAccess, decideEnvironmentIntent, effectiveScopes, problemCodeForRefusal, environmentKindSchema, principalKindSchema, principalSchema, scopeSchema, } from "./authority.js";
+export { ENVIRONMENT_KINDS_IN_ORDER, PRINCIPAL_KINDS, SCOPES, SESSION_AUTHORITY_HEADERS, authoritySchema, credentialContextSchema, decideAccess, decideEnvironmentIntent, effectiveScopes, problemCodeForRefusal, environmentKindSchema, principalKindSchema, principalSchema, scopeSchema, } from "./authority.js";
 export { PROBLEM_CATEGORIES, PROBLEM_CODES, fieldErrorSchema, isRetryable, problem, problemCategorySchema, problemCodeSchema, problemSchema, } from "./problems.js";
 export { CONCURRENCY_HEADERS, PAGE_SIZE, canonicalRequest, classifyIdempotency, conditionalRequestHeaderSchema, decodeCursor, encodeCursor, etagSchema, freshnessSchema, projectedFreshnessSchema, fromETag, idempotencyKeySchema, idempotencyReplayResponseHeaderSchema, idempotencyRequestHeaderSchema, idempotencyReceiptSchema, idempotencyScopeSchema, pageRequestSchema, pageSchema, parsePageRequest, replayedResponseHeaderSchema, requiredIdempotencyRequestHeaderSchema, requestFingerprint, toETag, versionResponseHeaderSchema, versionSchema, } from "./protocol.js";
 export { CALLBACK_CONTENT_TYPE, CALLBACK_DELIVERY_PROTOCOL, CALLBACK_DELIVERY_PROTOCOL_VERSION, CALLBACK_ENVELOPE_VERSION, CALLBACK_ENVELOPE_VERSION_2026_07_01, CALLBACK_ENVELOPE_VERSION_2026_08_08, CALLBACK_ENVELOPE_VERSION_CHANGE, CALLBACK_ENVELOPE_VERSIONS, CALLBACK_HEADERS, SIGNATURE_SCHEME, SIGNATURE_TOLERANCE_SECONDS, callbackDeferredCompletionSchema, callbackDeliveryTestVectors, callbackEnvelopeSchema, callbackEnvelopeTrigger, callbackHeadersSchema, callbackRun, callbackTriggerSchema, classifyOutcome, classifyStatus, formatSignature, extractCanonicalEnvelopeIds, isTimestampFresh, signatureHeaderSchema, serializeCallbackEnvelope, signingInput, trySigningInput, } from "./signatures.js";
@@ -10,7 +10,7 @@ export { EVENT_TYPES, eventEnvelopeSchema, eventTypeSchema, genericEventSchema,
 export { MEMBERSHIP_ROLES, MEMBERSHIP_STATUSES, externalMembershipIdSchema, externalOrganizationIdSchema, externalUserIdSchema, grantsAccess, leastRole, leastStatus, membershipChangeSchema, membershipRoleSchema, membershipSchema, membershipStatusSchema, organizationTombstoneSchema, sessionMembershipSchema, } from "./identity.js";
 export { CHANGE_KINDS, CHANGE_OPERATIONS, CHANGE_SUBJECTS, CONTRACT_VERSION, assess, changeKindSchema, classifyChange, contractVersionSchema, } from "./compatibility.js";
 export { WORKSPACE_LAYERS, scaffoldProblemSchema, scaffoldVersionSchema, toolDescriptorSchema, toolListSchema, workspaceIdentitySchema, workspaceLayerSchema, workspaceScaffoldSchema, } from "./workspace.js";
-export { MOCK_BEHAVIORS, MOCK_HEADERS, OPERATIONS, UNIVERSAL_PROBLEMS, AUTHENTICATED_PROBLEMS, findOperation, fixtureListSchema, mockBehaviorSchema, mockScenarioRequestSchema, mockScenarioResponseSchema, operationsFor, problemsFor, requestSchemaFor, responseSchemaFor, successStatusFor, } from "./operations.js";
+export { MOCK_BEHAVIORS, MOCK_HEADERS, OPERATIONS, UNIVERSAL_PROBLEMS, AUTHENTICATED_PROBLEMS, SCOPED_PROBLEMS, findOperation, fixtureListSchema, mockBehaviorSchema, mockScenarioRequestSchema, mockScenarioResponseSchema, operationsFor, problemsFor, requestSchemaFor, responseSchemaFor, successStatusFor, } from "./operations.js";
 export { PROJECT_LIST_LIMIT, PROJECT_STATUSES, environmentSchema, organizationSchema, projectCreateRequestSchema, projectListSchema, projectNameSchema, projectSchema, projectStatusSchema, projectSummarySchema, provisionedProjectSchema, } from "./tenancy.js";
 export { ATTEMPT_DURATION_MAX_MS, ATTEMPT_FAILURE_SNIPPET_MAX_LENGTH, ATTEMPT_REMEDIATIONS, ATTEMPT_RESPONSE_HEADER_MAX_LENGTH, ATTEMPT_STATES, CRON_EXPRESSION_MAX_LENGTH, LATENCY_CLASSES, OCCURRENCE_STATES, PARTITION_KEY_MAX_LENGTH, RECURRENCE_REQUEST_FIELDS, SCHEDULE_STATUSES, SCHEDULING_BOUNDS, TERMINAL_OCCURRENCE_STATES, attemptFailureSnippetSchema, attemptResponseHeaderSchema, attemptSchema, attemptDiagnosticSchema, attemptPageSchema, attemptRemediationSchema, attemptStateForResponse, attemptStateSchema, attemptTriggerSchema, attemptViewSchema, cronExpressionSchema, DELIVERY_COMPLETION_MODES, DELIVERY_DURATION_TIERS, DELIVERY_OVERLAP_POLICIES, DEFAULT_DELIVERY_DURATION_SECONDS, DEFAULT_DELIVERY_OVERLAP_POLICY, FREE_DELIVERY_DURATION_SECONDS, isLongRunningDuration, deliveryCompletionModeSchema, deliveryDurationSecondsSchema, deliveryOverlapPolicySchema, deriveDeliverySettings, deriveLatencyClass, generationSchema, isTerminalOccurrenceState, latencyClassSchema, occurrenceSchema, occurrencePageSchema, occurrenceStateSchema, occurrenceViewSchema, partitionKeySchema, remediationForAttempt, recurrenceSchema, schedulePageSchema, scheduleRequestSchema, scheduleSchema, scheduleStatusSchema, scheduleViewSchema, } from "./scheduling.js";
 export { portableAttemptRecordSchema, portableEncryptedPayloadRecordSchema, portableOccurrenceRecordSchema, portableReceiptRecordSchema, portableScheduleRecordSchema, portableSchedulingRecordSetSchema, } from "./scheduling-records.js";
@@ -21,6 +21,6 @@ export { CALLBACK_OWNERSHIP_POLICIES, DEFAULT_CALLBACK_OWNERSHIP_POLICY, readCal
 export { CALLBACK_ENDPOINT_SECRET_PATTERN, CALLBACK_URL_REJECTION_REASONS, evaluateCallbackUrl, isPublicCallbackAddress, } from "./callback-safety.js";
 export { CALLBACK_ENDPOINT_LIMIT_PER_ENVIRONMENT, CALLBACK_ENDPOINT_STATUSES, CALLBACK_SIGNING_KEY_ROTATION_OVERLAP_SECONDS, CALLBACK_VERIFICATION_FAILURES, CALLBACK_VERIFICATION_HEADERS, CALLBACK_VERIFICATION_PROTOCOL, CALLBACK_VERIFICATION_PROTOCOL_VERSION, CALLBACK_VERIFICATION_RATE_LIMITS, CALLBACK_VERIFICATION_RESPONSE_BYTES, CALLBACK_VERIFICATION_TIMEOUT_MILLISECONDS, CALLBACK_VERIFICATION_TYPE, callbackEndpointCreatedSchema, callbackEndpointPageSchema, callbackEndpointRequestSchema, callbackEndpointRotatedSchema, callbackEndpointSchema, callbackEndpointStatusSchema, callbackSigningKeyRotationRequestSchema, callbackSigningKeysSchema, callbackVerificationChallengeSchema, callbackVerificationFailureSchema, } from "./endpoints.js";
 export { FORECAST_BOUNDS, FORECAST_BREAKDOWNS, FORECAST_COMPATIBILITY, FORECAST_RULES, FORECAST_WINDOW_VERSION, decideForecastAnswer, forecastBreakdownSchema, forecastBucketSchema, forecastBucketStartMs, forecastLatencyCountsSchema, forecastRequestSchema, forecastSchema, forecastViolations, forecastWindowBucketSchema, forecastWindowViolations, forecastWindowsSchema, mergeForecastBuckets, parseForecastRequest, resolveForecastWindow, topPartitionKeys, } from "./forecast.js";
-export { CURL_JOURNEY_TOOLS, FIRST_VALUE_JOURNEY, FIRST_VALUE_PREREQUISITES, FIRST_VALUE_STEPS, FIRST_VALUE_VARIABLES, JOURNEY_CONDITIONS, MINIMUM_CURL_VERSION, journeyCapturedVariables, journeyReferences, journeyStepSchema, journeyVariable, journeyVariableSchema, resolveJourneyReferences, } from "./first-value-journey.js";
+export { CURL_JOURNEY_TOOLS, FIRST_VALUE_JOURNEY, FIRST_VALUE_PREREQUISITES, FIRST_VALUE_STEPS, FIRST_VALUE_VARIABLES, JOURNEY_ACTIVATION_DURATIONS, JOURNEY_ACTIVATION_OUTCOMES, JOURNEY_CONDITIONS, MINIMUM_CURL_VERSION, WEBSITE_JOURNEY_STEPS, WEBSITE_JOURNEY_STEP_KEYS, journeyActivationDuration, journeyCapturedVariables, journeyPathVariables, journeyPoll, journeyPrerequisite, journeyReferences, journeyStepSchema, journeyStepVariables, journeyVariable, journeyVariableName, journeyVariableSchema, parseWebsiteActivationEvent, pathParameterNames, resolveJourneyReferences, websiteActivationEventSchema, websiteJourneySteps, } from "./first-value-journey.js";
 export { BILLABLE_TERMINAL_STATES, USAGE_BOUNDS, USAGE_WINDOW_REASONS, billableTerminalStateSchema, parseUsageRequest, resolveUsageWindow, usageDaySchema, usageRequestSchema, usageSchema, utcMidnightMs, } from "./usage.js";
 export { CALLBACK_RECEIVER_DISPOSITIONS, CALLBACK_RECEIVER_PROTOCOL, CALLBACK_RECEIVER_STATUS, TEST_SINK_BEHAVIORS, TEST_SINK_BEHAVIOR_FACTS, TEST_SINK_BOUNDS, TEST_SINK_CLIENT_ERROR_STATUSES, TEST_SINK_DISPOSITIONS, TEST_SINK_PROTOCOL_VERSION, TEST_SINK_SERVER_ERROR_STATUSES, callbackReceiverAcknowledgementSchema, callbackReceiverDispositionSchema, resolveTestSinkAction, testSinkBehaviorSchema, testSinkCreateRequestSchema, testSinkDeliveryBodySchema, testSinkDispositionSchema, testSinkDeliveryPageSchema, testSinkDeliverySchema, testSinkPageSchema, testSinkProgramSchema, testSinkSchema, } from "./test-sink.js";