root a21a34b057 docs: close 2 cross-runtime parity gaps + document unified log

Companion to lakehouse 98b6647. Architecture comparison decisions
tracker now captures:

  - Go validatord direct header read (fixes 6847bbc): closes the
    case where Langfuse-off middleware passthrough silently dropped
    forwarded X-Lakehouse-Trace-Id
  - Rust IterateResponse trace_id echo (fixes 98b6647): closes the
    asymmetry where Go's response carried the join key and Rust's
    didn't
  - Unified longitudinal log demonstrated end-to-end: both daemons
    co-writing /tmp/lakehouse-validator/sessions.jsonl, distinct
    daemon tags, one DuckDB query covers both

24/24 parity assertions (validator 6/6, extract_json 12/12,
session_log 4/4, materializer 2/2) hold against live :3100 + :4110.
Both runtimes deployed with today's full stack.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-05-02 06:25:21 -05:00

728 B

Raw Blame History

Validator parity probe — Rust :3100 vs Go :4110

Date: 2026-05-02T11:24:15Z Rust gateway: http://127.0.0.1:3100 · Go gateway: http://127.0.0.1:4110

Identical POST /v1/validate request → both runtimes. Match = identical HTTP status + identical body (modulo elapsed_ms).

Case	Rust status	Go status	Status match	Body match
playbook_happy	200	200	✓	✓
playbook_missing_fingerprint	422	422	✓	✓
playbook_wrong_prefix	422	422	✓	✓
playbook_empty_endorsed	422	422	✓	✓
playbook_overfull	422	422	✓	✓
fill_phantom	422	422	✓	✓

Tally: 6 match · 0 diff (out of 6 cases)

728 B Raw Blame History

Validator parity probe — Rust :3100 vs Go :4110

728 B

Raw Blame History