artifact-chain-assistant 0.14.1 → 0.15.0

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "artifact-chain-assistant",
-  "version": "0.14.1",
+  "version": "0.15.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.14.1",
+  "version": "0.15.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.14.1",
+  "version": "0.15.0",
   "description": "Artifact-chain intake, review/repair/batch/audit workflows, diagnostics, and version-lock maintenance helpers.",
   "author": {
     "name": "广州市风荷科技有限公司"

package/CHANGELOG.md

@@ -2,6 +2,23 @@
 
 ## Unreleased
 
+## 0.15.0
+
+### Added
+
+- The assistant reads the Graph package list at `artifact-graph/project-artifact-profiles` through the existing runtime. The readiness report includes `candidate_types` (common minimum, category standard, stage, capability, and project extras), `missing_standard_types` (unadopted common or skill-plugin standard types, kept separate from `gaps`), and `profile_contract` (whether the list loaded with `schema_version` `1.0`). `profile_contract` is read-compatibility status, not template or method readiness. If the list is missing or `schema_version` is not `1.0`, list-dependent recommendations pause and no copied STAGE/SHAPE table is used. Extra types already in project config or method bindings remain.
+
+### Changed
+
+- Plugin and Graph install coordinates are unified at `0.15.0`. Compatibility metadata, README, and INSTALL pin `artifact-graph@0.15.0`.
+
+## 0.14.2
+
+### Fixed
+
+- Resolve `design-spec` profiles as the `design` artifact type. Preserve each action's existing method precedence: use the configured `design` key first, then fall back to its associated `design-spec` profile alias if the key is missing; a missing method still reports `NEEDS_INPUT`.
+- Derive `artifact-chain-assistant` and `artifact-graph` release coordinates from their respective package versions. The assistant-only 0.14.2 update retains the verified Graph 0.14.1 dependency and installation coordinates; version-field and adapter drift continue to fail checks.
+
 ## 0.14.1
 
 ### Changed

package/EXTENDED-ARTIFACT-CATALOG.md

@@ -14,8 +14,8 @@ plugin README and INSTALL.md. This document covers opt-in types beyond the core
 
 | Layer | Scope | Responsibility for Extended Types |
 | --- | --- | --- |
-| **artifact-graph** | Deterministic graph capabilities | Reads type definitions from config; indexes artifacts; provides context/packet/validate. Does **not** ship default paths or ID patterns for extended types. Types without configured paths are not indexed. |
-| **artifact-chain-assistant** | General assistant guidance | Provides starter templates, profile suggestions, and generic review checklists. **Templates are guidance, not authority.** Project-local templates and review skills override plugin suggestions. |
+| **artifact-graph** | Deterministic graph capabilities, plus the published common-minimum and project-type standard lists at `artifact-graph/project-artifact-profiles` | Reads type definitions from config; indexes artifacts; provides context/packet/validate. Ships recommendation lists only; it does **not** auto-enable types or ship default paths or ID patterns for extended types. Types without configured paths are not indexed. |
+| **artifact-chain-assistant** | General assistant guidance | Reads the Graph lists, then provides starter templates, adoption-readiness checks, and generic review checklists. **Templates are guidance, not authority.** The assistant does not keep a second list source of truth. Project-local templates and review skills override plugin suggestions. |
 | **Target project** | Final working method | Decides which extended types to enable; maintains config, local templates, review skills, and ID rules. **Project-local overrides plugin suggestions.** Enables new types progressively as maturity grows. |
 
 ## Extended Artifact Type Catalog
@@ -90,15 +90,19 @@ has corresponding files or processes.
 ## Bootstrap Trimming Strategy
 
 Bootstrap selects a **minimum viable profile** rather than enabling all known types.
+The published lists are `artifact-graph/project-artifact-profiles`. Reading them does not enable types.
 
 Rules:
 
-1. **Core set always enabled**: `feature`, `scenario`, `decision`, `design`, `test`, `e2e_test`.
-2. **Contracts by evidence**: Enable only when the project has corresponding interface files (e.g., OpenAPI spec, CLI entry, IPC channel definition).
-3. **Domain/data by project shape**: Enterprise Java/DDD projects may enable `domain_model`; projects with databases may enable `database_migration`.
-4. **Ops by operational process**: Enable only when the project has deployment configs, security review processes, or operational manuals.
-5. **Agent/hook by local files**: Enable only when the project has `skills/`, `policies/`, or hook config files.
-6. **Progressive expansion**: As project maturity grows, add new types in `artifact-graph.config.yaml`. Existing artifacts and traceability relationships are unaffected.
+1. **Common minimum is visible, not auto-enabled**: `feature`, `scenario`, `design`. Missing items stay visible until the project adopts them.
+2. **Only `skill-plugin` has an approved category standard**: it adds `agent_skill` and `e2e_test` on top of the common minimum. Other shapes use the common minimum plus matching stage and capability candidates.
+3. **Stage items stay candidates**: `requirement`, `spec`, and `decision` appear for matching adoption stages and are enabled only by config, profile, or explicit selection.
+4. **Contracts by evidence**: Enable `cli_contract`, `api_contract`, `ui_contract`, `ipc_contract`, or `data_contract` only when the project has corresponding interface files.
+5. **Domain/data by project shape**: Enterprise Java/DDD projects may enable `domain_model`; projects with databases may enable `database_migration`.
+6. **Ops by operational process**: Enable only when the project has deployment configs, security review processes, or operational manuals.
+7. **Agent/hook by local files**: `hook_policy` and `prompt_packet` remain capability candidates for `skill-plugin`; enable them only when the project has `skills/`, `policies/`, or hook config files.
+8. **Release by duty**: Enable `release_policy` and related types only when the project owns publish and distribution.
+9. **Progressive expansion**: As project maturity grows, add new types in `artifact-graph.config.yaml`. Existing extras and traceability relationships are kept.
 
 After bootstrap, the enabled types, paths, and ID patterns are recorded in
 `artifact-graph.config.yaml`. Deferred types and their evidence conditions are documented in the

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

@@ -15,8 +15,8 @@ INSTALL.md。本文档只介绍核心集合之外的可选类型。
 
 | 层级 | 权威范围 | 对扩展制品的职责 |
 |------|---------|-----------------|
-| **artifact-graph** | 确定性图能力 | 从 config 读取类型定义，索引制品，提供 context/packet/validate。**不内置扩展类型的默认路径或 ID 模式。** 未配置路径的类型不会被索引。 |
-| **artifact-chain-assistant** | 通用助手指导 | 提供扩展制品的入门模板、profile 建议和通用审查清单。**模板是指导，不是权威。** 项目本地模板和审查技能覆盖插件建议。 |
+| **artifact-graph** | 确定性图能力，以及随包发布的共同最小清单与项目类型标准（入口 `artifact-graph/project-artifact-profiles`） | 从 config 读取类型定义，索引制品，提供 context/packet/validate。只发布推荐清单，**不自动启用类型，也不内置扩展类型的默认路径或 ID 模式。** 未配置路径的类型不会被索引。 |
+| **artifact-chain-assistant** | 通用助手指导 | 读取 Graph 清单，再提供入门模板、采用就绪检查和通用审查清单。**模板是指导，不是权威。** 助手不另存一份清单真源。项目本地模板和审查技能覆盖插件建议。 |
 | **目标项目** | 最终工作法 | 决定启用哪些扩展类型，维护 config、本地模板、审查技能和 ID 规则。**项目本地覆盖插件建议。** 随成熟度提升逐步启用新类型。 |
 
 ## 扩展制品类型目录
@@ -82,17 +82,19 @@ Agent 与 Hook 制品覆盖 AI 辅助工作流和 CI/CD 门禁。项目存在对
 
 ## Bootstrap 裁剪策略
 
-bootstrap 的职责是按项目形态选出**最小可用 profile**，而不是启用所有已知类型。
+bootstrap 按项目形态选出最小可用 profile，而不是启用所有已知类型。权威清单位于 `artifact-graph/project-artifact-profiles`。读到清单不等于已经启用类型。
 
 裁剪规则：
 
-1. **基础集合始终启用**：`feature`、`scenario`、`decision`、`design`、`test`、`e2e_test`。
-2. **契约类按证据加入**：项目本地存在对应的接口文件（如 OpenAPI spec、CLI 入口、IPC 通道定义）才启用。
-3. **领域与数据类按项目形态加入**：企业 Java/DDD 项目可启用 `domain_model`；使用数据库的项目可启用 `database_migration`。
-4. **运维类按运维流程加入**：项目有部署配置、安全审查流程或运维手册，才启用对应类型。
-5. **Agent/Hook 类按本地文件加入**：项目存在 `skills/`、`policies/` 或 hook 配置文件才启用。
-6. **发布治理类按治理证据加入**：项目存在发布策略、发布脚本或开源合规流程时，才启用 `release_policy`、`publish_skill`、`oss_compliance`。
-7. **渐进扩展**：项目成熟度提升后，可按需在 `artifact-graph.config.yaml` 中新增类型，已有制品和追溯关系不受影响。
+1. **共同最小清单可见，但不自动启用**：`feature`、`scenario`、`design`。尚未采用的项必须仍能看见。
+2. **只有 `skill-plugin` 有获批的类别标准**：在共同最小之上增加 `agent_skill`、`e2e_test`。其余形态按共同最小集，再加匹配的阶段项和能力项。
+3. **阶段项保持候选**：`requirement`、`spec`、`decision` 只在对应采用阶段出现，且须有配置、profile 或明确选择才会启用。
+4. **契约类按证据加入**：项目本地存在对应的接口文件才启用 `cli_contract`、`api_contract`、`ui_contract`、`ipc_contract` 或 `data_contract`。
+5. **领域与数据类按项目形态加入**：企业 Java/DDD 项目可启用 `domain_model`；使用数据库的项目可启用 `database_migration`。
+6. **运维类按运维流程加入**：项目有部署配置、安全审查流程或运维手册，才启用对应类型。
+7. **Agent/Hook 类按本地文件加入**：`hook_policy`、`prompt_packet` 仍是 `skill-plugin` 的能力候选；项目存在对应文件才启用。
+8. **发布治理类按职责加入**：项目承担发布与分发时，才启用 `release_policy`、`publish_skill`、`oss_compliance`。
+9. **渐进扩展**：可按需在 `artifact-graph.config.yaml` 中新增类型；已有追加项和追溯关系予以保留。
 
 bootstrap 执行后，启用的类型、路径和 ID 模式记录在 `artifact-graph.config.yaml` 中；延后启用的
 类型及其证据条件记录在项目制品目录中，让日后的扩展有据可查。

package/INSTALL.md

@@ -15,7 +15,7 @@ instructions.
 ## Prerequisites
 
 - Node.js `>=22.22.2 <23`.
-- `artifact-graph` 0.14.1 installed in the target project.
+- `artifact-graph` 0.15.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
@@ -27,24 +27,24 @@ instructions.
 
 | Plugin | Verified Runtime | Install |
 | --- | --- | --- |
-| `artifact-chain-assistant` 0.14.1 | `artifact-graph` 0.14.1 | `pnpm add -D artifact-graph@0.14.1` |
+| `artifact-chain-assistant` 0.15.0 | `artifact-graph` 0.15.0 | `pnpm add -D artifact-graph@0.15.0` |
 
 ### Install The Runtime
 
 The default installation path uses the npm registry with a precise version:
 
 ```bash
-pnpm add -D artifact-graph@0.14.1
+pnpm add -D artifact-graph@0.15.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.14.1
+pnpm add -D github:ifoohoo/artifact-graph#artifact-graph-v0.15.0
 ```
 
 > **Never** install with an unlocked range (`artifact-graph`, `artifact-graph@latest`,
-> `artifact-graph@^0.14.1`) or an unpinned GitHub URL (`github:ifoohoo/artifact-graph`).
+> `artifact-graph@^0.15.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`
@@ -71,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.14.1`) and exits non-zero.
+command (`pnpm add -D artifact-graph@0.15.0`) and exits non-zero.
 
 ### CLI Resolution Order
 
@@ -156,7 +156,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.14.1 before the install commands above will
+> must publish and enable `artifact-chain-assistant` 0.15.0 before the install commands above will
 > succeed.
 
 ### Kimi Code
@@ -303,7 +303,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.14.1` (see Prerequisites above). The
+1. **Install the CLI** — `pnpm add -D artifact-graph@0.15.0` (see Prerequisites above). The
    `artifact-chain-setup` skill can run this and the other mechanical install steps for you
    after showing a plan and getting your confirmation.
 2. **Install the plugin** — follow the Codex or Claude Code section above.
@@ -954,13 +954,35 @@ node "$PLUGIN_ROOT/scripts/check-workflow-profile.mjs" \
   --format json
 ```
 
-`candidate_types` contains shape and stage suggestions. `enabled_types` contains only candidates
-backed by the effective `artifact-graph.config.yaml`, an existing workflow profile, or explicit
-`--types` selection. Candidate-only entries are not readiness gaps. For enabled types, the report
-checks registration, starter templates, and generate/review methods separately. Requirement and SPEC
-generation can report `bundled-skill`; its presence never implies that review is ready. A review
-method must be configured in the workflow profile. The checker loads the effective graph config
-through the artifact-graph runtime and does not maintain a second YAML interpretation.
+The assistant reads the list from the resolved Graph package at `artifact-graph/project-artifact-profiles`.
+It does not keep a second copy. Shape and stage suggestions are not proof the project has that
+capability.
+
+`candidate_types` lists common minimum, category standard, stage, capability, and project extras.
+Each item has `applicability` and `enabled`. `enabled` is true only with the effective
+`artifact-graph.config.yaml`, an existing workflow profile, or explicit `--types` selection.
+Stage and capability items are not auto-enabled. The common minimum is `feature`, `scenario`, and
+`design`. Only `skill-plugin` adds `agent_skill` and `e2e_test`. Project configuration owns adoption
+and keeps extra types already present in config or method bindings.
+
+`missing_standard_types` lists unadopted common-minimum or skill-plugin standard types. A successful
+list read is not adoption. This field is separate from `gaps`.
+
+`gaps` lists effective-config failures and missing type declarations, ID patterns, artifact paths or
+directories, starter templates, or executable generate/review methods for enabled types. Candidate-only entries are not readiness gaps. A readable list does not hide missing
+templates or methods.
+
+`profile_contract` reports whether the published list loaded and whether `schema_version` is `1.0`.
+Status `OK` is read-compatibility. It is not `registration.ready`, template readiness, or method
+readiness. If the export is missing (`profiles_export_missing`) or `schema_version` is not `1.0`
+(`profiles_schema_incompatible`), pause only list-dependent recommendations. Do not fall back to a
+copied STAGE/SHAPE table. Extra types already in project config or method bindings remain.
+
+The checker loads the effective graph config through the artifact-graph runtime and does not maintain
+a second YAML interpretation. For enabled types, the report checks registration, starter templates,
+and generate/review methods separately. Requirement and SPEC generation can report `bundled-skill`;
+its presence never implies that review is ready. A review method must be configured in the workflow
+profile.
 
 ### Requirement pool and iteration SPEC
 
@@ -1346,7 +1368,7 @@ with append-only behavior; it does not overwrite local rules.
 ### Recovery Steps
 
 ```bash
-# 1. Install dependencies from lockfile (gets artifact-graph@0.14.1)
+# 1. Install dependencies from lockfile (gets artifact-graph@0.15.0)
 pnpm install --frozen-lockfile
 
 # 2. Install plugin per your host (Codex / Claude Code / Kimi Code)
@@ -1413,7 +1435,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.14.1` and the plugin marketplace repository on an internal registry. The mirror
+`artifact-graph@0.15.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

@@ -112,8 +112,12 @@ Project shape and adoption stage produce `candidate_types`; they do not assert t
 capability exists. `enabled_types` contains only candidates supported by the effective graph config,
 an existing workflow profile, or explicit `--types` selection. Readiness then checks registration,
 templates, and executable methods separately. The bundled requirement/SPEC skill can satisfy
-generation, while review remains a gap until a review method is actually configured. See
-[INSTALL.md](INSTALL.md#project-shape-and-stage-readiness) for the read-only command.
+generation, while review remains a gap until a review method is actually configured. The assistant
+reads the published list from the resolved `artifact-graph` package at
+`artifact-graph/project-artifact-profiles` and does not keep a second copy. Unadopted
+common-minimum or skill-plugin standard types appear in `missing_standard_types`; that field is not
+`gaps`. See [INSTALL.md](INSTALL.md#project-shape-and-stage-readiness) for field meanings and the
+read-only command.
 
 ### Professional Skill Families
 
@@ -204,13 +208,13 @@ override, compact query, fallback behavior, and `PLUGIN_ROOT` discovery, see
 
 | Plugin | Runtime | Install |
 | --- | --- | --- |
-| `artifact-chain-assistant` 0.14.1 | `artifact-graph` 0.14.1 | `pnpm add -D artifact-graph@0.14.1` |
+| `artifact-chain-assistant` 0.15.0 | `artifact-graph` 0.15.0 | `pnpm add -D artifact-graph@0.15.0` |
 
 ## Install
 
 ```bash
 # Runtime (required)
-npm install --save-dev artifact-graph@0.14.1
+npm install --save-dev artifact-graph@0.15.0
 ```
 
 ```bash
@@ -232,7 +236,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.14.1 before the install commands above will
+> must publish and enable `artifact-chain-assistant` 0.15.0 before the install commands above will
 > succeed.
 
 ```text
@@ -261,7 +265,7 @@ For the full installation guide, quick start, Agent prompts, and clone onboardin
 
 ## Quick Start
 
-1. Install plugin 0.14.1 (above) and runtime: `pnpm add -D artifact-graph@0.14.1`.
+1. Install plugin 0.15.0 (above) and runtime: `pnpm add -D artifact-graph@0.15.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

@@ -91,7 +91,9 @@ Audit 定义技能族制品规范，助手帮助项目采用适用的类型、
 项目形态与采用阶段只生成 `candidate_types`，不证明每项候选能力都已存在。`enabled_types`
 只包含有效图配置、已有 workflow profile 或 `--types` 显式选择支持的候选。随后分别检查
 类型登记、模板与可执行方法。插件自带的需求/SPEC 技能可以满足制作入口；没有实际配置审阅方法时，
-review 仍报告缺口。只读命令见[安装说明](INSTALL.md#project-shape-and-stage-readiness)。
+review 仍报告缺口。助手从已解析的 `artifact-graph` 包读取公开清单，入口是
+`artifact-graph/project-artifact-profiles`，不另存一份真源。尚未采用的共同最小或技能族标准项
+记在 `missing_standard_types`，该字段不是 `gaps`。完整解释见[安装说明](INSTALL.md#project-shape-and-stage-readiness)。
 
 ### 项目形态分类
 
@@ -236,13 +238,13 @@ catalog 还包含 `artifact.generate`，用于从模板和 profile 配置生成
 
 | 插件 | 运行时 | 安装 |
 | --- | --- | --- |
-| `artifact-chain-assistant` 0.14.1 | `artifact-graph` 0.14.1 | `pnpm add -D artifact-graph@0.14.1` |
+| `artifact-chain-assistant` 0.15.0 | `artifact-graph` 0.15.0 | `pnpm add -D artifact-graph@0.15.0` |
 
 ## 安装
 
 ```bash
 # 运行时（必需）
-npm install --save-dev artifact-graph@0.14.1
+npm install --save-dev artifact-graph@0.15.0
 ```
 
 ```bash
@@ -264,7 +266,7 @@ codex plugin add artifact-chain-assistant@artifact-skill-set
 
 > **市场说明**：`ifoohoo/artifact-skill-set` 是外部独立市场，插件载荷仍由
 > `ifoohoo/artifact-chain-assistant` 发布。市场条目必须先发布并启用
-> `artifact-chain-assistant` 0.14.1，上述安装命令才能生效。
+> `artifact-chain-assistant` 0.15.0，上述安装命令才能生效。
 
 ```text
 # Kimi Code 插件（交互式，user 作用域）
@@ -291,7 +293,7 @@ Qoder 当前承诺的边界是技能安装与发现；不提供 Claude Code 的
 
 ## 快速开始
 
-1. 安装插件 0.14.1（见上文）和运行时：`pnpm add -D artifact-graph@0.14.1`。
+1. 安装插件 0.15.0（见上文）和运行时：`pnpm add -D artifact-graph@0.15.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.14.1",
+  "version": "0.15.0",
   "description": "Artifact-chain intake, review/repair/batch/audit workflows, diagnostics, hooks, and version-lock maintenance helpers.",
   "author": {
     "name": "广州市风荷科技有限公司"

package/adapters/claude/EXTENDED-ARTIFACT-CATALOG.md

@@ -14,8 +14,8 @@ plugin README and INSTALL.md. This document covers opt-in types beyond the core
 
 | Layer | Scope | Responsibility for Extended Types |
 | --- | --- | --- |
-| **artifact-graph** | Deterministic graph capabilities | Reads type definitions from config; indexes artifacts; provides context/packet/validate. Does **not** ship default paths or ID patterns for extended types. Types without configured paths are not indexed. |
-| **artifact-chain-assistant** | General assistant guidance | Provides starter templates, profile suggestions, and generic review checklists. **Templates are guidance, not authority.** Project-local templates and review skills override plugin suggestions. |
+| **artifact-graph** | Deterministic graph capabilities, plus the published common-minimum and project-type standard lists at `artifact-graph/project-artifact-profiles` | Reads type definitions from config; indexes artifacts; provides context/packet/validate. Ships recommendation lists only; it does **not** auto-enable types or ship default paths or ID patterns for extended types. Types without configured paths are not indexed. |
+| **artifact-chain-assistant** | General assistant guidance | Reads the Graph lists, then provides starter templates, adoption-readiness checks, and generic review checklists. **Templates are guidance, not authority.** The assistant does not keep a second list source of truth. Project-local templates and review skills override plugin suggestions. |
 | **Target project** | Final working method | Decides which extended types to enable; maintains config, local templates, review skills, and ID rules. **Project-local overrides plugin suggestions.** Enables new types progressively as maturity grows. |
 
 ## Extended Artifact Type Catalog
@@ -90,15 +90,19 @@ has corresponding files or processes.
 ## Bootstrap Trimming Strategy
 
 Bootstrap selects a **minimum viable profile** rather than enabling all known types.
+The published lists are `artifact-graph/project-artifact-profiles`. Reading them does not enable types.
 
 Rules:
 
-1. **Core set always enabled**: `feature`, `scenario`, `decision`, `design`, `test`, `e2e_test`.
-2. **Contracts by evidence**: Enable only when the project has corresponding interface files (e.g., OpenAPI spec, CLI entry, IPC channel definition).
-3. **Domain/data by project shape**: Enterprise Java/DDD projects may enable `domain_model`; projects with databases may enable `database_migration`.
-4. **Ops by operational process**: Enable only when the project has deployment configs, security review processes, or operational manuals.
-5. **Agent/hook by local files**: Enable only when the project has `skills/`, `policies/`, or hook config files.
-6. **Progressive expansion**: As project maturity grows, add new types in `artifact-graph.config.yaml`. Existing artifacts and traceability relationships are unaffected.
+1. **Common minimum is visible, not auto-enabled**: `feature`, `scenario`, `design`. Missing items stay visible until the project adopts them.
+2. **Only `skill-plugin` has an approved category standard**: it adds `agent_skill` and `e2e_test` on top of the common minimum. Other shapes use the common minimum plus matching stage and capability candidates.
+3. **Stage items stay candidates**: `requirement`, `spec`, and `decision` appear for matching adoption stages and are enabled only by config, profile, or explicit selection.
+4. **Contracts by evidence**: Enable `cli_contract`, `api_contract`, `ui_contract`, `ipc_contract`, or `data_contract` only when the project has corresponding interface files.
+5. **Domain/data by project shape**: Enterprise Java/DDD projects may enable `domain_model`; projects with databases may enable `database_migration`.
+6. **Ops by operational process**: Enable only when the project has deployment configs, security review processes, or operational manuals.
+7. **Agent/hook by local files**: `hook_policy` and `prompt_packet` remain capability candidates for `skill-plugin`; enable them only when the project has `skills/`, `policies/`, or hook config files.
+8. **Release by duty**: Enable `release_policy` and related types only when the project owns publish and distribution.
+9. **Progressive expansion**: As project maturity grows, add new types in `artifact-graph.config.yaml`. Existing extras and traceability relationships are kept.
 
 After bootstrap, the enabled types, paths, and ID patterns are recorded in
 `artifact-graph.config.yaml`. Deferred types and their evidence conditions are documented in the

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

@@ -15,8 +15,8 @@ INSTALL.md。本文档只介绍核心集合之外的可选类型。
 
 | 层级 | 权威范围 | 对扩展制品的职责 |
 |------|---------|-----------------|
-| **artifact-graph** | 确定性图能力 | 从 config 读取类型定义，索引制品，提供 context/packet/validate。**不内置扩展类型的默认路径或 ID 模式。** 未配置路径的类型不会被索引。 |
-| **artifact-chain-assistant** | 通用助手指导 | 提供扩展制品的入门模板、profile 建议和通用审查清单。**模板是指导，不是权威。** 项目本地模板和审查技能覆盖插件建议。 |
+| **artifact-graph** | 确定性图能力，以及随包发布的共同最小清单与项目类型标准（入口 `artifact-graph/project-artifact-profiles`） | 从 config 读取类型定义，索引制品，提供 context/packet/validate。只发布推荐清单，**不自动启用类型，也不内置扩展类型的默认路径或 ID 模式。** 未配置路径的类型不会被索引。 |
+| **artifact-chain-assistant** | 通用助手指导 | 读取 Graph 清单，再提供入门模板、采用就绪检查和通用审查清单。**模板是指导，不是权威。** 助手不另存一份清单真源。项目本地模板和审查技能覆盖插件建议。 |
 | **目标项目** | 最终工作法 | 决定启用哪些扩展类型，维护 config、本地模板、审查技能和 ID 规则。**项目本地覆盖插件建议。** 随成熟度提升逐步启用新类型。 |
 
 ## 扩展制品类型目录
@@ -82,17 +82,19 @@ Agent 与 Hook 制品覆盖 AI 辅助工作流和 CI/CD 门禁。项目存在对
 
 ## Bootstrap 裁剪策略
 
-bootstrap 的职责是按项目形态选出**最小可用 profile**，而不是启用所有已知类型。
+bootstrap 按项目形态选出最小可用 profile，而不是启用所有已知类型。权威清单位于 `artifact-graph/project-artifact-profiles`。读到清单不等于已经启用类型。
 
 裁剪规则：
 
-1. **基础集合始终启用**：`feature`、`scenario`、`decision`、`design`、`test`、`e2e_test`。
-2. **契约类按证据加入**：项目本地存在对应的接口文件（如 OpenAPI spec、CLI 入口、IPC 通道定义）才启用。
-3. **领域与数据类按项目形态加入**：企业 Java/DDD 项目可启用 `domain_model`；使用数据库的项目可启用 `database_migration`。
-4. **运维类按运维流程加入**：项目有部署配置、安全审查流程或运维手册，才启用对应类型。
-5. **Agent/Hook 类按本地文件加入**：项目存在 `skills/`、`policies/` 或 hook 配置文件才启用。
-6. **发布治理类按治理证据加入**：项目存在发布策略、发布脚本或开源合规流程时，才启用 `release_policy`、`publish_skill`、`oss_compliance`。
-7. **渐进扩展**：项目成熟度提升后，可按需在 `artifact-graph.config.yaml` 中新增类型，已有制品和追溯关系不受影响。
+1. **共同最小清单可见，但不自动启用**：`feature`、`scenario`、`design`。尚未采用的项必须仍能看见。
+2. **只有 `skill-plugin` 有获批的类别标准**：在共同最小之上增加 `agent_skill`、`e2e_test`。其余形态按共同最小集，再加匹配的阶段项和能力项。
+3. **阶段项保持候选**：`requirement`、`spec`、`decision` 只在对应采用阶段出现，且须有配置、profile 或明确选择才会启用。
+4. **契约类按证据加入**：项目本地存在对应的接口文件才启用 `cli_contract`、`api_contract`、`ui_contract`、`ipc_contract` 或 `data_contract`。
+5. **领域与数据类按项目形态加入**：企业 Java/DDD 项目可启用 `domain_model`；使用数据库的项目可启用 `database_migration`。
+6. **运维类按运维流程加入**：项目有部署配置、安全审查流程或运维手册，才启用对应类型。
+7. **Agent/Hook 类按本地文件加入**：`hook_policy`、`prompt_packet` 仍是 `skill-plugin` 的能力候选；项目存在对应文件才启用。
+8. **发布治理类按职责加入**：项目承担发布与分发时，才启用 `release_policy`、`publish_skill`、`oss_compliance`。
+9. **渐进扩展**：可按需在 `artifact-graph.config.yaml` 中新增类型；已有追加项和追溯关系予以保留。
 
 bootstrap 执行后，启用的类型、路径和 ID 模式记录在 `artifact-graph.config.yaml` 中；延后启用的
 类型及其证据条件记录在项目制品目录中，让日后的扩展有据可查。

package/adapters/claude/INSTALL.md

@@ -18,7 +18,7 @@ instructions.
 ## Prerequisites
 
 - Node.js `>=22.22.2 <23`.
-- `artifact-graph` 0.14.1 installed in the target project.
+- `artifact-graph` 0.15.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
@@ -30,24 +30,24 @@ instructions.
 
 | Plugin | Verified Runtime | Install |
 | --- | --- | --- |
-| `artifact-chain-assistant` 0.14.1 | `artifact-graph` 0.14.1 | `pnpm add -D artifact-graph@0.14.1` |
+| `artifact-chain-assistant` 0.15.0 | `artifact-graph` 0.15.0 | `pnpm add -D artifact-graph@0.15.0` |
 
 ### Install The Runtime
 
 The default installation path uses the npm registry with a precise version:
 
 ```bash
-pnpm add -D artifact-graph@0.14.1
+pnpm add -D artifact-graph@0.15.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.14.1
+pnpm add -D github:ifoohoo/artifact-graph#artifact-graph-v0.15.0
 ```
 
 > **Never** install with an unlocked range (`artifact-graph`, `artifact-graph@latest`,
-> `artifact-graph@^0.14.1`) or an unpinned GitHub URL (`github:ifoohoo/artifact-graph`).
+> `artifact-graph@^0.15.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`
@@ -74,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.14.1`) and exits non-zero.
+command (`pnpm add -D artifact-graph@0.15.0`) and exits non-zero.
 
 ### CLI Resolution Order
 
@@ -159,7 +159,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.14.1 before the install commands above will
+> must publish and enable `artifact-chain-assistant` 0.15.0 before the install commands above will
 > succeed.
 
 ### Kimi Code
@@ -306,7 +306,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.14.1` (see Prerequisites above). The
+1. **Install the CLI** — `pnpm add -D artifact-graph@0.15.0` (see Prerequisites above). The
    `artifact-chain-setup` skill can run this and the other mechanical install steps for you
    after showing a plan and getting your confirmation.
 2. **Install the plugin** — follow the Codex or Claude Code section above.
@@ -957,13 +957,35 @@ node "$PLUGIN_ROOT/scripts/check-workflow-profile.mjs" \
   --format json
 ```
 
-`candidate_types` contains shape and stage suggestions. `enabled_types` contains only candidates
-backed by the effective `artifact-graph.config.yaml`, an existing workflow profile, or explicit
-`--types` selection. Candidate-only entries are not readiness gaps. For enabled types, the report
-checks registration, starter templates, and generate/review methods separately. Requirement and SPEC
-generation can report `bundled-skill`; its presence never implies that review is ready. A review
-method must be configured in the workflow profile. The checker loads the effective graph config
-through the artifact-graph runtime and does not maintain a second YAML interpretation.
+The assistant reads the list from the resolved Graph package at `artifact-graph/project-artifact-profiles`.
+It does not keep a second copy. Shape and stage suggestions are not proof the project has that
+capability.
+
+`candidate_types` lists common minimum, category standard, stage, capability, and project extras.
+Each item has `applicability` and `enabled`. `enabled` is true only with the effective
+`artifact-graph.config.yaml`, an existing workflow profile, or explicit `--types` selection.
+Stage and capability items are not auto-enabled. The common minimum is `feature`, `scenario`, and
+`design`. Only `skill-plugin` adds `agent_skill` and `e2e_test`. Project configuration owns adoption
+and keeps extra types already present in config or method bindings.
+
+`missing_standard_types` lists unadopted common-minimum or skill-plugin standard types. A successful
+list read is not adoption. This field is separate from `gaps`.
+
+`gaps` lists effective-config failures and missing type declarations, ID patterns, artifact paths or
+directories, starter templates, or executable generate/review methods for enabled types. Candidate-only entries are not readiness gaps. A readable list does not hide missing
+templates or methods.
+
+`profile_contract` reports whether the published list loaded and whether `schema_version` is `1.0`.
+Status `OK` is read-compatibility. It is not `registration.ready`, template readiness, or method
+readiness. If the export is missing (`profiles_export_missing`) or `schema_version` is not `1.0`
+(`profiles_schema_incompatible`), pause only list-dependent recommendations. Do not fall back to a
+copied STAGE/SHAPE table. Extra types already in project config or method bindings remain.
+
+The checker loads the effective graph config through the artifact-graph runtime and does not maintain
+a second YAML interpretation. For enabled types, the report checks registration, starter templates,
+and generate/review methods separately. Requirement and SPEC generation can report `bundled-skill`;
+its presence never implies that review is ready. A review method must be configured in the workflow
+profile.
 
 ### Requirement pool and iteration SPEC
 
@@ -1349,7 +1371,7 @@ with append-only behavior; it does not overwrite local rules.
 ### Recovery Steps
 
 ```bash
-# 1. Install dependencies from lockfile (gets artifact-graph@0.14.1)
+# 1. Install dependencies from lockfile (gets artifact-graph@0.15.0)
 pnpm install --frozen-lockfile
 
 # 2. Install plugin per your host (Codex / Claude Code / Kimi Code)
@@ -1416,7 +1438,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.14.1` and the plugin marketplace repository on an internal registry. The mirror
+`artifact-graph@0.15.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.14.1"
+  version: "0.15.0"
 entries:
   - ref: artifact.prd-feature.default
     provider:

package/adapters/claude/compatibility.json

@@ -1,9 +1,9 @@
 {
   "schemaVersion": "1.0",
-  "pluginVersion": "0.14.1",
+  "pluginVersion": "0.15.0",
   "artifactGraph": {
-    "verifiedVersion": "0.14.1",
-    "installSpec": "artifact-graph@0.14.1",
-    "githubFallbackSpec": "github:ifoohoo/artifact-graph#artifact-graph-v0.14.1"
+    "verifiedVersion": "0.15.0",
+    "installSpec": "artifact-graph@0.15.0",
+    "githubFallbackSpec": "github:ifoohoo/artifact-graph#artifact-graph-v0.15.0"
   }
 }

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

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