Repository navigation
codegen-orchestrator-1712: Isolate live-owner lookup in workspace lock units - #852
Merged
Merged
Conversation
…kup seam The fixture let competing creates reach the real control API, so refusals proved API unavailability and the exhaustive sweep case exceeded the unit budget. Each manager now answers the owner lookup with in_progress and the refusals assert the live-owner message with the owner worker and story.
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.
What
Candidate commit eab5faa (tree 9847fe273971507eba4b5ddbe186c6d8083c7ab1), based on main 063c55e. Test-isolation hotfix only; no runtime, lock, sweep, checkout or publication code changed.
Why
Repair the existing workspace-lock unit fixture so it proves live-owner refusal and sweep/acquisition exclusion without contacting the control API. This is a mandatory narrow hotfix after sprint1496's1711 postmerge CI failure; feature continuation waits for a trustworthy integration base.
How verified
CI runs
Backend Docker-in-Docker Integration Tests,Build Service Image Candidates,Build Worker Base Image Candidates,CI Contract,Detect Changed Services,Fast Checks (Unit Tests),Lint (Ruff),Publish Service Image Release,Publish Worker Base Images,Required CI Gate,Service Image Entrypoint Importsoneab5faa8a482; the merge waits for them to pass.Card:
codegen-orchestrator-1712