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

www/reports/phase-9-jotform-implementation-plan-2026-10-18.md

@@ -1,6 +1,38 @@
 # P9-03 source-specific implementation plan
 
-Date: **2026-10-18** · Plan version **1.7 revision 2026-10-28** · Governing contract: [P9-03-JF-2026-10-18 v1.7](phase-9-jotform-integration-contract-2026-10-18.md).
+## Current decision — 2026-10-30: default-live Form A
+
+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.
+
+Date: **2026-10-18** · Plan version **1.9 revision 2026-10-30** · Governing contract: [P9-03-JF-2026-10-18 v1.9](phase-9-jotform-integration-contract-2026-10-18.md).
 
 **Planning only. Do not execute any batch from this document without separate authorization.** Phase 9 establishes decisions and bounded implementation authority. Phase 10 retains final production integration acceptance, rollback and cutover. The user stages, signs and pushes.