Skip to content

Free, Open Source, Self-Hosted WhatsApp API Gateway

docs(plugins): drop the schema-form fallback for a stalled config UI

Yudhi Armyndharis814a48e6d31c
diff --git a/docs/19-plugin-architecture.md b/docs/19-plugin-architecture.md
index 5946de92b..8538fcd99 100644
--- a/docs/19-plugin-architecture.md
+++ b/docs/19-plugin-architecture.md
@@ -691,7 +691,8 @@ URL / catalog), not an npm/github source descriptor.
> and `X-Content-Type-Options: nosniff`. The dashboard fetches it **with** the API key and injects the
> body as an iframe `srcdoc` (opaque origin), applying the current document's CSP nonce to inline scripts;
> the editor exchanges config over a `postMessage` bridge, so the API key never reaches the iframe. If
-> the bridge does not initialize, the dashboard shows an error and keeps a declared `configSchema` form usable.
+> the bridge does not initialize within 5 s, the dashboard shows an error; the generated `configSchema`
+> form is not rendered as a fallback.
## 19.9 Plugin Security