Repository navigation
Conversation
An Orca scout teardown, or any Orca teardown run with --force, skipped the early Orca path-match check and only re-verified it after reap_task_worktree_processes had already run against the recorded worktree path, so a stale or reassigned Orca worktree id could have its processes signalled before ownership was ever proven. Fold the Orca proof into require_owned_task_worktree_slot, the same early, single-owner ownership determination the treehouse pool-slot claim already uses, so it runs once, well before Fix 1/Fix 2, for every kind and --force alike, instead of being re-checked ad hoc at each later call site.
…PATH sanitization
…all destructive steps
MLA82
force-pushed
the
fm/werft-pr3723-ersatz
branch
from
September 20, 2026 17:18
6b27cbd to
e2eeed0
Compare
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.
Internal verification run only. This pull request exists solely so the inherited CI runs against this branch inside our own fork, where no workflow approval is required.
It is not intended to be merged. The corresponding upstream proposal is kunchenguid#4838, which replaces the earlier kunchenguid#3723.
The mandatory no-mistakes gate is expected to be red here: the attestation is bound to the upstream head, not to this internal pull request. That gate is a separate step and is not what this run is testing.