@cat-factory/contracts 0.168.0 → 0.170.0

package/dist/execution.d.ts

@@ -225,287 +225,6 @@ export declare const priorStepOutputSchema: v.ObjectSchema<{
     readonly truncated: v.OptionalSchema<v.BooleanSchema<undefined>, undefined>;
 }, undefined>;
 export type PriorStepOutput = v.InferOutput<typeof priorStepOutputSchema>;
-/**
- * State a polling **gate** step carries (today `ci` and `conflicts`). A gate is
- * special (like a `deployer` step): it is NOT itself an LLM/container agent. It
- * runs a programmatic precheck against a provider (CI check runs / PR mergeability)
- * for the PR head commit and only escalates to a helper container agent (`ci-fixer`
- * / `conflict-resolver`) on a negative verdict, looping until the precheck passes or
- * the attempt budget is spent. Which gate a step is comes from its `agentKind`, so it
- * is not duplicated here. See the engine's `GateDefinition` registry.
- *   - `phase: 'checking'` — running the precheck / waiting for the provider.
- *   - `phase: 'working'`  — a helper agent is in flight (tracked via the step's
- *                           `jobId`); on completion the gate returns to `checking`.
- */
-/** One failing check the CI gate's precheck saw, flattened for display. */
-export declare const gateFailingCheckSchema: v.ObjectSchema<{
-    readonly name: v.StringSchema<undefined>;
-    /** GitHub conclusion (e.g. `failure`, `timed_out`), or null when not reported. */
-    readonly conclusion: v.NullableSchema<v.StringSchema<undefined>, undefined>;
-    /**
-     * The check run's GitHub web URL (`html_url`), so the UI can link straight to the
-     * failed run's logs. Null when GitHub didn't report one.
-     */
-    readonly url: v.OptionalSchema<v.NullableSchema<v.StringSchema<undefined>, undefined>, undefined>;
-    /**
-     * The repo (owner/name) this check belongs to, on a MULTI-REPO block — so the UI can group
-     * failing checks by service. Absent on a single-repo block (there is only the own repo).
-     */
-    readonly repo: v.OptionalSchema<v.StringSchema<undefined>, undefined>;
-}, undefined>;
-export type GateFailingCheck = v.InferOutput<typeof gateFailingCheckSchema>;
-/**
- * One helper-agent attempt the gate dispatched (a ci-fixer / conflict-resolver run),
- * recorded when the job finishes so the UI can show what each attempt tried and how it
- * ended — detail that used to be discarded the moment the gate re-probed.
- */
-export declare const gateAttemptSchema: v.ObjectSchema<{
-    /** 1-based attempt number (matches `attempts` at the time the helper was dispatched). */
-    readonly attempt: v.NumberSchema<undefined>;
-    /** Epoch ms when the helper job finished. */
-    readonly at: v.NumberSchema<undefined>;
-    /**
-     * How the helper job ended:
-     *   - `completed` — the container finished (it may or may not have fully fixed the
-     *     issue; the gate's next precheck is the source of truth, and `summary` carries
-     *     the agent's own account, e.g. which files it left conflicting).
-     *   - `failed`    — the job errored / was evicted without finishing.
-     */
-    readonly outcome: v.PicklistSchema<["completed", "failed"], undefined>;
-    /** The PR head commit the helper worked against, when known. */
-    readonly headSha: v.OptionalSchema<v.NullableSchema<v.StringSchema<undefined>, undefined>, undefined>;
-    /**
-     * The fixing instructions handed to the helper for this round — the failing-check
-     * summary the CI gate fed the `ci-fixer`, the conflict reason / human-review comments
-     * the other gates fed their fixer. Stashed at dispatch and recorded with the attempt so
-     * the run-detail UI can show WHAT each round was asked to fix (not only that a round
-     * happened) — the gate analogue of the Tester attempt's `concerns`. Null when the gate
-     * hands its fixer no textual instructions (the conflicts gate: GitHub reports mergeability
-     * as a single bit and the harness leaves the conflict markers for the resolver).
-     */
-    readonly instructions: v.OptionalSchema<v.NullableSchema<v.StringSchema<undefined>, undefined>, undefined>;
-    /**
-     * Structured failing checks handed to this attempt's helper (the CI gate's red check runs
-     * behind {@link instructions}), snapshotted at dispatch so each attempt shows the checks it
-     * set out to fix. Absent for the conflicts gate (no file-level detail) and when the round
-     * carried no structured checks.
-     */
-    readonly failingChecks: v.OptionalSchema<v.NullableSchema<v.ArraySchema<v.ObjectSchema<{
-        readonly name: v.StringSchema<undefined>;
-        /** GitHub conclusion (e.g. `failure`, `timed_out`), or null when not reported. */
-        readonly conclusion: v.NullableSchema<v.StringSchema<undefined>, undefined>;
-        /**
-         * The check run's GitHub web URL (`html_url`), so the UI can link straight to the
-         * failed run's logs. Null when GitHub didn't report one.
-         */
-        readonly url: v.OptionalSchema<v.NullableSchema<v.StringSchema<undefined>, undefined>, undefined>;
-        /**
-         * The repo (owner/name) this check belongs to, on a MULTI-REPO block — so the UI can group
-         * failing checks by service. Absent on a single-repo block (there is only the own repo).
-         */
-        readonly repo: v.OptionalSchema<v.StringSchema<undefined>, undefined>;
-    }, undefined>, undefined>, undefined>, undefined>;
-    /** The helper's own summary (or the failure reason), naming what it did / what remains. */
-    readonly summary: v.OptionalSchema<v.NullableSchema<v.StringSchema<undefined>, undefined>, undefined>;
-}, undefined>;
-export type GateAttempt = v.InferOutput<typeof gateAttemptSchema>;
-export declare const gateStepStateSchema: v.ObjectSchema<{
-    readonly phase: v.PicklistSchema<["checking", "working"], undefined>;
-    /** How many helper-agent attempts have been dispatched so far. */
-    readonly attempts: v.NumberSchema<undefined>;
-    /** Ceiling on attempts, resolved from the task's merge preset at step start. */
-    readonly maxAttempts: v.NumberSchema<undefined>;
-    /** The PR head commit being gated, once resolved (the own-service PR on a multi-repo block). */
-    readonly headSha: v.OptionalSchema<v.NullableSchema<v.StringSchema<undefined>, undefined>, undefined>;
-    /**
-     * Per-PR head commits for a MULTI-REPO block (service-connections phase 4), keyed by repo
-     * full name (owner/name) — own-service PR plus each peer-service PR. Set by the CI /
-     * conflicts gates whose precheck aggregates across every PR the task opened. Absent for a
-     * single-repo block (the scalar {@link headSha} is the only head).
-     */
-    readonly headShas: v.OptionalSchema<v.NullableSchema<v.RecordSchema<v.StringSchema<undefined>, v.StringSchema<undefined>, undefined>, undefined>, undefined>;
-    /**
-     * The repo the conflicts gate's most recent `fail` verdict found conflicted, so the
-     * single-repo conflict-resolver is dispatched at THAT repo (own-service or a peer) rather
-     * than always the own-service one. Absent ⇒ the own-service repo. Only the conflicts gate
-     * sets it (the CI-fixer runs across all repos, so the CI gate leaves it undefined).
-     */
-    readonly conflictTarget: v.OptionalSchema<v.NullableSchema<v.ObjectSchema<{
-        readonly repo: v.StringSchema<undefined>;
-        readonly frameId: v.OptionalSchema<v.StringSchema<undefined>, undefined>;
-        readonly branch: v.OptionalSchema<v.StringSchema<undefined>, undefined>;
-    }, undefined>, undefined>, undefined>;
-    /**
-     * The most recent precheck verdict, so the UI can show why the gate is looping
-     * (failing → a helper is fixing) vs idle-passing. Set on every probe.
-     */
-    readonly lastVerdict: v.OptionalSchema<v.NullableSchema<v.PicklistSchema<["pass", "pending", "fail"], undefined>, undefined>, undefined>;
-    /**
-     * Human-readable summary of the latest failing precheck (the failing CI checks /
-     * the conflict reason) — the conclusion detail that used to be fed only to the
-     * helper agent and then discarded. Carried across the helper dispatch so the
-     * window keeps showing what is being fixed. Null when the last probe passed.
-     */
-    readonly lastFailureSummary: v.OptionalSchema<v.NullableSchema<v.StringSchema<undefined>, undefined>, undefined>;
-    /**
-     * Structured failing checks behind {@link lastFailureSummary} for the CI gate, so
-     * the UI can list each red check by name + conclusion. Absent for the conflicts
-     * gate (GitHub reports no file-level detail) and when the last probe passed.
-     */
-    readonly failingChecks: v.OptionalSchema<v.NullableSchema<v.ArraySchema<v.ObjectSchema<{
-        readonly name: v.StringSchema<undefined>;
-        /** GitHub conclusion (e.g. `failure`, `timed_out`), or null when not reported. */
-        readonly conclusion: v.NullableSchema<v.StringSchema<undefined>, undefined>;
-        /**
-         * The check run's GitHub web URL (`html_url`), so the UI can link straight to the
-         * failed run's logs. Null when GitHub didn't report one.
-         */
-        readonly url: v.OptionalSchema<v.NullableSchema<v.StringSchema<undefined>, undefined>, undefined>;
-        /**
-         * The repo (owner/name) this check belongs to, on a MULTI-REPO block — so the UI can group
-         * failing checks by service. Absent on a single-repo block (there is only the own repo).
-         */
-        readonly repo: v.OptionalSchema<v.StringSchema<undefined>, undefined>;
-    }, undefined>, undefined>, undefined>, undefined>;
-    /**
-     * The fixing instructions handed to the most-recently dispatched helper (the failing-check
-     * summary / conflict reason / human fix prompt), stashed at dispatch so the attempt recorded
-     * when that helper's job settles can carry WHAT the round was asked to fix onto its
-     * {@link gateAttemptSchema} entry. Transient bookkeeping — the durable per-round history lives
-     * on {@link attemptLog}. Null when the gate hands its fixer no textual instructions.
-     */
-    readonly lastDispatchedInstructions: v.OptionalSchema<v.NullableSchema<v.StringSchema<undefined>, undefined>, undefined>;
-    /**
-     * Epoch ms of the release marker for a time-windowed gate (post-release-health) — the
-     * moment it began watching the deployed release. The gate keeps polling `pending`
-     * until this + the preset's watch window has elapsed (then a clean run passes) or a
-     * monitor/SLO regresses (then it escalates to the on-call agent). Absent for the
-     * CI/conflicts gates.
-     */
-    readonly watchSince: v.OptionalSchema<v.NullableSchema<v.NumberSchema<undefined>, undefined>, undefined>;
-    /**
-     * The watch-window length (minutes) for a time-windowed gate (post-release-health),
-     * resolved from the task's merge preset ONCE on first entry (alongside `maxAttempts`)
-     * so the probe doesn't re-load the block + re-resolve the preset on every poll. Absent
-     * for the CI/conflicts gates.
-     */
-    readonly watchWindowMinutes: v.OptionalSchema<v.NullableSchema<v.NumberSchema<undefined>, undefined>, undefined>;
-    /**
-     * The regressed signals captured when the post-release-health gate escalated to the
-     * on-call agent, so the agent's completion handler can build the `release_regression`
-     * notification + incident enrichment from the SAME evidence the agent investigated
-     * — rather than re-reading Datadog (a third round-trip that could also disagree with
-     * what the agent saw if the window moved). Absent for the CI/conflicts gates.
-     */
-    readonly regressedSignals: v.OptionalSchema<v.NullableSchema<v.ArraySchema<v.ObjectSchema<{
-        readonly kind: v.PicklistSchema<["monitor", "slo"], undefined>;
-        readonly id: v.StringSchema<undefined>;
-        readonly name: v.StringSchema<undefined>;
-        readonly state: v.PicklistSchema<["ok", "warn", "alert", "no_data"], undefined>;
-        readonly detail: v.OptionalSchema<v.StringSchema<undefined>, undefined>;
-    }, undefined>, undefined>, undefined>, undefined>;
-    /**
-     * Append-only history of the helper-agent attempts this gate dispatched (ci-fixer /
-     * conflict-resolver runs), each recorded when its job finished. Lets the UI show what
-     * every attempt tried and how it ended, instead of only a bare `attempts` count.
-     * Absent for the post-release-health gate (its on-call helper is resolved specially).
-     */
-    readonly attemptLog: v.OptionalSchema<v.NullableSchema<v.ArraySchema<v.ObjectSchema<{
-        /** 1-based attempt number (matches `attempts` at the time the helper was dispatched). */
-        readonly attempt: v.NumberSchema<undefined>;
-        /** Epoch ms when the helper job finished. */
-        readonly at: v.NumberSchema<undefined>;
-        /**
-         * How the helper job ended:
-         *   - `completed` — the container finished (it may or may not have fully fixed the
-         *     issue; the gate's next precheck is the source of truth, and `summary` carries
-         *     the agent's own account, e.g. which files it left conflicting).
-         *   - `failed`    — the job errored / was evicted without finishing.
-         */
-        readonly outcome: v.PicklistSchema<["completed", "failed"], undefined>;
-        /** The PR head commit the helper worked against, when known. */
-        readonly headSha: v.OptionalSchema<v.NullableSchema<v.StringSchema<undefined>, undefined>, undefined>;
-        /**
-         * The fixing instructions handed to the helper for this round — the failing-check
-         * summary the CI gate fed the `ci-fixer`, the conflict reason / human-review comments
-         * the other gates fed their fixer. Stashed at dispatch and recorded with the attempt so
-         * the run-detail UI can show WHAT each round was asked to fix (not only that a round
-         * happened) — the gate analogue of the Tester attempt's `concerns`. Null when the gate
-         * hands its fixer no textual instructions (the conflicts gate: GitHub reports mergeability
-         * as a single bit and the harness leaves the conflict markers for the resolver).
-         */
-        readonly instructions: v.OptionalSchema<v.NullableSchema<v.StringSchema<undefined>, undefined>, undefined>;
-        /**
-         * Structured failing checks handed to this attempt's helper (the CI gate's red check runs
-         * behind {@link instructions}), snapshotted at dispatch so each attempt shows the checks it
-         * set out to fix. Absent for the conflicts gate (no file-level detail) and when the round
-         * carried no structured checks.
-         */
-        readonly failingChecks: v.OptionalSchema<v.NullableSchema<v.ArraySchema<v.ObjectSchema<{
-            readonly name: v.StringSchema<undefined>;
-            /** GitHub conclusion (e.g. `failure`, `timed_out`), or null when not reported. */
-            readonly conclusion: v.NullableSchema<v.StringSchema<undefined>, undefined>;
-            /**
-             * The check run's GitHub web URL (`html_url`), so the UI can link straight to the
-             * failed run's logs. Null when GitHub didn't report one.
-             */
-            readonly url: v.OptionalSchema<v.NullableSchema<v.StringSchema<undefined>, undefined>, undefined>;
-            /**
-             * The repo (owner/name) this check belongs to, on a MULTI-REPO block — so the UI can group
-             * failing checks by service. Absent on a single-repo block (there is only the own repo).
-             */
-            readonly repo: v.OptionalSchema<v.StringSchema<undefined>, undefined>;
-        }, undefined>, undefined>, undefined>, undefined>;
-        /** The helper's own summary (or the failure reason), naming what it did / what remains. */
-        readonly summary: v.OptionalSchema<v.NullableSchema<v.StringSchema<undefined>, undefined>, undefined>;
-    }, undefined>, undefined>, undefined>, undefined>;
-    /**
-     * The number of approving reviews the PR had at the last probe, so the UI can show
-     * "1 / N approvals". The "required" side is derived from {@link requiredApprovingReviewCount}
-     * via the same `max(1, …)` floor the gate applies (see review.logic.ts) rather than persisted
-     * a second time. Absent for the other gates.
-     */
-    readonly lastApprovals: v.OptionalSchema<v.NullableSchema<v.NumberSchema<undefined>, undefined>, undefined>;
-    /**
-     * The raw branch-protection required-approving-review count, cached after the FIRST probe
-     * resolves it so subsequent polls skip the static protection read (branch protection is repo
-     * config, not PR activity — re-reading it every poll over a multi-day review only burns GitHub
-     * rate budget). The UI's displayed "required" count is `max(1, this)` (the gate's effective
-     * floor). Absent for the other gates.
-     */
-    readonly requiredApprovingReviewCount: v.OptionalSchema<v.NullableSchema<v.NumberSchema<undefined>, undefined>, undefined>;
-    /**
-     * The GraphQL ids of the review threads the gate just handed the `fixer`, stashed at
-     * dispatch so the helper-completion hook can post a reply + RESOLVE exactly those threads
-     * on GitHub before the next probe reads them. Absent for the other gates.
-     */
-    readonly pendingThreadIds: v.OptionalSchema<v.NullableSchema<v.ArraySchema<v.StringSchema<undefined>, undefined>, undefined>, undefined>;
-    /**
-     * Epoch ms of the newest plain PR comment the gate has already handed the `fixer`. Plain
-     * conversation comments (unlike review threads) can't be "resolved" on GitHub, so they are
-     * tracked by timestamp: a comment newer than this is outstanding; the dispatch advances it to
-     * the batch max. A reviewer's later comment (newer timestamp) re-opens the work. Absent for
-     * the other gates.
-     */
-    readonly lastAddressedCommentAt: v.OptionalSchema<v.NullableSchema<v.NumberSchema<undefined>, undefined>, undefined>;
-    /**
-     * The grace window (minutes) the human-review gate waits after the latest review comment
-     * before dispatching the fixer, resolved from the task's merge preset ONCE on first entry
-     * (alongside `maxAttempts`) so the probe doesn't re-resolve the preset every poll. Absent
-     * for the other gates.
-     */
-    readonly humanReviewGraceMinutes: v.OptionalSchema<v.NullableSchema<v.NumberSchema<undefined>, undefined>, undefined>;
-    /**
-     * A human-initiated freeform fix request parked on the gate (an in-app prompt). Consumed at
-     * the top of the next `evaluateGate` pass, which dispatches the fixer with these instructions
-     * folded in — bypassing the grace window. Absent for the other gates.
-     */
-    readonly pendingFix: v.OptionalSchema<v.NullableSchema<v.ObjectSchema<{
-        readonly instructions: v.StringSchema<undefined>;
-        readonly at: v.NumberSchema<undefined>;
-    }, undefined>, undefined>, undefined>;
-}, undefined>;
-export type GateStepState = v.InferOutput<typeof gateStepStateSchema>;
 /**
  * State a `tester` step carries while it runs the Tester → Fixer loop. Unlike `ci`,
  * the gate's own work IS a container job (the Tester); on a withheld greenlight the
@@ -517,7 +236,7 @@ export type GateStepState = v.InferOutput<typeof gateStepStateSchema>;
 /**
  * One round of the Tester→Fixer loop, recorded when a `fixer` job finishes so the test
  * window can show what each fixer attempt set out to fix and how it ended — the analogue of
- * a polling gate's {@link gateAttemptSchema}, since a fixer run is otherwise an opaque
+ * a polling gate's `gateAttemptSchema`, since a fixer run is otherwise an opaque
  * sub-job with no surface of its own (only a bare `attempts` count).
  */
 export declare const testerAttemptSchema: v.ObjectSchema<{
@@ -1104,92 +823,26 @@ export declare const pipelineStepSchema: v.ObjectSchema<{
      */
     readonly gate: v.OptionalSchema<v.NullableSchema<v.ObjectSchema<{
         readonly phase: v.PicklistSchema<["checking", "working"], undefined>;
-        /** How many helper-agent attempts have been dispatched so far. */
         readonly attempts: v.NumberSchema<undefined>;
-        /** Ceiling on attempts, resolved from the task's merge preset at step start. */
         readonly maxAttempts: v.NumberSchema<undefined>;
-        /** The PR head commit being gated, once resolved (the own-service PR on a multi-repo block). */
         readonly headSha: v.OptionalSchema<v.NullableSchema<v.StringSchema<undefined>, undefined>, undefined>;
-        /**
-         * Per-PR head commits for a MULTI-REPO block (service-connections phase 4), keyed by repo
-         * full name (owner/name) — own-service PR plus each peer-service PR. Set by the CI /
-         * conflicts gates whose precheck aggregates across every PR the task opened. Absent for a
-         * single-repo block (the scalar {@link headSha} is the only head).
-         */
         readonly headShas: v.OptionalSchema<v.NullableSchema<v.RecordSchema<v.StringSchema<undefined>, v.StringSchema<undefined>, undefined>, undefined>, undefined>;
-        /**
-         * The repo the conflicts gate's most recent `fail` verdict found conflicted, so the
-         * single-repo conflict-resolver is dispatched at THAT repo (own-service or a peer) rather
-         * than always the own-service one. Absent ⇒ the own-service repo. Only the conflicts gate
-         * sets it (the CI-fixer runs across all repos, so the CI gate leaves it undefined).
-         */
         readonly conflictTarget: v.OptionalSchema<v.NullableSchema<v.ObjectSchema<{
             readonly repo: v.StringSchema<undefined>;
             readonly frameId: v.OptionalSchema<v.StringSchema<undefined>, undefined>;
             readonly branch: v.OptionalSchema<v.StringSchema<undefined>, undefined>;
         }, undefined>, undefined>, undefined>;
-        /**
-         * The most recent precheck verdict, so the UI can show why the gate is looping
-         * (failing → a helper is fixing) vs idle-passing. Set on every probe.
-         */
         readonly lastVerdict: v.OptionalSchema<v.NullableSchema<v.PicklistSchema<["pass", "pending", "fail"], undefined>, undefined>, undefined>;
-        /**
-         * Human-readable summary of the latest failing precheck (the failing CI checks /
-         * the conflict reason) — the conclusion detail that used to be fed only to the
-         * helper agent and then discarded. Carried across the helper dispatch so the
-         * window keeps showing what is being fixed. Null when the last probe passed.
-         */
         readonly lastFailureSummary: v.OptionalSchema<v.NullableSchema<v.StringSchema<undefined>, undefined>, undefined>;
-        /**
-         * Structured failing checks behind {@link lastFailureSummary} for the CI gate, so
-         * the UI can list each red check by name + conclusion. Absent for the conflicts
-         * gate (GitHub reports no file-level detail) and when the last probe passed.
-         */
         readonly failingChecks: v.OptionalSchema<v.NullableSchema<v.ArraySchema<v.ObjectSchema<{
             readonly name: v.StringSchema<undefined>;
-            /** GitHub conclusion (e.g. `failure`, `timed_out`), or null when not reported. */
             readonly conclusion: v.NullableSchema<v.StringSchema<undefined>, undefined>;
-            /**
-             * The check run's GitHub web URL (`html_url`), so the UI can link straight to the
-             * failed run's logs. Null when GitHub didn't report one.
-             */
             readonly url: v.OptionalSchema<v.NullableSchema<v.StringSchema<undefined>, undefined>, undefined>;
-            /**
-             * The repo (owner/name) this check belongs to, on a MULTI-REPO block — so the UI can group
-             * failing checks by service. Absent on a single-repo block (there is only the own repo).
-             */
             readonly repo: v.OptionalSchema<v.StringSchema<undefined>, undefined>;
         }, undefined>, undefined>, undefined>, undefined>;
-        /**
-         * The fixing instructions handed to the most-recently dispatched helper (the failing-check
-         * summary / conflict reason / human fix prompt), stashed at dispatch so the attempt recorded
-         * when that helper's job settles can carry WHAT the round was asked to fix onto its
-         * {@link gateAttemptSchema} entry. Transient bookkeeping — the durable per-round history lives
-         * on {@link attemptLog}. Null when the gate hands its fixer no textual instructions.
-         */
         readonly lastDispatchedInstructions: v.OptionalSchema<v.NullableSchema<v.StringSchema<undefined>, undefined>, undefined>;
-        /**
-         * Epoch ms of the release marker for a time-windowed gate (post-release-health) — the
-         * moment it began watching the deployed release. The gate keeps polling `pending`
-         * until this + the preset's watch window has elapsed (then a clean run passes) or a
-         * monitor/SLO regresses (then it escalates to the on-call agent). Absent for the
-         * CI/conflicts gates.
-         */
         readonly watchSince: v.OptionalSchema<v.NullableSchema<v.NumberSchema<undefined>, undefined>, undefined>;
-        /**
-         * The watch-window length (minutes) for a time-windowed gate (post-release-health),
-         * resolved from the task's merge preset ONCE on first entry (alongside `maxAttempts`)
-         * so the probe doesn't re-load the block + re-resolve the preset on every poll. Absent
-         * for the CI/conflicts gates.
-         */
         readonly watchWindowMinutes: v.OptionalSchema<v.NullableSchema<v.NumberSchema<undefined>, undefined>, undefined>;
-        /**
-         * The regressed signals captured when the post-release-health gate escalated to the
-         * on-call agent, so the agent's completion handler can build the `release_regression`
-         * notification + incident enrichment from the SAME evidence the agent investigated
-         * — rather than re-reading Datadog (a third round-trip that could also disagree with
-         * what the agent saw if the window moved). Absent for the CI/conflicts gates.
-         */
         readonly regressedSignals: v.OptionalSchema<v.NullableSchema<v.ArraySchema<v.ObjectSchema<{
             readonly kind: v.PicklistSchema<["monitor", "slo"], undefined>;
             readonly id: v.StringSchema<undefined>;
@@ -1197,102 +850,25 @@ export declare const pipelineStepSchema: v.ObjectSchema<{
             readonly state: v.PicklistSchema<["ok", "warn", "alert", "no_data"], undefined>;
             readonly detail: v.OptionalSchema<v.StringSchema<undefined>, undefined>;
         }, undefined>, undefined>, undefined>, undefined>;
-        /**
-         * Append-only history of the helper-agent attempts this gate dispatched (ci-fixer /
-         * conflict-resolver runs), each recorded when its job finished. Lets the UI show what
-         * every attempt tried and how it ended, instead of only a bare `attempts` count.
-         * Absent for the post-release-health gate (its on-call helper is resolved specially).
-         */
         readonly attemptLog: v.OptionalSchema<v.NullableSchema<v.ArraySchema<v.ObjectSchema<{
-            /** 1-based attempt number (matches `attempts` at the time the helper was dispatched). */
             readonly attempt: v.NumberSchema<undefined>;
-            /** Epoch ms when the helper job finished. */
             readonly at: v.NumberSchema<undefined>;
-            /**
-             * How the helper job ended:
-             *   - `completed` — the container finished (it may or may not have fully fixed the
-             *     issue; the gate's next precheck is the source of truth, and `summary` carries
-             *     the agent's own account, e.g. which files it left conflicting).
-             *   - `failed`    — the job errored / was evicted without finishing.
-             */
             readonly outcome: v.PicklistSchema<["completed", "failed"], undefined>;
-            /** The PR head commit the helper worked against, when known. */
             readonly headSha: v.OptionalSchema<v.NullableSchema<v.StringSchema<undefined>, undefined>, undefined>;
-            /**
-             * The fixing instructions handed to the helper for this round — the failing-check
-             * summary the CI gate fed the `ci-fixer`, the conflict reason / human-review comments
-             * the other gates fed their fixer. Stashed at dispatch and recorded with the attempt so
-             * the run-detail UI can show WHAT each round was asked to fix (not only that a round
-             * happened) — the gate analogue of the Tester attempt's `concerns`. Null when the gate
-             * hands its fixer no textual instructions (the conflicts gate: GitHub reports mergeability
-             * as a single bit and the harness leaves the conflict markers for the resolver).
-             */
             readonly instructions: v.OptionalSchema<v.NullableSchema<v.StringSchema<undefined>, undefined>, undefined>;
-            /**
-             * Structured failing checks handed to this attempt's helper (the CI gate's red check runs
-             * behind {@link instructions}), snapshotted at dispatch so each attempt shows the checks it
-             * set out to fix. Absent for the conflicts gate (no file-level detail) and when the round
-             * carried no structured checks.
-             */
             readonly failingChecks: v.OptionalSchema<v.NullableSchema<v.ArraySchema<v.ObjectSchema<{
                 readonly name: v.StringSchema<undefined>;
-                /** GitHub conclusion (e.g. `failure`, `timed_out`), or null when not reported. */
                 readonly conclusion: v.NullableSchema<v.StringSchema<undefined>, undefined>;
-                /**
-                 * The check run's GitHub web URL (`html_url`), so the UI can link straight to the
-                 * failed run's logs. Null when GitHub didn't report one.
-                 */
                 readonly url: v.OptionalSchema<v.NullableSchema<v.StringSchema<undefined>, undefined>, undefined>;
-                /**
-                 * The repo (owner/name) this check belongs to, on a MULTI-REPO block — so the UI can group
-                 * failing checks by service. Absent on a single-repo block (there is only the own repo).
-                 */
                 readonly repo: v.OptionalSchema<v.StringSchema<undefined>, undefined>;
             }, undefined>, undefined>, undefined>, undefined>;
-            /** The helper's own summary (or the failure reason), naming what it did / what remains. */
             readonly summary: v.OptionalSchema<v.NullableSchema<v.StringSchema<undefined>, undefined>, undefined>;
         }, undefined>, undefined>, undefined>, undefined>;
-        /**
-         * The number of approving reviews the PR had at the last probe, so the UI can show
-         * "1 / N approvals". The "required" side is derived from {@link requiredApprovingReviewCount}
-         * via the same `max(1, …)` floor the gate applies (see review.logic.ts) rather than persisted
-         * a second time. Absent for the other gates.
-         */
         readonly lastApprovals: v.OptionalSchema<v.NullableSchema<v.NumberSchema<undefined>, undefined>, undefined>;
-        /**
-         * The raw branch-protection required-approving-review count, cached after the FIRST probe
-         * resolves it so subsequent polls skip the static protection read (branch protection is repo
-         * config, not PR activity — re-reading it every poll over a multi-day review only burns GitHub
-         * rate budget). The UI's displayed "required" count is `max(1, this)` (the gate's effective
-         * floor). Absent for the other gates.
-         */
         readonly requiredApprovingReviewCount: v.OptionalSchema<v.NullableSchema<v.NumberSchema<undefined>, undefined>, undefined>;
-        /**
-         * The GraphQL ids of the review threads the gate just handed the `fixer`, stashed at
-         * dispatch so the helper-completion hook can post a reply + RESOLVE exactly those threads
-         * on GitHub before the next probe reads them. Absent for the other gates.
-         */
         readonly pendingThreadIds: v.OptionalSchema<v.NullableSchema<v.ArraySchema<v.StringSchema<undefined>, undefined>, undefined>, undefined>;
-        /**
-         * Epoch ms of the newest plain PR comment the gate has already handed the `fixer`. Plain
-         * conversation comments (unlike review threads) can't be "resolved" on GitHub, so they are
-         * tracked by timestamp: a comment newer than this is outstanding; the dispatch advances it to
-         * the batch max. A reviewer's later comment (newer timestamp) re-opens the work. Absent for
-         * the other gates.
-         */
         readonly lastAddressedCommentAt: v.OptionalSchema<v.NullableSchema<v.NumberSchema<undefined>, undefined>, undefined>;
-        /**
-         * The grace window (minutes) the human-review gate waits after the latest review comment
-         * before dispatching the fixer, resolved from the task's merge preset ONCE on first entry
-         * (alongside `maxAttempts`) so the probe doesn't re-resolve the preset every poll. Absent
-         * for the other gates.
-         */
         readonly humanReviewGraceMinutes: v.OptionalSchema<v.NullableSchema<v.NumberSchema<undefined>, undefined>, undefined>;
-        /**
-         * A human-initiated freeform fix request parked on the gate (an in-app prompt). Consumed at
-         * the top of the next `evaluateGate` pass, which dispatches the fixer with these instructions
-         * folded in — bypassing the grace window. Absent for the other gates.
-         */
         readonly pendingFix: v.OptionalSchema<v.NullableSchema<v.ObjectSchema<{
             readonly instructions: v.StringSchema<undefined>;
             readonly at: v.NumberSchema<undefined>;
@@ -1800,6 +1376,57 @@ export declare const pipelineStepSchema: v.ObjectSchema<{
         }, "Provide exactly one of forkId or custom.">]>, undefined>, undefined>;
         readonly model: v.OptionalSchema<v.NullableSchema<v.StringSchema<undefined>, undefined>, undefined>;
     }, undefined>, undefined>, undefined>;
+    /**
+     * Live JUDGE state on a judge step (the fourth taxonomy bucket): the rubric identity, the
+     * latest structured verdict, the per-task threshold it was compared against, the bounce
+     * budget, and the round history. Created lazily by the engine on first entry and — like
+     * `forkDecision` / `followUps` — deliberately PRESERVED across `resetStepForRerun`, so a
+     * bounce that re-runs the producer plus this step does not erase the verdict it is looping
+     * on. Absent for non-judge steps. See {@link judgeStepStateSchema}.
+     */
+    readonly judge: v.OptionalSchema<v.NullableSchema<v.ObjectSchema<{
+        readonly status: v.PicklistSchema<["evaluating", "awaiting_decision", "bouncing", "passed", "failed", "skipped"], undefined>;
+        readonly rubricId: v.OptionalSchema<v.NullableSchema<v.StringSchema<undefined>, undefined>, undefined>;
+        readonly rubricName: v.OptionalSchema<v.NullableSchema<v.StringSchema<undefined>, undefined>, undefined>;
+        readonly rubricOverridden: v.OptionalSchema<v.BooleanSchema<undefined>, false>;
+        readonly verdict: v.OptionalSchema<v.NullableSchema<v.ObjectSchema<{
+            readonly score: v.SchemaWithFallback<v.SchemaWithPipe<readonly [v.NumberSchema<undefined>, v.MinValueAction<number, 0, undefined>, v.MaxValueAction<number, 1, undefined>]>, 0>;
+            readonly summary: v.SchemaWithFallback<v.StringSchema<undefined>, "">;
+            readonly findings: v.OptionalSchema<v.SchemaWithFallback<v.ArraySchema<v.ObjectSchema<{
+                readonly title: v.SchemaWithFallback<v.StringSchema<undefined>, "Untitled finding">;
+                readonly detail: v.SchemaWithFallback<v.OptionalSchema<v.StringSchema<undefined>, undefined>, undefined>;
+                readonly severity: v.SchemaWithFallback<v.PicklistSchema<["low", "medium", "high", "critical"], undefined>, "medium">;
+                readonly where: v.SchemaWithFallback<v.OptionalSchema<v.StringSchema<undefined>, undefined>, undefined>;
+            }, undefined>, undefined>, readonly []>, readonly []>;
+        }, undefined>, undefined>, undefined>;
+        readonly threshold: v.OptionalSchema<v.NullableSchema<v.NumberSchema<undefined>, undefined>, undefined>;
+        readonly disposition: v.OptionalSchema<v.NullableSchema<v.PicklistSchema<["pass", "park", "bounce", "fail"], undefined>, undefined>, undefined>;
+        readonly bounces: v.OptionalSchema<v.NumberSchema<undefined>, 0>;
+        readonly maxBounces: v.OptionalSchema<v.NumberSchema<undefined>, 1>;
+        readonly model: v.OptionalSchema<v.NullableSchema<v.StringSchema<undefined>, undefined>, undefined>;
+        readonly rounds: v.OptionalSchema<v.ArraySchema<v.ObjectSchema<{
+            readonly round: v.NumberSchema<undefined>;
+            readonly at: v.NumberSchema<undefined>;
+            readonly verdict: v.ObjectSchema<{
+                readonly score: v.SchemaWithFallback<v.SchemaWithPipe<readonly [v.NumberSchema<undefined>, v.MinValueAction<number, 0, undefined>, v.MaxValueAction<number, 1, undefined>]>, 0>;
+                readonly summary: v.SchemaWithFallback<v.StringSchema<undefined>, "">;
+                readonly findings: v.OptionalSchema<v.SchemaWithFallback<v.ArraySchema<v.ObjectSchema<{
+                    readonly title: v.SchemaWithFallback<v.StringSchema<undefined>, "Untitled finding">;
+                    readonly detail: v.SchemaWithFallback<v.OptionalSchema<v.StringSchema<undefined>, undefined>, undefined>;
+                    readonly severity: v.SchemaWithFallback<v.PicklistSchema<["low", "medium", "high", "critical"], undefined>, "medium">;
+                    readonly where: v.SchemaWithFallback<v.OptionalSchema<v.StringSchema<undefined>, undefined>, undefined>;
+                }, undefined>, undefined>, readonly []>, readonly []>;
+            }, undefined>;
+            readonly disposition: v.PicklistSchema<["pass", "park", "bounce", "fail"], undefined>;
+            readonly model: v.OptionalSchema<v.NullableSchema<v.StringSchema<undefined>, undefined>, undefined>;
+        }, undefined>, undefined>, readonly []>;
+        readonly note: v.OptionalSchema<v.NullableSchema<v.StringSchema<undefined>, undefined>, undefined>;
+        readonly resolution: v.OptionalSchema<v.NullableSchema<v.ObjectSchema<{
+            readonly choice: v.PicklistSchema<["proceed", "bounce", "stop"], undefined>;
+            readonly feedback: v.OptionalSchema<v.NullableSchema<v.StringSchema<undefined>, undefined>, undefined>;
+            readonly at: v.NumberSchema<undefined>;
+        }, undefined>, undefined>, undefined>;
+    }, undefined>, undefined>, undefined>;
     /**
      * Live "Ralph loop" state carried on a `ralph` step: the persistent retry-until-done
      * loop's iteration count, budget, validation command, and per-iteration history. Seeded
@@ -2596,92 +2223,26 @@ export declare const executionInstanceSchema: v.ObjectSchema<{
          */
         readonly gate: v.OptionalSchema<v.NullableSchema<v.ObjectSchema<{
             readonly phase: v.PicklistSchema<["checking", "working"], undefined>;
-            /** How many helper-agent attempts have been dispatched so far. */
             readonly attempts: v.NumberSchema<undefined>;
-            /** Ceiling on attempts, resolved from the task's merge preset at step start. */
             readonly maxAttempts: v.NumberSchema<undefined>;
-            /** The PR head commit being gated, once resolved (the own-service PR on a multi-repo block). */
             readonly headSha: v.OptionalSchema<v.NullableSchema<v.StringSchema<undefined>, undefined>, undefined>;
-            /**
-             * Per-PR head commits for a MULTI-REPO block (service-connections phase 4), keyed by repo
-             * full name (owner/name) — own-service PR plus each peer-service PR. Set by the CI /
-             * conflicts gates whose precheck aggregates across every PR the task opened. Absent for a
-             * single-repo block (the scalar {@link headSha} is the only head).
-             */
             readonly headShas: v.OptionalSchema<v.NullableSchema<v.RecordSchema<v.StringSchema<undefined>, v.StringSchema<undefined>, undefined>, undefined>, undefined>;
-            /**
-             * The repo the conflicts gate's most recent `fail` verdict found conflicted, so the
-             * single-repo conflict-resolver is dispatched at THAT repo (own-service or a peer) rather
-             * than always the own-service one. Absent ⇒ the own-service repo. Only the conflicts gate
-             * sets it (the CI-fixer runs across all repos, so the CI gate leaves it undefined).
-             */
             readonly conflictTarget: v.OptionalSchema<v.NullableSchema<v.ObjectSchema<{
                 readonly repo: v.StringSchema<undefined>;
                 readonly frameId: v.OptionalSchema<v.StringSchema<undefined>, undefined>;
                 readonly branch: v.OptionalSchema<v.StringSchema<undefined>, undefined>;
             }, undefined>, undefined>, undefined>;
-            /**
-             * The most recent precheck verdict, so the UI can show why the gate is looping
-             * (failing → a helper is fixing) vs idle-passing. Set on every probe.
-             */
             readonly lastVerdict: v.OptionalSchema<v.NullableSchema<v.PicklistSchema<["pass", "pending", "fail"], undefined>, undefined>, undefined>;
-            /**
-             * Human-readable summary of the latest failing precheck (the failing CI checks /
-             * the conflict reason) — the conclusion detail that used to be fed only to the
-             * helper agent and then discarded. Carried across the helper dispatch so the
-             * window keeps showing what is being fixed. Null when the last probe passed.
-             */
             readonly lastFailureSummary: v.OptionalSchema<v.NullableSchema<v.StringSchema<undefined>, undefined>, undefined>;
-            /**
-             * Structured failing checks behind {@link lastFailureSummary} for the CI gate, so
-             * the UI can list each red check by name + conclusion. Absent for the conflicts
-             * gate (GitHub reports no file-level detail) and when the last probe passed.
-             */
             readonly failingChecks: v.OptionalSchema<v.NullableSchema<v.ArraySchema<v.ObjectSchema<{
                 readonly name: v.StringSchema<undefined>;
-                /** GitHub conclusion (e.g. `failure`, `timed_out`), or null when not reported. */
                 readonly conclusion: v.NullableSchema<v.StringSchema<undefined>, undefined>;
-                /**
-                 * The check run's GitHub web URL (`html_url`), so the UI can link straight to the
-                 * failed run's logs. Null when GitHub didn't report one.
-                 */
                 readonly url: v.OptionalSchema<v.NullableSchema<v.StringSchema<undefined>, undefined>, undefined>;
-                /**
-                 * The repo (owner/name) this check belongs to, on a MULTI-REPO block — so the UI can group
-                 * failing checks by service. Absent on a single-repo block (there is only the own repo).
-                 */
                 readonly repo: v.OptionalSchema<v.StringSchema<undefined>, undefined>;
             }, undefined>, undefined>, undefined>, undefined>;
-            /**
-             * The fixing instructions handed to the most-recently dispatched helper (the failing-check
-             * summary / conflict reason / human fix prompt), stashed at dispatch so the attempt recorded
-             * when that helper's job settles can carry WHAT the round was asked to fix onto its
-             * {@link gateAttemptSchema} entry. Transient bookkeeping — the durable per-round history lives
-             * on {@link attemptLog}. Null when the gate hands its fixer no textual instructions.
-             */
             readonly lastDispatchedInstructions: v.OptionalSchema<v.NullableSchema<v.StringSchema<undefined>, undefined>, undefined>;
-            /**
-             * Epoch ms of the release marker for a time-windowed gate (post-release-health) — the
-             * moment it began watching the deployed release. The gate keeps polling `pending`
-             * until this + the preset's watch window has elapsed (then a clean run passes) or a
-             * monitor/SLO regresses (then it escalates to the on-call agent). Absent for the
-             * CI/conflicts gates.
-             */
             readonly watchSince: v.OptionalSchema<v.NullableSchema<v.NumberSchema<undefined>, undefined>, undefined>;
-            /**
-             * The watch-window length (minutes) for a time-windowed gate (post-release-health),
-             * resolved from the task's merge preset ONCE on first entry (alongside `maxAttempts`)
-             * so the probe doesn't re-load the block + re-resolve the preset on every poll. Absent
-             * for the CI/conflicts gates.
-             */
             readonly watchWindowMinutes: v.OptionalSchema<v.NullableSchema<v.NumberSchema<undefined>, undefined>, undefined>;
-            /**
-             * The regressed signals captured when the post-release-health gate escalated to the
-             * on-call agent, so the agent's completion handler can build the `release_regression`
-             * notification + incident enrichment from the SAME evidence the agent investigated
-             * — rather than re-reading Datadog (a third round-trip that could also disagree with
-             * what the agent saw if the window moved). Absent for the CI/conflicts gates.
-             */
             readonly regressedSignals: v.OptionalSchema<v.NullableSchema<v.ArraySchema<v.ObjectSchema<{
                 readonly kind: v.PicklistSchema<["monitor", "slo"], undefined>;
                 readonly id: v.StringSchema<undefined>;
@@ -2689,102 +2250,25 @@ export declare const executionInstanceSchema: v.ObjectSchema<{
                 readonly state: v.PicklistSchema<["ok", "warn", "alert", "no_data"], undefined>;
                 readonly detail: v.OptionalSchema<v.StringSchema<undefined>, undefined>;
             }, undefined>, undefined>, undefined>, undefined>;
-            /**
-             * Append-only history of the helper-agent attempts this gate dispatched (ci-fixer /
-             * conflict-resolver runs), each recorded when its job finished. Lets the UI show what
-             * every attempt tried and how it ended, instead of only a bare `attempts` count.
-             * Absent for the post-release-health gate (its on-call helper is resolved specially).
-             */
             readonly attemptLog: v.OptionalSchema<v.NullableSchema<v.ArraySchema<v.ObjectSchema<{
-                /** 1-based attempt number (matches `attempts` at the time the helper was dispatched). */
                 readonly attempt: v.NumberSchema<undefined>;
-                /** Epoch ms when the helper job finished. */
                 readonly at: v.NumberSchema<undefined>;
-                /**
-                 * How the helper job ended:
-                 *   - `completed` — the container finished (it may or may not have fully fixed the
-                 *     issue; the gate's next precheck is the source of truth, and `summary` carries
-                 *     the agent's own account, e.g. which files it left conflicting).
-                 *   - `failed`    — the job errored / was evicted without finishing.
-                 */
                 readonly outcome: v.PicklistSchema<["completed", "failed"], undefined>;
-                /** The PR head commit the helper worked against, when known. */
                 readonly headSha: v.OptionalSchema<v.NullableSchema<v.StringSchema<undefined>, undefined>, undefined>;
-                /**
-                 * The fixing instructions handed to the helper for this round — the failing-check
-                 * summary the CI gate fed the `ci-fixer`, the conflict reason / human-review comments
-                 * the other gates fed their fixer. Stashed at dispatch and recorded with the attempt so
-                 * the run-detail UI can show WHAT each round was asked to fix (not only that a round
-                 * happened) — the gate analogue of the Tester attempt's `concerns`. Null when the gate
-                 * hands its fixer no textual instructions (the conflicts gate: GitHub reports mergeability
-                 * as a single bit and the harness leaves the conflict markers for the resolver).
-                 */
                 readonly instructions: v.OptionalSchema<v.NullableSchema<v.StringSchema<undefined>, undefined>, undefined>;
-                /**
-                 * Structured failing checks handed to this attempt's helper (the CI gate's red check runs
-                 * behind {@link instructions}), snapshotted at dispatch so each attempt shows the checks it
-                 * set out to fix. Absent for the conflicts gate (no file-level detail) and when the round
-                 * carried no structured checks.
-                 */
                 readonly failingChecks: v.OptionalSchema<v.NullableSchema<v.ArraySchema<v.ObjectSchema<{
                     readonly name: v.StringSchema<undefined>;
-                    /** GitHub conclusion (e.g. `failure`, `timed_out`), or null when not reported. */
                     readonly conclusion: v.NullableSchema<v.StringSchema<undefined>, undefined>;
-                    /**
-                     * The check run's GitHub web URL (`html_url`), so the UI can link straight to the
-                     * failed run's logs. Null when GitHub didn't report one.
-                     */
                     readonly url: v.OptionalSchema<v.NullableSchema<v.StringSchema<undefined>, undefined>, undefined>;
-                    /**
-                     * The repo (owner/name) this check belongs to, on a MULTI-REPO block — so the UI can group
-                     * failing checks by service. Absent on a single-repo block (there is only the own repo).
-                     */
                     readonly repo: v.OptionalSchema<v.StringSchema<undefined>, undefined>;
                 }, undefined>, undefined>, undefined>, undefined>;
-                /** The helper's own summary (or the failure reason), naming what it did / what remains. */
                 readonly summary: v.OptionalSchema<v.NullableSchema<v.StringSchema<undefined>, undefined>, undefined>;
             }, undefined>, undefined>, undefined>, undefined>;
-            /**
-             * The number of approving reviews the PR had at the last probe, so the UI can show
-             * "1 / N approvals". The "required" side is derived from {@link requiredApprovingReviewCount}
-             * via the same `max(1, …)` floor the gate applies (see review.logic.ts) rather than persisted
-             * a second time. Absent for the other gates.
-             */
             readonly lastApprovals: v.OptionalSchema<v.NullableSchema<v.NumberSchema<undefined>, undefined>, undefined>;
-            /**
-             * The raw branch-protection required-approving-review count, cached after the FIRST probe
-             * resolves it so subsequent polls skip the static protection read (branch protection is repo
-             * config, not PR activity — re-reading it every poll over a multi-day review only burns GitHub
-             * rate budget). The UI's displayed "required" count is `max(1, this)` (the gate's effective
-             * floor). Absent for the other gates.
-             */
             readonly requiredApprovingReviewCount: v.OptionalSchema<v.NullableSchema<v.NumberSchema<undefined>, undefined>, undefined>;
-            /**
-             * The GraphQL ids of the review threads the gate just handed the `fixer`, stashed at
-             * dispatch so the helper-completion hook can post a reply + RESOLVE exactly those threads
-             * on GitHub before the next probe reads them. Absent for the other gates.
-             */
             readonly pendingThreadIds: v.OptionalSchema<v.NullableSchema<v.ArraySchema<v.StringSchema<undefined>, undefined>, undefined>, undefined>;
-            /**
-             * Epoch ms of the newest plain PR comment the gate has already handed the `fixer`. Plain
-             * conversation comments (unlike review threads) can't be "resolved" on GitHub, so they are
-             * tracked by timestamp: a comment newer than this is outstanding; the dispatch advances it to
-             * the batch max. A reviewer's later comment (newer timestamp) re-opens the work. Absent for
-             * the other gates.
-             */
             readonly lastAddressedCommentAt: v.OptionalSchema<v.NullableSchema<v.NumberSchema<undefined>, undefined>, undefined>;
-            /**
-             * The grace window (minutes) the human-review gate waits after the latest review comment
-             * before dispatching the fixer, resolved from the task's merge preset ONCE on first entry
-             * (alongside `maxAttempts`) so the probe doesn't re-resolve the preset every poll. Absent
-             * for the other gates.
-             */
             readonly humanReviewGraceMinutes: v.OptionalSchema<v.NullableSchema<v.NumberSchema<undefined>, undefined>, undefined>;
-            /**
-             * A human-initiated freeform fix request parked on the gate (an in-app prompt). Consumed at
-             * the top of the next `evaluateGate` pass, which dispatches the fixer with these instructions
-             * folded in — bypassing the grace window. Absent for the other gates.
-             */
             readonly pendingFix: v.OptionalSchema<v.NullableSchema<v.ObjectSchema<{
                 readonly instructions: v.StringSchema<undefined>;
                 readonly at: v.NumberSchema<undefined>;
@@ -3292,6 +2776,57 @@ export declare const executionInstanceSchema: v.ObjectSchema<{
             }, "Provide exactly one of forkId or custom.">]>, undefined>, undefined>;
             readonly model: v.OptionalSchema<v.NullableSchema<v.StringSchema<undefined>, undefined>, undefined>;
         }, undefined>, undefined>, undefined>;
+        /**
+         * Live JUDGE state on a judge step (the fourth taxonomy bucket): the rubric identity, the
+         * latest structured verdict, the per-task threshold it was compared against, the bounce
+         * budget, and the round history. Created lazily by the engine on first entry and — like
+         * `forkDecision` / `followUps` — deliberately PRESERVED across `resetStepForRerun`, so a
+         * bounce that re-runs the producer plus this step does not erase the verdict it is looping
+         * on. Absent for non-judge steps. See {@link judgeStepStateSchema}.
+         */
+        readonly judge: v.OptionalSchema<v.NullableSchema<v.ObjectSchema<{
+            readonly status: v.PicklistSchema<["evaluating", "awaiting_decision", "bouncing", "passed", "failed", "skipped"], undefined>;
+            readonly rubricId: v.OptionalSchema<v.NullableSchema<v.StringSchema<undefined>, undefined>, undefined>;
+            readonly rubricName: v.OptionalSchema<v.NullableSchema<v.StringSchema<undefined>, undefined>, undefined>;
+            readonly rubricOverridden: v.OptionalSchema<v.BooleanSchema<undefined>, false>;
+            readonly verdict: v.OptionalSchema<v.NullableSchema<v.ObjectSchema<{
+                readonly score: v.SchemaWithFallback<v.SchemaWithPipe<readonly [v.NumberSchema<undefined>, v.MinValueAction<number, 0, undefined>, v.MaxValueAction<number, 1, undefined>]>, 0>;
+                readonly summary: v.SchemaWithFallback<v.StringSchema<undefined>, "">;
+                readonly findings: v.OptionalSchema<v.SchemaWithFallback<v.ArraySchema<v.ObjectSchema<{
+                    readonly title: v.SchemaWithFallback<v.StringSchema<undefined>, "Untitled finding">;
+                    readonly detail: v.SchemaWithFallback<v.OptionalSchema<v.StringSchema<undefined>, undefined>, undefined>;
+                    readonly severity: v.SchemaWithFallback<v.PicklistSchema<["low", "medium", "high", "critical"], undefined>, "medium">;
+                    readonly where: v.SchemaWithFallback<v.OptionalSchema<v.StringSchema<undefined>, undefined>, undefined>;
+                }, undefined>, undefined>, readonly []>, readonly []>;
+            }, undefined>, undefined>, undefined>;
+            readonly threshold: v.OptionalSchema<v.NullableSchema<v.NumberSchema<undefined>, undefined>, undefined>;
+            readonly disposition: v.OptionalSchema<v.NullableSchema<v.PicklistSchema<["pass", "park", "bounce", "fail"], undefined>, undefined>, undefined>;
+            readonly bounces: v.OptionalSchema<v.NumberSchema<undefined>, 0>;
+            readonly maxBounces: v.OptionalSchema<v.NumberSchema<undefined>, 1>;
+            readonly model: v.OptionalSchema<v.NullableSchema<v.StringSchema<undefined>, undefined>, undefined>;
+            readonly rounds: v.OptionalSchema<v.ArraySchema<v.ObjectSchema<{
+                readonly round: v.NumberSchema<undefined>;
+                readonly at: v.NumberSchema<undefined>;
+                readonly verdict: v.ObjectSchema<{
+                    readonly score: v.SchemaWithFallback<v.SchemaWithPipe<readonly [v.NumberSchema<undefined>, v.MinValueAction<number, 0, undefined>, v.MaxValueAction<number, 1, undefined>]>, 0>;
+                    readonly summary: v.SchemaWithFallback<v.StringSchema<undefined>, "">;
+                    readonly findings: v.OptionalSchema<v.SchemaWithFallback<v.ArraySchema<v.ObjectSchema<{
+                        readonly title: v.SchemaWithFallback<v.StringSchema<undefined>, "Untitled finding">;
+                        readonly detail: v.SchemaWithFallback<v.OptionalSchema<v.StringSchema<undefined>, undefined>, undefined>;
+                        readonly severity: v.SchemaWithFallback<v.PicklistSchema<["low", "medium", "high", "critical"], undefined>, "medium">;
+                        readonly where: v.SchemaWithFallback<v.OptionalSchema<v.StringSchema<undefined>, undefined>, undefined>;
+                    }, undefined>, undefined>, readonly []>, readonly []>;
+                }, undefined>;
+                readonly disposition: v.PicklistSchema<["pass", "park", "bounce", "fail"], undefined>;
+                readonly model: v.OptionalSchema<v.NullableSchema<v.StringSchema<undefined>, undefined>, undefined>;
+            }, undefined>, undefined>, readonly []>;
+            readonly note: v.OptionalSchema<v.NullableSchema<v.StringSchema<undefined>, undefined>, undefined>;
+            readonly resolution: v.OptionalSchema<v.NullableSchema<v.ObjectSchema<{
+                readonly choice: v.PicklistSchema<["proceed", "bounce", "stop"], undefined>;
+                readonly feedback: v.OptionalSchema<v.NullableSchema<v.StringSchema<undefined>, undefined>, undefined>;
+                readonly at: v.NumberSchema<undefined>;
+            }, undefined>, undefined>, undefined>;
+        }, undefined>, undefined>, undefined>;
         /**
          * Live "Ralph loop" state carried on a `ralph` step: the persistent retry-until-done
          * loop's iteration count, budget, validation command, and per-iteration history. Seeded