Module coverage 

Phase 60 coverage harness — the Spark-reference SQL surface as a measured number, not a vibe.

Three things live here:

1. The Spark-checklist suite (CHECKLIST): one representative case per batch-claimed feature in the crate::grammar matrix. Runnable cases are executed against a fixed in-memory fixture and asserted to succeed; infra-gated features (Iceberg DML, Flight SQL protocol, the distributed runtime) point at where they are proven instead.
2. The matrix-to-test CI rule: every non-n/a, non-planned batch cell must have a checklist case — enforced by [tests::every_claimed_batch_feature_has_a_checklist_case].
3. The published KPI + generated pages: coverage_report computes the pass-rate, and the reference / honesty markdown pages are regenerated from the matrix and drift-guarded against the checked-in copies.

Structs

ChecklistCase

A single checklist case tying a matrix feature id to its evidence.

CoverageReport

A published coverage summary (the phase KPI).

Enums

Coverage

Evidence that a batch-claimed feature works.

Constants

FIXTURE_T

The fixture DDL run before the SQL checklist cases: t(id, name, ts) and u(id, val) as session tables.

FIXTURE_U

Statics

CHECKLIST

The Spark-reference checklist: one case per batch-claimed matrix feature.

Functions

coverage_report

Compute the coverage KPI from the matrix + checklist.