It was a dead end. my new tentative solution is xcomp.

Memory mapping is a dead end too, solution has to be at a higher
level. xcomp is my new approach.

This makes IMMEDIATE affected by memory mappings.

This way, it can be affected by memory mappers.

All "stop pings" are now explicitly made at appropriate places. This
fixes a problem I've introduced in the last commit where RAM+ was
unexpectedly part of a stable ABI because of "HERE" usage in dummy.fs.

This system will, anyways, soon change because boot.bin and z80c.bin
will be built during the same process (but there's a bit of retooling
to do before I get there).

We refer to stable offset as direct numbers instead of offset to JTBL.
Simpler that way.

forth.asm under 1K lines!

Lifting ourselves by the bootstraps!

This limitation was becoming annoying...

The removal of the "divide" routine highlighted the fact that
nativeWord wasn't properly stabilized.