corpus: mirror rvt-rs #210 — IFCCOLUMN 256/256 recovered, both surfaces widen

[DrunkOnJava]

rvt-rs PR #210 recovers columns from Revit 2024 partition element records
(256/256 on the full-project export, Tag set identical to Revit's own).
Both rvt-rs observations change; the paired-fixture surface is 7 fields /
5 excluded (columns become decoder_baseline there: that reference has no
columns) and the full-project surface is 5 fields / 8 excluded with
IFCCOLUMN the first non-zero field inside it. Manifests rebuilt from the
rvt-rs project-count fixtures under the corpus/README drop rules; index
re-chained; validate-corpus and check-registry pass.

---

Note

Low Risk
Corpus manifest, observation, and verdict JSON only—no runtime or auth changes; risk is limited to scoring-surface semantics and hash-chain consistency.

Overview
Updates the magnetar corpus to reflect rvt-rs #210: both rvt-rs observations now report 256 IFCCOLUMN with extruded geometry (building_elements_with_geometry 256), plus the related IFC graph growth (property sets, placements, etc.). Observation hashes and tamper-evident MANIFEST_INDEX chain head / per-artifact manifest and verdict hashes are refreshed; verdicts remain PASS.

g-2026-0002 (full export) treats columns as known (256/256): entity_counts.IFCCOLUMN joins the semantic_surface, the column exclusion is removed, and manifest notes document the closed #204 decode path. Rooms/spaces gaps are re-tagged from real_file_element_geometry to partial_element_geometry because columns now have real bodies.

g-2026-0001 (element fixture) keeps the bridge at 0 columns: columns become decoder_baseline with IFCCOLUMN excluded (and dropped from the semantic surface) so the 256 count is scored only on the sibling slim manifest, not double-claimed. Property-set and materials notes are updated for column geometry side effects.

Witness diagnostics drop the “no geometry” warning; unsupported feature real_file_element_geometry becomes partial_element_geometry in both observation files.

^{Reviewed by Cursor Bugbot for commit 48bb437. 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_dd0d0b1b-4d72-435d-93cd-ccf0bf1fc3ef)