docs(vault): fleet-wide fact re-verification pass (67 pages)

The docs-fact census wave re-read the live hosts and re-keyed every page
it could: runtime/payload identities, ports, sizes, ledger figures, unit
state, and the retirement banners that drifted as the fleet moved. The
wave was interrupted mid-run, so this commit carries only what passed the
integrity gates: every touched page parses (front matter or H1+status
convention intact, balanced fences, no truncated tables, trailing
newline), the docs_completeness and link-integrity seams are green, and
bats is 384/384.

Numbers that this session proved on live hosts are keyed to the measured
value, not the page's earlier claim.

serverAppConfigs-docs/Agent/OMP Harness.md

@@ -3,7 +3,7 @@ type: reference
 title: OMP Harness
 description: The omp agent harness as configured on this fleet — compaction chain arithmetic, per-model sampler routing via compat.extraBody, and the static-preamble/skill-library audits that keep session context lean.
 tags: [omp, harness, compaction, models-yml, context, samplers]
-timestamp: 2026-10-05T00:00:00-07:00
+timestamp: 2026-10-18T00:00:00Z
 ---
 
 # OMP Harness
@@ -25,6 +25,10 @@ picker/grants, the homepage docs and the raw API all use one id per model
 (see [[OpenWebUI]] for the grant re-key and the [[frank-archon-radiance-swift15-w4dn8]]
 note on radiance echoing the requested name).
 
+Verified 2026-10-18: `/v1/models` on 192.168.0.235:7770, 192.168.0.143:7770 and
+192.168.0.143:7771 each answer with the unit name (`frank-archon`,
+`frank-dragoon`, `frank-zealot`).
+
 ## Compaction chain arithmetic (verify before ANY window change)
 
 When a fleet endpoint's context grows past its harness-declared window, OMP
@@ -35,27 +39,40 @@ breaks compaction.
 
 Where the contract lives:
 
-- `~/.omp/agent/config.yml` → `compaction.remoteEndpoint` (target URL),
-  `methodOrder`, `thresholdPercent` (70), idle settings
+- `~/.omp/agent/config.yml` → `compaction.remoteEndpoint` (target URL:
+  `http://192.168.0.143:7771/v1/chat/completions`, `config.yml:76`),
+  `methodOrder` (`shake → snapcompact → soft → handoff → remote`,
+  `config.yml:77-82`), `thresholdPercent` (**95**, `config.yml:84`), idle
+  settings (`idleEnabled`, `idleThresholdTokens: 100000`)
 - `~/.omp/agent/models.yml` → per-model `contextWindow`, `maxTokens`,
   `compactionModel` references
-- Implementation: omp plugin `dist/core/compaction/compaction.js`
+- Implementation: omp plugin
+  `~/.omp/plugins/node_modules/@earendil-works/pi-coding-agent/dist/core/compaction/compaction.js`
 
 The arithmetic (the coupled contract every endpoint's maxTokens comment
-encodes):
+encodes). Recomputed from the live files 2026-10-18 — contextWindows
+200,000 (archon) / 155,648 (dragoon) / 200,704 (zealot) at
+`models.yml:48,131,206`; maxTokens 16,384 / 45,056 / 16,384 at
+`models.yml:56,143,212`:
 
-1. **Source trigger** = `thresholdPercent × source contextWindow`
-   (0.70 × 200,704 = 140,492 for frank-archon on the current shape)
-2. **Output budget** = capped at the target model's `maxTokens`
-   (32,768 for frank-zealot; 36,864 frank-archon; 57,344 frank-dragoon — the
-   largest, because halogen's `HALOGEN_MAX_TOKENS_CAP` must stay ≥ it)
+1. **Source trigger** = `thresholdPercent × source contextWindow`; at the live
+   95 % that is 190,000 (archon), 147,866 (dragoon), 190,669 (zealot). The
+   bundle clamps the percentage to 1–99 and converts it to a token threshold.
+2. **Output budget** = capped at the target model's `maxTokens` — every role
+   here compacts to frank-zealot, so the budget is its 16,384.
 3. **REQUIREMENT**: prompt (≤ trigger) + budget ≤ the target's per-slot
-   window. Worked pairs from the live registry: 140,492 + 36,864 = 177,356 ≤
-   200,704 (frank-archon); 140,490 + 57,344 = 197,834 ≤ 200,700
-   (frank-dragoon); 140,492 + 32,768 = 173,260 ≤ 200,704 (frank-zealot).
+   window. **At 95 % this no longer holds**: 190,000 + 16,384 = 206,384 >
+   200,704. The registry's own comments design around an 85 % trigger (archon:
+   170,000 est × 1.03 + 16,384 ≈ 191,500 ≤ 200,704, `models.yml:49-56`), which
+   does hold. While `config.yml` and those comments disagree, treat 85 % as the
+   design point and re-run this arithmetic after ANY window change — a 400 from
+   the compaction target mid-conversation is the symptom.
+   (Historic 2026-10-05 pairs, at `thresholdPercent: 70`: 140,492 + 36,864 =
+   177,356 ≤ 200,704 archon; 140,490 + 57,344 ≤ 200,700 dragoon; 140,492 +
+   32,768 ≤ 200,704 zealot.)
 
 Procedure (recompute from the LIVE files every time — windows rotate with
-every swap; the numbers above are the 2026-10-05 state):
+every swap; the block above is the 2026-10-18 state):
 
 1. Read the `config.yml` compaction block + `models.yml` entries for source
    and target. Every endpoint's `contextWindow` comment carries its own
@@ -76,15 +93,22 @@ Known reconciliation trap: comments in models.yml have described compaction
 as running "on the dankserver endpoint" while `remoteEndpoint` pointed at
 dankclaw — the comment/config disagreed. The comments now name the real
 target (`compaction.remoteEndpoint` = dankclaw :7771). **The config is
-truth; fix comments in the same change.** `maxTokens` never changes for a
-reslice — it caps output; `contextWindow` caps input. Boot-shape OOM
-laddering is a different problem ([[Llama Cpp Serving Sizing]]).
+truth; fix comments in the same change.** A fresh instance of the same trap is
+open 2026-10-18: every `maxTokens` comment still says "compaction fires at
+85 % of the window" while `config.yml:84` sets `thresholdPercent: 95`.
+`maxTokens` never changes for a reslice — it caps output; `contextWindow` caps
+input. Boot-shape OOM laddering is a different problem
+([[Llama Cpp Serving Sizing]]).
 
 ## Per-model sampler config (`compat.extraBody`)
 
-`models.yml` has **no per-model sampler keys**. Sampling is global
-(`config.yml`: `temperature`, `topP`, `topK`, `minP`, `presencePenalty`,
-`repetitionPenalty`; default `-1` = **not sent**). The per-model hook is
+`models.yml` has **no per-model sampler keys**. The global knobs are
+`config.yml`'s `temperature`, `topP`, `topK`, `minP`, `presencePenalty`,
+`repetitionPenalty`, and a knob reaches the wire only when it is set — the
+bundle guards each one with `!== void 0` (e.g. `minP!==void 0)e.min_p=t.minP`),
+and this workstation's `config.yml` sets **none** of them. The 2026-10-05 note
+that the unset default is `-1`/"not sent" is retired: there is no `-1`
+sentinel, an unset key is simply absent. The per-model hook is
 `compat.extraBody`:
 
 **Why it works:** `applyOpenAIExtraBody` runs **last** in the
@@ -117,15 +141,23 @@ Use **wire names**, not OMP camelCase. Two traps:
 2. **Never put `chat_template_kwargs` in `extraBody`** where a compat policy
    also sets it — `Object.assign` is shallow and replaces the whole object,
    silently dropping the `reasoning_effort` kwarg the compat policy set.
-   Top-level `preserve_thinking` is honoured by halogen. (frank-archon's
-   FreeToken entry currently carries a `chat_template_kwargs` extraBody with
-   a comment asking to verify-and-prune — the exact trap to check at that
-   endpoint's next swap.)
+   Top-level `preserve_thinking` is honoured by halogen. Live state 2026-10-18:
+   frank-archon's radiance entry carries `chat_template_kwargs:
+   {enable_thinking, preserve_thinking}` in `extraBody` (`models.yml:89-91`)
+   and nothing else sets that object at that endpoint, so the shallow-merge
+   hazard is latent rather than firing; the FreeToken-era "verify-and-prune at
+   the next swap" note is retired with that swap (2026-10-05,
+   `scripts/serve-frank-archon.sh:9-10`).
 
-**Gotcha: silent greedy decode.** halogen has **no server-side sampler
-defaults** — `temperature` absent or `0` = greedy. If OMP sends nothing, the
-endpoint decodes greedy while looking configured. This is why frank-dragoon's
-entry carries the recipe on the wire and a comment saying "do not drop it".
+**Gotcha (retired 2026-10-17): silent greedy decode.** Earlier flash-server
+builds carried **no server-side sampler defaults**, so an absent
+`temperature` decoded greedy while the endpoint looked configured. That era is
+over: `HALOGEN_TEMPERATURE/TOP_P/TOP_K` now set the card's thinking recipe
+(1.0 / 0.95 / 20) as engine defaults (`scripts/frank-dragoon.env:98-103`,
+exported at `scripts/serve-frank-dragoon.sh:186-188`), so an absent temperature
+is no longer greedy. frank-dragoon's `extraBody` still carries the same trio —
+consistent, not load-bearing. Treat any older "do not drop it or you get
+greedy" wording as history.
 
 **Reasoning-effort folding.** Qwen3.8's template accepts only
 `{xhigh (default), medium, low}` for `reasoning_effort` and 400s on anything
@@ -169,7 +201,7 @@ never `rm`.
 What loads statically every session (measure each, don't guess):
 
 1. Repo rules file — `wc -c AGENTS.md` (baseline 2026-10-05: 72,179 B, ~18k
-   tokens — historically the largest block).
+   tokens — historically the largest block; re-measured 2026-10-18: 89,723 B).
 2. Skill index — only names+descriptions load; bodies are on-demand. Sum
    description bytes across all SKILL.md frontmatter:
    ```bash
@@ -186,7 +218,8 @@ What loads statically every session (measure each, don't guess):
    EOF
    ```
    Baseline 2026-10-05: 171 managed skills / ~38 KB descriptions + 9 user
-   skills.
+   skills. Re-measured 2026-10-18 with the same glob: **87** managed
+   `SKILL.md` + 9 user skills — the dedupe happened.
 3. Memory lessons — `find ~/.omp/agent/memories -name 'MEMORY.md' -o -name
    'memory_summary.md' | xargs wc -c`. The injected block ≈ the largest
    MEMORY.md.
@@ -231,6 +264,9 @@ The static-context budget (measured 2026-10-05):
 | Learned-lessons block | ~14 KB | can contain corrupted/duplicate captures |
 | Harness system prompt + tool schemas | ~23 KB | fixed |
 
+Re-measured 2026-10-18: the skill library is down to 87 managed skills, but
+`AGENTS.md` has grown to 89,723 B — the dedupe landed, the slimming did not.
+
 Audit procedure:
 
 1. Build an inventory: per skill, name, mtime, body word count, description,