# Revision 2 CRM screenshot comparison

Fresh gpt-6-luna high reviewer `/root/rev2_blind_crm` described 14 screenshots without website, provider, source, or expected-result access. Root read the finished report once and compared it to actual screenshots and saved DOM/API receipts.

- Five mappings show matching partner links, synthetic email addresses, request identifiers, source and form details. First and repeated requests remain traceable through the previous-request cards. Partner IDs are 3660 main, 3661 wedding, 3662 company, 3663 private and 3659 custom group inquiry.
- The screenshot search contains eleven synthetic partners including five historical probes. API exact-email searches identify exactly one partner for each of the six acceptance addresses. Clipped table email cells alone are not claimed as full-address proof.
- The newsletter list shows Codex Hirlevel926, the exact synthetic address, and subscribed eligibility. Final source/consent preservation is evidenced in the separate final newsletter readback and screenshots.
- D4 request fields preserve 1 000 000 Ft per person with international flights and 7 Bali nights. Final properly measured mobile evidence is separate.

## Literal-description corrections and limits

The reviewer repeated ROUND1 text in some repeat-request descriptions. Actual screenshot and saved DOM show the distinct BO-QA-516/525/549/6-20260926-R2 markers, with different request UUIDs. Root rejects the copied prose as an exact transcription.

The wedding repeat screenshot visibly renders `Nászút & Esküvő Balin`, one literal entity, not the reviewer's `&`. Company similarly shows `Céges & Incentive Utak`. The existing CRM schema choices are the corresponding ordinary-ampersand labels. Integration sends those exact schema values; provider API and CRM display encode the ampersand. Semantic choice and other mapped values match, but this provider display blemish is retained explicitly rather than claimed typography-perfect. No global CRM schema or existing customer records were changed to conceal it.

D4 history screenshots precede later mobile verification requests. Their two-record count is historical, not a claim about the final total. Final provider reconciliation lists all task-created request IDs.