docs(runicnpc): stage 8 built and walked; MODULE_API 1.12.0 progress(), map.live's RunicNPC rows #323
@@ -1517,7 +1517,7 @@ in the Android app.
|
||||
- `rust-link/PROTOCOL.md` §17.3.
|
||||
- The integration kit, read again and its pin moved.
|
||||
|
||||
**Built (2026-10-06), five branches and this one.**
|
||||
**Built (2026-10-06), six branches and this one.**
|
||||
|
||||
| Piece | Branch | What it does |
|
||||
|---|---|---|
|
||||
@@ -1553,8 +1553,13 @@ stood in for a player.
|
||||
for every event the editor authors. It has done so since Events Phase 14a; its test used an `id` fixture. A one-line
|
||||
fix in `eventPublic.model.js`, raised with the org lead rather than folded into website#210.
|
||||
|
||||
**Still to do when website#210 merges:** the integration kit's `ci/core-ref.json` pin moves to that sha, and its
|
||||
`coreApi` with it, after the kit is read again for 1.12.0.
|
||||
**The integration kit** (`Integration-kit` `docs/core-1.12.0`). website#210 merged as `0a37a44`, and the kit's pin
|
||||
moved there from 1.10.0, past 1.11.0, which it had skipped.
|
||||
|
||||
- Chapter 5 was read again for both versions and teaches `progress()` and `ctx.events.expired`.
|
||||
- The template's `coreApi` is `^1.12.0`.
|
||||
- Every kit check and template suite passed at the new pin, and the template registered in a real core of that
|
||||
code.
|
||||
|
||||
### Stage 9 — Hardening and release
|
||||
|
||||
|
||||
Reference in New Issue
Block a user