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 29b99f90e6 - Show all commits
@@ -5,7 +5,7 @@ existing build system". It builds on:
- `ABI.md`, ABI v0 as ruled, in particular choice 1, "A host tool";
- `ARTIFACT.md`, the layout as ruled.
**Nothing here is built.** The questions are in §6, put to Captain Bob one at a time.
**Nothing here is built.** The questions in §6 are ruled (2026-11-19).
## 1. What is there already
@@ -133,4 +133,15 @@ ADR step 8 asks. The boot gains nothing.
The same source gives the same hash on every host. As asked: The provenance holds "the host tool's hash". The hash of the binary differs
with the host's compiler. Should it be the hash of the tool's source (`mkf18a.c`, `text.c`, `effect.c`
and their headers), or of the binary?
6. **The name.** `mkf18a` and `.f18a`, after the magic, or something else?
6. ~~The name~~ **Ruled 2026-11-19: "mkf18a / .f18a"**, after the magic: `v4/tools/mkf18a.c`, and each
train's artifact `<train>.f18a`. As asked: `mkf18a` and `.f18a`, after the magic, or something else?
## 7. Status, and the order of the work
All six questions are ruled, plus 2a and 3a. Each task below is built test-first, seen to fail, and
accepted before the next:
1. `text.c`'s address record (§4, test 1), with `test_host_rom_nucleus` unchanged (test 4).
2. `effect.c`, the stack-effect analysis (test 2).
3. `mkf18a` and `make -C v4 artifacts` (test 3).
4. The small train, placed at a base other than 0 (test 5).
5. The nucleus renamed to name order (3a), designed first: it changes the boot, so the protocol runs.