artifact-chain-assistant 0.8.0 → 0.8.2

package/.claude-plugin/plugin.json

@@ -1,11 +1,26 @@
 {
   "name": "artifact-chain-assistant",
-  "displayName": "Artifact Chain Assistant",
-  "version": "0.8.0",
+  "version": "0.8.2",
   "description": "Artifact-chain intake, review/repair/batch/audit workflows, diagnostics, hooks, and version-lock maintenance helpers.",
   "author": {
     "name": "Artifact Graph Maintainers"
   },
   "license": "Apache-2.0",
-  "keywords": ["artifact-graph", "traceability", "codex", "claude-code"]
+  "keywords": ["artifact-graph", "traceability", "codex", "claude-code"],
+  "skills": "./skills/",
+  "interface": {
+    "displayName": "Artifact Chain Assistant",
+    "shortDescription": "Artifact-chain context, review workflows, and version-lock maintenance.",
+    "longDescription": "Reusable skills for artifact-graph projects, including intake routing, generic artifact review/repair/batch/audit workflows, diagnostics, and version-lock refresh guidance.",
+    "developerName": "Artifact Graph Maintainers",
+    "category": "Productivity",
+    "capabilities": ["Write"],
+    "defaultPrompt": [
+      "Check where this artifact-chain task should start.",
+      "Review a design-spec artifact for traceability and completeness.",
+      "Run a batch review on multiple artifacts.",
+      "Refresh version locks for my staged changes.",
+      "Run artifact-chain doctor for this project."
+    ]
+  }
 }

package/.codex-plugin/plugin.json

@@ -1,27 +1,18 @@
 {
   "name": "artifact-chain-assistant",
-  "version": "0.8.0",
+  "displayName": "Artifact Chain Assistant",
+  "version": "0.8.2",
   "description": "Artifact-chain intake, review/repair/batch/audit workflows, diagnostics, and version-lock maintenance helpers.",
   "author": {
     "name": "Artifact Graph Maintainers"
   },
   "license": "Apache-2.0",
   "keywords": ["artifact-graph", "traceability", "codex", "claude-code"],
-  "skills": "./skills/",
+  "skills": "./adapters/codex/skills/",
   "hooks": {},
   "interface": {
     "displayName": "Artifact Chain Assistant",
     "shortDescription": "Artifact-chain context, review workflows, and version-lock maintenance.",
-    "longDescription": "Reusable skills for artifact-graph projects, including intake routing, generic artifact review/repair/batch/audit workflows, diagnostics, and version-lock refresh guidance.",
-    "developerName": "Artifact Graph Maintainers",
-    "category": "Productivity",
-    "capabilities": ["Write"],
-    "defaultPrompt": [
-      "Check where this artifact-chain task should start.",
-      "Review a design-spec artifact for traceability and completeness.",
-      "Run a batch review on multiple artifacts.",
-      "Refresh version locks for my staged changes.",
-      "Run artifact-chain doctor for this project."
-    ]
+    "category": "Productivity"
   }
 }

package/AGENT-METHOD-REGISTRY.md

@@ -0,0 +1,238 @@
+# Agent Method Registry
+
+[中文](AGENT-METHOD-REGISTRY.zh-CN.md)
+
+The plugin bundles a deterministic agent-method-registry integration covering catalog resolution,
+provider verification, and CLI diagnostics.
+
+## Default Catalog
+
+The default catalog is at `<plugin-root>/agent-methods/catalog.yaml` and registers **13 workflow
+entries**: 8 specialized entries across the `prd-feature` and `scenario-script` families plus 5
+generic review, repair, batch, audit, and generate entries. Generic entries exclude PRD/scenario
+types, so every supported type+intent query remains unique.
+
+The catalog also includes 3 `kind: operation` entries (`artifact.help`, `artifact.setup`,
+`artifact.quickstart`) for read-only discovery and diagnostics; they are not workflow entries
+and are omitted from the table below.
+
+| Ref | Family | Entry |
+|-----|--------|-------|
+| `artifact.prd-feature.default` | prd-feature | Default routing entry |
+| `artifact.prd-feature.author` | prd-feature | Author |
+| `artifact.prd-feature.review` | prd-feature | Review |
+| `artifact.prd-feature.repair` | prd-feature | Repair |
+| `artifact.scenario-script.default` | scenario-script | Default routing entry |
+| `artifact.scenario-script.author` | scenario-script | Author |
+| `artifact.scenario-script.review` | scenario-script | Review |
+| `artifact.scenario-script.repair` | scenario-script | Repair |
+| `artifact.review` | artifact-review | Review |
+| `artifact.repair` | artifact-repair | Repair |
+| `artifact.batch` | artifact-batch | Batch |
+| `artifact.audit` | artifact-audit | Audit / health |
+| `artifact.generate` | artifact-generate | Generate |
+
+## Standalone Install
+
+Install `agent-method-registry@0.2.0` as a separate dependency if you only need the registry
+capabilities:
+
+```bash
+npm install agent-method-registry@0.2.0
+```
+
+The CLI is available as `agent-method-registry` after installation.
+
+## Building the Effective Index
+
+The effective index is built from the catalog plus an optional project overlay. First, locate
+the installed plugin root from the host CLI. Do **not** use `require.resolve` — marketplace
+installations do not place the plugin into the target project's `node_modules`.
+
+**Codex** — use `codex plugin list --json` and the `CODEX_HOME` cache layout:
+
+```bash
+export CODEX_HOME="${CODEX_HOME:-$HOME/.codex}"
+PLUGIN_ROOT=$(codex plugin list --json 2>/dev/null \
+  | node -e "
+    let d='';process.stdin.on('data',c=>d+=c);process.stdin.on('end',()=>{
+      const data=JSON.parse(d);
+      const p=data.installed.find(x=>x.pluginId==='artifact-chain-assistant@artifact-skill-set');
+      if(!p||!p.installed||!p.enabled||!p.marketplaceName||!p.name||!p.version){process.stderr.write('artifact-chain-assistant record incomplete\n');process.exit(1);}
+      console.log(require('path').join(process.env.CODEX_HOME,'plugins','cache',p.marketplaceName,p.name,p.version));
+    });
+  ")
+[ -f "$PLUGIN_ROOT/agent-methods/catalog.yaml" ] || { echo "catalog not found at $PLUGIN_ROOT"; exit 1; }
+```
+
+**Claude Code** — use `claude plugin list --json` and `installPath` directly:
+
+```bash
+PLUGIN_ROOT=$(claude plugin list --json 2>/dev/null \
+  | node -e "
+    let d='';process.stdin.on('data',c=>d+=c);process.stdin.on('end',()=>{
+      const p=JSON.parse(d).find(x=>x.id==='artifact-chain-assistant@artifact-skill-set');
+      if(!p||!p.enabled||!p.installPath){process.stderr.write('artifact-chain-assistant not found, not enabled, or installPath missing\n');process.exit(1);}
+      console.log(p.installPath);
+    });
+  ")
+[ -f "$PLUGIN_ROOT/agent-methods/catalog.yaml" ] || { echo "catalog not found at $PLUGIN_ROOT"; exit 1; }
+```
+
+> For monorepo development only, the source checkout plugin root is `plugins/artifact-chain-assistant`.
+> Marketplace users must use the host CLI discovery above.
+
+After resolving `PLUGIN_ROOT`, verify the target project before running a generic workflow. This
+check is read-only:
+
+```bash
+node "$PLUGIN_ROOT/scripts/check-workflow-profile.mjs" \
+  --root . --action review --domain design-spec --format json
+```
+
+Exit code 0 means the required project marker and worker mapping exist. Exit code 2 returns
+`NEEDS_INPUT`; add the missing project profile or worker instead of claiming workflow success.
+
+For batch operations, use the split and merge scripts from the same resolved plugin root:
+
+```bash
+# Split artifacts into batches (JSON array to stdout)
+node "$PLUGIN_ROOT/scripts/batch-split.mjs" ./artifacts/design --batch-size 40000
+
+# Merge batch results from a results directory (merged JSON to stdout)
+node "$PLUGIN_ROOT/scripts/batch-merge.mjs" ./batch-results --run-id my-run
+```
+
+Then build the index:
+
+```bash
+# Catalog only (no project provider)
+agent-method-registry index \
+  --catalog "$PLUGIN_ROOT/agent-methods/catalog.yaml" \
+  --out .agent-method-registry/effective-index.json
+```
+
+When no project provider file exists, the registry does **not** create an empty overlay file.
+It builds the effective index from the catalog alone. The `--project` flag is only needed when
+the project defines overrides or disables:
+
+```bash
+# Catalog + project overlay
+agent-method-registry index \
+  --catalog "$PLUGIN_ROOT/agent-methods/catalog.yaml" \
+  --project agent-methods/project.yaml \
+  --out .agent-method-registry/effective-index.json
+```
+
+## Project-Level Override
+
+When the target project defines its own complete entries, put an
+`agent-methods/project.yaml` file in the project root. For example, to override the default
+`prd-feature` routing entry with a project-local skill:
+
+```yaml
+schemaVersion: 1
+overrides:
+  artifact.prd-feature.default:
+    provider:
+      scope: project
+      skill: prd-feature
+```
+
+The project overlay can also add new entries (via `entries`) and disable plugin entries
+(via `disabled`).
+
+## Effective Index Is a Generated Cache
+
+`.agent-method-registry/effective-index.json` is a **generated build artifact**, not a source
+of truth. It is derived from `catalog.yaml` plus the optional `project.yaml` overlay.
+
+- Do not edit it manually.
+- Rebuild it when the catalog or project overlay changes.
+- Do not commit it to version control unless the project explicitly opts in.
+
+## Compact Query for Planners
+
+Use `--format compact` to get a minimal view for planning. Compact queries return only
+`ref`, `kind`, and `summary` -- enough for the planner to select an entry without loading
+full metadata. After selection, use `resolve` to get the provider path:
+
+```bash
+# Compact query: planner sees ref/kind/summary only
+agent-method-registry query \
+  --index .agent-method-registry/effective-index.json \
+  --domain artifact --artifact-type prd-feature \
+  --kind workflow --format compact
+
+# Resolve after selection: get full provider path
+agent-method-registry resolve \
+  --index .agent-method-registry/effective-index.json \
+  --ref artifact.prd-feature.author \
+  --host claude-code \
+  --plugin-root "$PLUGIN_ROOT/skills"
+```
+
+## Closed-Loop Workflow Entries
+
+All 8 specialized entries have `kind: workflow`. A `workflow` entry is a **closed-loop leaf** -- it
+self-completes its own inspect, compose, review, validate, and repair cycle. The outer
+planner should not schedule separate review or repair steps for a workflow entry.
+
+## Registry Unavailable: Fallback Behavior
+
+When `agent-method-registry` is not installed or the effective index does not exist,
+`where-am-i` follows this behavior:
+
+1. Outputs a `"registry unavailable"` diagnostic.
+2. For contract-backed services, returns `NEEDS_INPUT` with registry unavailable message — **no fallback to builtin or config routing**.
+3. For generic non-contract-backed entries, may fall back to existing project configuration and plugin routing logic.
+4. Does **not** attempt to merge catalogs manually or create an empty effective index.
+
+## Locating the Plugin Root
+
+To find the installed plugin root, use your host CLI. Do **not** use `require.resolve` —
+marketplace installations do not place the plugin into the target project's `node_modules`.
+
+**Codex**:
+
+```bash
+export CODEX_HOME="${CODEX_HOME:-$HOME/.codex}"
+PLUGIN_ROOT=$(codex plugin list --json 2>/dev/null \
+  | node -e "
+    let d='';process.stdin.on('data',c=>d+=c);process.stdin.on('end',()=>{
+      const data=JSON.parse(d);
+      const p=data.installed.find(x=>x.pluginId==='artifact-chain-assistant@artifact-skill-set');
+      if(!p||!p.installed||!p.enabled||!p.marketplaceName||!p.name||!p.version){process.stderr.write('plugin record incomplete\n');process.exit(1);}
+      console.log(require('path').join(process.env.CODEX_HOME,'plugins','cache',p.marketplaceName,p.name,p.version));
+    });
+  ")
+```
+
+**Claude Code**:
+
+```bash
+PLUGIN_ROOT=$(claude plugin list --json 2>/dev/null \
+  | node -e "
+    let d='';process.stdin.on('data',c=>d+=c);process.stdin.on('end',()=>{
+      const p=JSON.parse(d).find(x=>x.id==='artifact-chain-assistant@artifact-skill-set');
+      if(!p||!p.enabled||!p.installPath){process.stderr.write('plugin not found, not enabled, or installPath missing\n');process.exit(1);}
+      console.log(p.installPath);
+    });
+  ")
+```
+
+Then use it in resolve commands:
+
+```bash
+agent-method-registry resolve \
+  --index .agent-method-registry/effective-index.json \
+  --ref artifact.prd-feature.author \
+  --host codex \
+  --plugin-root "$PLUGIN_ROOT/skills"
+
+agent-method-registry resolve \
+  --index .agent-method-registry/effective-index.json \
+  --ref artifact.prd-feature.author \
+  --host claude-code \
+  --plugin-root "$PLUGIN_ROOT/skills"
+```

package/AGENT-METHOD-REGISTRY.zh-CN.md

@@ -0,0 +1,229 @@
+# Agent Method Registry（代理方法注册表）
+
+[English](AGENT-METHOD-REGISTRY.md)
+
+插件内置了确定性的 agent-method-registry 集成，提供目录解析、provider 验证和 CLI 诊断。
+
+## 默认目录
+
+默认目录位于 `<plugin-root>/agent-methods/catalog.yaml`，注册了 **13 个 workflow 入口**：
+`prd-feature` 和 `scenario-script` 两个技能族的 8 个专业入口，加上 review、repair、
+batch、audit、generate 五个通用入口。通用入口不含 PRD/场景类型，因此每个受支持的
+type+intent 查询都唯一命中。
+
+目录还包含 3 个 `kind: operation` 条目（`artifact.help`、`artifact.setup`、
+`artifact.quickstart`），用于只读发现和诊断；它们不是 workflow 入口，下表省略。
+
+| Ref | 技能族 | 入口 |
+|-----|--------|------|
+| `artifact.prd-feature.default` | prd-feature | 默认路由入口 |
+| `artifact.prd-feature.author` | prd-feature | 编写 |
+| `artifact.prd-feature.review` | prd-feature | 审阅 |
+| `artifact.prd-feature.repair` | prd-feature | 修复 |
+| `artifact.scenario-script.default` | scenario-script | 默认路由入口 |
+| `artifact.scenario-script.author` | scenario-script | 编写 |
+| `artifact.scenario-script.review` | scenario-script | 审阅 |
+| `artifact.scenario-script.repair` | scenario-script | 修复 |
+| `artifact.review` | artifact-review | 审阅 |
+| `artifact.repair` | artifact-repair | 修复 |
+| `artifact.batch` | artifact-batch | 批处理 |
+| `artifact.audit` | artifact-audit | 审计 / health |
+| `artifact.generate` | artifact-generate | 生成 |
+
+## 单独安装
+
+只需要注册表能力时，可以单独安装 `agent-method-registry@0.2.0`：
+
+```bash
+npm install agent-method-registry@0.2.0
+```
+
+安装后即可使用 `agent-method-registry` CLI。
+
+## 构建有效索引
+
+有效索引由目录加上可选的项目覆盖层构建。首先通过宿主 CLI 定位已安装的插件根目录。
+**不要**使用 `require.resolve`——marketplace 安装不会把插件放进目标项目的 `node_modules`。
+
+**Codex**——使用 `codex plugin list --json` 和 `CODEX_HOME` 缓存布局：
+
+```bash
+export CODEX_HOME="${CODEX_HOME:-$HOME/.codex}"
+PLUGIN_ROOT=$(codex plugin list --json 2>/dev/null \
+  | node -e "
+    let d='';process.stdin.on('data',c=>d+=c);process.stdin.on('end',()=>{
+      const data=JSON.parse(d);
+      const p=data.installed.find(x=>x.pluginId==='artifact-chain-assistant@artifact-skill-set');
+      if(!p||!p.installed||!p.enabled||!p.marketplaceName||!p.name||!p.version){process.stderr.write('artifact-chain-assistant record incomplete\n');process.exit(1);}
+      console.log(require('path').join(process.env.CODEX_HOME,'plugins','cache',p.marketplaceName,p.name,p.version));
+    });
+  ")
+[ -f "$PLUGIN_ROOT/agent-methods/catalog.yaml" ] || { echo "catalog not found at $PLUGIN_ROOT"; exit 1; }
+```
+
+**Claude Code**——使用 `claude plugin list --json` 和 `installPath`：
+
+```bash
+PLUGIN_ROOT=$(claude plugin list --json 2>/dev/null \
+  | node -e "
+    let d='';process.stdin.on('data',c=>d+=c);process.stdin.on('end',()=>{
+      const p=JSON.parse(d).find(x=>x.id==='artifact-chain-assistant@artifact-skill-set');
+      if(!p||!p.enabled||!p.installPath){process.stderr.write('artifact-chain-assistant not found, not enabled, or installPath missing\n');process.exit(1);}
+      console.log(p.installPath);
+    });
+  ")
+[ -f "$PLUGIN_ROOT/agent-methods/catalog.yaml" ] || { echo "catalog not found at $PLUGIN_ROOT"; exit 1; }
+```
+
+> 仅限 monorepo 开发时，源码检出的插件根目录为 `plugins/artifact-chain-assistant`。
+> 市场用户必须使用上述宿主 CLI 发现方式。
+
+定位 `PLUGIN_ROOT` 后，运行通用工作流前先验证目标项目（只读）：
+
+```bash
+node "$PLUGIN_ROOT/scripts/check-workflow-profile.mjs" \
+  --root . --action review --domain design-spec --format json
+```
+
+退出码 0 表示所需的项目标记和 worker 映射均存在。退出码 2 返回 `NEEDS_INPUT`；
+请补充缺失的项目 profile 或 worker，而非声称工作流已成功。
+
+批量操作使用同一插件根目录下的切分和合并脚本：
+
+```bash
+# 切分制品为批次（JSON 数组输出到 stdout）
+node "$PLUGIN_ROOT/scripts/batch-split.mjs" ./artifacts/design --batch-size 40000
+
+# 从结果目录合并批次结果（合并后的 JSON 输出到 stdout）
+node "$PLUGIN_ROOT/scripts/batch-merge.mjs" ./batch-results --run-id my-run
+```
+
+然后构建索引：
+
+```bash
+# 仅目录（无项目 provider）
+agent-method-registry index \
+  --catalog "$PLUGIN_ROOT/agent-methods/catalog.yaml" \
+  --out .agent-method-registry/effective-index.json
+```
+
+项目没有 provider 文件时，注册表**不会**创建空的覆盖层文件，只根据目录构建有效索引。
+只有项目定义了覆盖或禁用项时才需要 `--project` 参数：
+
+```bash
+# 目录 + 项目覆盖层
+agent-method-registry index \
+  --catalog "$PLUGIN_ROOT/agent-methods/catalog.yaml" \
+  --project agent-methods/project.yaml \
+  --out .agent-method-registry/effective-index.json
+```
+
+## 项目级覆盖
+
+目标项目有自己的完整入口定义时，在项目根目录放置 `agent-methods/project.yaml`。
+例如把默认的 `prd-feature` 路由入口覆盖为项目本地技能：
+
+```yaml
+schemaVersion: 1
+overrides:
+  artifact.prd-feature.default:
+    provider:
+      scope: project
+      skill: prd-feature
+```
+
+项目覆盖层还可以通过 `entries` 添加新入口、通过 `disabled` 禁用插件入口。
+
+## 有效索引是生成缓存
+
+`.agent-method-registry/effective-index.json` 是**生成的构建产物**，不是事实来源，
+由 `catalog.yaml` 加上可选的 `project.yaml` 覆盖层派生而来。
+
+- 不要手工编辑。
+- 目录或项目覆盖层变更后要重新构建。
+- 除非项目明确选择提交，否则不要纳入版本控制。
+
+## 面向规划器的紧凑查询
+
+用 `--format compact` 获取规划所需的最小视图。紧凑查询只返回 `ref`、`kind` 和
+`summary`，规划器据此选定入口即可，无需加载完整元数据；选定后再用 `resolve` 获取
+provider 路径：
+
+```bash
+# 紧凑查询：规划器只看到 ref/kind/summary
+agent-method-registry query \
+  --index .agent-method-registry/effective-index.json \
+  --domain artifact --artifact-type prd-feature \
+  --kind workflow --format compact
+
+# 选定后解析：获取完整提供者路径
+agent-method-registry resolve \
+  --index .agent-method-registry/effective-index.json \
+  --ref artifact.prd-feature.author \
+  --host claude-code \
+  --plugin-root "$PLUGIN_ROOT/skills"
+```
+
+## 闭环 workflow 入口
+
+8 个专业入口的 `kind` 均为 `workflow`。`workflow` 入口是**闭环叶子**：进入后自行完成
+inspect、compose、review、validate、repair 整个循环，外层规划器不要再为它安排独立的
+review 或 repair 步骤。
+
+## Registry 不可用时的 fallback 行为
+
+`agent-method-registry` 未安装或有效索引不存在时，`where-am-i` 按以下方式回退：
+
+1. 输出 `"registry unavailable"` 诊断信息。
+2. 对于有契约支撑的服务，返回 `NEEDS_INPUT` 并附带 registry 不可用信息——**不会回落到内置或配置路由**。
+3. 对于无契约支撑的通用条目，可回落到现有项目配置和插件路由逻辑。
+4. **不会**尝试手工合并目录，也不会创建空的有效索引。
+
+## 定位插件根目录
+
+用宿主 CLI 查找已安装的插件根目录。**不要**使用 `require.resolve`——marketplace 安装
+不会把插件放进目标项目的 `node_modules`。
+
+**Codex**：
+
+```bash
+export CODEX_HOME="${CODEX_HOME:-$HOME/.codex}"
+PLUGIN_ROOT=$(codex plugin list --json 2>/dev/null \
+  | node -e "
+    let d='';process.stdin.on('data',c=>d+=c);process.stdin.on('end',()=>{
+      const data=JSON.parse(d);
+      const p=data.installed.find(x=>x.pluginId==='artifact-chain-assistant@artifact-skill-set');
+      if(!p||!p.installed||!p.enabled||!p.marketplaceName||!p.name||!p.version){process.stderr.write('plugin record incomplete\n');process.exit(1);}
+      console.log(require('path').join(process.env.CODEX_HOME,'plugins','cache',p.marketplaceName,p.name,p.version));
+    });
+  ")
+```
+
+**Claude Code**：
+
+```bash
+PLUGIN_ROOT=$(claude plugin list --json 2>/dev/null \
+  | node -e "
+    let d='';process.stdin.on('data',c=>d+=c);process.stdin.on('end',()=>{
+      const p=JSON.parse(d).find(x=>x.id==='artifact-chain-assistant@artifact-skill-set');
+      if(!p||!p.enabled||!p.installPath){process.stderr.write('plugin not found, not enabled, or installPath missing\n');process.exit(1);}
+      console.log(p.installPath);
+    });
+  ")
+```
+
+然后在 resolve 命令中使用：
+
+```bash
+agent-method-registry resolve \
+  --index .agent-method-registry/effective-index.json \
+  --ref artifact.prd-feature.author \
+  --host codex \
+  --plugin-root "$PLUGIN_ROOT/skills"
+
+agent-method-registry resolve \
+  --index .agent-method-registry/effective-index.json \
+  --ref artifact.prd-feature.author \
+  --host claude-code \
+  --plugin-root "$PLUGIN_ROOT/skills"
+```

package/CHANGELOG.md

@@ -1,5 +1,34 @@
 # Changelog
 
+## 0.8.2
+
+### Fixed
+
+- **Nested `author/review` skill reference file projection**: `sync-skills.mjs` now correctly
+  projects family-level reference files (`references/{inspect,compose,validate}.md`) into nested
+  `author/review` skill directories for `prd-feature` and `scenario-script` families. Both Codex
+  and Claude Code adapter surfaces, as well as the root `skills/` tree, include the projected
+  reference files. Skills that do not consume reference files no longer receive stale copies.
+
+### Changed
+
+- **Runtime compatibility pinned to `artifact-graph@0.8.2`**: plugin and runtime compatibility,
+  marketplace manifests, and adapter manifests verify `artifact-graph@0.8.2` exactly.
+
+## 0.8.1
+
+### Breaking Changes
+
+- **`artifact-chain-help` renamed to `help`**: the `artifact-chain-help` skill is now `help`. The old name is not preserved as an alias. Update any prompts or scripts that reference `artifact-chain-help`.
+- **New entry skills `setup` and `quickstart`**: `setup` provides read-only environment diagnostics; `quickstart` routes user intent to the correct skill. Both are `kind: operation` in the agent-method catalog.
+- **Self-marketplace removed**: the plugin no longer ships `.agents/plugins/marketplace.json` or `.claude-plugin/marketplace.json`. Installation now uses the external `ifoohoo/artifact-skill-set` marketplace. Root `.claude-plugin/plugin.json` and `.codex-plugin/plugin.json` are retained for external marketplace discovery.
+
+### Changed
+
+- **Deterministic release manifests clarified**: root plugin manifests now describe external marketplace
+  installation flow — the marketplace entry uses these root manifests to discover host-specific adapter
+  skills at `./adapters/claude` and `./adapters/codex`.
+
 ## 0.8.0
 
 ### Changed

package/CONTRIBUTING.md

@@ -2,6 +2,11 @@
 
 Thanks for your interest in contributing.
 
+> **This repository is a release snapshot.** Documentation (README, CHANGELOG, INSTALL,
+> NOTICE) and shared files are rendered from a private workspace. Direct pull requests
+> against these files will be overwritten by the next render — please open an issue
+> instead, and the maintainers will make the change at the source.
+
 ## Development
 
 Use Node.js `>=22.0.0`.
@@ -15,7 +20,7 @@ pnpm test
 ## Pull Requests
 
 - Keep changes focused.
-- Update README, CHANGELOG, and tests when behavior changes.
+- Documentation changes should be proposed as issues (see above); code changes should update tests when behavior changes.
 - Run the package validation commands before opening a pull request.
 - Do not include private parent-repository artifacts or local machine paths.
 

package/EXTENDED-ARTIFACT-CATALOG.md

@@ -1,5 +1,8 @@
 # Extended Artifact Catalog
 
+<!-- generated by scripts/render-public-docs.mjs from docs/public/** — do not edit directly -->
+
+
 This document summarizes the extended artifact type catalog for `artifact-chain-assistant`. It
 covers type classification, recommended paths and ID patterns, template adoption rules, and the
 three-tier authority boundary between `artifact-graph`, the plugin, and target projects.

package/EXTENDED-ARTIFACT-CATALOG.zh-CN.md

@@ -1,5 +1,8 @@
 # 扩展制品目录
 
+<!-- generated by scripts/render-public-docs.mjs from docs/public/** — do not edit directly -->
+
+
 [English](EXTENDED-ARTIFACT-CATALOG.md)
 
 本文档汇总 `artifact-chain-assistant` 的扩展制品类型目录，内容包括类型分类、推荐路径与 ID 模式、