Expand public job APIs and harden scoped reads and execution services - #14
Merged
Merged
Conversation
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.
Producers and workers can now share job specifications and typed payload contracts, while operational callers can select explicit global, tenant, or administrative read scopes. Handlers gain deadline budgets and fenced progress/checkpoint services; compact summary pagination, enqueue outcomes, migration identity, and fluent DAG helpers round out the public API additions.
The branch also preserves index access for scoped reads, validates durable progress atomically, reduces redundant progress locking and workflow persistence statements, and bounds test database startup. The README and changelog document compatibility changes and the required pagination migration, including its queue-write blocking deployment window.
Validation on PostgreSQL 18.6:
Detailed research, measurements, and validation limitations are recorded in
docs/review-hot-path-fixes-2026-09-05.md. Downstream application suites were not rerun. Broader run-ID indexing and consumer-adoption investigations remain tracked separately in Beads.Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.