- 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
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
