Instruction: Fix the defect where the cache retries a non-idempotent operation in the access-control service. The affected entry point is CachePolicy47018; keep the change aligned with the existing library package boundary.

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

The cache no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/cache/test_cache_470_18.ts

Locate the implementation and callers associated with CachePolicy47018.

Search evidence identifies src/cache/cache_470_18.ts as the narrow implementation boundary.

correct retry-safety defect while preserving the public contract

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 access-control service to remove duplicated configuration parsing without changing behavior. The affected entry point is QueuePolicy47019; keep the change aligned with the existing library package boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

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_470_19.ts

Ground every decision in repository evidence before editing.

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

Locate the implementation and callers associated with QueuePolicy47019.

Search evidence identifies src/queue/queue_470_19.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.

Hard tasks require caller evidence to control compatibility risk.

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

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.

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

correct state-isolation defect while preserving the public contract

Apply a localized change that follows existing abstractions.

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

Obtain executable evidence for the requested behavior.

Diff inspection is required before making a completion claim.

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


Instruction: Fix the defect where the search skips cleanup after cancellation in the cache coordinator. The affected entry point is SearchPolicy47100; keep the change aligned with the existing plugin-based service boundary.

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

The search 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

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

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

Confirm the local module boundary before searching for implementation details.

Question: SearchPolicy47100|resource_cleanup_defect

Locate the implementation and callers associated with SearchPolicy47100.

Search evidence identifies src/search/search_471_00.rs as the narrow implementation boundary.

correct resource-cleanup 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: Add regression coverage for the case where the index rejects valid boundary values in the cache coordinator. The affected entry point is IndexPolicy47101; keep the change aligned with the existing plugin-based service boundary.

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

The index 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: IndexPolicy47101|boundary_condition_defect

Locate the implementation and callers associated with IndexPolicy47101.

Search evidence identifies src/index/index_471_01.py as the narrow implementation boundary.

correct boundary-condition defect while preserving the public contract


Instruction: Review the proposed migration change in the cache coordinator for correctness, scope, and regressions. The affected entry point is MigrationPolicy47102; keep the change aligned with the existing plugin-based service boundary.

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

The migration no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests MigrationRegression47102

Locate the implementation and callers associated with MigrationPolicy47102.

Search evidence identifies src/main/java/migration/MigrationService471.java as the narrow implementation boundary.

correct error-propagation defect while preserving the public contract


Instruction: Add regression coverage for the case where the upload fails when an optional field is absent in the cache coordinator. The affected entry point is UploadPolicy47103; keep the change aligned with the existing plugin-based 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

npm test -- test/upload/test_upload_471_03.ts

correct nullability defect while preserving the public contract

Verify the claimed behavior with targeted checks before completion.


Instruction: Fix the defect where the download logs a secret-bearing request field in the cache coordinator. The affected entry point is DownloadPolicy47104; keep the change aligned with the existing plugin-based 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

Question: DownloadPolicy47104|sensitive_data_exposure

correct sensitive-data exposure while preserving the public contract

Ground every decision in repository evidence before editing.


Instruction: Add guarded support for dry-run mode in the audit of the cache coordinator. The affected entry point is AuditPolicy47105; keep the change aligned with the existing plugin-based 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

correct idempotency defect while preserving the public contract


Instruction: Fix the defect where the worker loads an unbounded result set in the cache coordinator. The affected entry point is WorkerPolicy47106; keep the change aligned with the existing plugin-based 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

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

Question: WorkerPolicy47106|resource_bounding_defect

correct resource-bounding defect while preserving the public contract


Instruction: Harden the scheduler in the cache coordinator against secret leakage while preserving valid behavior. The affected entry point is SchedulerPolicy47107; keep the change aligned with the existing plugin-based 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

go test ./scheduler -run SchedulerRegression47107

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

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

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

repair diagnosed cause without broadening scope

Locate the implementation and callers associated with SchedulerPolicy47107.

Search evidence identifies internal/scheduler/scheduler_471_07.go as the narrow implementation boundary.

correct failure-classification defect while preserving the public contract

The original acceptance criterion passes

The failure signal is no longer reproduced

The final report distinguishes executed evidence from assumptions


Instruction: Add regression coverage for the case where the router accepts malformed input after normalization in the cache coordinator. The affected entry point is RouterPolicy47108; keep the change aligned with the existing plugin-based 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

npm test -- test/router/test_router_471_08.ts

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

Question: RouterPolicy47108|validation_order_defect

Locate the implementation and callers associated with RouterPolicy47108.

Search evidence identifies src/router/router_471_08.ts as the narrow implementation boundary.

correct validation-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.

revise the failed assumption without expanding scope

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.

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


Instruction: Add regression coverage for the case where the metrics retries a non-idempotent operation in the cache coordinator. The affected entry point is MetricsPolicy47109; keep the change aligned with the existing plugin-based 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

npm test -- test/metrics/test_metrics_471_09.ts

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

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

Locate the implementation and callers associated with MetricsPolicy47109.

Search evidence identifies src/metrics/metrics_471_09.ts 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.

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

Check static constraints relevant to the modified code.


Instruction: Correct the configuration and operator guidance for per-tenant configuration in the cache coordinator. The affected entry point is LoggingPolicy47110; keep the change aligned with the existing plugin-based 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

Question: LoggingPolicy47110|state_isolation_defect

Locate the implementation and callers associated with LoggingPolicy47110.

Search evidence identifies src/logging/logging_471_10.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.

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

Apply a localized change that follows existing abstractions.

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

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

Diff inspection is required before making a completion claim.


Instruction: Fix the defect where the sandbox matches identifiers case-insensitively in the cache coordinator. The affected entry point is SandboxPolicy47111; keep the change aligned with the existing plugin-based 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

Respect scope and request approval only for materially risky actions.

Question: SandboxPolicy47111|identity_comparison_defect


Instruction: Review the proposed session change in the cache coordinator for correctness, scope, and regressions. The affected entry point is SessionPolicy47112; keep the change aligned with the existing plugin-based 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

./gradlew test --tests SessionRegression47112

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

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 SessionPolicy47112.

Search evidence identifies src/main/java/session/SessionService471.java as the narrow implementation 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 false-success defect while preserving the public contract

Obtain executable evidence for the requested behavior.


Instruction: Review the proposed token change in the cache coordinator for correctness, scope, and regressions. The affected entry point is TokenPolicy47113; keep the change aligned with the existing plugin-based 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

Locate the implementation and callers associated with TokenPolicy47113.

Search evidence identifies src/token/token_471_13.php 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 least-privilege defect while preserving the public contract


Instruction: Fix the defect where the pagination does not verify the persisted state in the cache coordinator. The affected entry point is PaginationPolicy47114; keep the change aligned with the existing plugin-based 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

Respect scope and request approval only for materially risky actions.

Locate the implementation and callers associated with PaginationPolicy47114.

Search evidence identifies src/pagination/pagination_471_14.php as the narrow implementation boundary.

Unnecessary approval requests would reduce agent usefulness without improving safety.

Proceed because the operation is local, reversible, and within the explicit task boundary.

correct verification defect while preserving the public contract

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


Instruction: Add guarded support for structured errors in the cache of the cache coordinator. The affected entry point is CachePolicy47115; keep the change aligned with the existing plugin-based 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

npm test -- test/cache/test_cache_471_15.ts

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

Question: CachePolicy47115|cache_invalidation_defect

Locate the implementation and callers associated with CachePolicy47115.

Search evidence identifies src/cache/cache_471_15.ts as the narrow implementation boundary.

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

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: Refactor the queue in the cache coordinator to remove duplicated error mapping without changing behavior. The affected entry point is QueuePolicy47116; keep the change aligned with the existing plugin-based 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

./gradlew test --tests QueueRegression47116

Repository evidence contradicts the initial assumption about the data representation.

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

Locate the implementation and callers associated with QueuePolicy47116.

Search evidence identifies src/main/java/queue/QueueService471.java as the narrow implementation boundary.

correct unit-conversion defect while preserving the public contract


Instruction: Refactor the webhook in the cache coordinator to remove duplicated error mapping without changing behavior. The affected entry point is WebhookPolicy47117; keep the change aligned with the existing plugin-based 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

npm test -- test/webhook/test_webhook_471_17.ts

Use a bounded, updateable plan proportional to task complexity.

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

Question: WebhookPolicy47117|authorization_order_defect

Locate the implementation and callers associated with WebhookPolicy47117.

Search evidence identifies src/webhook/webhook_471_17.ts as the narrow implementation boundary.

Hard tasks require caller evidence to control compatibility risk.

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

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

Identify existing test style and the nearest regression boundary.

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

correct authorization-order defect while preserving the public contract

Apply a localized change that follows existing abstractions.

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

Diff inspection is required before making a completion claim.


Instruction: Correct the configuration and operator guidance for explicit timeouts in the cache coordinator. The affected entry point is PermissionPolicy47118; keep the change aligned with the existing plugin-based 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 PermissionRegression47118

Locate the implementation and callers associated with PermissionPolicy47118.

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

correct input-size handling defect while preserving the public contract

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

Check static constraints relevant to the modified code.

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


Instruction: Add guarded support for audit metadata in the configuration of the cache coordinator. The affected entry point is ConfigurationPolicy47119; keep the change aligned with the existing plugin-based 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

./gradlew test --tests ConfigurationRegression47119

correct compatibility defect while preserving the public contract

rewrite subsystem
replace dependencies
change API

Use a bounded, updateable plan proportional to task complexity.


Instruction: Add guarded support for input size limits in the upload of the CLI backend. The affected entry point is UploadPolicy47200; 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 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_472_00.ts

correct retry-safety defect while preserving the public contract

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


Instruction: Fix the defect where the download mutates shared state across requests in the CLI backend. The affected entry point is DownloadPolicy47201; keep the change aligned with the existing layered service 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

go test ./download -run DownloadRegression47201

Question: DownloadPolicy47201|state_isolation_defect

Locate the implementation and callers associated with DownloadPolicy47201.

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

correct state-isolation defect while preserving the public contract

Obtain executable evidence for the requested behavior.


Instruction: Fix the defect where the audit matches identifiers case-insensitively in the CLI backend. The affected entry point is AuditPolicy47202; keep the change aligned with the existing layered service 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

Question: AuditPolicy47202|identity_comparison_defect

Locate the implementation and callers associated with AuditPolicy47202.

Search evidence identifies src/audit/audit_472_02.py as the narrow implementation boundary.

correct identity-comparison defect while preserving the public contract


Instruction: Fix the defect where the worker marks partial work as successful in the CLI backend. The affected entry point is WorkerPolicy47203; keep the change aligned with the existing layered service 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_472_03.ts

Locate the implementation and callers associated with WorkerPolicy47203.

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


Instruction: Fix the defect where the scheduler uses a broad filesystem permission in the CLI backend. The affected entry point is SchedulerPolicy47204; keep the change aligned with the existing layered service 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

./gradlew test --tests SchedulerRegression47204

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 SchedulerPolicy47204.

Search evidence identifies src/main/java/scheduler/SchedulerService472.java as the narrow implementation boundary.

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


Instruction: Review the proposed router change in the CLI backend for correctness, scope, and regressions. The affected entry point is RouterPolicy47205; 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 router 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 RouterPolicy47205.

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

Confirm the current control flow, local conventions, and error 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: Add regression coverage for the case where the metrics returns stale state after an update in the CLI backend. The affected entry point is MetricsPolicy47206; keep the change aligned with the existing layered service 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

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

Question: MetricsPolicy47206|cache_invalidation_defect

Locate the implementation and callers associated with MetricsPolicy47206.

Search evidence identifies src/metrics/metrics_472_06.py as the narrow implementation boundary.

correct cache-invalidation defect while preserving the public contract


Instruction: Refactor the logging in the CLI backend to remove duplicated serialization logic without changing behavior. The affected entry point is LoggingPolicy47207; keep the change aligned with the existing layered service 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

ctest -R LoggingRegression47207 --output-on-failure

Use a bounded, updateable plan proportional to task complexity.

Question: LoggingPolicy47207|unit_conversion_defect

Locate the implementation and callers associated with LoggingPolicy47207.

Search evidence identifies src/logging/logging_472_07.cpp 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.

Identify existing test style and the nearest regression boundary.

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

Apply a localized change that follows existing abstractions.

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

Diff inspection is required before making a completion claim.


Instruction: Refactor the sandbox in the CLI backend to remove duplicated serialization logic without changing behavior. The affected entry point is SandboxPolicy47208; keep the change aligned with the existing layered service 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

Question: SandboxPolicy47208|authorization_order_defect

Locate the implementation and callers associated with SandboxPolicy47208.

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


Instruction: Harden the session in the CLI backend against cross-tenant access while preserving valid behavior. The affected entry point is SessionPolicy47209; keep the change aligned with the existing layered service 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

dotnet test --filter SessionRegression47209

Question: SessionPolicy47209|input_size_handling_defect

Locate the implementation and callers associated with SessionPolicy47209.

Search evidence identifies src/session/SessionService472.cs as the narrow implementation boundary.


Instruction: Add regression coverage for the case where the token does not preserve the public error contract in the CLI backend. The affected entry point is TokenPolicy47210; 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 token no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

ctest -R TokenRegression47210 --output-on-failure


Instruction: Review the proposed pagination change in the CLI backend for correctness, scope, and regressions. The affected entry point is PaginationPolicy47211; keep the change aligned with the existing layered service 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

go test ./pagination -run PaginationRegression47211

Locate the implementation and callers associated with PaginationPolicy47211.

Search evidence identifies internal/pagination/pagination_472_11.go as the narrow implementation boundary.

Hard tasks require caller evidence to control compatibility risk.

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

correct resource-cleanup defect while preserving the public contract

Obtain executable evidence for the requested behavior.


Instruction: Refactor the cache in the CLI backend to remove duplicated state transitions without changing behavior. The affected entry point is CachePolicy47212; keep the change aligned with the existing layered service 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

npm test -- test/cache/test_cache_472_12.ts

Question: CachePolicy47212|boundary_condition_defect

Locate the implementation and callers associated with CachePolicy47212.

Search evidence identifies src/cache/cache_472_12.ts as the narrow implementation boundary.

correct boundary-condition 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.

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


Instruction: Fix the defect where the queue drops the original error context in the CLI backend. The affected entry point is QueuePolicy47213; keep the change aligned with the existing layered service 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

Question: QueuePolicy47213|error_propagation_defect

Locate the implementation and callers associated with QueuePolicy47213.

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

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

correct error-propagation defect while preserving the public contract


Instruction: Add regression coverage for the case where the webhook fails when an optional field is absent in the CLI backend. The affected entry point is WebhookPolicy47214; keep the change aligned with the existing layered service 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

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

Locate the implementation and callers associated with WebhookPolicy47214.

Search evidence identifies src/webhook/webhook_472_14.php 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.


Instruction: Refactor the permission in the CLI backend to remove duplicated cleanup logic without changing behavior. The affected entry point is PermissionPolicy47215; 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 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_472_15.ts

Locate the implementation and callers associated with PermissionPolicy47215.

Search evidence identifies src/permission/permission_472_15.ts 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.

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.

correct sensitive-data exposure while preserving the public contract

Apply a localized change that follows existing abstractions.

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.

Diff inspection is required before making a completion claim.


Instruction: Add guarded support for bounded retries in the configuration of the CLI backend. The affected entry point is ConfigurationPolicy47216; keep the change aligned with the existing layered service 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

./gradlew test --tests ConfigurationRegression47216

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.

Locate the implementation and callers associated with ConfigurationPolicy47216.

Search evidence identifies src/main/java/configuration/ConfigurationService472.java as the narrow implementation boundary.

Hard tasks require caller evidence to control compatibility risk.

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

correct idempotency defect while preserving the public contract

Obtain executable evidence for the requested behavior.


Instruction: Refactor the parser in the CLI backend to remove duplicated validation logic without changing behavior. The affected entry point is ParserPolicy47217; keep the change aligned with the existing layered service 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: ParserPolicy47217|resource_bounding_defect

correct resource-bounding defect while preserving the public contract


Instruction: Fix the defect where the serializer misclassifies transient failures as permanent in the CLI backend. The affected entry point is SerializerPolicy47218; keep the change aligned with the existing layered service 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

npm test -- test/serializer/test_serializer_472_18.ts

correct failure-classification defect while preserving the public contract


Instruction: Refactor the validator in the CLI backend to remove duplicated error mapping without changing behavior. The affected entry point is ValidatorPolicy47219; keep the change aligned with the existing layered service 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

correct validation-order defect while preserving the public contract


Instruction: Fix the defect where the worker silently truncates an oversized payload in the model evaluation runner. The affected entry point is WorkerPolicy47300; keep the change aligned with the existing modular monolith 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

Question: WorkerPolicy47300|input_size_handling_defect

Locate the implementation and callers associated with WorkerPolicy47300.

Search evidence identifies src/worker/worker_473_00.php 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: Fix the defect where the scheduler does not preserve the public error contract in the model evaluation runner. The affected entry point is SchedulerPolicy47301; keep the change aligned with the existing modular monolith 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

Locate the implementation and callers associated with SchedulerPolicy47301.

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

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.


Instruction: Add regression coverage for the case where the router skips cleanup after cancellation in the model evaluation runner. The affected entry point is RouterPolicy47302; keep the change aligned with the existing modular monolith 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.

Question: RouterPolicy47302|resource_cleanup_defect

Locate the implementation and callers associated with RouterPolicy47302.

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

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

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


Instruction: Add guarded support for audit metadata in the metrics of the model evaluation runner. The affected entry point is MetricsPolicy47303; keep the change aligned with the existing modular monolith 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

Question: MetricsPolicy47303|boundary_condition_defect

Locate the implementation and callers associated with MetricsPolicy47303.

Search evidence identifies src/metrics/metrics_473_03.py as the narrow implementation boundary.


Instruction: Fix the defect where the logging drops the original error context in the model evaluation runner. The affected entry point is LoggingPolicy47304; 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 logging no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

go test ./logging -run LoggingRegression47304

Question: LoggingPolicy47304|error_propagation_defect

Locate the implementation and callers associated with LoggingPolicy47304.

Search evidence identifies internal/logging/logging_473_04.go 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.

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

Produce only evidence-backed findings with severity and confidence.


Instruction: Refactor the sandbox in the model evaluation runner to remove duplicated configuration parsing without changing behavior. The affected entry point is SandboxPolicy47305; keep the change aligned with the existing modular monolith 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

dotnet test --filter SandboxRegression47305

The diff includes a configuration change outside the requested boundary.

Locate the implementation and callers associated with SandboxPolicy47305.

Search evidence identifies src/sandbox/SandboxService473.cs as the narrow implementation boundary.

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

correct nullability defect while preserving the public contract

Apply a localized change that follows existing abstractions.

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.

Diff inspection is required before making a completion claim.


Instruction: Add regression coverage for the case where the session logs a secret-bearing request field in the model evaluation runner. The affected entry point is SessionPolicy47306; keep the change aligned with the existing modular monolith 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

Question: SessionPolicy47306|sensitive_data_exposure

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


Instruction: Add guarded support for safe fallback behavior in the token of the model evaluation runner. The affected entry point is TokenPolicy47307; keep the change aligned with the existing modular monolith 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

npm test -- test/token/test_token_473_07.ts

Locate the implementation and callers associated with TokenPolicy47307.

Search evidence identifies src/token/token_473_07.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.

Hard tasks require caller evidence to control compatibility risk.

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

Obtain executable evidence for the requested behavior.


Instruction: Review the proposed pagination change in the model evaluation runner for correctness, scope, and regressions. The affected entry point is PaginationPolicy47308; keep the change aligned with the existing modular monolith 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

./gradlew test --tests PaginationRegression47308

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 PaginationPolicy47308.

Search evidence identifies src/main/java/pagination/PaginationService473.java as the narrow implementation 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.

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.

revise the failed assumption without expanding scope

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.

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


Instruction: Fix the defect where the cache misclassifies transient failures as permanent in the model evaluation runner. The affected entry point is CachePolicy47309; 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 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: CachePolicy47309|failure_classification_defect

Locate the implementation and callers associated with CachePolicy47309.

Search evidence identifies src/cache/cache_473_09.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.

Identify existing test style and the nearest regression boundary.

Apply a localized change that follows existing abstractions.

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


Instruction: Fix the defect where the queue accepts malformed input after normalization in the model evaluation runner. The affected entry point is QueuePolicy47310; keep the change aligned with the existing modular monolith 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

Question: QueuePolicy47310|validation_order_defect

Locate the implementation and callers associated with QueuePolicy47310.

Search evidence identifies src/queue/queue_473_10.py 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.

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 structured errors in the webhook of the model evaluation runner. The affected entry point is WebhookPolicy47311; keep the change aligned with the existing modular monolith 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

Locate the implementation and callers associated with WebhookPolicy47311.

Search evidence identifies src/webhook/webhook_473_11.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.

Obtain executable evidence for the requested behavior.


Instruction: Fix the defect where the permission mutates shared state across requests in the model evaluation runner. The affected entry point is PermissionPolicy47312; keep the change aligned with the existing modular monolith 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

./gradlew test --tests PermissionRegression47312

Confirm the local module boundary before searching for implementation details.

Locate the implementation and callers associated with PermissionPolicy47312.

Search evidence identifies src/main/java/permission/PermissionService473.java as the narrow implementation boundary.


Instruction: Add guarded support for dry-run mode in the configuration of the model evaluation runner. The affected entry point is ConfigurationPolicy47313; keep the change aligned with the existing modular monolith 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

npm test -- test/configuration/test_configuration_473_13.ts


Instruction: Refactor the parser in the model evaluation runner to remove duplicated state transitions without changing behavior. The affected entry point is ParserPolicy47314; 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 parser no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests ParserRegression47314

Locate the implementation and callers associated with ParserPolicy47314.

Search evidence identifies src/main/java/parser/ParserService473.java as the narrow implementation boundary.

correct false-success defect while preserving the public contract


Instruction: Harden the serializer in the model evaluation runner against authorization bypass while preserving valid behavior. The affected entry point is SerializerPolicy47315; keep the change aligned with the existing modular monolith 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

correct least-privilege defect while preserving the public contract

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


Instruction: Refactor the validator in the model evaluation runner to remove duplicated state transitions without changing behavior. The affected entry point is ValidatorPolicy47316; keep the change aligned with the existing modular monolith 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

npm test -- test/validator/test_validator_473_16.ts

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

Locate the implementation and callers associated with ValidatorPolicy47316.

Search evidence identifies src/validator/validator_473_16.ts as the narrow implementation boundary.

Hard tasks require caller evidence to control compatibility risk.

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

correct verification 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.

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


Instruction: Refactor the retry in the model evaluation runner to remove duplicated cleanup logic without changing behavior. The affected entry point is RetryPolicy47317; keep the change aligned with the existing modular monolith 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

npm test -- test/retry/test_retry_473_17.ts

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

Question: RetryPolicy47317|cache_invalidation_defect

Locate the implementation and callers associated with RetryPolicy47317.

Search evidence identifies src/retry/retry_473_17.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.

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

Apply a localized change that follows existing abstractions.

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


Instruction: Fix the defect where the timeout uses seconds where milliseconds are expected in the model evaluation runner. The affected entry point is TimeoutPolicy47318; keep the change aligned with the existing modular monolith 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

Question: TimeoutPolicy47318|unit_conversion_defect

Locate the implementation and callers associated with TimeoutPolicy47318.

Search evidence identifies src/timeout/timeout_473_18.php as the narrow implementation boundary.

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

correct unit-conversion defect while preserving the public contract

Obtain executable evidence for the requested behavior.

Diff inspection is required before making a completion claim.


Instruction: Add guarded support for safe fallback behavior in the search of the model evaluation runner. The affected entry point is SearchPolicy47319; 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 search no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: SearchPolicy47319|authorization_order_defect

Locate the implementation and callers associated with SearchPolicy47319.

Search evidence identifies src/search/search_473_19.py as the narrow implementation boundary.

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

correct authorization-order defect while preserving the public contract


Instruction: Add guarded support for bounded retries in the metrics of the sandbox controller. The affected entry point is MetricsPolicy47400; keep the change aligned with the existing event-driven worker 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

Confirm the local module boundary before searching for implementation details.

Question: MetricsPolicy47400|failure_classification_defect

Locate the implementation and callers associated with MetricsPolicy47400.

Search evidence identifies src/metrics/metrics_474_00.php 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.


Instruction: Fix the defect where the logging accepts malformed input after normalization in the sandbox controller. The affected entry point is LoggingPolicy47401; 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 logging no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: LoggingPolicy47401|validation_order_defect


Instruction: Refactor the sandbox in the sandbox controller to remove duplicated validation logic without changing behavior. The affected entry point is SandboxPolicy47402; keep the change aligned with the existing event-driven worker 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

npm test -- test/sandbox/test_sandbox_474_02.ts

correct retry-safety defect while preserving the public contract


Instruction: Harden the session in the sandbox controller against secret leakage while preserving valid behavior. The affected entry point is SessionPolicy47403; 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 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_474_03.ts

Question: SessionPolicy47403|state_isolation_defect

Locate the implementation and callers associated with SessionPolicy47403.

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

correct state-isolation defect while preserving the public contract

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 matches identifiers case-insensitively in the sandbox controller. The affected entry point is TokenPolicy47404; 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 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 TokenRegression47404

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

Question: TokenPolicy47404|identity_comparison_defect

Locate the implementation and callers associated with TokenPolicy47404.

Search evidence identifies internal/token/token_474_04.go as the narrow implementation boundary.

Hard tasks require caller evidence to control compatibility risk.

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

correct identity-comparison defect while preserving the public contract


Instruction: Add regression coverage for the case where the pagination marks partial work as successful in the sandbox controller. The affected entry point is PaginationPolicy47405; keep the change aligned with the existing event-driven worker 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

npm test -- test/pagination/test_pagination_474_05.ts

Locate the implementation and callers associated with PaginationPolicy47405.

Search evidence identifies src/pagination/pagination_474_05.ts 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.

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.

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


Instruction: Refactor the cache in the sandbox controller to remove duplicated retry decisions without changing behavior. The affected entry point is CachePolicy47406; 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 cache no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/cache/test_cache_474_06.ts


Instruction: Fix the defect where the queue does not verify the persisted state in the sandbox controller. The affected entry point is QueuePolicy47407; keep the change aligned with the existing event-driven worker 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

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

Locate the implementation and callers associated with QueuePolicy47407.

Search evidence identifies src/queue/queue_474_07.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.

Identify existing test style and the nearest regression boundary.

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

Apply a localized change that follows existing abstractions.

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

Obtain executable evidence for the requested behavior.

Diff inspection is required before making a completion claim.


Instruction: Add regression coverage for the case where the webhook returns stale state after an update in the sandbox controller. The affected entry point is WebhookPolicy47408; 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 webhook no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/webhook/test_webhook_474_08.ts

Question: WebhookPolicy47408|cache_invalidation_defect

correct cache-invalidation defect while preserving the public contract


Instruction: Add guarded support for graceful shutdown in the permission of the sandbox controller. The affected entry point is PermissionPolicy47409; 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 permission no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

ctest -R PermissionRegression47409 --output-on-failure


Instruction: Harden the configuration in the sandbox controller against unsafe deserialization while preserving valid behavior. The affected entry point is ConfigurationPolicy47410; keep the change aligned with the existing event-driven worker 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 ConfigurationPolicy47410.

Search evidence identifies src/configuration/configuration_474_10.php as the narrow implementation boundary.


Instruction: Fix the defect where the parser silently truncates an oversized payload in the sandbox controller. The affected entry point is ParserPolicy47411; 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 parser no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: ParserPolicy47411|input_size_handling_defect

correct input-size handling defect while preserving the public contract


Instruction: Correct the configuration and operator guidance for bounded retries in the sandbox controller. The affected entry point is SerializerPolicy47412; keep the change aligned with the existing event-driven worker 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

Confirm the local module boundary before searching for implementation details.

Locate the implementation and callers associated with SerializerPolicy47412.

Search evidence identifies src/serializer/serializer_474_12.php as the narrow implementation boundary.

correct compatibility defect while preserving the public contract


Instruction: Fix the defect where the validator skips cleanup after cancellation in the sandbox controller. The affected entry point is ValidatorPolicy47413; 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 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 ValidatorPolicy47413.

Search evidence identifies src/validator/validator_474_13.php 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.


Instruction: Add guarded support for request cancellation in the retry of the sandbox controller. The affected entry point is RetryPolicy47414; 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 retry no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

dotnet test --filter RetryRegression47414

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

repair diagnosed cause without broadening scope

Question: RetryPolicy47414|boundary_condition_defect

Locate the implementation and callers associated with RetryPolicy47414.

Search evidence identifies src/retry/RetryService474.cs as the narrow implementation boundary.

correct boundary-condition defect while preserving the public contract


Instruction: Fix the defect where the timeout drops the original error context in the sandbox controller. The affected entry point is TimeoutPolicy47415; keep the change aligned with the existing event-driven worker 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

go test ./timeout -run TimeoutRegression47415

Question: TimeoutPolicy47415|error_propagation_defect

Locate the implementation and callers associated with TimeoutPolicy47415.

Search evidence identifies internal/timeout/timeout_474_15.go 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.

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


Instruction: Harden the search in the sandbox controller against replay attacks while preserving valid behavior. The affected entry point is SearchPolicy47416; 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 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_474_16.ts

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

Locate the implementation and callers associated with SearchPolicy47416.

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

correct nullability 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.

revise the failed assumption without expanding scope

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.

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

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


Instruction: Add regression coverage for the case where the index logs a secret-bearing request field in the sandbox controller. The affected entry point is IndexPolicy47417; keep the change aligned with the existing event-driven worker 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

npm test -- test/index/test_index_474_17.ts

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

Question: IndexPolicy47417|sensitive_data_exposure

Locate the implementation and callers associated with IndexPolicy47417.

Search evidence identifies src/index/index_474_17.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.

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

correct sensitive-data exposure while preserving the public contract

Apply a localized change that follows existing abstractions.

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

Obtain executable evidence for the requested behavior.

Diff inspection is required before making a completion claim.


Instruction: Add regression coverage for the case where the migration creates duplicate jobs under concurrent delivery in the sandbox controller. The affected entry point is MigrationPolicy47418; 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 migration no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/migration/test_migration_474_18.ts

Locate the implementation and callers associated with MigrationPolicy47418.

Search evidence identifies src/migration/migration_474_18.ts as the narrow implementation boundary.

correct idempotency defect while preserving the public contract

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 upload change in the sandbox controller for correctness, scope, and regressions. The affected entry point is UploadPolicy47419; 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 upload no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

ctest -R UploadRegression47419 --output-on-failure

Question: UploadPolicy47419|resource_bounding_defect

Locate the implementation and callers associated with UploadPolicy47419.

Search evidence identifies src/upload/upload_474_19.cpp as the narrow implementation boundary.

correct resource-bounding defect while preserving the public contract