test: guard the public feature graph

[jderochervlk]

Tracking issue: #342

Stack context

Part 31 and final PR of the Option 5 folder-feature stack.

• Previous: refactor: clean up shared feature helpers #340
• Next: none; this closes the implementation stack

Review this PR as the incremental diff against #340.

Summary

• add npm run check:features to validate the exact 27 supported public features
• require one unqualified owning folder feature per public feature
• validate unique source features, source directories, and flat public module files
• compile every qualified WebAPI.* feature independently
• run the feature guardrail in CI
• generate API documentation directly from the rescript.json public module lists
• replace legacy nested feature/interface docs with flat interface pages
• document the distinction between consumer feature bundles and flat module paths

Guardrails

The new check fails when:

• the supported 27-feature list changes unintentionally
• a source folder uses a qualified public feature name
• a public feature lacks exactly one owning internal folder feature
• a public module is duplicated or its source file is missing
• any supported feature has an incomplete compiler dependency closure

Documentation update

The old documentation pipeline still read the pre-Option-5 migration taxonomy and expected nested interface routes. API pages and navigation now follow the actual flat public surface, producing one page per public interface module.

Temporary state

None from the Option 5 migration remains. Future feature changes should update the explicit contract and pass the per-feature compiler checks in this PR.

Review focus

• feature-contract assertions
• per-feature build behavior and CI placement
• flat API documentation discovery and navigation
• consumer feature documentation

Verification

• npm run check:features (all 27 supported features)
• npm run build
• npm test
• npm run build:docs (303 static pages)
• 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: 1091517f92

ℹ️ 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]

Launch the Windows ReScript shim through cmd.exe

On Windows, this selects rescript.cmd but passes it directly to spawnSync without shell: true or cmd.exe /c. Windows batch shims cannot be executed directly this way, so npm run check:features fails before the first feature build; invoke the shim through the command shell or use a cross-platform executable resolution strategy.

Useful? React with 👍 / 👎.