docs: record the wake-up adapter and require roadmap updates - #15
Merged
Conversation
Milestone 2 shipped without the roadmap being updated, so it still described PostgreSQL notifications as unimplemented and the cross-process polling delay as unaddressed. Record the adapter, its measured latency, why it is opt-in rather than automatic, and that MySQL has no notification primitive. Milestone 2 now covers only the remaining Redis adapter.
Greptile SummaryThe roadmap now records the shipped opt-in PostgreSQL
Confidence Score: 5/5The documentation-only PR appears safe to merge. The updated roadmap claims are consistent with the adapter implementation, integration coverage, benchmark documentation, and current backend behavior. Important Files Changed
Reviews (1): Last reviewed commit: "docs: record the PostgreSQL wake-up adap..." | Re-trigger Greptile |
Two releases shipped milestones without the roadmap following, leaving it claiming that implemented capabilities were missing. Make the update part of the pull request that changes what the project claims about itself, and say plainly that correcting a stale entry matters more than appending a new one.
This was referenced Aug 10, 2026
This was referenced Aug 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Milestone 2 shipped in #14 without the roadmap being updated, so it still claimed PostgreSQL
LISTEN/NOTIFYwas not implemented and described the cross-process polling delay as the largest unaddressed latency term.This is the second time a release landed without the roadmap following, so this PR fixes both the stale content and the process that let it go stale.
Roadmap
LISTENnot surviving a transaction-pooling proxyAGENTS.md
Requires
docs/roadmap.mdto be updated in the same pull request whenever a change alters what the project claims about itself: completing or advancing a milestone, moving an entry between implemented and partially implemented, or discovering a limitation worth recording such as a capability that turns out to be opt-in, adapter-specific, or measured rather than assumed.Two points made explicit, because both were the actual failure modes here: prefer correcting a stale entry over only appending a new one, since an inaccurate claim misleads more than a missing one; and state what was measured and what was not, so a reader can tell evidence from intent. Defect fixes, tooling, and prose changes are exempt.
Documentation only. No version bump.