@stalfh233/omc-cli 0.4.0 → 0.4.11

package/README.md

@@ -244,42 +244,31 @@ src/        args/support/plan/read/write/package/context（治理管道）
 | `omc-acceptance-criteria` | 验收门：读回、交付态、零残留、反例基线 |
 | `omc-glossary` | 术语：环境指纹、覆盖清单、交付态、Void envelope、结果状态 |
 
-## GitLab npm Package Registry 分发
+## npm 分发
 
-本包通过项目级 GitLab npm Registry 分发。`omc-core` 是 `omc-cli` 的内部依赖，发布流水线会先发布 `omc-core`，再发布 `omc-cli`；两者版本保持一致。当前版本为 `0.3.0`，尚未宣称 `1.0.0` 稳定契约。
+本包（`@stalfh233/omc-cli`，可执行命令仍是 `omc`）通过公共 npm registry 分发。`omc-core` 是 `omc-cli` 的内部依赖，发布时先发 `omc-core`，再发 `omc-cli`；两者版本保持一致。当前版本为 `0.4.11`，尚未宣称 `1.0.0` 稳定契约。
 
 ### 使用已发布包
 
-先从 GitLab 项目概览页取得 `<PROJECT_ID>`，再在使用方项目目录创建本地 `.npmrc`。不要把 token 写入仓库：
-
-```ini
-registry=https://gitlab.h3yun.com/api/v4/projects/<PROJECT_ID>/packages/npm/
-//gitlab.h3yun.com/api/v4/projects/<PROJECT_ID>/packages/npm/:_authToken=${NPM_TOKEN}
-```
-
-`NPM_TOKEN` 使用具有 `read_package_registry` 的 Deploy Token，或 GitLab 推荐的其他 npm Registry token。然后安装：
-
 ```bash
-npm install omc-cli@0.3.0
-npx omc setup
-npx omc doctor
-npx omc help omc-write-hazards
-npx omc help omc-business-configuration
+npm install -g @stalfh233/omc-cli@0.4.11
+omc setup
+omc doctor
+omc help omc-write-hazards
+omc help omc-business-configuration
 ```
 
-如果组织使用 group/instance Registry，可把 `.npmrc` 的 project endpoint 换成对应 group/instance endpoint；token 必须有目标包及其 `omc-core` 依赖的读取权限。
-
 ### 发布新版本
 
-发布由 GitLab CI 的 tag pipeline 完成，不在开发机直接 `npm publish`：
+发布在开发机执行，必须先 `omc-core` 后 `omc-cli`，顺序不能反：
 
 ```bash
 npm run verify
-git tag v0.3.0
-git push origin v0.3.0
+npm publish --workspace packages/omc-core
+npm publish --workspace packages/omc-cli
 ```
 
-`vX.Y.Z` tag 触发 `publish-npm` job。job 使用 `CI_JOB_TOKEN` 写入项目 Package Registry，校验 `omc-core`/`omc-cli` 版本与 tag 一致，构建后按顺序发布两个包。不要手工提交 `.npmrc` 或 token。
+`omc-core` 与 `omc-cli` 版本保持一致；发布前先用 `git tag vX.Y.Z` 记录该版本。新包首次发布进入 npm staged-publishing 审核队列，需维护者在 npmjs.com 用交互式 2FA 批准后真实版本才可见。
 
 ### 版本策略
 

package/dist/call.js

@@ -106,10 +106,21 @@ export async function runToolCall(toolName, options = {}) {
     };
     const result = options.timeoutMs === undefined
         ? await invoke()
-        : await Promise.race([
-            invoke(),
-            new Promise((resolve) => setTimeout(() => resolve({ status: "uncertain", blocker: "cli-timeout", nextAction: "read back the requestId before retrying; retry only after the outcome is established", retryable: true }), options.timeoutMs)),
-        ]);
+        : await (async () => {
+            let timer;
+            try {
+                return await Promise.race([
+                    invoke(),
+                    new Promise((resolve) => { timer = setTimeout(() => resolve({ status: "uncertain", blocker: "cli-timeout", nextAction: "read back the requestId before retrying; retry only after the outcome is established", retryable: true }), options.timeoutMs); }),
+                ]);
+            }
+            finally {
+                // Clear the losing timeout so a completed call does not leave a
+                // pending timer that would otherwise keep the event loop alive.
+                if (timer)
+                    clearTimeout(timer);
+            }
+        })();
     // The stderr line is a human diagnostic, NOT a second copy of the result: the
     // stdout envelope is the single machine truth. Dumping the whole result here
     // doubled every call's payload on stderr (unbounded and un-sanitized — it also

package/dist/cli.js

@@ -1,6 +1,6 @@
 #!/usr/bin/env node
 import { createInterface } from "node:readline/promises";
-import { stdin, argv, exit } from "node:process";
+import { stdin, argv } from "node:process";
 import { Command, CommanderError } from "commander";
 import { ConfigStore, defaultPaths, removedProfileKeys } from "./config-store.js";
 import { loadCoverageManifest, versionFamilyNotice } from "./coverage.js";
@@ -1373,22 +1373,35 @@ async function main() {
     await command.parseAsync(stripOutputFlags(argv));
     return commandExitCode;
 }
+/**
+ * End the process with `code` without the Windows-only libuv abort a bare
+ * `process.exit()` triggers while undici is still closing its sockets:
+ *   Assertion failed: !(handle->flags & UV_HANDLE_CLOSING), src\win\async.c
+ * We set `exitCode` so the loop drains and the process exits with the right
+ * status; an unref'd guard force-exits only if some ref'd handle (e.g. an
+ * optional `--timeout-ms` race timer) would otherwise keep the loop alive — by
+ * which point the HTTP sockets are closed, so the forced exit is safe.
+ */
+function finish(code) {
+    process.exitCode = code;
+    setTimeout(() => process.exit(code), 1000).unref();
+}
 const request = requestId();
 main().then((code) => {
     if (argv[2] === "call" || argv[2] === "artifact" || argv[2] === "commands" || argv[2] === "describe" || argv[2] === "contract" || argv[2] === "capabilities" || argv[2] === "capability" || argv[2] === "next" || argv[2] === "usage" || argv[2] === "intent" || argv[2] === "help") {
         completeUsage(code);
-        exit(code);
+        finish(code);
         return;
     }
     writeEnvelope(envelope(code === 0 ? "ok" : "error", {}, request, code === 0 ? null : { code: "internal", message: "command failed", retryable: false }));
     completeUsage(code);
-    exit(code);
+    finish(code);
 }, (error) => {
     // commander prints `--help` / `-h` usage to stderr and signals success with
     // this code; it is not an error and must not grow a spurious error envelope.
     if (error instanceof CommanderError && error.code === "commander.helpDisplayed") {
         completeUsage(0);
-        exit(0);
+        finish(0);
         return;
     }
     const commander = error instanceof CommanderError;
@@ -1413,6 +1426,6 @@ main().then((code) => {
     const parsed = errorEnvelope(new Error(message), commander ? "invalid-input" : "internal", commander ? CLI_EXIT_CODES.invalidInput : CLI_EXIT_CODES.internal, request);
     writeEnvelope(parsed.envelope);
     completeUsage(parsed.exitCode);
-    exit(parsed.exitCode);
+    finish(parsed.exitCode);
 });
 //# sourceMappingURL=cli.js.map

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@stalfh233/omc-cli",
-  "version": "0.4.0",
+  "version": "0.4.11",
   "description": "CloudPivot 8.6 configuration capability CLI — governed, fail-closed, coverage-manifest bounded.",
   "type": "module",
   "bin": {
@@ -51,7 +51,7 @@
   },
   "dependencies": {
     "commander": "14.0.3",
-    "omc-core": "0.4.0",
+    "omc-core": "0.4.11",
     "proper-lockfile": "4.1.2",
     "write-file-atomic": "6.0.0",
     "zod": "^3.23.8",