xytara 2.9.0 → 2.10.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/RELEASE_NOTES.md CHANGED
@@ -1,75 +1,11 @@
1
- # xytara 2.9.0 Release Notes
1
+ # xytara 2.10.0 Release Notes
2
2
 
3
- `xytara` 2.9.0 is the public-polish release line for canonical Naxytra product URLs and safer first-contact runtime guidance.
3
+ `xytara` 2.10.0 is the release-hygiene and launch-polish line for current-release-only package notes, safer first-contact docs, and stronger release-candidate packaging checks.
4
4
 
5
5
  Highlights:
6
6
 
7
- - moves the package homepage and funding URL to `https://naxytra.com/xytara`
8
- - removes standalone product-domain assumptions from current launch guidance
9
- - replaces older wallet-secret and txid-led first-contact examples with the quote-first `xytara first-run --run-quote` path
10
- - keeps the 2.8.0 release-boundary hardening around provider promotion, treasury claims, pricing guardrails, and read-only operator observability intact
11
- - prepares the synchronized Naxytra 2.9.0 line for a cleaner public website, npm, and release verification pass
12
-
13
- # xytara 2.8.0 Release Notes
14
-
15
- `xytara` 2.8.0 is the release-boundary hardening line for live-provider promotion discipline, treasury/operator public-claim safety, and pricing experiment guardrails.
16
-
17
- Highlights:
18
-
19
- - adds framework-provider promotion evidence gates so LangGraph/LangChain style claims stay reference-contract until endpoint, auth, health, latency, failure, and proof-fact evidence exists
20
- - hardens pricing experiment planning and launch gates so optimization remains sample-maturity and operator-review gated
21
- - hardens treasury public claim boundaries so public surfaces do not leak landing/custody/provider refs or promote readiness-only/internal rails as live
22
- - hardens operator observability boundaries so read-only views cannot drift into mutation, settlement submission, fund movement, unsafe attention actions, or secret-bearing control behavior
23
- - keeps the 2.7.0 clean-consumer packaging and release-smoke posture intact while making expansion claims more defensible
24
-
25
- # xytara 2.7.0 Release Notes
26
-
27
- `xytara` 2.7.0 is the expansion-closeout release line for package-hardening, clean-consumer release smoke testing, and disciplined adapter/product claim boundaries.
28
-
29
- Highlights:
30
-
31
- - ships `scripts/` in the npm artifact so packaged verification commands are available to consumers
32
- - adds release-candidate guards that fail if required verifier scripts are missing from `npm pack`
33
- - participates in the Naxytra release-smoke harness that installs packed tarballs into a clean consumer project before synchronized release
34
- - keeps the 2.6.0 expansion capabilities and adapter surfaces intact while closing the packaging reliability gap
35
-
36
- # xytara 2.6.0 Release Notes
37
-
38
- `xytara` 2.6.0 is the expansion release line for first-run execution polish, provider-backed adapter depth, and framework reference adapters while preserving the existing machine-commerce, settlement, observability, and release surfaces.
39
-
40
- Highlights:
41
-
42
- - umbrella CLI entrypoint with `xytara start-here`, plus `xytara run` and `xytara release`
43
- - public first-run quote and credits-first execution posture for outside builders
44
- - provider-backed `adapter.mcp.invoke` depth with concrete MCP tool binding
45
- - executable LangGraph and LangChain reference framework adapters with manifests and proof-compatible execution facts
46
- - adapter verifier coverage for provider and framework execution posture
47
- - read-only operator observability across activity, payment, delivery, settlement, external credit grants, adapter failures, and pricing telemetry
48
- - first-class public contract lanes for `OpenAPI`, `AsyncAPI`, and `CloudEvents`
49
- - first-class provider, framework, protocol, and integration-matrix discovery surfaces
50
- - surfaced runtime breadth across `MCP`, `A2A`, `A2C`, `x402`, `Stripe MPP`, stablecoins, major rails, treasury, and registry-backed integrations
51
- - surfaced framework and ecosystem breadth including `LangGraph`, `LangChain`, `AutoGen`, `Semantic Kernel`, `CrewAI`, and `LlamaIndex`
52
- - surfaced protocol and transport breadth including `ACP`, `gRPC`, `Kafka`, `NATS`, `MQTT`, `ROS2`, and webhook event bus posture
53
- - first-class observability, provenance, artifact-distribution, shared-signals, and feature-control lanes
54
- - clearer install-and-use posture for humans, developers, and agents without widening the native runtime core
55
- - existing wallet / authority / identity / trust / capability / pricing / participation foundations remain in place
56
-
57
- Recommended first checks:
58
-
59
- 1. `npm install xytara`
60
- 2. `xytara start-here`
61
- 3. `npm run verify:release-candidate`
62
- 4. `node examples/partner_launch_walkthrough.js`
63
- 5. inspect `/v1/providers`, `/v1/frameworks`, `/v1/protocols`, and `/v1/integration-matrix`
64
- 6. inspect `/v1/adapter-depth/summary` and `/v1/operator-observability/summary`
65
- 7. inspect `/v1/mcp`, `/v1/a2a`, `/v1/a2c`, `/v1/x402`, and `/v1/settlement`
66
- 8. inspect `/v1/telemetry`, `/v1/provenance`, `/v1/artifact-distribution`, `/v1/shared-signals`, and `/v1/feature-control`
67
- 9. inspect `/v1/economics/accounts/:account_id/wallet-ledger-bundle`
68
- 10. inspect `/v1/economics/accounts/:account_id/network-participation-package`
69
-
70
- Recommended first docs:
71
-
72
- - `PROGRAM_COMPLETE_RELEASE.md`
73
- - `FINAL_CONTRACT.md`
74
- - `WHY_XYTARA_XOONYA.md`
75
- - `PARTNER_READY_PATH.md`
7
+ - keeps `RELEASE_NOTES.md` scoped to the current release so npm and GitHub release notes do not read like a rolling changelog
8
+ - adds a release-candidate guard that fails when package release notes contain prior release headings or drift from the package version
9
+ - replaces the remaining soft-launch wallet-secret and txid example with the quote-first public first-run path
10
+ - keeps the canonical `https://naxytra.com/xytara` public product URL and website polish intact
11
+ - prepares the synchronized Naxytra 2.10.0 line for a cleaner npm, GitHub, website, and post-deploy verification pass
@@ -10,6 +10,18 @@ function buildReleaseHistory() {
10
10
  current_version: packageJson.version,
11
11
  release_track: "public_release",
12
12
  history: [
13
+ {
14
+ version: "2.10.0",
15
+ channel: "public_release",
16
+ maturity_posture: "release_hygiene",
17
+ headline: "release-hygiene line with current-release-only notes, package verifier guards, and safer first-contact soft-launch guidance",
18
+ milestone_refs: [
19
+ "current_release_only_release_notes",
20
+ "release_notes_packaging_guard",
21
+ "soft_launch_quote_first_guidance",
22
+ "synchronized_2_10_release_prep"
23
+ ]
24
+ },
13
25
  {
14
26
  version: "2.9.0",
15
27
  channel: "public_release",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "xytara",
3
- "version": "2.9.0",
3
+ "version": "2.10.0",
4
4
  "description": "Agent-commerce runtime for quote, pay, execute, deliver, meter, and integrate.",
5
5
  "main": "index.js",
6
6
  "bin": {
@@ -1,6 +1,7 @@
1
1
  "use strict";
2
2
 
3
3
  const assert = require("assert");
4
+ const fs = require("fs");
4
5
  const path = require("path");
5
6
  const { execFileSync, execSync } = require("child_process");
6
7
  const packageJson = require("../package.json");
@@ -14,6 +15,29 @@ function parsePackDryRun() {
14
15
  return Array.isArray(parsed) ? parsed[0] : parsed;
15
16
  }
16
17
 
18
+ function verifyReleaseNotes() {
19
+ const notesPath = path.resolve(__dirname, "..", "RELEASE_NOTES.md");
20
+ const notes = fs.readFileSync(notesPath, "utf8");
21
+ const headings = (notes.match(/^#\s+xytara\s+\d+\.\d+\.\d+\s+Release Notes\s*$/gm) || [])
22
+ .map((heading) => heading.trim());
23
+ assert.deepStrictEqual(
24
+ headings,
25
+ [`# xytara ${packageJson.version} Release Notes`],
26
+ "RELEASE_NOTES.md must contain only the current xytara release heading"
27
+ );
28
+ assert.strictEqual(
29
+ notes.includes(`xytara\` ${packageJson.version}`),
30
+ true,
31
+ "RELEASE_NOTES.md must mention the current package version"
32
+ );
33
+ const mentionedVersions = notes.match(/\b\d+\.\d+\.\d+\b/g) || [];
34
+ assert.strictEqual(
35
+ mentionedVersions.every((version) => version === packageJson.version),
36
+ true,
37
+ "RELEASE_NOTES.md must not mention prior package versions"
38
+ );
39
+ }
40
+
17
41
  function main() {
18
42
  const releaseOutput = execFileSync(process.execPath, [
19
43
  path.resolve(__dirname, "..", "bin", "xytara-release.js"),
@@ -27,6 +51,7 @@ function main() {
27
51
  assert.strictEqual(releaseCandidate.product, "xytara", "release candidate product mismatch");
28
52
  assert.strictEqual(releaseCandidate.publish_access, "public", "release candidate publish access mismatch");
29
53
  assert.strictEqual(releaseCandidate.checklist_count >= 5, true, "release candidate checklist count mismatch");
54
+ verifyReleaseNotes();
30
55
 
31
56
  const dryRun = parsePackDryRun();
32
57
  assert.strictEqual(dryRun.name, packageJson.name, "npm pack dry-run name mismatch");