@oevery/rsp 3.3.0 → 4.0.0

package/README.md

@@ -4,31 +4,30 @@ English | [简体中文](./README.zh-CN.md)
 
 **A repository-native engineering workflow for humans and AI agents.**
 
-RSP turns unclear intent into shaped, implemented, reviewed, and verified software changes while keeping project knowledge durable and work recoverable. It uses ordinary repository files—Rules, Specs, and Plans—rather than hidden workflow state.
+RSP turns unclear intent into shaped, implemented, reviewed, and verified software changes while keeping project knowledge durable and work recoverable. It uses ordinary repository files—Skills, Specs, and Plans—rather than hidden workflow state.
 
 ## What RSP helps you do
 
 - Shape ambiguous work into an executable Change.
 - Resolve design questions from repository evidence before implementation.
-- Route diagnosis, implementation, TDD, review, and release work to explicit capabilities.
+- Route diagnosis, implementation, risk-selected test-first work, review, and release work to explicit capabilities.
 - Preserve current facts, lasting rationale, scoped instructions, and completed history in the right owners.
 - Keep authority visible: RSP never infers permission to commit, publish, deploy, or approve work.
 
-```text
-intent → shape → design when needed → diagnose | TDD | implement
-       → review → durable review → archive
-```
+RSP selects the next responsibility from the task and evidence, not a fixed stage pipeline. A settled authorized task can proceed directly to implementation and its own checks; design, review, coordination and lifecycle closeout apply only when needed and permitted.
 
 ## Five-minute start
 
-RSP requires Node.js 22 (`>=22`). Use the current stable release:
+RSP requires Node.js 22 (`>=22`). Run setup from the target project root. For a new project, resolve a stable version once and keep that exact selection. Existing projects use the version in `.rsp/version` and the generated AGENTS entry, not a fresh `latest` resolution. Later `rsp` examples denote that exact invocation or a verified matching executable:
 
 ```bash
-npx -y @oevery/rsp@latest init --with-project-setup
+npm view @oevery/rsp dist-tags.latest
+# Replace <version> with the inspected exact version.
+RSP_VERSION='<version>'
+npx -y @oevery/rsp@"$RSP_VERSION" init --with-project-setup
 # fill .rsp/changes/project-setup.md
 # fill .rsp/specs/design.md
-npx -y @oevery/rsp@latest doctor
-npx -y @oevery/rsp@latest status --json
+npx -y @oevery/rsp@"$RSP_VERSION" status
 ```
 
 Then create and focus one tracked change:
@@ -36,10 +35,12 @@ Then create and focus one tracked change:
 ```bash
 rsp create improve-login "Make login failures actionable"
 rsp focus improve-login
-rsp show --focused
+rsp show improve-login
 ```
 
-Follow the nearest `AGENTS.md`, edit the focused Change as work progresses, run fresh project checks, make the durable-update decision, and archive only after acceptance is satisfied.
+Focus is a set: the setup Change may still be focused alongside improve-login. Use the explicit name to inspect it; show --focused requires exactly one marker.
+
+Confirm that `status` shows the expected work; use read-only `doctor` when diagnosing setup. These are deterministic observations, not semantic acceptance. Follow the nearest `AGENTS.md`, keep the selected Change current and establish applicable required verification, reusing traceable passing evidence when its tested boundary and relevant inputs still apply. Before authorized archive, decide necessary knowledge updates, converge the whole Change and check current readiness.
 
 [Read the full getting-started guide](./docs/site/en/getting-started.md).
 
@@ -47,8 +48,8 @@ Follow the nearest `AGENTS.md`, edit the focused Change as work progresses, run
 
 ```text
 .rsp/
-├── rsp-rules.md       # minimal fallback protocol
-├── specs/             # durable current facts
+├── version            # exact CLI package selection
+├── specs/             # current contracts, boundaries, and constraints
 ├── changes/           # open work
 ├── focus.d/           # markers selecting work; optional short recovery capsules
 └── archives/          # completed history
@@ -65,8 +66,12 @@ A Change is one Markdown file with canonical Proposal, Spec, Design, Tasks, Veri
 - [Configuration reference](./docs/site/en/reference/configuration.md)
 - [CLI reference](./docs/site/en/reference/cli.md)
 - [3.0 migration guide](./docs/migrations/3.0.md) and [3.1 migration guide](./docs/migrations/3.1.md)
-- [Release notes](./docs/releases/3.3.0.md)
-- [Design philosophy](./docs/maintainers/design-philosophy.md) and [maintainer upstream research](./docs/maintainers/upstreams.md)
+- [4.0 migration guide](./docs/migrations/pinned-skills.md)
+- [Changelog](./CHANGELOG.md)
+- [Maintainer tests and Skill validation](./tests/README.md)
+- [Maintainer workflows, publication and documentation recovery](./docs/site/en/contributing.md)
+- [Repository context and contract navigation](./CONTEXT.md)
+- [Authoritative architecture and Specs](./.rsp/specs/design.md) and [maintainer research](./research/README.md)
 
 Run the documentation locally:
 
@@ -80,6 +85,8 @@ The site is only a presentation layer over the Markdown in this repository. It a
 
 ## Platform support
 
-RSP is a tool-agnostic file convention and works with any assistant or editor that can read project files. Humans start here; agents follow the nearest `AGENTS.md`, load `skills/rsp/SKILL.md` when available, and use `.rsp/rsp-rules.md` only when the Skill is unavailable.
+RSP is a tool-agnostic file convention and works with any assistant or editor that can read project files. Humans start here; agents follow the nearest `AGENTS.md`, load the required project Core through host Skill discovery or `.agents/skills/rsp/SKILL.md`. Missing required Skills stop dependent work; there is no Rules fallback. Root `skills/` contains authored sources in the RSP repository, not the consumer installation entry.
+
+RSP 4.0 uses `init` for a complete setup and the selected target CLI's `update` for the complete environment. It pins exact versions and retires Rules and separate Skill installation; existing projects must follow the [4.0 migration guide](docs/migrations/pinned-skills.md). The seven core Skills remain independently invocable; see [Skill ownership](docs/site/en/guides/skills.md).
 
 RSP is licensed under the [MIT License](./LICENSE).

package/README.zh-CN.md

@@ -4,31 +4,30 @@
 
 **面向人类与 AI 智能体的仓库原生工程工作流。**
 
-RSP 把模糊意图转化为经过塑造、实现、审查和验证的软件变更，同时让项目知识可持久化、工作可恢复。它使用普通仓库文件——规则、规格和计划——而不是隐藏的工作流状态。
+RSP 把模糊意图转化为经过塑造、实现、审查和验证的软件变更，同时让项目知识可持久化、工作可恢复。它使用普通仓库文件——Skills、规格和计划——而不是隐藏的工作流状态。
 
 ## RSP 帮助你完成什么
 
 - 把模糊工作塑造成一个可执行 Change。
 - 在实现前根据仓库证据解决设计问题。
-- 把诊断、实现、TDD、审查和发布工作路由给明确的能力。
+- 把诊断、实现、按风险选择的测试先行、审查和发布工作路由给明确的能力。
 - 把当前事实、长期理由、作用域指令和完成历史保存在正确的归属位置。
 - 保持权限可见：RSP 不会推断提交、发布、部署或批准权限。
 
-```text
-意图 → 塑造 → 必要时设计 → 诊断 | TDD | 实现
-     → 审查 → 持久化审查 → 归档
-```
+RSP 根据任务与证据选择下一项职责，不采用固定阶段流水线。已经明确且获授权的任务可以直接实现并完成自身检查；设计、审查、协调和生命周期收尾仅在需要且权限允许时执行。
 
 ## 五分钟入门
 
-RSP 需要 Node.js 22（`>=22`）。使用当前稳定版本：
+RSP 需要 Node.js 22（`>=22`），从目标项目根目录执行初始化。新项目只解析一次稳定版本，后续始终使用同一精确版本；已有项目使用 `.rsp/version` 和 AGENTS 中记录的版本，不重新解析 `latest`。后续 `rsp` 表示该精确调用或已核验版本一致的可执行文件：
 
 ```bash
-npx -y @oevery/rsp@latest init --with-project-setup
+npm view @oevery/rsp dist-tags.latest
+# 把 <version> 替换为已检查的精确版本。
+RSP_VERSION='<version>'
+npx -y @oevery/rsp@"$RSP_VERSION" init --with-project-setup
 # 填写 .rsp/changes/project-setup.md
 # 填写 .rsp/specs/design.md
-npx -y @oevery/rsp@latest doctor
-npx -y @oevery/rsp@latest status --json
+npx -y @oevery/rsp@"$RSP_VERSION" status
 ```
 
 然后创建并聚焦一个受跟踪变更：
@@ -36,10 +35,12 @@ npx -y @oevery/rsp@latest status --json
 ```bash
 rsp create improve-login "让登录失败信息可供用户采取行动"
 rsp focus improve-login
-rsp show --focused
+rsp show improve-login
 ```
 
-遵循最近的 `AGENTS.md`，在工作推进时同步当前聚焦的 Change，运行最新的项目检查，判断是否需要持久化更新，并仅在满足验收条件后归档。
+Focus 是一个集合：project-setup 和 improve-login 可以同时聚焦。使用明确名称查看目标；show --focused 要求恰好一个标记。
+
+确认 `doctor` 显示预期的项目设置，`status` 显示预期工作；这些是确定性观察，不是语义验收。遵循最近的 `AGENTS.md`，保持选中的 Change 与实际结果同步，并建立适用的必需验证：被测边界和相关输入仍然适用时，复用可追溯的通过证据。授权归档前，判断必要的知识更新，收敛整个 Change，再检查当前就绪状态。
 
 [阅读完整入门指南](./docs/site/zh-CN/getting-started.md)。
 
@@ -47,10 +48,10 @@ rsp show --focused
 
 ```text
 .rsp/
-├── rsp-rules.md       # 最小后备协议
-├── specs/             # 持久化的当前事实
+├── version            # 精确的 CLI 软件包版本
+├── specs/             # 当前契约、边界与必要约束
 ├── changes/           # 未完成工作
-├── focus.d/           # 选择当前工作的空标记文件
+├── focus.d/           # 工作选择标记；可附短恢复胶囊
 └── archives/          # 已完成历史
 ```
 
@@ -65,8 +66,12 @@ rsp show --focused
 - [配置参考](./docs/site/zh-CN/reference/configuration.md)
 - [CLI 参考](./docs/site/zh-CN/reference/cli.md)
 - [3.0 迁移指南](./docs/migrations/3.0.md)与 [3.1 迁移指南](./docs/migrations/3.1.md)
-- [发布说明](./docs/releases/3.3.0.md)
-- [设计哲学](./docs/maintainers/design-philosophy.md)与[维护者上游研究](./docs/maintainers/upstreams.md)
+- [4.0 迁移指南](./docs/migrations/pinned-skills.md)
+- [变更日志](./CHANGELOG.md)
+- [维护者测试与 Skill 验证](./tests/README.md)
+- [维护工作流、发布与文档恢复](./docs/site/zh-CN/contributing.md)
+- [仓库上下文与契约导航](./CONTEXT.md)
+- [权威架构与 Specs](./.rsp/specs/design.md)及[维护者研究](./research/README.md)
 
 在本地运行文档：
 
@@ -80,6 +85,8 @@ pnpm docs:build
 
 ## 平台支持
 
-RSP 是与工具无关的文件约定，适用于任何能读取项目文件的助手或编辑器。人类从这里开始；AI 智能体遵循最近的 `AGENTS.md`，优先加载 `skills/rsp/SKILL.md`，仅在 Skill 不可用时使用 `.rsp/rsp-rules.md` 后备协议。
+RSP 是与工具无关的文件约定，适用于任何能读取项目文件的助手或编辑器。人类从这里开始；AI 智能体遵循最近的 `AGENTS.md`，通过宿主 Skill discovery 或 `.agents/skills/rsp/SKILL.md` 加载必需的项目 Core。缺少必需 Skill 时停止依赖工作，不再使用 Rules 后备协议。根目录 `skills/` 是 RSP 仓库中的分发源码，不是消费者的安装入口。
+
+RSP 4.0 用 `init` 完成接入，用选定目标 CLI 的 `update` 一次更新完整环境；固定精确版本，退役 Rules 与独立 Skill 安装流程。已有项目须先阅读 [4.0 迁移指南](docs/migrations/pinned-skills.md)。七个核心 Skills 仍可独立调用，职责见 [Skills 指南](docs/site/zh-CN/guides/skills.md)。
 
 RSP 使用 [MIT 许可证](./LICENSE)。