omnius 1.0.848 → 1.0.850

package/docs/DISCOVERY.md

@@ -455,6 +455,7 @@ Daemon equivalents are `GET /v1/discovery/bootstrap`, `GET /v1/discovery?q=<inte
 | `guide.guides-tui-workflows` | TUI Workflows | The TUI is the primary Omnius control surface for interactive use. |
 | `guide.handoff-crl-encoder-decoder-fix-uppercase` | HANDOFF: CRL Encoder/Decoder Bidirectional Fix | Date: 2026-04-22 Status: Needs Implementation Failing Test: packages/memory/tests/crl-converter.test.ts - "should validate roundtrip accuracy" |
 | `guide.index` | Omnius Documentation | Omnius is an autonomous local-first agent runtime with a TUI, REST daemon, P2P sponsor mesh, Telegram bridge, realtime conversation mode, media generation routes, and AIWG-compatible documentation skills. |
+| `guide.inference-fallback-priority` | Inference fallback priority | Local inference remains first. After a qualifying local failure and any required manual approval, the remote cascade uses these stages: |
 | `guide.keyless-provider-survey` | Keyless provider survey | Reviewed 2026-10-12. Discovery used public primary documentation and metadata. Live probes contained small synthetic prompts, never private conversation or repository context, and executed no tools. The complete sanitized survey is recorded with the keyless fallback work order. |
 | `guide.longhaul-35b-workorders` | Work Orders — Long-Haul Implementation on a 35B-Class Model | Origin: Root-cause review of the myactuator ESP32/PlatformIO session (35B ornith-vision) plus a 2026-literature sweep of surprising remedies. See companion analysis in docs/context-management-medium-models-proposal.md and docs/duplicate-calls-root-cause-analysis.md. |
 | `guide.memory-integration-analysis` | Memory Integration Analysis — Parallel Systems Gap Assessment | Date: 2026-04-23 Status: ✅ INTEGRATED — All P0 gaps closed Context: Review of literature on memory compression + integration testing of Omnius parallel memory systems |
@@ -522,13 +523,27 @@ Daemon equivalents are `GET /v1/discovery/bootstrap`, `GET /v1/discovery?q=<inte
 | `guide.voice-flow-architecture` | Voice TTS Flow — Architecture &amp; Implementation Guide | This document describes the voice synthesis system in omnius: how it's built, how all the pieces connect, and how to add new voice features following the same patterns. |
 | `guide.work-orders-active-inference-route-remote-probes-20261012` | Active Inference Route Remote Probes 20261012 | Bundled Omnius documentation artifact: docs/work-orders/active-inference-route-remote-probes-20261012.json. |
 | `guide.work-orders-daemon-hud-ui-overhaul` | Daemon HUD UI Overhaul Work Order | Overhaul the daemon web interface using /home/roko/Desktop/hud-ui-style-kit(6)/hud-ui-style-kit as the source of truth. Preserve current daemon behavior while replacing the OpenWebUI-like rounded dashboard styling with the cold tactical HUD visual system. |
+| `guide.work-orders-evidence-fallback-model-benchmarks-20261012` | Fallback Model Benchmarks 20261012 | Bundled Omnius documentation artifact: docs/work-orders/evidence/fallback-model-benchmarks-20261012.json. |
+| `guide.work-orders-evidence-fallback-quality-installed-20261012` | Fallback Quality Installed 20261012 | Bundled Omnius documentation artifact: docs/work-orders/evidence/fallback-quality-installed-20261012.json. |
+| `guide.work-orders-evidence-fallback-reply-contracts-installed-20261012` | Fallback Reply Contracts Installed 20261012 | Bundled Omnius documentation artifact: docs/work-orders/evidence/fallback-reply-contracts-installed-20261012.json. |
 | `guide.work-orders-evidence-installed-fallback-verification-20261012` | Installed Fallback Verification 20261012 | Bundled Omnius documentation artifact: docs/work-orders/evidence/installed-fallback-verification-20261012.json. |
 | `guide.work-orders-evidence-keyless-compatibility-20261012` | Keyless Compatibility 20261012 | Bundled Omnius documentation artifact: docs/work-orders/evidence/keyless-compatibility-20261012.json. |
 | `guide.work-orders-evidence-keyless-provider-survey-20261012` | Keyless Provider Survey 20261012 | Bundled Omnius documentation artifact: docs/work-orders/evidence/keyless-provider-survey-20261012.json. |
 | `guide.work-orders-evidence-kilo-production-compatibility-20261012` | Kilo Production Compatibility 20261012 | Bundled Omnius documentation artifact: docs/work-orders/evidence/kilo-production-compatibility-20261012.json. |
+| `guide.work-orders-evidence-native-conversation-prompt-audit-20261012` | Native Conversation Prompt Audit 20261012 | Bundled Omnius documentation artifact: docs/work-orders/evidence/native-conversation-prompt-audit-20261012.json. |
+| `guide.work-orders-evidence-native-goal-contract-probe-20261012` | Native Goal Contract Probe 20261012 | Bundled Omnius documentation artifact: docs/work-orders/evidence/native-goal-contract-probe-20261012.json. |
+| `guide.work-orders-evidence-opencode-all-free-audit-20261012` | Opencode All Free Audit 20261012 | Bundled Omnius documentation artifact: docs/work-orders/evidence/opencode-all-free-audit-20261012.json. |
+| `guide.work-orders-evidence-opencode-all-free-installed-verification-20261012` | Opencode All Free Installed Verification 20261012 | Bundled Omnius documentation artifact: docs/work-orders/evidence/opencode-all-free-installed-verification-20261012.json. |
+| `guide.work-orders-evidence-opencode-installed-production-stream-live-20261012` | Opencode Installed Production Stream Live 20261012 | Bundled Omnius documentation artifact: docs/work-orders/evidence/opencode-installed-production-stream-live-20261012.json. |
+| `guide.work-orders-evidence-opencode-production-cascade-live-20261012` | Opencode Production Cascade Live 20261012 | Bundled Omnius documentation artifact: docs/work-orders/evidence/opencode-production-cascade-live-20261012.json. |
 | `guide.work-orders-evidence-opencode-production-compatibility-20261012` | Opencode Production Compatibility 20261012 | Bundled Omnius documentation artifact: docs/work-orders/evidence/opencode-production-compatibility-20261012.json. |
+| `guide.work-orders-evidence-opencode-production-pre-recovery-live-20261012` | Opencode Production Pre Recovery Live 20261012 | Bundled Omnius documentation artifact: docs/work-orders/evidence/opencode-production-pre-recovery-live-20261012.json. |
+| `guide.work-orders-evidence-opencode-step-rate-limited-diagnostic-20261012` | Opencode Step Rate Limited Diagnostic 20261012 | Bundled Omnius documentation artifact: docs/work-orders/evidence/opencode-step-rate-limited-diagnostic-20261012.json. |
 | `guide.work-orders-evidence-ovh-production-compatibility-20261012` | Ovh Production Compatibility 20261012 | Bundled Omnius documentation artifact: docs/work-orders/evidence/ovh-production-compatibility-20261012.json. |
 | `guide.work-orders-evidence-ovh-structured-context-compatibility-20261012` | Ovh Structured Context Compatibility 20261012 | Bundled Omnius documentation artifact: docs/work-orders/evidence/ovh-structured-context-compatibility-20261012.json. |
+| `guide.work-orders-evidence-terminal-review-contract-probe-20261012` | Terminal Review Contract Probe 20261012 | Bundled Omnius documentation artifact: docs/work-orders/evidence/terminal-review-contract-probe-20261012.json. |
+| `guide.work-orders-evidence-terminal-review-error-probe-20261012` | Terminal Review Error Probe 20261012 | Bundled Omnius documentation artifact: docs/work-orders/evidence/terminal-review-error-probe-20261012.json. |
+| `guide.work-orders-evidence-terminal-review-schema-repair-probe-20261012` | Terminal Review Schema Repair Probe 20261012 | Bundled Omnius documentation artifact: docs/work-orders/evidence/terminal-review-schema-repair-probe-20261012.json. |
 | `guide.work-orders-hermes-architecture-deltas-01-public-scrutiny-provenance-control-index-uppercase` | Public Scrutiny Provenance Control Index | Bundled Omnius documentation artifact: docs/work-orders/hermes-architecture-deltas/01-public-scrutiny-provenance-control/INDEX.md. |
 | `guide.work-orders-hermes-architecture-deltas-01-public-scrutiny-provenance-control-workorder-uppercase` | Workorder: Public Scrutiny Provenance Control | Add a public Telegram scrutiny control plane that can elevate completion provenance checks when public accuracy risk rises, without hard-coded scenario phrases or shortcut wording that teaches the model to satisfy the gate without evidence. |
 | `guide.work-orders-hermes-architecture-deltas-02-context-engine-plugin-boundary-index-uppercase` | Context Engine Plugin Boundary Index | Bundled Omnius documentation artifact: docs/work-orders/hermes-architecture-deltas/02-context-engine-plugin-boundary/INDEX.md. |
@@ -652,12 +667,17 @@ Daemon equivalents are `GET /v1/discovery/bootstrap`, `GET /v1/discovery?q=<inte
 | `guide.work-orders-telegram-reliability-consolidation-2026-09-28` | Telegram Reliability Consolidation — 2026-09-28 | Rule: check a box only after the named behavior is implemented and its listed verification passes. A parent box stays open until every child box is checked. |
 | `guide.work-orders-wo-active-inference-route-and-telegram-review-20261012-uppercase` | Active inference route and Telegram completion review | Status: implementation complete and verified. Publication remains with the user. |
 | `guide.work-orders-wo-am-gaps-uppercase` | Associative Memory Gap Work Orders | Generated: 2026-04-13 Source: Deep audit of multimodal associative memory systems Status: READY FOR IMPLEMENTATION |
+| `guide.work-orders-wo-fallback-quality-order-20261012-uppercase` | Benchmark-informed fallback cascade | Status: implemented and verified. Publication and active runtime replacement remain with the user. Telegram progress presentation stays deferred. |
+| `guide.work-orders-wo-fallback-reply-contracts-20261012-uppercase` | Fallback reply contracts and live Telegram regressions | Status: implemented and verified in source and the freshly installed package. Publishing and restarting the active bot remain user-owned. The subsequent OpenCode-first capability ordering is tracked in its work order; Telegram progress presentation remains explicitly deferred. |
 | `guide.work-orders-wo-inference-fallback-20261012-uppercase` | Local inference outage fallback | Status: source implementation complete and verified. Installed-runtime activation is separate; the running daemon has not been upgraded or restarted. |
 | `guide.work-orders-wo-keyless-fallback-coverage-20261012-uppercase` | Keyless automatic fallback coverage and compatibility | Status: implemented and verified. Publication and replacement of the running bot remain user-owned; the running bot has not been restarted by this work. |
 | `guide.work-orders-wo-native-transport-fresh-install-20261012-uppercase` | Native transport failure in the fresh npm installation gate | Status: implemented and verified. Publication remains with the user. |
+| `guide.work-orders-wo-opencode-all-free-models-20261012-uppercase` | All OpenCode free models in the fallback cascade | Status: implemented and verified. Publication and runtime replacement remain with the user. The subsequent live-reply fixes are tracked separately in fallback reply contracts. The original preferred-first/provider-fairness ordering recorded below has been superseded by benchmark-informed priority at the user's subsequent request. |
+| `guide.work-orders-wo-opencode-production-compatibility-20261012-uppercase` | OpenCode production request compatibility | Status: implemented and verified. Telegram presentation is also completed. Publication and active-runtime restart remain with the operator. Step's native attention-format compatibility remains unverified after a provider limit; the working cascade can continue to other compatible models. |
 | `guide.work-orders-wo-primary-checkout-fallback-delivery-20261012-uppercase` | Primary checkout delivery and remote output capacity | Status: implementation complete and verified in the primary checkout. Publication remains with the user. |
 | `guide.work-orders-wo-telegram-fallback-20261012-uppercase` | Telegram outage fallback and user-selected approval mode | Status: implementation complete; distributable verification recorded below. Publication and runtime installation are reserved for the user. |
 | `guide.work-orders-wo-telegram-plain-answer-and-provider-catalog-20261012-uppercase` | Preserve native Telegram answers and use compatible free inference routes | Status: implemented and verified. The user owns publication and runtime replacement. |
+| `guide.work-orders-wo-telegram-progress-presentation-20261012-uppercase` | Telegram progress presentation | Status: implemented and verified, resumed by the user with instructions to complete, commit and push. The evidenced OpenCode compatibility failure is handled in the current repair order. |
 | `guide.work-orders-wo-telegram-unavailable-review-presentation-20261012-uppercase` | Telegram reply presentation when an auxiliary review is unavailable | Status: implemented and verified. Publication and runtime replacement remain with the user. |
 | `guide.work-orders-world-class-memory-compiler-readme-uppercase` | World-Class Memory Compiler Program | Status: active implementation program Owner: Omnius orchestration and memory packages Last updated: 2026-07-13 |
 | `guide.work-orders-world-class-memory-compiler-tracker-uppercase` | Memory Compiler Implementation Tracker | Last reconciled: 2026-07-13 Authority: This file is the granular program tracker. The work-order documents define the contract and acceptance criteria; neither test output nor a model claim may check an item without the named evidence. |

package/docs/inference-fallback-priority.md

@@ -0,0 +1,91 @@
+# Inference fallback priority
+
+Local inference remains first. After a qualifying local failure and any required
+manual approval, the remote cascade uses these stages:
+
+1. Every eligible OpenCode free model, in benchmark-informed order.
+2. Every eligible Hermes model, as explicitly requested by the operator.
+3. Remaining keyless routes merged by model quality across providers.
+4. Explicitly configured keyed providers, in their configured order.
+
+An explicit `keyless: false` policy retains configured-only behavior. The
+OpenCode and Hermes stages are discovered lazily: successful OpenCode inference
+does not fetch lower provider catalogs. All stages retain the existing deadline,
+capability, context, cost, cooldown, ownership and cancellation checks. Models
+cooling after HTTP 429 do not hold up ready alternatives. Ready retries retain
+the original cascade priority rather than simply favoring an earlier expiry.
+
+## Benchmark basis
+
+The host-owned table in
+`packages/orchestrator/src/inference-fallback-priority.ts` uses non-estimated
+Artificial Analysis Intelligence Index **v4.3.2**, observed 2026-10-12. The same
+revision includes agentic workflow, terminal, coding, knowledge and long-context
+evaluations. Scores from older index revisions are not mixed into this order.
+
+| OpenCode model | Published index | Evaluated setting |
+| --- | ---: | --- |
+| [Muse Spark 1.3](https://artificialanalysis.ai/models/muse-spark-1-3) | 48.09 | Max; Xhigh separately scores 45.07 |
+| [Step 5 Preview](https://artificialanalysis.ai/models/step-5) | 43.73 | Reasoning |
+| [Ling 3.1 Flash](https://artificialanalysis.ai/models/ling-3-1-flash) | 41.09 | Reasoning |
+| [MiMo V2.6 Flash](https://artificialanalysis.ai/models/mimo-v2-6-flash) | 37.88 | Reasoning |
+| [Nemotron 3.5 Lightning](https://artificialanalysis.ai/models/nemotron-3-5-lightning) | 12.86 | Reasoning |
+
+These are published measurements of the named models, not benchmarks of the
+anonymous endpoints. Gateway effort, precision and checkpoint equivalence have
+not been established. The runtime uses each named model's highest published
+non-estimated variant as a preference for model potential; this does not change
+the caller's thinking policy or silently request maximum reasoning effort.
+
+Official coding results provide separate cross-checks: Muse 1.3 Max reports
+75.4% DeepSWE v1.1 and 88.8% Terminal-Bench 2.1; Step 5 High reports 67.7% and
+85.0%; MiMo Flash-RL reports 67.9% and 87.6%. Different harnesses and settings
+prevent treating those figures as an exact cross-model league table.
+[Meta](https://dev.meta.ai/models/muse-spark),
+[StepFun](https://www.stepfun.com/step-5-preview),
+[Xiaomi](https://huggingface.co/XiaomiMiMo/MiMo-V2.6-Flash-RL).
+
+## Unranked models and dynamic discovery
+
+Space Bunny and Big Pickle are undisclosed or rolling aliases. LongCat 2.5 has
+no exact comparable published result in the bounded search. They remain
+eligible after models with comparable measured results; this placement expresses
+evidence confidence, not proof that they are weaker. Small original experiments
+on Big Pickle and Space Bunny use different subsets and are recorded separately,
+without converting them into an invented AA score. New free models remain
+automatically discovered within the existing catalog bounds.
+
+For unmeasured models, declared tool/schema support and usable context/output
+headroom provide deterministic operational tie-breaks, followed by the host
+preferred identity and stable model ID. These fields do not measure intelligence.
+An opaque selector remains unranked; known measured concrete models precede it.
+For a wholly unmeasured compatible pool, its existing automatic selector remains
+available before concrete alternatives, without borrowing their token limits.
+
+The [research receipt](work-orders/evidence/fallback-model-benchmarks-20261012.json)
+maps 44 advertised candidate identities across OpenCode, Hermes, Kilo, LLM7, OVH
+and ch.at, with exact-version/mode alternatives and exclusions. Only measured
+matching identities enter the runtime table. Estimated-only scores, older
+LongCat/Mistral versions, and base-model scores for the quantized Hermes
+derivative do not become fabricated endpoint measurements.
+
+Published quality never establishes free access. In particular, current LLM7
+concrete rows advertise positive prices and its homepage describes free-token
+access; these facts do not confer anonymous tool/schema authority. The existing
+pricing and authentication filters remain in force.
+
+## Compatibility and verification
+
+Before dispatch, exact native tools, structured output and full request token
+budgets still determine eligibility. Ling's explicit schema-support rejection
+excludes it from schema-bearing turns. Muse retains its Responses transport.
+Learned native grammar restrictions are isolated by endpoint/model/API, and the
+complete original host schema remains authoritative. Successful output ends
+the cascade; no replay occurs after visible ordinary output or tool fragments.
+
+Source regressions cover full 512-model OpenCode traversal before Hermes,
+unknown-model discovery, published-score ordering, cross-provider quality merge,
+configured-only/tail behavior, cooldown recovery, ready retry priority and
+unchanged tool/schema/Stop contracts. The packaged backend verifier repeats the
+ordering and schema repair through synthetic HTTP with no real inference or
+Telegram messages.

package/docs/opencode-free-model-discovery.md

@@ -8,12 +8,20 @@ Source revision: [`anomalyco/opencode@15b24ae12ddb8b7ae3e923b286b4032761bee510`]
 - [`packages/core/src/plugin/models-dev.ts`](https://github.com/anomalyco/opencode/blob/15b24ae12ddb8b7ae3e923b286b4032761bee510/packages/core/src/plugin/models-dev.ts) excludes deprecated models and models without text support.
 - [`packages/core/src/plugin/provider/opencode.ts`](https://github.com/anomalyco/opencode/blob/15b24ae12ddb8b7ae3e923b286b4032761bee510/packages/core/src/plugin/provider/opencode.ts) enables anonymous access using the public sentinel `public` and disables models with positive input costs when no real key is configured.
 
-Omnius requires explicit zero input and output costs, including any advertised context tiers and cache prices. It pins the provider and endpoint, accepts only the OpenAI-compatible chat transport, excludes protocol/endpoint overrides, and preserves documented tool, schema and token-limit metadata. Missing schema support remains unknown. The returned `admission: "catalog_only"` records that metadata alone establishes no route availability. Per-model Responses/Anthropic overrides require their own adapters.
+Omnius requires explicit zero input and output costs, including any advertised context tiers and cache prices. It pins the provider and endpoint, accepts the OpenAI-compatible chat transport and the per-model `@ai-sdk/openai` Responses transport, excludes foreign endpoints and unsupported protocols, and preserves documented tool, schema and token-limit metadata. Missing schema support remains unknown. The returned `admission: "catalog_only"` records that metadata alone establishes no route availability. Responses models use the dedicated adapter at the same pinned `/inference/v1/responses` endpoint.
 
 The catalog lists paid models too. The inference `/v1/models` response supplies IDs without cost or capability metadata and cannot establish free eligibility. Free suffixes are insufficient: Big Pickle has zero costs without that suffix, and old free rows can remain deprecated or unavailable.
 
 An optional intersection with `https://opencode.ai/inference/v1/models` removes free metadata rows that the gateway no longer lists. This unauthenticated endpoint returned 83 IDs on 2026-10-12; `exo-free`, `ling-3.0-flash-fin-free` and `nemotron-3-ultra-free` were absent. These observations are not hardcoded exclusions. A valid empty list excludes all models; missing, malformed or oversized discovery preserves the canonical zero-cost metadata instead of treating a discovery outage as an authoritative empty provider. ID-only rows can never add a model or supply price, tools, schema or context metadata.
 
+The [complete free-model follow-up](work-orders/WO-opencode-all-free-models-20261012.md)
+removes the previous 16-model cascade cutoff: all eligible OpenCode models within
+the shared 512-row catalog bound are queued. The subsequent
+[benchmark-informed priority](inference-fallback-priority.md) exhausts eligible
+OpenCode models before Hermes and other providers. The current audit found seven live free chat models plus
+`muse-spark-1.3-contributor-free`, whose `@ai-sdk/openai` declaration selects
+Responses. The ordinary chat adapter must never substitute for that transport.
+
 On 2026-10-12, synthetic tool-less Nemotron requests returned HTTP 403 `FreeTierError`, including probes using the public sentinel, current upstream headers and legacy `/zen/v1/chat/completions` endpoint. Within the user's explicitly authorized partner compatibility scope, a subsequent source-derived native-shaped request succeeded at `https://opencode.ai/inference/v1/chat/completions`: HTTP 200 SSE, visible answer `OK`, normal `stop` and `[DONE]`, in 1.044 seconds. It used `opencode/latest/2.0.27/cli`, client `cli`, transparent `x-omnius-client: omnius/1.0.847`, fresh source-format session/message IDs, the current system prefix, genuine read/shell definitions, automatic tool selection and streaming. No tool executed. This demonstrates native-agent availability for that request; it does not identify which shape differences the server requires or establish all models and modes.
 
 Two further synthetic streamed probes also returned HTTP 200 with normal terminal receipts. The same compatibility definitions with `tool_choice: "none"` and a strict JSON schema produced exactly `{"value":"ok"}` without tool calls in 4.120 seconds. A forced custom `omnius_probe` tool alongside those definitions returned that custom call with the expected arguments in 0.946 seconds. These establish those request shapes for Nemotron, without executing any tool or sending private context. They do not imply every catalog model supports them.

package/docs/work-orders/WO-fallback-quality-order-20261012.md

@@ -0,0 +1,70 @@
+# Benchmark-informed fallback cascade
+
+Status: implemented and verified. Publication and active runtime replacement
+remain with the user. Telegram progress presentation stays deferred.
+
+## User request
+
+Try all free OpenCode models from highest capability to lowest before Hermes,
+then descend through remaining keyless endpoints. Research published benchmarks
+for the actual listed model versions to determine the stack. Do not derail the
+ongoing inference compatibility repair.
+
+## Findings and work
+
+The prior helper tried configured providers first, preferred Nemotron over
+stronger available models, and interleaved providers before exhausting OpenCode.
+OpenCode's catalog provides no quality score; its upstream default follows
+release date, which is not an intelligence ranking.
+
+The [benchmark evidence](evidence/fallback-model-benchmarks-20261012.json) uses
+current Artificial Analysis v4.3.2 plus original vendor coding evaluations.
+Current comparable OpenCode order is Muse 1.3, Step 5, Ling 3.1, MiMo 2.6,
+Nemotron 3.5. Three additional anonymous/unmeasured models remain eligible;
+they are explicitly unranked rather than assigned fabricated scores. Free
+gateway reasoning settings and checkpoint equivalence remain unverified.
+
+Implement OpenCode-all → Hermes-all → remaining keyless merged by model quality
+→ configured keyed tail. Preserve explicit configured-only policy, model-specific
+and provider-wide quota scopes, schema adapters, tool/context/cost admission,
+deadline bounds, manual permission and no replay after output. Do not delay
+ready alternatives for a throttled higher route. Ready retries use original
+cascade priority. Research scores must never confer free-access authority.
+
+The [priority reference](../inference-fallback-priority.md) records the source
+URLs, exact settings, unknown-model behavior and operational limitations.
+
+## Acceptance
+
+- A successful 512th OpenCode model produces zero lower-provider dispatches;
+  full OpenCode exhaustion reaches Hermes only after all eligible OpenCode rows.
+- A stronger measured nonpreferred model precedes a weaker seed. Catalog or
+  registry row order does not change selection. Newly discovered unknown models
+  remain included; incompatible or nonfree rows remain excluded.
+- Remaining providers merge by model quality, so a weak alternative does not
+  preempt a stronger model at another endpoint. Opaque selectors claim no fixed
+  benchmark identity.
+- Cooldowns immediately allow ready alternatives; recovery returns to higher
+  routes. Stop, stale ownership, total deadlines and bounded retries still hold.
+- Verify source suites, complete workspace build, freshly installed package and
+  actual bundled backend ordering/schema checks. Commit and push scoped work.
+
+## Verification receipt
+
+542 orchestrator tests passed with one existing skip; 122 CLI tests passed.
+The complete workspace build, package bundle, README/tarball audit and fresh
+compiler-free global npm installation passed. SQLite, CLI and library loaded.
+
+The [freshly installed backend receipt](evidence/fallback-quality-installed-20261012.json)
+records 64/64 mocked transport cases passing. Six reach the 512th OpenCode alias
+with zero other-provider generations; two prove benchmark preference over the
+Nemotron seed and larger unmeasured context limits; two exhaust ten eligible
+keyless aliases before the configured keyed tail. Native tool, Responses,
+structured validation and the original-schema `uniqueItems` regressions remain
+green. These checks made no real inference requests or Telegram sends.
+
+Prepared artifact: `publish/omnius-1.0.848.tgz`, SHA-256
+`2f0b02299333dea363eaa93c8e1f7e10a4371aeb3388fba35e6a3a39359c8611`.
+Its bundled backend SHA-256 is
+`651aa2819b85678d8aac1fa84f9e9c6fd7a088d17645d9cd212b00500bcf468c`.
+No publication or active runtime restart was performed.

package/docs/work-orders/WO-fallback-reply-contracts-20261012.md

@@ -0,0 +1,116 @@
+# Fallback reply contracts and live Telegram regressions
+
+Status: implemented and verified in source and the freshly installed package.
+Publishing and restarting the active bot remain user-owned. The subsequent
+OpenCode-first capability ordering is tracked in
+[its work order](WO-fallback-quality-order-20261012.md); Telegram progress
+presentation remains explicitly deferred.
+
+## User steering
+
+The running cascade selects OpenCode Nemotron, Kilo Nemotron and Hermes but
+reports `invalid_response`; OVH reports `empty_response`, and Big Pickle rejects
+the request with HTTP 400. Handle the actual protocol and expected reply contract
+dynamically for every selected fallback. Do not treat a successful isolated
+provider probe as proof that production routing uses the same adapter.
+
+The user also reported that replying to ordinary "good dog" chatter created and
+uploaded `reply.txt`. Review current live logs and fix evidenced problems before
+publication; preserve the ongoing full free-model coverage work.
+
+## Evidence
+
+The scoped public run `telegram-c34a3d7d53728329-1791861851684-1` began at
+2026-10-13T03:24:12Z. It produced a plain reply, which the host rejected after a
+semantic review demanded delivery evidence. The current criterion was
+`effect:visible_response`; the current user message requested no file. That
+rejection led to a failed file send, file creation, another blocked result check,
+then a successful upload and an echoed final reply at 03:25:41Z. Eventual upload
+success does not justify the invented delivery obligation.
+
+The [sanitized prompt audit](evidence/native-conversation-prompt-audit-20261012.json)
+also found generic zero-execution guidance that told the model to take a tool
+action for a conversational goal. Tool receipt authority must remain intact;
+ordinary conversation must not be required to manufacture execution evidence.
+
+Current debug artifacts redact actual outbound requests and do not retain
+auxiliary provider response bodies. The generic `invalid_response` category
+combined transport JSON, native tool and structured-schema failures; that label
+alone did not identify the cause. Production-helper probes with invented context
+isolated it: the simple native-goal schema passed, but the full terminal-review
+schema produced an HTTP 200 error envelope. The upstream Nvidia grammar rejected
+`uniqueItems`, wrapped as `server_error`. See the [exact safe diagnostic
+receipt](evidence/terminal-review-error-probe-20261012.json). No private message,
+credential or raw provider response body is retained in the public receipts.
+
+## Work and acceptance
+
+1. Trace selected-model metadata through the actual production fallback helper,
+   backend factory, request builder and response decoder. Select Chat Completions
+   or Responses per model, preserve tool/schema/context contracts, and condition
+   unsupported wire hints without weakening host validation.
+2. Exercise the actual native-goal review policy and schema through these
+   production adapters with invented conversation/evidence. Derive provider
+   limits from their public catalogs. Use no local inference, real actions,
+   Telegram messages or private human context. Honor quota cooldowns.
+3. Add safe, precise rejection diagnostics identifying the expected reply kind
+   and validation stage; never print raw bodies, secret values or user context.
+   Validate structured auxiliary replies before exposing their text as a
+   completed reply. Preserve Stop, ownership and no replay after visible output.
+4. Repair evidenced conversational tool pressure and test a direct chat reply
+   without files, uploads or fabricated tool receipts. Real mutation/delivery
+   requests must retain actual effect and provider-acknowledgement requirements.
+5. Run focused and production Telegram regressions, rebuild the package, verify
+   the freshly installed artifact and record scoped commit/push receipts.
+
+## Additional live checks
+
+Review later runs for duplicate contradictory completion events and tool
+description truncation. Apply only repairs supported by current evidence;
+record unresolved observations explicitly instead of broadening the task into
+unrelated runtime changes.
+
+## Implementation and verification
+
+- Normalize in-band provider errors before decoding Chat Completions or
+  Responses, including HTTP 200 JSON and SSE envelopes. Retain only whitelisted
+  failure categories and status, never upstream text or nested causes.
+- Learn the proven native `uniqueItems` restriction per full endpoint path,
+  model and API shape for five minutes. Retry that route once with a separately
+  lowered wire schema. Preserve the complete original host schema, completion
+  callback, tool parameters and uniqueness checks. Include original-schema
+  guidance in the admitted request budget. Do not strip arbitrary constraints.
+- Validate expected JSON and native tool calls before releasing structured
+  replies or executable tool fragments. Accept one complete JSON fence without
+  changing values; reject prose extraction, malformed arguments, unoffered
+  calls, truncation and duplicate citations. Preserve cancellation, ownership,
+  deadlines, manual fallback permission and the no-replay boundary after output.
+- Distinguish JSON syntax, schema mismatch, unsupported schema, tool choice,
+  tool arguments and transport envelope failures in safe route diagnostics.
+- Remove generic pressure to manufacture tool execution for conversation.
+  Preserve file-write/edit/send purpose before long scoped paths consume the
+  model-facing description budget. Text replies need no fabricated reply file;
+  requested material effects still require actual tool and delivery receipts.
+
+Source verification: 520 orchestrator tests passed with one existing skip;
+122 CLI tests passed. The complete workspace build and artifact audit passed.
+The compiler-free fresh npm installation loaded SQLite and the CLI/library;
+60 deterministic checks exercised the actual installed backend, including
+12 full terminal-review grammar-repair/host-rejection cases.
+
+The [post-repair live receipt](evidence/terminal-review-schema-repair-probe-20261012.json)
+uses the actual production fallback helper and backend with synthetic context,
+the unchanged full terminal-review schema and public provider limits. OpenCode
+and Kilo both rejected the initial native grammar, then returned original-schema
+valid JSON after the same-route repair. Kilo chose `deliver`; OpenCode chose
+`stop`. OpenCode's generated justification was not retained, so semantic
+correctness is not claimed. Hermes reached the adapted request and returned
+HTTP 429; the probe stopped at its two-send quota. No local inference, Telegram
+messages or tool actions occurred. Remote quota or outage can still exhaust a
+bounded cascade; this repair does not promise perpetual service availability.
+
+The later 03:28 run's successful handler result and failed synthetic terminal
+projection are distinct events. The latter retained pending visible-response
+acknowledgement. This observation does not establish a duplicate-handler bug or
+justify weakening the delivery gate; presentation work remains queued in
+[its work order](WO-telegram-progress-presentation-20261012.md).

package/docs/work-orders/WO-opencode-all-free-models-20261012.md

@@ -0,0 +1,88 @@
+# All OpenCode free models in the fallback cascade
+
+Status: implemented and verified. Publication and runtime replacement remain
+with the user. The subsequent live-reply fixes are tracked separately in
+[fallback reply contracts](WO-fallback-reply-contracts-20261012.md).
+The original preferred-first/provider-fairness ordering recorded below has been
+superseded by [benchmark-informed priority](WO-fallback-quality-order-20261012.md)
+at the user's subsequent request.
+
+## Request
+
+All free models offered by OpenCode must be lined up in Omnius's fallback chain,
+including later catalog entries and models using the Responses API. This extends
+the [keyless fallback repair](WO-keyless-fallback-coverage-20261012.md).
+
+## Findings
+
+The prior implementation loaded the free chat catalog dynamically, but limited
+each provider to 16 compatible models. An installed-runtime regression with 512
+eligible models reproduced exhaustion after only 16 OpenCode dispatches. The
+global distinct-attempt bound also assumed 16 models per provider.
+
+The [current primary-source audit](evidence/opencode-all-free-audit-20261012.json)
+found eight active, live, explicitly zero-cost models:
+
+| Model | API |
+| --- | --- |
+| `nemotron-3.5-lightning-free` | Chat completions |
+| `big-pickle` | Chat completions |
+| `ling-3.1-flash-free` | Chat completions |
+| `longcat-2.5-preview-free` | Chat completions |
+| `mimo-v2.6-flash-free` | Chat completions |
+| `space-bunny-free` | Chat completions |
+| `step-5-preview-free` | Chat completions |
+| `muse-spark-1.3-contributor-free` | Responses |
+
+The chat-only parser excluded Muse Spark 1.3 because its per-model SDK is
+`@ai-sdk/openai`, whose upstream transport uses `/responses`. OpenCode's default
+loader excludes deprecated models; the current live ID list also contains an
+unknown free-suffix ID without corresponding cost/capability metadata. Neither
+a deprecated entry nor an unknown suffix alone establishes an offered free
+model for automatic routing.
+
+## Work and acceptance
+
+1. Enumerate every compatible OpenCode free model within the shared 512-row
+   catalog safety bound. Adjust total dispatch accounting accordingly. Keep
+   stable ordering, preferred Nemotron first, provider fairness and model-level
+   cooldowns. Newly published eligible catalog entries require no code update.
+2. Add the source-derived, exact-origin Responses adapter for the model's
+   declared transport. Preserve full conversation, tool-result history, exact
+   original host tool schemas and choices, structured output, cancellation and
+   no replay after visible output. Protocol metadata never authorizes tools.
+3. Share enumeration and Responses handling with the credentialless setup
+   pool. Model-specific failures must not disable all OpenCode alternatives.
+   Keep setup deadlines and count network requests against the full model bound.
+4. Prove full 512-model traversal through the helper and packaged backend in
+   unary and streaming modes, including tool/schema requests, plus Responses
+   routing, capability exclusions, cooldowns, catalog refresh and host identity
+   isolation. Tests use synthetic HTTP; no local model requests or tools execute.
+5. Rebuild and verify the package, record receipts, commit and push scoped work.
+   Preserve unrelated checkout changes and leave publication/runtime activation
+   to the user.
+
+All models belong in the eligible cascade; a request still stops at its first
+usable success, cancellation, or deadline. Capability and context checks must
+not weaken the requested contract to force an incompatible model into use.
+
+## Verification
+
+The complete current metadata audit yields all eight active live free models,
+including Muse's declared Responses transport. The regression suite reconstructs
+the audited metadata to assert exactly that coverage. Both the production helper
+and the packaged backend reach the 512th eligible model after 511 model-specific
+failures, in text, forced native-tool and strict-schema requests, unary and
+streaming. Other providers retain their first attempt before OpenCode alternates.
+
+The source suites passed 399 orchestrator and 100 CLI tests, with one existing
+skip. This includes 57 setup-pool tests, model-level cooldowns, catalog refresh,
+transport isolation, complete context/tool/schema preservation and Responses
+terminal/cancellation handling. The compatibility harness passed 30 tests.
+
+Full clean recursive build, bundling, packing and compiler-free fresh npm
+installation passed for the prepared 1.0.848 artifact. The required SQLite
+prebuild loaded. The [installed backend receipt](evidence/opencode-all-free-installed-verification-20261012.json)
+records all 48 mocked transport cases passing, including full 512-model traversal
+and Muse's six unary/streaming text/tool/schema cases. These checks sent no real
+inference requests or Telegram messages. No package was published by this work.

package/docs/work-orders/WO-opencode-production-compatibility-20261012.md

@@ -0,0 +1,90 @@
+# OpenCode production request compatibility
+
+Status: implemented and verified. Telegram presentation is also completed.
+Publication and active-runtime restart remain with the operator. Step's native
+attention-format compatibility remains unverified after a provider limit; the
+working cascade can continue to other compatible models.
+
+## Evidence and cause
+
+The running 1.0.849 bundle matched the prepared artifact. The discrepancy was
+request compatibility and routing, not an old installed bundle. Earlier live
+Nemotron/Kilo probes did not establish compatibility of the newly prioritized
+Muse/Step models with the full Telegram attention schema.
+
+Real synthetic probes found:
+
+- Muse Responses rejects `tool_choice: none`, `required` and named choices;
+  it accepts only `auto`. The compatibility core definitions made the original
+  tool-free request include tools on the wire. Host tool authority must remain
+  unchanged when adapting that wire choice.
+- After the choice repair, Muse rejects `uniqueItems` with the diagnostic
+  “JSON schema keyword `uniqueItems` is not supported for structured outputs”.
+  The existing schema-recovery path did not recognize this HTTP 400 wording.
+- Step returned `pong` for a plain conversation, but the original attention
+  schema returned an opaque upstream HTTP 400. Its cause is still under live
+  investigation; do not attribute it to a particular keyword without evidence.
+- The public native fast path promoted a sealed `conversation` judgment into
+  an action runner. That produced the empty progress panel and false incomplete
+  suffix. Admission must require both action route and action execution class.
+
+## Required work and acceptance
+
+1. Condition the selected model's actual protocol and observed wire limitations.
+   Keep original tool choice, offered names, argument schemas and structured
+   response validation authoritative. Compatibility definitions grant no actions.
+2. Recognize only evidenced HTTP 400 schema limitations and retain bounded
+   same-route recovery. Preserve auth, rate, context, cancellation and ownership
+   behavior; never treat arbitrary upstream messages as capability evidence.
+3. Validate with real OpenCode generations through production builders, parsers,
+   fallback discovery, budgeting and original host-schema checks. No fabricated
+   model replies. The reusable `scripts/live-opencode-fallback-harness.mjs`
+   enters the exact production remote phase without inventing a local result or
+   local failure. This does not test local broker admission or Telegram transport.
+4. Fix public conversation admission and complete the paragraph/Activity
+   presentation work under its separate work order. Preserve final ACK authority.
+5. Rebuild all workspace packages, verify the packaged artifact, retain safe live
+   receipts and commit/push scoped changes.
+
+## Verification
+
+The real remote cascade returned original-schema-valid attention JSON from
+Muse after HTTP 400 -> same-model adapted HTTP 200, then returned `pong` on
+HTTP 200. The first selected-backend probes also returned `pong` from Step.
+Synthetic input only; zero local inference requests, Telegram messages or tool
+executions. Mocked regressions protect invariants and are not availability proof.
+
+The clean rebuild, tarball audit and compiler-free fresh npm installation passed.
+The [installed-bundle live receipt](evidence/opencode-installed-production-stream-live-20261012.json)
+exercises the exact shipped fallback stream phase, actual free/available model
+discovery, production request/parser paths and the original attention schema.
+Both attention and conversation passed with 56,000 bytes of synthetic background:
+Muse returned HTTP 400 -> adapted same-model HTTP 200 for attention, and HTTP 200
+with exactly `pong` for conversation. No model/metadata replies were mocked.
+The installed and prepared bundle SHA256 is
+`d8636120a09b01e5510cb048c5cafcbb0598474653831174196e6e708de3c33e`.
+The packed artifact SHA256 is
+`88e078ab0bfd38895f8d1691060526f5c7bba8b894b874be7b1c0b361a72545b`.
+The validation artifact retains version 1.0.849; the operator's publication
+workflow must still select a new release version.
+
+Step's [bounded diagnostic](evidence/opencode-step-rate-limited-diagnostic-20261012.json)
+stopped after one HTTP 429 (“Endpoint is unavailable”). Its second diagnostic
+was withheld. No evidence supports a static Step schema adaptation, so none was
+invented. This is not a promise that all remote providers remain available.
+
+404 focused inference regression tests and 237 Telegram regression tests passed.
+The latter use explicit mocked transport acknowledgements, not real Telegram
+sends. Inference acceptance uses real providers. Local admission and the active
+bot's restart were deliberately outside this live remote harness.
+
+Reproduce after building and installing the artifact:
+
+```sh
+node scripts/live-opencode-fallback-harness.mjs --run --cascade --stream \
+  --bundle /path/to/installed/omnius/dist/index.js --context-bytes 56000 \
+  --cases attention,conversation --output /tmp/omnius-opencode-live.json
+```
+
+Delivered implementation commits: `7a48a712` (inference compatibility) and
+`82fce9cf` (Telegram narration, activity controls and conversation admission).

package/docs/work-orders/WO-telegram-progress-presentation-20261012.md

@@ -0,0 +1,45 @@
+# Telegram progress presentation
+
+Status: implemented and verified, resumed by the user with instructions to
+complete, commit and push. The evidenced OpenCode compatibility failure is handled in
+[the current repair order](WO-opencode-production-compatibility-20261012.md).
+
+## Requested behavior
+
+- Show the agent's intermediate explanations in public group chat as a compact
+  sequence of short paragraphs describing what it is doing or has learned.
+- Keep detailed activity behind a button that opens the activity view.
+- Present tool calls and results in clean, separate wrapped code blocks using
+  supported Telegram message formatting and controls.
+- Replace the public numbered started/succeeded activity dump and its generic
+  "Working"/"Work ended" panel with useful intermediate chat narration.
+- Deliver the final answer separately, with completion wording derived from
+  actual delivery state rather than an internal handler's acceptance.
+
+## Implementation and verification
+
+The runner emits finalized main-agent prose as `assistant_text` with source
+`model_visible_text`; the terminal chat/voice path renders that visible text.
+Telegram action runs previously kept it only as a final reply candidate. The
+bridge now publishes prose accompanying a same-response nonterminal work tool
+through its existing bound progress writer. Standalone explicit
+`telegram_progress` remains available. Hidden reasoning, final-only drafts,
+transport contracts and internal guidance do not become progress.
+
+Keep the four latest distinct paragraphs in collapsed public/private summaries.
+Activity opens the chronological details; public Summary returns to prose.
+Admin calls/results use separate escaped HTML code blocks; public detail shows
+safe tool names and phases without leaking private arguments or outputs.
+Keep telemetry and adversarial diagnostics in private archives while filtering
+ordinary sub-agent display callbacks.
+
+Verify private/public scope, edit and
+send limits, interruption/Stop, callback ownership, long tool-output handling,
+and that diagnostics/adversarial guidance remain out of ordinary public chat.
+Progress never settles work or substitutes for final provider acknowledgement.
+Verification: 126 focused presentation/routing tests passed; 51 public/native
+fallback/diagnostic tests and 60 private-native tests also passed. These delivery
+tests use explicit mocked Telegram acknowledgements and do not claim real bot
+messages. The actual listener is exercised in `telegram-runner-commentary.test.ts`.
+The full workspace rebuild and package audit passed. Real inference acceptance,
+including production streaming, is recorded under the inference repair order.