Readable MCP resource responses — verified landing

The progressive response contract passed compatibility, typed-resource, pagination, input-boundary, payload-size, and full-suite verification.

Summary, detail, history, raw, and schema layers for an MCP resource response.
Current human state is the default; lossless storage and historical workflow are requested deliberately.

Measured payloads

ResourceLegacy compact JSONSummary compact JSONReductionVerdict
Plan4,241 bytes564 bytes86.7%Pass
Sprint3,668 bytes576 bytes84.3%Pass
Discovery56,470 bytes4,747 bytes91.6%Pass
Audit18,057 bytes481 bytes97.3%Pass

Measurements use deterministic UTF-8 compact JSON with sorted keys against the final post-landing Reckon checkout. Summary fixtures also enforce absolute byte ceilings and proportional reductions for populated synthetic resources.

Contract verification

Test evidence

GateResult
Focused progressive-view testsAll passing
Malformed selector/cursor and prerequisite-blocking regressions2 passed
Complete repository suite1,373 passed in 28.53 s
Ruff lintClean
Ruff formatClean
Implementation commits8cc940f, c9e14f2

No compatibility failures, schema drift, typed-directory regressions, or concurrency-test regressions were observed.