Phase 1: Tas input manifest: per-space record of what Tas actually received #230

Parent: #227

Goal

The Tas counterpart of SAM-BIM/SAM_OpenStudio#30: after Tas preparation, record per space what the TBD actually contains, using the same JSON structure, so that inputs can be compared field by field.

Context

• TBD preparation (weather, zones, shading) happens in WPF/SAM.Analytical.UI.WPF/Modify/Simulate.cs:923-955 before RunWorkflow.
• Use the read-back functions SAM_Tas already has (TBD → SAM conversions) wherever possible. If something is missing in SAM_Tas, raise a separate SAM_Tas issue rather than adding a workaround here.

Scope

• Read the generated TBD (copy) after preparation and write input-manifest-tas.json with the fields defined in Input manifest: per-space record of what EnergyPlus actually received (for Tas comparison) SAM_OpenStudio#30: geometry areas and volumes, construction U and g values as Tas computes them, gains, schedule full-load hours, setpoints, infiltration and ventilation, weather and design-day identity.
• Fields Tas does not expose are written as available:false with a reason.

Out of scope

Changing Tas preparation behaviour.

Depends on

#228 (Tas baseline, same models and settings); SAM-BIM/SAM_OpenStudio#30 (manifest schema).

Acceptance criteria

• On case A, comparing the SAM-side manifest with the Tas manifest gives values within the tolerances defined in the benchmark-cases issue. Anything outside them is classified (mapping rule, Tas methodology, or defect).
• Deterministic output for the same TBD.

Validation