docs: update roadmap status table

[NikolayS]

Summary

• mark Improved send_batch performance as done in the README roadmap

Details

Updated the README roadmap table to reflect current repo reality:

• Improved send_batch performance → ✅

Other roadmap rows remain unchanged until their status/evidence is reviewed separately.

Verification

• reviewed the README-only diff against the current implementation/docs
• GitHub CI is green (14/14)

[NikolayS]

REV Code Review Report

• PR: NikolayS/PgQue#241 — docs: update roadmap status table
• Author: @NikolayS
• Branch: docs/roadmap-status-fixes
• CI: ✅ success (all 14 checks pass)

This is README-only and the CI matrix is green. I checked the changed roadmap rows against the current tree (docs/reference.md, docs/upgrading.md, sql/pgque.sql, sql/pgque-additions/*, sql/experimental/*). Most changed rows are backed by source/docs: send_batch fast path, experimental observability/OTel rows, delayed delivery, config API, and pause/resume all have corresponding implementations/docs.

---

BLOCKING (1)

MEDIUM README.md:515-530 — roadmap update is incomplete / contradicts the PR description

The PR description says this marks already-shipped roadmap items done, including:

• System-table rotation / bloat mitigation
• LISTEN/NOTIFY consumer wakeups on tick
• Cross-database pg_cron scheduling
• Migration guides

But the actual diff leaves all four rows blank. The current tree has evidence for these rows:

• rotation/bloat mitigation: hot-path three-table rotation is documented in README.md architecture text and implemented via rotation maintenance;
• LISTEN/NOTIFY wakeups: pg_notify('pgque_' || queue, ...) is in sql/pgque.sql / sql/pgque-tle.sql, with docs in docs/three-latencies.md and docs/reference.md;
• cross-database pg_cron scheduling: lifecycle uses cron.schedule_in_database(...) in sql/pgque-additions/lifecycle.sql and generated SQL;
• migration guides: docs/upgrading.md is linked from README/docs and fix: support v0.1.0 upgrade path #238 added the v0.1.0→HEAD upgrade CI gate.

Since the PR's purpose is roadmap correctness, leaving these rows blank keeps the table materially stale.

Suggestion: Update the table for those rows (likely ✅), or narrow the PR description and explain why each is intentionally still blank.

---

NON-BLOCKING (1)

LOW README.md:524 — "OpenTelemetry SQL metrics export" is clearer than the old Prometheus claim

This rename is good: pgque.otel_metrics() returns OTel-compatible metric rows, not a Prometheus endpoint/exporter. No action needed.

---

Summary

Area	Findings	Potential	Filtered
CI	0	—	—
Security	0	0	0
Bugs	0	0	0
Docs	1	0	0

Blocked on completing/reconciling the roadmap rows above.

---

REV-assisted review (AI analysis by postgres-ai/rev)

[NikolayS]

Re-review after c94d509: PR is now narrowed to the one supported roadmap change (Improved send_batch performance → ✅), and the PR description has been updated to match.

Verification: git diff --check passed locally; GitHub CI is green (14/14) on head c94d509. No remaining blocker from my side.