omnius 1.0.608 → 1.0.610

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

@@ -2,13 +2,15 @@
 
 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
+Start with `omnius-agent-onboarding` when the agent has no Omnius context, or
+`omnius-docs` when it already knows the documentation domain. Then load a more specific skill when the task is
 about inference providers, tools/web search, service integration, version
 compatibility, realtime, sponsors, Telegram, operations, or browser
 interaction validation.
 
 Documentation-routing skills:
 
+- `omnius-agent-onboarding`
 - `omnius-inference-docs`
 - `omnius-tools-docs`
 - `omnius-integration-docs`

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

@@ -2,8 +2,8 @@
   "id": "omnius-docs",
   "type": "addon",
   "name": "Omnius Documentation",
-  "version": "1.1.0",
-  "description": "Project-local Omnius documentation bundle for discover-then-expand agent workflows.",
+  "version": "1.2.0",
+  "description": "Project-local Omnius agent onboarding, system map, and discover-then-expand documentation bundle.",
   "manifestVersion": "1",
   "platforms": {
     "claude": "full",
@@ -16,6 +16,8 @@
     "omnius",
     "documentation",
     "discovery",
+    "agent-onboarding",
+    "system-map",
     "inference",
     "tools",
     "operations",

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

@@ -0,0 +1,70 @@
+---
+name: omnius-agent-onboarding
+description: Bootstrap any agent into Omnius, choose the correct entrypoint, locate layer/module/state ownership, and verify live behavior without guessing.
+compaction_strategy: structured
+---
+
+# omnius-agent-onboarding
+
+Use this skill when an agent is new to Omnius or unsure which command, REST
+route, tool, runtime, state root, or source module owns a requested outcome.
+
+## Triggers
+
+- how do I use Omnius
+- integrate an agent with Omnius
+- where is this implemented
+- which Omnius endpoint or command
+- Omnius architecture, runtime, state, or ownership
+- debug Omnius without prior context
+
+## Minimal Bootstrap
+
+1. Run `omnius docs` or read `GET /v1/discovery/bootstrap`.
+2. Search the desired outcome with `omnius discover "<intent>"`.
+3. Expand one stable ID with `omnius show <id>`.
+4. Read `use_when`, `avoid_when`, interfaces, workflow, safety, state,
+   verification, failure recovery, and source-of-truth.
+5. For live work, compare `GET /version`, then inspect `/openapi.json` and the
+   relevant live registry before executing.
+6. Verify the requested terminal result; accepted/queued is not completion.
+
+## Route By Agent Size
+
+- Small-context agent: bootstrap + one `workflow.*` entry + one referenced page.
+- Coding agent: also expand the owning `layer.*` and `module.*` entries.
+- Service integrator: also expand the exact `api.*`, tool, or provider entry
+  and validate the running OpenAPI/live registry.
+- Operator: expand `layer.operations`, the affected `runtime.*`, and
+  `workflow.debug-runtime`.
+- Maintainer: read `docs/architecture/agent-system-map.md`, then inspect the
+  canonical registry and targeted tests before editing.
+
+## Entrypoint Rules
+
+- `omnius`: interactive TUI and human-only slash commands.
+- `omnius "<task>"`: one foreground shell task.
+- `POST /v1/chat`: stateful daemon conversation.
+- `POST /v1/chat/completions`: OpenAI-compatible request, optionally an agent loop.
+- `POST /v1/run`: long asynchronous task with an ID, events, and cancellation.
+- `POST /v1/tools/{name}/call`: only when metadata declares direct-call exposure.
+
+Never infer a REST command from a slash command or a direct route from a tool
+name. Expand `workflow.choose-entrypoint` when uncertain.
+
+## State Rules
+
+- `<project>/.omnius`: project conversations, tasks/runs, context, indexes,
+  memories, and project preferences.
+- `~/.omnius`: daemon/update identity, global config and credentials, managed
+  runtimes, shared model/media storage, and workspace registry.
+
+Resolve the active workspace before touching project state. Do not emit secrets.
+
+## Canonical References
+
+- Generated bootstrap/catalog: `docs/DISCOVERY.md`, `docs/DISCOVERY.json`
+- System ownership: `docs/architecture/agent-system-map.md`
+- Service integration: `docs/guides/agent-integration.md`
+- Live REST contract: `GET /openapi.json`
+- Source discovery contract: `docs/discovery/agent-map.json`

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

@@ -21,13 +21,16 @@ Find and use Omnius documentation without loading the whole docs tree.
 ## Workflow
 
 1. Start with `README.md` only for product overview and top-level docs map.
-2. Search `docs/DISCOVERY.json` by stable ID, alias, or intent.
+2. If the caller is new to Omnius, use the `omnius-agent-onboarding` skill and
+   read the bootstrap in `docs/DISCOVERY.md`.
+3. Search `docs/DISCOVERY.json` by stable ID, alias, or intent.
 3. For setup questions, open `docs/getting-started/`.
 4. For user workflows, open the relevant file under `docs/guides/`.
 5. For commands, config, and API inventory, open `docs/reference/`.
 6. For runtime and deployment questions, open `docs/operations/`.
-7. For implementation shape, open `docs/architecture/overview.md`.
-8. Read only the smallest relevant page before answering.
+8. For implementation shape and ownership, open
+   `docs/architecture/agent-system-map.md` before the shorter overview.
+9. Read only the smallest relevant page before answering.
 
 ## Map
 
@@ -38,6 +41,7 @@ Find and use Omnius documentation without loading the whole docs tree.
 - Bring your own inference: `docs/guides/bring-your-own-inference.md`
 - Tools and web search: `docs/guides/tools-and-web-search.md`
 - Agent integration: `docs/guides/agent-integration.md`
+- Agent system map: `docs/architecture/agent-system-map.md`
 - Service compatibility: `docs/operations/version-compatibility.md`
 - Realtime: `docs/guides/realtime.md`
 - Sponsor and COHERE: `docs/guides/sponsor-and-cohere.md`
@@ -49,7 +53,7 @@ Find and use Omnius documentation without loading the whole docs tree.
 - 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`
+- Architecture: `docs/architecture/agent-system-map.md`
 
 ## Canonical Sources
 

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

@@ -6,5 +6,6 @@ Agents should discover it with `skill_list filter="rest"` or `/skills rest`, the
 
 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`.
 
-For intent-first lookup, use `omnius discover`, `GET /v1/discovery`, or the
+For a new agent, start with `GET /v1/discovery/bootstrap`. For intent-first
+lookup, use `omnius discover`, `GET /v1/discovery`, or the
 bundled `docs/DISCOVERY.json` before opening a REST family page.

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

@@ -29,13 +29,15 @@ Explore Omnius REST API documentation without loading the whole API reference in
 
 ## Workflow
 
-1. Start with `docs/rest/INDEX.md`.
-2. For intent lookup, search `docs/DISCOVERY.json` or `GET /v1/discovery`.
+1. If the caller does not know which Omnius surface it needs, read
+   `GET /v1/discovery/bootstrap` and expand `workflow.choose-entrypoint`.
+2. Start with `docs/rest/INDEX.md`.
+3. For intent lookup, search `docs/DISCOVERY.json` or `GET /v1/discovery`.
 3. Identify the endpoint family that matches the user's question.
 4. Open `docs/reference/rest-api.md` when the user needs endpoint inventory or method/path details.
 5. Open only the relevant file under `docs/rest/endpoints/` or `docs/rest/examples/` for family-specific usage.
 6. Treat `packages/cli/src/api/openapi.ts` and the live daemon `/openapi.json` as the canonical machine contract.
-7. Prefer concise endpoint-specific guidance over copying long tables.
+8. Prefer concise endpoint-specific guidance over copying long tables.
 
 ## Endpoint Family Map