@inplaysoft/cli-staging 0.0.0-stage → 0.0.0-staging.0.g12f761067754

package/README.md

@@ -1,3 +1,63 @@
-# Temporary Holding Version
+> **staging channel.** This is `@inplaysoft/cli-staging`, the staging build of the Inplaysoft CLI. Install it with
+> `npm install -g @inplaysoft/cli-staging` and run it as `inplay-staging` (not `inplay`). The text below describes the
+> prod package: read `@inplaysoft/cli-staging` for `@inplaysoft/cli` in every install line and `inplay-staging` for `inplay` in every command.
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+# @inplaysoft/cli
+
+`inplay` — Inplaysoft Platform command-line interface.
+
+## Install
+
+```bash
+npm install -g @inplaysoft/cli
+```
+
+The install pulls one matching native binary for your OS + arch via npm's
+`optionalDependencies` mechanism. Supported targets:
+
+| OS      | Architectures   |
+| ------- | --------------- |
+| Linux   | x64, arm64      |
+| macOS   | x64, arm64      |
+| Windows | x64, arm64      |
+
+## Quick start
+
+```bash
+inplay login                  # opens your browser to /cli/authorize
+inplay whoami                 # confirm the session
+inplay devices list           # list your CLI devices
+inplay api GET /api/v1/...    # raw passthrough with your token
+```
+
+## Configuration
+
+| Flag / env             | Default                                | Purpose                                    |
+| ---------------------- | -------------------------------------- | ------------------------------------------ |
+| `--gateway`            | (baked-in at build time)               | Override the gateway URL                   |
+| `INPLAY_GATEWAY`       | (baked-in at build time)               | Same, via env                              |
+| `--insecure-storage`   | (off)                                  | Store creds in a 0600 file instead of OS keychain |
+
+Releases on npm currently point at the **staging** gateway
+(`https://gateway.staging.inplaysoft.com`). When the production gateway
+ships, prod binaries publish under a separate dist-tag.
+
+## Known caveats
+
+- **Device revocation lag**: the gateway caches token validity for ~5
+  minutes. Revoking a device in the admin UI takes up to that long to be
+  honored by an actively-used CLI session.
+- **Alpine / musl**: the `linux-x64` / `linux-arm64` packages have no
+  npm-level Alpine constraint and the binaries are built with
+  `CGO_ENABLED=0` (statically linked Go), so the binary itself runs on
+  Alpine. **But** the default OS-keychain credential store relies on
+  the Secret Service API over D-Bus, which Alpine doesn't ship by
+  default — pass `--insecure-storage` to `inplay login` to fall back to
+  a 0600 file in `~/.config/inplay/`.
+- **`--omit=optional`**: `npm install -g @inplaysoft/cli --omit=optional`
+  installs the main package but skips every platform binary. The CLI
+  will then fail with a clear error on first invocation.
+
+## License
+
+UNLICENSED — distributed only for use by Inplaysoft Platform admins.

package/inplay.js

@@ -0,0 +1,76 @@
+#!/usr/bin/env node
+// Thin Node wrapper that locates the matching native <wrapper>-<os>-<arch>
+// package and execs its binary. The release workflow ships one binary per
+// optional-platform package and npm only installs the one that matches the
+// host's process.platform + process.arch — same pattern as esbuild, swc,
+// biome, tailwindcss-oxide.
+//
+// One wrapper serves every release channel (#27756): the platform-package
+// prefix is this package's OWN name, read from the package.json npm ships
+// beside it — `@inplaysoft/cli` (prod) resolves `@inplaysoft/cli-linux-x64`,
+// `@inplaysoft/cli-staging` resolves `@inplaysoft/cli-staging-linux-x64`.
+// There is deliberately NO fallback to the prod prefix: a channel wrapper that
+// cannot name itself must fail, never silently run another channel's binary.
+
+const { spawnSync } = require('node:child_process');
+
+const SUPPORTED = ['darwin-arm64', 'darwin-x64', 'linux-arm64', 'linux-x64', 'win32-arm64', 'win32-x64'];
+
+let wrapper;
+try {
+  wrapper = require('./package.json').name;
+} catch (err) {
+  console.error(
+    `inplay: cannot read the wrapper's own package.json (${err.message}).\n` +
+      `  Reinstall the inplay CLI package you installed (e.g. npm install -g @inplaysoft/cli).`,
+  );
+  process.exit(1);
+}
+if (typeof wrapper !== 'string' || !/^@inplaysoft\/cli(-[a-z]+)?$/.test(wrapper)) {
+  console.error(`inplay: the wrapper's package.json names '${wrapper}', not an @inplaysoft/cli package. Reinstall it.`);
+  process.exit(1);
+}
+
+const key = `${process.platform}-${process.arch}`;
+
+if (!SUPPORTED.includes(key)) {
+  console.error(`${wrapper}: unsupported platform ${key}. Supported: ${SUPPORTED.join(', ')}.`);
+  process.exit(1);
+}
+
+const pkg = `${wrapper}-${key}`;
+const binName = process.platform === 'win32' ? 'inplay.exe' : 'inplay';
+
+let binaryPath;
+try {
+  binaryPath = require.resolve(`${pkg}/bin/${binName}`);
+} catch (err) {
+  // The matching optional-platform package isn't installed. This usually
+  // means npm skipped it because the host advertised a different
+  // platform/arch than the one running the wrapper (e.g. installing in CI
+  // with --omit=optional, or using a tool that filters optional deps).
+  console.error(
+    `${wrapper}: native binary for ${key} is not installed.\n` +
+      `  Try: npm install ${pkg}\n` +
+      `  Or:  reinstall ${wrapper} without --omit=optional.`,
+  );
+  process.exit(1);
+}
+
+const result = spawnSync(binaryPath, process.argv.slice(2), {
+  stdio: 'inherit',
+  windowsHide: true,
+});
+
+if (result.error) {
+  console.error(`${wrapper}: failed to spawn ${binaryPath}: ${result.error.message}`);
+  process.exit(1);
+}
+
+// Preserve signal-termination fidelity for scripted callers: if the child
+// was killed by a signal (Ctrl-C, etc.), re-raise it on ourselves rather
+// than exiting 0 — status is null when signal is set.
+if (result.signal) {
+  process.kill(process.pid, result.signal);
+}
+process.exit(result.status ?? 1);

package/package.json

@@ -1,6 +1,31 @@
 {
   "name": "@inplaysoft/cli-staging",
-  "version": "0.0.0-stage",
-  "stub": true,
-  "description": "Temporary package placeholder for staged publishing"
-}
+  "version": "0.0.0-staging.0.g12f761067754",
+  "description": "Inplaysoft Platform command-line interface (inplay-staging).",
+  "bin": {
+    "inplay-staging": "./inplay.js"
+  },
+  "engines": {
+    "node": ">=18"
+  },
+  "files": [
+    "inplay.js",
+    "README.md"
+  ],
+  "optionalDependencies": {
+    "@inplaysoft/cli-staging-darwin-arm64": "0.0.0-staging.0.g12f761067754",
+    "@inplaysoft/cli-staging-darwin-x64": "0.0.0-staging.0.g12f761067754",
+    "@inplaysoft/cli-staging-linux-arm64": "0.0.0-staging.0.g12f761067754",
+    "@inplaysoft/cli-staging-linux-x64": "0.0.0-staging.0.g12f761067754",
+    "@inplaysoft/cli-staging-win32-arm64": "0.0.0-staging.0.g12f761067754",
+    "@inplaysoft/cli-staging-win32-x64": "0.0.0-staging.0.g12f761067754"
+  },
+  "publishConfig": {
+    "access": "public"
+  },
+  "license": "UNLICENSED",
+  "keywords": [
+    "inplaysoft",
+    "cli"
+  ]
+}