Make the recurrent lease state coherent

[FujitsuPolycom]

Outcome

This stack fixes the GLM recurrent lease document so the strict verifier can select one coherent final runtime state across all eleven files.

SparkCache PR #35 added four recurrent postimages but left the seven unchanged files under a different named state. The verifier correctly rejected that mixed composition. This change makes recurrent_boundary_contract the only accepted state for the final runtime: the four producer postimages use their new hashes and the seven unchanged files retain their exact existing hashes under the same state name.

The impossible pre-producer state is no longer advertised. The four SparkCache patches still have exact source-state preimage/postimage receipts and produce the inputs consumed by the separate recurrent-boundary producer. The final eleven-file verifier runs only after that producer is composed.

A GPU-free regression executes the real verifier across all eleven contract records with their exact accepted final-state digests and required symbol surface. The SparkRing composer separately applies the patches to the exact vLLM tree and invokes this verifier against the fully composed source.

Exact source identity

• parent: SparkCache PR Bind page-tail publication to proven recurrent boundaries #35 commit 08e297769a796da2668ea58d0ed5c0d9b588565b;
• commit: 49c517ed76e09dd2f7e78eb3ad5fe83382bda6fb;
• Git tree: c8cbfb54fc52c5966f19af3450629376e4e703db;
• deployable SparkCache source SHA-256: 83853050f790b18af95d424fec837abeb1a9a33f0538b5e4b97c16fb9c681781;
• final lease-contract SHA-256: f36ed14eaf1f97a5dffa94bda8151b1e0fa182afc0d121b757b70bebc6a43811.

Cache namespace impact

None. CacheIdentity values, digest salts, 256-token geometry, manifest schemas, page-delta bytes, and the page-tail-cow-v1 namespace are unchanged. The contract metadata changes only the accepted final source-state naming; incompatible or unverified source remains a cache miss.

Validation

• python -m pytest sparkcache -q: 760 passed, 7 skipped;
• python -m pytest deploy -q: 108 passed, 1 skipped;
• python -m ruff check .;
• git diff --check.

No image was built or published, and no service or deployment was changed.

[FujitsuPolycom]

The resulting behavior and evidence are consolidated in retained draft stack #39 → #42 → #44. Independent heat and SSD research remains in #36. Closing this superseded draft and deleting only its remote head branch.