docs(runicnpc): example outfits and full durability (D323, D324)

Decisions from the 9d player walk, 2026-10-09: each example profile wears its own
outfit, and the example kits' items are written at full durability read from the
item definitions. API.md's note on the example kits says both.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY

runicnpc/API.md

@@ -403,7 +403,8 @@ route is walked back and forth. An NPC joins the route at its nearest point.
 - `data/RunicNPC/state.json` (API 5): `examplesWritten`, set on the first load. That load writes the four example
   kits (`rnpc_raider`, `rnpc_campguard`, `rnpc_sniper`, `rnpc_juggernaut`) into Kits' own data file, each where
   its name is free and each needing the permission `kits.runicnpc` (Kits' prefix, since Kits registers it), which nobody is granted, so no player can
-  claim one. On a server no site manages it also adds the four example profiles (`raider`, `campguard`, `sniper`,
+  claim one. Each wears its own outfit (D323), and every item is written at this Rust's full durability for it
+  (D324). On a server no site manages it also adds the four example profiles (`raider`, `campguard`, `sniper`,
   `juggernaut`). Then it reloads Kits, which reloads RunicNPC with it. **Nothing is written again, even if you
   delete them** (D280, D284, D289).
 - **A Kits reload reloads RunicNPC** on both frameworks, because RunicNPC requires Kits, and the NPCs it had spawned