docs: add GitHub issue drafts for page-load & renderer failures (#273–#277)

[ford442]

Summary

Adds local copies of the expanded GitHub issue bodies created during the 2026-06-17 production investigation (https://test.1ink.us/xm-player/).

These drafts correspond to live issues:

• WebGPU init failure does not auto-fallback to WebGL2/HTML #273 — WebGPU init failure does not auto-fallback to WebGL2/HTML
• Pattern data never reaches renderers after parser worker (blank WebGL2 / empty HTML grid) #274 — Pattern data never reaches renderers after parser worker
• Production stylesheet uses .1iss extension and incorrect utf-16 charset header #275 — Production stylesheet .1iss extension + wrong utf-16 charset
• Parser status stuck at 'Parsing…' — no timeout, worker errors swallowed #276 — Parser status stuck at "Parsing…"
• Production deploy hygiene: COEP mismatch, stale /assets bundles, CDN dependency risk #277 — Production deploy hygiene (COEP, stale assets, CDN)

Why keep these in-repo?

• Preserves full RCA text, file references, and acceptance criteria alongside the codebase
• Useful as implementation checklists when fixing the linked issues
• Avoids losing detail if issue comments are edited on GitHub

Files

• .github/issues/issue-1-webgpu-fallback.md
• .github/issues/issue-2-pattern-data-pipeline.md
• .github/issues/issue-3-css-build-artifact.md
• .github/issues/issue-4-parser-timeout-ux.md
• .github/issues/issue-5-deployment-hygiene.md

No runtime code changes.

  

[coderabbitai]

Warning

Review limit reached

@ford442, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 52 minutes and 34 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 6c1d2765-41d7-4e90-b482-67dce35003c0

📥 Commits

Reviewing files that changed from the base of the PR and between 86ca33b and 04e39f2.

📒 Files selected for processing (5)

• .github/issues/issue-1-webgpu-fallback.md
• .github/issues/issue-2-pattern-data-pipeline.md
• .github/issues/issue-3-css-build-artifact.md
• .github/issues/issue-4-parser-timeout-ux.md
• .github/issues/issue-5-deployment-hygiene.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch cursor/github-issue-drafts-b9a1

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}