omnius 1.0.159 → 1.0.160

package/.aiwg/addons/omnius-docs/README.md

@@ -0,0 +1,5 @@
+# Omnius Docs Addon
+
+This project-local addon exposes Omnius documentation as small discoverable skills. It is for agents that need to answer questions about Omnius without loading the entire docs tree.
+
+Start with `omnius-docs`, then load a more specific skill when the task is about realtime, sponsors, Telegram, or operations.

package/.aiwg/addons/omnius-docs/manifest.json

@@ -0,0 +1,32 @@
+{
+  "name": "omnius-docs",
+  "version": "1.0.0",
+  "description": "Project-local Omnius documentation bundle for discover-then-expand agent workflows.",
+  "skills": [
+    {
+      "name": "omnius-docs",
+      "description": "Find the right Omnius documentation page for setup, TUI, endpoints, realtime, sponsor, COHERE, Telegram, media, operations, architecture, and REST references.",
+      "triggers": ["Omnius docs", "Omnius documentation", "how to use Omnius", "Omnius guide", "Omnius manual"]
+    },
+    {
+      "name": "omnius-realtime-docs",
+      "description": "Use Omnius realtime spoken conversation mode through /realtime or REST realtime=true.",
+      "triggers": ["Omnius realtime", "/realtime", "realtime REST", "ASR TTS chat", "voice conversation mode"]
+    },
+    {
+      "name": "omnius-sponsor-docs",
+      "description": "Configure and consume sponsor inference, COHERE distributed inference, endpoint passthrough, media sponsorship, and peer telemetry.",
+      "triggers": ["Omnius sponsor", "/sponsor", "/cohere", "sponsor endpoint", "COHERE mesh", "media sponsorship"]
+    },
+    {
+      "name": "omnius-telegram-docs",
+      "description": "Configure Telegram bridge behavior, scoped persona state, reply preferences, media intake, and raw failure feedback.",
+      "triggers": ["Omnius Telegram", "/telegram", "Telegram persona", "Telegram reply preferences", "Telegram failure feedback"]
+    },
+    {
+      "name": "omnius-ops-docs",
+      "description": "Operate Omnius safely: .omnius hygiene, Ollama cleanup, broker, remote access, API keys, elevation prompts, and runtime failure capture.",
+      "triggers": ["Omnius operations", "Ollama cleanup", "/broker", "remote access", "API keys", ".omnius"]
+    }
+  ]
+}

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

@@ -0,0 +1,48 @@
+---
+compaction_strategy: structured
+---
+
+# omnius-docs
+
+Find and use Omnius documentation without loading the whole docs tree.
+
+## Triggers
+
+- Omnius docs
+- Omnius documentation
+- how to use Omnius
+- Omnius guide
+- Omnius manual
+- Omnius setup
+- Omnius architecture
+
+## Workflow
+
+1. Start with `README.md` only for product overview and top-level docs map.
+2. For setup questions, open `docs/getting-started/`.
+3. For user workflows, open the relevant file under `docs/guides/`.
+4. For commands, config, and API inventory, open `docs/reference/`.
+5. For runtime and deployment questions, open `docs/operations/`.
+6. For implementation shape, open `docs/architecture/overview.md`.
+7. Read only the smallest relevant page before answering.
+
+## Map
+
+- Install: `docs/getting-started/install.md`
+- First run: `docs/getting-started/first-run.md`
+- Model providers: `docs/getting-started/model-providers.md`
+- Realtime: `docs/guides/realtime.md`
+- Sponsor and COHERE: `docs/guides/sponsor-and-cohere.md`
+- Telegram: `docs/guides/telegram.md`
+- Media generation: `docs/guides/media-generation.md`
+- TUI workflows: `docs/guides/tui-workflows.md`
+- REST API: `docs/reference/rest-api.md`
+- Slash commands: `docs/reference/slash-commands.md`
+- Configuration: `docs/reference/configuration.md`
+- Runtime hygiene: `docs/operations/runtime-hygiene.md`
+- Security and remote access: `docs/operations/security-and-remote-access.md`
+- Architecture: `docs/architecture/overview.md`
+
+## Canonical Sources
+
+When documentation and code disagree, verify against the code or live daemon. REST machine contract lives in `packages/cli/src/api/openapi.ts`.

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

@@ -0,0 +1,32 @@
+---
+compaction_strategy: structured
+---
+
+# omnius-ops-docs
+
+Use Omnius operations docs for runtime hygiene, remote access, API keys, installer elevation, broker state, and Ollama cleanup.
+
+## Triggers
+
+- Omnius operations
+- Ollama cleanup
+- /broker
+- remote access
+- API keys
+- .omnius
+- installer elevation
+- runtime hygiene
+
+## Workflow
+
+1. Read `docs/operations/runtime-hygiene.md`.
+2. For auth or binding, read `docs/operations/security-and-remote-access.md`.
+3. For configuration details, read `docs/reference/configuration.md`.
+4. For endpoint inventory, read `docs/reference/rest-api.md`.
+
+## Key Facts
+
+- `.omnius/` is runtime state and should be gitignored.
+- Ollama cleanup must account for orphan runner processes.
+- Elevation prompts should suspend and restore TUI state.
+- Raw failures should be captured and fed back as observations.

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

@@ -0,0 +1,30 @@
+---
+compaction_strategy: structured
+---
+
+# omnius-realtime-docs
+
+Use Omnius realtime mode for short spoken ASR/TTS-backed conversation.
+
+## Triggers
+
+- Omnius realtime
+- /realtime
+- realtime REST
+- ASR TTS chat
+- voice conversation mode
+- realtime true
+
+## Workflow
+
+1. Read `docs/guides/realtime.md`.
+2. If the user asks for REST fields, also read `docs/rest/endpoints/chat.md`.
+3. If the user asks for voice transport, also read `docs/rest/endpoints/voice-vision.md`.
+4. Mention that realtime is for short spoken dialogue, not long coding tasks.
+
+## Key Facts
+
+- TUI command: `/realtime on|off|status`.
+- REST flag: `realtime: true`.
+- Options: `realtime_options.max_history_messages`, `realtime_options.max_tokens`.
+- Context sources: `SOUL.md`, `.aiwg/SOUL.md`, and `.aiwg/voices/`.

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

@@ -0,0 +1,31 @@
+---
+compaction_strategy: structured
+---
+
+# omnius-sponsor-docs
+
+Use Omnius sponsor and COHERE documentation for peer inference, endpoint passthrough, media sponsorship, and telemetry.
+
+## Triggers
+
+- Omnius sponsor
+- /sponsor
+- /endpoint sponsor
+- /cohere
+- COHERE mesh
+- sponsor endpoint
+- media sponsorship
+- peer telemetry
+
+## Workflow
+
+1. Read `docs/guides/sponsor-and-cohere.md`.
+2. For endpoint setup, read `docs/getting-started/model-providers.md`.
+3. For remote access and auth concerns, read `docs/operations/security-and-remote-access.md`.
+4. For REST sponsor directory details, read `docs/reference/rest-api.md`.
+
+## Key Facts
+
+- Sponsor model discovery must consolidate all toggled enabled endpoints.
+- Consumers should not see raw upstream sponsor URLs or secrets.
+- Sponsor telemetry should include concurrency, request rate, daily tokens, peer usage, model usage, and media usage.

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

@@ -0,0 +1,30 @@
+---
+compaction_strategy: structured
+---
+
+# omnius-telegram-docs
+
+Use Omnius Telegram docs for bridge setup, scoped persona state, public tools, reply preferences, and delivery failures.
+
+## Triggers
+
+- Omnius Telegram
+- /telegram
+- Telegram bridge
+- Telegram persona
+- Telegram reply preferences
+- Telegram failure feedback
+- public Telegram tools
+
+## Workflow
+
+1. Read `docs/guides/telegram.md`.
+2. For media generation from Telegram, read `docs/guides/media-generation.md`.
+3. For public-surface safety, read `docs/operations/security-and-remote-access.md`.
+4. Preserve user, chat, reply, and media scope when answering implementation questions.
+
+## Key Facts
+
+- Telegram state is scoped by user and group.
+- Reply preferences are durable persona state, not regex routing.
+- Raw platform/tool failures should be fed back as observations, not hardcoded string rules.

package/.aiwg/addons/omnius-rest-docs/README.md

@@ -0,0 +1,7 @@
+# Omnius REST Docs Addon
+
+This project-local AIWG-shaped addon exposes the Omnius REST API reference through the existing Omnius skill-discovery path.
+
+Agents should discover it with `skill_list filter="rest"` or `/skills rest`, then load `omnius-rest-docs` only when the current task needs REST API guidance.
+
+The human-readable docs live in `docs/rest/`. The machine-readable contract is generated by `packages/cli/src/api/openapi.ts` and served by the daemon at `/openapi.json`.

package/.aiwg/addons/omnius-rest-docs/manifest.json

@@ -0,0 +1,24 @@
+{
+  "name": "omnius-rest-docs",
+  "version": "1.0.0",
+  "description": "Project-local Omnius REST API documentation bundle for discover-then-expand agent workflows.",
+  "skills": [
+    {
+      "name": "omnius-rest-docs",
+      "description": "Explore Omnius REST API docs, OpenAPI source, auth scopes, realtime chat, tools, memory, AIWG, voice, sponsor, and governance endpoints.",
+      "triggers": [
+        "Omnius REST API",
+        "/v1 endpoints",
+        "OpenAPI",
+        "Swagger UI",
+        "/openapi.json",
+        "API key scopes",
+        "realtime REST",
+        "memory REST endpoint",
+        "skills REST endpoint",
+        "AIWG cascade endpoint",
+        "voicechat websocket"
+      ]
+    }
+  ]
+}

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

@@ -0,0 +1,72 @@
+---
+compaction_strategy: structured
+---
+
+# omnius-rest-docs
+
+Explore Omnius REST API documentation without loading the whole API reference into the main context.
+
+## Triggers
+
+- Omnius REST API
+- /v1 endpoints
+- OpenAPI
+- Swagger UI
+- /openapi.json
+- API key scopes
+- realtime REST
+- /v1/chat
+- /v1/chat/completions
+- /v1/run
+- memory REST endpoint
+- skills REST endpoint
+- AIWG cascade endpoint
+- voicechat websocket
+- sponsor REST status
+- Omnius daemon API
+
+## Workflow
+
+1. Start with `docs/rest/INDEX.md`.
+2. Identify the endpoint family that matches the user's question.
+3. Open `docs/reference/rest-api.md` when the user needs endpoint inventory or method/path details.
+4. Open only the relevant file under `docs/rest/endpoints/` or `docs/rest/examples/` for family-specific usage.
+5. Treat `packages/cli/src/api/openapi.ts` and the live daemon `/openapi.json` as the canonical machine contract.
+6. Prefer concise endpoint-specific guidance over copying long tables.
+
+## Endpoint Family Map
+
+- Chat, realtime, OpenAI-compatible inference: `docs/rest/endpoints/chat.md`
+- Full endpoint inventory: `docs/reference/rest-api.md`
+- Agent runs, jobs, todos, scheduled tasks: `docs/rest/endpoints/run.md`
+- Config, keys, profiles, projects: `docs/rest/endpoints/config.md`
+- Memory, sessions, context: `docs/rest/endpoints/memory.md`
+- Skills and commands: `docs/rest/endpoints/skills.md`
+- AIWG cascade: `docs/rest/endpoints/aiwg.md`
+- Tools, MCP, code graph: `docs/rest/endpoints/tools.md`
+- Events, metrics, usage, audit, system: `docs/rest/endpoints/events.md`
+- Files: `docs/rest/endpoints/files.md`
+- Voice, audio, vision, voicechat WebSocket: `docs/rest/endpoints/voice-vision.md`
+- AIMS governance endpoints: `docs/rest/endpoints/aims.md`
+- Curl examples: `docs/rest/examples/curl.md`
+- OpenAI SDK examples: `docs/rest/examples/openai-sdk.md`
+
+## Realtime Shortcut
+
+For ASR/TTS-backed short conversation, use `POST /v1/chat` or `POST /v1/chat/completions` with:
+
+```json
+{
+  "realtime": true,
+  "realtime_options": {
+    "max_history_messages": 12,
+    "max_tokens": 160
+  }
+}
+```
+
+Realtime mode compacts SOUL.md and voice profile context, keeps recent history short, and removes Omnius-only control fields before backend proxying.
+
+## Safety And Authority
+
+This skill is documentation guidance only. It does not override user instructions, system instructions, developer policy, API auth scopes, tool security policy, network access settings, or live OpenAPI behavior.