@xenosystem/agent-cli 0.5.17

package/native/xeno-pty/prebuilds/PROVENANCE.md

@@ -0,0 +1,69 @@
+# xeno-pty native artifact provenance — 0.5.17
+
+`*.node` binaries are gitignored, so this directory is populated by a build, not
+by a checkout. This file records where each shipped artifact actually came from.
+Every claim below is checkable from the artifacts themselves.
+
+Native sources for this release:
+
+- `src/xeno_pty_posix.cpp` — `sha256 6ba69e62cf0c0765546afa19f1820c1cc7f64f452802718c20b4a117d6c8f9c6`
+- `src/xeno_pty_win.cpp` — `sha256 9f6f6248f35f2f6b767b153f66670d5ed8f95cb7d6242c77c652efe5cca2d038`
+
+Each `manifest.json` records the `sourceSha256` its binary was compiled from.
+Line endings are pinned to LF via `.gitattributes` so these hashes are
+checkout-independent.
+
+| Target         | `sha256` of `xeno_pty.node`                                        | Origin |
+| -------------- | ------------------------------------------------------------------ | ------ |
+| `win32-x64`    | `91d9a464823091603d784cbc3a570b8a0e514576eeb4b8fb2aabcdcbb64bccad` | Built for 0.5.17, MSVC 19.44.35222, `/Brepro`. Reproduced the hash already recorded in the tracked manifest. Load-verified. |
+| `linux-x64`    | `a93757b552cb9236fe33773228072df270659d6a015a92fb96d21a9d22c5f2cb` | Built for 0.5.17 in a Debian 12 container, g++ 12.2.0. Load-verified plus a real PTY spawn round-trip. |
+| `linux-arm64`  | `07f660ac0c32ac7a2900f3abdfa12550f603880f02a1763a12a63064fe802006` | Built for 0.5.17 in a Debian 12 `linux/arm64` container under QEMU, g++ 12.2.0. Load-verified plus a real PTY spawn round-trip **on aarch64**. |
+| `darwin-arm64` | `b1e689d8563464cd95ac600f42a26182d072d1922f5a57f85ec5717603eff864` | **Carried forward from published 0.4.45.** Not rebuilt. See below. |
+| `darwin-x64`   | `ff459f0ee222bec04513190d2922a9ed76d9bbeb80f5335e6663eed942a4996a` | **Carried forward from published 0.4.45.** Not rebuilt. See below. |
+| `win32-arm64`  | *(absent)*                                                          | **Not shipped.** See below. |
+
+## macOS artifacts are carried forward, not rebuilt
+
+`darwin-arm64` and `darwin-x64` are the exact artifacts published in
+`@xeno-corporation/xeno-agent-cli@0.4.45`, compiled by the last macOS CI run
+with Apple clang 17.0.0.
+
+They are carried forward rather than dropped because they are provably built
+from *this* release's source: both manifests record
+`sourceSha256 = 6ba69e62cf0c…`, byte-identical to `src/xeno_pty_posix.cpp`
+above. Verified during release preparation:
+
+- binary `sha256` matches the value in its own `manifest.json`;
+- `manifest.sourceSha256` matches this release's POSIX source;
+- both are valid 64-bit Mach-O `MH_BUNDLE` images with the correct `cputype`
+  (`arm64` / `x86_64`).
+
+Not verified, and not claimed: these binaries were **not executed** during
+release preparation. Building or running macOS binaries requires Apple hardware,
+which was not available. macOS is source-verified, not run-verified, for 0.5.17.
+
+## `win32-arm64` is not shipped
+
+Two independent reasons:
+
+1. The Windows-on-ARM cross-compiler was not present on the release machine.
+   Visual Studio 2022 Build Tools were installed with `x86`/`x64` targets only;
+   `Microsoft.VisualStudio.Component.VC.Tools.ARM64` was absent, and installing
+   it needs elevation. `scripts/build-windows.ps1 -Architecture arm64` already
+   supports the cross-build once that component exists.
+2. The `win32-arm64` artifact published in 0.4.45 records
+   `sourceSha256 = 58b4f8c09219…`, which does **not** match this release's
+   `xeno_pty_win.cpp` (`9f6f6248f35f…`). It was built from a different source
+   revision, so carrying it forward would ship a binary whose manifest
+   contradicts the shipped source.
+
+Dropping it is the honest option: on `win32-arm64` the CLI reports the
+unavailability explicitly and runs shell commands in pipe mode.
+
+## Signature status
+
+All manifests are `unsigned-development` and `trusted-keys.json` is empty, so on
+a normal install the loader refuses to load any of these artifacts and the
+interactive terminal is off by default on every platform. Opt in with
+`XENO_ALLOW_UNSIGNED_NATIVE=1`. This is unchanged from 0.4.45, which shipped six
+binaries under exactly the same gate.

package/native/xeno-pty/prebuilds/darwin-arm64/manifest.json

@@ -0,0 +1,18 @@
+{
+  "schemaVersion": 2,
+  "component": "xeno-pty",
+  "binary": "xeno_pty.node",
+  "apiVersion": 1,
+  "platform": "darwin",
+  "architecture": "arm64",
+  "abi": "napi-v8",
+  "napi": 8,
+  "minimumNode": "20.0.0",
+  "nodeHeaders": "24.18.0",
+  "compiler": "Apple clang version 17.0.0 (clang-1700.0.13.5)",
+  "sourceSha256": "6ba69e62cf0c0765546afa19f1820c1cc7f64f452802718c20b4a117d6c8f9c6",
+  "sha256": "b1e689d8563464cd95ac600f42a26182d072d1922f5a57f85ec5717603eff864",
+  "signature": {
+    "status": "unsigned-development"
+  }
+}

package/native/xeno-pty/prebuilds/darwin-x64/manifest.json

@@ -0,0 +1,18 @@
+{
+  "schemaVersion": 2,
+  "component": "xeno-pty",
+  "binary": "xeno_pty.node",
+  "apiVersion": 1,
+  "platform": "darwin",
+  "architecture": "x64",
+  "abi": "napi-v8",
+  "napi": 8,
+  "minimumNode": "20.0.0",
+  "nodeHeaders": "24.18.0",
+  "compiler": "Apple clang version 17.0.0 (clang-1700.0.13.5)",
+  "sourceSha256": "6ba69e62cf0c0765546afa19f1820c1cc7f64f452802718c20b4a117d6c8f9c6",
+  "sha256": "ff459f0ee222bec04513190d2922a9ed76d9bbeb80f5335e6663eed942a4996a",
+  "signature": {
+    "status": "unsigned-development"
+  }
+}

package/native/xeno-pty/prebuilds/linux-arm64/manifest.json

@@ -0,0 +1,18 @@
+{
+  "schemaVersion": 2,
+  "component": "xeno-pty",
+  "binary": "xeno_pty.node",
+  "apiVersion": 1,
+  "platform": "linux",
+  "architecture": "arm64",
+  "abi": "napi-v8",
+  "napi": 8,
+  "minimumNode": "20.0.0",
+  "nodeHeaders": "18.20.4",
+  "compiler": "c++ (Debian 12.2.0-14+deb12u1) 12.2.0",
+  "sourceSha256": "6ba69e62cf0c0765546afa19f1820c1cc7f64f452802718c20b4a117d6c8f9c6",
+  "sha256": "07f660ac0c32ac7a2900f3abdfa12550f603880f02a1763a12a63064fe802006",
+  "signature": {
+    "status": "unsigned-development"
+  }
+}

package/native/xeno-pty/prebuilds/linux-x64/manifest.json

@@ -0,0 +1,18 @@
+{
+  "schemaVersion": 2,
+  "component": "xeno-pty",
+  "binary": "xeno_pty.node",
+  "apiVersion": 1,
+  "platform": "linux",
+  "architecture": "x64",
+  "abi": "napi-v8",
+  "napi": 8,
+  "minimumNode": "20.0.0",
+  "nodeHeaders": "18.20.4",
+  "compiler": "c++ (Debian 12.2.0-14+deb12u1) 12.2.0",
+  "sourceSha256": "6ba69e62cf0c0765546afa19f1820c1cc7f64f452802718c20b4a117d6c8f9c6",
+  "sha256": "a93757b552cb9236fe33773228072df270659d6a015a92fb96d21a9d22c5f2cb",
+  "signature": {
+    "status": "unsigned-development"
+  }
+}

package/native/xeno-pty/prebuilds/win32-x64/manifest.json

@@ -0,0 +1,18 @@
+{
+    "schemaVersion":  2,
+    "component":  "xeno-pty",
+    "binary":  "xeno_pty.node",
+    "apiVersion":  1,
+    "platform":  "win32",
+    "architecture":  "x64",
+    "abi":  "napi-v8",
+    "napi":  8,
+    "minimumNode":  "20.0.0",
+    "nodeHeaders":  "24.13.1",
+    "compiler":  "Microsoft (R) C/C++ Optimizing Compiler Version 19.44.35222 for x64",
+    "sourceSha256":  "9f6f6248f35f2f6b767b153f66670d5ed8f95cb7d6242c77c652efe5cca2d038",
+    "sha256":  "91d9a464823091603d784cbc3a570b8a0e514576eeb4b8fb2aabcdcbb64bccad",
+    "signature":  {
+                      "status":  "unsigned-development"
+                  }
+}

package/native/xeno-pty/trusted-keys.json

@@ -0,0 +1,4 @@
+{
+  "schemaVersion": 1,
+  "keys": []
+}

package/ownership/CLEAN_ROOM_CONTRIBUTOR_GUIDE.md

@@ -0,0 +1,63 @@
+# Xeno Clean-Room Contributor Guide
+
+Status: engineering control draft. Legal counsel approval is required before Xeno makes a public clean-room or proprietary-ownership claim.
+
+## Purpose
+
+This guide governs replacement of third-party implementation code with independently authored Xeno code. It is an engineering provenance control, not legal advice and not proof by itself that a replacement is clean-room work.
+
+## Required roles
+
+- The contract author records behavior from Xeno-owned tests, public standards, public API documentation, and black-box observations.
+- The implementer writes the replacement from the approved contract and declared normative sources.
+- The provenance reviewer independently reviews the implementation, evidence, and contributor disclosures.
+- Counsel determines whether contributor separation or additional review is required for a specific component.
+
+One person may not approve their own provenance review. High-risk native, codec, parser, and cryptographic work also requires a domain reviewer.
+
+## Before implementation
+
+1. Create a clean-room implementation record from `templates/clean-room-implementation-record.md`.
+2. Freeze the required behavior and compatibility fixtures before reading implementation source from the component being replaced.
+3. List every normative standard, public API document, Xeno-owned test, and black-box observation used.
+4. Disclose whether each contributor previously inspected the replaced implementation source and when.
+5. Obtain a written role/separation decision for contributors who inspected that source.
+6. Record patents, trademarks, specification licenses, and export-control questions for counsel.
+
+## Allowed inputs
+
+- Published standards whose terms permit the intended use.
+- Public API and user documentation used only to define observable behavior.
+- Xeno-owned requirements, tests, fixtures, traces, and interoperability captures.
+- Black-box behavior measured through a documented harness.
+- Operating-system and language-host API documentation for approved platform boundaries.
+
+## Prohibited inputs and actions
+
+- Copying third-party source, comments, tests, identifiers, non-normative constants, or internal architecture.
+- Asking an AI model to translate, rewrite, disguise, or recreate third-party source.
+- Including third-party source in prompts, tickets, implementation records, fixtures, or generated-code context.
+- Claiming clean-room status when source-exposure disclosures or counsel review are incomplete.
+- Using a compatibility result as evidence of independent authorship.
+
+## During implementation
+
+1. Keep the implementation record current with design decisions and source citations.
+2. Add conformance, malformed-input, resource-limit, and fuzz tests appropriate to the surface.
+3. Record any behavior that differs from the frozen contract and obtain an explicit versioning decision.
+4. Keep generated artifacts traceable to Xeno-owned source and the approved build process.
+5. Stop and escalate if an undeclared source, copied fragment, or provenance ambiguity is discovered.
+
+AI-generated contributions follow the same rules. Prompts must request independent, standards-based implementation and must be retained or summarized in the implementation record without sensitive user data.
+
+## Required completion evidence
+
+- Completed clean-room implementation record.
+- Completed independent provenance review.
+- Contributor source-exposure disclosures and counsel disposition.
+- Contract fixtures and conformance results.
+- Fuzz and security evidence where required.
+- Ownership inventory, bundle graph, native hashes, SBOM, and clean-install report for the candidate release.
+- Commit or source revision and reviewer identities.
+
+The ownership capability gate remains false until all required evidence exists and the designated reviewer signs the provenance record. Public ownership language additionally requires counsel and product approval.