v3.14.4 - a refused gate is not an unchecked one

Four findings, all on the third candidate state introduced one release earlier.

A refused gate and an unchecked one returned the same string. Every caller read both as a refusal, so DMS came back unavailable on a profile where nobody had collected the recovery model. That word asserts the source was examined and failed. It also took the offline P23 variant down with it, which consumes neither online-only fact, and could force a switch to SQL VM. The two are distinguished now, and an unchecked gate leaves both the candidate and the fallback standing.

The unproven-prerequisite check keyed on bridged fields only. A path whose questions are all unbridged had nothing to test, which is how transactional replication was offered as available with none of P13 established. A path the interview cannot reach at all is named as such. It goes to evidenceRequired rather than unknowns, because it is a property of where the two skills divide and not a fact the interview failed to collect.

The evidence line was pushed without the matching unknowns entry, so the always-loaded exemplar failed invariant 5, its own pre-render self-check. Both arrays carry it now, and the two evidence-complete scenarios state the method prerequisites their name claims, so the medium ceiling still has something to prove.

Two schema descriptions still required the selected candidate to be available, while the output contract permits a winner at unknown_requires_assessment with a matching gate, which is what both canonical examples now are.

74 gates, 117 scenarios, 3625 prerequisite checks.