@xenosystem/agent-sdk 0.8.13 → 0.9.8

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.