docs: refresh README and CLAUDE.md after recent worker/store updates

[myzie]

Summary

• Refresh README.md and CLAUDE.md to reflect the changes that landed in 002 phase 1.1+1.2: Claim carries WorkerID; fencing calls take *Claim #37, feat: richer NewRun/Claim, HandlerContext, Run API, configurable schema #38, and fix: PR #38 follow-ups — upgrade path, DeleteRun race, runquery lift #39.
• Lighter, more approachable tone — especially in README.md.
• Drops the "Going to production" framing in favor of a friendlier "Bring your own storage" section that still lays out the interface story.

What's reflected

• Claim now carries WorkerID, ProjectID, ParentRunID, InitiatedBy, and Metadata.
• *HandlerContext with the only-Checkpointer-is-lease-fenced caveat; SignalStore lives on Config.
• New experimental/worker/runquery/ subpackage as the backend-neutral run query API.
• Postgres WithSchema(...) for configurable schema namespace, with Migrate issuing CREATE SCHEMA IF NOT EXISTS.
• Atomic DeleteRun that refuses running runs.
• v0.0.3 → v0.0.4 single-tenant upgrade carry-forward (empty org_id/initiated_by rewritten to NULL).
• SQLite coexistence note (no schema namespacing — pass a dedicated *sql.DB).
• Postgres read-side Run API (GetRun, ListRuns, CountRuns, DeleteRun).

Test plan

• Skim the rendered README on the PR page to confirm tone and links land
• Verify referenced doc paths still exist (docs/worker.md, docs/postgres.md, docs/suspension.md, documentation/, examples/signal_wait, examples/durable_sleep, examples/pause_unpause)

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Clarified library positioning as a pure in-process execution engine for multi-step workflows with suspend/resume capability
  • Emphasized storage, queues, and infrastructure are consumer responsibilities
  • Expanded descriptions of experimental worker, postgres store, and sqlite store modules
  • Refined guidance comparing Runner (convenience wrapper) vs Execute (direct execution)

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 410aabc3-1bf7-452e-b24c-f9b3555bc4d3

📥 Commits

Reviewing files that changed from the base of the PR and between 8d39f63 and 2a29a65.

📒 Files selected for processing (2)

• CLAUDE.md
• README.md

---

📝 Walkthrough

Walkthrough

Documentation updates reframing the library as a pure in-process execution engine, clarifying consumer responsibilities for external storage/infrastructure implementation, and expanding descriptions of experimental submodules including new runquery APIs and storage implementations.

Changes

Cohort / File(s)	Summary
Documentation Repositioning CLAUDE.md	Reframed library as in-process execution engine; clarified consumer-supplied storage/infra patterns; revised experimental module descriptions (worker handler API, lease-fencing semantics); added experimental/worker/runquery/ submodule section; expanded experimental/store/postgres/ and experimental/store/sqlite/ details including pagination, migration behavior, and schema requirements.
README Execution Model Clarification README.md	Updated execution engine positioning and "ability to suspend and resume" language; reframed Runner as convenience wrapper rather than production requirement; replaced "Going to production" section with "Bring your own storage" guidance; added experimental submodule capability descriptions (claim/credit reconciliation, runquery APIs); reorganized reference links.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• docs: update CLAUDE.md and README.md for post-v1 accuracy #36 — Concurrent documentation-only updates to CLAUDE.md and README.md covering overlapping experimental submodule and interface descriptions (SignalStore, worker/postgres/sqlite positioning).

Poem

🐰 A rabbit's ode to clearer docs,
Where execution flows like garden stocks—
In-process pure, let consumers own,
The storage seeds they're free to sown! 🌱

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/post-pr39-refresh

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}