[relsunkaev]

Prepare effect-qb and effect-db 0.24.2. Six files; local gates pass. After merge, publish the exact merged SHA through the guarded Publish workflow.

Why

Problem: the released packages do not yet contain the table typing repairs or the Effect compatibility fixes now on main.

• Keep both packages on the 0.x line.
• Release the fixes and updated documentation without claiming all mixed-selector inference is repaired.

Key Changes

Version alignment:

• Set both package versions, the workspace version, and CLI version to 0.24.2.
• Update only the matching workspace versions in the lockfile.
• Use the repository's native release-preparation script; no tag is created during preparation.

Release notes:

• Summarize table-option, JSON/CASE/MATCH metadata, partial-index, and source-discovery fixes since 0.24.1.
• Include the reorganized documentation and implementation ownership work.
• State the Effect >=4.0.0 <4.1.0 compatibility range and remaining implicit mixed-selector limitation.
• Replace the generated commit inventory with reader-facing notes.

Risks & Testing Needed

Requirement: publication must use the merged release commit, not the branch SHA.
→ Dispatch Publish with that exact commit and v0.24.2; its existing guards verify versions, notes, ancestry, and immutable tags.

Requirement: both registry packages and their fresh consumers must work.
→ Verify npm latest versions, artifact integrity, provenance, CLI version, package imports, and native Node SQLite after publication.

Not tested yet:

• The new registry artifacts do not exist until Publish completes.
• Effect 4.1 compatibility remains intentionally unsupported.

Build status: types (including 56 generated README groups), 741 tests / 80 snapshots, build, and packed consumer tests pass locally.

Test Plan

bun install --frozen-lockfile
bun run test:types
bun test --coverage
bun run build
bun run test:pack

All seven existing CI jobs must pass before merge, including Node 22/24/26 package and database-integration checks.

Rollback

Before publication, revert this merge commit with git revert -m 1 <merge-commit>.

After publication, never move the tag or overwrite npm artifacts; ship a new corrective patch if needed.