v1.2.3 — Frontend fixes and CDN fallback

What's new

1.2.3

• Fix: duplicate widget rendering on some forms. The inner container shared an id with the outer Gravity Forms wrapper, which caused the <cap-widget> web component's connectedCallback to fire twice (visible as two trigger checkboxes inside one shadow root). Inner container now uses input_X_Y to match the label's for attribute.
• Change: the field's visible <label> is no longer rendered on the frontend. Screen readers still get an accessible name via aria-label on the widget container. Label and label-placement settings are also hidden in the editor.

1.2.2

• Probe the Cap server's /assets/widget.js endpoint on settings save; fall back to a public CDN (jsDelivr, pinned to @cap.js/widget@0.1.51) when ENABLE_ASSETS_SERVER is off or the endpoint is unreachable. Re-checked every 6h.
• Fail-open on siteverify network errors and 5xx responses (logged as errors), so a broken Cap server doesn't lock users out of forms.
• Removed dead type="module" script-tag filter (widget is an IIFE).

1.2.1

• Load the Cap widget directly from {cap_server_url}/assets/widget.js instead of bundling it. Requires ENABLE_ASSETS_SERVER=true on the Cap server.