@guanlin4924/devflow-pi 0.1.105 → 0.1.107

package/src/dynamic-workflow.ts

@@ -0,0 +1,31 @@
+/** Presentation only. The revisioned Core plan owns every execution fact. */
+export function renderDynamicWorkflow(snapshot: Record<string, unknown>, showHistory = false): string {
+  const tasks = (snapshot.workflow_steps ?? []) as Array<Record<string, unknown>>;
+  const marks: Record<string, string> = { completed: "✓", cancelled: "—", pending: "○", running: "●", checking: "●", failed: "✗" };
+  const labels: Record<string, string> = { cancelled: "已取消", waiting_decision: "待确认", waiting_external: "等待外部条件", failed: "未通过", checking: "验证中" };
+  const visible = !showHistory && tasks.length > 8 ? tasks.filter(task => !["completed", "cancelled"].includes(String(task.status))) : tasks;
+  const lines = visible.map(task => `${marks[String(task.status)] ?? "○"} ${task.label}${labels[String(task.status)] ? `（${labels[String(task.status)]}）` : ""}${task.verification === "stale" ? "（需要重新验证）" : ""}${task.reason ? `：${task.reason}` : ""}`);
+  if (visible.length < tasks.length) lines.push(`已折叠 ${tasks.length - visible.length} 项历史记录，可在 /devflow control 查看全部步骤。`);
+  const decisions = (snapshot.decisions ?? []) as Array<Record<string, unknown>>;
+  for (const decision of decisions.filter(item => item.status === "pending")) lines.push(`待确认：${decision.question}`);
+  return [String(snapshot.current_feature ?? "需求工作流"), `需求说明：${snapshot.document}`, ...lines,
+    snapshot.delivery === "ready" ? "验收证据齐备，可以交付。" : snapshot.delivery === "cancelled" ? "需求已取消，历史结果已保留。" : snapshot.reason ? `需要调整计划：${snapshot.reason}` : "",
+  ].filter(Boolean).join("\n");
+}
+
+export function dynamicWorkflowDirective(snapshot: Record<string, unknown>): string {
+  return [
+    "<devflow-dynamic-workflow>",
+    "读取 skill://workflow-dynamic。当前是动态计划模式，按需求选择工作，不套用固定阶段和逐步审批。",
+    "Core STATE 是计划与结果的唯一写入入口。通过 devflow_plan inspect/revise/claim/report/verify 管理任务。",
+    "先读需求主文档和下列真实状态。没有计划时，核实项目后在主文档验收要求下维护稳定的 ### R-1: 描述 条目，提交中文任务计划。",
+    "已有计划时，执行 Core 选中的任务，读取它的精确 skill。缺项先补证据，技术失败自动修复。完成后继续可执行任务，不逐步询问用户。",
+    "只有真实业务取舍或未获授权的操作才调用 devflow_plan decision，给出 2–3 个选项，首项为推荐并说明影响。",
+    "已有 running/checking 任务先检查实际产物与执行状态；不得盲目重复外部操作。确认旧执行已结束才 recover。",
+    "不生成无关前端任务、空白方案或每技能一份报告。修改需求主文档；源码、测试、API 契约等必要产物照常维护。",
+    "验证必须用 verify 运行声明的命令；review 必须派发 devflow-code-reviewer 独立只读 task，返回 JSON {summary:string,findings:array}，再用 review_result 提交捕获的原始结果。",
+    "Agent 回合结束不等于任务完成；缺失证据、失败、取消与通过必须保持区别。",
+    JSON.stringify(snapshot),
+    "</devflow-dynamic-workflow>",
+  ].join("\n");
+}

package/templates/omp/AGENTS.md

@@ -2,12 +2,17 @@
 
 This repository uses an OMP-native, project-scoped software delivery runtime.
 
+## Gate policy
+
+New requirements use dynamic plans: continue dependency-ready work and automatically repair technical findings. Delivery requires current verification and applicable independent review evidence. Preserve failed, stale, waiting and cancelled results; none means passed. Business choices use concise runtime option cards. Actual operation errors, unreadable control state and revision conflicts reject the affected operation. Existing fixed workflows retain their advisory checkpoint policy; do not apply their fixed stage/document requirements to dynamic tasks.
+
 ## Control plane
 
-- Start only through `/devflow start <feature>|<phase>` after `/devflow doctor` passes; resume with `/devflow resume`.
+- Start only through `/devflow start <feature>|<phase>` after checking `/devflow doctor` and reporting its diagnostics; resume with `/devflow resume`.
 - Inspect workflow state with `devflow_state`; do not infer state from chat history.
 - Initialize delivery with `devflow_bootstrap`.
-- Mutate checkpoints and steps only with `devflow_transition`.
+- When the inspector reports `mode: dynamic`, load `workflow-dynamic` and use `devflow_plan` for task proposals, execution results and verification. The requirement document owns intent; Core owns progress and observed results. Do not generate irrelevant UI tasks or per-skill Markdown/meta pairs.
+- For existing fixed workflows, mutate checkpoints and steps only with `devflow_transition`.
 - To abandon an active feature, use the runtime-confirmed `devflow_transition`
   `cancel-feature` operation or `/devflow abandon`; never edit control files.
 - Never directly edit `.devflow/planning/STATE.md`, `.devflow/planning/.next-intent`, `.devflow/planning/workflows/`, or `.devflow/planning/artifacts/index.yaml`.
@@ -35,4 +40,4 @@ An index accelerates discovery; it never overrides source code, executable tests
 - A model assertion is not validation evidence.
 - Record exact commands and results for tests, builds, migrations, and acceptance checks.
 - When context reconciliation is requested, follow `skill://workflow-context-sync`, validate the required level, then acknowledge through `devflow_context_sync`.
-- Human checkpoints never pass silently in headless mode.
+- Legacy soft checkpoints continue with `continued_with_warning`. Dynamic plans continue from actual task results and never treat an Agent turn ending as successful completion. Never synthesize human approval.