feat(protocol): publish protocol v1 schemas, golden vectors, and conformance runner

[CompleteDotTech]

Summary

Publishes the consumer-ready Psyche protocol v1 release surface required by OpenCoven#11, on top of the G2 foundation:

• protocol/v1/ — generated, checksummed artifact set. Self-contained JSON Schema (draft 2020-12) for all sixteen registry kinds (psyche.identity_snapshot.v1 … psyche.error.v1), the Coven boundary types (psyche.execution_request.v1 launch/input, result bundle), and the store-owned transition; a generated TypeScript surface; byte-exact canonical JSON golden vectors with pinned SHA-256 digests; a machine-readable inventory with stability classes (stable-v1 / experimental / internal / deprecated); and a sha256sum-format MANIFEST.sha256 for downstream pinning.
• Golden vectors cover every fixture class Publish Psyche protocol v1 schemas, golden vectors, and conformance runner OpenCoven/psyche#11 requires: positive, structured denial, stale-correlation (ack outside window, expired request window, evidence session mismatch), unknown-version (psyche.intent.v2), crash/restart (append-only revision chain whose revision 2 binds previous_revision_digest to revision 1's canonical bytes, plus a broken-chain profile-rejection), and downgrade (fail closed on an unsupported major).
• packages/psyche-protocol/ — standalone conformance runner (psyche-conformance). Zero dependencies, no network, no credentials, bounded machine-readable output. Implements the consumer-v1 profile: negotiation, session/execution correlation, snapshot/attempt binding, adoption proof, ambiguity/fencing shape, cursor/restart, terminal-authority shape, the full cancellation evidence matrix (ported from ExecutionBinding::validate_cancellation), result/artifact binding (ported from ResultBundle::validate), append-only revision chains and frozen fields (ported from validate_revision_chain), structured-denial/quarantine classification (RejectionReason vocabulary), and the canonical JSON domain.
• scripts/protocol/ — single source of truth + deterministic generator. node scripts/protocol/generate.mjs rewrites the artifact tree byte-identically; a new CI job re-runs it and fails on any uncommitted drift (schemas, fixtures, generated TypeScript).
• crates/psyche-core/tests/protocol_golden.rs cross-checks every registry golden vector through the real decoder and byte-compares canonical_bytes against the published files — schema↔decoder drift is caught in both directions.
• docs/PROTOCOL.md — the compatibility policy: semantic versioning of the artifact set, compatibility windows, unknown-field/enum/kind/major fail-closed behavior, migration/downgrade/rollback, deprecation, the conformance profile mapping, and decision records with alternatives.

Canonicalization is RFC 8785. The JavaScript canonicalizer is pinned to byte parity against Rust-produced digests this repo's own CI already verifies: sha256:75d651c5… / sha256:c8c3d0ca… (execution request goldens) and both decoder-recomputed effect_digest values. The execution-request golden vectors are byte copies of the Rust fixtures, so their file digests are the pinned request digests.

Issue

Refs OpenCoven#11

Test plan

• node scripts/protocol/generate.mjs --check — artifact drift clean (56 files)
• npm --prefix packages/psyche-protocol test — 30/30 node:test unit tests (canonicalizer byte-parity vs Rust goldens, schema validator, full cancellation/revision/binding/negotiation matrix, CLI end-to-end + tamper detection)
• psyche-conformance run --root protocol/v1 — 33/33 vectors pass, exit 0; tampered copies exit 2
• psyche-conformance verify --root protocol/v1 — 55 files + 33 vectors verified, exit 0
• cargo fmt --all -- --check — clean (pinned 1.88.0 toolchain)
• cargo test -p psyche-core --test protocol_golden and the full CI rust matrix — compile proof deferred to CI (no local linker)
• New protocol CI job green (generate/drift, runner tests, conformance, manifest verification)

Vehicle note: opened in the fork CompleteDotTech/psyche as the CI vehicle — this token cannot write to OpenCoven/psyche. Re-target upstream once write access is restored. Refs OpenCoven#11.

[CompleteDotTech]

CI status on this fork vehicle — verdict and one unrelated failure

Green (every run): Protocol artifacts (Node 22) (generate/drift gate, runner unit tests, conformance over 33 vectors, manifest verification), npm distribution ×2, Secret guard, Dependency audit, and on the rust legs: Format, Clippy, Tests, G2 state machine, G2 reusable conformance, G2 migrations, G2 crash recovery, G2 fault-injection clippy, G2 evidence checker unit tests.

Fix cycles applied to this PR (3 of 4):

1. protocol_golden.rs ran the registry decoder over the store-owned transition vector; restructured so store-owned vectors assert decoder denial and registry vectors decode + re-canonicalize.
2. Separated IdExpectation::NotPersistable (psyche.error.v1 decodes but never persists) from IdExpectation::NotADocument (psyche.transition is not a registry document).
3. Re-pinned REVIEWED_WORKFLOW_SHA256 in scripts/check-g2-evidence.py for the reviewed addition of the protocol job (the checker hashes the complete CI workflow; no G2 command, trigger, env, or job shape changed — all still verified structurally).

Two failures that are NOT caused by this PR:

1. G2 evidence relationships — fails with G2 evidence check failed: GitHub Actions repository provenance is invalid on all three OS legs. scripts/check-g2-evidence.py::verify_actions_source_relationship requires the CI event's repository.full_name (and PR head repo) to be exactly OpenCoven/psyche — a deliberate upstream-provenance gate. On the fork CompleteDotTech/psyche this step cannot pass by construction, independent of the change contents. It will pass when this PR is re-targeted upstream; everything it depends on (hash pin, structural checks, evidence relationships logic) is verified green around it, and the unit-level mutation suite (G2 evidence checker unit tests) passes.

2. One transient windows failure of concurrent_first_open_applies_migration_once (crates/psyche-store/tests/migrations.rs:556) — a pre-existing store concurrency test this PR does not touch (no psyche-store source change in the diff). It passed on job re-run; recorded here as a flake observation.

Per the CI contract this PR therefore stays draft: it is green except a step that is structurally impossible on the fork vehicle. Re-target upstream (restore write access to OpenCoven/psyche) and the full matrix should be green as-is — no content change expected.

Refs OpenCoven#11