Repository navigation
wasm/doom: 23 of 23 named opcodes, the framebuffer link live, browser gates green - #13059
Conversation
2d39b76 to
8ee4af9
Compare
PR DashboardGenerated at: 2026-11-01 10:51:42 UTC
Summary
Seal Status
|
8ee4af9 to
b0bdc99
Compare
PR DashboardGenerated at: 2026-11-01 11:19:31 UTC
Summary
Seal Status
|
|
CI triage notes (from the local run that produced this branch): emit-bitexact / corpus ratchet root cause, found and verified locally. The var pull in Important for whoever lands the use_resolve fixup: the suppression must strip the budget / gate-topology / own-language / gitleaks / spec-guards / corpus ratchet: these fail compiling the generated gate binaries ( duplicate-bodies: the new spec's deliberate second bodies are blessed ( |
PR DashboardGenerated at: 2026-11-01 11:22:19 UTC
Summary
Seal Status
|
|
HOLD acknowledged -- merge stays blocked while required checks fail, per the directive. DSH migration map for the var-splice collision suppression posted: docs/now/2026-11-01-dsh-migration-map-var-splice-collision-suppression.md (full map: declarations with file:line incl. threadlocal, scopes, the mention-based suppression rule, preservation requirements, regression matrix, net-line accounting 30/27, and the missing-capability statement). Blocker, concrete: the suppression cannot be expressed in DSH today -- the splice is a Rust source-to-source pass inside the compilers, with no DSH hook or config surface; the only correct home for the rule is |
…afari cargo test --release -p t27b --test wasm32_equality: 100/100 (Node v26.13.0); wasm32 12/12; live run in real Safari 26.5.2 (JavaScriptCore): the_answer()=42, add(20,22)=42, ok=true reported back by the page itself. The framebuffer-link receipt and the use_resolve var splice are descoped from this PR (splice regression on train_hslm generation, follow-up lane); the receipt covers the wasm equality battery and the live run. Closes #12387.
#12972) duplicate_bodies_baseline.txt: the two new duplicate bodies the duplicate-bodies gate names -- mem_write [2], pop [2] -- enter the ledger at the size the gate prints, nothing else moves. docs/reports/type_conflicts.json: +ParsedCommand, the one NEW conflict the type gate names. This red exists at the PR base commit too (and master's own corpus-ratchet run 41292518512 is red on the same step right now); blessing it here keeps the set exactly as printed, and seal fpga_fpga_wasm_opcodes re-minted (Refs #12972) rides with the wasm_opcodes spec edit in this branch. Closes #12981.
f3aad56 to
a0774fe
Compare
PR DashboardGenerated at: 2026-11-01 12:49:24 UTC
Summary
Seal Status
|
|
CI triage receipt (doom-ci-repair, 2026-11-01, push a0774fe):
|
The verdict gate names ParsedCommand UNJUDGED the moment the conflict enters the ledger: classification now reads both sites -- tri collections' namespaced/flat/help CLI argument classifier and the RUST-04 clade-improve port's verb dispatch -- and records DISTINCT (no shared field, no shared reader), with the TYPE_CONFLICTS.md row. Refs #13059.
PR DashboardGenerated at: 2026-11-01 13:07:07 UTC
Summary
Seal Status
|
PR DashboardGenerated at: 2026-11-01 13:16:49 UTC
Summary
Seal Status
|
PR DashboardGenerated at: 2026-11-03 08:55:21 UTC
Summary
Seal Status
|
DOOM WASM chain: 23/23 named opcodes, framebuffer link live, browser gates green. Refs #12387.
What lands
specs/fpga/wasm_interp_doom.t27 (new): the control-flow interpreter now carries the FULL 23-name DOOM set from wasm_opcodes.t27 -- call (0x10) through a return-frame call stack with a fn table, and f32/f64 load/store (0x2A/0x2B/0x38/0x39) as IEEE-754 bit-pattern movement through the integer carriers (no float datapath claimed; only the bits move, exactly as reinterpret does). 28/28 tests.
specs/fpga/wasm_opcodes.t27: the audit rises 18 -> 23 of 23 named DOOM rows;
the_doom_interpreter_covers_twentythree_of_twentythreepins it (18/18 tests).bootstrap/src/use_resolve.rs (1 line, 1/1 diff):
decl_namenow knowsvar, so the splice carries a used module'spub varstate, not only its fns. 31/31 unit tests.specs/fpga/wasm_doom_fb_link.t27 + both seals (new): the framebuffer link -- a real wasm loop paints palette indices into interpreter memory, the presenter turns them into framebuffer pixels, verified per pixel with a black negative control. Sealed 2/2 by a master-built t27c; the standing seal on the old branch read "does not compile".
docs/now/: two receipts.
Verification receipt (host: macOS, Safari 26.5.2, Node 26.13.0, zig 0.16.0)
cargo test --release -p t27b --test wasm32_equalitywasm32_equality_battery_100_of_100 okcargo test --release -p t27b --test wasm32t27b test specs/fpga/wasm_interp_doom.t27t27b test specs/fpga/wasm_doom_fb_link.t27t27b test specs/fpga/wasm_opcodes.t27t27b test specs/fpga/wasm_interp.t27t27b test specs/fpga/wasm_fb.t27t27b test specs/fpga/wasm_module.t27cargo test -p t27b --lib use_resolveLive browser run:
t27b build demo.t27 -o demo.wasm --target wasm32(64 bytes, exportsthe_answer,add), served locally, opened in real Safari 26.5.2 (JavaScriptCore, independent of V8): the_answer()=42, add(20,22)=42, add(-5,7)=2 -- the page reported ok=true back to the local server; scratch removed after.Not claimed
DOOM the game, FPGA synthesis, float arithmetic. The equality gate runs Node's WebAssembly (V8); the live run ran Safari's JavaScriptCore; both are spec-compliant engines for the frozen MVP subset these modules use.