refactor(forms): enable approved Form A placements by default

www/reports/phase-9-jotform-integration-contract-2026-10-18.md

@@ -1,8 +1,40 @@
 # P9-03 Jotform integration contract
 
-**Contract ID:** P9-03-JF-2026-10-18 · **Version:** 1.8 · **Decision revision:** 2026-10-29
+## Current decision — 2026-10-30: default-live Form A
 
-**Status: Form A owner-approved for existing contexts; consultation surfaces implemented for isolated testing only; deployment and production consultation activation NOT authorized.**
+The owner intentionally supersedes the earlier isolated-test and seven-route
+production-gate architecture. `npm run dev` and `npm run build` now enable Form A
+on exactly **16 approved placements**, including the publicly reachable
+`aia.web3app.dev` environment. No additional approval flags or access restriction
+are required. `PUBLIC_AIA_FORMS_MODE` is optional: absent/empty means `live`;
+explicit `off` and `mock` remain available. Invalid/obsolete `isolated-test`
+settings produce an actionable configuration error. The former approval flags
+and form environment role are retired, not renamed.
+
+Indexing and forms are independent. Both publication modes emit ten immediate
+frames (two contact, five landing, three consultation) and six deferred bilingual
+service-drawer frames. The bounded registry fixes ID `262946078314059`, HTTPS
+origin, context and language. Forms B/C are not activated; physical B is retired.
+
+Live drawers retain four-second/50%-scroll opening, shared 30-day suppression,
+manual CTA override, deferred loading, verified completion acknowledgment for
+five seconds, animated dismissal and fresh-form reopening. Off mode does not
+automatically show inactive drawers. All iframe security/fallback behavior is
+preserved. Employee-portal preview remains independently gated by explicit local
+approval, valid private ciphertext input and non-indexing output; Form A cannot
+authorize private content. No portal private resources enter normal artifacts.
+
+This owner authorization does not modify Jotform, authorize site cutover or
+complete pending consultation-language, provider-event, accessibility, runtime
+telemetry/privacy, recipient-routing or hosting acceptance. See the
+[current operating guide](../integrations/jotform/README.md) and
+[implementation and validation report](phase-9-form-a-default-live-2026-10-30.md).
+Earlier dated decisions and test results below are historical evidence, not
+current environment setup instructions.
+
+**Contract ID:** P9-03-JF-2026-10-18 · **Version:** 1.9 · **Decision revision:** 2026-10-30
+
+**Current status: default-live Form A approved on 16 placements; site deployment/cutover not authorized. Historical contract follows.**
 
 This is the authoritative P9-03 planning contract for the owner decisions supplied on October 18 and revised through October 29. It supersedes conflicting *proposals* in the [October 17 inventory](phase-9-form-entry-point-inventory-2026-10-17.md), without rewriting that historical record. It does not supersede project policy, approve clinical/legal content beyond the Form A configuration scope recorded below, close the Phase 9 register, or authorize production changes. Future changes require an explicit owner decision, a version/change record and evidence links. Version 1.0 records the original planning instruction; version 1.1 adds the owner-supplied complete roster; version 1.2 supersedes the copy-based Form B proposal with three new blank forms; version 1.3 records limited owner-confirmed Form A configuration evidence; version 1.4 reconciles completed direct-Jotform testing and the seven-route isolated iframe adapter; version 1.5 records owner-reported embedded synthetic acceptance for sampled routes; version 1.6 adds the independent production-build gate without deploying it; version 1.7 retires physical Form B and specifies Form A consultation plus Form C referral planning; version 1.8 records the owner-reported consultation configuration and a separate nine-route isolated-test adapter. No future commit SHA is invented.