Instruction: Add guarded support for cursor pagination in the index of the job scheduler. The affected entry point is IndexPolicy48509; keep the change aligned with the existing background processor boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

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 IndexRegression48509

Question: IndexPolicy48509|cache_invalidation_defect

Locate the implementation and callers associated with IndexPolicy48509.

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


Instruction: Add guarded support for request cancellation in the migration of the job scheduler. The affected entry point is MigrationPolicy48510; keep the change aligned with the existing background processor boundary.

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

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

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

Search evidence identifies src/migration/migration_485_10.rs 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 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 unit-conversion 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.

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.

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: Harden the upload in the job scheduler against unsafe deserialization while preserving valid behavior. The affected entry point is UploadPolicy48511; keep the change aligned with the existing background processor boundary.

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

The upload no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests UploadRegression48511

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

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

The diff includes a configuration change outside the requested boundary.

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

repair diagnosed cause without broadening scope

Question: UploadPolicy48511|authorization_order_defect

Locate the implementation and callers associated with UploadPolicy48511.

Search evidence identifies src/main/java/upload/UploadService485.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.

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 authorization-order 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: Fix the defect where the download silently truncates an oversized payload in the job scheduler. The affected entry point is DownloadPolicy48512; keep the change aligned with the existing background processor boundary.

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

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 DownloadRegression48512

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: DownloadPolicy48512|input_size_handling_defect

Locate the implementation and callers associated with DownloadPolicy48512.

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

correct input-size handling defect while preserving the public contract


Instruction: Fix the defect where the audit does not preserve the public error contract in the job scheduler. The affected entry point is AuditPolicy48513; keep the change aligned with the existing background processor boundary.

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

The audit 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 AuditPolicy48513.

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

correct compatibility defect while preserving the public contract


Instruction: Fix the defect where the worker skips cleanup after cancellation in the job scheduler. The affected entry point is WorkerPolicy48514; keep the change aligned with the existing background processor boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

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

Question: WorkerPolicy48514|resource_cleanup_defect

Locate the implementation and callers associated with WorkerPolicy48514.

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

correct resource-cleanup defect while preserving the public contract


Instruction: Refactor the scheduler in the job scheduler to remove duplicated state transitions without changing behavior. The affected entry point is SchedulerPolicy48515; keep the change aligned with the existing background processor boundary.

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

The scheduler no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

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

Locate the implementation and callers associated with SchedulerPolicy48515.

Search evidence identifies src/scheduler/scheduler_485_15.py 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 router drops the original error context in the job scheduler. The affected entry point is RouterPolicy48516; keep the change aligned with the existing background processor boundary.

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

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

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

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

Question: RouterPolicy48516|error_propagation_defect

Locate the implementation and callers associated with RouterPolicy48516.

Search evidence identifies src/router/router_485_16.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 error-propagation 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 guarded support for graceful shutdown in the metrics of the job scheduler. The affected entry point is MetricsPolicy48517; keep the change aligned with the existing background processor boundary.

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

The metrics 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.

correct nullability defect while preserving the public contract


Instruction: Fix the defect where the logging logs a secret-bearing request field in the job scheduler. The affected entry point is LoggingPolicy48518; keep the change aligned with the existing background processor boundary.

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

The logging 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: LoggingPolicy48518|sensitive_data_exposure

correct sensitive-data exposure while preserving the public contract


Instruction: Add guarded support for safe fallback behavior in the sandbox of the job scheduler. The affected entry point is SandboxPolicy48519; keep the change aligned with the existing background processor boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

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

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

Locate the implementation and callers associated with SandboxPolicy48519.

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

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

correct idempotency defect while preserving the public contract

Apply a localized change that follows existing abstractions.

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

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

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.

Diff inspection is required before making a completion claim.


Instruction: Add guarded support for bounded retries in the parser of the observability collector. The affected entry point is ParserPolicy48600; keep the change aligned with the existing library package boundary.

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

The parser no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

ctest -R ParserRegression48600 --output-on-failure

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

Confirm the local module boundary before searching for implementation details.

Question: ParserPolicy48600|cache_invalidation_defect

Locate the implementation and callers associated with ParserPolicy48600.

Search evidence identifies src/parser/parser_486_00.cpp as the narrow implementation boundary.


Instruction: Fix the defect where the serializer uses seconds where milliseconds are expected in the observability collector. The affected entry point is SerializerPolicy48601; keep the change aligned with the existing library package boundary.

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

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

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

Hard tasks require caller evidence to control compatibility risk.

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

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


Instruction: Add regression coverage for the case where the validator performs authorization after the side effect in the observability collector. The affected entry point is ValidatorPolicy48602; keep the change aligned with the existing library package boundary.

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

The validator no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

go test ./validator -run ValidatorRegression48602

Respect scope and request approval only for materially risky actions.


Instruction: Add guarded support for structured errors in the retry of the observability collector. The affected entry point is RetryPolicy48603; keep the change aligned with the existing library package boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The retry no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests RetryRegression48603

Use a bounded, updateable plan proportional to task complexity.

Question: RetryPolicy48603|input_size_handling_defect

Locate the implementation and callers associated with RetryPolicy48603.

Search evidence identifies src/main/java/retry/RetryService486.java as the narrow implementation boundary.

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

Identify existing test style and the nearest regression boundary.


Instruction: Fix the defect where the timeout does not preserve the public error contract in the observability collector. The affected entry point is TimeoutPolicy48604; keep the change aligned with the existing library package boundary.

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

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 TimeoutRegression48604

Ground every decision in repository evidence before editing.


Instruction: Add guarded support for dry-run mode in the search of the observability collector. The affected entry point is SearchPolicy48605; keep the change aligned with the existing library package 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

npm test -- test/search/test_search_486_05.ts

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

Question: SearchPolicy48605|resource_cleanup_defect

Locate the implementation and callers associated with SearchPolicy48605.

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

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 explicit timeouts in the index of the observability collector. The affected entry point is IndexPolicy48606; keep the change aligned with the existing library package 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

Question: IndexPolicy48606|boundary_condition_defect

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


Instruction: Fix the defect where the migration drops the original error context in the observability collector. The affected entry point is MigrationPolicy48607; keep the change aligned with the existing library package 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


Instruction: Fix the defect where the upload fails when an optional field is absent in the observability collector. The affected entry point is UploadPolicy48608; keep the change aligned with the existing library package 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

ctest -R UploadRegression48608 --output-on-failure

Locate the implementation and callers associated with UploadPolicy48608.

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

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


Instruction: Add guarded support for graceful shutdown in the download of the observability collector. The affected entry point is DownloadPolicy48609; keep the change aligned with the existing library package 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: DownloadPolicy48609|sensitive_data_exposure

Locate the implementation and callers associated with DownloadPolicy48609.

Search evidence identifies src/download/download_486_09.php as the narrow implementation boundary.

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


Instruction: Add guarded support for per-tenant configuration in the audit of the observability collector. The affected entry point is AuditPolicy48610; keep the change aligned with the existing library package 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

./gradlew test --tests AuditRegression48610

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


Instruction: Correct the configuration and operator guidance for safe fallback behavior in the observability collector. The affected entry point is WorkerPolicy48611; keep the change aligned with the existing library package 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

Question: WorkerPolicy48611|resource_bounding_defect

Locate the implementation and callers associated with WorkerPolicy48611.

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

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

correct resource-bounding 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 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.


Instruction: Refactor the scheduler in the observability collector to remove duplicated authorization checks without changing behavior. The affected entry point is SchedulerPolicy48612; keep the change aligned with the existing library package 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

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

Search evidence identifies src/scheduler/scheduler_486_12.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.

correct failure-classification defect while preserving the public contract

Obtain executable evidence for the requested behavior.


Instruction: Fix the defect where the router accepts malformed input after normalization in the observability collector. The affected entry point is RouterPolicy48613; keep the change aligned with the existing library package 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_486_13.ts

Question: RouterPolicy48613|validation_order_defect

Locate the implementation and callers associated with RouterPolicy48613.

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

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

Identify existing test style and the nearest regression boundary.

correct validation-order defect while preserving the public contract


Instruction: Review the proposed metrics change in the observability collector for correctness, scope, and regressions. The affected entry point is MetricsPolicy48614; keep the change aligned with the existing library package 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

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

Locate the implementation and callers associated with MetricsPolicy48614.

Search evidence identifies src/metrics/metrics_486_14.php 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 retry-safety defect while preserving the public contract


Instruction: Fix the defect where the logging mutates shared state across requests in the observability collector. The affected entry point is LoggingPolicy48615; keep the change aligned with the existing library package 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

go test ./logging -run LoggingRegression48615

Question: LoggingPolicy48615|state_isolation_defect

correct state-isolation defect while preserving the public contract


Instruction: Harden the sandbox in the observability collector against command injection while preserving valid behavior. The affected entry point is SandboxPolicy48616; keep the change aligned with the existing library package 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

Question: SandboxPolicy48616|identity_comparison_defect

Locate the implementation and callers associated with SandboxPolicy48616.

Search evidence identifies src/sandbox/sandbox_486_16.php as the narrow implementation boundary.

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

correct identity-comparison defect while preserving the public contract

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 guarded support for dry-run mode in the session of the observability collector. The affected entry point is SessionPolicy48617; keep the change aligned with the existing library package 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

ctest -R SessionRegression48617 --output-on-failure

correct false-success defect while preserving the public contract


Instruction: Fix the defect where the token uses a broad filesystem permission in the observability collector. The affected entry point is TokenPolicy48618; keep the change aligned with the existing library package 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

./gradlew test --tests TokenRegression48618

Locate the implementation and callers associated with TokenPolicy48618.

Search evidence identifies src/main/java/token/TokenService486.java as the narrow implementation boundary.

correct least-privilege defect while preserving the public contract

Apply a localized change that follows existing abstractions.


Instruction: Harden the pagination in the observability collector against unbounded resource use while preserving valid behavior. The affected entry point is PaginationPolicy48619; keep the change aligned with the existing library package 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

ctest -R PaginationRegression48619 --output-on-failure

Locate the implementation and callers associated with PaginationPolicy48619.

Search evidence identifies src/pagination/pagination_486_19.cpp as the narrow implementation boundary.

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

correct verification defect while preserving the public contract

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


Instruction: Fix the defect where the retry logs a secret-bearing request field in the configuration service. The affected entry point is RetryPolicy48700; 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 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_487_00.ts

Question: RetryPolicy48700|sensitive_data_exposure

Locate the implementation and callers associated with RetryPolicy48700.

Search evidence identifies src/retry/retry_487_00.ts as the narrow implementation boundary.

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: Fix the defect where the timeout creates duplicate jobs under concurrent delivery in the configuration service. The affected entry point is TimeoutPolicy48701; 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 timeout no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

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


Instruction: Add regression coverage for the case where the search loads an unbounded result set in the configuration service. The affected entry point is SearchPolicy48702; keep the change aligned with the existing plugin-based service boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The search no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: SearchPolicy48702|resource_bounding_defect


Instruction: Refactor the index in the configuration service to remove duplicated cleanup logic without changing behavior. The affected entry point is IndexPolicy48703; 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 index no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

go test ./index -run IndexRegression48703

Question: IndexPolicy48703|failure_classification_defect

Locate the implementation and callers associated with IndexPolicy48703.

Search evidence identifies internal/index/index_487_03.go as the narrow implementation boundary.

Diff inspection is required before making a completion claim.


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

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

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 MigrationRegression48704

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

Search evidence identifies src/main/java/migration/MigrationService487.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.

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: Harden the upload in the configuration service against path traversal while preserving valid behavior. The affected entry point is UploadPolicy48705; 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 upload no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

rewrite subsystem
replace dependencies
change API

Use a bounded, updateable plan proportional to task complexity.


Instruction: Review the proposed download change in the configuration service for correctness, scope, and regressions. The affected entry point is DownloadPolicy48706; 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 download no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: DownloadPolicy48706|state_isolation_defect


Instruction: Fix the defect where the audit matches identifiers case-insensitively in the configuration service. The affected entry point is AuditPolicy48707; keep the change aligned with the existing plugin-based 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: AuditPolicy48707|identity_comparison_defect


Instruction: Fix the defect where the worker marks partial work as successful in the configuration service. The affected entry point is WorkerPolicy48708; 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 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_487_08.ts

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

Locate the implementation and callers associated with WorkerPolicy48708.

Search evidence identifies src/worker/worker_487_08.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 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.

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


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

go test ./scheduler -run SchedulerRegression48709

Locate the implementation and callers associated with SchedulerPolicy48709.

Search evidence identifies internal/scheduler/scheduler_487_09.go as the narrow implementation 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 router does not verify the persisted state in the configuration service. The affected entry point is RouterPolicy48710; 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 router no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope


Instruction: Add guarded support for audit metadata in the metrics of the configuration service. The affected entry point is MetricsPolicy48711; 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 metrics no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: MetricsPolicy48711|cache_invalidation_defect

correct cache-invalidation defect while preserving the public contract


Instruction: Add regression coverage for the case where the logging uses seconds where milliseconds are expected in the configuration service. The affected entry point is LoggingPolicy48712; keep the change aligned with the existing plugin-based 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

npm test -- test/logging/test_logging_487_12.ts

Question: LoggingPolicy48712|unit_conversion_defect

Locate the implementation and callers associated with LoggingPolicy48712.

Search evidence identifies src/logging/logging_487_12.ts as the narrow implementation boundary.

correct unit-conversion 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: Fix the defect where the sandbox performs authorization after the side effect in the configuration service. The affected entry point is SandboxPolicy48713; 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 sandbox no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: SandboxPolicy48713|authorization_order_defect

correct authorization-order defect while preserving the public contract

revise the failed assumption without expanding scope


Instruction: Add regression coverage for the case where the session silently truncates an oversized payload in the configuration service. The affected entry point is SessionPolicy48714; keep the change aligned with the existing plugin-based 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

npm test -- test/session/test_session_487_14.ts

Repository evidence contradicts the initial assumption about the data representation.

repair diagnosed cause without broadening scope

Question: SessionPolicy48714|input_size_handling_defect

Locate the implementation and callers associated with SessionPolicy48714.

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

correct input-size handling defect while preserving the public contract

Diff inspection is required before making a completion claim.


Instruction: Fix the defect where the token does not preserve the public error contract in the configuration service. The affected entry point is TokenPolicy48715; 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 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_487_15.ts

Verify the claimed behavior with targeted checks before completion.

Locate the implementation and callers associated with TokenPolicy48715.

Search evidence identifies src/token/token_487_15.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 compatibility 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: Fix the defect where the pagination skips cleanup after cancellation in the configuration service. The affected entry point is PaginationPolicy48716; 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 pagination 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 PaginationPolicy48716.

Search evidence identifies src/pagination/pagination_487_16.py as the narrow implementation boundary.

correct resource-cleanup defect while preserving the public contract


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

Question: CachePolicy48717|boundary_condition_defect

Locate the implementation and callers associated with CachePolicy48717.

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

correct boundary-condition defect while preserving the public contract


Instruction: Fix the defect where the queue drops the original error context in the configuration service. The affected entry point is QueuePolicy48718; 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 queue no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

go test ./queue -run QueueRegression48718

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

Question: QueuePolicy48718|error_propagation_defect

Locate the implementation and callers associated with QueuePolicy48718.

Search evidence identifies internal/queue/queue_487_18.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.

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 error-propagation defect while preserving the public contract

Obtain executable evidence for the requested behavior.

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


Instruction: Refactor the webhook in the configuration service to remove duplicated serialization logic without changing behavior. The affected entry point is WebhookPolicy48719; keep the change aligned with the existing plugin-based 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

go test ./webhook -run WebhookRegression48719

Locate the implementation and callers associated with WebhookPolicy48719.

Search evidence identifies internal/webhook/webhook_487_19.go 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.


Instruction: Add guarded support for idempotency keys in the index of the repository indexer. The affected entry point is IndexPolicy48800; keep the change aligned with the existing layered service boundary.

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

The index 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 IndexPolicy48800.

Search evidence identifies src/index/index_488_00.rs as the narrow implementation boundary.


Instruction: Add guarded support for dry-run mode in the migration of the repository indexer. The affected entry point is MigrationPolicy48801; keep the change aligned with the existing layered service boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The migration no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

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

Locate the implementation and callers associated with MigrationPolicy48801.

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


Instruction: Add guarded support for explicit timeouts in the upload of the repository indexer. The affected entry point is UploadPolicy48802; keep the change aligned with the existing layered service boundary.

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

The upload no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: UploadPolicy48802|cache_invalidation_defect

Locate the implementation and callers associated with UploadPolicy48802.

Search evidence identifies src/upload/upload_488_02.py as the narrow implementation boundary.

Diff inspection is required before making a completion claim.


Instruction: Correct the configuration and operator guidance for audit metadata in the repository indexer. The affected entry point is DownloadPolicy48803; keep the change aligned with the existing layered service boundary.

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

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 DownloadRegression48803

Question: DownloadPolicy48803|unit_conversion_defect

Locate the implementation and callers associated with DownloadPolicy48803.

Search evidence identifies internal/download/download_488_03.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.

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: Harden the audit in the repository indexer against secret leakage while preserving valid behavior. The affected entry point is AuditPolicy48804; 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 audit no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

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: AuditPolicy48804|authorization_order_defect

Locate the implementation and callers associated with AuditPolicy48804.

Search evidence identifies src/audit/audit_488_04.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 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.

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


Instruction: Refactor the worker in the repository indexer to remove duplicated cleanup logic without changing behavior. The affected entry point is WorkerPolicy48805; keep the change aligned with the existing layered service 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

npm test -- test/worker/test_worker_488_05.ts

Question: WorkerPolicy48805|input_size_handling_defect

Locate the implementation and callers associated with WorkerPolicy48805.

Search evidence identifies src/worker/worker_488_05.ts as the narrow implementation 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.

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 scheduler does not preserve the public error contract in the repository indexer. The affected entry point is SchedulerPolicy48806; keep the change aligned with the existing layered service 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


Instruction: Refactor the router in the repository indexer to remove duplicated cleanup logic without changing behavior. The affected entry point is RouterPolicy48807; keep the change aligned with the existing layered service 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

./gradlew test --tests RouterRegression48807

Question: RouterPolicy48807|resource_cleanup_defect

Locate the implementation and callers associated with RouterPolicy48807.

Search evidence identifies src/main/java/router/RouterService488.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.

Diff inspection is required before making a completion claim.


Instruction: Add guarded support for bounded retries in the metrics of the repository indexer. The affected entry point is MetricsPolicy48808; keep the change aligned with the existing layered service 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_488_08.ts

Question: MetricsPolicy48808|boundary_condition_defect


Instruction: Refactor the logging in the repository indexer to remove duplicated validation logic without changing behavior. The affected entry point is LoggingPolicy48809; 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 logging no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/logging/test_logging_488_09.ts

Question: LoggingPolicy48809|error_propagation_defect

Locate the implementation and callers associated with LoggingPolicy48809.

Search evidence identifies src/logging/logging_488_09.ts as the narrow implementation boundary.


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


Instruction: Add guarded support for structured errors in the session of the repository indexer. The affected entry point is SessionPolicy48811; keep the change aligned with the existing layered service 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_488_11.ts

Question: SessionPolicy48811|sensitive_data_exposure

Locate the implementation and callers associated with SessionPolicy48811.

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

correct sensitive-data exposure while preserving the public contract


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

Locate the implementation and callers associated with TokenPolicy48812.

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

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


Instruction: Refactor the pagination in the repository indexer to remove duplicated error mapping without changing behavior. The affected entry point is PaginationPolicy48813; keep the change aligned with the existing layered service 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 PaginationRegression48813

Locate the implementation and callers associated with PaginationPolicy48813.

Search evidence identifies src/main/java/pagination/PaginationService488.java as the narrow implementation boundary.

correct resource-bounding defect while preserving the public contract


Instruction: Fix the defect where the cache misclassifies transient failures as permanent in the repository indexer. The affected entry point is CachePolicy48814; 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 cache no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: CachePolicy48814|failure_classification_defect

Locate the implementation and callers associated with CachePolicy48814.

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

correct failure-classification defect while preserving the public contract


Instruction: Add guarded support for audit metadata in the queue of the repository indexer. The affected entry point is QueuePolicy48815; keep the change aligned with the existing layered service 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

npm test -- test/queue/test_queue_488_15.ts

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

Question: QueuePolicy48815|validation_order_defect

Locate the implementation and callers associated with QueuePolicy48815.

Search evidence identifies src/queue/queue_488_15.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 task spans implementation and verification but does not justify an architectural redesign.

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

correct validation-order defect while preserving the public contract

Obtain executable evidence for the requested behavior.

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


Instruction: Fix the defect where the webhook retries a non-idempotent operation in the repository indexer. The affected entry point is WebhookPolicy48816; keep the change aligned with the existing layered service 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

dotnet test --filter WebhookRegression48816

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

Search evidence identifies src/webhook/WebhookService488.cs as the narrow implementation boundary.

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

correct retry-safety 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.


Instruction: Add guarded support for graceful shutdown in the permission of the repository indexer. The affected entry point is PermissionPolicy48817; keep the change aligned with the existing layered service 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

go test ./permission -run PermissionRegression48817

Locate the implementation and callers associated with PermissionPolicy48817.

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

correct state-isolation 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.


Instruction: Refactor the configuration in the repository indexer to remove duplicated configuration parsing without changing behavior. The affected entry point is ConfigurationPolicy48818; keep the change aligned with the existing layered service 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

dotnet test --filter ConfigurationRegression48818

Locate the implementation and callers associated with ConfigurationPolicy48818.

Search evidence identifies src/configuration/ConfigurationService488.cs 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: Harden the parser in the repository indexer against cross-tenant access while preserving valid behavior. The affected entry point is ParserPolicy48819; 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 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_488_19.ts

Locate the implementation and callers associated with ParserPolicy48819.

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

correct false-success defect while preserving the public contract

revise the failed assumption without expanding scope


Instruction: Fix the defect where the download drops the original error context in the test orchestration service. The affected entry point is DownloadPolicy48900; keep the change aligned with the existing modular monolith boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

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

Question: DownloadPolicy48900|error_propagation_defect


Instruction: Harden the audit in the test orchestration service against cross-tenant access while preserving valid behavior. The affected entry point is AuditPolicy48901; keep the change aligned with the existing modular monolith boundary.

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

The audit no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope


Instruction: Review the proposed worker change in the test orchestration service for correctness, scope, and regressions. The affected entry point is WorkerPolicy48902; keep the change aligned with the existing modular monolith boundary.

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

The worker no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests WorkerRegression48902

Question: WorkerPolicy48902|sensitive_data_exposure

Locate the implementation and callers associated with WorkerPolicy48902.

Search evidence identifies src/main/java/worker/WorkerService489.java as the narrow implementation boundary.

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

Identify existing test style and the nearest regression boundary.


Instruction: Add guarded support for structured errors in the scheduler of the test orchestration service. The affected entry point is SchedulerPolicy48903; 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 scheduler no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests SchedulerRegression48903

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

Locate the implementation and callers associated with SchedulerPolicy48903.

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

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.

Obtain executable evidence for the requested behavior.

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


Instruction: Refactor the router in the test orchestration service to remove duplicated serialization logic without changing behavior. The affected entry point is RouterPolicy48904; keep the change aligned with the existing modular monolith boundary.

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

The router 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: RouterPolicy48904|resource_bounding_defect

Locate the implementation and callers associated with RouterPolicy48904.

Search evidence identifies src/router/router_489_04.php as the narrow implementation boundary.

Apply a localized change that follows existing abstractions.

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 metrics misclassifies transient failures as permanent in the test orchestration service. The affected entry point is MetricsPolicy48905; keep the change aligned with the existing modular monolith 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

Question: MetricsPolicy48905|failure_classification_defect

Locate the implementation and callers associated with MetricsPolicy48905.

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


Instruction: Add regression coverage for the case where the logging accepts malformed input after normalization in the test orchestration service. The affected entry point is LoggingPolicy48906; keep the change aligned with the existing modular monolith 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: LoggingPolicy48906|validation_order_defect

Locate the implementation and callers associated with LoggingPolicy48906.

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

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


Instruction: Add guarded support for audit metadata in the sandbox of the test orchestration service. The affected entry point is SandboxPolicy48907; keep the change aligned with the existing modular monolith 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

./gradlew test --tests SandboxRegression48907


Instruction: Review the proposed session change in the test orchestration service for correctness, scope, and regressions. The affected entry point is SessionPolicy48908; 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 session no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests SessionRegression48908

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

Question: SessionPolicy48908|state_isolation_defect

Locate the implementation and callers associated with SessionPolicy48908.

Search evidence identifies src/main/java/session/SessionService489.java as the narrow implementation boundary.

Diff inspection is required before making a completion claim.


Instruction: Refactor the token in the test orchestration service to remove duplicated cleanup logic without changing behavior. The affected entry point is TokenPolicy48909; keep the change aligned with the existing modular monolith 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 TokenRegression48909

Question: TokenPolicy48909|identity_comparison_defect

Locate the implementation and callers associated with TokenPolicy48909.

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


Instruction: Fix the defect where the pagination marks partial work as successful in the test orchestration service. The affected entry point is PaginationPolicy48910; keep the change aligned with the existing modular monolith 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

./gradlew test --tests PaginationRegression48910

Locate the implementation and callers associated with PaginationPolicy48910.

Search evidence identifies src/main/java/pagination/PaginationService489.java as the narrow implementation boundary.


Instruction: Fix the defect where the cache uses a broad filesystem permission in the test orchestration service. The affected entry point is CachePolicy48911; keep the change aligned with the existing modular monolith 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

correct least-privilege defect while preserving the public contract


Instruction: Refactor the queue in the test orchestration service to remove duplicated validation logic without changing behavior. The affected entry point is QueuePolicy48912; keep the change aligned with the existing modular monolith 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

correct verification defect while preserving the public contract


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

A targeted verification path is identified

The final change remains inside the requested scope

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

repair diagnosed cause without broadening scope

Question: WebhookPolicy48913|cache_invalidation_defect

Locate the implementation and callers associated with WebhookPolicy48913.

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

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

Identify existing test style and the nearest regression boundary.

correct cache-invalidation defect while preserving the public contract


Instruction: Fix the defect where the permission uses seconds where milliseconds are expected in the test orchestration service. The affected entry point is PermissionPolicy48914; keep the change aligned with the existing modular monolith 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

go test ./permission -run PermissionRegression48914

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

Locate the implementation and callers associated with PermissionPolicy48914.

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

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

correct unit-conversion defect while preserving the public contract


Instruction: Fix the defect where the configuration performs authorization after the side effect in the test orchestration service. The affected entry point is ConfigurationPolicy48915; keep the change aligned with the existing modular monolith 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

./gradlew test --tests ConfigurationRegression48915

Locate the implementation and callers associated with ConfigurationPolicy48915.

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

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

correct authorization-order defect while preserving the public contract

Obtain executable evidence for the requested behavior.

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


Instruction: Add guarded support for idempotency keys in the parser of the test orchestration service. The affected entry point is ParserPolicy48916; keep the change aligned with the existing modular monolith 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

go test ./parser -run ParserRegression48916

Respect scope and request approval only for materially risky actions.

Confirm the local module boundary before searching for implementation details.

Question: ParserPolicy48916|input_size_handling_defect

Locate the implementation and callers associated with ParserPolicy48916.

Search evidence identifies internal/parser/parser_489_16.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.

Unnecessary approval requests would reduce agent usefulness without improving safety.

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

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

correct input-size handling 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.


Instruction: Add regression coverage for the case where the serializer does not preserve the public error contract in the test orchestration service. The affected entry point is SerializerPolicy48917; keep the change aligned with the existing modular monolith 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

correct compatibility defect while preserving the public contract


Instruction: Refactor the validator in the test orchestration service to remove duplicated retry decisions without changing behavior. The affected entry point is ValidatorPolicy48918; 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 validator no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

dotnet test --filter ValidatorRegression48918

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

Locate the implementation and callers associated with ValidatorPolicy48918.

Search evidence identifies src/validator/ValidatorService489.cs as the narrow implementation boundary.

correct resource-cleanup defect while preserving the public contract


Instruction: Add guarded support for audit metadata in the retry of the test orchestration service. The affected entry point is RetryPolicy48919; keep the change aligned with the existing modular monolith 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

./gradlew test --tests RetryRegression48919

Question: RetryPolicy48919|boundary_condition_defect

correct boundary-condition defect while preserving the public contract


Instruction: Add regression coverage for the case where the scheduler matches identifiers case-insensitively in the release manager. The affected entry point is SchedulerPolicy49000; 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 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 SchedulerPolicy49000.

Search evidence identifies src/scheduler/scheduler_490_00.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.

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.

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


Instruction: Review the proposed router change in the release manager for correctness, scope, and regressions. The affected entry point is RouterPolicy49001; keep the change aligned with the existing event-driven worker boundary.

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

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

Locate the implementation and callers associated with RouterPolicy49001.

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

Confirm the current control flow, local conventions, and error 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 metrics uses a broad filesystem permission in the release manager. The affected entry point is MetricsPolicy49002; 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 metrics no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: MetricsPolicy49002|least_privilege_defect

Locate the implementation and callers associated with MetricsPolicy49002.

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

Identify existing test style and the nearest regression boundary.


Instruction: Review the proposed logging change in the release manager for correctness, scope, and regressions. The affected entry point is LoggingPolicy49003; 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 logging no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/logging/test_logging_490_03.ts

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

Locate the implementation and callers associated with LoggingPolicy49003.

Search evidence identifies src/logging/logging_490_03.ts as the narrow implementation boundary.

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

Obtain executable evidence for the requested behavior.

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


Instruction: Add guarded support for bounded retries in the sandbox of the release manager. The affected entry point is SandboxPolicy49004; keep the change aligned with the existing event-driven worker boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The sandbox no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: SandboxPolicy49004|cache_invalidation_defect


Instruction: Add guarded support for cursor pagination in the session of the release manager. The affected entry point is SessionPolicy49005; 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 session no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests SessionRegression49005

Question: SessionPolicy49005|unit_conversion_defect

Locate the implementation and callers associated with SessionPolicy49005.

Search evidence identifies src/main/java/session/SessionService490.java 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: Fix the defect where the token performs authorization after the side effect in the release manager. The affected entry point is TokenPolicy49006; keep the change aligned with the existing event-driven worker boundary.

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

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 TokenRegression49006

Question: TokenPolicy49006|authorization_order_defect

Locate the implementation and callers associated with TokenPolicy49006.

Search evidence identifies internal/token/token_490_06.go 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 pagination in the release manager to remove duplicated serialization logic without changing behavior. The affected entry point is PaginationPolicy49007; 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 pagination no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests PaginationRegression49007

Locate the implementation and callers associated with PaginationPolicy49007.

Search evidence identifies src/main/java/pagination/PaginationService490.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.

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: Harden the cache in the release manager against authorization bypass while preserving valid behavior. The affected entry point is CachePolicy49008; 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 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 CacheRegression49008


Instruction: Harden the queue in the release manager against authorization bypass while preserving valid behavior. The affected entry point is QueuePolicy49009; keep the change aligned with the existing event-driven worker 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

Question: QueuePolicy49009|resource_cleanup_defect

Locate the implementation and callers associated with QueuePolicy49009.

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

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


Instruction: Add guarded support for explicit timeouts in the webhook of the release manager. The affected entry point is WebhookPolicy49010; 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 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 WebhookRegression49010

Question: WebhookPolicy49010|boundary_condition_defect

Locate the implementation and callers associated with WebhookPolicy49010.

Search evidence identifies internal/webhook/webhook_490_10.go 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.

Obtain executable evidence for the requested behavior.

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 permission in the release manager to remove duplicated state transitions without changing behavior. The affected entry point is PermissionPolicy49011; keep the change aligned with the existing event-driven worker boundary.

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

The permission 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 PermissionPolicy49011.

Search evidence identifies src/permission/permission_490_11.php as the narrow implementation boundary.

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

correct error-propagation defect while preserving the public contract


Instruction: Add guarded support for input size limits in the configuration of the release manager. The affected entry point is ConfigurationPolicy49012; 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 configuration no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests ConfigurationRegression49012

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

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

correct nullability defect while preserving the public contract


Instruction: Fix the defect where the parser logs a secret-bearing request field in the release manager. The affected entry point is ParserPolicy49013; 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 parser no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: ParserPolicy49013|sensitive_data_exposure

Locate the implementation and callers associated with ParserPolicy49013.

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


Instruction: Add regression coverage for the case where the serializer creates duplicate jobs under concurrent delivery in the release manager. The affected entry point is SerializerPolicy49014; keep the change aligned with the existing event-driven worker boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

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

Locate the implementation and callers associated with SerializerPolicy49014.

Search evidence identifies src/serializer/serializer_490_14.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: Fix the defect where the validator loads an unbounded result set in the release manager. The affected entry point is ValidatorPolicy49015; 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 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 ValidatorPolicy49015.

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

correct resource-bounding defect while preserving the public contract


Instruction: Add regression coverage for the case where the retry misclassifies transient failures as permanent in the release manager. The affected entry point is RetryPolicy49016; keep the change aligned with the existing event-driven worker boundary.

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

The retry no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests RetryRegression49016

Question: RetryPolicy49016|failure_classification_defect

Locate the implementation and callers associated with RetryPolicy49016.

Search evidence identifies src/main/java/retry/RetryService490.java as the narrow implementation boundary.

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

correct failure-classification 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: Refactor the timeout in the release manager to remove duplicated validation logic without changing behavior. The affected entry point is TimeoutPolicy49017; 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 timeout no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: TimeoutPolicy49017|validation_order_defect

Locate the implementation and callers associated with TimeoutPolicy49017.

Search evidence identifies src/timeout/timeout_490_17.py 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.

correct validation-order defect while preserving the public contract


Instruction: Review the proposed search change in the release manager for correctness, scope, and regressions. The affected entry point is SearchPolicy49018; 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 search no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests SearchRegression49018

Locate the implementation and callers associated with SearchPolicy49018.

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

Identify existing test style and the nearest regression boundary.

correct retry-safety defect while preserving the public contract

Obtain executable evidence for the requested behavior.