@linimin/pi-letscook 0.1.50 → 0.1.52

package/scripts/release-check.sh

@@ -4,45 +4,52 @@ set -euo pipefail
 ROOT="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"
 cd "$ROOT"
 
-echo "[release-check] running control-plane validation, bare /cook parity, role-runner extraction, startup/refocus/context regressions, canonical evidence artifact, active-slice contract, observability, legacy cleanup, evaluator calibration, and rubric contract coverage"
+echo "[release-check] running control-plane validation, /cook public parity, workflow-aware router coverage, role-runner extraction, startup/refocus/context regressions, canonical evidence artifact, active-slice contract, observability, legacy cleanup, evaluator calibration, and rubric contract coverage"
 bash .agent/verify_completion_control_plane.sh
 
-echo "[release-check] verifying public /cook parity"
+echo "[release-check] verifying public /cook parity and workflow-aware router docs/help"
 python3 - <<'PY'
 import re
 from pathlib import Path
 
 checks = {
     "README.md": [
-        "`/cook` supports both bare discussion-driven startup and optional inline intent hints.",
-        "`/cook <hint>` acts as a high-priority intent hint that helps proposal derivation interpret the recent discussion",
-        "clarify the mission in the main chat before rerunning `/cook`",
-        "Matching or unclear discussion resumes from canonical `.agent/**` state.",
-        "approval-only Start/Cancel gate",
-        "Start new workflow from recent discussion",
-        "fails closed instead of guessing",
-        "README/CHANGELOG updates still count as concrete repo changes",
-        "assistant-produced summaries and plan/spec/design-doc/proposal-only artifacts do not",
-        "Assistant/summary artifacts or plan/spec/design-doc/proposal-only context do not refocus the workflow.",
-        "Optional `/cook <hint>` text biases that routing and candidate ranking toward the hinted implementation intent",
+        "Natural-language routing is optional and shipped in three modes: `off` disables it, `assist` offers short confirm-first handoffs after clear workflow discussion, and `router` reviews each non-bypass user turn before implementation starts while leaving ordinary questions in the main chat.",
+        "Set `PI_COMPLETION_TRIGGER_MODE` before starting Pi if you want to change how natural-language routing behaves:",
+        "- `off` — natural-language routing is disabled. Only explicit `/cook` or `/cook <hint>` can enter the workflow.",
+        "- `assist` *(default)* — after clear discussion of a concrete repo change, short execution handoff phrases such as `開始做`, `開始實作`, or `go ahead` can offer to enter the same `/cook` flow before the primary agent starts implementation work.",
+        "- `router` — the workflow-aware router reviews each non-bypass normal user turn before implementation starts.",
+        "the original message only reaches the normal chat path if you explicitly choose **Send as normal chat**",
+        "Explicit `/cook` is always the canonical fallback, even when natural-language routing is enabled in `assist` or `router` mode.",
+        "router-mode false positives and classifier failures stay fail-closed unless you explicitly choose **Send as normal chat**",
+        "bash ./scripts/cook-trigger-routing-test.sh",
     ],
     "CHANGELOG.md": [
-        "restored optional `/cook <hint>` support as a soft intent hint that biases context analysis, proposal ranking, active-workflow disambiguation, and next-round startup without bypassing fail-closed routing or the approval-only Start/Cancel gate",
-        "removed inline `/cook <text>` argument support so bare `/cook` is now the only supported workflow entrypoint",
-        "historically allowed `/cook <hint>` as an analyst-only high-priority prompt",
+        "updated README/help/release parity copy to describe the shipped `off` / `assist` / `router` natural-language routing behavior truthfully while keeping `/cook` as the canonical confirm-first workflow boundary and manual fallback",
+        "documented the explicit router-mode **Send as normal chat** recovery path as a user choice, not as a silent downgrade, and kept public copy scoped to currently shipped router behavior rather than future auto-mode plans",
+        "made `npm run release-check` fail closed on the shipped workflow-aware router docs/help contract while continuing to rerun `bash ./scripts/cook-trigger-routing-test.sh` alongside the existing `/cook` smoke/refocus/context regressions",
     ],
     "extensions/completion/index.ts": [
-        'description: "/cook workflow: start, continue, refocus, or start the next round (optional hint supported)"',
+        'description: "/cook workflow: start, continue, refocus, or start the next round; /cook stays canonical while natural-language routing can be off, assist, or router"',
         'const COOK_BARE_ONLY_GUIDANCE =',
-        '"/cook supports optional inline hints as high-priority intent cues, but mission selection still comes from recent discussion, repo truth, and the approval-only confirmation flow."',
-        '"/cook failed closed because recent discussion did not produce a clear execution-ready Mission/Scope/Constraints/Acceptance proposal for concrete repo changes. Clarify the concrete repo changes in the main chat and rerun /cook."',
+        '"/cook remains the canonical workflow boundary. Natural-language routing can stay off, run in assist mode for short confirm-first handoffs, or run in router mode to review each non-bypass user turn before implementation starts, but the shared /cook flow still owns mission selection and confirmation."',
+        '"/cook failed closed because recent discussion did not produce a clear execution-ready Mission/Scope/Constraints/Acceptance proposal for concrete repo changes. Assist and router modes only offer the same /cook flow, and router recovery only replays to normal chat when you explicitly choose Send as normal chat, so clarify the concrete repo changes in the main chat and rerun /cook."',
     ],
 }
 
 forbidden = {
-    "README.md": ["compatibility" + " shim", "optional inline /cook hint"],
+    "README.md": [
+        "Assist-mode natural-language handoff can also offer to enter that same `/cook` flow before the primary agent starts implementation work, but `/cook` remains the canonical workflow boundary.",
+        "## Natural-language handoff (assist mode)",
+    ],
     "CHANGELOG.md": ["compatibility" + " shim"],
-    "extensions/completion/index.ts": ["temporary" + " compatibility" + " shim, pass /cook", "optional inline /cook hint"],
+    "extensions/completion/index.ts": [
+        'description: "/cook workflow: start, continue, refocus, or start the next round; assist-mode natural-language handoff can offer the same /cook boundary"',
+        '"/cook remains the canonical workflow boundary. Assist-mode natural-language handoff can offer to enter the same /cook flow before implementation starts, while mission selection still comes from recent discussion, repo truth, and the approval-only confirmation flow."',
+        '"/cook failed closed because recent discussion did not produce a clear execution-ready Mission/Scope/Constraints/Acceptance proposal for concrete repo changes. Natural-language handoff only offers to enter the same /cook flow, so clarify the concrete repo changes in the main chat and rerun /cook."',
+        "temporary" + " compatibility" + " shim, pass /cook",
+        "optional inline /cook hint",
+    ],
 }
 
 for path, needles in checks.items():
@@ -58,6 +65,7 @@ for path, needles in forbidden.items():
             raise SystemExit(f"[release-check] found stale compatibility wording in {path}: {needle}")
 PY
 
+bash ./scripts/cook-trigger-routing-test.sh
 npm run smoke-test
 npm run refocus-test
 npm run context-proposal-test