docs(referrals): retire Form C plan and document existing hosted workflow

www/integrations/jotform/README.md

@@ -57,8 +57,11 @@ Every URL has exactly `formContext` and `language` parameters:
 | consultation | `/client-consultation` (en), `/es/client-consultation` (es), `/schedule-consultation` (en) | Immediate, 3 |
 | consultation | `/aba-therapy`, `/autism-evaluations`, `/learner-social-club` (en), and their `/es/` counterparts (es) | Deferred, 6 |
 
-The context is presentation-only. Physical Form B is retired. Form C and
-`/referrals` remain inactive; other routes cannot acquire Form A by setting a mode.
+The context is presentation-only. Physical Form B is retired. No Form C is planned.
+`/referrals` independently links to the existing hosted Jotform
+`https://form.jotform.com/231638510219149`, not to Form A. That link is
+owner-directed but its legacy form's runtime privacy/recipient acceptance remains
+separate from Form A. Other routes cannot acquire Form A by setting a mode.
 The typed future Academy service copy does not publish another page.
 
 Live service drawers open at four seconds OR 50% scroll, canceling the unused
@@ -110,6 +113,15 @@ node tools/phase10-artifact-verify.mjs --mode=indexing --forms=live
 Employee-portal ciphertext remains separately gated by its own approval, private
 input and non-indexing preview requirement. Form A modes cannot authorize it.
 
+## Existing professional referral destination (owner decision 2026-11-01)
+
+`/referrals` has one `Refer a Client` link to
+[the existing hosted Jotform](https://form.jotform.com/231638510219149). It does not embed Form A
+or use Form C. No new form, question, Jotform integration, query parameter or
+notification routing is introduced. Test the link and verify the separate
+existing form's privacy, field necessity, recipients and confirmation with its
+account owner before release.
+
 ## Form context and button labels
 
 The current Form A design uses a hidden `formContext` value with fixed, approved values such as `contact` and `landing`. Jotform does not provide a native conditional rule that changes one Submit button's accessible label safely in every context. If owner-approved context-specific labels are required, use multiple native Jotform Submit buttons and Jotform's conditional visibility rules:
@@ -130,7 +142,7 @@ cross-origin iframe.
 
 - [x] Direct English/Spanish Form A language handling, conditional email requirement, synthetic submission and native thank-you were owner-verified; this is not embedded-iframe acceptance.
 - [x] Direct staff-notification/autoresponder delivery, generic no-answer/no-PDF content, fixed Reply-To, recipient access/retention, and absent webhooks/integrations were owner-verified for Form A.
-- [ ] Exact remaining Form A consultation question properties, choices, conditional routing and availability, plus future Form C configuration, are approved.
+- [ ] Exact remaining Form A consultation question properties, choices, conditional routing and availability, and consultation language/configuration, are approved.
 - [ ] English and Spanish embedded-iframe labels, validation, confirmation, and button variants are reviewed by fluent-language owners.
 - [ ] The hidden honeypot remains present, effective, and excluded from user-facing visual changes.
 - [ ] Exactly one native Submit button is visible for every valid context.