@xenosystem/agent-sdk 0.9.11 → 0.9.13

package/native/mxc/README.md

@@ -1,25 +1,25 @@
-# Microsoft MXC native assets
-
-This directory contains only the seven release-reviewed executables needed by
-XENO's containment adapter and Windows host preparation. They were extracted from the integrity-pinned
-`@microsoft/mxc-sdk@0.7.0` npm artifact recorded in `package.json`.
-
-XENO does not execute or redistribute that package's JavaScript wrapper or its
-`node-pty`, `node-addon-api`, or `semver` dependency graph. Every executable is
-checked against both this manifest and the compiled XENO trust table before it
-can be probed or launched.
-
-The two `wxc-host-prep.exe` assets are invoked only by the explicit
-`prepareMxcWindowsHost()` setup API. They apply MXC's idempotent
-`prepare-system-drive` and `prepare-null-device` operations from an elevated
-host setup context; normal agent execution never attempts to elevate. Windows
-11 on Arm runs the reviewed x64 host-preparation helper through the operating
-system's x64 emulation layer because these operations are architecture-neutral
-and MXC's ARM64 helper can stall while applying the system-drive metadata ACEs.
-The containment runtime itself remains the native ARM64 `wxc-exec.exe`.
-
-The original Microsoft MIT license is preserved in
-`LICENSE.microsoft-mxc-sdk.md`. Presence of these assets is not containment
-certification: XENO still requires a candidate-bound, platform-bound, signed
-certification and independent reviewer approval before advertising or using
-`contained` execution.
+# Microsoft MXC native assets
+
+This directory contains only the seven release-reviewed executables needed by
+XENO's containment adapter and Windows host preparation. They were extracted from the integrity-pinned
+`@microsoft/mxc-sdk@0.7.0` npm artifact recorded in `package.json`.
+
+XENO does not execute or redistribute that package's JavaScript wrapper or its
+`node-pty`, `node-addon-api`, or `semver` dependency graph. Every executable is
+checked against both this manifest and the compiled XENO trust table before it
+can be probed or launched.
+
+The two `wxc-host-prep.exe` assets are invoked only by the explicit
+`prepareMxcWindowsHost()` setup API. They apply MXC's idempotent
+`prepare-system-drive` and `prepare-null-device` operations from an elevated
+host setup context; normal agent execution never attempts to elevate. Windows
+11 on Arm runs the reviewed x64 host-preparation helper through the operating
+system's x64 emulation layer because these operations are architecture-neutral
+and MXC's ARM64 helper can stall while applying the system-drive metadata ACEs.
+The containment runtime itself remains the native ARM64 `wxc-exec.exe`.
+
+The original Microsoft MIT license is preserved in
+`LICENSE.microsoft-mxc-sdk.md`. Presence of these assets is not containment
+certification: XENO still requires a candidate-bound, platform-bound, signed
+certification and independent reviewer approval before advertising or using
+`contained` execution.

package/native/mxc/package.json

@@ -1,58 +1,58 @@
-{
-  "name": "microsoft-mxc-native-assets",
-  "version": "0.7.0",
-  "private": true,
-  "license": "MIT",
-  "sourcePackage": {
-    "name": "@microsoft/mxc-sdk",
-    "version": "0.7.0",
-    "integrity": "sha512-EWhz2pKkcPluZHAOI1yneV+JK0NO/3hdh7nABBb0x4PjyUWMeSWPTBAjtIu+BhtMYOqlaijSPZMZ0Hs/J4ZL4A==",
-    "shasum": "561a269b8cb5a4eb7e71fc9158ffd0f74760b640"
-  },
-  "assets": [
-    {
-      "platform": "win32",
-      "arch": "x64",
-      "path": "bin/x64/wxc-exec.exe",
-      "sha256": "db0a3422be9e1b396cc1b2547c70ff16b27412438a31c10a45abf370cac86ae2"
-    },
-    {
-      "platform": "win32",
-      "arch": "arm64",
-      "path": "bin/arm64/wxc-exec.exe",
-      "sha256": "e430d0e4f44f616e91db684f8d825a6dc93e06a1262b8d00bcaac7522a317aab"
-    },
-    {
-      "platform": "win32",
-      "arch": "x64",
-      "purpose": "host-preparation",
-      "path": "bin/x64/wxc-host-prep.exe",
-      "sha256": "531fb3cdb4b0c964908fd71b71d40961417afb399cbab72f92a25e95309a6416"
-    },
-    {
-      "platform": "win32",
-      "arch": "arm64",
-      "purpose": "host-preparation",
-      "path": "bin/arm64/wxc-host-prep.exe",
-      "sha256": "3ef702332286a39153fc259310b5021e3de3c191751d7522684f6475f73af5ef"
-    },
-    {
-      "platform": "linux",
-      "arch": "x64",
-      "path": "bin/x64/lxc-exec",
-      "sha256": "1efe3f817f5ae9ba9f9f2fd59142e79b2dde7a4dd024576b0ddb635fc87edeb5"
-    },
-    {
-      "platform": "linux",
-      "arch": "arm64",
-      "path": "bin/arm64/lxc-exec",
-      "sha256": "fdc00ccecf362ae3ddd8ccad93fd7c8b5b1f03c68897ab05ef1c9f1d327ea3fe"
-    },
-    {
-      "platform": "darwin",
-      "arch": "arm64",
-      "path": "bin/arm64/mxc-exec-mac",
-      "sha256": "77c07a86f483ed91dd5be290cd77878ac0c56fe113cdb8c764e7e5201c744ad2"
-    }
-  ]
-}
+{
+  "name": "microsoft-mxc-native-assets",
+  "version": "0.7.0",
+  "private": true,
+  "license": "MIT",
+  "sourcePackage": {
+    "name": "@microsoft/mxc-sdk",
+    "version": "0.7.0",
+    "integrity": "sha512-EWhz2pKkcPluZHAOI1yneV+JK0NO/3hdh7nABBb0x4PjyUWMeSWPTBAjtIu+BhtMYOqlaijSPZMZ0Hs/J4ZL4A==",
+    "shasum": "561a269b8cb5a4eb7e71fc9158ffd0f74760b640"
+  },
+  "assets": [
+    {
+      "platform": "win32",
+      "arch": "x64",
+      "path": "bin/x64/wxc-exec.exe",
+      "sha256": "db0a3422be9e1b396cc1b2547c70ff16b27412438a31c10a45abf370cac86ae2"
+    },
+    {
+      "platform": "win32",
+      "arch": "arm64",
+      "path": "bin/arm64/wxc-exec.exe",
+      "sha256": "e430d0e4f44f616e91db684f8d825a6dc93e06a1262b8d00bcaac7522a317aab"
+    },
+    {
+      "platform": "win32",
+      "arch": "x64",
+      "purpose": "host-preparation",
+      "path": "bin/x64/wxc-host-prep.exe",
+      "sha256": "531fb3cdb4b0c964908fd71b71d40961417afb399cbab72f92a25e95309a6416"
+    },
+    {
+      "platform": "win32",
+      "arch": "arm64",
+      "purpose": "host-preparation",
+      "path": "bin/arm64/wxc-host-prep.exe",
+      "sha256": "3ef702332286a39153fc259310b5021e3de3c191751d7522684f6475f73af5ef"
+    },
+    {
+      "platform": "linux",
+      "arch": "x64",
+      "path": "bin/x64/lxc-exec",
+      "sha256": "1efe3f817f5ae9ba9f9f2fd59142e79b2dde7a4dd024576b0ddb635fc87edeb5"
+    },
+    {
+      "platform": "linux",
+      "arch": "arm64",
+      "path": "bin/arm64/lxc-exec",
+      "sha256": "fdc00ccecf362ae3ddd8ccad93fd7c8b5b1f03c68897ab05ef1c9f1d327ea3fe"
+    },
+    {
+      "platform": "darwin",
+      "arch": "arm64",
+      "path": "bin/arm64/mxc-exec-mac",
+      "sha256": "77c07a86f483ed91dd5be290cd77878ac0c56fe113cdb8c764e7e5201c744ad2"
+    }
+  ]
+}

package/ownership/CLEAN_ROOM_CONTRIBUTOR_GUIDE.md

@@ -1,63 +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.
+# 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.

package/ownership/evidence/PROPRIETARY-COMMAND-1/implementation-record.md

@@ -1,77 +1,77 @@
-# Clean-Room Implementation Record: Xeno Command Runtime
-
-## Identity
-
-- Component: Xeno-owned command schema, parser, help renderer, runner, discovery, and completion metadata
-- Replacement milestone: PROPRIETARY-COMMAND-1
-- Repository and paths: `xeno-agent-cli/apps/xeno-agent-cli/src/cli/`
-- Record owner: Xeno engineering, final owner assignment pending
-- Implementer(s): Codex implementation assistant; human engineering review pending
-- Contract author(s): Xeno engineering behavior capture; final attribution pending
-- Started at (UTC): 2026-07-12
-- Candidate revision: `87ae64b55aa1b8c2e126294e717b229e0945db65` plus recorded working-tree changes
-- Status: implementation complete; provenance approval pending
-
-## Frozen behavioral contract
-
-- Public API and observable behavior: the 201-command Xeno command tree, option and argument metadata, help and usage output, aliases, defaults, action invocation, parent option access, typed errors, and completion/discovery data.
-- Compatibility fixtures: `tests/fixtures/command-runtime/commander-golden.json`, captured before the replacement runtime was selected.
-- Intentional incompatibilities and versioning decision: parse failures are typed and do not call `process.exit` below the top-level host boundary. No user-visible command or help incompatibility is accepted.
-- Security and resource limits: parsing is bounded by the supplied argument vector; suggestions use deterministic edit distance over declared flags and commands; no command text is evaluated.
-- Supported platforms and architectures: host-tokenized arguments on supported Node 20+ Windows, macOS, and Linux environments. Windows behavior has been exercised locally; cross-platform CI remains required.
-
-## Normative and permitted inputs
-
-| Source | Revision/date | Purpose | Terms reviewed by | Evidence path |
-| --- | --- | --- | --- | --- |
-| Xeno proprietary migration specification | 2026-07-12 | Required command behavior and ownership constraints | Engineering; counsel pending | `switch-to-proprietary.md` |
-| Frozen Xeno command runtime fixture | schema version 2 | Black-box compatibility oracle for Xeno's public command surface | Engineering | `tests/fixtures/command-runtime/commander-golden.json` |
-| Xeno command declarations and handlers | candidate working tree | Names, arguments, options, descriptions, defaults, and action contracts | Engineering | `apps/xeno-agent-cli/src/index.ts`, `apps/xeno-agent-cli/src/commands/` |
-| Xeno-owned compatibility and fuzz tests | candidate working tree | Parser, runner, discovery, completion, and failure behavior | Engineering | `tests/command-runtime.test.ts` |
-
-## Contributor source-exposure disclosure
-
-| Contributor | Inspected replaced source? | Date/range | Separation or review decision | Counsel reference |
-| --- | --- | --- | --- | --- |
-| Codex implementation assistant | No Commander implementation source was inspected during this implementation session. Work used Xeno declarations and the frozen black-box fixture. | 2026-07-12 | Independent provenance review required | Pending |
-| Human contributors | Disclosure not yet collected | Pending | Must be completed before capability approval | Pending |
-
-## Implementation log
-
-| Date (UTC) | Decision | Contract/source basis | Author | Evidence path |
-| --- | --- | --- | --- | --- |
-| 2026-07-12 | Use a Xeno schema and parser with a migration builder facade | FR-020 through FR-025 | Codex implementation assistant | `apps/xeno-agent-cli/src/cli/` |
-| 2026-07-12 | Keep local and global option views separate | Existing Xeno handlers and action contract | Codex implementation assistant | `command-parser.ts`, `command-runner.ts` |
-| 2026-07-12 | Generate help, usage, discovery, and completion from one tree | FR-023 | Codex implementation assistant | `command-help.ts`, `command-completion.ts` |
-| 2026-07-12 | Reject Commander runtime residue during release verification | Phase 2 exit gate | Codex implementation assistant | `scripts/verify-release-package.mjs` |
-
-## AI assistance
-
-- Models/tools used: OpenAI Codex coding agent and local PowerShell tooling.
-- Prompt or retained prompt-summary path: active Xeno proprietary migration goal and `switch-to-proprietary.md`.
-- Confirmation that no third-party source entered the prompt: no Commander source was supplied or inspected in this implementation session; only Xeno-owned command declarations and black-box output fixtures were used.
-- Human review performed: pending.
-
-## Verification evidence
-
-- Unit and compatibility tests: `tests/command-runtime.test.ts`; all 201 frozen records match.
-- Conformance corpus: every production command help path and deterministic unknown-option path.
-- Fuzz campaign and duration: deterministic 20,000-case argument corpus completes in the focused test suite.
-- Security/resource-limit tests: typed parse failures, no lower-layer `process.exit`, conflicts, choices, mandatory options, implications, hidden commands.
-- Cross-platform results: Windows local pass; Linux and macOS CI pending.
-- Performance comparison: focused suite completes within normal test duration; formal benchmark pending.
-- Bundle/native/SBOM evidence: artifact ownership audit and paired clean-package smoke must be attached after candidate packaging.
-
-## Open legal or provenance questions
-
-- Patents/specification terms: counsel review pending.
-- Trademarks: Commander name appears only as historical fixture provenance and development-toolchain inventory; counsel disposition pending.
-- Export or distribution constraints: none identified by engineering; counsel review pending.
-- Other: collect all human source-exposure disclosures and assign an independent reviewer.
-
-## Handoff
-
-- Implementation complete: yes
-- Evidence complete: no
-- Ready for independent provenance review: after cross-platform and candidate-package evidence is attached
-- Author/date: Codex implementation assistant, 2026-07-12
+# Clean-Room Implementation Record: Xeno Command Runtime
+
+## Identity
+
+- Component: Xeno-owned command schema, parser, help renderer, runner, discovery, and completion metadata
+- Replacement milestone: PROPRIETARY-COMMAND-1
+- Repository and paths: `xeno-agent-cli/apps/xeno-agent-cli/src/cli/`
+- Record owner: Xeno engineering, final owner assignment pending
+- Implementer(s): Codex implementation assistant; human engineering review pending
+- Contract author(s): Xeno engineering behavior capture; final attribution pending
+- Started at (UTC): 2026-07-12
+- Candidate revision: `87ae64b55aa1b8c2e126294e717b229e0945db65` plus recorded working-tree changes
+- Status: implementation complete; provenance approval pending
+
+## Frozen behavioral contract
+
+- Public API and observable behavior: the 201-command Xeno command tree, option and argument metadata, help and usage output, aliases, defaults, action invocation, parent option access, typed errors, and completion/discovery data.
+- Compatibility fixtures: `tests/fixtures/command-runtime/commander-golden.json`, captured before the replacement runtime was selected.
+- Intentional incompatibilities and versioning decision: parse failures are typed and do not call `process.exit` below the top-level host boundary. No user-visible command or help incompatibility is accepted.
+- Security and resource limits: parsing is bounded by the supplied argument vector; suggestions use deterministic edit distance over declared flags and commands; no command text is evaluated.
+- Supported platforms and architectures: host-tokenized arguments on supported Node 20+ Windows, macOS, and Linux environments. Windows behavior has been exercised locally; cross-platform CI remains required.
+
+## Normative and permitted inputs
+
+| Source | Revision/date | Purpose | Terms reviewed by | Evidence path |
+| --- | --- | --- | --- | --- |
+| Xeno proprietary migration specification | 2026-07-12 | Required command behavior and ownership constraints | Engineering; counsel pending | `switch-to-proprietary.md` |
+| Frozen Xeno command runtime fixture | schema version 2 | Black-box compatibility oracle for Xeno's public command surface | Engineering | `tests/fixtures/command-runtime/commander-golden.json` |
+| Xeno command declarations and handlers | candidate working tree | Names, arguments, options, descriptions, defaults, and action contracts | Engineering | `apps/xeno-agent-cli/src/index.ts`, `apps/xeno-agent-cli/src/commands/` |
+| Xeno-owned compatibility and fuzz tests | candidate working tree | Parser, runner, discovery, completion, and failure behavior | Engineering | `tests/command-runtime.test.ts` |
+
+## Contributor source-exposure disclosure
+
+| Contributor | Inspected replaced source? | Date/range | Separation or review decision | Counsel reference |
+| --- | --- | --- | --- | --- |
+| Codex implementation assistant | No Commander implementation source was inspected during this implementation session. Work used Xeno declarations and the frozen black-box fixture. | 2026-07-12 | Independent provenance review required | Pending |
+| Human contributors | Disclosure not yet collected | Pending | Must be completed before capability approval | Pending |
+
+## Implementation log
+
+| Date (UTC) | Decision | Contract/source basis | Author | Evidence path |
+| --- | --- | --- | --- | --- |
+| 2026-07-12 | Use a Xeno schema and parser with a migration builder facade | FR-020 through FR-025 | Codex implementation assistant | `apps/xeno-agent-cli/src/cli/` |
+| 2026-07-12 | Keep local and global option views separate | Existing Xeno handlers and action contract | Codex implementation assistant | `command-parser.ts`, `command-runner.ts` |
+| 2026-07-12 | Generate help, usage, discovery, and completion from one tree | FR-023 | Codex implementation assistant | `command-help.ts`, `command-completion.ts` |
+| 2026-07-12 | Reject Commander runtime residue during release verification | Phase 2 exit gate | Codex implementation assistant | `scripts/verify-release-package.mjs` |
+
+## AI assistance
+
+- Models/tools used: OpenAI Codex coding agent and local PowerShell tooling.
+- Prompt or retained prompt-summary path: active Xeno proprietary migration goal and `switch-to-proprietary.md`.
+- Confirmation that no third-party source entered the prompt: no Commander source was supplied or inspected in this implementation session; only Xeno-owned command declarations and black-box output fixtures were used.
+- Human review performed: pending.
+
+## Verification evidence
+
+- Unit and compatibility tests: `tests/command-runtime.test.ts`; all 201 frozen records match.
+- Conformance corpus: every production command help path and deterministic unknown-option path.
+- Fuzz campaign and duration: deterministic 20,000-case argument corpus completes in the focused test suite.
+- Security/resource-limit tests: typed parse failures, no lower-layer `process.exit`, conflicts, choices, mandatory options, implications, hidden commands.
+- Cross-platform results: Windows local pass; Linux and macOS CI pending.
+- Performance comparison: focused suite completes within normal test duration; formal benchmark pending.
+- Bundle/native/SBOM evidence: artifact ownership audit and paired clean-package smoke must be attached after candidate packaging.
+
+## Open legal or provenance questions
+
+- Patents/specification terms: counsel review pending.
+- Trademarks: Commander name appears only as historical fixture provenance and development-toolchain inventory; counsel disposition pending.
+- Export or distribution constraints: none identified by engineering; counsel review pending.
+- Other: collect all human source-exposure disclosures and assign an independent reviewer.
+
+## Handoff
+
+- Implementation complete: yes
+- Evidence complete: no
+- Ready for independent provenance review: after cross-platform and candidate-package evidence is attached
+- Author/date: Codex implementation assistant, 2026-07-12

package/ownership/evidence/PROPRIETARY-COMMAND-1/provenance-review.md

@@ -1,51 +1,51 @@
-# Independent Provenance Review: Xeno Command Runtime
-
-## Review identity
-
-- Component: Xeno-owned command runtime
-- Replacement milestone: PROPRIETARY-COMMAND-1
-- Implementation record path: `ownership/evidence/PROPRIETARY-COMMAND-1/implementation-record.md`
-- Candidate revision: `87ae64b55aa1b8c2e126294e717b229e0945db65` plus recorded working-tree changes
-- Reviewer: pending
-- Domain reviewer (required): pending
-- Review date (UTC): pending
-- Reviewer independent of implementation: pending
-
-## Evidence checks
-
-- [ ] Behavioral contract predates or is independent from implementation work.
-- [ ] Normative and public sources are listed with revisions and evidence paths.
-- [ ] Contributor source-exposure disclosures are complete.
-- [ ] Required separation/counsel decisions are attached.
-- [ ] No copied source, comments, tests, identifiers, non-normative constants, or distinctive internal structure were found.
-- [ ] AI inputs and human review satisfy the contributor guide.
-- [ ] Intentional incompatibilities are approved and versioned.
-- [ ] Conformance, malformed-input, security, resource-limit, and fuzz evidence meets the component gate.
-- [ ] Bundle graph, native hashes, SBOM, ownership inventory, and clean-install graph agree.
-- [ ] Licenses, patents, trademarks, and specification terms have an explicit disposition.
-
-## Similarity and provenance review method
-
-- Files and revisions reviewed: pending
-- Comparison method and tools: pending
-- Findings: pending
-- False positives and disposition: pending
-
-## Verification summary
-
-| Gate | Evidence | Result | Notes |
-| --- | --- | --- | --- |
-| Contract compatibility | `tests/fixtures/command-runtime/commander-golden.json`, `tests/command-runtime.test.ts` | engineering pass | Independent confirmation pending |
-| Security/resource limits | typed-error and bounded parser tests | engineering pass | Domain review pending |
-| Fuzz/conformance | deterministic 20,000-case corpus | engineering pass | Independent rerun pending |
-| Cross-platform | Windows local | partial | Linux and macOS CI pending |
-| Artifact ownership | ownership audit and package verifier | pending | Attach candidate reports |
-
-## Decision
-
-- Engineering provenance decision: needs-work
-- Capability gate may be marked achieved: no
-- Public clean-room/proprietary claim approved by this review: no
-- Required follow-up: assign independent and domain reviewers, collect contributor disclosures, run cross-platform and package gates, attach counsel disposition.
-- Reviewer signature/date: pending
-- Counsel approval reference (required for public claim): pending
+# Independent Provenance Review: Xeno Command Runtime
+
+## Review identity
+
+- Component: Xeno-owned command runtime
+- Replacement milestone: PROPRIETARY-COMMAND-1
+- Implementation record path: `ownership/evidence/PROPRIETARY-COMMAND-1/implementation-record.md`
+- Candidate revision: `87ae64b55aa1b8c2e126294e717b229e0945db65` plus recorded working-tree changes
+- Reviewer: pending
+- Domain reviewer (required): pending
+- Review date (UTC): pending
+- Reviewer independent of implementation: pending
+
+## Evidence checks
+
+- [ ] Behavioral contract predates or is independent from implementation work.
+- [ ] Normative and public sources are listed with revisions and evidence paths.
+- [ ] Contributor source-exposure disclosures are complete.
+- [ ] Required separation/counsel decisions are attached.
+- [ ] No copied source, comments, tests, identifiers, non-normative constants, or distinctive internal structure were found.
+- [ ] AI inputs and human review satisfy the contributor guide.
+- [ ] Intentional incompatibilities are approved and versioned.
+- [ ] Conformance, malformed-input, security, resource-limit, and fuzz evidence meets the component gate.
+- [ ] Bundle graph, native hashes, SBOM, ownership inventory, and clean-install graph agree.
+- [ ] Licenses, patents, trademarks, and specification terms have an explicit disposition.
+
+## Similarity and provenance review method
+
+- Files and revisions reviewed: pending
+- Comparison method and tools: pending
+- Findings: pending
+- False positives and disposition: pending
+
+## Verification summary
+
+| Gate | Evidence | Result | Notes |
+| --- | --- | --- | --- |
+| Contract compatibility | `tests/fixtures/command-runtime/commander-golden.json`, `tests/command-runtime.test.ts` | engineering pass | Independent confirmation pending |
+| Security/resource limits | typed-error and bounded parser tests | engineering pass | Domain review pending |
+| Fuzz/conformance | deterministic 20,000-case corpus | engineering pass | Independent rerun pending |
+| Cross-platform | Windows local | partial | Linux and macOS CI pending |
+| Artifact ownership | ownership audit and package verifier | pending | Attach candidate reports |
+
+## Decision
+
+- Engineering provenance decision: needs-work
+- Capability gate may be marked achieved: no
+- Public clean-room/proprietary claim approved by this review: no
+- Required follow-up: assign independent and domain reviewers, collect contributor disclosures, run cross-platform and package gates, attach counsel disposition.
+- Reviewer signature/date: pending
+- Counsel approval reference (required for public claim): pending