xytara 2.5.0 → 2.6.0

package/OPERATIONS_RUNBOOK.md

@@ -1,66 +0,0 @@
-# xytara Operations Runbook
-
-Use this runbook for the normal post-program operating posture.
-
-## Daily checks
-
-Run:
-
-```bash
-xytara-release --center --summary
-xytara-release --candidate --summary
-```
-
-Inspect:
-
-- `/v1/release-center/summary`
-- `/v1/release-candidate/summary`
-- `/v1/runtime/durability`
-
-## Runtime durability checks
-
-Healthy durability should show:
-
-- `enabled: true`
-- recoverable posture present
-- no active persistence blocker
-
-If you use hidden-account grants, credits, entitlements, or usage meters, durability is not optional.
-
-## Release confidence checks
-
-Run:
-
-```bash
-npm run verify:examples
-npm run verify:release-candidate
-npm run verify:production-readiness
-```
-
-## Partner-facing checks
-
-Keep these ready:
-
-- `PROGRAM_COMPLETE_RELEASE.md`
-- `PARTNER_READY_PATH.md`
-- `PUBLIC_DEMO_SCRIPT.md`
-- `CARRIED_HANDOFF_DEMO.md`
-
-## If durability looks wrong
-
-Check in this order:
-
-1. `/v1/runtime/durability`
-2. persistence configuration
-3. the most recent persisted timestamp
-4. whether the last real grant/write advanced persistence state
-
-## If an external adopter asks “where do I start?”
-
-Point them to:
-
-1. `START_HERE.md`
-2. `PARTNER_READY_PATH.md`
-3. `PUBLIC_DEMO_SCRIPT.md`
-
-Do not send a raw dump of all docs first.

package/OPERATOR_START_HERE.md

@@ -1,63 +0,0 @@
-# xytara Operator Start Here
-
-This is the shortest path for an operator who needs to evaluate `xytara` after the 10-phase program has already closed.
-
-## 1. Confirm Terminal Program State
-
-Run:
-
-```bash
-xytara-release --phases --summary
-xytara-release --phase-10 --summary
-```
-
-Or inspect:
-
-- `GET /v1/phases/summary`
-- `GET /v1/phases/phase-10/gate/summary`
-- `GET /v1/phases/phase-10/completion/summary`
-
-## 2. Confirm Release Posture
-
-Run:
-
-```bash
-xytara-release --center --summary
-xytara-release --candidate --summary
-```
-
-These are the fastest checks for "is the package live, coherent, and publish-shaped?"
-
-## 3. Exercise The Runtime Path
-
-Run:
-
-```bash
-node examples/quickstart.js
-```
-
-This remains the fastest package-level execution story.
-
-## 4. Verify Confidence
-
-Run:
-
-```bash
-npm run verify:all
-npm run verify:release-candidate
-```
-
-For the compact day-two operator path, also read:
-
-- `OPERATIONS_RUNBOOK.md`
-
-## 5. Choose The Next Workstream
-
-After the program is closed, the next useful work is one of:
-
-- productization
-- real partner/internal integration
-- operational hardening
-- launch and release packaging
-
-If you only pick one, pick a real integration and keep the docs/productization work close behind it.

package/PROGRAM_COMPLETE_RELEASE.md

@@ -1,63 +0,0 @@
-# xytara Program-Complete Release
-
-`xytara` is no longer an in-flight phase build. The public 10-phase program is complete, and this repository now represents a release-shaped machine-commerce runtime.
-
-## What is complete
-
-- the full phase program is closed
-- the default runtime path is stable
-- reusable credits and entitlements exist on the public spine
-- cross-repo handoff into `xoonya` is documented and runnable
-- operator and partner-facing docs now exist alongside the package
-- runtime durability is explicit instead of hidden
-- Supabase-backed durability is available when persistent disk is not
-
-## What this release means
-
-This release is the point where `xytara` should be evaluated as a public runtime and commerce surface, not as an unfinished internal roadmap.
-
-The recommended evaluation path is now:
-
-1. read `START_HERE.md`
-2. run `node examples/quickstart.js`
-3. run `node examples/partner_launch_walkthrough.js`
-4. inspect `CARRIED_HANDOFF_DEMO.md`
-5. inspect `PARTNER_READY_PATH.md`
-
-## Public outcome
-
-An external builder should now be able to:
-
-- understand the runtime role quickly
-- run a first machine-commerce path locally
-- inspect release and launch posture through summary surfaces
-- understand partner adapter onboarding without private explanation
-- understand how proof-side followthrough continues into `xoonya`
-
-## Operator outcome
-
-An operator should now be able to:
-
-- inspect runtime durability explicitly
-- verify release-candidate posture quickly
-- onboard generic external builders without writing one-off handoff notes
-- point durability-sensitive adopters to the correct persistence path
-
-## Recommended live checks
-
-- `/v1/release-center/summary`
-- `/v1/release-candidate/summary`
-- `/v1/runtime/durability`
-- `/v1/adapter-partners/summary`
-
-## Release rule
-
-Do not describe this repository as “phase-complete but still basically internal.”
-
-The correct external posture is:
-
-- program complete
-- runtime public
-- partner-ready
-- proof-aware
-- operationally inspectable

package/PROGRAM_STATUS.md

@@ -1,57 +0,0 @@
-# xytara Program Status
-
-`xytara` is no longer in an active milestone-build posture.
-
-The public phase program is complete and the runtime now sits in terminal closeout posture:
-
-- `current_phase: "program_closed"`
-- `completed_phase_count: 10`
-- `active_phase_count: 0`
-- Phase 10 decision: `ready_for_program_closeout`
-
-## What Exists Now
-
-The live package now includes:
-
-- transaction discovery, quoting, execution, and lifecycle inspection
-- release-center and phase-program inspection surfaces
-- production-facing adapter onboarding and third-party registration material
-- multi-rail settlement and continuity surfaces through the full 10-phase program
-- machine-readable closeout state instead of an indefinitely open final phase
-
-## Best Next Work
-
-The highest-value next work is no longer "add more phases."
-
-It is:
-
-1. productization: tighten onboarding, examples, install paths, and first-contact docs
-2. real integrations: wire 1-3 actual partner or internal use cases end to end
-3. operational hardening: improve observability, deployment metadata, and operator audit posture
-4. commercial packaging: prepare demos, launch collateral, and versioned release framing
-
-## Operator Checks
-
-For a quick terminal-state inspection, use:
-
-```bash
-xytara-release --phases --summary
-xytara-release --phase-10 --summary
-xytara-release --center --summary
-```
-
-Or inspect the live HTTP surfaces:
-
-- `GET /v1/phases/summary`
-- `GET /v1/phases/phase-10/completion/summary`
-- `GET /v1/phases/phase-10/gate/summary`
-- `GET /v1/release-center/summary`
-
-## Recommended Reading Order
-
-1. [START_HERE.md](C:/Users/Yoga/Desktop/workspace/vscode_workspace_public/naxytra/xytara/START_HERE.md)
-2. [README.md](C:/Users/Yoga/Desktop/workspace/vscode_workspace_public/naxytra/xytara/README.md)
-3. [FINAL_CONTRACT.md](C:/Users/Yoga/Desktop/workspace/vscode_workspace_public/naxytra/xytara/FINAL_CONTRACT.md)
-4. [SERVICE_CONTRACT.md](C:/Users/Yoga/Desktop/workspace/vscode_workspace_public/naxytra/xytara/SERVICE_CONTRACT.md)
-5. [PROGRAM_STATUS.md](C:/Users/Yoga/Desktop/workspace/vscode_workspace_public/naxytra/xytara/PROGRAM_STATUS.md)
-6. [CARRIED_HANDOFF_DEMO.md](C:/Users/Yoga/Desktop/workspace/vscode_workspace_public/naxytra/xytara/CARRIED_HANDOFF_DEMO.md)

package/PUBLISH_PLAN.md

@@ -1,14 +0,0 @@
-# xytara Publish Plan
-
-1. Run `npm run verify:release-candidate`.
-2. Run `node examples/partner_launch_walkthrough.js`.
-3. Run `npm pack --dry-run --json` and confirm the package contents.
-4. Publish with `npm publish --access public`.
-5. Redeploy the live service surfaces.
-6. Verify:
-   - `/v1/release-candidate/summary`
-   - `/v1/release-center/summary`
-   - `/v1/announcement-pack/summary`
-   - `/v1/outreach-proof/summary`
-   - `/v1/runtime/durability`
-7. Run the first public machine proof path.

package/RELEASE_CHECKLIST.md

@@ -1,16 +0,0 @@
-# xytara Release Checklist
-
-1. Run `npm run verify:release-candidate`.
-2. Confirm `npm pack --dry-run --json` includes the public docs and both CLI entrypoints.
-3. Run `node examples/partner_launch_walkthrough.js`.
-3. Redeploy the service and verify:
-   - `/v1/release-center/summary`
-   - `/v1/announcement-pack/summary`
-   - `/v1/outreach-proof/summary`
-   - `/v1/runtime/durability`
-4. Confirm the program-complete docs are packaged:
-   - `PROGRAM_COMPLETE_RELEASE.md`
-   - `WHY_XYTARA_XOONYA.md`
-   - `PARTNER_READY_PATH.md`
-5. Run the first public proof path.
-6. Only then publish the npm package.