Publish store connector conformance specification

[djgrant]

What changed

• publish @yieldstar/store-conformance with a factory-only Vitest registration API
• define base, shared-client, and durable-restart qualification capabilities
• specify CAS, exactly-once receipt, updater replay, waiter coordination, and at-least-once wake delivery requirements
• run the extracted artifact unchanged against memory, bun:sqlite, and node:sqlite in the existing CI matrix

Why

The conformance suite previously lived inside the integration-test workspace, mixed portable contract assertions with implementation-specific assumptions, and did not define the crash boundary for wake delivery. Third-party connector authors could not consume or qualify against it.

The specification makes wake intent atomic with mutation or stale registration, requires retry and durable recovery for persistent backends, and explicitly permits duplicate delivery after a crash. A transactional outbox remains a recommended implementation rather than a protocol requirement.

Impact

Connector authors can install one published package and register the suite with a backend factory. Optional createPeer and restart factory methods activate capability-specific race and recovery checks. Async remote drivers such as Turso and batch-only backends such as D1 remain future extensions.

Validation

• bun run bundle
• bun run test:bun — 113 passed, 1 skipped
• pnpm run test:node — 113 passed, 1 skipped
• bun run test:store-conformance-package — packed external install, 20 passed
• package dry-run verified README, manifest, JavaScript, and declaration contents