🦉 wiki audit 2026-10-21: gateway unclean-exit orphaned run (new), Gitea config-backup push dead since 2026-08-08 (new), model default → nous, 503 back to monitoring, canned-substitute trigger corrected

This commit is contained in:
Tony0410
2026-10-21 00:11:44 +08:00
parent fbd4f297eb
commit b662254569
10 changed files with 386 additions and 25 deletions
@@ -59,8 +59,34 @@ The delivered message, stored verbatim as the run's assistant output:
`custom:omni-101` alias family that produced the 2026-10-14 → 10-15 connection-refused storm and the
2026-10-16 → 10-17 resource-pressure 503 burst. Single-node topology unchanged.
- **Second recorded surface: an interactive session, 2026-10-20 18:37 AWST — and a different guard fired.**
Session `20261020_183748_6d40ea` (`source: desktop`, `model: minimax/minimax-m3.1-flash:free`, 2 messages,
0 tool calls, `end_reason: agent_close`) holds **one user question** — *“i want to use the nous oauth dashboard
aut for this gateway how do i do that. can i also set up a gateway token of …”* — and one assistant reply: the
**identical canned substitute**. The turn-end log names the trigger:
`Rebuilt-message restart limit (3) exceeded; ending turn instead of refunding the iteration budget
indefinitely.` → `reason=rebuilt_restart_limit_exceeded model=qwen3.5:397b api_calls=1/150 tool_turns=0
response_len=0` (single occurrence in the retained logs). **No incident row was created** — the ledger relays
*cron* failures only, so a user's unanswered question never enters it. **The question itself was never
answered** → [[current-state]].
- **Open:** whether the canned sentence should be **suppressed** for interactive sessions (where the user is
present and would rather see the real error) while kept for cron (where silence looks like success).
## Recurrence 2026-10-20 (interactive desktop session, rebuild-limit path)
Same visible outcome — a canned non-answer persisted as the assistant's reply — reached by **two routes on the
same day**: the 2026-10-18 cron path (repetition-loop guard) and, on 2026-10-20 18:37, the **rebuilt-message
restart limit**: the conversation loop rebuilt the message list three times, gave up, and ended the turn with
`response_len=0`, leaving the canned line as the only thing the user saw. Correlation with the same-day provider
change is **not established** — the session's own pin was `minimax/minimax-m3.1-flash:free`, while the turn-end
line names `model=qwen3.5:397b`; the two disagree and the audit cannot resolve which model the failing API call
actually went to. The **durable conclusion holds regardless: the canned substitute is emitted by the harness's
failure path generally**, not only by the repetition-loop guard. It is a delivery-integrity problem, not a
stream-parser one.
## Related
- [[systems/scheduled-tasks]]
- [[systems/current-profile]]
- [[incidents/2026-10-16-omniroute-503-resource-pressure]]
- [[incidents/2026-10-14-omniroute-node-connection-refused-storm]]