Resolve call-script dispatch: id = raw SYS4INI file index

Native-RE (Ghidra) cracked call-script <id> (opcode 0x03): its handler
FUN_0041bc90 -> loader FUN_0040e980 -> resolver FUN_0044f390 indexes an
80-byte record table at base + id*0x50 == the SYS4INI record layout. So
`call-script <id>` is a direct RAW index into the SYS4INI global file
table (the asset index we already parse) -- there is no separate on-disk
id->code registry. This resolves name-resolution.md #1, statically, no
Frida.

Confirmed: all 297 distinct corpus call-script ids resolve to a .BIN
script with a semantically-exact name (0x1ab->ADDITEM, 0x2ae7->MES,
0x143->BUNKI, 0x329d->CALCREVISE), 0 out-of-range, 0 alternate-pack.
Companion op 0x8f `call` is an intra-script JSR (FUN_0041fba0), not
cross-script.

- parse_sys4ini.py: preserve `raw_index` per entry (= the engine file id;
  index the RAW records incl. '@' placeholders) + emit
  build/callscript-names.json (id->name).
- sys4load.py: annotate `call-script 0x1ab =ADDITEM.BIN`.
- opcodes.toml 0x03/0x8f refined (source=investigation, confidence high,
  handler VAs) + rebuilt opcode-reference.md.
- docs: engine-re.md (op 0x03 section + backlog re-aimed),
  name-resolution.md #1 (SOLVED), script-inventory.md (call graph +
  living-reference decision), tools-reference.md.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

docs/script-inventory.md

@@ -95,6 +95,25 @@ outside scenes lives.
 
 ---
 
+## Call graph — scripts are addressable by `call-script <id>` (2026-07-07)
+
+`call-script <id>` (opcode 0x03) loads another script by a **raw index into the SYS4INI file table**
+(id = the entry's `raw_index` = its global position in SYS4INI). This is the resolved call-graph
+registry — there is no separate id→code table; SYS4INI is it. Mechanism: `engine-re.md` (op 0x03
+section); id→name single source: `build/callscript-names.json` (from `parse_sys4ini.py`); `sys4load`
+and the regenerated `build/disasm/*.asm` corpus now render targets by name
+(`call-script 0x1ab =ADDITEM.BIN`). **297 distinct scripts are called** across the corpus (3002 sites);
+the hottest are `HISTORY` (backlog), `MENU`, `HIDEWIN`, `BUNKI` (branch), `MES` (message), `ADDITEM`,
+`ADDEN`, `LOOK`, `RENDERMAP`. Scenes (`SCxxxx.BIN`) load through the *same* id-indexed loader.
+
+**Living-reference decision:** no separate generated markdown call-script reference is kept. Unlike
+`opcode-reference.md` / `global-reference.md` (rendered from *curated* knowledge bases), the id→name
+mapping is purely mechanical (SYS4INI index → filename) with no semantics to curate — it already lives
+in the build artifact and in the named disasm corpus. Full call-graph edges (caller→callee counts) are
+derivable on demand from the corpus; materialize a doc only if a consumer needs it.
+
+---
+
 ## Implications for the port
 
 1. **Much more game logic lives in bytecode than expected.** Damage formulas