v3.14.3 - four review findings

Four findings, all founded. The first was a bridge built four hours earlier, in the commit meant to close this exact class.

CHAIN_INTACT cleared eight blockers on one sentence. log_chain_status: CHAIN_INTACT mapped to backup_chain_status: CONFIRMED, and that field feeds eight blocking prerequisites whose evidence columns ask for RESTORE VERIFYONLY, a gap check and a restore rehearsal. The consumer is told never to re-ask an inherited fact, so a user saying the chain was unbroken settled all eight and moved a never-tested restore route off blocked. The mapping is asymmetric now, because the two directions are not equally conclusive: a reported break is proof of a problem and stays MISSING, an intact chain is an input to proof and converts to nothing.

Fabric could not be the more permissive of two surfaces. fabric_sql_db stayed eligible for a profile with linked servers while the same trace refused Azure SQL Database for them, on a reason that argues ranking rather than eligibility. SQL database in Fabric is database-scoped and narrower, so it inherits any verdict SQL Database receives. Ten scenarios moved with it.

The error table licensed working from memory. It said the bundled copy is always in context, which contradicts step 1 and lets a model skip the mandatory reads and rebuild the rules from recall, defeating the stop-on-read-failure rule. The row points back at step 1, and step 1 names all seven files rather than three, including both schemas and advisor-coverage.json, without which the candidate list cannot be built.

A candidate nobody could vouch for was written up as available. The exemplar marked five methods available while its profile stated none of the facts their paths turn on, and readers are explicitly invited to hand any available candidate to the planner. A candidate whose blocking prerequisites are unstated now reads unknown_requires_assessment, derived from the catalog, questions.json and the crosswalk rather than written per method, with the missing fields named in evidenceRequired.

74 gates, 117 scenarios, 3625 prerequisite checks.