`[2026-10-06]` gen-large contention: jekyll moved to sec-reasoning (Prime)

gen-large contention (2026-10-06 1432): the jekyll Hermes seat (nh3-dev, shared all-agents-local key) was sending 165–183k-token prompts every few seconds while Prime ran ~140k from his MacBook. flash-next's KV (344k tokens) overflowed: 539 → 819 preemptions, decode 2–16 tok/s, calls of 221–244 s. Prime moved jekyll to sec-reasoning (cyberprev, GPU 0) at ~1435. At 1439 gen-large was back to 90–143 tok/s with 1 running; sec had KV at 34% and 0 preemptions. ⚠ Watch: sec's KV is 337k tokens, so jekyll plus a long sec prompt (up to 192k) can overflow it too. jekyll's context grows ~1k/call toward the 262k ceiling. Heavier long-context traffic may grow cyberprev's footprint and eat GPU 0's ~2.3 GB spare; check at the 10-07/08 plateau review.
How it was found: LiteLLM spend logs for :8022 (two long-context clients interleaving: 10.100.10.166 Prime's MacBook ~134–141k, and 10.100.10.50 nh3-dev ~165–183k on all-agents-local), then ss -tnp on nh3-dev mapped the gateway connection to pid 124754, a Hermes process with ALTHING_HANDLE=jekyll in ~/development/jekyll. ~/.hermes/config.yaml defaults every Hermes seat to gen-large.
Engine view: KV 88–100%, preemptions 539 → 819, decode 2–16 tok/s against ~108 with one stream.

[2026-10-06] gen-large contention: jekyll moved to sec-reasoning (Prime)