@easonwumac/computer-linker 0.1.2 → 0.1.4

package/CHANGELOG.md

@@ -3,11 +3,34 @@
 All notable changes to Computer Linker will be documented in this file.
 
 This project follows a small pre-1.0 changelog: breaking contract changes are
-called out even when the package version is still `0.x`.
-
+called out even when the package version is still `0.x`.
+
+## 0.1.4 - 2026-06-27
+
+### Added
+
+- Added `computer-linker check` as the productized install check command. It
+  runs the existing isolated self-test flow while keeping `self-test` as a
+  compatibility/advanced command.
+
+## 0.1.3 - 2026-06-27
+
+### Added
+
+- Added `release:verify` to confirm a published npm version's exact metadata,
+  dist-tag, and published CLI from a clean temporary directory.
+
+### Changed
+
+- `release:publish` now runs the post-publish npm registry verification
+  automatically after npm accepts the package.
+- `release:publish -- --push` now pushes `HEAD` and the exact release tag
+  explicitly, so lightweight release tags are not skipped by `git push
+  --follow-tags`.
+
 ## 0.1.2 - 2026-06-27
-
-### Added
+
+### Added
 
 - Local npm release wrapper commands: `release:check`, `release:dry-run`, and
   `release:publish`.

package/README.md

@@ -16,10 +16,11 @@ computer; Cloudflare, Tailscale, or OpenAI tunnel exposure is optional.
 
 Install the CLI, expose one folder, and keep the server running:
 
-```powershell
-npm install -g @easonwumac/computer-linker
-computer-linker start C:\Projects\my-app
-```
+```powershell
+npm install -g @easonwumac/computer-linker
+computer-linker check
+computer-linker start C:\Projects\my-app
+```
 
 Leave that terminal running. In another terminal, copy the MCP client settings
 and verify the connection:
@@ -65,10 +66,10 @@ File content reads and text searches block common sensitive files by default,
 including `.env*`, private keys, credential JSON files, and cloud CLI credential
 directories. Keep real secrets outside exposed folders.
 
-`self-test` is safe to run before exposing real folders. It creates a temporary
-config and workspace, starts a loopback HTTP MCP server, verifies `/healthz`,
-the local JSON API, MCP initialize, tools/list, `get_computer_info`, and one
-read-only `computer_operation`, then removes the temporary files.
+`check` is safe to run before exposing real folders. It creates a temporary
+config and workspace, starts a loopback HTTP MCP server, verifies `/healthz`,
+the local JSON API, MCP initialize, tools/list, `get_computer_info`, and one
+read-only `computer_operation`, then removes the temporary files.
 
 There is no web dashboard in the product path. Human setup and management are
 CLI-first; MCP and the JSON API are only protocol surfaces for clients,
@@ -471,19 +472,21 @@ For npm publishing, use the local release wrapper instead of hand-running every
 step:
 
 ```bash
-npm run release:check
-npm run release:dry-run
-npm run release:publish -- --create-tag --otp <code>
-git push origin main --follow-tags
-```
+npm run release:check
+npm run release:dry-run
+npm run release:publish -- --create-tag --push --otp <code>
+```
 
 `release:check` runs the local product/public package gates without publishing.
 `release:dry-run` runs `npm publish --dry-run` and creates a temporary local
 `v<package.version>` tag only for that dry-run when the tag is missing.
-`release:publish` requires a clean main/master worktree, a dated changelog
-heading, npm login, and a release tag. Pass `--create-tag` to create the tag
-on `HEAD`; pass `--push` only when you want the script to push `HEAD` and tags
-after a successful npm publish.
+`release:publish` requires a clean main/master worktree, a dated changelog
+heading, npm login, and a release tag. Pass `--create-tag` to create the tag
+on `HEAD`; pass `--push` only when you want the script to push `HEAD` and the
+release tag after a successful npm publish. After npm accepts the publish, the
+wrapper waits for registry metadata, verifies the npm dist-tag, and runs the
+published CLI from a clean temporary directory. Use `npm run release:verify` to
+repeat that post-publish check for the current `package.json` version.
 
 For a public alpha from this private dogfooding checkout, use the fresh public
 snapshot path:

package/dist/cli.js

@@ -84,6 +84,9 @@ async function main(argv) {
         case "status":
             status(args);
             return;
+        case "check":
+            await selfTest(args, "check");
+            return;
         case "self-test":
             await selfTest(args);
             return;
@@ -143,7 +146,7 @@ function normalizeCommand(command) {
         throw new Error("connect-profile was removed; use `computer-linker client chatgpt profile` only when ChatGPT asks for connector-specific fields.");
     if (command === "chatgpt")
         throw new Error("chatgpt was removed; use `computer-linker client chatgpt <subcommand>` only when ChatGPT asks for connector-specific fields.");
-    if (command === "init" || command === "start" || command === "quickstart" || command === "status" || command === "self-test" || command === "expose" || command === "tunnel" || command === "service" || command === "workspace" || command === "process" || command === "screen" || command === "doctor" || command === "diagnose" || command === "history" || command === "profile" || command === "client" || command === "config" || command === "setup")
+    if (command === "init" || command === "start" || command === "quickstart" || command === "status" || command === "check" || command === "self-test" || command === "expose" || command === "tunnel" || command === "service" || command === "workspace" || command === "process" || command === "screen" || command === "doctor" || command === "diagnose" || command === "history" || command === "profile" || command === "client" || command === "config" || command === "setup")
         return command;
     if (command === "version" || command === "--version" || command === "-v")
         return "version";
@@ -166,9 +169,12 @@ function status(args) {
     }
     process.stdout.write(args.includes("--details") ? formatDetailedCliStatus(report) : formatCliStatus(report));
 }
-async function selfTest(args) {
+async function selfTest(args, commandLabel = "self-test") {
     if (hasHelpFlag(args)) {
-        printSelfTestHelp();
+        if (commandLabel === "check")
+            printCheckHelp();
+        else
+            printSelfTestHelp();
         return;
     }
     const unknown = args.filter((arg, index) => (arg !== "--json" &&
@@ -176,8 +182,8 @@ async function selfTest(args) {
         arg !== "--timeout-ms" &&
         args[index - 1] !== "--timeout-ms"));
     if (unknown.length > 0)
-        throw new Error(`Unknown self-test option: ${unknown[0]}`);
-    const timeoutMs = readOptionalIntegerOption(args, "--timeout-ms", "self-test --timeout-ms") ?? 15000;
+        throw new Error(`Unknown ${commandLabel} option: ${unknown[0]}`);
+    const timeoutMs = readOptionalIntegerOption(args, "--timeout-ms", `${commandLabel} --timeout-ms`) ?? 15000;
     const keepTemp = args.includes("--keep-temp");
     const tempRoot = mkdtempSync(join(tmpdir(), "computer-linker-self-test-"));
     const configDir = join(tempRoot, "config");
@@ -3484,7 +3490,7 @@ function buildQuickstartReport(options) {
         "Use the startup check printed by start as the first readiness signal.",
         "Run client setup --show-token only on a trusted local screen when configuring client auth.",
         "Use client setup --details when the MCP client or agent needs full setup instructions.",
-        "Use self-test only when you want an isolated install check.",
+        "Use check only when you want an isolated install check.",
     ];
     if (options.tunnelProvider) {
         nextActions.push("Use tunnel status and connection history to confirm traffic reaches /mcp only.");
@@ -3507,7 +3513,7 @@ function buildQuickstartReport(options) {
             openaiTunnelId: options.tunnelProvider === "openai" ? options.openaiTunnelId ?? "tunnel_..." : null,
         },
         commands: {
-            selfTest: formatCliCommand([...commandParts, "self-test"]),
+            selfTest: formatCliCommand([...commandParts, "check"]),
             start: formatCliCommand(startParts),
             status: formatCliCommand([...commandParts, "status"]),
             token: formatCliCommand([...commandParts, "client", "setup", "--show-token"]),
@@ -3667,6 +3673,10 @@ function printHelp(args = []) {
         printStatusHelp();
         return;
     }
+    if (topic === "check" && rest.length === 0) {
+        printCheckHelp();
+        return;
+    }
     if ((topic === "self-test" || topic === "selftest") && rest.length === 0) {
         printSelfTestHelp();
         return;
@@ -3753,14 +3763,16 @@ function printCoreHelp() {
         "Usage:",
         "  computer-linker start <workspace-path>",
         "  computer-linker start <workspace-path> --tunnel openai|tailscale|cloudflare",
+        "  computer-linker check",
         "  computer-linker client setup",
         "  computer-linker status",
         "  computer-linker help advanced",
         "",
         "First run:",
-        "  1. Start local: computer-linker start C:\\Projects\\my-app",
-        "  2. Connect client: computer-linker client setup",
-        "  3. Check state: computer-linker status",
+        "  1. Optional install check: computer-linker check",
+        "  2. Start local: computer-linker start C:\\Projects\\my-app",
+        "  3. Connect client: computer-linker client setup",
+        "  4. Check state: computer-linker status",
         "",
         "Cloud client:",
         "  computer-linker start C:\\Projects\\my-app --tunnel openai --tunnel-id tunnel_...",
@@ -3777,7 +3789,7 @@ function printCoreHelp() {
         "  By default, start allows file edits and approved project commands for normal development work.",
         "  Use --read-only to inspect only; use --full-trust only when Codex and screen capture are intended.",
         "  Tokens stay hidden by default; use client setup --show-token only on a trusted local setup screen.",
-        "  Details: computer-linker help start | computer-linker help client setup | computer-linker help advanced",
+        "  Details: computer-linker help check | computer-linker help start | computer-linker help client setup | computer-linker help advanced",
     ]);
 }
 function printStartHelp() {
@@ -4063,6 +4075,22 @@ function printSelfTestHelp() {
         "  computer-linker self-test",
     ].join("\n"));
 }
+function printCheckHelp() {
+    console.log([
+        "Computer Linker check",
+        "",
+        "Usage:",
+        "  computer-linker check [--json] [--keep-temp] [--timeout-ms ms]",
+        "",
+        "What it does:",
+        "  Runs an isolated install check without touching your real config or folders.",
+        "  Creates a temporary config and workspace, starts a loopback MCP server,",
+        "  verifies health, MCP initialize, tools/list, get_computer_info, and one read-only computer_operation.",
+        "",
+        "Example:",
+        "  computer-linker check",
+    ].join("\n"));
+}
 function printDoctorHelp() {
     console.log([
         "Computer Linker doctor",
@@ -4462,6 +4490,7 @@ function printAdvancedHelp() {
         "  computer-linker start --tunnel tailscale",
         "  computer-linker start --tunnel openai --tunnel-id tunnel_...",
         "  computer-linker status [--details] [--json]",
+        "  computer-linker check [--json] [--keep-temp] [--timeout-ms ms]",
         "  computer-linker self-test [--json] [--keep-temp] [--timeout-ms ms]",
         "  computer-linker process list <workspace-id> [--json]",
         "  computer-linker process read <workspace-id> <process-id> [--json]",

package/docs/release-checklist.md

@@ -33,11 +33,10 @@ npm run public:check
 Use the local wrapper when you are ready to publish from the current repository:
 
 ```bash
-npm run release:check
-npm run release:dry-run
-npm run release:publish -- --create-tag --otp <code>
-git push origin main --follow-tags
-```
+npm run release:check
+npm run release:dry-run
+npm run release:publish -- --create-tag --push --otp <code>
+```
 
 `release:check` runs the local product and public package gates without
 publishing. It does not require a clean worktree, so it is useful before the
@@ -48,12 +47,15 @@ It runs `npm publish --dry-run`; if `v<package.version>` is missing, it creates
 a temporary local tag for the dry-run and removes it afterward. If that tag
 already exists on another commit, bump the package version before releasing.
 
-`release:publish` performs the real npm publish. It requires a clean
-main/master worktree, a dated `CHANGELOG.md` heading for the package version,
-npm login, and a release tag on `HEAD`. Pass `--create-tag` to create the
-release tag automatically before publishing, `--otp <code>` for npm 2FA, and
-`--push` only when the script should push `HEAD` and tags to `origin` after a
-successful publish.
+`release:publish` performs the real npm publish. It requires a clean
+main/master worktree, a dated `CHANGELOG.md` heading for the package version,
+npm login, and a release tag on `HEAD`. Pass `--create-tag` to create the
+release tag automatically before publishing, `--otp <code>` for npm 2FA, and
+`--push` only when the script should push `HEAD` and the release tag to
+`origin` after a successful publish. After npm accepts the publish, it also waits for exact
+version metadata, verifies the configured npm dist-tag, and runs the published
+CLI from a clean temporary directory. `release:verify` repeats only that
+post-publish registry check for the current `package.json` version.
 
 For the one-command local alpha readiness gate, run:
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@easonwumac/computer-linker",
-  "version": "0.1.2",
+  "version": "0.1.4",
   "description": "One computer, one permissioned MCP linker for local workspaces.",
   "type": "module",
   "main": "dist/client.js",
@@ -64,6 +64,7 @@
     "release:check": "node scripts/release-npm.mjs --check",
     "release:dry-run": "node scripts/release-npm.mjs --dry-run",
     "release:publish": "node scripts/release-npm.mjs --publish",
+    "release:verify": "node scripts/verify-npm-release.mjs",
     "release:validate": "node scripts/release-validate.mjs",
     "start": "node dist/cli.js start",
     "test": "node scripts/run-tests.mjs",