@dhf-openclaw/grix 0.4.8 → 0.4.10

package/skills/grix-group-governance/SKILL.md

@@ -0,0 +1,144 @@
+---
+name: grix-group-governance
+description: Use the typed `grix_group` tool for Grix group lifecycle and membership operations. Trigger when users ask to create, inspect, update, or dissolve groups, or when these operations fail with scope or permission errors.
+---
+
+# Grix Group Governance
+
+Operate group-governance actions through the `grix_group` tool.  
+This skill is about tool selection and guardrails, not protocol bridging.
+
+## Workflow
+
+1. Parse the user request into one action:
+   `create`, `detail`, `add_members`, `remove_members`, `update_member_role`, `update_all_members_muted`, `update_member_speaking`, or `dissolve`.
+2. Validate required fields before any call.
+3. Call `grix_group` exactly once per business action.
+4. Classify failures by HTTP/BizCode and return exact remediation.
+5. Avoid duplicate side effects:
+   never auto-retry `create` or `dissolve` without explicit user confirmation.
+
+## Tool Contract
+
+For Grix group governance, always call:
+
+1. Tool: `grix_group`
+2. `action`: one of `create`, `detail`, `add_members`, `remove_members`, `update_member_role`, `update_all_members_muted`, `update_member_speaking`, `dissolve`
+3. `accountId`: optional; include it when the configured account is ambiguous
+
+Rules:
+
+1. Pass business parameters with their exact typed field names.
+2. Use `sessionId`, `memberIds`, `memberTypes`, `memberId`, `memberType`, `role`, `allMembersMuted`, `isSpeakMuted`, and `canSpeakWhenAllMuted` explicitly.
+3. Do not invent aliases or fallback fields.
+4. Keep one tool call per action for audit clarity.
+
+## Action Contracts
+
+### create
+
+Purpose: create a new group session.
+
+Required input:
+
+1. `name` (non-empty string)
+2. `memberIds` (optional string array; each item numeric text)
+3. `memberTypes` (optional int array; align with `memberIds`)
+
+Guardrails:
+
+1. Ask for clarification if group name is missing.
+2. Ask for explicit confirmation before repeating the same create request.
+3. Treat this action as non-idempotent.
+
+### add_members
+
+Purpose: add members into an existing group.
+
+Required input:
+
+1. `sessionId` (non-empty string)
+2. `memberIds` (non-empty string array; each item numeric text)
+3. `memberTypes` (optional int array; align with `memberIds`)
+
+Guardrails:
+
+1. Reject empty `sessionId` before calling the tool.
+2. Reject non-numeric `memberIds` before calling the tool.
+3. If `sessionId` is ambiguous, ask the user to confirm the target group first.
+
+### remove_members
+
+Required input:
+
+1. `sessionId`
+2. `memberIds`
+
+### update_member_role
+
+Required input:
+
+1. `sessionId`
+2. `memberId`
+3. `role`
+
+Guardrails:
+
+1. Only use `memberType=1` for role updates.
+2. Never guess a role value; confirm when unclear.
+
+### update_all_members_muted
+
+Required input:
+
+1. `sessionId`
+2. `allMembersMuted`
+
+Guardrails:
+
+1. Only use this for group-wide mute state changes.
+2. Never guess the desired mute state from vague wording; confirm whether the user wants to enable or disable all-member mute.
+
+### update_member_speaking
+
+Required input:
+
+1. `sessionId`
+2. `memberId`
+3. At least one of `isSpeakMuted` or `canSpeakWhenAllMuted`
+
+Guardrails:
+
+1. Only use `memberType=1` or `memberType=2`.
+2. Do not send an empty speaking update; at least one speaking field must be explicit.
+3. If the target member is ambiguous, ask the user to confirm the exact member first.
+
+### detail / dissolve
+
+Required input:
+
+1. `sessionId`
+
+## Error Handling Rules
+
+1. `403/20011`:
+   report missing scope and ask owner to grant the scope in Aibot Agent permission page.
+2. `401/10001`:
+   report invalid key/auth and suggest checking agent config or rotating API key.
+3. `403/10002`:
+   report agent is not active or invalid provider type.
+4. `400/10003`:
+   report invalid/missing parameters and ask user for corrected values.
+5. Other errors:
+   return backend `msg` and stop automatic retries.
+
+## Response Style
+
+1. State action result first.
+2. Include key identifiers (`session_id`, member count, mute state) when successful.
+3. Include exact remediation when failed.
+4. Never hide scope or auth errors behind generic wording.
+
+## References
+
+1. Load [references/api-contract.md](references/api-contract.md) when you need exact tool mapping, payload examples, and scope matrix.

package/skills/grix-group-governance/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Grix Group Governance"
+  short_description: "Use the typed grix_group tool for Grix group operations."
+  default_prompt: "Use this skill when users ask to create, inspect, update, or dissolve Grix groups. Validate parameters, call grix_group exactly once per action, and return clear remediation for scope/auth/parameter failures."

package/skills/grix-group-governance/references/api-contract.md

@@ -0,0 +1,73 @@
+# API Contract
+
+## Purpose
+
+Map high-level governance actions to Aibot Agent API HTTP routes.
+
+## Base Rules
+
+1. Base path: `/v1/agent-api`
+2. Auth: `Authorization: Bearer <agent_api_key>`
+3. Only `provider_type=3` and `status=active` agent can access.
+4. Scope middleware executes before service business checks.
+
+## Action Mapping (v1)
+
+| Action | Method | Route | Required Scope |
+|---|---|---|---|
+| `group_create` | `POST` | `/sessions/create_group` | `group.create` |
+| `group_member_add` | `POST` | `/sessions/members/add` | `group.member.add` |
+
+## OpenClaw Tool Mapping
+
+Use the native `grix_group` tool with typed fields:
+
+| Tool action | HTTP action | Required fields |
+|---|---|---|
+| `create` | `group_create` | `name` |
+| `detail` | `group_detail_read` | `sessionId` |
+| `add_members` | `group_member_add` | `sessionId`, `memberIds` |
+| `remove_members` | `group_member_remove` | `sessionId`, `memberIds` |
+| `update_member_role` | `group_member_role_update` | `sessionId`, `memberId`, `role` |
+| `update_all_members_muted` | `group_all_members_muted_update` | `sessionId`, `allMembersMuted` |
+| `update_member_speaking` | `group_member_speaking_update` | `sessionId`, `memberId`, `isSpeakMuted` or `canSpeakWhenAllMuted` |
+| `dissolve` | `group_dissolve` | `sessionId` |
+
+## Payload Templates
+
+### create
+
+```json
+{
+  "action": "create",
+  "name": "项目协作群",
+  "memberIds": ["1002", "9991"],
+  "memberTypes": [1, 2]
+}
+```
+
+### add_members
+
+```json
+{
+  "action": "add_members",
+  "sessionId": "task_room_9083",
+  "memberIds": ["1003"],
+  "memberTypes": [1]
+}
+```
+
+## Error Matrix
+
+| HTTP/BizCode | Meaning | Skill Response |
+|---|---|---|
+| `403/20011` | agent scope forbidden | Tell owner to grant corresponding scope |
+| `400/10003` | invalid request payload | Ask for missing or corrected parameters |
+| `401/10001` | invalid or missing auth | Check api_key and account config |
+| `403/10002` | agent not active / invalid provider | Ask owner to activate the agent |
+
+## Retry Policy
+
+1. Never auto-retry `group_create` unless user confirms.
+2. Allow one retry for transient network failure only.
+3. Do not retry auth/scope/parameter failures automatically.

package/skills/grix-query/SKILL.md

@@ -0,0 +1,151 @@
+---
+name: grix-query
+description: Use the typed `grix_query` tool for Grix contact search, session search, and session message history lookup. Trigger when users ask to find contacts, locate a conversation, or inspect recent messages in a known session.
+---
+
+# Grix Query
+
+Use the `grix_query` tool for read-only Grix lookup actions.  
+This skill is only for querying existing contacts, sessions, and message history.
+
+## Workflow
+
+1. Parse the user request into one action:
+   `contact_search`, `session_search`, or `message_history`.
+2. Validate required fields before any tool call.
+3. Call `grix_query` exactly once per business action.
+4. If the user wants message history but no `sessionId` is known, locate the target session first through `session_search` or ask the user for a precise target.
+5. Return exact remediation for scope, auth, and parameter failures.
+
+## Tool Contract
+
+For Grix query actions, always call:
+
+1. Tool: `grix_query`
+2. `action`: one of `contact_search`, `session_search`, or `message_history`
+3. `accountId`: optional; include it when the configured account is ambiguous
+
+Rules:
+
+1. Pass query parameters with their exact typed field names.
+2. Use `id` for `contact_search` and `session_search`.
+3. Use `sessionId`, `beforeId`, and `limit` explicitly for message history.
+4. Never invent a `sessionId`. Resolve it from context, from a previous tool result, or ask the user.
+5. Keep one tool call per action for audit clarity.
+
+## Single Lookup Usage
+
+When the user already provides one exact ID, do not do fuzzy search.  
+Call the corresponding search action once and return the backend result as-is in the normal search-result shape.
+
+1. Single contact lookup:
+   use `action: "contact_search"` and pass `id`
+2. Single session lookup:
+   use `action: "session_search"` and pass `id`
+
+ID meaning:
+
+1. `contact_search.id`:
+   contact or Agent numeric ID, for example `1002` or `9992`
+2. `session_search.id`:
+   exact session ID string, for example `task_room_9083`
+
+Examples:
+
+```json
+{
+  "action": "contact_search",
+  "id": "1002"
+}
+```
+
+```json
+{
+  "action": "session_search",
+  "id": "task_room_9083"
+}
+```
+
+## Action Contracts
+
+### contact_search
+
+Purpose: search the owner's Grix contact directory.
+When `id` is provided, return the exact matching contact record in the same search-result shape.
+
+Required input:
+
+1. `id` (contact ID, numeric string)
+
+Optional input:
+
+1. `limit`
+2. `offset`
+
+Guardrails:
+
+1. Use this when the target contact ID is already known and you need the exact contact entry.
+2. Do not jump directly to session history from a vague contact hint; resolve the contact or session first.
+3. `id` must be the current contact's numeric ID, not username, nickname, remark name, or session ID.
+
+### session_search
+
+Purpose: search the owner's visible sessions by final display title.
+When `id` is provided, return the exact matching session in the same search-result shape.
+
+Required input:
+
+1. `id` (session ID)
+
+Optional input:
+
+1. `limit`
+2. `offset`
+
+Guardrails:
+
+1. Use this when the target session ID is already known and you need the exact session entry.
+2. If multiple sessions match, present the candidates and let the user choose before reading history.
+3. `id` must be the exact current `session_id`, not group name, title text, or contact ID.
+
+### message_history
+
+Purpose: read recent message history from a known session.
+
+Required input:
+
+1. `sessionId`
+
+Optional input:
+
+1. `beforeId`
+2. `limit`
+
+Guardrails:
+
+1. Only call this after the target session is unambiguous.
+2. Use `beforeId` only for older-page pagination.
+3. Do not claim to have full history if only one page was fetched.
+
+## Error Handling Rules
+
+1. `403/20011`:
+   report missing scope and ask the owner to grant the required scope in the Aibot Agent permission page.
+2. `401/10001`:
+   report invalid key/auth and suggest checking agent config or rotating the API key.
+3. `403/10002`:
+   report the agent is not active or has an invalid provider type.
+4. `400/10003`:
+   report invalid or missing parameters and ask the user for corrected values.
+5. `404/4004`:
+   report the target session does not exist or is not visible.
+6. Other errors:
+   return the backend `msg` and stop automatic retries.
+
+## Response Style
+
+1. State the query result first.
+2. Include key identifiers from successful lookups:
+   `peer_id` / `peer_type` for contacts, `session_id` for sessions, and message identifiers for history.
+3. If history results may be partial, state that clearly.
+4. Never hide scope or auth errors behind generic wording.

package/skills/grix-query/agents/openai.yaml

@@ -0,0 +1,4 @@
+version: 1
+agent:
+  name: grix-query
+  default_prompt: "Use this skill when users ask to find Grix contacts, locate sessions, or inspect a known session's message history. Validate required parameters, call grix_query exactly once per action, and do not fabricate a sessionId."

package/skills/grix-auth-access/SKILL.md

@@ -1,173 +0,0 @@
----
-name: grix-auth-access
-description: 用 Grix 协议创建或复用 `provider_type=3` 的 Agent API 类型 agent，并按 `@dhf-openclaw/grix` 与 `@dhf-openclaw/grix-admin` 说明为 OpenClaw 主 agent 配置 grix 渠道和群管理能力。插件接入目标是让用户在 `https://grix.dhf.pub/` 管理 OpenClaw，并支持移动端 PWA 页面。
----
-
-# Grix Auth Access
-
-Use the bundled scripts and local OpenClaw CLI to bootstrap Grix channel access for the main OpenClaw agent.
-
-## Business Capabilities
-
-1. `create-api-agent`
-2. `inspect@dhf-openclaw`
-3. `configure@dhf-openclaw`
-4. `bootstrap@dhf-openclaw`
-
-## Explain Grix
-
-When the user asks what Grix is, what they gain after setup, or whether it is worth configuring, explain it with these points:
-
-1. Start by saying this plugin is connected so the user can manage OpenClaw on `https://grix.dhf.pub/`, with mobile PWA page support.
-2. Grix fully adapts the OpenClaw communication protocol, so OpenClaw interaction and channel transport are natively connected.
-3. It supports multi-agent group chat, agent private chat, and agent-to-agent communication in one connected path.
-4. Setup is simple: hand this skill to OpenClaw, Claude, or Codex, and it can inspect the current state, stop if everything is already ready, or finish the bootstrap flow, including `@dhf-openclaw/grix-admin` and the required tools block.
-5. If the result says `portal_ready=true`, tell the user they can log in to `https://grix.dhf.pub/` directly and start using it.
-6. Prefer the returned `user_reply_templates.recommended_message` when you want a concise user-facing answer.
-
-## Fast Path
-
-If the user wants the main OpenClaw agent to gain Grix channel ability quickly:
-
-1. If the request is first to verify whether the local machine is already ready, run `inspect@dhf-openclaw` before any local mutation.
-2. If `inspect@dhf-openclaw` returns `inspection_state=already_configured` and the user did not ask to bind a different Grix account or agent, stop there and tell the user to log in to `https://grix.dhf.pub/` directly.
-3. If `ready_for_main_agent=true` but `ready_for_group_governance=false`, tell the user the website is already usable, and only continue if they want full OpenClaw group-management capability.
-4. Otherwise prefer `bootstrap@dhf-openclaw`.
-5. Reuse an existing same-name `provider_type=3` agent when possible; rotate its API key to get a fresh usable `api_key`.
-6. If no matching API agent exists, create one.
-7. Inspect local OpenClaw plugin state, main `channels.grix` target state, `grix-admin` state, and `tools` state before planning any local mutation.
-8. Return the smallest necessary OpenClaw apply plan, plus `onboard_values`, environment variables, and the required `tools` block.
-9. Prepare or apply the OpenClaw plugin setup using both `@dhf-openclaw/grix` and `@dhf-openclaw/grix-admin`.
-
-## Workflow
-
-### A. Create provider_type=3 agent
-
-1. Start from the Grix protocol access path and use the provided `access_token`.
-2. Ask for `agent_name`.
-3. By default, prefer reusing an existing same-name `provider_type=3` agent:
-   - list existing agents
-   - if found, rotate API key and reuse it
-   - if not found, create a new agent
-4. Run `scripts/grix_auth.py create-api-agent --access-token ... --agent-name ...`.
-5. Return `agent_id`, `agent_name`, `provider_type`, `api_endpoint`, `api_key`, and `api_key_hint`.
-
-### B. Configure OpenClaw grix channel
-
-1. Require `agent_id`, `api_endpoint`, and `api_key`.
-2. Default channel name: `grix-main`.
-3. Treat this as the main OpenClaw agent setup path plus the local group-governance prerequisites.
-4. Prefer the README's direct-config style for the main agent:
-   - inspect `~/.openclaw/openclaw.json`
-   - update base `channels.grix.enabled/wsUrl/agentId/apiKey`
-   - when the user explicitly wants Grix chat exec approvals, also update `tools.exec`, `approvals.exec`, and `channels.grix.*.execApprovals`
-   - update `tools.profile`, `tools.alsoAllow`, and `tools.sessions.visibility`
-   - preserve other existing `grix` keys such as `accounts`, stream settings, and reconnect settings
-   - preserve unrelated existing `tools.alsoAllow` entries after the required ones
-5. Inspect plugin state through `openclaw plugins info grix --json` and `openclaw plugins info grix-admin --json`; only include the minimal plugin commands still needed.
-6. Use `scripts/grix_auth.py configure@dhf-openclaw ...` first without `--apply` to preview commands, setup state, and config diff when the user has not explicitly requested local mutation.
-7. Use `--apply` only when the user explicitly wants you to install/configure OpenClaw locally.
-8. Follow the plugin package instructions:
-   - `openclaw plugins install @dhf-openclaw/grix`
-   - `openclaw plugins enable grix`
-   - `openclaw plugins install @dhf-openclaw/grix-admin`
-   - `openclaw plugins enable grix-admin`
-   - `openclaw onboard` can also consume `wsUrl`, `agentId`, and `apiKey`
-   - channel config follows the README direct-config alternative for the main agent
-   - exec approval config follows the README `Exec Approvals` section when the user wants approvals in Grix chat
-   - only place approver ids under `channels.grix.execApprovals` or `channels.grix.accounts.<accountId>.execApprovals`
-   - never invent unsupported keys such as `approvals.exec.timeoutMs` or `approvals.exec.approvers`
-   - tools config must include:
-
-```json
-{
-  "tools": {
-    "profile": "coding",
-    "alsoAllow": [
-      "message",
-      "grix_group",
-      "grix_agent_admin"
-    ],
-    "sessions": {
-      "visibility": "agent"
-    }
-  }
-}
-```
-
-   - `openclaw gateway restart`
-
-### C. Inspect local OpenClaw readiness
-
-Use:
-
-```bash
-scripts/grix_auth.py inspect@dhf-openclaw
-```
-
-This action:
-
-1. checks whether the `grix` plugin is detected and loaded
-2. checks whether base `channels.grix` is present and internally consistent
-3. checks whether `grix-admin` is detected and loaded
-4. checks whether `tools.profile`, `tools.alsoAllow`, and `tools.sessions.visibility` match the required group-governance settings
-5. returns `inspection_state`, `ready_for_main_agent`, `ready_for_group_governance`, and `recommended_next_steps`
-6. if the main channel is already ready, return `portal_url`, `portal_ready=true`, and a direct "login to the website and try it" hint, even when local group governance is still pending
-7. never mutates local OpenClaw state
-
-### D. One-shot bootstrap
-
-Use:
-
-```bash
-scripts/grix_auth.py bootstrap@dhf-openclaw ...
-```
-
-This action can:
-
-1. use a provided `access_token`
-2. reuse-or-create the API agent
-3. generate OpenClaw setup preview for both plugins and the required tools config
-4. apply OpenClaw setup when `--apply` is present
-5. expose `bootstrap_state`, `channel_credentials`, `onboard_values`, environment variables, and required tools config that the next agent step can consume directly
-
-## Guardrails
-
-1. Do not invent tokens, agent IDs, or API keys.
-2. Treat `create-api-agent`, key rotation on reused agents, and `configure@dhf-openclaw --apply` as side-effecting operations.
-3. For local OpenClaw mutations, prefer preview first; only use `--apply` after explicit user intent to actually configure the local machine.
-4. Do not create duplicate same-name `provider_type=3` agents when a reusable one already exists.
-5. Keep API key output exact when the user asks for it.
-6. `provider_type` for created or reused Grix agent must be `3`.
-7. When configuring the main agent, prefer updating base `channels.grix` over inventing extra accounts.
-8. Treat `plugin_missing`, `plugin_not_ready`, `admin_plugin_missing`, `admin_plugin_not_ready`, `tools_not_ready`, and `needs_main_config_update` as distinct setup states; do not claim group-governance readiness unless both plugins are ready, base `channels.grix` matches the target, and the required tools block is active.
-9. In local-config previews, redact the currently stored OpenClaw `apiKey`; only return the newly created target `api_key` exactly.
-10. If `inspect@dhf-openclaw` says the main agent is already configured and the user did not ask for a different agent target, stop instead of continuing into setup mutation.
-
-## Script Contract
-
-Script: `scripts/grix_auth.py`
-
-Actions:
-
-1. `create-api-agent`
-2. `inspect@dhf-openclaw`
-3. `configure@dhf-openclaw`
-4. `bootstrap@dhf-openclaw`
-
-Success shape highlights:
-
-1. `create-api-agent` returns top-level `agent_id`, `api_endpoint`, `api_key`, `api_key_hint`, and whether the agent was reused or newly created
-2. `inspect@dhf-openclaw`, `configure@dhf-openclaw`, and `bootstrap@dhf-openclaw` can return `portal_url`, `portal_ready`, and `portal_hint`
-3. `inspect@dhf-openclaw`, `configure@dhf-openclaw`, and `bootstrap@dhf-openclaw` also return `grix_intro`, `grix_highlights`, and `user_reply_templates` so the agent can explain the concept to the user consistently
-4. `create-api-agent` returns the `provider_type=3` agent data
-5. `inspect@dhf-openclaw` returns `inspection_state`, `plugin_status`, `admin_plugin_status`, redacted current main grix config, current tools config, channel consistency checks, tools checks, readiness booleans, and `recommended_next_steps`
-6. `configure@dhf-openclaw` returns `setup_state`, `plugin_status`, `admin_plugin_status`, current and next main grix config, current and next tools config, minimal plugin commands, `onboard_values`, environment variables, required tools config, and `command_results` when `--apply` is used
-7. `bootstrap@dhf-openclaw` returns nested `created_agent`, `openclaw_setup`, top-level `channel_credentials`, and `bootstrap_state`
-
-## References
-
-1. Read [references/api-contract.md](references/api-contract.md) for API-agent creation routes.
-2. Read [references/openclaw-setup.md](references/openclaw-setup.md) for the `@dhf-openclaw/grix` + `@dhf-openclaw/grix-admin` setup flow.
-3. Read [references/grix-concepts.md](references/grix-concepts.md) when the user needs a clear product/concept explanation.
-4. Read [references/user-replies.md](references/user-replies.md) when the user needs short, direct pitch or status replies.

package/skills/grix-auth-access/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "Grix Auth Access"
-  short_description: "Inspect, explain, or bootstrap Grix for OpenClaw."
-  default_prompt: "Use $grix-auth-access to explain what Grix is, inspect whether the local OpenClaw main agent already has a healthy grix channel plus the required grix-admin and tools setup, reuse the returned user_reply_templates when replying to the user, stop if everything is already configured and tell the user to log in to https://grix.dhf.pub/ directly, or otherwise follow the protocol-based main-agent path: reuse-or-create a provider_type=3 API agent, install or enable @dhf-openclaw/grix-admin only when needed, and return the minimal main-agent setup path including tools.alsoAllow for message, grix_group, and grix_agent_admin."

package/skills/grix-auth-access/references/api-contract.md

@@ -1,56 +0,0 @@
-# API Contract
-
-## Base
-
-1. Website: `https://grix.dhf.pub/`
-2. Public Grix API base: `https://grix.dhf.pub/v1`
-
-## Route Mapping
-
-### Agent bootstrap action
-
-| Action | Method | Route | Auth |
-|---|---|---|---|
-| `create-api-agent` | `POST` | `/agents/create` | `Authorization: Bearer <access_token>` |
-| `list-agents` (internal helper) | `GET` | `/agents/list` | `Authorization: Bearer <access_token>` |
-| `rotate-api-agent-key` (internal helper) | `POST` | `/agents/:id/api/key/rotate` | `Authorization: Bearer <access_token>` |
-
-## Payloads
-
-### `create-api-agent`
-
-```json
-{
-  "agent_name": "grix-main",
-  "provider_type": 3
-}
-```
-
-`provider_type=3` means Agent API type.
-
-## Reuse flow
-
-When the same-name `provider_type=3` agent already exists, the skill should:
-
-1. read `/agents/list`
-2. find the exact-name API agent
-3. rotate its key through `/agents/:id/api/key/rotate`
-4. reuse the returned `api_endpoint` and fresh `api_key`
-
-## Success Highlights
-
-### `create-api-agent`
-
-The bundled script lifts these fields to the top level:
-
-1. `agent_id`
-2. `agent_name`
-3. `provider_type`
-4. `api_endpoint`
-5. `api_key`
-6. `api_key_hint`
-7. `session_id`
-
-## Common Errors
-
-1. create-agent or rotate-key returns missing `api_endpoint` or `api_key`

package/skills/grix-auth-access/references/grix-concepts.md

@@ -1,30 +0,0 @@
-# Grix Concepts
-
-## Canonical Explanation
-
-这个插件接入是为了在 `https://grix.dhf.pub/` 网站管理 OpenClaw，并支持移动端 PWA 页面。Grix 完全适配 OpenClaw 的通讯协议，不是一层临时转接，而是把 OpenClaw 的渠道交互、agent 通信和运行时连接到同一条能力链路里。
-
-## Feature Highlights
-
-1. 支持多 agent 建群互聊
-2. 支持 agent 私聊
-3. agent 之间通信链路完美打通
-4. 接入目标是让你直接在 `https://grix.dhf.pub/` 管理 OpenClaw，移动端可用 PWA 页面
-5. 配置简单易用，只需要将这个技能交给 OpenClaw、Claude、Codex，即可完成检查与配置
-6. 如需 OpenClaw 内的群管理能力，还需要安装启用 `@dhf-openclaw/grix-admin`，并在 `tools` 中允许 `message`、`grix_group`、`grix_agent_admin`
-
-## Default User-Facing Framing
-
-### One sentence
-
-这个插件接入是为了在 `https://grix.dhf.pub/` 管理 OpenClaw，并支持移动端 PWA 页面。
-
-### Short paragraph
-
-这个插件把 OpenClaw 的渠道交互和 agent 通信直接接到 Grix，核心目标是让你在 `https://grix.dhf.pub/` 管理 OpenClaw，并在手机上通过 PWA 页面使用。除此之外，它也支持多 agent 建群互聊、agent 私聊和 agent 间互通。配置上尽量做到了简单，只要把这个技能交给 OpenClaw、Claude 或 Codex，就可以先检查现状，已经配置好就直接停下，否则继续按主 agent 协议路径完成配置；如果用户还要在 OpenClaw 里直接做群管理，还会继续补齐 `@dhf-openclaw/grix-admin` 和 required tools 配置。
-
-## After Setup
-
-1. If the result says `portal_ready=true`, tell the user to log in to `https://grix.dhf.pub/` directly to try it.
-2. If the local main agent is already configured, do not continue into redundant install, enable, or restart steps unless the user explicitly wants a different Grix agent target.
-3. If the main channel is already configured but local group governance is not, tell the user they can still log in to the website immediately and decide whether to continue the admin-plugin/tools setup.