@easonwumac/computer-linker 0.1.4 → 0.1.6

package/CHANGELOG.md

@@ -5,6 +5,27 @@ 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`.
 
+## 0.1.6 - 2026-06-27
+
+### Changed
+
+- The local npm release wrapper now loads `NODE_AUTH_TOKEN` from the Windows
+  User environment when the current shell process has not inherited it, avoiding
+  a false `npm whoami` 401 after saving a token with `setx` or the Windows
+  environment UI.
+- README and release checklist now document that Windows release token
+  hydration behavior.
+
+## 0.1.5 - 2026-06-27
+
+### Changed
+
+- `quickstart --json` now exposes `commands.check` as the productized install
+  check command while preserving `commands.selfTest` as a compatibility alias
+  for older agents.
+- README and release/manual test docs now use `computer-linker check` as the
+  primary isolated install check command.
+
 ## 0.1.4 - 2026-06-27
 
 ### Added

package/README.md

@@ -70,10 +70,14 @@ directories. Keep real secrets outside exposed folders.
 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,
-automation, and smoke checks. The default help output is intentionally short;
+
+`quickstart --json` exposes `commands.check` for the optional isolated install
+check. `commands.selfTest` remains as a compatibility alias for older agents
+that already consumed the previous JSON field.
+
+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,
+automation, and smoke checks. The default help output is intentionally short;
 use `computer-linker help advanced` for service, config, API, and compatibility
 commands. ChatGPT-specific setup exports are compatibility helpers under
 `computer-linker help chatgpt`; prefer the generic MCP client commands first.
@@ -487,9 +491,12 @@ 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:
+On Windows, if `NODE_AUTH_TOKEN` is saved in the User environment but the
+current shell has not picked it up yet, the release wrapper loads it only into
+the current release process before running `npm whoami` or `npm publish`.
+
+For a public alpha from this private dogfooding checkout, use the fresh public
+snapshot path:
 
 ```bash
 npm run public:release-ready

package/dist/cli.js

@@ -3495,6 +3495,7 @@ function buildQuickstartReport(options) {
     if (options.tunnelProvider) {
         nextActions.push("Use tunnel status and connection history to confirm traffic reaches /mcp only.");
     }
+    const checkCommand = formatCliCommand([...commandParts, "check"]);
     return {
         kind: "computer-linker-quickstart",
         schemaVersion: 1,
@@ -3513,7 +3514,8 @@ function buildQuickstartReport(options) {
             openaiTunnelId: options.tunnelProvider === "openai" ? options.openaiTunnelId ?? "tunnel_..." : null,
         },
         commands: {
-            selfTest: formatCliCommand([...commandParts, "check"]),
+            check: checkCommand,
+            selfTest: checkCommand,
             start: formatCliCommand(startParts),
             status: formatCliCommand([...commandParts, "status"]),
             token: formatCliCommand([...commandParts, "client", "setup", "--show-token"]),
@@ -3574,7 +3576,7 @@ function printQuickstartReport(report) {
         console.log(`   ${report.commands.tunnelStatus}`);
     if (report.commands.historyConnections)
         console.log(`   ${report.commands.historyConnections}`);
-    console.log(`   optional isolated install check: ${report.commands.selfTest}`);
+    console.log(`   optional isolated install check: ${report.commands.check}`);
 }
 function quickstartCommandParts() {
     return invocationCommandParts();

package/docs/architecture.md

@@ -20,10 +20,10 @@ manually before a wider release. The local and CI release gate is
 the progress-reporting test runner, build, and package smoke.
 The package smoke uses `npm pack --dry-run` to verify packed files, CLI bins,
 SDK exports, release docs, security policy, and the published
-`computer_operation` schema, then creates a real `.tgz`, installs it into a
-temporary consumer project, runs the installed `computer-linker` bin, verifies
-installed `self-test`, `setup`, and `status` against isolated config
-directories, and imports the installed SDK entrypoint. The package build uses
+`computer_operation` schema, then creates a real `.tgz`, installs it into a
+temporary consumer project, runs the installed `computer-linker` bin, verifies
+installed `check`, `setup`, and `status` against isolated config
+directories, and imports the installed SDK entrypoint. The package build uses
 `tsconfig.build.json` so tests are typechecked but are not emitted into the
 runtime package.
 
@@ -414,9 +414,10 @@ surface for the same config file used by the MCP server:
   mode, local MCP URL, auth summary, workspace/tunnel summary, user-facing
   readiness, and the next few actions. `status --details` prints the full
   workspace rows, warnings, running tunnel rows, and all next actions.
-- `computer-linker self-test` creates an isolated temporary config/workspace,
-  starts the loopback HTTP MCP server, runs the generic MCP SDK smoke flow, and
-  exits non-zero when the installed CLI/server/tool flow is not working.
+- `computer-linker check` creates an isolated temporary config/workspace,
+  starts the loopback HTTP MCP server, runs the generic MCP SDK smoke flow, and
+  exits non-zero when the installed CLI/server/tool flow is not working.
+  `computer-linker self-test` remains available as a compatibility command.
 - `computer-linker doctor` shows full runtime diagnostics, startup readiness,
   local MCP/API URLs, security findings, tool availability, release readiness,
   and next actions.

package/docs/manual-test-plan.md

@@ -11,26 +11,26 @@ installed package instead, replace `npm run dev --` with `computer-linker`.
 
 ```bash
 npm ci
-npm run product:check
-npm run alpha:check
-npm run public:mirror -- --dry-run --remote <github-owner>/<public-repo>
-npm run dev -- self-test
+npm run product:check
+npm run alpha:check
+npm run public:mirror -- --dry-run --remote <github-owner>/<public-repo>
+npm run dev -- check
 ```
 
 Expected:
 
-- typecheck, tests, build, release validation, and package smoke pass
-- package smoke reports `computer-linker-<version>.tgz` and verifies a
-  temporary consumer install, installed CLI execution, installed self-test,
-  isolated setup/status, and SDK import
+- typecheck, tests, build, release validation, and package smoke pass
+- package smoke reports `computer-linker-<version>.tgz` and verifies a
+  temporary consumer install, installed CLI execution, installed check,
+  isolated setup/status, and SDK import
 - alpha readiness reports `status: ready`, or `status: needs_attention` only
   because preserved Git history must be published through `public:mirror`
 - `public:mirror -- --dry-run --remote ...` reports the mirror dry-run is
   publishable when the fresh public mirror path is accepted and the other gates
   pass; before a real mirror release, resolve any `release tag check: blocked
   for real run` changelog warning
-- `self-test` reports `ready: yes` and verifies the local MCP SDK tool flow
-  without touching real user workspaces
+- `check` reports `ready: yes` and verifies the local MCP SDK tool flow
+  without touching real user workspaces
 - external MCP client/tunnel evidence is still pending until the later tunnel
   smoke step writes `.computer-linker-alpha-evidence.json`
 
@@ -129,10 +129,10 @@ npm run dev -- start . --id app
 Terminal B:
 
 ```bash
-npm run dev -- doctor
-npm run dev -- status
-npm run dev -- self-test
-npm run dev -- profile
+npm run dev -- doctor
+npm run dev -- status
+npm run dev -- check
+npm run dev -- profile
 npm run dev -- client setup
 npm run dev -- client setup --details
 npm run dev -- client setup --show-token

package/docs/product-spec.md

@@ -779,7 +779,7 @@ Auth rules:
 
 Smoke tests:
 
-- installed CLI self-test using a temporary config and workspace.
+- installed CLI check using a temporary config and workspace.
 - local MCP initialize, tools/list, `get_computer_info`, and read-only
   `computer_operation` through the MCP SDK.
 - HTTP `/healthz`.

package/docs/release-checklist.md

@@ -17,10 +17,10 @@ This performs:
 - Release metadata validation.
 - TypeScript typecheck.
 - Full test suite.
-- Runtime build.
-- Package smoke check with `npm pack --dry-run`, real `.tgz` creation,
-  temporary consumer install, installed CLI execution, isolated installed
-  `self-test`, `setup` / `status` config smoke, and installed SDK import.
+- Runtime build.
+- Package smoke check with `npm pack --dry-run`, real `.tgz` creation,
+  temporary consumer install, installed CLI execution, isolated installed
+  `check`, `setup` / `status` config smoke, and installed SDK import.
 
 Before publishing a public npm/package artifact, run:
 
@@ -56,8 +56,10 @@ release tag automatically before publishing, `--otp <code>` for npm 2FA, and
 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:
+On Windows, a `NODE_AUTH_TOKEN` saved in the User environment is loaded into
+the release process automatically when the current shell has not inherited it.
+
+For the one-command local alpha readiness gate, run:
 
 ```bash
 npm run alpha:check
@@ -237,10 +239,11 @@ For each shell or Codex-enabled scope, verify:
 
 ## Smoke Commands
 
-```bash
-computer-linker init
-computer-linker self-test
-computer-linker status
+```bash
+computer-linker init
+computer-linker check
+computer-linker self-test
+computer-linker status
 computer-linker status --details
 computer-linker status --json
 computer-linker doctor

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@easonwumac/computer-linker",
-  "version": "0.1.4",
+  "version": "0.1.6",
   "description": "One computer, one permissioned MCP linker for local workspaces.",
   "type": "module",
   "main": "dist/client.js",