corpus: rebuild manifest surfaces from all three blocks — fixes the MANIFEST_ERROR my #9 merge shipped

[DrunkOnJava]

The #9 mirror rebuilt semantic_surface/excluded from the counts block
alone, dropping relations.IFCRELFILLSELEMENT and storeys.IFCBUILDINGSTOREY,
and I merged it while both verdict jobs were red — the gate said
MANIFEST_ERROR and was right. The mirror now folds the relations and
storeys blocks into the declared surface/exclusions; both verdicts PASS
locally against the committed observations and the index re-chains.

---

Note

Low Risk
Metadata-only corpus manifest and index updates; no runtime decoder or auth changes, only restores CI gate consistency.

Overview
Repairs corpus manifests after a mirror rebuild that only derived semantic_surface / excluded from counts, which left relations.opening_fills and storeys.building_storeys out of sync with the normative §6.1 blocks and tripped MANIFEST_ERROR in tools/verdict.py.

On g-2026-0002 (full export), relations.opening_fills and storeys.building_storeys are added to the claimed surface. On g-2026-0001 (element fixture), storeys.building_storeys is claimed and relations.opening_fills is listed under excluded as decoder_baseline, matching the existing relation row. Redundant relation_ifc_type / expected_pairs and storey_ifc_type / expected_storeys fields are removed from those blocks per corpus README. MANIFEST_INDEX.json manifest hashes, prev_hash, and chain_head are updated for the re-chained manifests.

^{Reviewed by Cursor Bugbot for commit 0928ea2. Configure here.}

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_3bc1db60-0e43-4df0-ac46-b80f40b58659)