chore(release): v0.20.0

[relsunkaev]

Publishes the Effect v4 work as stable zerover 0.20.0. Nine files changed; all local release gates pass. Merge this PR, then push the existing annotated tag to publish.

Why

The project remains work in progress, so its public package version should stay on the zerover line even though it currently targets Effect v4 beta.98.

• npm latest is still 0.19.0.
• The verified Effect v4 package line is currently published only as 4.0.0-beta.98.
• Consumers need a normal latest release without pretending Effect itself is stable.

Key Changes

Stable package version:

• Set effect-qb, effect-db, the workspace, and the database CLI to 0.20.0.
• Keep Effect and every Effect platform/SQL package pinned to 4.0.0-beta.98.
• Generate cumulative stable release notes from all 62 commits since v0.19.0.

Release boundary correctness:

• Stable releases now compare against the latest stable tag instead of the nearest prerelease tag.
• Prereleases continue from the latest tag on the same version line, then fall back to the latest stable tag.
• Regression coverage proves both stable and prerelease boundary selection.

Breaking changes included:

• Renderer construction no longer accepts the removed casing option.
• Table options require callbacks.
• JSON traversal, casting, dialect helpers, and transaction helpers use the Effect v4 APIs documented in the changelog.

Risks & Testing Needed

Effect dependency: the packages remain coupled to effect@4.0.0-beta.98.
→ Review package metadata to confirm no Effect dependency was promoted or widened.

Stable changelog: this release crosses from the beta channel back to zerover.
→ Review the 0.20.0 section as the cumulative delta from v0.19.0, including all seven breaking changes.

Publish trigger: the annotated tag exists locally but has not been pushed.
→ Merge first; push v0.20.0 only after the release commit is reachable from main.

Not tested:

• Registry installation cannot be tested until the immutable 0.20.0 packages are published.

Build status: all local gates pass; protected-branch CI is pending.

Test Plan

bun install --frozen-lockfile
bun run build
bun test
bun run test:types
bunx npm pack --dry-run
bun run test:pack
bun run test:integration
bun run test:integration:datatypes

Expected package metadata:

effect-qb: 0.20.0, peer effect: 4.0.0-beta.98
effect-db: 0.20.0, peer effect: 4.0.0-beta.98
npm tag after publish: latest

Rollback

git revert 6178b33 381c314 ef00b31

Rollback restores the beta.98 package metadata and prior release-boundary behavior. Published npm versions are immutable, so a post-publication rollback requires a new zerover patch rather than moving 0.20.0.