@stalfh233/omc-cli 0.6.4 → 0.6.5

package/dist/cli-contract.js

@@ -272,15 +272,31 @@ export function classifyResult(result) {
         const suffix = candidates.length > 0 ? `；did you mean: ${candidates.join("、")}` : "；用 `omc commands --json --compact --lane <lane>` 或 `omc next` 定位工具";
         return { status: "error", error: withNext({ code: "invalid-input", message: `unknown tool ${String(result.tool ?? "")}${suffix}`, retryable: false }), exitCode: CLI_EXIT_CODES.invalidInput };
     }
-    if (result.blocker === "tool-input-invalid" || result.blocker === "tool-input-unknown-keys")
+    // r25 探针实证（2026-11-04）：`blocker: "invalid-input"` 有 8 处产出点
+    // （workflow/runtime-data/compound-writes），但这里只认 `tool-input-*`——于是
+    // 它们全落到函数末尾的 internal 分支：`error.code=internal` + exit 15，被调用方
+    // 读成"CLI 内部故障"，而实际是**自己传错了参数**（探针原话：
+    // 「rejected ✓, but error.code=internal (should be invalid-input), and no nextCommand」）。
+    // 入参形状错误一律 exit 10，并给出下一步。
+    const inputShapeBlocker = result.blocker === "tool-input-invalid"
+        || result.blocker === "tool-input-unknown-keys"
+        || result.blocker === "invalid-input";
+    if (inputShapeBlocker) {
+        // `invalid-input` 也可能是 CLI 层参数校验（compound-writes 的 --schema 必填），
+        // 那时没有 tool 字段——别硬拼一条指向不存在的工具的 describe。
+        const toolName = typeof result.tool === "string" && result.tool ? result.tool : undefined;
+        const nextCommand = typeof result.nextCommand === "string"
+            ? result.nextCommand
+            : toolName !== undefined ? `omc describe ${toolName}` : undefined;
         return {
             status: "error",
             error: {
                 ...withNext({ code: "invalid-input", message: String(result.message ?? "tool input is invalid"), retryable: false }),
-                nextCommand: typeof result.nextCommand === "string" ? result.nextCommand : `omc describe ${String(result.tool ?? "<tool>")}`,
+                ...(nextCommand !== undefined ? { nextCommand } : {}),
             },
             exitCode: CLI_EXIT_CODES.invalidInput,
         };
+    }
     if (status === "uncertain")
         return { status, error: withNext({ code: "uncertain", message: String(result.message ?? result.reason ?? "outcome is uncertain"), retryable: true }), exitCode: CLI_EXIT_CODES.uncertain };
     if (status === "refused") {

package/dist/support.js

@@ -126,8 +126,8 @@ export function applicationScopeHint(scope, noun) {
 export function applicationScopeNotice(scope) {
     const count = scope.applicationCount ?? 1;
     const where = scope.source === "first-tenant-application" && count > 1
-        ? `租户首个应用 ${scope.code}（租户共 ${count} 个应用）`
-        : `应用 ${scope.code}`;
+        ? `租户首个应用「${scope.code}」（租户共 ${count} 个应用）`
+        : `应用「${scope.code}」`;
     return `本次只在${where}内扫描（source=${scope.source}）——结果被应用边界裁剪，不代表租户全集；跨应用先 app.list 取 applicationCode 再传 applicationCode。`;
 }
 export function flattenTreeRows(rows) {

package/dist/tool-types.js

@@ -50,6 +50,23 @@ const KEY_SYNONYMS = Object.freeze({
     code: ["schemaCode", "sheetCode", "workflowCode"],
     ruleCode: ["code"],
 });
+/**
+ * r25 沙盒实证（2026-11-04）：探针给 `configure_form` 传了 `publish:true`，
+ * 得到「未知键 publish。最接近的合法键：publish→（无相近键）」——写面 fail-closed
+ * 是对的，但**意图没被接住**：配置与发布本来就是两步，用户真正要的是
+ * `form.publish`。同类还有「配完字段就发布」（`field.publish`）与
+ * 「配完列表视图」（无需发布）。这里按工具给出可执行的两步指引，
+ * 比「无相近键」有用得多；代价是探针少花一轮（21→22 实测）。
+ */
+const TWO_STEP_GUIDANCE = Object.freeze({
+    configure_form: Object.freeze({
+        publish: "表单的配置与发布是两步：本工具只写草稿，发布用 `omc call form.publish --args '{\"schemaCode\":\"<模型>\",\"sheetCode\":\"<槽位>\"}'`（也可在本工具的成功回执后紧接着跑）。",
+        publishNow: "同上：本工具不负责发布，用 `omc call form.publish`。",
+    }),
+    configure_model: Object.freeze({
+        publish: "模型/字段的配置与发布是两步：字段建好后用 `omc call field.publish --args '{\"schemaCode\":\"<模型>\"}'` 发布；模型本身不需要单独发布。",
+    }),
+});
 /**
  * Per-tool input aliases: a synonym the caller may send INSTEAD of the canonical
  * key. Applied in `parseToolInput` BEFORE validation (fill canonical from an
@@ -152,11 +169,17 @@ export function parseToolInput(tool, input) {
         const unknown = Object.keys(normalized).filter((key) => !schemaKeys.has(key));
         if (unknown.length > 0) {
             const suggestions = unknown.map((key) => `${key}→${closestSchemaKey(key, schemaKeys) ?? "（无相近键，omc describe <tool> 看参数表）"}`);
+            // r25 实证：`publish→（无相近键）` 等于没说——配置与发布是两步，用户要的是
+            // 另一个工具。有语义指引时优先给可执行的下一步。
+            const twoStep = unknown
+                .map((key) => TWO_STEP_GUIDANCE[tool.name]?.[key])
+                .filter((hint) => typeof hint === "string" && hint.length > 0);
             throw new ToolInputError({
                 status: "error",
                 blocker: "tool-input-unknown-keys",
                 tool: tool.name,
-                message: `写面工具不接受未知键（会被静默丢弃）：${unknown.join("、")}。最接近的合法键：${suggestions.join("；")}。参数表：omc describe ${tool.name}`,
+                message: `写面工具不接受未知键（会被静默丢弃）：${unknown.join("、")}。${twoStep.length > 0 ? twoStep.join(" ") : `最接近的合法键：${suggestions.join("；")}。参数表：omc describe ${tool.name}`}`,
+                ...(twoStep.length > 0 ? { nextCommand: `omc describe ${tool.name}` } : {}),
                 issues: unknown.map((key) => ({ path: [key], code: "unrecognized_key", message: `unknown key; closest: ${closestSchemaKey(key, schemaKeys) ?? "none"}` })),
             });
         }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@stalfh233/omc-cli",
-  "version": "0.6.4",
+  "version": "0.6.5",
   "description": "CloudPivot 8.6 configuration capability CLI — governed, fail-closed, coverage-manifest bounded.",
   "type": "module",
   "bin": {
@@ -52,9 +52,9 @@
     "access": "public"
   },
   "dependencies": {
-    "@stalfh233/omc-fake-platform": "0.6.4",
+    "@stalfh233/omc-fake-platform": "0.6.5",
     "commander": "14.0.3",
-    "omc-core": "0.6.4",
+    "omc-core": "0.6.5",
     "proper-lockfile": "4.1.2",
     "write-file-atomic": "6.0.0",
     "zod": "^3.23.8",