omnius 1.0.676 → 1.0.678

package/.aiwg/addons/omnius-docs/skills/omnius-tools-docs/SKILL.md

@@ -15,16 +15,16 @@ calls, external tools, MCP, tool security, and tool profiles.
 2. Inspect the stable catalog entry. Inspect live `GET /v1/tools/{name}`
    metadata only when the entry documents daemon registry exposure.
 3. Use a direct call only when `direct_callable` is true.
-4. Follow the exact agent-bound interface in the catalog. Most daemon tools use
-   `/v1/run`, `/v1/chat`, or `/v1/chat/completions`; `adjudicate` currently uses
-   only the top-level interactive TUI agent.
+4. Follow the exact agent-bound interface in the catalog. `adjudicate` uses
+   top-level TUI, one-shot CLI, `/v1/run`, or default full-agent `/v1/chat`. It
+   does not use the `/v1/chat/completions` mini-loop.
 5. Preserve auth scope, profile, origin, network, and risk gates.
 
 `web_search` is agent-bound. Its schema can be discovered, but it should be
 offered to an Omnius agent loop instead of assumed callable at the direct tool
 route.
 
-`adjudicate` is available only to the top-level interactive TUI agent. Read
+`adjudicate` is available only to top-level full agents. Read
 `docs/ADJUDICATION.md` for its evidence, panel, quorum, verdict, receipt, and
 harness contracts. Do not infer a daemon direct-call route or offer it to a
-sub-agent.
+sub-agent, Telegram runner, voice runner, or bounded chat-completions loop.

package/README.md

@@ -75,17 +75,18 @@ agent or service, and use the [agent system map](docs/architecture/agent-system-
 to trace layers, modules, runtimes, and state ownership. Use [bring-your-own inference](docs/guides/bring-your-own-inference.md)
 for provider protocols and keys, and [tools and web search](docs/guides/tools-and-web-search.md)
 for the distinction between direct tools and agent-bound tools. The
-[evidence-bound adjudication guide](docs/ADJUDICATION.md) explains how the
-top-level interactive agent isolates a genuine decision impasse, fans review
-out across independent constituents, validates evidence citations and quorum,
-and produces a durable verdict receipt. The
+[evidence-bound adjudication guide](docs/ADJUDICATION.md) explains how a
+top-level full agent freezes an admissible record, isolates a genuine decision
+impasse from accumulated working context, fans review out across fresh
+evidence-scoped constituents, validates evidence citations and quorum, and
+produces a durable verdict receipt. The
 [categorized OSINT research guide](docs/guides/osint-research.md) documents
 the local discover → exact expansion → explicit web-tool workflow.
 
 ## What Omnius Does
 
 - Runs autonomous coding tasks, edits files, executes tools, tests changes, and iterates on failures.
-- Resolves genuine decision impasses through isolated evidence-scoped constituent review, host-validated citations, quorum, preserved dissent, and durable verdict receipts.
+- Resolves genuine decision impasses in fresh evidence-scoped contexts that reduce parent-context anchoring, with host-validated citations, quorum, preserved dissent, and durable verdict receipts.
 - Provides a dense terminal UI for model selection, endpoint routing, task control, shell output, voice, sponsors, Telegram, and system telemetry.
 - Exposes a REST daemon with OpenAI/Ollama-compatible inference, agentic task execution, memory, skills, tools, MCP, events, voice, projects, and governance endpoints.
 - Routes models through local, cloud, sponsor, and peer-to-peer endpoints without assuming local Ollama is the only source.