v3.14.0 — three P1 defects from a behaviour audit

Three defects found by replaying profiles instead of reading files. Every surface was green.

DMS-MODE read neither of the two fields it names. recovery_model and log_chain_status became typed fields in v3.11.0, and the engine mentioned neither, so online DMS came back available on a source in SIMPLE recovery with a broken log chain — the one state the rule exists to refuse. Four combinations of the two produced the same answer. AVS-LICENSING and COPILOT-AGENT were in the same position with target_region and preview_acceptable.

The check written for exactly this compared the rule index against the schema, not against the engine. Declaring a field and reading it are different things. It compares both now, and a scenario carries the refusal.

The plan validator checked the rows a plan carried, never the rows it owed. A P10 plan cut from nineteen prerequisites to one, counts recalculated to agree, came back valid and ready. The catalog knows what a path owes and is asked now.

The exemplar plan failed its own output schema in 181 places. acceptedEvidence ids were resolved against sourceRegister, which types citations and cannot hold an evidence record. The one plan object shipped here was built to satisfy the validator and never run past the schema it claims to be. One evidence model now, and the exemplar is checked against the schema and the invariants in the same run.

Six DMS online scenarios state the recovery model and chain the rule requires. Three AVS scenarios drop to low confidence while a regional licence question is open.

73 gates, 3613 prerequisite checks, 117 scenarios.