feat(e2e): batch cases across Harbor tasks - #1279
Draft
PsiACE wants to merge 1 commit into
Draft
Conversation
PsiACE
force-pushed
the
codex/shared-harbor-e2e-batches
branch
from
August 20, 2026 09:06
7ee18e8 to
c7afdd9
Compare
PsiACE
force-pushed
the
codex/shared-harbor-e2e-batches
branch
from
August 20, 2026 13:21
c7afdd9 to
58af689
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.
Which issue or RFC does this PR close?
N/A — no issue or RFC is linked.
Rationale for this change
Allow compatible Harbor cases to run in shared batches while keeping each case’s PowerContext scope, workspace, and evidence isolated.
What changes are included in this PR?
Are there any user-facing changes?
No direct runtime API changes. This primarily improves developer-facing E2E evaluation workflows and documentation.
How was this change tested?
Adds coverage for batch evidence, scope isolation, evidence redaction, workload catalogs, and acceptance behavior.
AI usage statement
Codex (GPT-5) was used to inspect the branch and prepare this PR description.