refactor(cli): 收敛 knowledge-first 命令面

Author: sincerely90

.agents/plugins/marketplace.json

@@ -1,6 +1,6 @@
 {
   "name": "aisee-plugin",
-  "version": "0.6.0",
+  "version": "0.7.0",
   "interface": {
     "displayName": "Aisee Plugin",
     "description": "Aisee plugin marketplace for OpenSpec and Compound Engineering workflows."

README.en.md

@@ -95,11 +95,10 @@ Compound Engineering = optional implementation / review / test consumer
 
 ## Skill Taxonomy
 
-`plugins/aisee-plugin/.codex-plugin/plugin.json` still exposes all 22 public skills through `skills: "./skills/"`, but the default happy path contains only **11 core workflow skills**. The full contract lives in [Skill Taxonomy](plugins/aisee-plugin/references/skill-taxonomy.md).
+`plugins/aisee-plugin/.codex-plugin/plugin.json` still exposes all public skills through `skills: "./skills/"`, but the default happy path contains only **10 core workflow skills**. The full contract lives in [Skill Taxonomy](plugins/aisee-plugin/references/skill-taxonomy.md).
 
 Core workflow:
 
-- `aisee:flow`
 - `aisee:init`
 - `aisee:srs`
 - `aisee:ui-content`
@@ -125,7 +124,6 @@ On-demand extensions:
 - **Schema-aware change planning**: `aisee:change-plan` maps confirmed inputs into independently deliverable OpenSpec changes.
 - **OpenSpec schema pack**: includes app, device, docsite, infra, security, quick-fix, quick-research, and collaboration schemas.
 - **Context packs**: `aisee context pack` generates JSON context for implementation, verification, and review.
-- **Contract context service**: `aisee contract` exposes service contracts through manifest-first and section-level reads for cross-repository frontend/backend collaboration.
 - **Team knowledge guardrails**: `aisee knowledge` retrieves a small number of reviewed engineering lessons through pack/card protocols without turning the knowledge repository into a second specification source.
 - **Anchor-aware traceability**: `aisee get`, `aisee trace`, and `aisee index` connect upstream documents, OpenSpec artifacts, tasks, code paths, tests, and evidence through `doc-ref#LOCAL-ID` or alias anchors.
 - **Verification and archive guardrails**: `aisee:verify` and `aisee:archive-guard` diagnose gaps and risks before archive.
@@ -255,7 +253,6 @@ Check the project state again:
 
 ```bash
 aisee doctor --json
-aisee flow inspect --json
 ```
 
 ## Documentation
@@ -282,18 +279,16 @@ aisee flow inspect --json
 5. openspec validate <change>
 6. aisee:implementation-bridge
 7. implementation / review / test
-8. aisee:verify
-9. aisee:archive-guard
-10. openspec archive <change>
+8. openspec archive <change>
 
 For small, bounded, low-risk work, an abbreviated path is also valid:
 
 ```text
 quick-fix / quick-research / another lightweight schema
   -> change-author
   -> implementation-bridge
-  -> verify
-  -> archive-guard
+  -> implementation / review / test
+  -> archive
 ```
 ```
 
@@ -305,7 +300,6 @@ For existing projects, use `aisee:spec-migrate` to derive OpenSpec baseline spec
 
 | Skill | Purpose |
 | --- | --- |
-| `aisee:flow` | Inspect the current workflow stage and recommend the next step. |
 | `aisee:init` | Initialize or audit `AGENTS.md`, `openspec/project.md`, Aisee docs, memory, and Codex hooks. |
 | `aisee:srs` | Clarify software requirements and produce planning-level SRS documents. |
 | `aisee:ui-content` | Produce UI content specs for pages, elements, states, flows, permissions, and platform differences. |
@@ -372,11 +366,7 @@ aisee schemas check --json
 aisee sources list --json
 aisee sources check --json
 aisee index --json
-aisee flow inspect --json
-aisee flow inspect --change <change> --json
 aisee change inspect <change> --json
-aisee change author-check <change> --json
-aisee gaps --change <change> --json
 aisee context pack --change <change> --for ce-work --json
 aisee context pack --change <change> --for ce-work --knowledge --json
 aisee context pack --change <change> --for aisee-verify --json
@@ -391,12 +381,6 @@ aisee knowledge query --from-change <change> --for ce-work --json
 aisee knowledge index --json
 aisee knowledge index --team-path .aisee/team-knowledge --json
 aisee knowledge promote-batch --curation <path> --team-path .aisee/team-knowledge --pack web-app --json
-aisee contract manifest --json
-aisee contract summary --change <change> --json
-aisee contract get --change <change> --artifact service-contract --section capabilities --json
-aisee contract serve --host 127.0.0.1 --port 8765
-aisee change verify-check <change> --json
-aisee change archive-check <change> --json
 aisee index --json
 aisee get docs/requirements/auth-srs.md#FR-001 --json
 aisee trace srs:auth-login#FR-001 --json
@@ -412,29 +396,8 @@ Key CLI rules:
 - If `aisee/registry/id-registry.json` still exists, treat it as legacy compatibility data rather than a formal authoring entry point.
 - `bootstrap --plan` is a read-only plan and does not perform broad initialization writes.
 - `aisee openspec ensure` only bridges OpenSpec initialization and profile setup. It does not replace `aisee:init`.
-- `aisee contract serve` is a read-only contract context service, not a mock backend, API gateway, or second API source of truth. It binds to `127.0.0.1` by default; LAN access requires explicit `--host 0.0.0.0` and exposes local contract documents to that network.
 - `aisee knowledge query` returns only a small number of guardrails. By default it reads pack manifests and card frontmatter; `--debug` is required for matched card body excerpts.
 
-### Cross-Repository Contract Reads
-
-When frontend and backend are developed in separate repositories, the backend repository, BFF repository, or independent contract repository should own `service-contract.md` and optional machine-readable attachments such as `contracts/openapi.yaml`, `contracts/events.yaml`, `contracts/webhooks.yaml`, or `contracts/proto/*.proto`.
-
-Recommended flow:
-
-```bash
-# In the contract provider repository
-aisee contract manifest --json
-aisee contract summary --change <change> --json
-aisee contract serve --host 127.0.0.1 --port 8765
-
-# In the consumer repository AI context, read the manifest first and fetch small sections as needed
-curl http://127.0.0.1:8765/manifest
-curl http://127.0.0.1:8765/changes/<change>/summary
-curl "http://127.0.0.1:8765/changes/<change>/contracts/service-contract/sections/<section>?max_chars=4000"
-```
-
-OpenSpec/Aisee artifacts remain the authoritative contract source. The HTTP service reads current files on request and returns a JSON view; it does not persist contract copies and does not expose source code, environment variables, secrets, or full-repository search results.
-
 ### Team Knowledge Guardrails
 
 Team knowledge is experimental. It reuses engineering lessons across projects, but it does not replace OpenSpec, `source-map.md`, contracts, tasks, or baseline specs.

README.md

@@ -104,11 +104,10 @@ Compound Engineering = 可选的执行 / 审查 / 测试消费方
 
 ## Skill 分层
 
-`plugins/aisee-plugin/.codex-plugin/plugin.json` 继续通过 `skills: "./skills/"` 暴露全部 22 个公开 skill，但默认 happy path 只包含 **11 个核心主流程 skill**。完整分类合同见 [Skill Taxonomy](plugins/aisee-plugin/references/skill-taxonomy.md)。
+`plugins/aisee-plugin/.codex-plugin/plugin.json` 继续通过 `skills: "./skills/"` 暴露全部公开 skill，但默认 happy path 只包含 **10 个核心主流程 skill**。完整分类合同见 [Skill Taxonomy](plugins/aisee-plugin/references/skill-taxonomy.md)。
 
 核心主流程：
 
-- `aisee:flow`
 - `aisee:init`
 - `aisee:srs`
 - `aisee:ui-content`
@@ -134,7 +133,6 @@ Compound Engineering = 可选的执行 / 审查 / 测试消费方
 - **Schema-aware change planning**：`aisee:change-plan` 将已确认输入映射为可独立交付的 OpenSpec changes。
 - **OpenSpec schema pack**：提供 app、device、docsite、infra、security、quick-fix、quick-research、collaboration 等 schema。
 - **Context packs**：`aisee context pack` 为实现、验证和 review 生成 JSON 上下文。
-- **契约上下文服务**：`aisee contract` 以 manifest-first、section 级读取方式暴露服务契约，支持前后端跨仓库协作。
 - **团队知识 Guardrails**：`aisee knowledge` 基于 pack/card 协议按需检索少量已审查工程经验，不把知识库变成第二份规范事实源。
 - **Anchor-aware traceability**：`aisee get`、`aisee trace` 和 `aisee index` 通过 `doc-ref#LOCAL-ID` / alias anchor 连接上游文档、OpenSpec artifacts、tasks、代码路径、测试和 evidence。
 - **验证与归档门禁**：`aisee:verify` 和 `aisee:archive-guard` 在 archive 前诊断缺口和风险。
@@ -264,7 +262,6 @@ Schema packs 来自 marketplace-installed plugin。`aisee schemas list/check` 
 
 ```bash
 aisee doctor --json
-aisee flow inspect --json
 ```
 
 ## 文档
@@ -291,18 +288,16 @@ aisee flow inspect --json
 5. openspec validate <change>
 6. aisee:implementation-bridge
 7. implementation / review / test
-8. aisee:verify
-9. aisee:archive-guard
-10. openspec archive <change>
+8. openspec archive <change>
 
 对小范围、边界明确、低风险工作，也可以直接走：
 
 ```text
 quick-fix / quick-research / 其它轻量 schema
   -> change-author
   -> implementation-bridge
-  -> verify
-  -> archive-guard
+  -> implementation / review / test
+  -> archive
 ```
 ```
 
@@ -314,16 +309,13 @@ quick-fix / quick-research / 其它轻量 schema
 
 | Skill | 作用 |
 | --- | --- |
-| `aisee:flow` | 检查当前工作流阶段并推荐下一步。 |
 | `aisee:init` | 初始化或审计 `AGENTS.md`、`openspec/project.md`、Aisee docs、memory 和 Codex hooks。 |
 | `aisee:srs` | 澄清软件需求并生成规划级 SRS。 |
 | `aisee:ui-content` | 生成页面、元素、状态、流程、权限和平台差异等 UI 内容规格。 |
 | `aisee:architecture` | 捕获软件架构上下文、技术约束、可复用能力和 artifact hints。 |
 | `aisee:change-plan` | 规划独立 OpenSpec changes 并选择 schema。 |
 | `aisee-schema-pack` | 通过 marketplace plugin 提供并维护 OpenSpec schema packs。 |
 | `aisee:implementation-bridge` | 生成单个 change 的实现交接 brief 和 context pack 摘要。 |
-| `aisee:verify` | 诊断 artifact、task、source-map、ID 和 evidence 缺口。 |
-| `aisee:archive-guard` | 在 `openspec archive` 前给出最终归档建议。 |
 | `aisee:spec-migrate` | 为已有项目整理 OpenSpec baseline specs。 |
 | `aisee:design-spec` | 生成设计规范，不重复 UI 内容规格。 |
 | `aisee:design-assets` | 生成或提取视觉参考和设计素材。 |
@@ -382,11 +374,7 @@ aisee schemas check --json
 aisee sources list --json
 aisee sources check --json
 aisee index --json
-aisee flow inspect --json
-aisee flow inspect --change <change> --json
 aisee change inspect <change> --json
-aisee change author-check <change> --json
-aisee gaps --change <change> --json
 aisee context pack --change <change> --for ce-work --json
 aisee context pack --change <change> --for ce-work --knowledge --json
 aisee context pack --change <change> --for aisee-verify --json
@@ -401,12 +389,6 @@ aisee knowledge query --from-change <change> --for ce-work --json
 aisee knowledge index --json
 aisee knowledge index --team-path .aisee/team-knowledge --json
 aisee knowledge promote-batch --curation <path> --team-path .aisee/team-knowledge --pack web-app --json
-aisee contract manifest --json
-aisee contract summary --change <change> --json
-aisee contract get --change <change> --artifact service-contract --section 能力契约 --json
-aisee contract serve --host 127.0.0.1 --port 8765
-aisee change verify-check <change> --json
-aisee change archive-check <change> --json
 aisee index --json
 aisee get docs/requirements/auth-srs.md#FR-001 --json
 aisee trace srs:auth-login#FR-001 --json
@@ -422,29 +404,8 @@ CLI 关键规则：
 - `aisee/registry/id-registry.json` 如仍存在，只视为历史兼容数据，不再作为正式 authoring 入口。
 - `bootstrap --plan` 是只读计划，不做大而全初始化写入。
 - `aisee openspec ensure` 只桥接 OpenSpec 初始化和 profile 设置，不替代 `aisee:init`。
-- `aisee contract serve` 是只读契约上下文服务，不是 mock backend、API gateway 或第二份接口事实源；默认只监听 `127.0.0.1`，如需局域网访问必须显式传 `--host 0.0.0.0` 并承担暴露本地契约文档的风险。
 - `aisee knowledge query` 只返回少量 guardrails；默认只读 pack manifest 和 card frontmatter，`--debug` 才包含命中 card 的正文摘要。
 
-### 跨仓库接口契约读取
-
-当前后端分离在不同仓库开发时，建议由后端仓库、BFF 仓库或独立契约仓库维护 `service-contract.md` 与可选的机器可读附件，例如 `contracts/openapi.yaml`、`contracts/events.yaml`、`contracts/webhooks.yaml` 或 `contracts/proto/*.proto`。
-
-推荐流程：
-
-```bash
-# 在契约提供方仓库
-aisee contract manifest --json
-aisee contract summary --change <change> --json
-aisee contract serve --host 127.0.0.1 --port 8765
-
-# 在消费方仓库的 AI 上下文中，先读 manifest，再按需读取小 section
-curl http://127.0.0.1:8765/manifest
-curl http://127.0.0.1:8765/changes/<change>/summary
-curl "http://127.0.0.1:8765/changes/<change>/contracts/service-contract/sections/<section>?max_chars=4000"
-```
-
-契约权威来源仍然是 OpenSpec/Aisee artifacts。HTTP 服务只在请求时读取当前文件并返回 JSON 视图，不持久化契约副本，不暴露源码、环境变量、密钥或全仓库搜索结果。
-
 ### 团队知识 Guardrails
 
 团队知识是实验性功能，用于跨项目复用工程经验，但不替代 OpenSpec、`source-map.md`、contracts、tasks 或 baseline specs。

docs/architecture/aisee-cli-context-and-id-registry.md

@@ -117,24 +117,6 @@ aisee get srs:auth-login#FR-001 --json
 
 它不把缓存或摘要当事实源。
 
-### 3.5 `aisee contract *`
-
-只读暴露 change contracts 和被允许的上下文片段。
-
-支持：
-
-- `manifest`
-- `summary`
-- `get`
-- `serve`
-
-跨项目消费者必须：
-
-1. 先读 manifest
-2. 再按 change / artifact / anchor 获取片段
-
-禁止 provider 暴露全仓库任意读取。
-
 ## 4. Source Map 规则
 
 `source-map.md` 是当前 change 的路由中心。

docs/architecture/aisee-openspec-compound-integration.md

@@ -92,8 +92,6 @@ Compound Engineering
 
 进入实现前使用：
 
-- `aisee change author-check`
-- `aisee gaps`
 - `aisee context pack --for ce-work`
 - `aisee:implementation-bridge`
 
@@ -166,10 +164,7 @@ srs:auth-login#FR-001
 
 跨仓库消费者通过：
 
-- `aisee contract manifest`
-- `aisee contract summary`
-- `aisee contract get`
-- `aisee contract serve`
+不再提供跨项目制品获取命令或本地只读服务；当前项目上下文通过 OpenSpec artifacts、`aisee context pack` 和 knowledge 检索提供。
 
 读取 provider 明确暴露的片段。
 

docs/best-practices.en.md

@@ -160,7 +160,7 @@ Rules:
 
 Before creating tasks, entering implementation, proposing reviewer lenses, or recommending a next step, check existing workflows and skills first:
 
-- When there is no explicit change, use `aisee:flow` or `aisee flow inspect --json` to identify the current stage.
+- When there is no explicit change, return to requirements clarification, change-plan, or the current change itself rather than relying on a dedicated flow command.
 - When there is an explicit change, read the target context pack first, such as `aisee context pack --change <change> --for ce-work --json`.
 - `reusable_workflow_candidates` in the `ce-work` context pack is a routing hint only, not a source of truth.
 - Use `ce-plan` only when `requires_ce_plan=true`; its conclusions must be written back to the current schema apply tracks, and only source-map schemas write back to `source-map.md`.
@@ -223,7 +223,7 @@ When `aisee:archive-guard` says archive is not recommended, fix blockers first.
 For frontend/backend split work, the contract provider can expose read-only context:
 
 ```bash
-aisee contract serve --host 127.0.0.1 --port 8765
+Read the current project's OpenSpec artifacts directly or use `aisee context pack`
 ```
 
 Best practices:

docs/best-practices.md

@@ -160,7 +160,7 @@ aisee context pack --change <change> --for ce-code-review --json
 
 创建任务、进入实现、提出审查角色或推荐下一步前，先检查已有 workflow 和 skill：
 
-- 无明确 change 时，先用 `aisee:flow` 或 `aisee flow inspect --json` 判断当前 stage。
+- 无明确 change 时，先回到需求澄清、change-plan 或当前 change 本身，不再依赖单独的 flow 命令判断阶段。
 - 有明确 change 时，优先读取目标 context pack，例如 `aisee context pack --change <change> --for ce-work --json`。
 - `ce-work` context pack 的 `reusable_workflow_candidates` 只是路由提示，不是事实源。
 - `requires_ce_plan=true` 时才按需使用 `ce-plan` 细化执行顺序；结论必须回写当前 schema apply tracks，只有 source-map schema 才回写 `source-map.md`。
@@ -223,7 +223,7 @@ archive 前应满足：
 前后端分离时，推荐 contract provider 暴露只读上下文：
 
 ```bash
-aisee contract serve --host 127.0.0.1 --port 8765
+直接读取当前项目内的 OpenSpec artifacts 或 `aisee context pack` 输出
 ```
 
 最佳实践：

docs/release.md

@@ -34,13 +34,13 @@ Aisee 使用 SemVer：
 
 公开契约分层和破坏性变更判断见 [Compatibility Policy](compatibility-policy.md)。
 
-## 0.6.0 合同提示
+## 0.7.0 合同提示
 
-`0.6.0` 引入的是向后兼容的 CLI JSON 增量字段与执行投影调整：
+`0.7.0` 引入的是命令面重分层与 CLI 职责收缩：
 
-- `aisee context pack --for aisee-verify --json` / `--for ce-work --json` 的 traceability 增加 `intake_sources` 与 `mode`。
-- `aisee context pack --for ce-work --json` 新增 `facts.derived.execution.brief`，并且 ce-work target 不再携带 artifact 正文副本。
-- schema metadata、schema mismatch、schema installed 状态被提升为 author / implementation blocker。
+- `aisee flow *`、`aisee gaps`、`aisee change author-check`、`aisee change verify-check`、`aisee change archive-check`、`aisee contract *` 已从公开 CLI 命令面删除。
+- `aisee context pack --for ce-work --json` / `--for aisee-verify --json` 继续保留，但定位为最小上下文投影，不再搭配独立 gate 命令使用。
+- CLI 重心收敛到 knowledge / memory / bridge / governance；OpenSpec 继续负责 change lifecycle、validate 与 archive authority。
 
 发布说明必须同时覆盖两条分发面：