/**
 * Verify failures as categories, for the command beacon.
 *
 * `classify.ts` writes its failures as prose for the agent and the creator, and that prose can
 * carry a path, an error message or a console line — none of which belongs in an analytics
 * event (see the contract in `telemetry/report.ts`). This maps each failure back to the check
 * that produced it, so `cli_command(verify, ok=false)` can say WHICH check failed without saying
 * anything else. The messages in `result.json` are unchanged; publish still reads them.
 *
 * Keep the table in step with `classify.ts`: a new failure there lands in `other` here until it
 * gets a row, and `categories.test.ts` pins every existing message to its category.
 */
export type VerifyFailureCategory = 'page_error' | 'start_threw' | 'play_unclickable' | 'selection_stalled' | 'never_started' | 'webgpu_fallback' | 'mobile_parity' | 'no_canvas' | 'canvas_zero' | 'canvas_unclaimed' | 'frame_blank' | 'frame_black' | 'frame_flat' | 'gl_context_lost' | 'engine_error' | 'cors_blocked' | 'fell_out_of_world' | 'still_falling' | 'render_stalled' | 'other';
export declare function categoriseVerifyFailure(message: string): VerifyFailureCategory;
/** The distinct categories of a run's failures, in first-seen order — what the beacon carries. */
export declare function verifyFailureCategories(failures: readonly string[]): VerifyFailureCategory[];