docs(runicnpc): stage 5 built, tested and walked; API 4; protocol 13 §19.13 #312

Merged
whitlocktech merged 2 commits from docs/runicnpc-stage5-built into main 2026-10-05 08:35:42 +00:00
Member

What

Merge #311 (D267–D272) first — this branch sits on it.

  • runicnpc/PLAN.md: stage 5 as built; three things the build found that the spike did not (Rust's CanSeeTarget is no line of sight for an NPC target; a destroyed escort target compares equal to null; a rocket's line of sight); the harness results on both rigs; the site walk and what it did not cover.
  • runicnpc/API.md: API 4.
  • rust-link/PROTOCOL.md §19.13: the faction table on npc.profiles/npc.profiles.set, world.place's escort, ally and tether, three new world.error reasons; the bridge needs RunicNPC API 4. Joins protocol 13 (D253).

PRs: runicnpc-rust, Rust-Plugins and Module-Rust (each into edge). Rust-Link and the installer need no change.

Checklist

  • I have read CONTRIBUTING.md.
  • Docs only.
  • AI tools were used. Tool(s): Claude Code (Claude Opus 5.5). The commits carry the Co-Authored-By trailer.
  • I agree that my contribution is licensed under GPL-3.0-or-later.

🤖 Generated with Claude Code

https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY

## What **Merge #311 (D267–D272) first** — this branch sits on it. - `runicnpc/PLAN.md`: stage 5 as built; three things the build found that the spike did not (Rust's `CanSeeTarget` is no line of sight for an NPC target; a destroyed escort target compares equal to null; a rocket's line of sight); the harness results on both rigs; the site walk and what it did not cover. - `runicnpc/API.md`: API 4. - `rust-link/PROTOCOL.md` §19.13: the faction table on `npc.profiles`/`npc.profiles.set`, `world.place`'s `escort`, `ally` and `tether`, three new `world.error` reasons; the bridge needs RunicNPC API 4. Joins protocol 13 (D253). PRs: runicnpc-rust, Rust-Plugins and Module-Rust (each into `edge`). Rust-Link and the installer need no change. ## Checklist - [x] I have read CONTRIBUTING.md. - [x] Docs only. - [x] AI tools were used. Tool(s): `Claude Code (Claude Opus 5.5)`. The commits carry the `Co-Authored-By` trailer. - [x] I agree that my contribution is licensed under GPL-3.0-or-later. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY
wtclaude added 2 commits 2026-10-05 06:17:43 +00:00
The org lead's answers to the six questions the stage 5 build raised
(2026-10-01): a Harmony patch for the safe-zone sentries under the
condition that it never reaches Rust's own scientists (D267), faction pairs
both ways and shooting back (D268), escort as an order that walks home
when the target is gone (D269), the event step's escort and ally (D270),
the PVE opt-out as two checkboxes (D271), and the tether on placements and
event steps rather than profiles (D272).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY
- runicnpc/PLAN.md: stage 5 as built, what the build found that the spike
  did not (Rust's CanSeeTarget is no line of sight for an NPC target; a
  destroyed escort target compares equal to null; a rocket's line of
  sight), the harness results on both rigs, and the site walk;
- runicnpc/API.md: API 4 (the faction table, escort, ally, tether, the
  profile's stage 5 fields, a placement's tether, OnRunicNpcEscortEnded,
  the new rows of RunicNpc_List, rnpc.faction, /rnpc follow, tether=);
- rust-link/PROTOCOL.md §19.13: the faction table on npc.profiles and
  npc.profiles.set, world.place's escort, ally and tether, the three new
  world.error reasons; the bridge needs RunicNPC API 4. Joins protocol 13
  (D253).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY
whitlocktech merged commit d32886f348 into main 2026-10-05 08:35:42 +00:00
whitlocktech deleted branch docs/runicnpc-stage5-built 2026-10-05 08:35:43 +00:00
Sign in to join this conversation.
No description provided.