AI sections fall back to fetch with no Qt bridge, for non-React web frontends

ai_sections.html fetches {API_BASE}+path when window.qt is absent; a page-check case routes those requests to server_stub.dispatch(). AI SKILL.md step 6 and frontend.md send plain-HTML/Vue/Angular/Svelte projects to it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

rpa-dashboard-no-ai/templates/frontend.md

@@ -54,6 +54,12 @@ before you report.
 | React, Vue, Angular, Svelte | In the app's `public/` folder (`public/dashboard.html`), so it is served as-is. Port it into the app's components only if the user asks: best effort, with the page as reference. |
 | PyQt web view | Next to the host's page. Use the desktop path (`bridge.py`). |
 
+**AI skill (`rpa-dashboard-ai`):** a React app gets the React starter's components
+ported in. Plain HTML, Vue, Angular and Svelte get this same page with the AI skill's
+`templates/desktop/ai_sections.html` pasted in before `</body>`, placed as above. With no
+Qt bridge it fetches `{API_BASE}` + the AI contract's endpoints. A port into components
+uses `ai_sections.html` as the reference.
+
 Don't edit existing pages to link to it. Tell the user the path to link from
 their nav.