refactor: establish HTML folder feature

[jderochervlk]

Tracking issue: #342

Stack context

Part 17 of the Option 5 folder-feature stack.

• Previous: refactor: establish DOMNodes folder feature #326
• Next: the Media folder layer

Review this PR as the incremental diff against #326.

Summary

• add the target src/html folder on the unqualified internal HTML feature
• move 61 non-media HTML interface modules out of the legacy broad DOM folder
• add the supported WebAPI.HTML -> WebAPI.DOMNodes + WebAPI.File + HTML feature
• expose the existing HTMLUnknownElement interface publicly
• preserve every existing flat HTML module path and binding signature

Media boundary

DomHTMLMediaElement, HTMLAudioElement, HTMLTrackElement, and HTMLVideoElement remain for the next Media layer. Their APIs directly reference Remote Playback, Picture-in-Picture, WebVTT, media-error, time-range, and playback-quality types. Moving them here would create an HTML <-> Media cycle because Media already depends on HTML.

Temporary state

• the four media-specific HTML interfaces remain in the legacy folder for one layer and move with Media next
• HTML.res is received transitively from DOMNodes because Element and ShadowRoot require its serialization/shadow-root options
• final helper-type cleanup remains deferred

Review focus

• HTML folder membership and the explicit media boundary
• the WebAPI.HTML dependency closure
• public exposure of HTMLUnknownElement

Verification

• node_modules/.bin/rescript clean
• node_modules/.bin/rescript build --prod --features DOM,Event,DOMPlatform,Animation,CSSOM,Geometry,DOMNodes,File,HTML
• npm run build
• npm test
• npm run format:check
• git diff --check

[jderochervlk]

@codex

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 9604786121

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Keep HTMLElement available to the DOM feature

When a consumer builds only WebAPI.DOM, this source group still compiles DomHTMLMediaElement and HTMLTrackElement, whose implementations include HTMLElement.Impl (src/DOM/DomHTMLMediaElement.res:147 and src/DOM/HTMLTrackElement.res:14). Because HTMLElement was moved behind the separate HTML feature and WebAPI.DOM does not enable it, that previously valid feature-only build now fails with an unresolved module; keep the base module in the DOM slice until these media interfaces move, or otherwise ensure the slice includes their dependency.

Useful? React with 👍 / 👎.