v4: init.4th and the ACL at call; the F18 ADR, ABI and artifact layout; ADR step 3 tasks 1-3 (mkf18a) #198

Open
rajames wants to merge 52 commits from StarForth-v4.0.0 into master
Showing only changes of commit 255dd92deb - Show all commits
@@ -116,6 +116,14 @@ ADR step 8 asks. The boot gains nothing.
there is no list to keep. As asked: Captain Bob's image is "the .f18 assembler assembles all .f18 files it
finds", but the order matters: the map first, `sys_files.h`'s list, `end.f18` last. Does each train
name its order in a list, as `sys_files.h` does, or does the tool take the files in name order?
**3a, ruled 2026-11-19: "Nucleus too: rename".** Asked whether name order applies to the nucleus,
which is read in `sys_files.h`'s order: it does. `capsules/v4/sys` is renamed so that its name order is
today's order, the map first and `end.f18` last (`00-map`, `01-core`, ... `99-end`), and `sys_files.h`
goes. The boot, the tests and the ROM's feed read the directory in name order. The blob names and the
capsule hashes change, so the protocol runs again. This is a task of its own, designed and tested
first. One point for its design: the directory holds both widths' maps, `map-32.f18` and `map-64.f18`,
and name order would take both.
4. **Which words are exports.** The nucleus defines hundreds of words, and some have no fixed effect, which
2c refuses as exports. Is every word with a fixed effect exported, or only those a list names? With a
list, the words outside it stay internal.