/**
 * Server route handler for client-originated tracking events.
 *
 * The browser-side `track()` helper (see `client/track.ts`) POSTs
 * `{ name, properties }` to `/_agent-native/track`. This handler validates the
 * payload, resolves the caller's identity, and forwards the event to the same
 * server-side provider registry that server code reaches through `track()`.
 *
 * It is deliberately best-effort: a malformed body is rejected with a 400, but
 * provider delivery never throws back to the browser (the server `track()`
 * already swallows provider errors). On success it returns 204 with no body.
 *
 * Security: this is an authenticated, first-party-only endpoint. It is mounted
 * behind the framework CSRF middleware (which requires the
 * `X-Agent-Native-CSRF` header / JSON content type / same-origin marker that
 * the client helper always sends) and it requires a resolved session so it
 * cannot be used as an open analytics relay. Events are attributed to the
 * resolved `userId` (and `orgId` when the request has an active org), never to
 * a client-supplied identity.
 */
/** Max length of an event name. Mirrors typical provider limits. */
export declare const MAX_TRACK_EVENT_NAME_LENGTH = 200;
export declare const MAX_TRACK_PROPERTIES_BYTES: number;
export interface TrackRouteValidationResult {
    ok: boolean;
    name?: string;
    properties?: Record<string, unknown>;
    error?: string;
}
export declare function validateTrackPayload(body: unknown): TrackRouteValidationResult;