/**
 * Payload bounding for the Outpost session heartbeat.
 *
 * ## Why this exists
 *
 * The heartbeat enumerates every Claude transcript and Codex rollout on the
 * box. On a long-lived Outpost that is an archive, not a status: the box this
 * was first run against had **8,258 Claude transcripts and 1,082 Codex
 * rollouts — 9,340 sessions — of which 15 had any activity in the last 15
 * minutes.** Publishing all of them produced a payload of roughly 1.9 MB.
 *
 * AWS IoT Core rejects anything over 128 KB, so the very first real publish
 * failed with `payload larger than 131072 bytes`. Every subsequent one would
 * have too. The heartbeat is a liveness signal; it must carry what is live.
 *
 * Two rules, both tested here:
 *   1. `ended` sessions are not published — they are history, and re-sending
 *      thousands of them every five seconds is the bug.
 *   2. Whatever survives that filter is still bounded by BYTES, because a busy
 *      box could exceed the limit on live sessions alone. When the bound bites
 *      it is reported, never silent — a truncated payload that looks complete
 *      is how you get a wrong dashboard instead of a missing one.
 */
export {};
//# sourceMappingURL=session-heartbeat-bounds.test.d.ts.map