v1.11.1 — the audit release: 38 fixes, 32 repaired gates, honest coverage

This is the audit release. Every change in it comes from a three-round, 209-agent audit of the entire codebase — every validation gate, every public function, and every published claim — with each finding adversarially refuted before being accepted, and each fix proven by a before/after control with real numbers rather than inspection.

• 38 product defects fixed across the engines and dialogs. The ones most likely to have touched a number you read: the reference impedance is now per-frequency end to end (a waveguide port's modal impedance was truncated to its first sweep value — checked against Pozar eq. 3.22, the column now matches the analytic TE10 impedance across WR-28, and the worst-case normalising error at the top of the band falls from +40 % to +10 %; nothing moves for lumped, coax or microstrip ports). Every Palace solve started from the GUI had been running on one core — the MPI-ranks property was attached to the wrong solver's property block, so the parallel speedup released in v1.5.0 never reached the GUI path until now. Reported wind drag was four to five orders of magnitude low (it rendered as 0.000 N/m) from a doubled area term, and mislabelled Pa when it is newtons. The Smith tab's caption now uses the solver's own S11, so its VSWR and return loss can no longer disagree with the VSWR tab. Nine Element Designer inputs (horn/IFA/PIFA) were wired to nothing — the predicted panel and the PDF described the design from before your edit while Accept & Generate built the edited one. Also fixed: intermodulation levels above third order (wrong by tens of dB), a material change that silently coarsened the FDTD mesh at metal edges, open-conductor inductance, reversed-coil sign handling, assistant answers fabricated beyond the sweep edge, P.1546 optional corrections returning NaN, and a licence path that could lock out a paying customer during a Gumroad outage.
• 32 validation gates could pass while checking nothing — a skip path that returned success when a backend was absent, a bare except-clause that relabelled real regressions as "backend unavailable", checks whose passing condition was a constant, and one gate that asserted against a stub it had installed itself. Each repair was proven by sabotage (gate goes red) then revert (green), and independently re-verified. If you run a gate by hand without its backend now, it says SKIPPED and exits non-zero instead of printing a pass it did not earn.
• The battery now reports coverage, not just exit codes. Each gate's line ends with the number of checks it actually executed, and the summary totals them — because a green run used to discard the only evidence separating a gate that checked 118 things from one that checked none.
• Six published claims were corrected on their live surfaces — including a stale check count, an overstated GPU-agreement tolerance, and a claim that two Pro-only gates ship in this repository's CI. The corrections are in the storefront, the site and the forum threads, with the changes acknowledged in place.
• Two known issues are documented rather than half-fixed (CHANGELOG "Known and deliberately NOT fixed"): a latent NEC2 multi-block parser selection no shipped caller currently reaches, and the pyramidal horn's circular gain cross-check — the candidate fix changed a validated, published anchor's geometry and is held for an explicit design decision.

Pre-tag proof: the full solver battery ran complete on the fix commit itself — 115 ok, 0 failed, 0 skipped, 21,557.2 s (5.99 hours), 3,524 executed checks across 105 gates — with per-gate check counts recorded for the first time. The difference between the proved tree and this tag is version stamps and the CHANGELOG entry.

97 automated validation gates in this repository. Full details in CHANGELOG.md.