Repository navigation
Fix: Enforce worker execution limits and preserve research lifecycle evidence - #13
Merged
Merged
Conversation
…arvester prefix collisions
…hor harvester prefix
…ary tests portable
…isolate dispatch env
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.
Fix cloud workers reporting success before verification or artifact delivery succeeds. Verification runs even without source changes, provider requests and shell commands have finite budgets, and failed work retains diagnostics and safe evidence.
Limits come from task manifests or explicit environment variables, then defaults. The extra CLI and runtime-JSON limit configuration has been removed. Artifact uploads share path and credential checks, reject unsafe patch destinations before writing, and publish final status after delivery attempts. Harvesting requires the exact session and complete task coverage.
Regression tests cover provider exhaustion, descendant-process cleanup, no-change verification, credential rejection, upload failure, nested byte-preserving transport, and harvest quarantine. Repeated canary cases and scientific package fixtures are outside this worker repair. The generated-package tests are preserved on a separate branch.
Validation: 389 passed, 3 skipped, and 153 subtests passed. The final exit-code assertion passed all eight finalization cases; independent fix review passed 86 tests and direct validation probes. Ruff and git diff --check passed. Deployment and live canary validation remain separate work.