@surlymochan/evalid 0.0.0-stage → 0.4.1

package/docs/launch-dossier.md

@@ -0,0 +1,180 @@
+# evalid Launch Dossier
+
+Generated: 2026-11-05T17:36:26.724Z
+Mode: post_publish
+Verdict: conditionally ready: engine and adoption evidence are strong, registry publication remains required for a splash launch
+Launch ready: not yet
+Splash verdict: conditionally ready: engine and maintainer adoption evidence are strong, but third-party adoption and registry publication remain required for an industry-splash launch
+Splash launch ready: not yet
+Competitive score: 100/100
+
+## Quality Judgment
+
+strong, launch-ready after registry publish; adoption evidence is now non-fixture but third-party proof remains the next ecosystem win
+
+Codex native goal comparison: xflow can beat Codex native goal at the project layer, not as a thread reminder.
+
+## Surface Scorecard
+
+| Surface | Grade | Why | Next win |
+| --- | --- | --- | --- |
+| xflow:goal | A | Durable .xflow/GOAL.md anchor with CLI access, cross-tool portability, and machine-readable goal audit. | Collect real project examples where goal alignment changed handoff or review quality. |
+| xflow:yolo | A | Lite workflow is executable YAML with split red/green TDD proof, quality review, archive order, and drift coverage. | Publish a tiny external repo walkthrough that shows a real bugfix from red proof to archive. |
+| xflow:corps | A | Heavy workflow has governed proof, visual benchmark gates, no-stub runtime witnesses, control-plane observability, and a first-time operator guide. | Publish a third-party product/UI adoption walkthrough backed by corps proof. |
+| skill family | A- | The ladder now reads goal -> takein -> plan -> yolo/corps -> ralph -> handoff/aha, with sync and diff checks. | Publish the package and collect third-party adoption evidence beyond maintainer dogfooding. |
+
+## Objective Audit
+
+- `goal_vs_codex`: proven_project_layer
+- `yolo_delivery`: proven_from_source
+- `corps_delivery`: proven_from_source
+- `skill_family_open_source_credibility`: ready_from_source_checkout
+- `open_source_launch`: blocked
+- `industry_splash`: blocked
+
+## Demo Proof Paths
+
+### Goal to yolo
+
+Use when: backend, docs, infra, and small UI changes
+
+Commands:
+- `xflow guide`
+- `xflow assess`
+- `xflow init --project-root .`
+- `xflow goal set "Ship the next verified change" --project-root .`
+- `xflow goal audit --project-root . --json`
+- `xflow workflow validate yolo --project-root .`
+- `xflow workflow run yolo --project-root . --title "Example verified change" --change-type backend --tdd-red-command "npm test -- --grep new-behavior" --tdd-green-command "npm test"`
+
+Evidence:
+- `.xflow/GOAL.md`
+- `xflow goal audit --json`
+- `specs/changes/<change-id>/tdd/red-0.json`
+- `specs/changes/<change-id>/tdd/green-0.json`
+- `specs/changes/<change-id>/tdd/quality-0.json`
+- `HANDOFF.md`
+
+### Goal to corps proof
+
+Use when: product, UI, competitor-led, or multi-agent work
+
+Commands:
+- `xflow goal show --json`
+- `xflow goal audit --json`
+- `xflow corps --title "Competitor-aligned workbench" --change-type frontend --change-id launch-corps-demo --capture-url http://127.0.0.1:4174/ --reference-image refs/competitor-main.png --dry-run --json`
+- `xflow proof --track corps --change-id launch-corps-demo`
+
+Evidence:
+- `.xflow/GOAL.md`
+- `xflow goal audit --json`
+- `specs/changes/launch-corps-demo/visual_benchmark.json`
+- `specs/changes/launch-corps-demo/corps_proof.json`
+- `hash-linked execution log witnesses`
+- `final goal-alignment review`
+
+## Runnable Examples
+
+- `docs/examples-gallery.md` maps clean adoption smoke, goal-to-yolo, goal-to-corps proof, external tracker import, and release gate examples.
+- Use `xflow demo launch --json` for the machine-readable launch path summary.
+
+## Release Gate
+
+- `npm run release:pack`
+- `npm run publish:check`
+- `xflow evaluate --json`
+- `xflow release status --json`
+- `xflow adoption trial --name <team-or-project> --source <tracker-or-pr> --track yolo --json`
+- `xflow goal audit --json`
+- `xflow adoption status --json`
+- `xflow adoption validate --json`
+- `xflow launch claims --json`
+- `xflow launch copy --json`
+- `xflow package status --json`
+- `xflow package preflight --check-registry --check-auth --json`
+- `xflow package audit --check-registry --json`
+- `xflow launch audit --strict --json`
+- `xflow launch audit --splash --strict --json`
+- `git status --short --branch`
+
+## Missing Before Ordinary Launch
+
+- **published_package**: Public npm package ownership confirmed and package published from a green dry run.
+  Why it matters: A launch story is incomplete while users cannot install the advertised package name.
+  Acceptable evidence: npm view @surlymochan/evalid name version --json returns this package; npm publish --access public completed for the intended version
+
+## Missing Before Splash Launch
+
+- **third_party_adoption**: At least one adoption artifact comes from a third-party project, public PR, external repository, or named external team beyond maintainer dogfooding.
+  Why it matters: An industry-splash claim needs ecosystem evidence, not only a maintainer hardening run inside evalid.
+  Acceptable evidence: docs/adoption/<third-party-project>.md with a public PR, external repository, or named external team source; xflow adoption validate --splash --json passes; xflow launch audit --splash --strict --json passes
+- **published_package**: Public npm package ownership confirmed and package published from a green dry run.
+  Why it matters: A launch story is incomplete while users cannot install the advertised package name.
+  Acceptable evidence: npm view @surlymochan/evalid name version --json returns this package; npm publish --access public completed for the intended version
+
+## Current Evidence Snapshot
+
+- Adoption records: 1; status: pass
+- Goal audit: pass; goal: Keep evalid credible as an open-source agent delivery runtime: repo-owned workflow contracts, executable verification gates, durable project context, and honest benchmark evidence.
+- Package evidence: missing; source: registry_json
+- Package name/version: @surlymochan/evalid@0.4.1
+
+## Passing Evidence
+
+- `xflow assess --json`
+- `xflow score --json`
+- `xflow goal audit --json`
+- `xflow adoption validate --json`
+
+## Available Checks
+
+- `xflow quickstart --json`
+- `xflow evaluate --json`
+- `xflow release status --json`
+- `xflow assess --json`
+- `xflow demo launch --json`
+- `xflow launch claims --json`
+- `xflow launch copy --json`
+- `xflow score --json`
+- `xflow goal audit --json`
+- `xflow adoption status --json`
+- `npm run release:pack`
+- `npm run publish:check`
+- `xflow package status --json`
+- `xflow package preflight --check-registry --check-auth --json`
+- `xflow package audit --check-registry --json`
+
+## Next Actions For Ordinary Launch
+
+- **verify_release_pack**: `npm run release:pack`
+  Reason: Re-run the full local release pack immediately before any publish attempt.
+- **check_package_preflight**: `xflow package preflight --check-registry --check-auth --json`
+  Reason: Verify npm identity plus package-name/version availability without publishing.
+- **run_pre_publish_launch_audit**: `xflow launch audit --pre-publish --strict --json`
+  Reason: Prove score, adoption evidence, npm identity, and package availability before the irreversible publish step.
+- **publish_package**: `npm publish --access public`
+  Reason: Run only after release:pack, package preflight, and pre-publish launch audit are green.
+- **verify_registry_publication**: `xflow package audit --check-registry --json`
+  Reason: Prove the public npm registry reports the expected package name and version before claiming npm install readiness.
+- **rerun_launch_audit**: `xflow launch audit --strict --json`
+  Reason: Close the post-publish launch gate after registry evidence is visible.
+
+## Next Actions For Splash Launch
+
+- **record_third_party_adoption**: `xflow adoption kit --name <third-party-project> --source <public-pr-or-external-repo> --track yolo`
+  Reason: Industry-splash claims require a third-party trial packet that becomes reviewable evidence beyond maintainer dogfooding.
+- **validate_splash_adoption**: `xflow adoption validate --splash --json`
+  Reason: Remove the third_party_adoption gap only after a third-party record passes validation.
+- **verify_release_pack**: `npm run release:pack`
+  Reason: Re-run the full local release pack immediately before any publish attempt.
+- **check_package_preflight**: `xflow package preflight --check-registry --check-auth --json`
+  Reason: Verify npm identity plus package-name/version availability without publishing.
+- **run_pre_publish_launch_audit**: `xflow launch audit --pre-publish --strict --json`
+  Reason: Prove score, adoption evidence, npm identity, and package availability before the irreversible publish step.
+- **publish_package**: `npm publish --access public`
+  Reason: Run only after release:pack, package preflight, and pre-publish launch audit are green.
+- **verify_registry_publication**: `xflow package audit --check-registry --json`
+  Reason: Prove the public npm registry reports the expected package name and version before claiming npm install readiness.
+- **rerun_launch_audit**: `xflow launch audit --strict --json`
+  Reason: Close the post-publish launch gate after registry evidence is visible.
+

package/docs/methodology.md

@@ -0,0 +1,149 @@
+# xflow Methodology
+
+Date: 2026-04-19
+
+## Purpose
+
+xflow should feel like a guided delivery loop, not a bag of internal atoms. Operators should know what to do next even when they do not know the workflow internals.
+
+The loop is:
+
+```text
+shape -> choose-track -> execute -> review -> finish
+```
+
+Use `xflow guide` when you need the shortest reminder of this loop.
+
+## 1. Shape The Work
+
+Goal: turn a rough request into a readable problem frame before implementation.
+
+Use:
+
+```bash
+xflow:plan
+```
+
+Expected artifacts:
+
+- `proposal.md`
+- `plan.md`
+
+Rules:
+
+- Keep planning track-neutral.
+- Do not choose yolo or corps inside plan.
+- Reuse an existing current `plan.md` when yolo or corps starts.
+
+## 2. Choose The Delivery Track
+
+Goal: select the smallest track that can safely complete the work.
+
+Use `xflow:yolo` when the change is bounded:
+
+- backend logic
+- docs
+- scripts
+- infrastructure
+- small UI changes without a design loop
+
+Use `xflow:corps` when the change needs heavier coordination:
+
+- complex UI or product work
+- multi-agent execution
+- visual review
+- mission control and gate observability
+
+CLI equivalents:
+
+```bash
+xflow workflow validate yolo
+xflow workflow validate corps
+```
+
+`workflow validate` is preflight only. It must not be used as proof that
+`xflow:corps` ran.
+
+## 3. Execute With Gates
+
+Goal: move work through deterministic phases while preserving evidence.
+
+Use:
+
+```bash
+xflow workflow run yolo --title "<title>" --change-type backend
+```
+
+or:
+
+```bash
+xflow corps --title "<title>" --change-type frontend --change-id <id>
+xflow proof --track corps --change-id <id>
+```
+
+Expected artifacts:
+
+- `status.json`
+- `verify_proof.json`
+- `corps_proof.json` for heavy-track completion
+- workflow logs
+- phase outputs under `specs/changes/<change-id>/`
+
+Rules:
+
+- Gates are stop signs, not decoration.
+- Human gates require explicit approval.
+- Verification evidence should be produced before archive.
+- `corps` completion requires the governed built-in workflow manifest, hash-linked execution-log witnesses for every canonical phase, successful atom/gate evidence, and no `stub`, `task_queued`, or `pencil_stubbed` fallback.
+- TDD is a first-class gate: the red proof runs before implementation, the green proof runs after implementation, and quality review rejects code changes without meaningful changed tests.
+
+## 4. Review The Evidence
+
+Goal: make completion defensible before shipping or handing off.
+
+Run:
+
+```bash
+npm test
+npm run drift:scan
+npm run skill:diff
+xflow score
+```
+
+Review:
+
+- `docs/reviewer-guide.md`
+- `verify_proof.json`
+- `HANDOFF.md`
+- current git status
+
+## 5. Finish And Preserve Context
+
+Goal: close the loop without losing durable learning.
+
+Archive ownership stays with:
+
+```text
+A5.archive.commit_push_close
+```
+
+Expected durable outputs:
+
+- refreshed `HANDOFF.md`
+- updated `AHA.md` when there is a durable insight
+- merged spec/workflow deltas
+- committed and pushed implementation
+
+## How This Beats Prompt-Only Workflows
+
+xflow does not rely on a remembered chat ritual. The methodology is backed by:
+
+- executable YAML workflows
+- schema and registry tests
+- local readiness checks
+- drift scans
+- installed skill sync checks
+- handoff and archive artifacts
+- `xflow score` evidence
+
+The result is a workflow that is understandable to humans and enforceable by tooling.

package/docs/npm-publish-handoff.md

@@ -0,0 +1,96 @@
+# npm Publish Handoff
+
+Date: 2026-05-23
+
+Use this page for the final irreversible public publish step. Everything here
+is intentionally explicit because `npm publish --access public` changes public
+distribution state.
+
+## Automated publish (trusted publishing)
+
+The registry-mutating step normally runs from GitHub Actions, not from a
+local shell: `.github/workflows/npm-publish.yml` publishes via npm trusted
+publishing (OIDC — no stored npm token anywhere) whenever a GitHub Release
+is published, and can also be started manually (workflow_dispatch) to
+publish the version in `package.json` if that version is not on npm yet.
+Before publishing it runs the same `npm run release:pack` gate as the manual
+sequence below, and for release events it refuses to publish when the
+release tag does not match the `package.json` version. The manual sequence
+below remains the fallback for when Actions or the trusted-publisher
+registration on npmjs.com is unavailable.
+
+## Current Verified State
+
+- Package: `evalid@0.2.0`
+- Registry name status: available in `xflow package preflight --check-registry --check-auth --json`
+- Current machine auth: blocked by `npm whoami` with `ENEEDAUTH`
+- Adoption gate: `xflow adoption validate --json` passes with
+  `docs/adoption/openflow-release-hardening.md`
+- Splash gate: `xflow release status --json` still reports
+  `third_party_adoption` alongside `published_package`; use
+  `xflow adoption brief --name <third-party-project> --source <public-pr-or-external-repo> --track yolo`
+  to generate the outbound ask, then
+  `xflow adoption trial --name <third-party-project> --source <public-pr-or-external-repo> --track yolo`
+  before asking an external team to create reviewable evidence.
+- Launch gate: `xflow launch audit --strict --json` still lists only
+  `published_package`
+
+Do not claim public installability until the registry reports `evalid@0.2.0`.
+
+## Auth Recovery
+
+```bash
+npm login
+npm whoami
+xflow package status --json
+xflow package preflight --check-registry --check-auth --json
+```
+
+The preflight must report:
+
+- `ok: true`
+- `registry_status: "available"` for a first publish
+- a non-empty `npm_identity`
+- no `registry already contains evalid@0.2.0` issue
+- `next_actions` containing `run_pre_publish_gate` as the next release-owner
+  command
+
+## Final Publish Sequence
+
+Run from the repository root after npm auth is restored:
+
+```bash
+npm run release:pack
+npm run publish:check
+xflow release status --json
+xflow adoption brief --name <third-party-project> --source <public-pr-or-external-repo> --track yolo
+xflow adoption trial --name <third-party-project> --source <public-pr-or-external-repo> --track yolo
+xflow adoption validate --json
+xflow goal audit --json
+xflow package status --json
+xflow package preflight --check-registry --check-auth --json
+xflow launch audit --pre-publish --strict --json
+npm publish --access public
+xflow package audit --check-registry --json
+xflow launch audit --strict --json
+```
+
+The real publish is allowed only after the pre-publish launch audit is green.
+After publish, the strict launch audit is allowed to become green only when
+`xflow package audit --check-registry --json` confirms the public registry
+returns the expected name and version.
+
+## Stop Conditions
+
+- `npm whoami` fails: restore npm auth first.
+- Registry already contains `evalid@0.2.0`: do not republish; bump version or
+  verify ownership before continuing.
+- `xflow package preflight --check-registry --check-auth --json` fails: follow
+  its `next_actions` before retrying or publishing.
+- `npm run release:pack` fails: fix local quality before publishing.
+- `xflow adoption validate --json` fails: restore a non-fixture adoption record.
+- `xflow launch audit --pre-publish --strict --json` fails: do not publish.
+- `xflow package audit --check-registry --json` fails after publish: follow its
+  `next_actions`; do not claim public installability until it passes.
+- `npm publish --dry-run --access public` includes test fixtures, Python caches,
+  local `.as-xflow/` state, or secrets: fix package inclusion before publishing.

package/docs/openspec-migration.md

@@ -0,0 +1,106 @@
+# OpenSpec Migration Guide
+
+Use this guide when moving an OpenSpec-style project into evalid, or when explaining how the two systems map.
+
+OpenSpec is strongest as a lightweight spec-driven development surface. evalid keeps that spec discipline, then adds executable workflow gates, TDD proof, test-quality review, archive ordering, handoff, and release checks.
+
+## Safe Mapping Command
+
+Run this first. It does not move or rewrite files.
+
+```bash
+xflow spec openspec-map --project-root . --openspec-root openspec
+xflow spec start --title "example change" --change-type backend
+xflow spec quick "example change"
+xflow spec delta --project-root . --change-id <id>
+```
+
+First command output:
+
+```text
+.as-xflow/openspec-migration.json
+```
+
+The report maps:
+
+- `openspec/specs/*.md` to durable `specs/*.md`
+- `openspec/changes/<change>/proposal.md` to `specs/changes/<change-id>/proposal.md`
+- `openspec/changes/<change>/design.md` to design context or change notes
+- accepted OpenSpec scope and design decisions to `specs/changes/<id>/plan.md`
+- `openspec/changes/<change>/tasks.md` to `specs/changes/<change-id>/tasks.md`
+- OpenSpec change folders to xflow `change_id` values
+
+## Command Mapping
+
+| OpenSpec | evalid |
+| --- | --- |
+| `openspec init` | `xflow init --project-root .` |
+| `/opsx:new <change>` | `xflow spec quick "<title>"` or `xflow spec start --title "<title>" --change-type <type>` |
+| `/opsx:ff` | `xflow:plan` creates or refreshes `plan.md` |
+| `/opsx:apply` | `xflow workflow run yolo|corps --project-root .` |
+| `/opsx:archive` | xflow archive phase through `A5.archive.commit_push_close` |
+| OpenSpec spec delta review | `xflow spec delta --change-id <id>` |
+
+## Folder Mapping
+
+| OpenSpec Path | evalid Path | Notes |
+| --- | --- | --- |
+| `openspec/specs/` | `specs/` | Durable root specs. Keep stable, reviewed, and human-readable. |
+| `openspec/changes/<id>/proposal.md` | `specs/changes/<id>/proposal.md` | Preserved as change intent. |
+| `openspec/changes/<id>/design.md` | `specs/changes/<id>/design.md` or `DESIGN.md` | Use root `DESIGN.md` for active frontend design contract. |
+| accepted OpenSpec scope/design | `specs/changes/<id>/plan.md` | Canonical reusable xflow implementation plan. |
+| `openspec/changes/<id>/tasks.md` | `specs/changes/<id>/tasks.md` | Optional working checklist; xflow:plan writes `plan.md` as the canonical plan. |
+| `openspec/changes/<id>/specs/` | `merge-product.md`, `merge-architecture.md`, `merge-workflow.md` | Archive-ready spec snippets. |
+
+## Spec Delta Review
+
+Run:
+
+```bash
+xflow spec delta --project-root . --change-id <id>
+```
+
+Output:
+
+```text
+specs/changes/<id>/spec_delta_review.json
+specs/changes/<id>/spec_delta_review.md
+```
+
+The review summarizes:
+
+- proposal headings and intent bullets
+- plan sections and verification commands
+- task counts and completed task counts
+- merge spec snippets that will affect durable root specs
+- warnings such as missing verification commands or missing merge spec snippets
+
+## Migration Strategy
+
+1. Run `xflow init --project-root .`.
+2. Run `xflow spec openspec-map --project-root . --openspec-root openspec`.
+3. Review `.as-xflow/openspec-migration.json`.
+4. Copy durable OpenSpec specs into `specs/` only after human review.
+5. Copy active OpenSpec changes into `specs/changes/<change-id>/`.
+6. Run `xflow spec quick "<change title>"` for the fastest scaffold, or `xflow spec start --title "<change title>" --change-id <change-id>` when you need tighter control.
+7. Run `xflow spec delta --change-id <change-id>`.
+8. Run `xflow workflow validate yolo --project-root .`.
+9. Use `xflow:yolo` or `xflow:corps` for execution.
+
+## What Not To Migrate Blindly
+
+- Do not overwrite existing `specs/*.md` without reviewing durable conflicts.
+- Do not turn every OpenSpec task checklist into the canonical xflow plan; `plan.md` remains the reusable implementation plan.
+- Do not skip TDD proof. OpenSpec specs explain intent; xflow proof verifies behavior.
+- Do not bypass archive. Durable spec deltas should land through the archive boundary.
+
+## Why This Beats A Pure OpenSpec Flow
+
+OpenSpec is excellent at making intent explicit before implementation. evalid keeps that benefit and adds:
+
+- executable workflow validation
+- deterministic spec delta review artifacts
+- red/green TDD proof
+- test-quality proof
+- archive ordering and PR publish boundary
+- release-pack verification

package/docs/public-benchmark.md

@@ -0,0 +1,68 @@
+# Public Benchmark And Demo
+
+This benchmark is the public, repeatable proof path for claims against OpenSpec, gstack, spec-kit, and prompt-only skill systems.
+
+## Demo Scenario
+
+A tracker item arrives from an external system. `evalid` imports the source context, turns it into local change artifacts, reviews spec deltas, and proves the release surface before any public claim or package publish.
+
+## Commands
+
+```bash
+xflow init --project-root .
+xflow spec start --title "release proof adapter" --change-type backend
+xflow objective --json
+xflow assess --json
+xflow demo launch --json
+xflow launch dossier
+xflow launch claims --json
+xflow launch copy --json
+xflow goal audit --json
+xflow corps --explain --json
+xflow adoption trial --name <team-or-project> --source <tracker-or-pr> --track yolo
+xflow launch audit --strict --json
+xflow doctor --project-root .
+xflow adapter import-file --project-root . --input docs/fixtures/tracker-item.json --json
+xflow spec delta --change-id release-proof-adapter
+xflow compare codex-goal
+xflow compare gstack
+xflow compare superpowers
+xflow compare super-assistant
+xflow compare openspec
+xflow compare spec-kit
+xflow score
+npm run publish:check
+xflow package preflight --check-registry --check-auth --json
+xflow launch audit --pre-publish --strict --json
+```
+
+## Expected Artifacts
+
+| Artifact | Meaning |
+| --- | --- |
+| `.as-xflow/config.json` | Project-local workflow defaults. |
+| `specs/changes/release-proof-adapter/proposal.md` | Imported tracker context, now owned by repo-local xflow artifacts. |
+| `specs/changes/release-proof-adapter/status.json` | Draft workflow state and adapter provenance. |
+| `specs/changes/release-proof-adapter/spec_delta_review.json` | Requirements-level spec delta review. |
+| `npm pack --dry-run` output | Package whitelist proof. |
+
+## Scoring Method
+
+| Dimension | Passing Evidence |
+| --- | --- |
+| Local engineering closure | `xflow workflow validate yolo`, `xflow workflow validate corps`, archive atoms, release pack. |
+| TDD quality pressure | `I6a.tdd.run`, `I6b.tdd.proof_validate`, `I6c.tdd.quality_review`, and `test/tdd-proof.test.js`. |
+| gstack comparison | `docs/gstack-comparison.md` and `xflow compare gstack --json`. |
+| Superpowers comparison | `docs/superpowers-comparison.md` and `xflow compare superpowers --json`. |
+| Super-Assistant comparison | `docs/super-assistant-comparison.md` and `xflow compare super-assistant --json`. |
+| OpenSpec migration | `xflow spec openspec-map`, `docs/openspec-migration.md`, and `xflow spec delta`. |
+| Spec authoring flow | `xflow spec start`, `docs/openspec-migration.md`, and generated `specs/changes/<id>/` artifacts. |
+| spec-kit comparison | `docs/spec-kit-benchmark.md`, `docs/integrations.md`, and `xflow compare spec-kit --json`. |
+| Public product readiness | README badges, `RELEASE_NOTES.md`, `docs/fixtures/tracker-item.json`, package whitelist, `npm run publish:check`, `xflow package status --json`, `xflow package preflight --check-registry --check-auth --json`, and `xflow package audit --check-registry --json`. |
+| Quality assessment | `xflow assess --json`, `docs/quality-assessment.md`, `docs/goal-vs-codex.md`, `xflow compare codex-goal --json`, `xflow goal audit --json`, and `xflow score --json`. |
+| Launch demo | `xflow demo launch --json`, `xflow corps --explain --json`, `xflow launch dossier`, `docs/launch-demo.md`, `docs/launch-dossier.md`, `docs/examples-gallery.md`, `docs/corps-operator-guide.md`, and goal-to-yolo / goal-to-corps proof paths. |
+| Launch readiness | `xflow evaluate --json` with `splash_launch` and `splash_claims`, `xflow goal audit --json`, `xflow launch claims --json`, `xflow launch claims --splash --json`, `xflow launch copy --json`, `xflow launch copy --splash --json`, `xflow launch audit --pre-publish --strict --json`, `xflow launch audit --strict --json`, `xflow launch audit --splash --strict --json`, `xflow adoption status --json`, `xflow adoption trial`, `xflow adoption validate --json`, `xflow adoption validate --splash --json`, `xflow package status --json`, `xflow package preflight --check-registry --check-auth --json`, `xflow package audit --check-registry --json`, `docs/public-release.md`, `docs/npm-publish-handoff.md`, `docs/adoption/README.md`, `docs/adoption/openflow-release-hardening.md`, and explicit missing registry proof. |
+
+## Current Result
+
+`evalid` is designed to win the local delivery and verification benchmark because every superiority claim is backed by a runnable command or checked file. Public ecosystem breadth still needs third-party adoption, but the repo now ships the adapter seam, adoption validator, fixture-backed smoke path, and a non-fixture maintainer release-hardening adoption record.