Check bilingual inquiry wording and routing
sanitized-routing-evidence.txt
BLANK INPUT: complete from acquired, approved evidence

Required extra input absent from the legacy JSON. For WPForms, capture existing Settings > Notifications evidence without saving changes. Other providers require their own verified path.

REQUIRED SECTIONS
provider/product/version; actual form_id; page capture_id; route_key
[Complete from the source. If unavailable, write unknown and explain the gap.]

notifications enabled/state; exact existing condition or Smart Tag rule
[Complete from the source. If unavailable, write unknown and explain the gap.]

destination role alias; source_ref; observed_at; admin reviewer
[Complete from the source. If unavailable, write unknown and explain the gap.]

configuration-only versus delivery evidence; unknown mappings
[Complete from the source. If unavailable, write unknown and explain the gap.]

IF EVIDENCE IS MISSING
Stop the dependent comparison or mark affected scope explicitly incomplete.

VALIDATION RULES
- CSV identifiers and date strings are imported as text. Preserve leading zeros and exact keys. Do not execute formulas from source values.
- Blank templates are deliberately incomplete. Unknown is not zero, false, missing-not-found or a passing review.
- Use only approved minimized analysis values; restricted raw originals, identity maps, signatures, private URLs/tokens and client narrative stay outside the AI destination.
- A native file may retain its actual header names if manifest.txt supplies a reviewer-verified one-to-one map to this contract. Do not blindly rename files/headers.

Read START-HERE.txt and NATIVE-INPUT-MAPPING.txt for source acquisition, privacy gates and the exact handoff. Include this completed input wherever the prompt expects it; a file that was not loaded or pasted is not AI-visible.