Parent: #142 Depends on: #262 Roadmap: #134
Implement pinned exception-handling and tail-call profiles with exact JS/Wasm boundaries.
Acceptance:
- Pin exact proposal revisions and opcode/type inventories.
- Implement decoding, validation, execution, traps/unwinding, tags/exceptions, and tail-call stack behavior.
- Preserve JavaScript exception identity and WebAssembly exception typing across imports/exports.
- Keep tail calls stack bounded and compatible with precise GC roots.
- Publish upstream profile totals with no hidden exclusions.
Child issue map
- #288 — tail-call opcode/file inventory, decoding, and validation
- #289 — bounded tail-call execution frames and precise GC roots
- #290 — exception tags, binary IR, validation, and core unwinding
- #291 — JavaScript Tag/Exception API and cross-boundary identity
- #292 — exact upstream corpora, bounded CI, host matrix, and terminal evidence
Implementation order
#288 precedes #289, and #290 precedes #291. The tail-call and exception tracks may proceed independently once their inventories lock the exact pinned revisions. #292 closes only after all four implementation slices are complete and every declared upstream command has an explicit execution mode and result.