[Docs] Promote the Web Build Constraints table into an audited parity matrix with test-coverage column #391

Open
opened 2026-07-16 16:48:06 +00:00 by john · 0 comments
Owner

Part of #387. CLAUDE.md's "Web Build Constraints" table is a 5-row hand-maintained summary (Audio / ImGui / Dynamic assets / Threading / Input). Several rows are asserted without a test behind them (Input " Full" — see #389), and the desktop-only boundaries (#62 multi-window, #336 free-threading, #337 numpy-out-of-scope) live only in issue comments.

Scope

Promote it to a living parity matrix (wiki page + the CLAUDE.md table linking to it) with, per feature:

  • Desktop (SFML) support
  • Web (SDL2/WebGL) support
  • Test coverage — which test/harness validates the row (e.g. #388 diff harness, #389 input test), or "unverified"
  • Notes / boundary rationale

Rows to add beyond the current five: shaders (GLSL ES dialect, #347), RenderTexture/framebuffer round-trip, pixel-perfect scaling & text AA, multi-window (desktop-only, #62), free-threading (desktop-only, #336), numpy (desktop-only, #337), dynamic filesystem.

Principle

The matrix is only honest if the "test coverage" column is real — a row marked with no test is a claim, not a fact. This doc is the human-readable index into what the #388 harness and #389 test actually prove.

Depends on the harness/tests it references landing, but the doc scaffold can go up first and be filled in as coverage lands.

Part of #387. CLAUDE.md's "Web Build Constraints" table is a 5-row hand-maintained summary (Audio / ImGui / Dynamic assets / Threading / Input). Several rows are asserted without a test behind them (Input "✅ Full" — see #389), and the desktop-only boundaries (#62 multi-window, #336 free-threading, #337 numpy-out-of-scope) live only in issue comments. ## Scope Promote it to a living **parity matrix** (wiki page + the CLAUDE.md table linking to it) with, per feature: - Desktop (SFML) support - Web (SDL2/WebGL) support - **Test coverage** — which test/harness validates the row (e.g. #388 diff harness, #389 input test), or "unverified" - Notes / boundary rationale Rows to add beyond the current five: shaders (GLSL ES dialect, #347), RenderTexture/framebuffer round-trip, pixel-perfect scaling & text AA, multi-window (desktop-only, #62), free-threading (desktop-only, #336), numpy (desktop-only, #337), dynamic filesystem. ## Principle The matrix is only honest if the "test coverage" column is real — a row marked ✅ with no test is a claim, not a fact. This doc is the human-readable index into what the #388 harness and #389 test actually prove. Depends on the harness/tests it references landing, but the doc scaffold can go up first and be filled in as coverage lands.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
john/McRogueFace#391
No description provided.