Narrow WASM and EVM execution ports to file subjects and preserve supplied subject types at the shared execution factory. Authenticate format with path and digest before recording or projecting Evidence, using the existing WASM identity owner in both consumers. Validation: focused WASM/EVM service and public MCP workflows passed, including malformed provider subjects and self-contained retained Evidence with contradictory format. Global typecheck/lint and documentation checks passed. Real WABT/Evmole execution and the full suite were not run. |
||
|---|---|---|
| .. | ||
| README.md | ||
| artifact.ts | ||
| custom-names.wat | ||
| decoded.wat | ||
| module-names.wat | ||
| module.wat | ||
| objdump.txt | ||
README.md
WABT producer fixtures
module.wat is source-owned. WABT 1.0.42 wat2wasm module.wat -o module.wasm
produced the binary used for wasm-objdump -h -x module.wasm (objdump.txt) and
wasm2wat --enable-all module.wasm (decoded.wat). No binary is checked in.
The module has an imported function, exported memory/function and a test
custom section. The custom payload is retained as an @custom annotation in decoded WAT.
Upstream tag commit: ff0ef7e0009402740c805a9744c09b05be063e48.
The separate real-tool verifier generates its own fixtures with caller-supplied
WABT and compares exact producer output against the public CLI/MCP surfaces.
custom-names.wat covers newlines, quotes, Unicode, backslashes, embedded
section markers and NUL in custom names; objdump displays those names without
escaping and ends each at its first NUL.
It also covers leading U+FEFF, including a name distinct from the special name
section, and distinguishes a U+FEFF-only name from an empty name.