#59 - wai-web: full JPEG-AI decode in wasm (decodeJpegAiFull) — re-land - Transaction-Science/open-standards

dcharlot commented

2026-08-25 17:12:03 -04:00

Owner

#56 reported merged but did not land on main (forge lost it in a rapid merge sequence). Re-landing: adds decodeJpegAiFull, verified byte-identical to native (sha256 dbc494a5…) and driving the live /jpegai full-image demo. Clean merge (neural_int.rs unchanged on main since the branch base, 0 conflicts).

Co-Authored-By: Claude Opus 4.8 [email protected]

#56 reported merged but did not land on main (forge lost it in a rapid merge sequence). Re-landing: adds decodeJpegAiFull, verified byte-identical to native (sha256 dbc494a5…) and driving the live /jpegai full-image demo. Clean merge (neural_int.rs unchanged on main since the branch base, 0 conflicts). Co-Authored-By: Claude Opus 4.8 <[email protected]>

dcharlot added 1 commit

2026-08-25 17:12:03 -04:00

wai-web: full JPEG-AI codestream→RGB decode in wasm (decodeJpegAiFull) a065082807

The whole byte-exact decoder (wai::jpegai_decode::decode) as a browser entry: 13
byte inputs (codestream + the model weight bundle from wai_jpegai_build_e2e_inputs.py
+ norm tables), returns the decoded RGB. Same integer decoder a native sink runs,
compiled to wasm32.

Verified in node: decodes test256 to 256x256 in ~8s and the RGB is byte-identical
to the native decode (sha256 dbc494a5…, the same digest the reconstruction-binding
test produced natively) — decode-equivalence across host and browser. The JS side
passes raw bytes; the wasm parses, so there is no JS-side double-parse. Drives the
full-image path of the /jpegai demo.

Co-Authored-By: Claude Opus 4.8 <[email protected]>

dcharlot merged commit 45a1df0838 into main

2026-08-25 17:12:07 -04:00

dcharlot referenced this pull request from a commit

2026-08-25 17:12:09 -04:00

wai-web: full JPEG-AI decode in wasm (decodeJpegAiFull) (#59)

Rows
Columns

wai-web: full JPEG-AI decode in wasm (decodeJpegAiFull) — re-land #59