import type { ServerSkillVersion, ServerArtifact, ServerPin, ServerRunLog, ServerRunRecord, ServerSkillBundle, ServerSkillRecord, PublishedSkillSelectionState } from "./types.js";
export declare function nowIso(): string;
/**
 * Coerce a caller-supplied row limit to a non-negative integer.
 *
 * The two engines disagree loudly about what a bad limit means. SQLite reads `LIMIT -1`
 * as *unlimited* and rejects `LIMIT 1.5` as a datatype mismatch; Postgres rejects -1 and
 * rounds 1.5 up. Left alone, `listRuns(principal, -1)` returned one org's entire history
 * on SQLite and an error on Postgres - and the SQLite answer is the dangerous direction,
 * since the argument exists to bound the response. HTTP callers are already clamped in
 * app.ts; this covers the store used as a library, which is a published seam.
 */
export declare function normalizeLimit(limit: number): number;
export declare function runId(): string;
export declare function artifactId(): string;
export declare function rowToRun(row: Record<string, unknown>): ServerRunRecord;
export declare function rowToLog(row: Record<string, unknown>): ServerRunLog;
export declare function rowToArtifact(row: Record<string, unknown>): ServerArtifact;
export declare function rowToSkill(row: Record<string, unknown>): ServerSkillRecord;
export declare function rowToPublishedSelectionState(row: Record<string, unknown>): PublishedSkillSelectionState;
export declare function rowToPin(row: Record<string, unknown>): ServerPin;
export declare function rowToSkillBundle(row: Record<string, unknown>): ServerSkillBundle;
export declare function parseJsonObject(value: unknown): Record<string, unknown>;
export declare function parseJsonArray(value: unknown): string[];
export declare function dateString(value: unknown): string;
export declare function rowToSkillVersion(row: Record<string, unknown>): ServerSkillVersion;