Instruction: Fix the defect where the upload accepts malformed input after normalization in the cache coordinator. The affected entry point is UploadPolicy49603; keep the change aligned with the existing layered service boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The upload no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

go test ./upload -run UploadRegression49603

Question: UploadPolicy49603|validation_order_defect

Locate the implementation and callers associated with UploadPolicy49603.

Search evidence identifies internal/upload/upload_496_03.go as the narrow implementation boundary.

The implementation boundary and acceptance criterion are now supported by repository evidence.

A successful edit is not established until the narrow regression boundary passes.

Obtain executable evidence for the requested behavior.


Instruction: Review the proposed download change in the cache coordinator for correctness, scope, and regressions. The affected entry point is DownloadPolicy49604; keep the change aligned with the existing layered service boundary.

Preserve the public API
Do not add dependencies
Limit changes to relevant files

The download no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

go test ./download -run DownloadRegression49604

Produce the smallest architecture-aligned patch that satisfies the task.

Summary: A bounded first attempt was applied after inspecting the target implementation.

The targeted test exposes a mismatch between the proposed behavior and the acceptance criterion.

The observed failure invalidates the first assumption; use the concrete signal to narrow the repair.

repair diagnosed cause without broadening scope

A bounded directory view reduces path assumptions without reading the full repository.

Confirm the local module boundary before searching for implementation details.

The task names behavior but repository evidence is required before selecting an edit target.

Locate the implementation and callers associated with DownloadPolicy49604.

Search evidence identifies internal/download/download_496_04.go as the narrow implementation boundary.

Confirm the current control flow, local conventions, and error contract.

The patch should be verified using project-native tests rather than an invented harness.

Identify existing test style and the nearest regression boundary.

Security and review decisions require evidence about authorization and validation order.

Question: authorize|permission|sanitize|validate

Locate the nearest trust-boundary implementation and existing guard pattern.

correct retry-safety defect while preserving the public contract

Apply a localized change that follows existing abstractions.

Diff inspection is required before making a completion claim.

Confirm the final change is bounded and contains no accidental edits.

The original acceptance criterion passes

The failure signal is no longer reproduced

The final report distinguishes executed evidence from assumptions


Instruction: Review the proposed audit change in the cache coordinator for correctness, scope, and regressions. The affected entry point is AuditPolicy49605; keep the change aligned with the existing layered service boundary.

Keep backward compatibility
Add or update a targeted test
Avoid unrelated refactors

The audit no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

go test ./audit -run AuditRegression49605

Ground every decision in repository evidence before editing.

Locate the implementation and callers associated with AuditPolicy49605.

Search evidence identifies internal/audit/audit_496_05.go as the narrow implementation boundary.

The task spans implementation and verification but does not justify an architectural redesign.

confirm behavior
apply bounded patch
run targeted test
inspect diff

Create a short plan with explicit verification and no unrelated work.

correct state-isolation defect while preserving the public contract

The targeted check establishes the fix; the wider suite provides additional regression evidence.

Check for regressions beyond the targeted behavior when the execution budget permits.

Preserve existing interfaces, correct only the evidenced behavior, and add narrow regression coverage.


Instruction: Fix the defect where the worker matches identifiers case-insensitively in the cache coordinator. The affected entry point is WorkerPolicy49606; keep the change aligned with the existing layered service boundary.

Do not expose secrets in logs
Preserve existing configuration keys
Run the narrow test first

The worker no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/worker/test_worker_496_06.ts

Produce the smallest architecture-aligned patch that satisfies the task.

Question: WorkerPolicy49606|identity_comparison_defect

Locate the implementation and callers associated with WorkerPolicy49606.

Search evidence identifies src/worker/worker_496_06.ts as the narrow implementation boundary.

correct identity-comparison defect while preserving the public contract


Instruction: Fix the defect where the scheduler marks partial work as successful in the cache coordinator. The affected entry point is SchedulerPolicy49607; keep the change aligned with the existing layered service boundary.

Keep the patch reviewable
Do not change database schema
Report any unverified assumption

The scheduler no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/scheduler/test_scheduler_496_07.ts

Locate the implementation and callers associated with SchedulerPolicy49607.

Search evidence identifies src/scheduler/scheduler_496_07.ts as the narrow implementation boundary.

correct false-success defect while preserving the public contract


Instruction: Refactor the router in the cache coordinator to remove duplicated serialization logic without changing behavior. The affected entry point is RouterPolicy49608; keep the change aligned with the existing layered service boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The router no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: RouterPolicy49608|least_privilege_defect

correct least-privilege defect while preserving the public contract

Produce the smallest architecture-aligned patch that satisfies the task.


Instruction: Add guarded support for dry-run mode in the metrics of the cache coordinator. The affected entry point is MetricsPolicy49609; keep the change aligned with the existing layered service boundary.

Preserve the public API
Do not add dependencies
Limit changes to relevant files

The metrics no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Choose the lowest-cost valid tool and use schema-correct arguments.

Locate the implementation and callers associated with MetricsPolicy49609.

Search evidence identifies src/metrics/metrics_496_09.php as the narrow implementation boundary.

correct verification defect while preserving the public contract

Hard tasks require caller evidence to control compatibility risk.

Identify callers and contract-sensitive edges before changing multi-file behavior.

Static validation catches interface and error-handling defects not covered by the targeted test.

Check static constraints relevant to the modified code.


Instruction: Review the proposed logging change in the cache coordinator for correctness, scope, and regressions. The affected entry point is LoggingPolicy49610; keep the change aligned with the existing layered service boundary.

Keep backward compatibility
Add or update a targeted test
Avoid unrelated refactors

The logging no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Classify failure evidence, revise the hypothesis, and repair without looping.

Question: LoggingPolicy49610|cache_invalidation_defect

correct cache-invalidation defect while preserving the public contract

Question: authorize|permission|sanitize|validate

revise the failed assumption without expanding scope


Instruction: Review the proposed sandbox change in the cache coordinator for correctness, scope, and regressions. The affected entry point is SandboxPolicy49611; keep the change aligned with the existing layered service boundary.

Do not expose secrets in logs
Preserve existing configuration keys
Run the narrow test first

The sandbox no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests SandboxRegression49611

Question: SandboxPolicy49611|unit_conversion_defect

Locate the implementation and callers associated with SandboxPolicy49611.

Search evidence identifies src/main/java/sandbox/SandboxService496.java as the narrow implementation boundary.

The implementation boundary and acceptance criterion are now supported by repository evidence.

correct unit-conversion defect while preserving the public contract

A successful edit is not established until the narrow regression boundary passes.

Obtain executable evidence for the requested behavior.


Instruction: Add regression coverage for the case where the session performs authorization after the side effect in the cache coordinator. The affected entry point is SessionPolicy49612; keep the change aligned with the existing layered service boundary.

Keep the patch reviewable
Do not change database schema
Report any unverified assumption

The session no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/session/test_session_496_12.ts

Static analysis finds an unchecked error path in the edited function.

A bounded directory view reduces path assumptions without reading the full repository.

Confirm the local module boundary before searching for implementation details.

The task names behavior but repository evidence is required before selecting an edit target.

Question: SessionPolicy49612|authorization_order_defect

Locate the implementation and callers associated with SessionPolicy49612.

Search evidence identifies src/session/session_496_12.ts as the narrow implementation boundary.

Confirm the current control flow, local conventions, and error contract.

The patch should be verified using project-native tests rather than an invented harness.

Identify existing test style and the nearest regression boundary.

correct authorization-order defect while preserving the public contract

The first targeted test fails and provides a concrete counterexample.

Repeating the same patch would ignore the new test evidence.

Replace the disproven assumption with an evidence-backed failure hypothesis.

The repair is tied to the observed failure rather than a speculative rewrite.

Apply the second bounded patch addressing the diagnosed cause.

The repaired behavior must be re-executed before completion.

Confirm the revised patch satisfies the original acceptance criterion.

Diff inspection is required before making a completion claim.

Confirm the final change is bounded and contains no accidental edits.


Instruction: Fix the defect where the token silently truncates an oversized payload in the cache coordinator. The affected entry point is TokenPolicy49613; keep the change aligned with the existing layered service boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The token no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/token/test_token_496_13.ts

Use a bounded, updateable plan proportional to task complexity.

Question: TokenPolicy49613|input_size_handling_defect

Locate the implementation and callers associated with TokenPolicy49613.

Search evidence identifies src/token/token_496_13.ts as the narrow implementation boundary.

The task spans implementation and verification but does not justify an architectural redesign.

Create a short plan with explicit verification and no unrelated work.

correct input-size handling defect while preserving the public contract

Apply a localized change that follows existing abstractions.


Instruction: Fix the defect where the pagination does not preserve the public error contract in the cache coordinator. The affected entry point is PaginationPolicy49614; keep the change aligned with the existing layered service boundary.

Preserve the public API
Do not add dependencies
Limit changes to relevant files

The pagination no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/pagination/test_pagination_496_14.ts

Locate the implementation and callers associated with PaginationPolicy49614.

Search evidence identifies src/pagination/pagination_496_14.ts as the narrow implementation boundary.

correct compatibility defect while preserving the public contract


Instruction: Refactor the cache in the cache coordinator to remove duplicated cleanup logic without changing behavior. The affected entry point is CachePolicy49615; keep the change aligned with the existing layered service boundary.

Keep backward compatibility
Add or update a targeted test
Avoid unrelated refactors

The cache no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

ctest -R CacheRegression49615 --output-on-failure

Question: CachePolicy49615|resource_cleanup_defect

correct resource-cleanup defect while preserving the public contract


Instruction: Refactor the queue in the cache coordinator to remove duplicated validation logic without changing behavior. The affected entry point is QueuePolicy49616; keep the change aligned with the existing layered service boundary.

Do not expose secrets in logs
Preserve existing configuration keys
Run the narrow test first

The queue no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Verify the claimed behavior with targeted checks before completion.

Question: QueuePolicy49616|boundary_condition_defect

correct boundary-condition defect while preserving the public contract


Instruction: Fix the defect where the webhook drops the original error context in the cache coordinator. The affected entry point is WebhookPolicy49617; keep the change aligned with the existing layered service boundary.

Keep the patch reviewable
Do not change database schema
Report any unverified assumption

The webhook no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: WebhookPolicy49617|error_propagation_defect

Locate the implementation and callers associated with WebhookPolicy49617.

Search evidence identifies src/webhook/webhook_496_17.php as the narrow implementation boundary.

correct error-propagation defect while preserving the public contract

Check static constraints relevant to the modified code.


Instruction: Harden the permission in the cache coordinator against unsafe deserialization while preserving valid behavior. The affected entry point is PermissionPolicy49618; keep the change aligned with the existing layered service boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The permission no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

go test ./permission -run PermissionRegression49618

Locate the implementation and callers associated with PermissionPolicy49618.

Search evidence identifies internal/permission/permission_496_18.go as the narrow implementation boundary.

correct nullability defect while preserving the public contract

Obtain executable evidence for the requested behavior.

Static validation catches interface and error-handling defects not covered by the targeted test.


Instruction: Add guarded support for structured errors in the configuration of the cache coordinator. The affected entry point is ConfigurationPolicy49619; keep the change aligned with the existing layered service boundary.

Preserve the public API
Do not add dependencies
Limit changes to relevant files

The configuration no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Locate the implementation and callers associated with ConfigurationPolicy49619.

Search evidence identifies src/configuration/configuration_496_19.py as the narrow implementation boundary.

The implementation boundary and acceptance criterion are now supported by repository evidence.

correct sensitive-data exposure while preserving the public contract

A successful edit is not established until the narrow regression boundary passes.


Instruction: Add regression coverage for the case where the upload does not verify the persisted state in the CLI backend. The affected entry point is UploadPolicy49700; keep the change aligned with the existing modular monolith boundary.

Do not expose secrets in logs
Preserve existing configuration keys
Run the narrow test first

The upload no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

go test ./upload -run UploadRegression49700

rewrite subsystem
replace dependencies
change API

Use a bounded, updateable plan proportional to task complexity.


Instruction: Fix the defect where the download returns stale state after an update in the CLI backend. The affected entry point is DownloadPolicy49701; keep the change aligned with the existing modular monolith boundary.

Keep the patch reviewable
Do not change database schema
Report any unverified assumption

The download no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/download/test_download_497_01.ts

Respect scope and request approval only for materially risky actions.

Question: DownloadPolicy49701|cache_invalidation_defect

Locate the implementation and callers associated with DownloadPolicy49701.

Search evidence identifies src/download/download_497_01.ts as the narrow implementation boundary.

Confirm the current control flow, local conventions, and error contract.

The requested operation crosses a trust boundary that cannot be inferred from coding scope alone.

Pause before a materially risky action and explain the bounded reason approval is required.

Hard tasks require caller evidence to control compatibility risk.

Identify callers and contract-sensitive edges before changing multi-file behavior.


Instruction: Add guarded support for explicit timeouts in the audit of the CLI backend. The affected entry point is AuditPolicy49702; keep the change aligned with the existing modular monolith boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The audit no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

The task names behavior but repository evidence is required before selecting an edit target.

Locate the implementation and callers associated with AuditPolicy49702.

Search evidence identifies src/audit/audit_497_02.php as the narrow implementation boundary.

The patch should be verified using project-native tests rather than an invented harness.

Identify existing test style and the nearest regression boundary.


Instruction: Fix the defect where the worker performs authorization after the side effect in the CLI backend. The affected entry point is WorkerPolicy49703; keep the change aligned with the existing modular monolith boundary.

Preserve the public API
Do not add dependencies
Limit changes to relevant files

The worker no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/worker/test_worker_497_03.ts

Question: WorkerPolicy49703|authorization_order_defect

Locate the implementation and callers associated with WorkerPolicy49703.

Search evidence identifies src/worker/worker_497_03.ts as the narrow implementation boundary.

Diff inspection is required before making a completion claim.

Confirm the final change is bounded and contains no accidental edits.


Instruction: Refactor the scheduler in the CLI backend to remove duplicated retry decisions without changing behavior. The affected entry point is SchedulerPolicy49704; keep the change aligned with the existing modular monolith boundary.

Keep backward compatibility
Add or update a targeted test
Avoid unrelated refactors

The scheduler no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

A bounded directory view reduces path assumptions without reading the full repository.

Confirm the local module boundary before searching for implementation details.

Locate the implementation and callers associated with SchedulerPolicy49704.

Search evidence identifies src/scheduler/scheduler_497_04.py as the narrow implementation boundary.

Apply a localized change that follows existing abstractions.


Instruction: Add guarded support for graceful shutdown in the router of the CLI backend. The affected entry point is RouterPolicy49705; keep the change aligned with the existing modular monolith boundary.

Do not expose secrets in logs
Preserve existing configuration keys
Run the narrow test first

The router no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

cargo clippy --all-targets -- -D warnings

Report evidence-backed correctness or security findings with calibrated severity.

Locate the implementation and callers associated with RouterPolicy49705.

Search evidence identifies src/router/router_497_05.rs as the narrow implementation boundary.

Review findings must point to a concrete execution path, not stylistic preference.

correctness security compatibility test_coverage

Produce only evidence-backed findings with severity and confidence.


Instruction: Fix the defect where the metrics skips cleanup after cancellation in the CLI backend. The affected entry point is MetricsPolicy49706; keep the change aligned with the existing modular monolith boundary.

Keep the patch reviewable
Do not change database schema
Report any unverified assumption

The metrics no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: MetricsPolicy49706|resource_cleanup_defect

Locate the implementation and callers associated with MetricsPolicy49706.

Search evidence identifies src/metrics/metrics_497_06.php as the narrow implementation boundary.


Instruction: Refactor the logging in the CLI backend to remove duplicated configuration parsing without changing behavior. The affected entry point is LoggingPolicy49707; keep the change aligned with the existing modular monolith boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The logging no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Verify the claimed behavior with targeted checks before completion.

Question: LoggingPolicy49707|boundary_condition_defect

Locate the implementation and callers associated with LoggingPolicy49707.

Search evidence identifies src/logging/logging_497_07.py as the narrow implementation boundary.

Obtain executable evidence for the requested behavior.

Static validation catches interface and error-handling defects not covered by the targeted test.

Check static constraints relevant to the modified code.


Instruction: Review the proposed sandbox change in the CLI backend for correctness, scope, and regressions. The affected entry point is SandboxPolicy49708; keep the change aligned with the existing modular monolith boundary.

Preserve the public API
Do not add dependencies
Limit changes to relevant files

The sandbox no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests SandboxRegression49708

Question: SandboxPolicy49708|error_propagation_defect

Question: authorize|permission|sanitize|validate


Instruction: Correct the configuration and operator guidance for cursor pagination in the CLI backend. The affected entry point is SessionPolicy49709; keep the change aligned with the existing modular monolith boundary.

Keep backward compatibility
Add or update a targeted test
Avoid unrelated refactors

The session no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/session/test_session_497_09.ts

Choose the lowest-cost valid tool and use schema-correct arguments.


Instruction: Refactor the token in the CLI backend to remove duplicated authorization checks without changing behavior. The affected entry point is TokenPolicy49710; keep the change aligned with the existing modular monolith boundary.

Do not expose secrets in logs
Preserve existing configuration keys
Run the narrow test first

The token no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/token/test_token_497_10.ts

Question: TokenPolicy49710|sensitive_data_exposure

Locate the implementation and callers associated with TokenPolicy49710.

Search evidence identifies src/token/token_497_10.ts as the narrow implementation boundary.

Confirm the current control flow, local conventions, and error contract.

The task spans implementation and verification but does not justify an architectural redesign.

Create a short plan with explicit verification and no unrelated work.

The implementation boundary and acceptance criterion are now supported by repository evidence.

A successful edit is not established until the narrow regression boundary passes.

The targeted check establishes the fix; the wider suite provides additional regression evidence.

Check for regressions beyond the targeted behavior when the execution budget permits.


Instruction: Add guarded support for structured errors in the pagination of the CLI backend. The affected entry point is PaginationPolicy49711; keep the change aligned with the existing modular monolith boundary.

Keep the patch reviewable
Do not change database schema
Report any unverified assumption

The pagination no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests PaginationRegression49711

Report evidence-backed correctness or security findings with calibrated severity.


Instruction: Refactor the cache in the CLI backend to remove duplicated serialization logic without changing behavior. The affected entry point is CachePolicy49712; keep the change aligned with the existing modular monolith boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The cache no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

The task names behavior but repository evidence is required before selecting an edit target.

Question: CachePolicy49712|resource_bounding_defect

Locate the implementation and callers associated with CachePolicy49712.

Search evidence identifies src/cache/cache_497_12.php as the narrow implementation boundary.

The patch should be verified using project-native tests rather than an invented harness.

Identify existing test style and the nearest regression boundary.

correct resource-bounding defect while preserving the public contract

Preserve existing interfaces, correct only the evidenced behavior, and add narrow regression coverage.


Instruction: Add guarded support for dry-run mode in the queue of the CLI backend. The affected entry point is QueuePolicy49713; keep the change aligned with the existing modular monolith boundary.

Preserve the public API
Do not add dependencies
Limit changes to relevant files

The queue no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Classify failure evidence, revise the hypothesis, and repair without looping.

Question: QueuePolicy49713|failure_classification_defect

Locate the implementation and callers associated with QueuePolicy49713.

Search evidence identifies src/queue/queue_497_13.php as the narrow implementation boundary.

correct failure-classification defect while preserving the public contract

The first targeted test fails and provides a concrete counterexample.

Repeating the same patch would ignore the new test evidence.

Replace the disproven assumption with an evidence-backed failure hypothesis.

The repair is tied to the observed failure rather than a speculative rewrite.

Apply the second bounded patch addressing the diagnosed cause.

The repaired behavior must be re-executed before completion.

Confirm the revised patch satisfies the original acceptance criterion.

Diff inspection is required before making a completion claim.

Confirm the final change is bounded and contains no accidental edits.


Instruction: Add guarded support for explicit timeouts in the webhook of the CLI backend. The affected entry point is WebhookPolicy49714; keep the change aligned with the existing modular monolith boundary.

Keep backward compatibility
Add or update a targeted test
Avoid unrelated refactors

The webhook no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

go test ./webhook -run WebhookRegression49714

Question: WebhookPolicy49714|validation_order_defect

correct validation-order defect while preserving the public contract

Ground every decision in repository evidence before editing.


Instruction: Add regression coverage for the case where the permission retries a non-idempotent operation in the CLI backend. The affected entry point is PermissionPolicy49715; keep the change aligned with the existing modular monolith boundary.

Do not expose secrets in logs
Preserve existing configuration keys
Run the narrow test first

The permission no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/permission/test_permission_497_15.ts


Instruction: Fix the defect where the configuration mutates shared state across requests in the CLI backend. The affected entry point is ConfigurationPolicy49716; keep the change aligned with the existing modular monolith boundary.

Keep the patch reviewable
Do not change database schema
Report any unverified assumption

The configuration no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/configuration/test_configuration_497_16.ts

correct state-isolation defect while preserving the public contract


Instruction: Add guarded support for graceful shutdown in the parser of the CLI backend. The affected entry point is ParserPolicy49717; keep the change aligned with the existing modular monolith boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The parser no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: ParserPolicy49717|identity_comparison_defect

Locate the implementation and callers associated with ParserPolicy49717.

Search evidence identifies src/parser/parser_497_17.py as the narrow implementation boundary.

correct identity-comparison defect while preserving the public contract

Apply a localized change that follows existing abstractions.


Instruction: Refactor the serializer in the CLI backend to remove duplicated cleanup logic without changing behavior. The affected entry point is SerializerPolicy49718; keep the change aligned with the existing modular monolith boundary.

Preserve the public API
Do not add dependencies
Limit changes to relevant files

The serializer no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests SerializerRegression49718

correct false-success defect while preserving the public contract


Instruction: Harden the validator in the CLI backend against command injection while preserving valid behavior. The affected entry point is ValidatorPolicy49719; keep the change aligned with the existing modular monolith boundary.

Keep backward compatibility
Add or update a targeted test
Avoid unrelated refactors

The validator no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Locate the implementation and callers associated with ValidatorPolicy49719.

Search evidence identifies src/validator/validator_497_19.py as the narrow implementation boundary.

correct least-privilege defect while preserving the public contract

Obtain executable evidence for the requested behavior.


Instruction: Refactor the worker in the model evaluation runner to remove duplicated validation logic without changing behavior. The affected entry point is WorkerPolicy49800; keep the change aligned with the existing event-driven worker boundary.

Keep the patch reviewable
Do not change database schema
Report any unverified assumption

The worker no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

A bounded directory view reduces path assumptions without reading the full repository.

Confirm the local module boundary before searching for implementation details.

Locate the implementation and callers associated with WorkerPolicy49800.

Search evidence identifies src/worker/worker_498_00.py as the narrow implementation boundary.

Confirm the current control flow, local conventions, and error contract.

Hard tasks require caller evidence to control compatibility risk.

Identify callers and contract-sensitive edges before changing multi-file behavior.

Check for regressions beyond the targeted behavior when the execution budget permits.


Instruction: Refactor the scheduler in the model evaluation runner to remove duplicated validation logic without changing behavior. The affected entry point is SchedulerPolicy49801; keep the change aligned with the existing event-driven worker boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The scheduler no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/scheduler/test_scheduler_498_01.ts

Locate the implementation and callers associated with SchedulerPolicy49801.

Search evidence identifies src/scheduler/scheduler_498_01.ts as the narrow implementation boundary.

The implementation boundary and acceptance criterion are now supported by repository evidence.

A successful edit is not established until the narrow regression boundary passes.

Static validation catches interface and error-handling defects not covered by the targeted test.

Check static constraints relevant to the modified code.


Instruction: Add guarded support for request cancellation in the router of the model evaluation runner. The affected entry point is RouterPolicy49802; keep the change aligned with the existing event-driven worker boundary.

Preserve the public API
Do not add dependencies
Limit changes to relevant files

The router no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

The task names behavior but repository evidence is required before selecting an edit target.

Locate the implementation and callers associated with RouterPolicy49802.

Search evidence identifies src/router/router_498_02.py as the narrow implementation boundary.

The patch should be verified using project-native tests rather than an invented harness.

Identify existing test style and the nearest regression boundary.

correct idempotency defect while preserving the public contract

The first targeted test fails and provides a concrete counterexample.

Replace the disproven assumption with an evidence-backed failure hypothesis.

revise the failed assumption without expanding scope

Apply the second bounded patch addressing the diagnosed cause.

Confirm the revised patch satisfies the original acceptance criterion.

Confirm the final change is bounded and contains no accidental edits.


Instruction: Add guarded support for structured errors in the metrics of the model evaluation runner. The affected entry point is MetricsPolicy49803; keep the change aligned with the existing event-driven worker boundary.

Keep backward compatibility
Add or update a targeted test
Avoid unrelated refactors

The metrics no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/metrics/test_metrics_498_03.ts

Question: MetricsPolicy49803|resource_bounding_defect


Instruction: Refactor the logging in the model evaluation runner to remove duplicated error mapping without changing behavior. The affected entry point is LoggingPolicy49804; keep the change aligned with the existing event-driven worker boundary.

Do not expose secrets in logs
Preserve existing configuration keys
Run the narrow test first

The logging no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests LoggingRegression49804

Question: LoggingPolicy49804|failure_classification_defect

Locate the implementation and callers associated with LoggingPolicy49804.

Search evidence identifies src/main/java/logging/LoggingService498.java as the narrow implementation boundary.

The task spans implementation and verification but does not justify an architectural redesign.

Create a short plan with explicit verification and no unrelated work.

Apply a localized change that follows existing abstractions.

Obtain executable evidence for the requested behavior.


Instruction: Add guarded support for dry-run mode in the sandbox of the model evaluation runner. The affected entry point is SandboxPolicy49805; keep the change aligned with the existing event-driven worker boundary.

Keep the patch reviewable
Do not change database schema
Report any unverified assumption

The sandbox no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/sandbox/test_sandbox_498_05.ts

A related regression test fails after the target behavior is corrected.

repair diagnosed cause without broadening scope

Question: SandboxPolicy49805|validation_order_defect

Locate the implementation and callers associated with SandboxPolicy49805.

Search evidence identifies src/sandbox/sandbox_498_05.ts as the narrow implementation boundary.

Confirm the current control flow, local conventions, and error contract.

Identify callers and contract-sensitive edges before changing multi-file behavior.

Repeating the same patch would ignore the new test evidence.

The repair is tied to the observed failure rather than a speculative rewrite.

The repaired behavior must be re-executed before completion.

The targeted check establishes the fix; the wider suite provides additional regression evidence.

Check for regressions beyond the targeted behavior when the execution budget permits.

Diff inspection is required before making a completion claim.


Instruction: Review the proposed session change in the model evaluation runner for correctness, scope, and regressions. The affected entry point is SessionPolicy49806; keep the change aligned with the existing event-driven worker boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The session no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/session/test_session_498_06.ts

Locate the implementation and callers associated with SessionPolicy49806.

Search evidence identifies src/session/session_498_06.ts as the narrow implementation boundary.

Review findings must point to a concrete execution path, not stylistic preference.

Produce only evidence-backed findings with severity and confidence.

Security and review decisions require evidence about authorization and validation order.

Question: authorize|permission|sanitize|validate

Locate the nearest trust-boundary implementation and existing guard pattern.


Instruction: Fix the defect where the token mutates shared state across requests in the model evaluation runner. The affected entry point is TokenPolicy49807; keep the change aligned with the existing event-driven worker boundary.

Preserve the public API
Do not add dependencies
Limit changes to relevant files

The token no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

go test ./token -run TokenRegression49807


Instruction: Fix the defect where the pagination matches identifiers case-insensitively in the model evaluation runner. The affected entry point is PaginationPolicy49808; keep the change aligned with the existing event-driven worker boundary.

Keep backward compatibility
Add or update a targeted test
Avoid unrelated refactors

The pagination no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/pagination/test_pagination_498_08.ts

A bounded directory view reduces path assumptions without reading the full repository.

Confirm the local module boundary before searching for implementation details.

Locate the implementation and callers associated with PaginationPolicy49808.

Search evidence identifies src/pagination/pagination_498_08.ts as the narrow implementation boundary.

Identify existing test style and the nearest regression boundary.


Instruction: Review the proposed cache change in the model evaluation runner for correctness, scope, and regressions. The affected entry point is CachePolicy49809; keep the change aligned with the existing event-driven worker boundary.

Do not expose secrets in logs
Preserve existing configuration keys
Run the narrow test first

The cache no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Locate the implementation and callers associated with CachePolicy49809.

Search evidence identifies src/cache/cache_498_09.py as the narrow implementation boundary.

The implementation boundary and acceptance criterion are now supported by repository evidence.

Hard tasks require caller evidence to control compatibility risk.

Question: authorize|permission|sanitize|validate

A successful edit is not established until the narrow regression boundary passes.

Static validation catches interface and error-handling defects not covered by the targeted test.

Check static constraints relevant to the modified code.

Confirm the final change is bounded and contains no accidental edits.


Instruction: Refactor the queue in the model evaluation runner to remove duplicated configuration parsing without changing behavior. The affected entry point is QueuePolicy49810; keep the change aligned with the existing event-driven worker boundary.

Keep the patch reviewable
Do not change database schema
Report any unverified assumption

The queue no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

The task names behavior but repository evidence is required before selecting an edit target.

Locate the implementation and callers associated with QueuePolicy49810.

Search evidence identifies src/queue/queue_498_10.py as the narrow implementation boundary.

The task spans implementation and verification but does not justify an architectural redesign.

Create a short plan with explicit verification and no unrelated work.

The patch should be verified using project-native tests rather than an invented harness.

Apply a localized change that follows existing abstractions.

Obtain executable evidence for the requested behavior.


Instruction: Fix the defect where the webhook does not verify the persisted state in the model evaluation runner. The affected entry point is WebhookPolicy49811; keep the change aligned with the existing event-driven worker boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The webhook no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests WebhookRegression49811

Locate the implementation and callers associated with WebhookPolicy49811.

Search evidence identifies src/main/java/webhook/WebhookService498.java as the narrow implementation boundary.

Confirm the current control flow, local conventions, and error contract.

correct verification defect while preserving the public contract


Instruction: Correct the configuration and operator guidance for bounded retries in the model evaluation runner. The affected entry point is PermissionPolicy49812; keep the change aligned with the existing event-driven worker boundary.

Preserve the public API
Do not add dependencies
Limit changes to relevant files

The permission no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

correct cache-invalidation defect while preserving the public contract


Instruction: Fix the defect where the configuration uses seconds where milliseconds are expected in the model evaluation runner. The affected entry point is ConfigurationPolicy49813; keep the change aligned with the existing event-driven worker boundary.

Keep backward compatibility
Add or update a targeted test
Avoid unrelated refactors

The configuration no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Locate the implementation and callers associated with ConfigurationPolicy49813.

Search evidence identifies src/configuration/configuration_498_13.py as the narrow implementation boundary.

correct unit-conversion defect while preserving the public contract

Diff inspection is required before making a completion claim.


Instruction: Add guarded support for request cancellation in the parser of the model evaluation runner. The affected entry point is ParserPolicy49814; keep the change aligned with the existing event-driven worker boundary.

Do not expose secrets in logs
Preserve existing configuration keys
Run the narrow test first

The parser no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/parser/test_parser_498_14.ts

Question: ParserPolicy49814|authorization_order_defect

Locate the implementation and callers associated with ParserPolicy49814.

Search evidence identifies src/parser/parser_498_14.ts as the narrow implementation boundary.

correct authorization-order defect while preserving the public contract


Instruction: Refactor the serializer in the model evaluation runner to remove duplicated serialization logic without changing behavior. The affected entry point is SerializerPolicy49815; keep the change aligned with the existing event-driven worker boundary.

Keep the patch reviewable
Do not change database schema
Report any unverified assumption

The serializer no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Locate the implementation and callers associated with SerializerPolicy49815.

Search evidence identifies src/serializer/serializer_498_15.py as the narrow implementation boundary.

correct input-size handling defect while preserving the public contract

The targeted check establishes the fix; the wider suite provides additional regression evidence.

Check for regressions beyond the targeted behavior when the execution budget permits.


Instruction: Refactor the validator in the model evaluation runner to remove duplicated serialization logic without changing behavior. The affected entry point is ValidatorPolicy49816; keep the change aligned with the existing event-driven worker boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The validator no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

A bounded directory view reduces path assumptions without reading the full repository.

Locate the implementation and callers associated with ValidatorPolicy49816.

Search evidence identifies src/validator/validator_498_16.py as the narrow implementation boundary.

correct compatibility defect while preserving the public contract


Instruction: Add guarded support for dry-run mode in the retry of the model evaluation runner. The affected entry point is RetryPolicy49817; keep the change aligned with the existing event-driven worker boundary.

Preserve the public API
Do not add dependencies
Limit changes to relevant files

The retry no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: RetryPolicy49817|resource_cleanup_defect

correct resource-cleanup defect while preserving the public contract


Instruction: Refactor the timeout in the model evaluation runner to remove duplicated state transitions without changing behavior. The affected entry point is TimeoutPolicy49818; keep the change aligned with the existing event-driven worker boundary.

Keep backward compatibility
Add or update a targeted test
Avoid unrelated refactors

The timeout no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests TimeoutRegression49818

Question: TimeoutPolicy49818|boundary_condition_defect

Locate the implementation and callers associated with TimeoutPolicy49818.

Search evidence identifies src/main/java/timeout/TimeoutService498.java as the narrow implementation boundary.

The implementation boundary and acceptance criterion are now supported by repository evidence.

correct boundary-condition defect while preserving the public contract

Preserve existing interfaces, correct only the evidenced behavior, and add narrow regression coverage.


Instruction: Add guarded support for audit metadata in the search of the model evaluation runner. The affected entry point is SearchPolicy49819; keep the change aligned with the existing event-driven worker boundary.

Do not expose secrets in logs
Preserve existing configuration keys
Run the narrow test first

The search no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests SearchRegression49819

Question: SearchPolicy49819|error_propagation_defect

Locate the implementation and callers associated with SearchPolicy49819.

Search evidence identifies src/main/java/search/SearchService498.java as the narrow implementation boundary.

Identify existing test style and the nearest regression boundary.

Hard tasks require caller evidence to control compatibility risk.

Identify callers and contract-sensitive edges before changing multi-file behavior.

correct error-propagation defect while preserving the public contract

A successful edit is not established until the narrow regression boundary passes.


Instruction: Add regression coverage for the case where the metrics marks partial work as successful in the sandbox controller. The affected entry point is MetricsPolicy49900; keep the change aligned with the existing CLI application boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The metrics no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests MetricsRegression49900

Confirm the local module boundary before searching for implementation details.

The task names behavior but repository evidence is required before selecting an edit target.

Locate the implementation and callers associated with MetricsPolicy49900.

Search evidence identifies src/main/java/metrics/MetricsService499.java as the narrow implementation boundary.

Static validation catches interface and error-handling defects not covered by the targeted test.

Check static constraints relevant to the modified code.

Confirm the final change is bounded and contains no accidental edits.


Instruction: Fix the defect where the logging uses a broad filesystem permission in the sandbox controller. The affected entry point is LoggingPolicy49901; keep the change aligned with the existing CLI application boundary.

Preserve the public API
Do not add dependencies
Limit changes to relevant files

The logging no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: LoggingPolicy49901|least_privilege_defect

Locate the implementation and callers associated with LoggingPolicy49901.

Search evidence identifies src/logging/logging_499_01.py as the narrow implementation boundary.

The patch should be verified using project-native tests rather than an invented harness.

Apply a localized change that follows existing abstractions.

Obtain executable evidence for the requested behavior.


Instruction: Add guarded support for per-tenant configuration in the sandbox of the sandbox controller. The affected entry point is SandboxPolicy49902; keep the change aligned with the existing CLI application boundary.

Keep backward compatibility
Add or update a targeted test
Avoid unrelated refactors

The sandbox no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Locate the implementation and callers associated with SandboxPolicy49902.

Search evidence identifies src/sandbox/sandbox_499_02.rs as the narrow implementation boundary.

Confirm the current control flow, local conventions, and error contract.

The task spans implementation and verification but does not justify an architectural redesign.

Create a short plan with explicit verification and no unrelated work.

Diff inspection is required before making a completion claim.


Instruction: Refactor the session in the sandbox controller to remove duplicated cleanup logic without changing behavior. The affected entry point is SessionPolicy49903; keep the change aligned with the existing CLI application boundary.

Do not expose secrets in logs
Preserve existing configuration keys
Run the narrow test first

The session no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/session/test_session_499_03.ts

Question: SessionPolicy49903|cache_invalidation_defect

Locate the implementation and callers associated with SessionPolicy49903.

Search evidence identifies src/session/session_499_03.ts as the narrow implementation boundary.

The first targeted test fails and provides a concrete counterexample.

Repeating the same patch would ignore the new test evidence.

Replace the disproven assumption with an evidence-backed failure hypothesis.

The repair is tied to the observed failure rather than a speculative rewrite.

Apply the second bounded patch addressing the diagnosed cause.

The repaired behavior must be re-executed before completion.

Confirm the revised patch satisfies the original acceptance criterion.


Instruction: Refactor the token in the sandbox controller to remove duplicated validation logic without changing behavior. The affected entry point is TokenPolicy49904; keep the change aligned with the existing CLI application boundary.

Keep the patch reviewable
Do not change database schema
Report any unverified assumption

The token no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

A bounded directory view reduces path assumptions without reading the full repository.

Locate the implementation and callers associated with TokenPolicy49904.

Search evidence identifies src/token/token_499_04.py as the narrow implementation boundary.

Identify existing test style and the nearest regression boundary.

The implementation boundary and acceptance criterion are now supported by repository evidence.


Instruction: Fix the defect where the pagination performs authorization after the side effect in the sandbox controller. The affected entry point is PaginationPolicy49905; keep the change aligned with the existing CLI application boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The pagination no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope


Instruction: Fix the defect where the cache silently truncates an oversized payload in the sandbox controller. The affected entry point is CachePolicy49906; keep the change aligned with the existing CLI application boundary.

Preserve the public API
Do not add dependencies
Limit changes to relevant files

The cache no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

go test ./cache -run CacheRegression49906

Question: CachePolicy49906|input_size_handling_defect

Locate the implementation and callers associated with CachePolicy49906.

Search evidence identifies internal/cache/cache_499_06.go as the narrow implementation boundary.

A successful edit is not established until the narrow regression boundary passes.


Instruction: Fix the defect where the queue does not preserve the public error contract in the sandbox controller. The affected entry point is QueuePolicy49907; keep the change aligned with the existing CLI application boundary.

Keep backward compatibility
Add or update a targeted test
Avoid unrelated refactors

The queue no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/queue/test_queue_499_07.ts

Respect scope and request approval only for materially risky actions.


Instruction: Add guarded support for idempotency keys in the webhook of the sandbox controller. The affected entry point is WebhookPolicy49908; keep the change aligned with the existing CLI application boundary.

Do not expose secrets in logs
Preserve existing configuration keys
Run the narrow test first

The webhook no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests WebhookRegression49908

Confirm the local module boundary before searching for implementation details.

The task names behavior but repository evidence is required before selecting an edit target.

Question: WebhookPolicy49908|resource_cleanup_defect

Locate the implementation and callers associated with WebhookPolicy49908.

Search evidence identifies src/main/java/webhook/WebhookService499.java as the narrow implementation boundary.

Confirm the final change is bounded and contains no accidental edits.


Instruction: Add guarded support for dry-run mode in the permission of the sandbox controller. The affected entry point is PermissionPolicy49909; keep the change aligned with the existing CLI application boundary.

Keep the patch reviewable
Do not change database schema
Report any unverified assumption

The permission no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/permission/test_permission_499_09.ts

Locate the implementation and callers associated with PermissionPolicy49909.

Search evidence identifies src/permission/permission_499_09.ts as the narrow implementation boundary.

Apply a localized change that follows existing abstractions.

Obtain executable evidence for the requested behavior.


Instruction: Harden the configuration in the sandbox controller against unsafe deserialization while preserving valid behavior. The affected entry point is ConfigurationPolicy49910; keep the change aligned with the existing CLI application boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The configuration no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Locate the implementation and callers associated with ConfigurationPolicy49910.

Search evidence identifies src/configuration/configuration_499_10.py as the narrow implementation boundary.

Confirm the current control flow, local conventions, and error contract.

The patch should be verified using project-native tests rather than an invented harness.

Create a short plan with explicit verification and no unrelated work.

Security and review decisions require evidence about authorization and validation order.

Question: authorize|permission|sanitize|validate

Locate the nearest trust-boundary implementation and existing guard pattern.

The targeted check establishes the fix; the wider suite provides additional regression evidence.

Check for regressions beyond the targeted behavior when the execution budget permits.

Diff inspection is required before making a completion claim.


Instruction: Add guarded support for audit metadata in the parser of the sandbox controller. The affected entry point is ParserPolicy49911; keep the change aligned with the existing CLI application boundary.

Preserve the public API
Do not add dependencies
Limit changes to relevant files

The parser no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/parser/test_parser_499_11.ts

The compiler reports an interface mismatch introduced by the first patch.

Locate the implementation and callers associated with ParserPolicy49911.

Search evidence identifies src/parser/parser_499_11.ts as the narrow implementation boundary.

correct nullability defect while preserving the public contract


Instruction: Add regression coverage for the case where the serializer logs a secret-bearing request field in the sandbox controller. The affected entry point is SerializerPolicy49912; keep the change aligned with the existing CLI application boundary.

Keep backward compatibility
Add or update a targeted test
Avoid unrelated refactors

The serializer no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

ctest -R SerializerRegression49912 --output-on-failure

Locate the implementation and callers associated with SerializerPolicy49912.

Search evidence identifies src/serializer/serializer_499_12.cpp as the narrow implementation boundary.

The task spans implementation and verification but does not justify an architectural redesign.

correct sensitive-data exposure while preserving the public contract


Instruction: Fix the defect where the validator creates duplicate jobs under concurrent delivery in the sandbox controller. The affected entry point is ValidatorPolicy49913; keep the change aligned with the existing CLI application boundary.

Do not expose secrets in logs
Preserve existing configuration keys
Run the narrow test first

The validator no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

The diff includes a configuration change outside the requested boundary.

Locate the implementation and callers associated with ValidatorPolicy49913.

Search evidence identifies src/validator/validator_499_13.py as the narrow implementation boundary.

Static validation catches interface and error-handling defects not covered by the targeted test.

Check static constraints relevant to the modified code.


Instruction: Harden the retry in the sandbox controller against unsafe deserialization while preserving valid behavior. The affected entry point is RetryPolicy49914; keep the change aligned with the existing CLI application boundary.

Keep the patch reviewable
Do not change database schema
Report any unverified assumption

The retry no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/retry/test_retry_499_14.ts

Question: RetryPolicy49914|resource_bounding_defect

correct resource-bounding defect while preserving the public contract


Instruction: Refactor the timeout in the sandbox controller to remove duplicated configuration parsing without changing behavior. The affected entry point is TimeoutPolicy49915; keep the change aligned with the existing CLI application boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The timeout no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: TimeoutPolicy49915|failure_classification_defect

Locate the implementation and callers associated with TimeoutPolicy49915.

Search evidence identifies src/timeout/timeout_499_15.py as the narrow implementation boundary.

Identify existing test style and the nearest regression boundary.

The implementation boundary and acceptance criterion are now supported by repository evidence.

correct failure-classification defect while preserving the public contract


Instruction: Add guarded support for bounded retries in the search of the sandbox controller. The affected entry point is SearchPolicy49916; keep the change aligned with the existing CLI application boundary.

Preserve the public API
Do not add dependencies
Limit changes to relevant files

The search no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/search/test_search_499_16.ts

A bounded directory view reduces path assumptions without reading the full repository.

Confirm the local module boundary before searching for implementation details.

Question: SearchPolicy49916|validation_order_defect

Locate the implementation and callers associated with SearchPolicy49916.

Search evidence identifies src/search/search_499_16.ts as the narrow implementation boundary.

correct validation-order defect while preserving the public contract

A successful edit is not established until the narrow regression boundary passes.

Confirm the final change is bounded and contains no accidental edits.


Instruction: Refactor the index in the sandbox controller to remove duplicated authorization checks without changing behavior. The affected entry point is IndexPolicy49917; keep the change aligned with the existing CLI application boundary.

Keep backward compatibility
Add or update a targeted test
Avoid unrelated refactors

The index no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests IndexRegression49917

The task names behavior but repository evidence is required before selecting an edit target.

Locate the implementation and callers associated with IndexPolicy49917.

Search evidence identifies src/main/java/index/IndexService499.java as the narrow implementation boundary.

correct retry-safety defect while preserving the public contract

Apply a localized change that follows existing abstractions.

Obtain executable evidence for the requested behavior.


Instruction: Refactor the migration in the sandbox controller to remove duplicated authorization checks without changing behavior. The affected entry point is MigrationPolicy49918; keep the change aligned with the existing CLI application boundary.

Do not expose secrets in logs
Preserve existing configuration keys
Run the narrow test first

The migration no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Locate the implementation and callers associated with MigrationPolicy49918.

Search evidence identifies src/migration/migration_499_18.php as the narrow implementation boundary.

Confirm the current control flow, local conventions, and error contract.

correct state-isolation defect while preserving the public contract


Instruction: Refactor the upload in the sandbox controller to remove duplicated serialization logic without changing behavior. The affected entry point is UploadPolicy49919; keep the change aligned with the existing CLI application boundary.

Keep the patch reviewable
Do not change database schema
Report any unverified assumption

The upload no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/upload/test_upload_499_19.ts

Question: UploadPolicy49919|identity_comparison_defect

Locate the implementation and callers associated with UploadPolicy49919.

Search evidence identifies src/upload/upload_499_19.ts as the narrow implementation boundary.

The patch should be verified using project-native tests rather than an invented harness.

Create a short plan with explicit verification and no unrelated work.

correct identity-comparison defect while preserving the public contract