html_export_form

HTML export options are hosted inside the general export_webview ( not a separate HTML-only panel long-term ).
When format is HTML: simple options include scope, output folder, export name, and runtime mode.
Advanced HTML settings should be collapsed by default behind an expandable section ( template, cluster strategy, page-family toggles, file filters, url base, header link, print entry, neighbourhood graph node cap ).
File filters: exclude `*.secret.rq` ideas ( `excludeSecretFiles` ) and / or exclude paths matched by `.reqlan/.rqignore` ( `excludeIgnoredFiles` ); both default off so indexed ideas from those files are included unless opted out.
Form defaults persist to application_memory as `export_settings.json` under `<workspace>/.reqlan/` ( shared with other export formats ).
Saving settings or running export writes that file; reopening the form reloads the last values.
HTML export still calls `@reqlan/analytical` `exportHtml` with an `ExportRequest` built from the form.
While export runs, the webview shows progress from the analytical pipeline ( snapshot phases, then write completed / total ) via `exportProgress` messages — see export_webview.
Current implementation is HTML-only and should be generalized; until then the existing panel satisfies the HTML path.

Status: partial

Interactive page: html_export_form