@reticlehq/server 2.14.0 → 3.2.0

package/dist/events/predicate-eval.d.ts

@@ -1,101 +0,0 @@
-import { PredicateKind, type ReticleEvent } from '@reticlehq/core';
-export { evalConsole } from './predicate-console.js';
-import type { Predicate } from './predicate-schema.js';
-export * from './predicate-schema.js';
-export interface EvalResult {
-    pass: boolean;
-    /**
-     * For a TIME-based failure: how long until this predicate could first become true, if nothing else
-     * changes. Purely a scheduling hint for `waitForPredicate` — it replaces a blind poll tick with one
-     * timed to the moment that matters, and never decides anything. Absent when the wait is on an
-     * external event (a request in flight settles when the server answers, not on a clock).
-     */
-    retryAfterMs?: number;
-    /**
-     * Set when the assertion could not be EVALUATED — the call was under-specified or there was
-     * nothing instrumented to read — rather than evaluated and found false. Carries the sentence that
-     * names what is missing.
-     *
-     * `pass` stays false because nothing was proven, but a false that nobody could have made true is
-     * not a defect in the user's app, and reporting it as one puts agent mistakes into the bug count.
-     */
-    inconclusive?: string;
-    /**
-     * No later event in this window can change this answer, so waiting out the rest of the budget
-     * buys nothing.
-     *
-     * Set ONLY where that is provable, which is rarer than it looks. "The toast never appeared" is not
-     * decided — it is only knowable when the budget ends, and ending early there would manufacture the
-     * false negative the budget exists to prevent. Exact cardinality IS decided once exceeded, because
-     * a window only accumulates matches and a count cannot come back down.
-     *
-     * A scheduling fact, never a verdict: `pass` already says what the answer is, and this only says
-     * that it is final.
-     */
-    decided?: boolean;
-    evidence?: unknown;
-    failureReason?: string;
-    /**
-     * The wait ended because the TAB went away, not because the app did anything observable.
-     *
-     * A sibling of `inconclusive` and for the same reason: `pass` is false because nothing was
-     * proven, but nobody could have made it true, so grading it as a defect in the user's app is a
-     * false claim. Without this the verdict rule saw only `pass: false` and answered
-     * `assertion_failed` — "the declared consequence did not hold" — naming the component the agent
-     * had just clicked. See VerifiedReason.OBSERVATION_LOST.
-     */
-    observationLost?: boolean;
-    /**
-     * The failure, structured — what was seen, what was required, and which oracle judged it.
-     *
-     * `failureReason` says the same thing in prose, and prose is the WRONG shape for this: measured on
-     * three seeded bugs, an agent handed observed/expected/assertion alongside the source pointer used
-     * fewer tool calls than one handed the pointer alone, and the repair literature has structured
-     * feedback beating rich natural-language feedback by 10.5pp. The prose stays for humans reading a
-     * log; these three fields are for the agent.
-     *
-     * Optional because they are populated per oracle, not globally — see the note in predicate.ts on
-     * which classes carry them today.
-     */
-    observed?: string;
-    expected?: string;
-    assertion?: string;
-}
-export declare function str(value: unknown): string | undefined;
-/**
- * Match one value against a pattern. Supports `*` (present), strict equality, and operators:
- * `{$gte,$lte,$gt,$lt}` (numbers), `{$contains}` (array membership or substring), `{$length}`.
- */
-export declare function matchValue(got: unknown, want: unknown): boolean;
-/** Shallow JSON pattern match: each key in `pattern` must match (see matchValue). */
-export declare function dataMatches(actual: Record<string, unknown>, pattern: Record<string, unknown>): boolean;
-/** Enough of a body to see what differed, without paying for a whole payload in the verdict. */
-export declare function clipBody(body: string): string;
-/**
- * The filter as APPLIED, every field of it.
- *
- * The count failure used to print `{method, urlContains, status}` while `ok` and `bodyContains` were
- * applied too, so the caller was shown a predicate it had not written and told nothing matched it.
- * A printed filter that is narrower than the real one is worse than none: it is believed.
- */
-export declare function describeNetFilter(p: Extract<Predicate, {
-    kind: typeof PredicateKind.NET;
-}>): string;
-export declare function evalNet(events: ReticleEvent[], p: Extract<Predicate, {
-    kind: typeof PredicateKind.NET;
-}>): EvalResult;
-export declare function evalAnimation(events: ReticleEvent[], p: Extract<Predicate, {
-    kind: typeof PredicateKind.ANIMATION;
-}>): EvalResult;
-export declare function evalSignal(events: ReticleEvent[], p: Extract<Predicate, {
-    kind: typeof PredicateKind.SIGNAL;
-}>): EvalResult;
-/**
- * "The page has gone quiet": no network/DOM/animation activity for at least `quietMs`. Needs the
- * wall-clock `now` (in the buffer's time base) because "no activity in the last N ms" is relative to
- * now, not to any buffered event — so `now` is injected (CLAUDE.md rule 7), and the wait loop's
- * poll interval is what eventually flips this to pass once activity stops.
- */
-export declare function evalSettled(allEvents: ReticleEvent[], p: Extract<Predicate, {
-    kind: typeof PredicateKind.SETTLED;
-}>, now: number): EvalResult;