@xenosystem/agent-cli 0.5.17 → 0.5.18

package/README.md

@@ -2,75 +2,6 @@
 
 Production terminal AI agent CLI from XENO Corporation.
 
-> **EXPERIMENTAL BUILD — not code-signed.** This release is published unsigned
-> pending code-signing certificates. Windows SmartScreen will warn on the
-> standalone installers, and the native interactive terminal is **opt-in** (see
-> below). Everything else — agent runs, tools, pipe-mode command execution — is
-> unaffected.
-
-## Platform support — interactive terminal
-
-The CLI itself runs anywhere Node.js >= 20 runs. The **interactive terminal**
-(the native `xeno_pty` module that gives shell commands a real TTY) is a
-per-platform native artifact, and its coverage is *not* uniform:
-
-| Platform       | Native terminal | How this build was produced                                   |
-| -------------- | --------------- | ------------------------------------------------------------- |
-| `linux-x64`    | Yes             | Built for this release (Debian 12, g++ 12.2; glibc floor 2.34) |
-| `linux-arm64`  | Yes             | Built for this release (Debian 12, g++ 12.2; glibc floor 2.34) |
-| `win32-x64`    | Yes<sup>1</sup> | Built for this release (MSVC 19.44, ConPTY)                    |
-| `darwin-arm64` | Yes<sup>2</sup> | Carried forward from 0.4.45 (Apple clang 17) — see note 2      |
-| `darwin-x64`   | Yes<sup>2</sup> | Carried forward from 0.4.45 (Apple clang 17) — see note 2      |
-| `win32-arm64`  | **No**          | **Not shipped in this release** — see note 3                   |
-
-<sup>1</sup> On `win32-x64` the terminal supports TTY startup, Unicode I/O,
-resize, and process-tree termination. **Ctrl+C delivered through the terminal
-input channel does not raise SIGINT in the child process** — a known ConPTY
-defect, tracked and reproducible. Use `/processes` to stop a task.
-
-<sup>2</sup> The macOS artifacts are **not rebuilt for 0.5.17**. They are the
-artifacts published in 0.4.45, carried forward because the native source
-(`xeno_pty_posix.cpp`) is byte-identical: the manifests record
-`sourceSha256 = 6ba69e62…`, which is exactly this release's source. They were
-compiled by the last macOS CI run (Apple clang 17) and are verified here as
-correct 64-bit Mach-O bundles for their CPU type, with their recorded hashes
-intact. They could **not** be re-executed during release preparation because
-building or running macOS binaries requires Apple hardware, which this release
-did not have. Treat macOS as source-verified, not run-verified, for 0.5.17.
-
-<sup>3</sup> `win32-arm64` ships **no** native terminal in this release. The
-Windows-on-ARM cross-compiler (`MSVC v143 ARM64 build tools`) was not available
-on the release machine, and the previously published `win32-arm64` artifact was
-built from a *different* source revision, so it was not carried forward. On
-`win32-arm64` the CLI runs normally, and shell commands run in **pipe mode**.
-
-### What "no interactive terminal" actually means
-
-Commands still run. They run through pipes instead of a TTY: no interactive
-prompts (`sudo`, `ssh`, `vim`, REPLs), no terminal size reporting, no Ctrl+C
-signal delivery. The CLI **says so explicitly** — it prints a notice on first
-use, `xeno --version` reports the status on its second line, and `xeno doctor`
-gives the cause and the fix. It never degrades silently.
-
-### The unsigned-artifact gate
-
-Native artifacts in this release are `unsigned-development`, and the package
-ships an empty trust store. On a normal install the loader therefore refuses to
-load them, and the interactive terminal is **off by default on every platform,
-including the ones with a build above.** This is deliberate: an unsigned native
-module is a supply-chain risk the CLI will not take on your behalf.
-
-To opt in on a platform that has a build:
-
-```bash
-XENO_ALLOW_UNSIGNED_NATIVE=1 xeno chat
-```
-
-Related switches: `XENO_DISABLE_PTY=1` turns the terminal off outright,
-`XENO_REQUIRE_SIGNED_NATIVE=1` refuses unsigned artifacts even in a source
-checkout, and `XENO_QUIET_PTY_WARNING=1` silences the unavailability notice.
-Once code signing is in place, signed manifests will load without any opt-in.
-
 ## Runtime Ownership
 
 The current ownership level is release-audited and may be lower than the terminal P2 program target. Node is an external host through P2, self-contained release assets embed Node.js or Bun, and the TypeScript/npm development toolchain remains third-party infrastructure. Runtime and toolchain replacement are not roadmap items. The package must not be described as fully proprietary, entirely Xeno-owned, free of third-party runtime code, or built by an owned toolchain. The packaged policy and engineering clean-room controls are in `ownership/`.