feat: prove first-run and recovery paths

Author: cardmagic

.github/workflows/ci.yml

@@ -23,6 +23,8 @@ jobs:
       - run: pnpm run test:coverage
       - run: pnpm run build
       - run: pnpm run pack:check
+      - run: pnpm run test:package
+      - run: pnpm run test:recovery
       - run: pnpm audit --audit-level=high
 
   postgresql:

CHANGELOG.md

@@ -4,6 +4,16 @@
 
 ## 0.13.0 - 2026-08-15
 
+- Replace the exhaustive README with an outcome-first introduction, explicit
+  fit and correctness boundaries, sourced comparisons, and factual design
+  provenance.
+- Add a packaged SQLite quickstart, a clean-install tarball smoke test, and a
+  deterministic multi-process crash and fencing demonstration.
+- Add a reproducible benchmark harness, record locally observed SQLite,
+  PostgreSQL 18, and MySQL 8.4 measurements, and label other configurations as
+  unmeasured.
+- Add support, contribution, and security policies plus stronger local
+  Markdown link validation.
 - **Breaking:** make unwrapped observables invalidation-only by default. They
   continue to detect changes and refresh dependent components without storing
   or sending their values. Wrap a projection in `broadcastValue()` to share

CONTRIBUTING.md

@@ -0,0 +1,46 @@
+# Contributing
+
+Solid Objects changes can affect durable state and recovery. A contribution
+should explain the invariant it changes and include a regression test at the
+lowest layer that can prove it.
+
+## Setup
+
+Install Node.js 24.15 or newer, enable Corepack, and install the locked
+dependencies:
+
+```bash
+corepack enable
+pnpm install --frozen-lockfile
+```
+
+## Validation
+
+Run the local quality gates before opening a pull request:
+
+```bash
+pnpm run format:check
+pnpm run check
+pnpm run test:coverage
+pnpm run build
+pnpm run pack:check
+pnpm run test:package
+pnpm run test:recovery
+```
+
+Run `pnpm run test:browser` after installing Playwright Chromium. The database
+and wake-up suites use these variables:
+
+- `SOLID_OBJECTS_DATABASE_URL` for PostgreSQL or MySQL integration tests;
+- `SOLID_OBJECTS_REDIS_URL` for the optional Redis wake-up suite.
+
+Use disposable databases. Do not include credentials, production data,
+customer identifiers, or other personal information in fixtures or reports.
+
+## Correctness changes
+
+For mailbox, lease, fencing, retry, effect, reminder, or migration changes,
+include the failure sequence the test exercises. Prefer deterministic clocks,
+explicit process coordination, and durable assertions over sleeps or mock-only
+proof. Update [Correctness and delivery semantics](docs/correctness.md) when a
+guarantee or limitation changes.