# mainskeeper CLI — PROPOSED product contract, not shipped software. Fictional demonstration data.
# screen: queue-draining · host: duplex-pi-probe · 80 columns · NO_COLOR · exit 0
# clock: Wed 30 Sep 2026 15:22 PDT · Fixture · incident state, now 15:22
# stderr lines (counting the prompt line as 1): none
duplex-pi-probe $ mainskeeper queue
MainsKeeper · duplex-pi-probe · queue                  Wed 30 Sep 2026 15:22 PDT
⇡ Draining · history arriving

Pending
  1,248 records
  38.2 MB
Storage
  38.2 MB of 512 MB disk cap
  retention target 30 days
  ██░░░░░░░░░░░░░░░░░░░░░░░░░░░░ 7%
Oldest pending
  13:41:00 PDT
  1 h 41 min ago
Last upload
  15:21:48 PDT (12 s ago)
  batch 16 of 64
Retries
  1 · 15:19:00 server 503 → accepted on retry
Drain
  ~22 min (estimate)
Dropped
  0 records
Gaps
  ▨ 14:30:00–14:52:10 No records
  probe offline — none exist, not lost in transit

Backfill
  Historical backfill updates history at observation time and does not generate
  duplicate or obsolete notifications. Fresh evidence of an active condition
  remains alertable while a backlog drains. Ordinary transmission latency does
  not make a reading historical replay.
  Replay = a record received more than 2 min after its observation time while
  the collector was reconnecting and draining its local buffer. Normal
  transmission latency (seconds) is not replay.
  History upload does not affect recovery: INC-0411 recovered 15:02:06.
