The Web leg of examples/portable is a boundary, and the linker says where it is

[Sunrisepeak]

The Web leg of examples/portable is a boundary, and the linker says where it is

openkal-emscripten 0.1.0 is in the index, so the Web line now resolves. It
does not build, and that is the mechanism rather than a gap.

Measured, with the dependency resolved and every translation unit compiled:

wasm-ld: error: obj/main.o: undefined symbol: kal_process_spawn
wasm-ld: error: obj/main.o: undefined symbol: kal_process_wait
wasm-ld: error: obj/main.o: undefined symbol: kal_process_close
wasm-ld: error: obj/main.o: undefined symbol: kal_task_start
wasm-ld: error: obj/main.o: undefined symbol: kal_task_join
wasm-ld: error: obj/main.o: undefined symbol: kal_task_wait
wasm-ld: error: obj/main.o: undefined symbol: kal_task_wake

Seven names, each one this program uses and this platform does not have. There
is no fork, no exec and no second address space under Emscripten, so
openkal.process, openkal.exec and openkal.space are absent from that
implementation -- and this program uses two of the three.

THE CRITERION WAS WRONG AND THE MEASUREMENT IS WHAT SAID SO. The design record
asked for this example to build "for all five platforms it names". It cannot,
and neither way of making it could is acceptable: #ifdef-ing the one file in
this ecosystem that exists to contain no platform awareness, or having
openkal-emscripten provide operations it cannot perform, which is the shape
clause 6.2 forbids -- present and always failing, which the caller cannot tell
from a condition.

So the line stays and the example is better for it. A program about
portability that also shows where portability stops is worth more than one that
stops at four platforms and says nothing about the fifth. The README and the
manifest carry the linker's own output as the evidence, and note that
openkal.task is a second question with the same answer here: the four
kal_task_* names resolve under that implementation's threads feature, and
the three kal_process_* names never will.

The other three legs are measured and unchanged: host 0 observations that did not hold, and both Android ABIs build over openkal-linux unchanged.