artifact-chain-assistant 0.9.3 → 0.10.0

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "artifact-chain-assistant",
-  "version": "0.9.3",
+  "version": "0.10.0",
   "description": "Artifact-chain intake, review/repair/batch/audit workflows, diagnostics, hooks, and version-lock maintenance helpers.",
   "author": {
     "name": "广州市风荷科技有限公司"

package/.codex-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "artifact-chain-assistant",
   "displayName": "Artifact Chain Assistant",
-  "version": "0.9.3",
+  "version": "0.10.0",
   "description": "Artifact-chain intake, review/repair/batch/audit workflows, diagnostics, and version-lock maintenance helpers.",
   "author": {
     "name": "广州市风荷科技有限公司"

package/.kimi-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "artifact-chain-assistant",
-  "version": "0.9.3",
+  "version": "0.10.0",
   "description": "Artifact-chain intake, review/repair/batch/audit workflows, diagnostics, and version-lock maintenance helpers.",
   "author": {
     "name": "广州市风荷科技有限公司"

package/CHANGELOG.md

@@ -1,5 +1,42 @@
 # Changelog
 
+## 0.10.0
+
+### Added
+
+- Added the product-owned setup runner and entry-discovery contract to every generated Codex,
+  Claude Code, and Kimi Code surface. Setup reports native-binding failures from structured doctor
+  output and keeps bootstrap behind explicit write authorization.
+
+### Changed
+
+- Aligned the existing 16-entry method catalog, generated host surfaces, and documentation with the
+  canonical `help`, `quickstart`, and `setup` entry semantics.
+- Runtime compatibility, installation commands, plugin manifests, Family API metadata, and adapter
+  catalogs are synchronized with `artifact-graph@0.10.0`.
+
+### Fixed
+
+- Entry skills resolve shared scripts from the installed plugin root. Their behavior no longer
+  depends on the target project's working directory or a parent-repository layout.
+
+## 0.9.4
+
+### Added
+
+- Qoder can consume the existing root plugin package as a skills-only host. This compatibility
+  path reuses the shared skills and does not add a Qoder-specific adapter, manifest, commands,
+  hooks, or settings.
+
+### Changed
+
+- Host smoke verification now confirms that Qoder's reported install path is isolated and contains
+  the shared runtime resource closure plus every expected skill entry point.
+- Shared skill descriptions use host-neutral language where the workflow is not specific to Codex,
+  so the same guidance remains accurate in Qoder and other supported hosts.
+- Runtime compatibility and generated plugin manifests are synchronized with
+  `artifact-graph@0.9.4`.
+
 ## 0.9.3
 
 ### Changed

package/INSTALL.md

@@ -2,18 +2,20 @@
 
 This guide separates two responsibilities:
 
-1. Install the assistant plugin into Codex and/or Claude Code.
+1. Install the assistant plugin into Codex, Claude Code, Kimi Code, or Qoder.
 2. Prepare each target project so the plugin has a project-local artifact chain to manage.
 
 Codex exposes `.codex-plugin/plugin.json` and `skills/**` only. Claude Code also exposes slash
-command wrappers and a Stop-hook guardrail. Neither host surface replaces Git hooks or CI: those
+command wrappers and a Stop-hook guardrail. Qoder currently runs in skill-compatible mode: it
+installs and discovers the shared skills but does not receive slash command wrappers or the
+Stop-hook guardrail (see [Qoder](#qoder)). Neither host surface replaces Git hooks or CI: those
 remain the hard gates for a target project's artifacts, graph config, version lock, and project
 instructions.
 
 ## Prerequisites
 
 - Node.js `>=22.0.0`.
-- `artifact-graph` 0.9.3 installed in the target project.
+- `artifact-graph` 0.10.0 installed in the target project.
 - **GitHub SSH key** — Claude Code clones `source: github` entries over SSH by default. If you
   have not configured a GitHub SSH key, set `CLAUDE_CODE_PLUGIN_PREFER_HTTPS=1` in your shell
   profile, or add the marketplace with an explicit `https://` URL. Codex users can check
@@ -25,24 +27,24 @@ instructions.
 
 | Plugin | Verified Runtime | Install |
 | --- | --- | --- |
-| `artifact-chain-assistant` 0.9.3 | `artifact-graph` 0.9.3 | `pnpm add -D artifact-graph@0.9.3` |
+| `artifact-chain-assistant` 0.10.0 | `artifact-graph` 0.10.0 | `pnpm add -D artifact-graph@0.10.0` |
 
 ### Install The Runtime
 
 The default installation path uses the npm registry with a precise version:
 
 ```bash
-pnpm add -D artifact-graph@0.9.3
+pnpm add -D artifact-graph@0.10.0
 ```
 
 If the npm registry is unavailable, use the explicit GitHub fallback pinned to the verified tag:
 
 ```bash
-pnpm add -D github:ifoohoo/artifact-graph#artifact-graph-v0.9.3
+pnpm add -D github:ifoohoo/artifact-graph#artifact-graph-v0.10.0
 ```
 
 > **Never** install with an unlocked range (`artifact-graph`, `artifact-graph@latest`,
-> `artifact-graph@^0.9.3`) or an unpinned GitHub URL (`github:ifoohoo/artifact-graph`).
+> `artifact-graph@^0.10.0`) or an unpinned GitHub URL (`github:ifoohoo/artifact-graph`).
 > Unlocked installs produce non-reproducible dependency trees and break version-lock audit.
 
 With pnpm 10+, projects that install `artifact-graph` must allow the native `better-sqlite3`
@@ -69,7 +71,7 @@ allowBuilds:
 
 The plugin's `doctor` command validates the installed runtime version before running any
 diagnostic. If it detects a version mismatch or missing CLI, it reports the exact remediation
-command (`pnpm add -D artifact-graph@0.9.3`) and exits non-zero.
+command (`pnpm add -D artifact-graph@0.10.0`) and exits non-zero.
 
 ### CLI Resolution Order
 
@@ -144,7 +146,7 @@ wrappers, and Stop-hook guardrail. These assistant controls do not replace Git h
 
 > **Marketplace note**: `ifoohoo/artifact-skill-set` is an external independent marketplace. The
 > plugin payload is still published from `ifoohoo/artifact-chain-assistant`. The marketplace entry
-> must publish and enable `artifact-chain-assistant` 0.9.3 before the install commands above will
+> must publish and enable `artifact-chain-assistant` 0.10.0 before the install commands above will
 > succeed.
 
 ### Kimi Code
@@ -171,19 +173,56 @@ skills, and managed scripts (`doctor.mjs`, `check-workflow-profile.mjs`, `run-ar
 non-interactive install CLI, so automated install verification is limited to layout checks;
 use `artifact-chain-maintainer` to guide version-lock CLI operations.
 
+### Qoder
+
+Qoder is currently supported as a **skill-compatible host**, not as a fourth adapter. It reuses the
+existing `artifact-skill-set` marketplace: Qoder recognizes the root
+`.claude-plugin/marketplace.json` and installs the shared plugin root (`skills/**`), so no
+Qoder-specific manifest or duplicated runtime assets are required.
+
+Register the marketplace and install the plugin (illustrative commands):
+
+```bash
+qodercli plugin marketplace add ifoohoo/artifact-skill-set --scope user
+qodercli plugin install artifact-chain-assistant@artifact-skill-set --scope user --json
+qodercli plugin list --json
+```
+
+> The exact flags may change between Qoder CLI releases. Treat the commands above as
+> illustrations and confirm against `qodercli plugin ... --help` at execution time.
+
+Current support boundary:
+
+- **Committed**: plugin installation and shared skill discovery. Qoder installs
+  `artifact-chain-assistant` from the marketplace and discovers the shared `skills/` entries.
+- **Not committed**: Claude Code slash command wrappers and the Stop-hook guardrail are not
+  provided for Qoder. `commands` and `hooks` being empty in `plugin list --json` is expected,
+  not a defect.
+
+Verify an installation with `qodercli plugin list --json`: confirm the installed version, that the
+plugin is enabled, that `installPath` points at the expected location, and that the `skills` list
+matches the shared skill set. Diagnostics still use the plugin root `scripts/doctor.mjs` — resolve
+the installed root from the `installPath` reported by `plugin list --json`, then run
+`node "$PLUGIN_ROOT/scripts/doctor.mjs" --root . --format json`. There is no Qoder-specific
+adapter doctor.
+
 ## Post-Installation Discovery
 
 After installing the plugin, use these entry points to understand available capabilities:
 
-1. **`help`** — Run this skill to see the standard Family API catalog and bundled legacy methods.
-   It shows what families and services the plugin provides, without claiming any are installed, enabled, or verified
-   for your project. Installation of the plugin does NOT mean families are bound or providers are active.
+1. **`help`** — Run this skill when you ask "what can this plugin do" or "how does the artifact
+   chain work". It shows the standard Family API catalog and bundled legacy methods — the plugin's
+   capabilities and what the artifact chain is for — without claiming any are installed, enabled, or
+   verified for your project. Installation of the plugin does NOT mean families are bound or providers
+   are active. If the Registry is missing, it still runs and honestly lists which standard services
+   are not yet executable.
 
-2. **`setup`** — Run this skill for read-only environment diagnostics: plugin closure integrity, Node/CLI
+2. **`setup`** — Run this skill when you ask "is my environment ready". It performs read-only
+   environment diagnostics: plugin closure integrity, Node/CLI
    availability, doctor output, project config, version lock, and registry availability. It outputs a structured status
    report with PASS/WARN/FAIL for each check plus precise next steps, and writes nothing without explicit authorization.
 
-3. **`quickstart`** — Run this skill when unsure which skill to use. It routes your intent to the correct skill:
+3. **`quickstart`** — Run this skill when getting started or unsure which skill to use. It routes your intent to the correct skill via a deterministic routing table covering common Chinese/English requests:
    capability questions go to `help`, environment checks to `setup`, initialization to `setup` then bootstrap,
    project triage to `where-am-i`, maintenance to `maintainer`, and explicit artifact tasks to the matching family/service.
 
@@ -218,7 +257,7 @@ The plugin should not move these files into the plugin repository.
 
 For a first-time setup, the end-to-end sequence is:
 
-1. **Install the CLI** — `pnpm add -D artifact-graph@0.9.3` (see Prerequisites above).
+1. **Install the CLI** — `pnpm add -D artifact-graph@0.10.0` (see Prerequisites above).
 2. **Install the plugin** — follow the Codex or Claude Code section above.
 3. **Run bootstrap** — ask the assistant to use the `artifact-chain-bootstrap` skill (see prompt
    below). The skill will:
@@ -1016,7 +1055,7 @@ with append-only behavior; it does not overwrite local rules.
 ### Recovery Steps
 
 ```bash
-# 1. Install dependencies from lockfile (gets artifact-graph@0.9.3)
+# 1. Install dependencies from lockfile (gets artifact-graph@0.10.0)
 pnpm install --frozen-lockfile
 
 # 2. Install plugin per your host (Codex / Claude Code / Kimi Code)
@@ -1083,7 +1122,7 @@ pnpm exec artifact-graph hooks install-git --hook all
 ### Enterprise Mirror
 
 If the corporate environment cannot access the public npm registry or GitHub, mirror both
-`artifact-graph@0.9.3` and the plugin marketplace repository on an internal registry. The mirror
+`artifact-graph@0.10.0` and the plugin marketplace repository on an internal registry. The mirror
 does not change the state ownership model: Git-tracked files remain authoritative, local caches
 remain derived.
 

package/README.md

@@ -2,7 +2,8 @@
 
 [中文](README.zh-CN.md)
 
-Codex, Claude Code, and Kimi Code assistant plugin for projects that use `artifact-graph`.
+Codex, Claude Code, and Kimi Code assistant plugin for projects that use `artifact-graph`; Qoder
+uses the same shared skills as a skill-compatible host.
 
 Artifact Chain Assistant packages reusable skills, host-specific adapter manifests, and install
 guidance for artifact-chain projects. It helps agents discover the right artifact context, bootstrap
@@ -142,6 +143,10 @@ override, compact query, fallback behavior, and `PLUGIN_ROOT` discovery, see
 - **Kimi Code** exposes `.kimi-plugin/plugin.json`, `skills/**`, and managed scripts
   (`doctor.mjs`, `check-workflow-profile.mjs`, `run-artifact-workflow.mjs`, `batch-split.mjs`, `batch-merge.mjs`). It does not
   expose plugin commands, hooks, or settings.
+- **Qoder** is a skill-compatible host: it installs from the same `artifact-skill-set`
+  marketplace and discovers the shared `skills/**`. It does not expose slash command wrappers or
+  the Stop-hook guardrail, and diagnostics still use the plugin root `scripts/doctor.mjs` (there
+  is no Qoder adapter doctor).
 - Git hook templates and installers are host-independent. Git hooks and CI are the hard gates;
   host-specific skills and hooks only provide assistant guidance.
 
@@ -149,13 +154,13 @@ override, compact query, fallback behavior, and `PLUGIN_ROOT` discovery, see
 
 | Plugin | Runtime | Install |
 | --- | --- | --- |
-| `artifact-chain-assistant` 0.9.3 | `artifact-graph` 0.9.3 | `pnpm add -D artifact-graph@0.9.3` |
+| `artifact-chain-assistant` 0.10.0 | `artifact-graph` 0.10.0 | `pnpm add -D artifact-graph@0.10.0` |
 
 ## Install
 
 ```bash
 # Runtime (required)
-npm install --save-dev artifact-graph@0.9.3
+npm install --save-dev artifact-graph@0.10.0
 ```
 
 ```bash
@@ -177,7 +182,7 @@ codex plugin add artifact-chain-assistant@artifact-skill-set
 
 > **Marketplace note**: `ifoohoo/artifact-skill-set` is an external independent marketplace. The
 > plugin payload is still published from `ifoohoo/artifact-chain-assistant`. The marketplace entry
-> must publish and enable `artifact-chain-assistant` 0.9.3 before the install commands above will
+> must publish and enable `artifact-chain-assistant` 0.10.0 before the install commands above will
 > succeed.
 
 ```text
@@ -188,12 +193,25 @@ codex plugin add artifact-chain-assistant@artifact-skill-set
 After installing or upgrading in Kimi Code, run `/reload` (or start a new session) so the plugin
 skills are picked up. Kimi Code has no non-interactive install CLI.
 
+```bash
+# Qoder plugin (skill-compatible host; illustrative commands —
+# confirm flags with `qodercli plugin ... --help` at execution time)
+qodercli plugin marketplace add ifoohoo/artifact-skill-set --scope user
+qodercli plugin install artifact-chain-assistant@artifact-skill-set --scope user --json
+qodercli plugin list --json
+```
+
+Qoder currently commits to skill installation and discovery only; Claude Code slash commands and
+the Stop hook are not provided. Use `qodercli plugin list --json` to check the installed version,
+`enabled`, `installPath`, and `skills`. Diagnostics still use the plugin root
+`scripts/doctor.mjs`; there is no Qoder adapter doctor.
+
 For the full installation guide, quick start, Agent prompts, and clone onboarding, see
 [INSTALL.md](INSTALL.md).
 
 ## Quick Start
 
-1. Install plugin 0.9.3 (above) and runtime: `pnpm add -D artifact-graph@0.9.3`.
+1. Install plugin 0.10.0 (above) and runtime: `pnpm add -D artifact-graph@0.10.0`.
 2. Run `artifact-graph doctor --root . --format json` to verify the runtime.
 3. For first-time setup, use the bootstrap skill.
 4. For daily work, use the maintainer skill.

package/README.zh-CN.md

@@ -2,7 +2,8 @@
 
 [English](README.md)
 
-Artifact Chain Assistant 是面向 `artifact-graph` 项目的 Codex / Claude Code / Kimi Code 助手插件。
+Artifact Chain Assistant 是面向 `artifact-graph` 项目的 Codex / Claude Code / Kimi Code 助手插件；
+Qoder 以技能兼容宿主身份复用同一套共享技能。
 
 它打包了可复用的 skill、按宿主划分的 adapter manifest 和安装指引，帮助 agent 找到正确的
 制品上下文、初始化项目本地配置，并维护追溯版本锁（traceability version lock）。
@@ -190,6 +191,9 @@ catalog 还包含 `artifact.generate`，用于从模板和 profile 配置生成
 - **Kimi Code** 暴露 `.kimi-plugin/plugin.json`、`skills/**` 和受管脚本（`doctor.mjs`、
   `check-workflow-profile.mjs`、`run-artifact-workflow.mjs`、`batch-split.mjs`、`batch-merge.mjs`），不暴露插件命令、hook 和
   settings。
+- **Qoder** 是技能兼容宿主：从同一个 `artifact-skill-set` 市场安装并发现共享
+  `skills/**`，不暴露 slash command 包装器和 Stop hook 防护；诊断仍使用插件根
+  `scripts/doctor.mjs`（不存在 Qoder adapter doctor）。
 - Git hook 模板和安装器与宿主无关。真正的硬门禁是 Git hook 和 CI；各宿主的 skill 和
   hook 只为 assistant 提供指引。
 
@@ -197,13 +201,13 @@ catalog 还包含 `artifact.generate`，用于从模板和 profile 配置生成
 
 | 插件 | 运行时 | 安装 |
 | --- | --- | --- |
-| `artifact-chain-assistant` 0.9.3 | `artifact-graph` 0.9.3 | `pnpm add -D artifact-graph@0.9.3` |
+| `artifact-chain-assistant` 0.10.0 | `artifact-graph` 0.10.0 | `pnpm add -D artifact-graph@0.10.0` |
 
 ## 安装
 
 ```bash
 # 运行时（必需）
-npm install --save-dev artifact-graph@0.9.3
+npm install --save-dev artifact-graph@0.10.0
 ```
 
 ```bash
@@ -225,7 +229,7 @@ codex plugin add artifact-chain-assistant@artifact-skill-set
 
 > **市场说明**：`ifoohoo/artifact-skill-set` 是外部独立市场，插件载荷仍由
 > `ifoohoo/artifact-chain-assistant` 发布。市场条目必须先发布并启用
-> `artifact-chain-assistant` 0.9.3，上述安装命令才能生效。
+> `artifact-chain-assistant` 0.10.0，上述安装命令才能生效。
 
 ```text
 # Kimi Code 插件（交互式，user 作用域）
@@ -235,12 +239,24 @@ codex plugin add artifact-chain-assistant@artifact-skill-set
 在 Kimi Code 中安装或升级后，运行 `/reload`（或新开会话）让插件技能生效。Kimi Code
 没有非交互式安装 CLI。
 
+```bash
+# Qoder 插件（技能兼容宿主；示意命令——
+# 具体命令以执行时 qodercli plugin ... --help 为准）
+qodercli plugin marketplace add ifoohoo/artifact-skill-set --scope user
+qodercli plugin install artifact-chain-assistant@artifact-skill-set --scope user --json
+qodercli plugin list --json
+```
+
+Qoder 当前承诺的边界是技能安装与发现；不提供 Claude Code 的 slash commands 和 Stop hook。
+使用 `qodercli plugin list --json` 检查安装版本、`enabled`、`installPath` 和 `skills`。
+诊断仍使用插件根 `scripts/doctor.mjs`，不存在 Qoder adapter doctor。
+
 完整的安装指南、快速开始、Agent 提示词和团队成员 clone 接入，请参阅
 [INSTALL.md](INSTALL.md)。
 
 ## 快速开始
 
-1. 安装插件 0.9.3（见上文）和运行时：`pnpm add -D artifact-graph@0.9.3`。
+1. 安装插件 0.10.0（见上文）和运行时：`pnpm add -D artifact-graph@0.10.0`。
 2. 运行 `artifact-graph doctor --root . --format json` 验证运行时。
 3. 首次搭建，进入 bootstrap 技能。
 4. 日常工作，进入 maintainer 技能。

package/adapters/claude/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "artifact-chain-assistant",
-  "version": "0.9.3",
+  "version": "0.10.0",
   "description": "Artifact-chain intake, review/repair/batch/audit workflows, diagnostics, hooks, and version-lock maintenance helpers.",
   "author": {
     "name": "广州市风荷科技有限公司"

package/adapters/claude/INSTALL.md

@@ -5,18 +5,20 @@
 
 This guide separates two responsibilities:
 
-1. Install the assistant plugin into Codex and/or Claude Code.
+1. Install the assistant plugin into Codex, Claude Code, Kimi Code, or Qoder.
 2. Prepare each target project so the plugin has a project-local artifact chain to manage.
 
 Codex exposes `.codex-plugin/plugin.json` and `skills/**` only. Claude Code also exposes slash
-command wrappers and a Stop-hook guardrail. Neither host surface replaces Git hooks or CI: those
+command wrappers and a Stop-hook guardrail. Qoder currently runs in skill-compatible mode: it
+installs and discovers the shared skills but does not receive slash command wrappers or the
+Stop-hook guardrail (see [Qoder](#qoder)). Neither host surface replaces Git hooks or CI: those
 remain the hard gates for a target project's artifacts, graph config, version lock, and project
 instructions.
 
 ## Prerequisites
 
 - Node.js `>=22.0.0`.
-- `artifact-graph` 0.9.3 installed in the target project.
+- `artifact-graph` 0.10.0 installed in the target project.
 - **GitHub SSH key** — Claude Code clones `source: github` entries over SSH by default. If you
   have not configured a GitHub SSH key, set `CLAUDE_CODE_PLUGIN_PREFER_HTTPS=1` in your shell
   profile, or add the marketplace with an explicit `https://` URL. Codex users can check
@@ -28,24 +30,24 @@ instructions.
 
 | Plugin | Verified Runtime | Install |
 | --- | --- | --- |
-| `artifact-chain-assistant` 0.9.3 | `artifact-graph` 0.9.3 | `pnpm add -D artifact-graph@0.9.3` |
+| `artifact-chain-assistant` 0.10.0 | `artifact-graph` 0.10.0 | `pnpm add -D artifact-graph@0.10.0` |
 
 ### Install The Runtime
 
 The default installation path uses the npm registry with a precise version:
 
 ```bash
-pnpm add -D artifact-graph@0.9.3
+pnpm add -D artifact-graph@0.10.0
 ```
 
 If the npm registry is unavailable, use the explicit GitHub fallback pinned to the verified tag:
 
 ```bash
-pnpm add -D github:ifoohoo/artifact-graph#artifact-graph-v0.9.3
+pnpm add -D github:ifoohoo/artifact-graph#artifact-graph-v0.10.0
 ```
 
 > **Never** install with an unlocked range (`artifact-graph`, `artifact-graph@latest`,
-> `artifact-graph@^0.9.3`) or an unpinned GitHub URL (`github:ifoohoo/artifact-graph`).
+> `artifact-graph@^0.10.0`) or an unpinned GitHub URL (`github:ifoohoo/artifact-graph`).
 > Unlocked installs produce non-reproducible dependency trees and break version-lock audit.
 
 With pnpm 10+, projects that install `artifact-graph` must allow the native `better-sqlite3`
@@ -72,7 +74,7 @@ allowBuilds:
 
 The plugin's `doctor` command validates the installed runtime version before running any
 diagnostic. If it detects a version mismatch or missing CLI, it reports the exact remediation
-command (`pnpm add -D artifact-graph@0.9.3`) and exits non-zero.
+command (`pnpm add -D artifact-graph@0.10.0`) and exits non-zero.
 
 ### CLI Resolution Order
 
@@ -147,7 +149,7 @@ wrappers, and Stop-hook guardrail. These assistant controls do not replace Git h
 
 > **Marketplace note**: `ifoohoo/artifact-skill-set` is an external independent marketplace. The
 > plugin payload is still published from `ifoohoo/artifact-chain-assistant`. The marketplace entry
-> must publish and enable `artifact-chain-assistant` 0.9.3 before the install commands above will
+> must publish and enable `artifact-chain-assistant` 0.10.0 before the install commands above will
 > succeed.
 
 ### Kimi Code
@@ -174,19 +176,56 @@ skills, and managed scripts (`doctor.mjs`, `check-workflow-profile.mjs`, `run-ar
 non-interactive install CLI, so automated install verification is limited to layout checks;
 use `artifact-chain-maintainer` to guide version-lock CLI operations.
 
+### Qoder
+
+Qoder is currently supported as a **skill-compatible host**, not as a fourth adapter. It reuses the
+existing `artifact-skill-set` marketplace: Qoder recognizes the root
+`.claude-plugin/marketplace.json` and installs the shared plugin root (`skills/**`), so no
+Qoder-specific manifest or duplicated runtime assets are required.
+
+Register the marketplace and install the plugin (illustrative commands):
+
+```bash
+qodercli plugin marketplace add ifoohoo/artifact-skill-set --scope user
+qodercli plugin install artifact-chain-assistant@artifact-skill-set --scope user --json
+qodercli plugin list --json
+```
+
+> The exact flags may change between Qoder CLI releases. Treat the commands above as
+> illustrations and confirm against `qodercli plugin ... --help` at execution time.
+
+Current support boundary:
+
+- **Committed**: plugin installation and shared skill discovery. Qoder installs
+  `artifact-chain-assistant` from the marketplace and discovers the shared `skills/` entries.
+- **Not committed**: Claude Code slash command wrappers and the Stop-hook guardrail are not
+  provided for Qoder. `commands` and `hooks` being empty in `plugin list --json` is expected,
+  not a defect.
+
+Verify an installation with `qodercli plugin list --json`: confirm the installed version, that the
+plugin is enabled, that `installPath` points at the expected location, and that the `skills` list
+matches the shared skill set. Diagnostics still use the plugin root `scripts/doctor.mjs` — resolve
+the installed root from the `installPath` reported by `plugin list --json`, then run
+`node "$PLUGIN_ROOT/scripts/doctor.mjs" --root . --format json`. There is no Qoder-specific
+adapter doctor.
+
 ## Post-Installation Discovery
 
 After installing the plugin, use these entry points to understand available capabilities:
 
-1. **`help`** — Run this skill to see the standard Family API catalog and bundled legacy methods.
-   It shows what families and services the plugin provides, without claiming any are installed, enabled, or verified
-   for your project. Installation of the plugin does NOT mean families are bound or providers are active.
+1. **`help`** — Run this skill when you ask "what can this plugin do" or "how does the artifact
+   chain work". It shows the standard Family API catalog and bundled legacy methods — the plugin's
+   capabilities and what the artifact chain is for — without claiming any are installed, enabled, or
+   verified for your project. Installation of the plugin does NOT mean families are bound or providers
+   are active. If the Registry is missing, it still runs and honestly lists which standard services
+   are not yet executable.
 
-2. **`setup`** — Run this skill for read-only environment diagnostics: plugin closure integrity, Node/CLI
+2. **`setup`** — Run this skill when you ask "is my environment ready". It performs read-only
+   environment diagnostics: plugin closure integrity, Node/CLI
    availability, doctor output, project config, version lock, and registry availability. It outputs a structured status
    report with PASS/WARN/FAIL for each check plus precise next steps, and writes nothing without explicit authorization.
 
-3. **`quickstart`** — Run this skill when unsure which skill to use. It routes your intent to the correct skill:
+3. **`quickstart`** — Run this skill when getting started or unsure which skill to use. It routes your intent to the correct skill via a deterministic routing table covering common Chinese/English requests:
    capability questions go to `help`, environment checks to `setup`, initialization to `setup` then bootstrap,
    project triage to `where-am-i`, maintenance to `maintainer`, and explicit artifact tasks to the matching family/service.
 
@@ -221,7 +260,7 @@ The plugin should not move these files into the plugin repository.
 
 For a first-time setup, the end-to-end sequence is:
 
-1. **Install the CLI** — `pnpm add -D artifact-graph@0.9.3` (see Prerequisites above).
+1. **Install the CLI** — `pnpm add -D artifact-graph@0.10.0` (see Prerequisites above).
 2. **Install the plugin** — follow the Codex or Claude Code section above.
 3. **Run bootstrap** — ask the assistant to use the `artifact-chain-bootstrap` skill (see prompt
    below). The skill will:
@@ -1019,7 +1058,7 @@ with append-only behavior; it does not overwrite local rules.
 ### Recovery Steps
 
 ```bash
-# 1. Install dependencies from lockfile (gets artifact-graph@0.9.3)
+# 1. Install dependencies from lockfile (gets artifact-graph@0.10.0)
 pnpm install --frozen-lockfile
 
 # 2. Install plugin per your host (Codex / Claude Code / Kimi Code)
@@ -1086,7 +1125,7 @@ pnpm exec artifact-graph hooks install-git --hook all
 ### Enterprise Mirror
 
 If the corporate environment cannot access the public npm registry or GitHub, mirror both
-`artifact-graph@0.9.3` and the plugin marketplace repository on an internal registry. The mirror
+`artifact-graph@0.10.0` and the plugin marketplace repository on an internal registry. The mirror
 does not change the state ownership model: Git-tracked files remain authoritative, local caches
 remain derived.
 

package/adapters/claude/agent-methods/catalog.yaml

@@ -1,7 +1,7 @@
 schemaVersion: 1
 catalog:
   id: artifact-chain-assistant
-  version: "0.9.3"
+  version: "0.10.0"
 entries:
   - ref: artifact.prd-feature.default
     provider:
@@ -247,7 +247,7 @@ entries:
       plugin: artifact-chain-assistant
       skill: help
     kind: operation
-    summary: "展示标准 Family API、bundled legacy 方法和安装后采用步骤"
+    summary: "能力说明入口：回答\"能做什么\"、\"制品链怎么用\"，展示标准 Family API、bundled legacy 方法和采用步骤；Registry 缺失时诚实降级"
     match:
       domains: [artifact]
       artifactTypes: [design-spec, link, e2e, domain, contract, blueprint, verification, prd-feature, scenario-script]
@@ -265,7 +265,7 @@ entries:
       plugin: artifact-chain-assistant
       skill: setup
     kind: operation
-    summary: "只读环境检查：插件闭包、CLI、config、版本锁、registry 可用性"
+    summary: "环境诊断入口：回答\"环境准备好了吗\"，只读检查插件闭包、CLI、config、版本锁、registry 可用性，输出 PASS/WARN/FAIL"
     match:
       domains: [artifact]
       artifactTypes: [design-spec, link, e2e, domain, contract, blueprint, verification, prd-feature, scenario-script]
@@ -283,7 +283,7 @@ entries:
       plugin: artifact-chain-assistant
       skill: quickstart
     kind: operation
-    summary: "按意图路由到正确的技能"
+    summary: "上手路径入口：不知道用哪个技能时，按确定性路由表把自然语言需求路由到 help/setup/where-am-i 等正确入口"
     match:
       domains: [artifact]
       artifactTypes: [design-spec, link, e2e, domain, contract, blueprint, verification, prd-feature, scenario-script]

package/adapters/claude/compatibility.json

@@ -1,9 +1,9 @@
 {
   "schemaVersion": "1.0",
-  "pluginVersion": "0.9.3",
+  "pluginVersion": "0.10.0",
   "artifactGraph": {
-    "verifiedVersion": "0.9.3",
-    "installSpec": "artifact-graph@0.9.3",
-    "githubFallbackSpec": "github:ifoohoo/artifact-graph#artifact-graph-v0.9.3"
+    "verifiedVersion": "0.10.0",
+    "installSpec": "artifact-graph@0.10.0",
+    "githubFallbackSpec": "github:ifoohoo/artifact-graph#artifact-graph-v0.10.0"
   }
 }

package/adapters/claude/family-apis/catalog.json

@@ -2,7 +2,7 @@
   "schemaVersion": 1,
   "catalog": {
     "id": "artifact-chain-assistant",
-    "version": "0.9.3"
+    "version": "0.10.0"
   },
   "families": [
     {