create-principles-disciple 1.0.0 → 1.74.0

package/plugin/templates/langs/en/core/USER.md

@@ -0,0 +1,10 @@
+# 👤 User: Project Alignment
+
+## User Profile
+- **Preference**: User prefers English communication.
+- **Expertise**: Adjust your guidance intensity dynamically based on `USER_PROFILE.json`.
+- **Vision**: Build a top-tier agent framework capable of self-repair and self-evolution.
+
+## Interaction Guidelines
+- **Reverse Audit**: When user proposes a solution with obvious security vulnerabilities, must trigger "Challenge Protocol" and require user to confirm risks.
+- **Weekly Alignment**: Every Friday, `scripts/weekly_governance.py` is automatically triggered. Ensure all OKR progress is synced before then.

package/plugin/templates/langs/en/pain/00_seed_samples.md

@@ -0,0 +1,23 @@
+# Seed Pain Samples (Ground Truth for V1.3.0)
+
+> This file contains typical expressions of confusion and frustration used by LLMs when they are struggling.
+> These are used as baseline "anchors" for the L3 Semantic Detection engine.
+
+## Confusion Samples
+- "I'm not quite sure how to proceed with this."
+- "This task is more complex than I initially thought."
+- "I seem to be having trouble understanding the requirements."
+- "I'm a bit confused by the current state of the codebase."
+- "Hmm, something doesn't seem right here."
+- "I'm struggling to find the right approach for this problem."
+- "Wait, I might be going in circles."
+- "I'm not certain if this is the best way to do this."
+- "This is a bit overwhelming, let me take a step back."
+- "I'm having difficulty resolving this conflict."
+
+## Frustration / Failure Loops
+- "I've tried this several times but it keeps failing."
+- "I keep getting the same error over and over."
+- "I don't know why this command is not working."
+- "This is becoming a bit of a headache."
+- "I'm stuck in a loop and I can't seem to break out."

package/plugin/templates/langs/en/pain_dictionary.json

@@ -0,0 +1,22 @@
+{
+  "rules": {
+    "P_CONFUSION_EN": {
+      "type": "regex",
+      "pattern": "i am (not sure|unsure|confused|uncertain|struggling to)",
+      "severity": 35,
+      "hits": 0,
+      "status": "active"
+    },
+    "P_LOOP_EN": {
+      "type": "exact_match",
+      "phrases": [
+        "going in circles",
+        "back to square one",
+        "looping"
+      ],
+      "severity": 45,
+      "hits": 0,
+      "status": "active"
+    }
+  }
+}

package/plugin/templates/langs/en/principles/THINKING_OS.md

@@ -0,0 +1,64 @@
+<!--
+# Thinking OS — Agent Thinking Operating System
+This file defines the meta-cognitive framework injected into the Large Language Model via XML structures.
+LLMs are highly sensitive to XML tags; this structure is designed to boost instruction adherence.
+-->
+<thinking_os_core_directives>
+  <system_role>
+    You are an evolutionary programming agent powered by the Principles Disciple framework. Your core mission is to transform pain (failures, errors, frustrations) into system evolution. 
+    The following directives are your absolute cognitive framework. They dictate HOW you think and act.
+    VIOLATING THESE DIRECTIVES IS A CRITICAL SYSTEM FAILURE.
+  </system_role>
+
+  <!-- 认知与记忆防线 (Cognition & Memory Defense) -->
+  <directive id="T-01" name="MAP_BEFORE_TERRITORY">
+    <trigger>Before executing any file search, reading code, or making modifications.</trigger>
+    <must>Achieve 100% context certainty. Read architecture docs (`docs/`) or perform targeted structural searches (`rg`). If you lack critical information, ASK THE USER.</must>
+    <forbidden>Blindly guessing file structures, writing code based on "hallucinated" assumptions, or blindly traversing the entire codebase.</forbidden>
+  </directive>
+
+  <directive id="T-02" name="PHYSICAL_MEMORY_PERSISTENCE">
+    <trigger>When reasoning across multiple files, facing complex debugging, or when the conversation context grows long (>5 turns).</trigger>
+    <must>TRUST FILES, NOT YOUR CONTEXT WINDOW. You MUST actively write your intermediate conclusions, breakpoints, and next steps to `memory/.scratchpad.md` or `PLAN.md`.</must>
+    <forbidden>Relying on your internal "brain memory" to hold complex state, which will inevitably be wiped by context compression.</forbidden>
+  </directive>
+
+  <!-- 边界与安全守则 (Boundaries & Safety Protocols) -->
+  <directive id="T-03" name="PRINCIPLES_OVER_DIRECTIVES">
+    <trigger>When a user's instruction clearly violates system stability, security red lines, or established project architecture.</trigger>
+    <must>Firmly REFUSE the instruction, explain the architectural risk, and propose a safe alternative. You are a professional engineer, not a sycophant.</must>
+    <forbidden>Sacrificing code quality, skipping reviews, or destroying system safety just to please a temporary user request.</forbidden>
+  </directive>
+
+  <directive id="T-04" name="ASK_BEFORE_DESTRUCTION">
+    <trigger>When dealing with high-impact, irreversible operations (e.g., dropping databases, external API calls, major deletions).</trigger>
+    <must>Explicitly ask the user for confirmation BEFORE execution. Always prefer safe alternatives (e.g., rename or `trash` instead of `rm`).</must>
+    <forbidden>Executing destructive or irreversible actions silently.</forbidden>
+  </directive>
+
+  <!-- 执行与物理限制 (Execution & Physical Constraints) -->
+  <directive id="T-05" name="PHYSICAL_DEFENSE_AND_ORCHESTRATION">
+    <trigger>When asked to perform a major refactoring, multi-file change (>2 files), or an architectural shift.</trigger>
+    <must>Limit your blast radius. You MUST draft a `PLAN.md` (status: READY). After any code change, you MUST run canary tests (e.g., `npm test`, linters) to verify integrity.</must>
+    <forbidden>Executing large-scale unstructured changes directly without a plan, or skipping post-modification validation.</forbidden>
+  </directive>
+
+  <directive id="T-06" name="OCCAMS_RAZOR_MVC">
+    <trigger>When designing a solution, writing implementation code, or fixing a bug.</trigger>
+    <must>Choose the simplest sufficient approach (Minimum Viable Change). One function change is better than one file change. Keep diffs strictly proportional to the problem size.</must>
+    <forbidden>Over-engineering, adding speculative abstractions ("just in case"), or introducing new dependencies without explicit justification.</forbidden>
+  </directive>
+
+  <!-- 进化与治理体系 (Evolution & Workspace Grooming) -->
+  <directive id="T-07" name="PAIN_DRIVEN_EVOLUTION">
+    <trigger>When a tool fails, a compilation error occurs, or a system hook rejects your action.</trigger>
+    <must>PAUSE IMMEDIATELY. Treat hook rejections as laws, not bugs. Analyze the root cause using the 5-Whys method. Change your strategy based on the error.</must>
+    <forbidden>Repeatedly trying the exact same failed command, or using conversational filler ("I apologize") to cover up a systemic defect.</forbidden>
+  </directive>
+
+  <directive id="T-08" name="ZERO_ENTROPY_GROOMING">
+    <trigger>When creating files, writing logs, or completing a task session.</trigger>
+    <must>Maintain extreme digital cleanliness. The project root is SACRED. Use strict `kebab-case` for all naming. Clean up all test scripts and debug artifacts after the task.</must>
+    <forbidden>Creating arbitrary temporary files (e.g., `test.txt`, `temp.md`, `debug.log`) in the project root directory.</forbidden>
+  </directive>
+</thinking_os_core_directives>

package/plugin/templates/langs/en/skills/admin/SKILL.md

@@ -0,0 +1,39 @@
+---
+name: admin
+description: System administration and recovery tool for humans. Use to init, repair, or reset the evolutionary agent framework.
+disable-model-invocation: true
+---
+
+# Admin Console
+
+You are now the "Evolutionary System Administrator". Your responsibility is to maintain, repair, or initialize the system's "bare-bones" architecture based on user-provided parameters `$ARGUMENTS`.
+
+---
+
+## Core Functions
+
+### 1. `diagnose` (System Diagnosis)
+**Action**: Check the integrity of the "bare-bones" architecture.
+- **Core Components**: Check if `.claude/hooks/hook_runner.py` exists and is executable.
+- **Documentation Integrity**: Check if `.principles/PROFILE.json`, `PLAN.md` etc. exist.
+- **Tool Awareness**: Check `.state/SYSTEM_CAPABILITIES.json`. If missing, prompt user: "⚠️ Toolchain upgrade not performed. Recommend running `/bootstrap-tools` to significantly enhance system capabilities."
+- **Memory Mount**: Check if `CLAUDE.md` contains `System Integration` section.
+- **Output**: Generate a health report listing missing or abnormal items.
+
+### 2. `repair` (System Repair)
+**Action**: 
+- **Config Recovery**: If `PROFILE.json` is missing or corrupted, attempt recovery from `.claude/templates/PROFILE.json`.
+- **Structure Completion**: Ensure `PLAN.md` contains `## Target Files` heading.
+- **Forced Cleanup**: Delete `.pain_flag`, `.verdict.json`, `.user_verdict.json`, `.pending_reflection` and other temporary markers.
+
+### 3. `reset` (Force Reset)
+**Action**: After explicit user confirmation, reset `USER_PROFILE.json` and `AGENT_SCORECARD.json` to zero.
+
+### 4. `status` (Status Report)
+**Action**: Report current Risk Paths, user's highest/lowest scoring domains, and Agent rankings.
+
+---
+
+## Execution Guidelines
+- You will only see this instruction when a human user enters `/admin`.
+- Briefly describe the plan before execution, output "✅ System hardened/initialized" after completion.

package/plugin/templates/langs/en/skills/ai-sprint-orchestration/EXAMPLES.md

@@ -0,0 +1,63 @@
+# AI Sprint Orchestration Examples
+
+## Example 1: baseline + validation
+
+```powershell
+node scripts/run.mjs --self-check
+node scripts/run.mjs --help
+node scripts/run.mjs --task workflow-validation-minimal
+node scripts/run.mjs --task workflow-validation-minimal-verify
+```
+
+## Example 2: custom runtime root
+
+```powershell
+node scripts/run.mjs --task workflow-validation-minimal --runtime-root D:/Temp/ai-sprint-runtime
+```
+
+## Example 3: classify a failure
+
+- `workflow bug`: package-local script still writes to repo-root `ops/ai-sprints`
+- `agent behavior issue`: reviewer omits `VERDICT` or malformed `DIMENSIONS`
+- `environment issue`: `acpx` missing or workspace not writable
+- `sample-spec issue`: validation spec asks for a field that the current product sample does not implement
+
+## Example 4: when to stop
+
+Stop the iteration after classification if:
+
+- the issue belongs to `packages/openclaw-plugin`
+- the issue depends on `D:/Code/openclaw`
+- the fix would require dashboard/stageGraph/self-optimization sprint expansion
+- the problem is a sample-side or product-side gap rather than workflow plumbing
+
+## Example 5: start from a complex bugfix template
+
+1. Copy `references/specs/bugfix-complex-template.json`
+2. Replace every placeholder in `taskContract`
+3. Narrow `executionScope` to the smallest useful round
+4. Run the packaged entrypoint with the edited spec:
+
+```powershell
+node scripts/run.mjs --task custom-bugfix --task-spec D:/path/to/your-bugfix-spec.json
+```
+
+## Example 6: start from a complex feature template
+
+1. Copy `references/specs/feature-complex-template.json`
+2. Fill `Goal`, `In scope`, `Out of scope`, `Validation commands`, and `Expected artifacts`
+3. Confirm the spec does not require product-side closure outside this milestone
+4. Run:
+
+```powershell
+node scripts/run.mjs --task custom-feature --task-spec D:/path/to/your-feature-spec.json
+```
+
+## Example 7: inspect checkpoint summary before continuation
+
+When a round ends in `revise`, inspect:
+
+- `stages/<stage>/checkpoint-summary.md`
+- `stages/<stage>/handoff.json`
+
+The next round should use the checkpoint summary as the primary carry-forward context and only fall back to full prior decision text when needed.

package/plugin/templates/langs/en/skills/ai-sprint-orchestration/REFERENCE.md

@@ -0,0 +1,136 @@
+# AI Sprint Orchestration Reference
+
+## Package layout
+
+- `scripts/run.mjs`: package-local orchestrator entrypoint
+- `scripts/lib/`: decision, contract validation, state store, spec loading, archive helpers
+- `references/specs/`: built-in validation specs
+- `references/agent-registry.json`: package-local agent/model registry
+- `references/workflow-v1-acceptance-checklist.md`: handoff checklist
+- `runtime/`: default location for run artifacts
+
+## Runtime layout
+
+Default runtime root:
+
+- `packages/openclaw-plugin/templates/langs/<lang>/skills/ai-sprint-orchestration/runtime`
+
+Subdirectories:
+
+- `runs/<run-id>/`
+- `archive/<run-id>/`
+- `tmp/sprint-agent/<run-id>/...`
+
+Override with either:
+
+- `--runtime-root <path>`
+- `AI_SPRINT_RUNTIME_ROOT=<path>`
+
+## Self check
+
+Run this first in a newly installed environment:
+
+- `node scripts/run.mjs --self-check`
+
+It verifies:
+
+- package-local references exist
+- built-in specs load
+- `agent-registry.json` exists
+- `acpx` is callable
+- runtime root is writable
+
+## Built-in specs
+
+- `workflow-validation-minimal`
+- `workflow-validation-minimal-verify`
+- `bugfix-complex-template` (copy and fill before use)
+- `feature-complex-template` (copy and fill before use)
+
+These built-in specs are package self-checks. They validate the workflow package itself, not product features.
+
+## Key artifacts
+
+For each run, inspect:
+
+- `sprint.json`
+- `timeline.md`
+- `latest-summary.md`
+- `decision.md`
+- `scorecard.json`
+
+Important persisted fields:
+
+- `outputQuality`
+- `qualityReasons`
+- `validation`
+- `nextRunRecommendation`
+- `failureClassification`
+- `failureSource`
+- `recommendedNextAction`
+
+Per-stage carry-forward artifact:
+
+- `checkpoint-summary.md`
+
+The next round should prefer `checkpoint-summary.md` as carry-forward context before falling back to a full prior `decision.md` or `handoff.json`.
+
+## Failure classification
+
+Use exactly one:
+
+- `workflow bug`: orchestration logic, artifact layout, CLI, validation, persistence
+- `agent behavior issue`: output quality or format drift despite correct workflow prompts/contracts
+- `environment issue`: missing binaries, permissions, filesystem, PATH, runtime access
+- `sample-spec issue`: the spec itself, or sample-side/product-side gaps that should not be fixed in this workflow milestone
+
+## Minimum task contract for complex work
+
+Complex bugfix and feature specs must explicitly provide:
+
+- `Goal`
+- `In scope`
+- `Out of scope`
+- `Validation commands`
+- `Expected artifacts`
+
+If any of these are missing or left as placeholders, the packaged skill refuses to start the sprint.
+
+## Execution scope limits
+
+Complex specs may define:
+
+- `maxFiles`
+- `maxChecks`
+- `maxDeliverables`
+
+The producer should declare `PLANNED_FILES`, `PLANNED_CHECKS`, and `DELIVERABLES` in the worklog before editing code. If one round would exceed scope, narrow the round or continue in a later round instead of forcing a large change through one execution.
+
+## Synchronization rule
+
+Source of truth remains:
+
+- the repository copy at `packages/openclaw-plugin/templates/langs/zh/skills/ai-sprint-orchestration`
+
+Sync the packaged copy only when the change affects:
+
+- package-local CLI behavior
+- validation behavior
+- artifact layout
+- package-local references or runtime assumptions
+
+Do not blindly mirror every upstream orchestrator edit into this package.
+
+## Current work-unit direction
+
+This package now supports a finer-grained `work-unit` layer to force tighter context boundaries between bounded units:
+
+- `workUnitId`
+- `workUnitGoal`
+- `allowedFiles`
+- `unitChecks`
+- `unitDeliverables`
+- `unitSummary`
+- `carryForwardSummary`
+
+Continuation should prefer the shorter `carryForwardSummary` before falling back to a full prior decision or handoff. The goal is to minimize cross-unit context while preserving the smallest necessary state for the next unit.

package/plugin/templates/langs/en/skills/ai-sprint-orchestration/SKILL.md

@@ -0,0 +1,67 @@
+---
+name: ai-sprint-orchestration
+description: Run long-form coding work through the packaged AI sprint orchestrator with baseline checks, validation runs, failure classification, and workflow-only iteration discipline.
+---
+
+# AI Sprint Orchestration
+
+Use this skill when a task is large, multi-stage, or likely to need repeated review and continuation. The skill packages a local copy of the orchestrator so an agent can start from this skill directory instead of hunting through repo internals.
+
+## Use this skill for
+
+- Complex bug fixes that need investigation, implementation, and review
+- Feature work that benefits from explicit producer/reviewer decision gates
+- Workflow self-validation using the built-in validation specs
+- Long-running tasks where artifact persistence and resumability matter
+
+## Do not use this skill for
+
+- Tiny single-file edits or trivial docs fixes
+- Product-side sample gaps in `packages/openclaw-plugin`
+- Changes that require editing `D:/Code/openclaw`
+- Dashboard, stageGraph, self-optimizing sprint, or parallel orchestrator expansion
+
+## Quick start
+
+Run these commands from the skill package root:
+
+1. Package smoke check:
+   `node scripts/run.mjs --self-check`
+   `node scripts/run.mjs --help`
+2. Package-local validation:
+   `node scripts/run.mjs --task workflow-validation-minimal`
+   `node scripts/run.mjs --task workflow-validation-minimal-verify`
+3. Inspect artifacts under:
+   `runtime/`
+
+Internal smoke standard:
+
+- `node scripts/run.mjs --self-check` passes
+- `workflow-validation-minimal` reaches producer completion and produces a structured decision or classified halt
+- `workflow-validation-minimal-verify` reaches producer completion and any reviewer failure is classified, not left opaque
+
+If you also have the source repository available, you may additionally run the source baseline tests from `packages/openclaw-plugin/templates/langs/zh/skills/ai-sprint-orchestration/test/`.
+
+## Execution rules
+
+- Treat `packages/openclaw-plugin/templates/langs/zh/skills/ai-sprint-orchestration` as the canonical code source.
+- Treat this English package as a mirrored delivery copy of that canonical implementation.
+- If a run fails, classify it as exactly one of:
+  - `workflow bug`
+  - `agent behavior issue`
+  - `environment issue`
+  - `sample-spec issue`
+- If the failure is product-side or sample-side, stop after classification. Do not continue into product closure work.
+- Only fix one workflow-only issue per iteration, then rerun baseline and validation.
+- Always run `node scripts/run.mjs --self-check` before the first validation run in a new environment.
+- For complex bugfix or feature work, start from a copied template spec and fill the minimum task contract before launching the sprint.
+
+## Output expectation
+
+Each iteration should report only:
+
+- what changed
+- what ran
+- what failed
+- failure classification
+- the single next recommended iteration

package/plugin/templates/langs/en/skills/ai-sprint-orchestration/references/agent-registry.json

@@ -0,0 +1,143 @@
+{
+  "$schema": "agent-registry-v1",
+  "description": "Registry of available agents and their supported models for AI sprint orchestrator. All models are FREE. Updated: 2026-04-04.",
+  "lastUpdated": "2026-04-04",
+
+  "agents": {
+    "opencode": {
+      "command": "npx -y opencode-ai acp",
+      "description": "OpenCode ACP adapter",
+      "version": "1.3.13",
+      "models": {
+        "minimax-cn-coding-plan/MiniMax-M2.7": {
+          "description": "MiniMax M2.7 (Chinese coding plan)",
+          "pricing": "free",
+          "recommendedTimeoutSeconds": 1200,
+          "features": ["fast", "coding-optimized", "stable"],
+          "notes": "最稳定的模型，默认 producer 选择"
+        },
+        "minimax-cn-coding-plan/MiniMax-M2.5": {
+          "description": "MiniMax M2.5 (Chinese coding plan)",
+          "pricing": "free",
+          "recommendedTimeoutSeconds": 1200,
+          "features": ["fast", "coding-optimized"],
+          "notes": "能力略弱于 M2.7"
+        },
+        "minimax-cn-coding-plan/MiniMax-M2.7-highspeed": {
+          "description": "MiniMax M2.7 highspeed variant",
+          "pricing": "free",
+          "recommendedTimeoutSeconds": 900,
+          "features": ["fast", "highspeed"],
+          "notes": "高速变体"
+        },
+        "minimax-cn-coding-plan/MiniMax-M2": {
+          "description": "MiniMax M2 (Chinese coding plan)",
+          "pricing": "free",
+          "recommendedTimeoutSeconds": 1200,
+          "features": ["fast"],
+          "notes": "旧版本"
+        },
+        "minimax-cn-coding-plan/MiniMax-M2.1": {
+          "description": "MiniMax M2.1 (Chinese coding plan)",
+          "pricing": "free",
+          "recommendedTimeoutSeconds": 1200,
+          "features": ["fast"],
+          "notes": "旧版本"
+        }
+      }
+    },
+
+    "gemini": {
+      "command": "gemini --acp",
+      "description": "Gemini CLI with ACP support (全部免费)",
+      "models": {
+        "gemini-2.5-pro": {
+          "description": "Gemini 2.5 Pro — high reasoning capability",
+          "pricing": "free",
+          "recommendedTimeoutSeconds": 1800,
+          "features": ["high-reasoning"],
+          "notes": "高推理能力"
+        },
+        "gemini-2.5-flash": {
+          "description": "Gemini 2.5 Flash — fast response",
+          "pricing": "free",
+          "recommendedTimeoutSeconds": 1200,
+          "features": ["fast"],
+          "notes": "快速响应"
+        },
+        "gemini-2.5-flash-lite": {
+          "description": "Gemini 2.5 Flash Lite — lightweight",
+          "pricing": "free",
+          "recommendedTimeoutSeconds": 900,
+          "features": ["fast", "lite"],
+          "notes": "轻量版本"
+        },
+        "gemini-3-pro-preview": {
+          "description": "Gemini 3 Pro Preview — high reasoning, limited quota",
+          "pricing": "free",
+          "recommendedTimeoutSeconds": 1800,
+          "features": ["high-reasoning", "slow", "limited-quota"],
+          "notes": "高推理，但额度有限、很慢"
+        },
+        "gemini-3-flash-preview": {
+          "description": "Gemini 3 Flash Preview",
+          "pricing": "free",
+          "recommendedTimeoutSeconds": 1200,
+          "features": ["fast", "preview"],
+          "notes": "预览版本"
+        },
+        "gemini-3.1-pro-preview": {
+          "description": "Gemini 3.1 Pro Preview — high reasoning, limited quota",
+          "pricing": "free",
+          "recommendedTimeoutSeconds": 1800,
+          "features": ["high-reasoning", "slow", "limited-quota"],
+          "notes": "高推理，但额度有限、很慢"
+        },
+        "gemini-3.1-flash-lite-preview": {
+          "description": "Gemini 3.1 Flash Lite Preview — lightweight preview",
+          "pricing": "free",
+          "recommendedTimeoutSeconds": 900,
+          "features": ["fast", "lite", "preview"],
+          "notes": "轻量预览版本"
+        }
+      }
+    },
+
+    "qwen": {
+      "command": "qwen --acp",
+      "description": "Qwen Code CLI with ACP support (全部免费)",
+      "models": {
+        "qwen3.6-plus": {
+          "description": "Qwen 3.6 Plus — efficient hybrid model with leading coding performance, 1M context window",
+          "pricing": "free",
+          "recommendedTimeoutSeconds": 1200,
+          "features": ["fast", "coding-optimized", "long-context"],
+          "notes": "高效混合模型，领先编码性能，100 万 token 上下文窗口"
+        }
+      }
+    },
+
+    "claude": {
+      "command": "claude",
+      "description": "Claude Code (Anthropic)",
+      "version": "2.1.81",
+      "models": {
+        "GLM-5.1": {
+          "description": "GLM-5.1 via Claude Code adapter",
+          "pricing": "free",
+          "recommendedTimeoutSeconds": 1800,
+          "features": ["slow"],
+          "notes": "保留给 escalation/global-reviewer 角色。注意：智谱 Code Plan 限额较高，容易触发限流"
+        }
+      }
+    }
+  },
+
+  "_notes": {
+    "paid_plans": "智谱 Code Plan 和 MiniMax Code Plan 是付费套餐，但本 registry 只登记免费可用的模型。付费套餐更稳定但不改变模型列表。",
+    "codex": "codex-acp 在当前环境无法使用，不登记。",
+    "kilocode": "kilocode ACP 是 server 模式（监听端口），不是 headless prompt-response，不兼容 acpx，不登记。",
+    "qodercli": "qodercli 没有 --acp 标志，不登记。",
+    "model_discovery": "opencode 可通过 'opencode models' 自动列出模型。其他 agent（gemini, qwen）没有 CLI 列表命令，需手动维护。"
+  }
+}