Skip to content

Fix starter callback and color failures with full browser acceptance - #173

Draft
proggeramlug wants to merge 3 commits into
codex/fixed-game-lifecyclefrom
codex/starter-browser
Draft

Fix starter callback and color failures with full browser acceptance#173
proggeramlug wants to merge 3 commits into
codex/fixed-game-lifecyclefrom
codex/starter-browser

Conversation

@proggeramlug

@proggeramlug proggeramlug commented Sep 11, 2026

Copy link
Copy Markdown
Contributor

The generated starter compiled for web but failed at runtime: named void callbacks reached Perry's i64 decoder as JavaScript undefined, and imported palette colors reached FFI with undefined RGBA channels. Preserve actual void returns in the production bootstrap while retaining the existing boxed-value decoder and its errors. Give the starter explicit typed black/white literals.

Require complete installed-starter browser acceptance. Windows creates the project through the installed CLI, runs unchanged source with bloom run --web, checks exact served bytes/MIME and retains the entire website with hashes. The scoped upload includes hidden files. Hosted Chrome loads that exact output through the production bootstrap and checks real asset fetch/read, clear/text/square arguments, eight frames, normal stop, one completed cleanup and the expected 800x450 image.

Validation:

  • Tests run 34578061311 passes all 22 jobs. The full starter browser capture has the expected black background, white square and 857 lit text pixels, with no recorded errors. All 11 website files match their build receipt.
  • The existing compiled-game browser frame and startup-fault control pass. Fresh installed native scene/direct-2D/lifecycle modes each pass all 16,384 expected pixels and one cleanup. Actual native/WASM named-hook and timing results agree, and all 20 examples compile/link.
  • Local corrected installed web execution, actual-WASM draw-argument checks and a bounded Radeon native starter render pass. The earlier named-void, omitted-hidden-file and non-finite-color failures remain retained.
  • The PR and hosted checkout have identical Git trees. Installed web/native reports preserve their dirty-source flags; eleven web and seven native reported installed sources match the PR with documented Windows newline/npm shebang conversion.

Published report and evidence contain raw results, source receipts, captures, earlier failures and the exact patch. ZIP SHA-256: 5a8e79c4373fc5f16950bd9204f9078fdfcd902814378a001b6cd20d99cd0caa.

General imported constant compatibility, canonical example browser/gameplay coverage, wider API/compiler qualification, browser physics, pause/focus, resize/device-loss handling and clean Windows distribution remain separate. Shared constant/example corrections are being qualified in #174. No PR merge or npm release is included.

Stacked on #172; relates to #142 and #74.

@coderabbitai

coderabbitai Bot commented Sep 11, 2026

Copy link
Copy Markdown

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

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

Comment @coderabbitai help to get the list of available commands.

@proggeramlug proggeramlug changed the title Fix named void callbacks and gate the complete web starter Fix starter callback and color failures with full browser acceptance Sep 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant