fulcra-lab-resultslisted

# fulcra-lab-results — lab-report PDFs into per-marker Fulcra tracks Turn a lab-report PDF into structured, queryable history in the operator's own Fulcra account: one canonical **data track per marker** (Total Cholesterol, LDL-C, HbA1c, TSH, ferritin, …), regardless of which lab produced the report. Over time, every LDL-C result — LabCorp in March, Quest in September, a hospital draw in between — lands on the *same* track, so it reads as one time series. ## The split: model extracts, code verifies This is the load-bearing idea. **You (the model) do exactly one thing the code can't: read the PDF and transcribe what's printed.** Everything else — resolving `"CHOL"` to `total-cholesterol`, converting `5.5 mmol/L` to `99.1 mg/dL`, sanity-checking the value, computing the idempotent id, writing to Fulcra — is done by the deterministic `fulcra-labs` engine. Do NOT convert units, round, infer a missing unit, or "fix" a value yourself. Transcribe exactly what's on the page; let the engine do the rest. This pipeline is **verify-before-ingest** — the deliberate opposite of the media plugins' over-capture. Lab data is medical PII, so a wrong value is worse than a missing one. Nothing reaches Fulcra unless it passes validation (`ok`) or the operator explicitly confirms a flagged row. **Invocation.** The engine is the `fulcra-labs` console script. From the fulcra-tools repo run it with `uv run fulcra-labs <command>`; once installed as a tool, just `fulcra-labs <command>`. All comman