xoonya 2.6.0 → 2.8.0

package/CROSS_RUNTIME_POSTURE.md

@@ -27,14 +27,44 @@ The current reference implementation is Node.js, but the proof contract is desig
 
 These vectors are intended to be reusable by future implementations in other runtimes.
 
-## Current limitation
+## Python candidate scaffold
+
+This repo now ships a Python candidate scaffold in `reference/python`.
+
+It is independent from the JavaScript implementation and can replay the XNYA atom, native atom adversarial, native payload profile, line-rate frame, canonical event, receipt, and non-signed proof-bundle vectors:
+
+```bash
+npm run verify:reference-python
+```
+
+This is not yet a full second reference implementation. It can verify Ed25519 native signed vectors when Python's optional `cryptography` package is installed; otherwise it proves the deterministic `native_signature_crypto_dependency_missing` boundary. It does not claim always-on native signature-suite cryptographic verification, secp256k1/P-256 parity, external proof import, or all native signed proof-bundle round-trip behavior.
+
+The crypto-enabled optional check is:
+
+```bash
+npm run verify:reference-python-crypto
+```
 
-This repo does not yet ship a second-language reference implementation.
+That command creates a temporary isolated Python virtual environment, installs `reference/python/requirements-optional.txt`, and requires the Ed25519 native signed vector to verify.
+
+## Rust candidate scaffold
+
+This repo also ships a source-only Rust candidate scaffold in `reference/rust`.
+
+```bash
+npm run verify:reference-rust-scaffold
+```
+
+That check verifies packaged scaffold files, XNYA atom constants, deterministic parser error-code names, and the `publish = false` boundary. It does not compile Rust or claim vector parity yet.
+
+## Current limitation
 
 So the current cross-runtime posture is:
 
 - contract and vectors are published
 - Node.js reference behavior is enforced
+- Python atom/payload/frame, non-signed proof-bundle vector parity, and optional Ed25519 crypto-gated verification are implemented as a candidate scaffold
+- Rust source scaffold is packaged and boundary-checked, but not vector-verified
 - additional runtime implementations can now target the same vector sets
 
 ## Final release expectation

package/README.md

@@ -262,9 +262,18 @@ XNYA atom conformance now includes stable machine-readable reject codes and adve
 
 The native payload profile is now explicit: `xoonya-native-payload-profile/v1` uses the binary `XNYP` magic and typed fields with deterministic ordering, fixed-width integer encoding, unknown-field policy checks, and no floats or loose JSON semantics. The optional `xoonya-native-line-rate-frame/v1` wraps an existing 58-byte or 70-byte `XNYA` atom with a 2-byte checksum for transport fast rejection; it does not change the atom and does not claim signature, encryption, custody, settlement, or external finality truth.
 
+The `XNYA-compatible` mark is now defined as a conformance claim, not a marketing label. Implementations may use it only when atom bytes, payload profile rules, proof-envelope method behavior, adversarial vectors, and stable error codes match the published artifacts. The mark must not be used to claim PQ/hybrid verification, live external-provider execution, chain finality, custody, identity/auth, or external issuer truth without separate verifier evidence. Until real PQ/hybrid validators exist, `xoonya-native-hybrid-v1` is an explicit design-gate method that rejects with `native_hybrid_design_gated`.
+
+The JavaScript `xoonya` package is the current canonical XNYA reference implementation. A Python candidate scaffold now verifies the XNYA atom, native atom adversarial, XNYP payload profile, line-rate frame, canonical event, receipt, and non-signed proof-bundle vectors independently. It also verifies Ed25519 native signed vectors when Python's optional `cryptography` package is installed, otherwise it reports the deterministic dependency gate. It is not yet a full second reference until always-on signature-suite parity, proof-bundle round trips, and the full promotion gates pass. Rust remains planned until a verified vector-parity implementation exists.
+
+Run `npm run verify:reference-python-crypto` to create an isolated temporary Python virtual environment, install the optional crypto dependency, and require the Ed25519 native signed vector to verify. Run `npm run verify:reference-rust-scaffold` to check the packaged source-only Rust scaffold and its non-promotion boundary.
+
 See [XOONYA_NATIVE_PROOF_FORMAT.md](./XOONYA_NATIVE_PROOF_FORMAT.md).
 See [XOONYA_NATIVE_ATOM_SPEC.md](./XOONYA_NATIVE_ATOM_SPEC.md).
 See [XOONYA_NATIVE_STANDARD_GOVERNANCE.md](./XOONYA_NATIVE_STANDARD_GOVERNANCE.md).
+See [XNYA_CONFORMANCE_MARK.md](./XNYA_CONFORMANCE_MARK.md).
+See [XNYA_REFERENCE_IMPLEMENTATIONS.md](./XNYA_REFERENCE_IMPLEMENTATIONS.md).
+See [CROSS_RUNTIME_POSTURE.md](./CROSS_RUNTIME_POSTURE.md).
 
 ## Compatibility Surface
 
@@ -346,6 +355,10 @@ Primary proof-model routes:
 - `GET /v1/proof-center/native-payload-profile/summary`
 - `GET /v1/proof-center/native-line-rate-frame`
 - `GET /v1/proof-center/native-line-rate-frame/summary`
+- `GET /v1/proof-center/native-conformance-mark`
+- `GET /v1/proof-center/native-conformance-mark/summary`
+- `GET /v1/proof-center/native-reference-implementations`
+- `GET /v1/proof-center/native-reference-implementations/summary`
 - `GET /v1/proof-center/import-adapter`
 - `GET /v1/proof-center/import-adapter/summary`
 - `POST /v1/proof-center/import-adapter/review`
@@ -600,7 +613,7 @@ xoonya conformance
 xoonya conformance --json
 ```
 
-The conformance command verifies the published vector files shipped in the package. The positive set covers `legacy-opreturn-v1`, `detached-assertion-v1`, `xoonya-native-sha256-v1`, `xoonya-native-signed-v1`, `xoonya-native-anchored-v1`, `jwt-assertion-v1`, `did-vc-v1`, `sd-jwt-vc-v1`, `signed-envelope-v1`, and `partner-proof-envelope-v1`. The adversarial set covers bad event versions, missing signatures, mismatched commitments, unsupported methods, ambiguous `none`, replayed receipt context, native digest tampering, native signed proof tampering, native anchored proof tampering, native-to-detached downgrade attempts, and receipt-id mismatches.
+The conformance command verifies the published vector files shipped in the package. The positive set covers `legacy-opreturn-v1`, `detached-assertion-v1`, `xoonya-native-sha256-v1`, `xoonya-native-signed-v1`, `xoonya-native-anchored-v1`, `jwt-assertion-v1`, `did-vc-v1`, `sd-jwt-vc-v1`, `signed-envelope-v1`, and `partner-proof-envelope-v1`. The adversarial set covers bad event versions, missing signatures, mismatched commitments, unsupported methods, ambiguous `none`, explicit native hybrid/PQ design-gated rejection, replayed receipt context, native digest tampering, native signed proof tampering, native anchored proof tampering, native-to-detached downgrade attempts, and receipt-id mismatches.
 
 Published proof hardening artifacts:
 

package/RELEASE_NOTES.md

@@ -1,3 +1,28 @@
+# xoonya 2.8.0 Release Notes
+
+`xoonya` 2.8.0 is the XNYA standard-hardening line for conformance marks, reference implementation promotion discipline, cross-language scaffold evidence, PQ/hybrid design gating, and external proof truth boundaries.
+
+Highlights:
+
+- exposes the XNYA-compatible conformance mark with explicit artifact, vector, error-code, and forbidden-claim boundaries
+- adds the XNYA reference implementation plan and promotion gate so JavaScript remains canonical while Python/Rust require independent vector, crypto, round-trip, conformance, and forbidden-claim evidence before promotion
+- adds Python XNYA atom/payload/frame, proof-bundle, and optional Ed25519 crypto verifier scaffolds without overclaiming full second-reference status
+- packages the Rust XNYA source scaffold while keeping it unpromoted until real Rust toolchain compilation and vector parity exist
+- adds native hybrid/PQ design-gate vectors and deterministic rejection so PQ/hybrid remains visible but not claimable as live verification
+- hardens external proof import truth boundaries for JWT, DID/VC, SD-JWT VC, signed-envelope, detached assertion, and partner proof material
+- keeps the 2.7.0 packaged conformance and clean-consumer release-smoke posture intact while making native-standard claims more defensible
+
+# xoonya 2.7.0 Release Notes
+
+`xoonya` 2.7.0 is the expansion-closeout release line for package-hardening, clean-consumer release smoke testing, and disciplined native-standard claim boundaries.
+
+Highlights:
+
+- ships `scripts/` in the npm artifact so `xoonya conformance` and `xoonya first-run --verify-native` work from a clean npm install
+- adds release-candidate guards that fail if conformance verifier scripts are missing from `npm pack`
+- participates in the Naxytra release-smoke harness that installs packed tarballs into a clean consumer project before synchronized release
+- keeps the 2.6.0 XNYA native, payload, line-rate frame, import-adapter, and standardization capabilities intact while closing the packaging reliability gap
+
 # xoonya 2.6.0 Release Notes
 
 `xoonya` 2.6.0 is the expansion release line for Xoonya Native standard hardening, external proof import, native signed and anchored verification, and strict XNYA payload/frame profile work.

package/SERVICE_CONTRACT.md

@@ -63,6 +63,10 @@ Primary proof-model routes:
 - `GET /v1/proof-center/native-hybrid-readiness/summary`
 - `GET /v1/proof-center/native-standardization`
 - `GET /v1/proof-center/native-standardization/summary`
+- `GET /v1/proof-center/native-conformance-mark`
+- `GET /v1/proof-center/native-conformance-mark/summary`
+- `GET /v1/proof-center/native-reference-implementations`
+- `GET /v1/proof-center/native-reference-implementations/summary`
 - `GET /v1/proof-center/native-atom-spec`
 - `GET /v1/proof-center/native-atom-spec/summary`
 - `GET /v1/proof-center/native-atom-conformance`

package/XNYA_CONFORMANCE_MARK.md

@@ -0,0 +1,78 @@
+# XNYA Conformance Mark
+
+`XNYA-compatible` is the compatibility mark for implementations that preserve the Xoonya Native atom, payload, proof-envelope, and vector behavior exactly enough for deterministic machine evidence to remain portable.
+
+The mark is not an identity, auth, custody, transport-security, settlement, chain-finality, or external-provider truth claim.
+
+## Required Meaning
+
+An implementation may claim `XNYA-compatible` only when it can show:
+
+- the native atom magic is exactly `XNYA`
+- atom versions and fixed sizes match the published spec
+- payload and identity hash derivation match the published vectors
+- required native methods either verify or are explicitly declared unsupported
+- adversarial vectors fail with stable error codes
+- `algorithm: "none"` is rejected for production proof
+- anchor binding does not claim independent external chain or provider truth
+
+## Required Artifacts
+
+The following artifacts define the current conformance floor:
+
+- `XOONYA_NATIVE_PROOF_FORMAT.md`
+- `XOONYA_NATIVE_ATOM_SPEC.md`
+- `XOONYA_NATIVE_STANDARD_GOVERNANCE.md`
+- `XNYA_CONFORMANCE_MARK.md`
+- `vectors/conformance-vectors.json`
+- `vectors/adversarial-vectors.json`
+- `vectors/native-atom-vectors.json`
+- `vectors/native-payload-profile-vectors.json`
+
+## Required Checks
+
+At minimum, a compatible implementation must pass equivalent checks to:
+
+```bash
+xoonya first-run --verify-native --pretty
+xoonya conformance --json
+npm run verify:release-candidate
+npm run verify:service
+```
+
+Non-JavaScript implementations should publish deterministic pass/fail output against the same vector IDs, byte layouts, and error-code expectations.
+
+## Allowed Claim Classes
+
+`xnya_atom_compatible` means the implementation preserves `XNYA` atom bytes, lengths, versions, record types, hash derivation, and reject codes.
+
+`xnya_payload_profile_compatible` means the implementation preserves the `XNYP` binary payload profile: typed fields, canonical ordering, fixed-width integers, explicit unknown-field policy, and no loose JSON or float semantics.
+
+`xnya_native_proof_compatible` means registered native methods verify through the declared suite registry, reject `algorithm: "none"`, and keep signatures, anchors, and external references outside the atom core.
+
+`xnya_external_interop_compatible` means external proof envelopes are bound to canonical Xoonya receipts without claiming issuer, DID, JWT, SD-JWT, chain, or partner-provider truth unless an external verifier is declared and bound.
+
+## Forbidden Claims
+
+Do not claim the mark if:
+
+- `XNYA` magic, fixed sizes, version semantics, or atom layout are changed
+- `algorithm: "none"` verifies as production proof
+- happy-path vectors pass but adversarial vectors are skipped
+- PQ/hybrid support is claimed without validators, vectors, downgrade tests, and deterministic error codes
+- external issuer, chain, finality, custody, or provider truth is claimed as Xoonya-verified without a declared external verifier
+- the mark is used to imply login, session, wallet, custody, payment, transport, or regulatory compliance behavior
+
+## Extra Evidence Gates
+
+PQ/hybrid native verification requires non-experimental validators, suite-specific public-key rules, positive conformance vectors, adversarial downgrade vectors, and deterministic error codes.
+
+Live external framework-provider compatibility requires real external endpoints, auth boundaries, health checks, failure behavior, latency evidence, and live execution checks.
+
+New signature suites require suite-specific validators plus wrong-key, wrong-method, tamper, and downgrade vectors before they can move from registry/planned status to implemented status.
+
+## Governance
+
+The mark should stay tied to concrete artifacts, not brand aspiration. New public mark claims require docs, vectors, deterministic error codes, release-candidate checks, and service surfaces before public use.
+
+The reference implementation ships inside the `xoonya` npm package until external adoption or governance pressure justifies a separate standards repository.

package/XNYA_REFERENCE_IMPLEMENTATIONS.md

@@ -0,0 +1,157 @@
+# XNYA Reference Implementations
+
+`XNYA-compatible` needs independent implementations, not only one JavaScript package. This document defines how Xoonya treats reference implementations without overclaiming maturity before vector parity exists.
+
+## Current Reference
+
+The current canonical reference implementation ships inside the `xoonya` npm package:
+
+- `proof_sdk.js` contains the canonical JavaScript helpers, validators, proof builders, and pack generators.
+- `vectors/` contains the positive and adversarial conformance inputs.
+- `bin/xoonya.js` exposes first-run and conformance checks.
+- `bin/xoonya-release.js` exposes public release and standardization artifacts.
+- `server.js` exposes the proof-center JSON surfaces.
+
+Required checks:
+
+```bash
+npm run verify:release-candidate
+npm run verify:all
+xoonya conformance --json
+xoonya first-run --verify-native --pretty
+```
+
+## Planned Independent References
+
+Python and Rust reference implementations are planned, but they are not public compatibility claims until they pass the same vector floor independently.
+
+Candidate names:
+
+- `xoonya-native-python`
+- `xoonya-native-rust`
+
+Each candidate must implement its own byte parser and verifier. Wrapping the JavaScript runtime is useful for demos, but it is not an independent reference implementation.
+
+Promotion evidence is checked separately from scaffold parity:
+
+```bash
+npm run verify:reference-promotion-gate
+```
+
+That verifier proves a complete candidate promotion packet can pass validation, while incomplete packets fail with deterministic rejection codes. The gate requires repository/package evidence, all required vector sets, deterministic error-code parity, independent parser evidence, native signature-suite crypto parity, cross-language round-trip evidence, conformance-mark review, forbidden-claim review, and no secret material.
+
+## Python Candidate Scaffold
+
+The Python candidate scaffold lives in `reference/python`.
+
+It currently covers:
+
+- XNYA atom v1 and v2 creation
+- XNYA atom parsing and verification
+- native atom adversarial reject codes
+- XNYP payload profile encoding and parsing
+- line-rate frame checksum verification
+- canonical event hash parity
+- receipt emission for external assertion, native digest, legacy OP_RETURN, and native anchored methods
+- proof-bundle build/verify parity for non-signed native methods
+- adversarial reason parity for non-signed proof-bundle checks
+- deterministic `native_hybrid_design_gated` rejection for the future hybrid/PQ method
+- optional Ed25519 native signed verification when the Python `cryptography` package is available
+- deterministic `native_signature_crypto_dependency_missing` when the optional crypto dependency is absent
+
+Run:
+
+```bash
+npm run verify:reference-python
+```
+
+This is vector-parity progress, not a full reference promotion. Python does not yet claim always-on native signature-suite cryptographic verification, secp256k1/P-256 parity, external method import, or all native signed proof-bundle round-trip behavior.
+
+Optional Ed25519 crypto check:
+
+```bash
+npm run verify:reference-python-crypto
+```
+
+This command creates an isolated temporary Python virtual environment, installs `reference/python/requirements-optional.txt`, runs the same vector verifier, and requires `verified_signature_suite_count = 1`.
+
+Without the optional dependency, the default verifier still passes by proving the explicit dependency boundary.
+
+## Rust Candidate Scaffold
+
+The Rust candidate scaffold lives in `reference/rust`.
+
+It currently covers:
+
+- source-only package boundary for `xoonya-native-rust`
+- fixed-size `XNYA` atom constants
+- v1/v2 atom byte-length checks
+- deterministic atom parser error codes
+- `publish = false` until vector parity and promotion gates exist
+
+Run:
+
+```bash
+npm run verify:reference-rust-scaffold
+```
+
+This is a packaging and boundary guard only. It does not compile Rust in the
+current release path, does not run positive/adversarial vectors, and does not
+claim `XNYA-compatible` status for Rust.
+
+## Required Vector Floor
+
+An independent implementation must pass:
+
+- `vectors/conformance-vectors.json`
+- `vectors/adversarial-vectors.json`
+- `vectors/native-atom-vectors.json`
+- `vectors/native-payload-profile-vectors.json`
+
+The implementation must also produce stable reject reasons equivalent to the published deterministic error codes.
+
+## Required Behavior
+
+An implementation may claim `XNYA-compatible` only when it:
+
+- parses `XNYA` atoms exactly by byte layout and fixed size
+- preserves `XNYA` atom v1 and v2 domain separation
+- parses `XNYP` payload profiles without loose JSON, floats, or implicit type coercion
+- rejects unsupported or malformed native atoms with deterministic errors
+- rejects `algorithm: "none"` as a production proof method
+- verifies only implemented signature suites with suite-specific validators
+- treats PQ/hybrid methods as design-gated until validators and vectors exist
+- binds external proof formats without claiming external issuer truth
+- binds anchor references without claiming external chain or provider finality truth
+
+## Promotion Gates
+
+Independent references become public reference implementations only after:
+
+1. A package or repository exists with public source, license, docs, and test commands.
+2. The candidate passes all positive and adversarial vector sets.
+3. The candidate emits deterministic errors that match the JavaScript reference.
+4. The candidate can generate artifacts verified by the JavaScript reference.
+5. The JavaScript reference can generate artifacts verified by the candidate.
+6. The candidate satisfies the `XNYA-compatible` mark without forbidden claims.
+7. The candidate passes `npm run verify:reference-promotion-gate` with promotion evidence that does not contain private keys, access tokens, credentials, or authorization material.
+
+## Non-Claims
+
+The reference implementation plan does not claim:
+
+- PQ or hybrid runtime validation
+- live external provider execution
+- identity, authentication, custody, transport, or settlement security
+- Rust vector parity or full Rust reference status
+- external issuer truth for JWT, DID/VC, SD-JWT VC, signed-envelope, or partner proofs
+- external chain or provider finality truth
+
+Those claims require separate validators, policies, and evidence.
+
+## Service Surface
+
+The machine-readable pack is exposed at:
+
+- `GET /v1/proof-center/native-reference-implementations`
+- `GET /v1/proof-center/native-reference-implementations/summary`

package/XOONYA_NATIVE_PROOF_FORMAT.md

@@ -331,6 +331,8 @@ This should provide stronger-crypto or PQC-sensitive proof lanes if production n
 
 The current rule is strict: `xoonya-native-hybrid-v1` remains design-gated until runtime validators, public key formats, conformance vectors, adversarial vectors, and deterministic error codes exist. Xoonya may expose readiness and promotion criteria for this method, but must not claim PQC or hybrid verification before those artifacts are real.
 
+Before promotion, any proof bundle that directly asks the current verifier to accept `xoonya-native-hybrid-v1` must fail with the deterministic reason `native_hybrid_design_gated`. Hybrid-looking native signatures also must not verify through an external assertion method; those downgrade attempts fail as `signature_method_mismatch`.
+
 ## Crypto And Identity Support Boundary
 
 Xoonya Native supports cryptographic ecosystems by committing to their canonical identity or proof material. It does not become those ecosystems.

package/XOONYA_NATIVE_STANDARD_GOVERNANCE.md

@@ -10,7 +10,7 @@ The goal is not to create a format for novelty. The goal is to preserve a small
 
 ## Compatibility Marks
 
-The phrase `Xoonya Native compatible` should mean:
+The phrase `XNYA-compatible` should mean:
 
 - the implementation accepts the canonical `XNYA` atom magic
 - it validates the published byte layouts exactly
@@ -18,6 +18,7 @@ The phrase `Xoonya Native compatible` should mean:
 - it passes the published conformance vectors
 - it rejects the published adversarial vectors
 - it does not redefine a published version line
+- it follows the public mark rules in `XNYA_CONFORMANCE_MARK.md`
 
 Implementations that use a different magic value, different field ordering, different hash derivation, or soft-forked validation behavior are not Xoonya Native atom implementations. They are separate formats.
 
@@ -91,6 +92,8 @@ Not current public claims:
 
 The current Xoonya Native atom conformance surface is:
 
+- `GET /v1/proof-center/native-conformance-mark`
+- `GET /v1/proof-center/native-conformance-mark/summary`
 - `GET /v1/proof-center/native-atom-spec`
 - `GET /v1/proof-center/native-atom-spec/summary`
 - `GET /v1/proof-center/native-atom-conformance`

package/bin/xoonya-release.js

@@ -51,6 +51,12 @@ const {
   buildReleaseCandidatePack,
   summarizeReleaseCandidatePack
 } = require("../lib/release_candidate");
+const {
+  buildXoonyaNativeConformanceMarkPack,
+  summarizeXoonyaNativeConformanceMarkPack,
+  buildXoonyaNativeReferenceImplementationPack,
+  summarizeXoonyaNativeReferenceImplementationPack
+} = require("../proof_sdk");
 const {
   buildPhaseProgramPack,
   summarizePhaseProgramPack
@@ -528,7 +534,7 @@ function printUsage() {
   process.stderr.write(
     [
       "Usage:",
-      "  xoonya-release [--summary] [--comparison] [--adoption] [--scenarios] [--launch] [--manifest] [--notes] [--center] [--history] [--phases] [--phase-1] [--phase-1-openai-codex] [--phase-1-openai-codex-proof] [--phase-1-claude-mcp] [--phase-1-claude-mcp-proof] [--phase-2] [--phase-2-completion] [--phase-2-freeze-review] [--phase-2-gate] [--phase-2-closeout] [--phase-2-decision-record] [--phase-2-decision-resolution] [--phase-2-flip-preview] [--phase-2-evm-proof] [--phase-2-evm-base-proof] [--phase-2-base-proof] [--phase-2-usdc-proof] [--phase-2-base-usdc-proof] [--phase-2-eth-proof] [--phase-3] [--phase-3-native-continuity] [--phase-3-freeze-baseline] [--phase-3-completion] [--phase-3-freeze-review] [--phase-3-gate] [--phase-3-closeout] [--phase-3-decision-record] [--phase-3-decision-resolution] [--phase-3-bsv-teranode-proof] [--phase-3-metanet-proof] [--phase-3-brc-proof] [--phase-4] [--phase-4-trust-continuity] [--phase-4-completion] [--phase-4-freeze-baseline] [--phase-4-freeze-review] [--phase-4-gate] [--phase-4-closeout] [--phase-4-decision-record] [--phase-4-decision-resolution] [--phase-4-erc8004-proof] [--phase-4-identity-registry-proof] [--phase-4-attestation-proof] [--phase-5] [--phase-5-major-rails-continuity] [--phase-5-completion] [--phase-5-freeze-baseline] [--phase-5-freeze-review] [--phase-5-gate] [--phase-5-closeout] [--phase-5-decision-record] [--phase-5-decision-resolution] [--phase-5-solana-proof] [--phase-5-antelope-proof] [--phase-5-proton-xpr-proof] [--phase-6] [--phase-6-framework-continuity] [--phase-6-completion] [--phase-6-freeze-baseline] [--phase-6-freeze-review] [--phase-6-gate] [--phase-6-closeout] [--phase-6-decision-record] [--phase-6-decision-resolution] [--phase-6-langgraph-proof] [--phase-6-langchain-proof] [--phase-6-autogen-proof] [--phase-6-semantic-kernel-proof] [--phase-7] [--phase-7-event-system-continuity] [--phase-7-completion] [--phase-7-freeze-baseline] [--phase-7-freeze-review] [--phase-7-gate] [--phase-7-closeout] [--phase-7-decision-record] [--phase-7-decision-resolution] [--phase-7-kafka-proof] [--phase-7-nats-proof] [--phase-7-mqtt-proof] [--phase-7-webhook-event-bus-proof] [--phase-8] [--phase-8-proof-bridge-continuity] [--phase-8-completion] [--phase-8-freeze-baseline] [--phase-8-freeze-review] [--phase-8-gate] [--phase-8-closeout] [--phase-8-decision-record] [--phase-8-decision-resolution] [--phase-8-external-result-import-proof] [--phase-8-external-receipt-import-proof] [--phase-8-proof-bundle-normalization-proof] [--phase-9] [--phase-9-treasury-continuity] [--phase-9-completion] [--phase-9-freeze-baseline] [--phase-9-freeze-review] [--phase-9-gate] [--phase-9-closeout] [--phase-9-decision-record] [--phase-9-decision-resolution] [--phase-9-treasury-destinations-proof] [--phase-9-custody-refs-proof] [--phase-9-operator-accounting-bridges-proof] [--phase-10] [--phase-10-long-tail-continuity] [--phase-10-completion] [--phase-10-freeze-baseline] [--phase-10-freeze-review] [--phase-10-gate] [--phase-10-closeout] [--phase-10-decision-record] [--phase-10-decision-resolution] [--phase-10-demand-signal-adapters-proof] [--phase-10-niche-extension-registry-proof] [--phase-10-ecosystem-backlog-triage-proof] [--publish-plan] [--ecosystem] [--narrative] [--outreach-proof] [--announcement] [--candidate] [--pretty]",
+      "  xoonya-release [--summary] [--comparison] [--adoption] [--scenarios] [--launch] [--manifest] [--notes] [--center] [--history] [--native-conformance-mark] [--native-reference-implementations] [--phases] [--phase-1] [--phase-1-openai-codex] [--phase-1-openai-codex-proof] [--phase-1-claude-mcp] [--phase-1-claude-mcp-proof] [--phase-2] [--phase-2-completion] [--phase-2-freeze-review] [--phase-2-gate] [--phase-2-closeout] [--phase-2-decision-record] [--phase-2-decision-resolution] [--phase-2-flip-preview] [--phase-2-evm-proof] [--phase-2-evm-base-proof] [--phase-2-base-proof] [--phase-2-usdc-proof] [--phase-2-base-usdc-proof] [--phase-2-eth-proof] [--phase-3] [--phase-3-native-continuity] [--phase-3-freeze-baseline] [--phase-3-completion] [--phase-3-freeze-review] [--phase-3-gate] [--phase-3-closeout] [--phase-3-decision-record] [--phase-3-decision-resolution] [--phase-3-bsv-teranode-proof] [--phase-3-metanet-proof] [--phase-3-brc-proof] [--phase-4] [--phase-4-trust-continuity] [--phase-4-completion] [--phase-4-freeze-baseline] [--phase-4-freeze-review] [--phase-4-gate] [--phase-4-closeout] [--phase-4-decision-record] [--phase-4-decision-resolution] [--phase-4-erc8004-proof] [--phase-4-identity-registry-proof] [--phase-4-attestation-proof] [--phase-5] [--phase-5-major-rails-continuity] [--phase-5-completion] [--phase-5-freeze-baseline] [--phase-5-freeze-review] [--phase-5-gate] [--phase-5-closeout] [--phase-5-decision-record] [--phase-5-decision-resolution] [--phase-5-solana-proof] [--phase-5-antelope-proof] [--phase-5-proton-xpr-proof] [--phase-6] [--phase-6-framework-continuity] [--phase-6-completion] [--phase-6-freeze-baseline] [--phase-6-freeze-review] [--phase-6-gate] [--phase-6-closeout] [--phase-6-decision-record] [--phase-6-decision-resolution] [--phase-6-langgraph-proof] [--phase-6-langchain-proof] [--phase-6-autogen-proof] [--phase-6-semantic-kernel-proof] [--phase-7] [--phase-7-event-system-continuity] [--phase-7-completion] [--phase-7-freeze-baseline] [--phase-7-freeze-review] [--phase-7-gate] [--phase-7-closeout] [--phase-7-decision-record] [--phase-7-decision-resolution] [--phase-7-kafka-proof] [--phase-7-nats-proof] [--phase-7-mqtt-proof] [--phase-7-webhook-event-bus-proof] [--phase-8] [--phase-8-proof-bridge-continuity] [--phase-8-completion] [--phase-8-freeze-baseline] [--phase-8-freeze-review] [--phase-8-gate] [--phase-8-closeout] [--phase-8-decision-record] [--phase-8-decision-resolution] [--phase-8-external-result-import-proof] [--phase-8-external-receipt-import-proof] [--phase-8-proof-bundle-normalization-proof] [--phase-9] [--phase-9-treasury-continuity] [--phase-9-completion] [--phase-9-freeze-baseline] [--phase-9-freeze-review] [--phase-9-gate] [--phase-9-closeout] [--phase-9-decision-record] [--phase-9-decision-resolution] [--phase-9-treasury-destinations-proof] [--phase-9-custody-refs-proof] [--phase-9-operator-accounting-bridges-proof] [--phase-10] [--phase-10-long-tail-continuity] [--phase-10-completion] [--phase-10-freeze-baseline] [--phase-10-freeze-review] [--phase-10-gate] [--phase-10-closeout] [--phase-10-decision-record] [--phase-10-decision-resolution] [--phase-10-demand-signal-adapters-proof] [--phase-10-niche-extension-registry-proof] [--phase-10-ecosystem-backlog-triage-proof] [--publish-plan] [--ecosystem] [--narrative] [--outreach-proof] [--announcement] [--candidate] [--pretty]",
       "",
       "Options:",
       "  --summary   Emit the compact release-pack summary",
@@ -540,6 +546,8 @@ function printUsage() {
       "  --notes   Emit the release notes artifact",
       "  --center   Emit the canonical release center artifact",
       "  --history   Emit the release history artifact",
+      "  --native-conformance-mark   Emit the XNYA conformance-mark artifact",
+      "  --native-reference-implementations   Emit the XNYA reference-implementation plan",
       "  --phases   Emit the multi-phase adapter program artifact",
       "  --phase-1   Emit the Phase 1 ecosystem artifact",
       "  --phase-1-openai-codex   Emit the Phase 1 OpenAI/Codex ecosystem artifact",
@@ -686,6 +694,8 @@ function main() {
   const notes = args.includes("--notes");
   const center = args.includes("--center");
   const history = args.includes("--history");
+  const nativeConformanceMark = args.includes("--native-conformance-mark");
+  const nativeReferenceImplementations = args.includes("--native-reference-implementations");
   const phases = args.includes("--phases");
   const phase1 = args.includes("--phase-1");
   const phase1OpenaiCodex = args.includes("--phase-1-openai-codex");
@@ -844,6 +854,14 @@ function main() {
     payload = summarizeReleaseHistory();
   } else if (history) {
     payload = buildReleaseHistory();
+  } else if (nativeConformanceMark && summary) {
+    payload = summarizeXoonyaNativeConformanceMarkPack();
+  } else if (nativeConformanceMark) {
+    payload = buildXoonyaNativeConformanceMarkPack();
+  } else if (nativeReferenceImplementations && summary) {
+    payload = summarizeXoonyaNativeReferenceImplementationPack();
+  } else if (nativeReferenceImplementations) {
+    payload = buildXoonyaNativeReferenceImplementationPack();
   } else if (phases && summary) {
     payload = summarizePhaseProgramPack();
   } else if (phases) {

package/bin/xoonya.js

@@ -41,6 +41,7 @@ function printStartHere() {
     "   xoonya conformance --json",
     "4. Inspect native proof surfaces:",
     "   https://xoonya.onrender.com/v1/proof-center/native-standard/summary",
+    "   https://xoonya.onrender.com/v1/proof-center/native-conformance-mark/summary",
     "   https://xoonya.onrender.com/v1/proof-center/native-anchor-profile/summary",
     "",
     "Native proof modes:",

package/lib/release_history.js

@@ -10,6 +10,33 @@ function buildReleaseHistory() {
     current_version: packageJson.version,
     release_track: "public_release",
     history: [
+      {
+        version: "2.8.0",
+        channel: "public_release",
+        maturity_posture: "native_standard_hardened",
+        headline: "XNYA standard-hardening release with conformance mark, reference promotion discipline, Python/Rust scaffold evidence, PQ/hybrid design gating, and external proof truth boundaries",
+        milestone_refs: [
+          "xnya_conformance_mark",
+          "xnya_reference_implementation_plan",
+          "python_xnya_vector_and_crypto_scaffold",
+          "rust_xnya_source_scaffold",
+          "native_hybrid_design_gate",
+          "external_proof_import_truth_gate"
+        ]
+      },
+      {
+        version: "2.7.0",
+        channel: "public_release",
+        maturity_posture: "expansion_closeout",
+        headline: "expansion-closeout release with packaged conformance verifiers, clean-consumer release smoke testing, and disciplined native-standard claim boundaries",
+        milestone_refs: [
+          "npm_packaged_first_run_native_verification",
+          "npm_packaged_conformance_cli",
+          "release_candidate_packaging_guard",
+          "clean_consumer_release_smoke",
+          "expansion_closeout_claim_boundaries"
+        ]
+      },
       {
         version: "2.6.0",
         channel: "public_release",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "xoonya",
-  "version": "2.6.0",
+  "version": "2.8.0",
   "description": "Deterministic proof and review engine for receipts, handoffs, governance, and verification.",
   "main": "index.js",
   "bin": {
@@ -23,8 +23,10 @@
     "proof_sdk.js",
     "server.js",
     "bin/",
+    "scripts/",
     "lib/",
     "integrations/",
+    "reference/",
     "vectors/",
     "RELEASE_NOTES.md",
     ".env.example",
@@ -32,6 +34,8 @@
     "XOONYA_NATIVE_PROOF_FORMAT.md",
     "XOONYA_NATIVE_ATOM_SPEC.md",
     "XOONYA_NATIVE_STANDARD_GOVERNANCE.md",
+    "XNYA_CONFORMANCE_MARK.md",
+    "XNYA_REFERENCE_IMPLEMENTATIONS.md",
     "WHY_XYTARA_XOONYA.md",
     "CARRIED_HANDOFF_DEMO.md",
     "PARTNER_READY_PATH.md",
@@ -68,13 +72,19 @@
     "start": "node server.js",
     "verify:package": "node scripts/verify_all.js",
     "verify:conformance": "node scripts/verify_vectors.js",
+    "verify:external-proof-import-gate": "node scripts/verify_external_proof_import_gate.js",
     "verify:integrations": "node scripts/verify_integrations.js",
     "verify:tooling": "node scripts/verify_tooling.js",
+    "verify:reference-python": "node scripts/verify_reference_python.js",
+    "verify:reference-python-crypto": "node scripts/verify_reference_python_crypto.js",
+    "verify:reference-promotion-gate": "node scripts/verify_reference_promotion_gate.js",
+    "verify:reference-rust-scaffold": "node scripts/verify_reference_rust_scaffold.js",
+    "verify:native-hybrid-gate": "node scripts/verify_native_hybrid_design_gate.js",
     "verify:vectors": "node scripts/verify_vectors.js",
     "verify:examples": "node scripts/verify_examples.js",
     "verify:service": "node scripts/verify_service.js",
     "verify:release-candidate": "node scripts/verify_release_candidate.js",
-    "verify:all": "node scripts/verify_all.js && node scripts/verify_integrations.js && node scripts/verify_tooling.js && node scripts/verify_vectors.js && node scripts/verify_examples.js && node scripts/verify_service.js",
+    "verify:all": "node scripts/verify_all.js && node scripts/verify_external_proof_import_gate.js && node scripts/verify_integrations.js && node scripts/verify_tooling.js && node scripts/verify_vectors.js && node scripts/verify_reference_python.js && node scripts/verify_reference_promotion_gate.js && node scripts/verify_reference_rust_scaffold.js && node scripts/verify_native_hybrid_design_gate.js && node scripts/verify_examples.js && node scripts/verify_service.js",
     "prepublishOnly": "npm run verify:release-candidate"
   }
 }