docs: add backend-integration-readiness tickets (103-107)#17
Merged
Conversation
Review of whether the engine can be driven cleanly from a long-running service (one process per job) surfaced five gaps that sharpen the contract a queue worker depends on, none blocking single-shot CLI use: - 103 backend-facing exit-code table + catch-all -> 13 on validate/sora/calibrate - 104 atomic --output writes (temp + os.replace) + SIGTERM cancellation code - 105 schema-versions command to discover contract versions without a run - 106 machine-readable JSONL progress for propagate/sample/batch (extends 067) - 107 JSON --validate-only preflight envelope + GeoJSON asset preflight (with 089) Docs-only; no code or fixtures changed. ruff clean.
Monotox
changed the title
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
1 participant
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.
Summary
Review of whether the engine can be driven cleanly from a long-running service (one process per job) surfaced five gaps that sharpen the contract a queue worker depends on, none blocking single-shot CLI use.
Test Plan
uv run pytestpassesuv run ruff check .passesContract Impact
docs/VERSIONING_POLICY.md