@mingfuyun/star-allinone 0.4.19 → 0.4.20

package/docs/skills/dev-flow/gates.md

@@ -1,12 +1,15 @@
 # 确认门禁口令
 
 > 维护源：能力包 `docs/skills/dev-flow/gates.md`  
-> 跨仓统一；三道门禁**互不推断**。
+> 跨仓统一。方案、提交、测发三道门禁互不推断。校验豁免不代替任何一道门禁。
 
 | 门禁 | 口令（须字面接近） | 不可替代为 |
 | --- | --- | --- |
-| 方案 | `确认方案` | 「确认」「OK」、提交/测发口令 |
+| 方案 | `确认方案` | 「确认」「OK」、提交/测发口令。只用于需求或接口调整 |
 | 提交 | `确认提交` / `确认提交并推送` | 方案确认、测发确认、「确认」单字 |
 | 测发 | `确认推送流水线` / `发布测试环境` | push 成功、提交确认、方案确认 |
+| 校验豁免 | `豁免校验继续提交` | 「继续吧」「OK」。只跳过 verify 拦截，之后仍须 `确认提交` |
+
+只说「按照星系流程 提交代码」或「按照星系流程 发布流水线」时，不用方案门禁。
 
 `确认方案` ≠ `确认提交` ≠ `确认推送流水线`

package/docs/skills/dev-flow/session-file.md

@@ -0,0 +1,21 @@
+# 续跑会话文件
+
+> 维护源：能力包 `docs/skills/dev-flow/session-file.md`  
+> 需求或接口调整需要跨会话续跑时，按下面的形状写入业务仓 `.agents/dev-flow-session.md`。没有进行中的单就不要创建。
+
+```text
+phase: await_plan
+plan_confirmed: no
+summary: …
+blocked: 无
+next_action: 用户回复「确认方案」
+gates:
+  plan: waiting
+  commit: not_started
+  publish: not_started
+verify_waiver: no
+```
+
+`plan_confirmed` 只有用户说过 `确认方案` 才写 `yes`。禁止默认写成 `yes`。
+
+只提交或只发布时不要补方案确认：`plan_confirmed` 保持 `no`，`phase` 用 `await_commit` 或 `await_publish`。

package/docs/skills/dev-flow/session-protocol.md

@@ -32,6 +32,8 @@
 
 单点 skill 不输出这些字段。只有 `reply-layout.md` 的「流程停住」才输出。
 
+续跑文件的形状见 [session-file.md](session-file.md)。写入业务仓 `.agents/dev-flow-session.md`，不要另起字段名。
+
 ---
 
 ## 示例

package/examples/AGENTS.md

@@ -19,7 +19,7 @@ Props for `MFProTable` are in `.agents/skills/shared-project-conventions/referen
 
 In business repos, dialogue uses **one entry only**: `$custom-entry`. It reads this file and `custom-entry/references/*`, then delegates to `shared-*` or internal `custom-*`. Do not treat direct `$shared-*` as the production entry.
 
-- Full requirement / end-to-end flow: intent `flow` (orchestrator `shared-dev-flow` when available; until then: output an implementation plan, wait for `确认方案`, then follow the composite order in `$custom-entry`).
+- Full requirement or API change: intent `flow` → `shared-dev-flow`. Output a plan and wait for `确认方案` before code changes. Submit-only and publish-only phrases stay on the single-point skills and skip `确认方案`.
 - One endpoint: via `$custom-entry` → `shared-api-to-service`, or `pnpm exec star-allinone gen service --operation "METHOD /path/"`.
 - Pages: via `$custom-entry` → `shared-design-to-page`. Standard lists run `pnpm exec star-allinone gen page` inside that skill.
 - Project health: `pnpm exec star-allinone doctor`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mingfuyun/star-allinone",
-  "version": "0.4.19",
+  "version": "0.4.20",
   "description": "星系运维前端能力包",
   "main": "dist/index.js",
   "bin": {

package/scripts/cli.js

@@ -29,6 +29,7 @@ docs/skills/overview.md is copied to shared-project-conventions/references/skill
 docs/skills/dev-flow/*.md is copied into skills/shared/dev-flow/references/ before that skill is synced.
 It never writes ~/.codex/skills and never modifies custom-* skills.
 If <project>/AGENTS.md is missing, it copies examples/AGENTS.md once.
+If AGENTS.md exists, sync only replaces the pre-dev-flow fallback sentence and the missing command-card path.
 
 doctor checks config, OpenAPI, MFRequest, MFProTable, skill sync, and bad imports.
 
@@ -134,6 +135,7 @@ const DEV_FLOW_REFERENCE_DOCS = [
   'verify-commands.md',
   'gates.md',
   'session-protocol.md',
+  'session-file.md',
 ];
 
 /** docs/skills/dev-flow/ is the only source; refresh skill references before sync. */
@@ -247,6 +249,7 @@ function syncProject(options) {
   pruneStaleShared(destination, prefix, syncedNames, options);
   writeSyncStamp(destination, prefix, syncedNames, options);
   seedAgentsMarkdown(target, options);
+  refreshAgentsNotes(target, options);
   console.log(`${options.dryRun ? 'Would sync' : 'Synced'} shared skills -> ${destination}`);
 }
 
@@ -275,6 +278,30 @@ function seedAgentsMarkdown(target, options) {
   if (!options.dryRun) fs.copyFileSync(source, dest);
 }
 
+const AGENTS_NOTE_REPLACEMENTS = [
+  [
+    '`shared-dev-flow` 就绪前：先出实现方案，等 `确认方案`，再按复合请求顺序执行',
+    '`shared-dev-flow`。需求或接口调整先出方案并等 `确认方案`。只提交或只发布不进状态机，回复与单点相同',
+  ],
+  [
+    '完整口令卡见本机工作区 `dev-agent/研发流程-口令卡.md`（与团队文档同步时以此口径为准）。',
+    '完整口令见 `.agents/skills/shared-dev-flow/references/gates.md`（维护源：能力包 `docs/skills/dev-flow/gates.md`）。',
+  ],
+];
+
+function refreshAgentsNotes(target, options) {
+  const dest = path.join(target, 'AGENTS.md');
+  if (!fs.existsSync(dest)) return;
+  const original = fs.readFileSync(dest, 'utf8');
+  let next = original;
+  for (const [from, to] of AGENTS_NOTE_REPLACEMENTS) {
+    if (next.includes(from)) next = next.split(from).join(to);
+  }
+  if (next === original) return;
+  console.log(`${options.dryRun ? '[dry-run] ' : ''}AGENTS.md flow notes`);
+  if (!options.dryRun) fs.writeFileSync(dest, next);
+}
+
 function main() {
   const [group, command, ...rest] = process.argv.slice(2);
   if (group === 'skills') {

package/scripts/gen/doctor.js

@@ -318,6 +318,34 @@ function runDoctor(cwd, options = {}) {
     findings.push(check(true, 'ok', 'Overlay imports use @mingfuyun/star-allinone or none found'));
   }
 
+  const agentsFile = path.join(root, 'AGENTS.md');
+  if (fs.existsSync(agentsFile)) {
+    const agents = fs.readFileSync(agentsFile, 'utf8');
+    if (agents.includes('就绪前') || agents.includes('研发流程-口令卡.md')) {
+      findings.push(check(false, 'error', 'AGENTS.md still has the pre-dev-flow fallback or a missing command-card path. Run skills sync'));
+    } else {
+      findings.push(check(true, 'ok', 'AGENTS.md flow sentence'));
+    }
+  }
+  const layoutFile = path.join(skillsDir, `${prefix}i-have-adhd`, 'reply-layout.md');
+  const gatesFile = path.join(skillsDir, `${prefix}dev-flow`, 'references', 'gates.md');
+  const sessionFile = path.join(skillsDir, `${prefix}dev-flow`, 'references', 'session-file.md');
+  if (!fs.existsSync(layoutFile) || !fs.readFileSync(layoutFile, 'utf8').includes('## 测发结果')) {
+    findings.push(check(false, 'error', 'reply-layout.md is missing the 测发结果 block. Run skills sync'));
+  } else {
+    findings.push(check(true, 'ok', 'reply-layout.md'));
+  }
+  if (!fs.existsSync(gatesFile) || !fs.readFileSync(gatesFile, 'utf8').includes('豁免校验继续提交')) {
+    findings.push(check(false, 'error', 'gates.md is missing 豁免校验继续提交. Run skills sync'));
+  } else {
+    findings.push(check(true, 'ok', 'gates.md exemption'));
+  }
+  if (!fs.existsSync(sessionFile) || !fs.readFileSync(sessionFile, 'utf8').includes('plan_confirmed')) {
+    findings.push(check(false, 'error', 'session-file.md is missing. Run skills sync'));
+  } else {
+    findings.push(check(true, 'ok', 'session-file.md'));
+  }
+
   printReport(root, findings);
   return findings;
 }

package/skills/shared/dev-flow/SKILL.md

@@ -70,7 +70,7 @@ next_action: …
 
 新会话继续同一单时：
 
-1. 先读 `.agents/dev-flow-session.md`（若有），或请用户确认上一 `phase`。
+1. 先读 `.agents/dev-flow-session.md`（若有）。没有就请用户确认上一 `phase`。文件形状以 [references/session-file.md](references/session-file.md) 为准，`plan_confirmed` 禁止默认 `yes`。
 2. 上一阶段是需求或接口调整，且没确认过方案：从 `plan` 或 `await_plan` 恢复。**禁止**默认方案已确认。
 3. 上一阶段只是提交代码或发布流水线：从 `await_commit` 或 `await_publish` 恢复，不要补 `确认方案`。
 4. 不确定上一阶段是哪一种：问一句，不要默认已经 `确认方案`。

package/skills/shared/dev-flow/references/gates.md

@@ -3,12 +3,15 @@
 # 确认门禁口令
 
 > 维护源：能力包 `docs/skills/dev-flow/gates.md`  
-> 跨仓统一；三道门禁**互不推断**。
+> 跨仓统一。方案、提交、测发三道门禁互不推断。校验豁免不代替任何一道门禁。
 
 | 门禁 | 口令（须字面接近） | 不可替代为 |
 | --- | --- | --- |
-| 方案 | `确认方案` | 「确认」「OK」、提交/测发口令 |
+| 方案 | `确认方案` | 「确认」「OK」、提交/测发口令。只用于需求或接口调整 |
 | 提交 | `确认提交` / `确认提交并推送` | 方案确认、测发确认、「确认」单字 |
 | 测发 | `确认推送流水线` / `发布测试环境` | push 成功、提交确认、方案确认 |
+| 校验豁免 | `豁免校验继续提交` | 「继续吧」「OK」。只跳过 verify 拦截，之后仍须 `确认提交` |
+
+只说「按照星系流程 提交代码」或「按照星系流程 发布流水线」时，不用方案门禁。
 
 `确认方案` ≠ `确认提交` ≠ `确认推送流水线`

package/skills/shared/dev-flow/references/session-file.md

@@ -0,0 +1,23 @@
+<!-- 维护源：能力包 docs/skills/dev-flow/session-file.md — 勿在业务仓改此副本 -->
+
+# 续跑会话文件
+
+> 维护源：能力包 `docs/skills/dev-flow/session-file.md`  
+> 需求或接口调整需要跨会话续跑时，按下面的形状写入业务仓 `.agents/dev-flow-session.md`。没有进行中的单就不要创建。
+
+```text
+phase: await_plan
+plan_confirmed: no
+summary: …
+blocked: 无
+next_action: 用户回复「确认方案」
+gates:
+  plan: waiting
+  commit: not_started
+  publish: not_started
+verify_waiver: no
+```
+
+`plan_confirmed` 只有用户说过 `确认方案` 才写 `yes`。禁止默认写成 `yes`。
+
+只提交或只发布时不要补方案确认：`plan_confirmed` 保持 `no`，`phase` 用 `await_commit` 或 `await_publish`。

package/skills/shared/dev-flow/references/session-protocol.md

@@ -34,6 +34,8 @@
 
 单点 skill 不输出这些字段。只有 `reply-layout.md` 的「流程停住」才输出。
 
+续跑文件的形状见 [session-file.md](session-file.md)。写入业务仓 `.agents/dev-flow-session.md`，不要另起字段名。
+
 ---
 
 ## 示例