Brand Proximity test harness

• 1. Original PDF (no params)
  Serves the untouched file from R2.
  https://bp.theframeworks.com/how-to-build-brand-visibility
• 1b. Original PDF, forced download
  Same bytes, as an attachment.
  https://bp.theframeworks.com/how-to-build-brand-visibility?dl=1
• 2. Link-injected PDF
  Same file with all CTA links repointed back here with &request=1. Open it and click a CTA.
  https://bp.theframeworks.com/how-to-build-brand-visibility?email=test%40example.com&name=Jane&company=Acme&source=lemlist
• 2b. Link-injected, forced download
  Same, as an attachment.
  https://bp.theframeworks.com/how-to-build-brand-visibility?email=test%40example.com&name=Jane&company=Acme&source=lemlist&dl=1
• 3. CTA click (what the PDF link hits)
  Updates HubSpot, then 302s to the thank-you page.
  https://bp.theframeworks.com/how-to-build-brand-visibility?email=test%40example.com&name=Jane&company=Acme&source=lemlist&request=1
• 3b. CTA click, JSON instead of redirect
  Same HubSpot write, but shows the result instead of redirecting.
  https://bp.theframeworks.com/how-to-build-brand-visibility?email=test%40example.com&name=Jane&company=Acme&source=lemlist&request=1&debug=1
• 3c. Thank-you page on its own
  The redirect destination, without touching HubSpot.
  https://bp.theframeworks.com/how-to-build-brand-visibility/report-requested?name=Jane&company=Acme
• 4. Link inventory in the source PDF
  Confirms the CTA match string.
  https://bp.theframeworks.com/debug/links