Cross-checked all four markdown files against the live GitHub issue list (33 closed, 24 open). Significant drift had accumulated since the last sweep — Tier 1-9 work (#33/#34/#35/#36/#37 already in code, plus everything from this session) wasn't reflected anywhere. README.md: - Status section (lines 686-695) listed five long-closed issues (#33-#37) as "big roadmap items still open". Replaced with the actual remaining open items (#26 docs site, #27 perf benchmarks, #4/#5 gRPC polish, #54 Akka-Streams DSL) plus a one-paragraph summary of what landed recently. - Two more `~1486 tests` references caught (lines 580, 682) — bumped to 1487. The auto-update workflow's regex matches these, but they were stale because CI was failing on the pubsub flake; they'd self-correct on the next green push but fixing now keeps the README honest. - "60+ runnable examples" → "75+" (actual count is 76). - "More examples" table extended with 11 new examples covering Tier 6-9 work: schema-registry, migrate-legacy-events, replicated-counter, projection-bank-statement, websocket-server, kafka-exactly-once, jetstream-orders, prometheus-endpoint, opentelemetry-tracing, backoff-supervisor, order-workflow, shopping-cart-orset. ROADMAP.md: - "Likely next" no longer lists 4 closed items (#2/#1/#3/#8). Reorganised: docs site + perf benchmarks promoted from "Want, but bigger" since they're the only medium-priority items left; gRPC polish (#4/#5) below. - "Want, but bigger" no longer lists 5 closed items (#6/#7/#9/ #10/#11). Added #54 (Akka-Streams), #44 (Cassandra tag side-table), #47 (MultiNodeSpec barrier), #56 (extended cluster-management endpoints) — open issues that weren't previously surfaced. - "Maybe (demand-driven)" — now includes the live-integration issue numbers explicitly (#20-#24) and tagged ZeroMQ (#15) / STOMP (#16) / etc with their issue refs. - "Known issues" — removed #17 (closed) and the zstd peer-dep entry (also fixed in code via #18+#59 even though those issues are technically still open in GitHub). Kept #19 (FilesystemObjectStorageBackend ETag map) — still genuinely out of scope. CHANGELOG.md: - New 0.6.0 — 2026-04-30 entry covering everything since 0.5.0. Six "Added" subsections grouped by theme: multi-node testing + sharding hardening; persistence performance + projections; additional CRDTs + persistent FSM + DX patterns; observability stack; schema migration & encryption polish; production-grade brokers & WS server-side. Plus a "Fixed" section for the pubsub eager-broadcast fix and the Tier 4 correctness batch. benchmarks/README.md: - No changes — content is benchmark-suite-specific and doesn't drift with framework feature work. Note for follow-up: GitHub issues #18, #57, #58, #59 still show as open even though their fixes shipped in the Tier 4 batch commit. The `closes #17, #57, #58, #18, #59` syntax in that commit only auto-closed #17 — GitHub requires each issue to be prefixed with its own keyword (`closes #X, closes #Y, closes #Z`). These four should be closed manually via `gh issue close`. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

STOMP broker actor (demand-driven) #16

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions