server.intent_replay

Private, data-only Intent Timeline artifact loading and comparison.

The.chirp-replayschema implemented here is deliberately private and has no compatibility promise or public export. Version 1 is UTF-8 JSON with this exact envelope::

{
  "schema": "chirp.intent-timeline/1",
  "kind": "observation",
  "created_with": {"chirp": "0.x"},
  "application": {"program_fingerprint": "sha256:..." | null},
  "capture": {
    "source": "debug-test",
    "redaction": "public-safe-v1",
    "truncated": false,
    "dropped_count": 0,
    "first_retained_sequence": null
  },
  "events": []
}

Only fields represented by the frozen observation model are serialized. The allowlist contains structural request, render-intent, response, SSE lifecycle, and diagnostic facts. Bodies, HTML, headers, cookies, sessions, authorization, query strings, concrete URLs, context, arbitrary notes, environment data, DSNs, and absolute paths are forbidden. The loader never imports an application, opens a network connection, invokes a route, or mutates application state.

Semantic comparison ignores only documented nondeterminism: elapsed time, opaque capture request IDs, per-event absolute sequence values, capture source, and Chirp patch-version differences. Route/mode, return/render intent, block/target, status, compiled transitions, lifecycle facts, causal parents, ordering, truncation, and program fingerprints remain authoritative.