w2.3c: cutover host prompt + skill sources from runtime-first to protocol-first

Li-Sanze · Li-Sanze · commit ead9b714b840 · 2026-06-08T11:41:09.000+08:00
Replace runtime gate / sopify_runtime / go_plan_runtime references in
tracked source templates (zh + en) with protocol-first entry language:
request admission, 4-step entry order, sopify_writer write boundary.

- Header templates: 3 runtime-first notes → protocol-first (zh + en)
- Design rules: runtime helper boundary section → protocol entry boundary
- Analyze/Design/Develop/KB skill files: remove runtime routing refs
- Golden snapshots regenerated for updated managed block
- tasks.md: sopify_protocol_check scoped as CI/preflight, not host prompt
diff --git a/.sopify-skills/plan/20260605_p8_protocol_kernel_runtime_retirement/plan.md b/.sopify-skills/plan/20260605_p8_protocol_kernel_runtime_retirement/plan.md
@@ -13,9 +13,9 @@ depends_on: [P7 (payload_only_onboarding_mainline), P6 (writer_cutover), P5 (con
 ## Plan Snapshot
 
 - **Goal**: 把 AI 开发过程中的方案、决策、交接、执行/验证证据收敛为可追溯审计资产；真相源从 runtime 切到 protocol.md + sopify_writer，并用 Qoder 证明这些资产可跨宿主接续
-- **Status**: W1 完成 / W2 进行中（W2.0a-W2.3b done，W2.3c next）
-- **Next**: W2.3c — Host Prompt / Copilot Instructions Cutover
-- **Task**: W2.3c 清理 copilot-instructions runtime-first 措辞，然后串行 W2.4 → ...
+- **Status**: W1 完成 / W2 进行中（W2.0a-W2.3c done，W2.4 next）
+- **Next**: W2.4 — Migrate StateStore to 2-File Model
+- **Task**: W2.4 把 StateStore 迁到 active_plan + current_handoff 2 文件模型，然后串行 W2.5 → ...
 
 ## Context / Why
 
diff --git a/.sopify-skills/plan/20260605_p8_protocol_kernel_runtime_retirement/tasks.md b/.sopify-skills/plan/20260605_p8_protocol_kernel_runtime_retirement/tasks.md
@@ -254,13 +254,13 @@ created: 2026-06-05
 
 ### W2.3c Host Prompt / Copilot Instructions Cutover
 
-- [ ] Depends: W2.3b
-- [ ] Input: `.github/copilot-instructions.md`
-- [ ] Output: 清理 runtime-first 措辞（runtime gate / sopify_runtime 引用）
-- [ ] Output: 删除不存在的 `go_plan_runtime.py` 引用
-- [ ] Output: 替换为 protocol-first 入口（protocol.md + sopify_protocol_check + sopify_writer）
-- [ ] Verify: `rg "runtime_gate|sopify_runtime|go_plan_runtime" .github/copilot-instructions.md` returns no matches
-- [ ] Verify: copilot-instructions.md 不再引用 runtime-first 入口
+- [x] Depends: W2.3b
+- [x] Input: `.github/copilot-instructions.md`
+- [x] Output: 清理 runtime-first 措辞（runtime gate / sopify_runtime 引用）
+- [x] Output: 删除不存在的 `go_plan_runtime.py` 引用
+- [x] Output: 替换为 protocol-first 入口（protocol.md + sopify_writer）；sopify_protocol_check 是 CI/preflight 验证项（W2.3b 已接入），不进入宿主 prompt
+- [x] Verify: `rg "runtime_gate|sopify_runtime|go_plan_runtime" .github/copilot-instructions.md` returns no matches
+- [x] Verify: copilot-instructions.md 不再引用 runtime-first 入口
 
 ### W2.4 Migrate StateStore to 2-File Model
 
diff --git a/skills/en/header.md.template b/skills/en/header.md.template
@@ -128,13 +128,11 @@ Complex Task (full 3 phases):
 | `~go plan` | Plan only, no execution |
 | `~go finalize` | Close out the current metadata-managed plan |
 
-Note: Before every Sopify turn, the host must execute the runtime gate and validate its JSON contract. Continue into normal stages only when the gate passes. See `.sopify-skills/blueprint/protocol.md §8.1` for the full gate entry protocol, `allowed_response_mode` values, and ActionProposal capability.
+Note: On each Sopify turn, the host first classifies the user request (consult / quick_fix / new_plan / continue_plan / finalize). Only managed plan / continuation / finalize enter the 4-step protocol entry; consult / quick_fix do not auto-resume active_plan by default. See `.sopify-skills/blueprint/protocol.md §8`.
 
-Note: After runtime execution, the host must consume `.sopify-skills/state/current_handoff.json` structured fields to decide the next step. Respect any pending checkpoint before continuing. See `.sopify-skills/blueprint/protocol.md §8.2` for the full handoff protocol and `required_host_action` values.
+Note: The 4-step entry order for managed plan / continuation / finalize is `state/active_plan.json` → `plan/<id>/plan.md` → `state/current_handoff.json` → `plan/<id>/receipts/`. Read plan.md first for semantic truth, then handoff as a resumption hint; handoff is not a second truth source. Respect any pending checkpoint before continuing.
 
-Note: The host must not self-route before the gate, bypass checkpoint constraints, or write machine truth directly. Routing and state management are owned by the runtime. See `.sopify-skills/blueprint/protocol.md §8.3` for boundaries.
-
-**Host Integration Contract:** See `.sopify-skills/blueprint/protocol.md §8` for the full host runtime integration protocol, including gate entry, handoff consumption, checkpoint handling, runtime helper index, and state file index.
+Note: The host must not bypass checkpoint constraints or write machine truth directly. Protocol state writes (active_plan / current_handoff / receipts) go through `sopify_writer`. See `.sopify-skills/blueprint/protocol.md §8`: Host Protocol Entry Contract.
 
 ---
 
@@ -361,7 +359,7 @@ Next: Please verify the functionality
 ~go finalize     # Explicitly close out the current metadata-managed plan
 ```
 
-**Runtime helpers and state files:** See `.sopify-skills/blueprint/protocol.md §8.4–8.5` for the full runtime helper index and state file index.
+**Protocol state files:** See `.sopify-skills/blueprint/protocol.md §8`.
 
 **Configuration File:** `sopify.config.yaml` (project root)
 
diff --git a/skills/en/skills/sopify/analyze/SKILL.md b/skills/en/skills/sopify/analyze/SKILL.md
@@ -49,4 +49,4 @@ The script returns JSON with total score, threshold result, and missing dimensio
 ## Boundaries
 
 - This skill does not generate a plan package directly; hand off to `design`.
-- This skill does not execute code changes directly; hand off to `develop` or runtime routing.
+- This skill does not execute code changes directly; hand off to `develop`.
diff --git a/skills/en/skills/sopify/design/SKILL.md b/skills/en/skills/sopify/design/SKILL.md
@@ -44,4 +44,4 @@ The script returns JSON with the suggested level and explicit reasons.
 ## Boundaries
 
 - This skill does not execute code changes directly; hand off to `develop`.
-- This skill does not replace runtime routing; it defines the plan structure and task contract only.
+- This skill does not handle routing or protocol state writes; it defines the plan structure and task contract only.
diff --git a/skills/en/skills/sopify/design/references/design-rules.md b/skills/en/skills/sopify/design/references/design-rules.md
@@ -71,15 +71,9 @@ Task markers:
   - `~go plan`: stop after rendering the plan summary.
 - If the user gives plan feedback, stay in this phase, update the files, and render again.
 
-## Runtime helper boundaries
+## Protocol entry boundary
 
-When the repo contains `scripts/sopify_runtime.py` and the input is the raw request:
-
-1. Prefer the default runtime entry; do not rewrite it manually into `~go plan`.
-2. When the intent is explicitly `~go plan`, prefer `scripts/go_plan_runtime.py`.
-3. `go_plan_runtime.py` is plan-only and not a generic default entry.
-
-Generate plan files manually only when the runtime helpers are absent.
+Plan structure and task splitting are owned by this skill; protocol state writes (active_plan / current_handoff / receipts) go through `sopify_writer`, not this skill directly.
 
 ## Naming rules
 
diff --git a/skills/en/skills/sopify/develop/references/develop-rules.md b/skills/en/skills/sopify/develop/references/develop-rules.md
@@ -174,7 +174,7 @@ Execution constraints:
 - Execution failure or `inconclusive` verdict does not block the main flow.
 - `concerns` / `needs_human_triage` are shown to the user and await their decision; do not auto-write checkpoints or auto-modify code.
 - If prerequisites are not met (e.g. CLI not installed), skip and log the reason without blocking.
-- Note: Phase 4a stays in Convention mode; this does not introduce `bridge.py`, `pipeline_hooks`, or a runtime lifecycle hook.
+- Note: Phase 4a stays in Convention mode; this does not introduce `bridge.py` or `pipeline_hooks`.
 
 ## Step 4: Sync the knowledge base
 
diff --git a/skills/zh/header.md.template b/skills/zh/header.md.template
@@ -128,13 +128,11 @@ Next: {下一步提示}
  | `~go plan` | 只规划不执行 |
  | `~go finalize` | 对当前 metadata-managed plan 执行收口归档 |
 
-说明：每次进入新的 Sopify 回合前，宿主必须先执行 runtime gate 并消费其 JSON contract；仅当 gate 通过时才可进入后续阶段。详见 `.sopify-skills/blueprint/protocol.md §8.1`：gate 入口协议、`allowed_response_mode` 值域、ActionProposal capability。
+说明：每次进入 Sopify 回合时，宿主先判断用户请求意图（consult / quick_fix / new_plan / continue_plan / finalize）。仅 managed plan / continuation / finalize 进入 4 步协议入口；consult / quick_fix 默认不自动接续 active_plan。详见 `.sopify-skills/blueprint/protocol.md §8`。
 
-说明：runtime 执行后，宿主必须优先消费 `.sopify-skills/state/current_handoff.json` 结构化字段决定下一步；有未完成 checkpoint 时必须先响应 checkpoint 再继续。详见 `.sopify-skills/blueprint/protocol.md §8.2`：handoff 消费协议与 `required_host_action` 值域。
+说明：managed plan / continuation / finalize 的 4 步入口顺序为 `state/active_plan.json` → `plan/<id>/plan.md` → `state/current_handoff.json` → `plan/<id>/receipts/`。先读 plan.md 建立语义真相，再读 handoff 作为恢复提示；handoff 不是第二真相源。有未完成 checkpoint 时必须先响应再继续。
 
-说明：宿主不得在 gate 前自行路由、绕过 checkpoint 约束、或直接写入 machine truth。路由与状态管理归 runtime 所有。详见 `.sopify-skills/blueprint/protocol.md §8.3`：宿主行为边界。
-
-**宿主接入约定：** 详见 `.sopify-skills/blueprint/protocol.md §8`：完整 gate 入口协议、handoff 消费规则、checkpoint 处理、runtime helper 索引与 state 文件索引。
+说明：宿主不得绕过 checkpoint 约束或直接写入 machine truth。协议状态写入（active_plan / current_handoff / receipts）统一走 `sopify_writer`。详见 `.sopify-skills/blueprint/protocol.md §8`：Host Protocol Entry Contract。
 
 ---
 
@@ -361,7 +359,7 @@ Next: 请验证功能
 ~go finalize     # 显式收口当前 metadata-managed plan
 ```
 
-**Runtime helper 与状态文件索引：** 详见 `.sopify-skills/blueprint/protocol.md §8.4–8.5`。
+**协议状态文件索引：** 详见 `.sopify-skills/blueprint/protocol.md §8`。
 
 **配置文件：** `sopify.config.yaml` (项目根目录)
 
diff --git a/skills/zh/skills/sopify/analyze/SKILL.md b/skills/zh/skills/sopify/analyze/SKILL.md
@@ -49,4 +49,4 @@ python3 skills/zh/skills/sopify/analyze/scripts/score_requirement.py \
 ## 边界
 
 - 不在本技能直接生成方案包（交给 `design`）。
-- 不在本技能直接执行代码修改（交给 `develop` 或 runtime 路由）。
+- 不在本技能直接执行代码修改（交给 `develop`）。
diff --git a/skills/zh/skills/sopify/design/SKILL.md b/skills/zh/skills/sopify/design/SKILL.md
@@ -44,4 +44,4 @@ python3 skills/zh/skills/sopify/design/scripts/select_plan_level.py \
 ## 边界
 
 - 不直接执行代码任务（交给 `develop`）。
-- 不替代 runtime 的路由决策，仅提供方案结构与任务拆分契约。
+- 不负责路由或协议状态写入，仅提供方案结构与任务拆分契约。
diff --git a/skills/zh/skills/sopify/design/references/design-rules.md b/skills/zh/skills/sopify/design/references/design-rules.md
@@ -71,15 +71,9 @@
   - `~go plan` 触发：只输出方案摘要并停止。
 - 用户反馈修改意见：留在本阶段，更新文件后再次输出摘要。
 
-## runtime helper 边界
+## 协议入口边界
 
-当仓库存在 `scripts/sopify_runtime.py` 且输入为原始请求时：
-
-1. 优先交给默认 runtime 入口，不手工强制改写为 `~go plan`。
-2. 明确是 `~go plan` 路径时，优先调用 `scripts/go_plan_runtime.py`。
-3. `go_plan_runtime.py` 仅用于 plan-only slice。
-
-入口缺失时，才按本技能模板手工生成方案文件。
+方案结构与任务拆分由本技能负责；协议状态写入（active_plan / current_handoff / receipts）统一走 `sopify_writer`，不在本技能直接写入。
 
 ## 命名规则
 
diff --git a/skills/zh/skills/sopify/develop/references/develop-rules.md b/skills/zh/skills/sopify/develop/references/develop-rules.md
@@ -174,7 +174,7 @@ Stage B `code_quality` 至少检查：
 - 执行失败或结果 `inconclusive` 不阻断主流程。
 - `concerns` / `needs_human_triage` 只展示并等待用户决定，不自动写 checkpoint、不自动改代码。
 - 若前置条件不满足（如 CLI 未安装），跳过并记录原因，不阻断。
-- 注释：Phase 4a 仅采用 Convention 模式；这里不引入 `bridge.py`、`pipeline_hooks` 或 runtime lifecycle hook。
+- 注释：Phase 4a 仅采用 Convention 模式；这里不引入 `bridge.py` 或 `pipeline_hooks`。
 
 ## 步骤 4：知识库同步
 
diff --git a/skills/zh/skills/sopify/kb/SKILL.md b/skills/zh/skills/sopify/kb/SKILL.md
@@ -25,7 +25,7 @@ description: 知识库管理技能；知识库操作时读取；包含初始化
 ├── history/
 │   ├── index.md            # 归档索引
 │   └── YYYY-MM/
-└── state/                  # runtime machine truth
+└── state/                  # protocol state
 ```
 
 ## 初始化策略
diff --git a/tests/golden-snapshots.json b/tests/golden-snapshots.json
@@ -8,13 +8,13 @@
   },
   "protocol_version": "1.0",
   "snapshots": {
-    "codex:zh-CN:header": "d768b84e5d07c1b955febe7ac05807906446aaedf416dfc78166d5b11c62602e",
-    "codex:en-US:header": "c99c1032818d0d016736fee847eb421131cc886a90120ad44669debfcc0378be",
-    "claude:zh-CN:header": "70d0cbf21c018b8333c62dca916cccb17889336458d7ee0aa08371a543832ae3",
-    "claude:en-US:header": "79156111d9dcb5899785fdc382d81e5739fc5fd8033a11c50a462d3d4ba552c8",
-    "copilot:zh-CN:managed_block_payload": "6a8342579829efe868c85738e811d86402da7cd16ebf905da81a3fea8082d7f9",
-    "skills:zh-CN:tree": "84f417998dcc6a3ad4434c7d295f6efcfd58b88780ad41c9c0c890e98c60aedb",
-    "copilot:en-US:managed_block_payload": "f6ba2c14cbb3d36bce48956ca1bc9893d503cf0fd512db68689aa63b6c0ca131",
-    "skills:en-US:tree": "7ac05bbb4c50b2aefa5a5bb7df270ff6ee1c46ca71cc7513d84dfb347e124128"
+    "codex:zh-CN:header": "037c7805526578222e27291604c9ae2daa7095c86193b6e8fdde5a3f714cec6c",
+    "codex:en-US:header": "4fa9efd7b72c2ed5e783cfec6c18e1c25e880c4e6757b196ce49c9125e574c6a",
+    "claude:zh-CN:header": "45509aba67ba7b3fbc84615ebfa45231f78e6f71e9b17f6032d2cc50a7bf4eec",
+    "claude:en-US:header": "03f4e7e85486519ac1dd6615f2ad954ba20a1feda4779980acc5e1055848e11b",
+    "copilot:zh-CN:managed_block_payload": "b0ab09c9326af88fb1c1b5e7679615022f4e33b8fa1b45ab4cf56077a8a873a0",
+    "skills:zh-CN:tree": "5a1c3ab3cc4074c7781c62fa791a22c3e77dc409ba714bc59e50290a62d90d3a",
+    "copilot:en-US:managed_block_payload": "5df6e7bc0a40ad6959ac769c4a1c8524726c22d5ef910f73229556e86290ea4b",
+    "skills:en-US:tree": "2032d4e523daedd74cda8b848031065703a1c5daec6bbcc70fcb792d05d93e5f"
   }
 }
