Instruction: Add regression coverage for the case where the index mutates shared state across requests in the release manager. The affected entry point is IndexPolicy49019; keep the change aligned with the existing event-driven worker 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

npm test -- test/index/test_index_490_19.ts

Locate the implementation and callers associated with IndexPolicy49019.

Search evidence identifies src/index/index_490_19.ts as the narrow implementation boundary.

correct state-isolation defect while preserving the public contract

Hard tasks require caller evidence to control compatibility risk.

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

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


Instruction: Fix the defect where the logging skips cleanup after cancellation in the knowledge graph API. The affected entry point is LoggingPolicy49100; keep the change aligned with the existing CLI application 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 LoggingRegression49100

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

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: LoggingPolicy49100|resource_cleanup_defect

Locate the implementation and callers associated with LoggingPolicy49100.

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

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.

Diff inspection is required before making a completion claim.

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


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

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

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

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

Question: SandboxPolicy49101|boundary_condition_defect

correct boundary-condition defect while preserving the public contract


Instruction: Refactor the session in the knowledge graph API to remove duplicated retry decisions without changing behavior. The affected entry point is SessionPolicy49102; keep the change aligned with the existing CLI application 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

go test ./session -run SessionRegression49102

Use a bounded, updateable plan proportional to task complexity.

Question: SessionPolicy49102|error_propagation_defect

confirm behavior
apply bounded patch
run targeted test
inspect diff

correct error-propagation defect while preserving the public contract

rewrite subsystem
replace dependencies
change API


Instruction: Add guarded support for audit metadata in the token of the knowledge graph API. The affected entry point is TokenPolicy49103; keep the change aligned with the existing CLI application 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 TokenRegression49103

Respect scope and request approval only for materially risky actions.

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

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

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

repair diagnosed cause without broadening scope

Locate the implementation and callers associated with TokenPolicy49103.

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

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

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

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 pagination logs a secret-bearing request field in the knowledge graph API. The affected entry point is PaginationPolicy49104; keep the change aligned with the existing CLI application 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

Use a bounded, updateable plan proportional to task complexity.

Locate the implementation and callers associated with PaginationPolicy49104.

Search evidence identifies src/pagination/pagination_491_04.rs 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.

correct sensitive-data exposure while preserving the public contract

Apply a localized change that follows existing abstractions.

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

Obtain executable evidence for the requested behavior.


Instruction: Add regression coverage for the case where the cache creates duplicate jobs under concurrent delivery in the knowledge graph API. The affected entry point is CachePolicy49105; keep the change aligned with the existing CLI application boundary.

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

The cache no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Locate the implementation and callers associated with CachePolicy49105.

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

correct idempotency defect while preserving the public contract

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

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


Instruction: Add guarded support for per-tenant configuration in the queue of the knowledge graph API. The affected entry point is QueuePolicy49106; keep the change aligned with the existing CLI application boundary.

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

The queue no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

ctest -R QueueRegression49106 --output-on-failure

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

Question: QueuePolicy49106|resource_bounding_defect

correct resource-bounding defect while preserving the public contract


Instruction: Add regression coverage for the case where the webhook misclassifies transient failures as permanent in the knowledge graph API. The affected entry point is WebhookPolicy49107; keep the change aligned with the existing CLI application boundary.

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

The webhook no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/webhook/test_webhook_491_07.ts

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

Question: WebhookPolicy49107|failure_classification_defect

Locate the implementation and callers associated with WebhookPolicy49107.

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


Instruction: Review the proposed permission change in the knowledge graph API for correctness, scope, and regressions. The affected entry point is PermissionPolicy49108; keep the change aligned with the existing CLI application boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The permission no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

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

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

Locate the implementation and callers associated with PermissionPolicy49108.

Search evidence identifies src/permission/permission_491_08.py as the narrow implementation boundary.

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

Question: authorize|permission|sanitize|validate

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

correct validation-order defect while preserving the public contract

The first targeted test fails and provides a concrete counterexample.

Repeating the same patch would ignore the new test evidence.

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

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

revise the failed assumption without expanding scope

Apply the second bounded patch addressing the diagnosed cause.

The repaired behavior must be re-executed before completion.

Confirm the revised patch satisfies the original acceptance criterion.

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


Instruction: Fix the defect where the configuration retries a non-idempotent operation in the knowledge graph API. The affected entry point is ConfigurationPolicy49109; keep the change aligned with the existing CLI application boundary.

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

The configuration no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

go test ./configuration -run ConfigurationRegression49109

Verify the claimed behavior with targeted checks before completion.

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

Locate the implementation and callers associated with ConfigurationPolicy49109.

Search evidence identifies internal/configuration/configuration_491_09.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.

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

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 regression coverage for the case where the parser mutates shared state across requests in the knowledge graph API. The affected entry point is ParserPolicy49110; keep the change aligned with the existing CLI application 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

Question: ParserPolicy49110|state_isolation_defect

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


Instruction: Fix the defect where the serializer matches identifiers case-insensitively in the knowledge graph API. The affected entry point is SerializerPolicy49111; keep the change aligned with the existing CLI application boundary.

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

The 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_491_11.ts

correct identity-comparison defect while preserving the public contract


Instruction: Refactor the validator in the knowledge graph API to remove duplicated serialization logic without changing behavior. The affected entry point is ValidatorPolicy49112; keep the change aligned with the existing CLI application 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

./gradlew test --tests ValidatorRegression49112

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

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

Search evidence identifies src/main/java/validator/ValidatorService491.java as the narrow implementation boundary.

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

correct false-success 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.


Instruction: Add guarded support for dry-run mode in the retry of the knowledge graph API. The affected entry point is RetryPolicy49113; keep the change aligned with the existing CLI application 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

Ground every decision in repository evidence before editing.

Locate the implementation and callers associated with RetryPolicy49113.

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


Instruction: Fix the defect where the timeout does not verify the persisted state in the knowledge graph API. The affected entry point is TimeoutPolicy49114; keep the change aligned with the existing CLI application 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

correct verification defect while preserving the public contract


Instruction: Fix the defect where the search returns stale state after an update in the knowledge graph API. The affected entry point is SearchPolicy49115; keep the change aligned with the existing CLI application 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

go test ./search -run SearchRegression49115

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

Question: SearchPolicy49115|cache_invalidation_defect

Locate the implementation and callers associated with SearchPolicy49115.

Search evidence identifies internal/search/search_491_15.go as the narrow implementation boundary.

correct cache-invalidation 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: Correct the configuration and operator guidance for input size limits in the knowledge graph API. The affected entry point is IndexPolicy49116; keep the change aligned with the existing CLI application boundary.

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

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

Locate the implementation and callers associated with IndexPolicy49116.

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

correct unit-conversion defect while preserving the public contract


Instruction: Fix the defect where the migration performs authorization after the side effect in the knowledge graph API. The affected entry point is MigrationPolicy49117; keep the change aligned with the existing CLI application boundary.

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

The migration no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests MigrationRegression49117

The diff includes a configuration change outside the requested boundary.

Locate the implementation and callers associated with MigrationPolicy49117.

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

correct authorization-order defect while preserving the public contract


Instruction: Harden the upload in the knowledge graph API against cross-tenant access while preserving valid behavior. The affected entry point is UploadPolicy49118; keep the change aligned with the existing CLI application boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The upload no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/upload/test_upload_491_18.ts

Repository evidence contradicts the initial assumption about the data representation.

Question: UploadPolicy49118|input_size_handling_defect

Locate the implementation and callers associated with UploadPolicy49118.

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

correct input-size handling defect while preserving the public contract

The first targeted test fails and provides a concrete counterexample.

Repeating the same patch would ignore the new test evidence.

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

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

Apply the second bounded patch addressing the diagnosed cause.

The repaired behavior must be re-executed before completion.

Confirm the revised patch satisfies the original acceptance criterion.

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


Instruction: Add guarded support for safe fallback behavior in the download of the knowledge graph API. The affected entry point is DownloadPolicy49119; keep the change aligned with the existing CLI application 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

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

Question: DownloadPolicy49119|compatibility_defect

Locate the implementation and callers associated with DownloadPolicy49119.

Search evidence identifies src/download/download_491_19.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.

Hard tasks require caller evidence to control compatibility risk.

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

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

Produce only evidence-backed findings with severity and confidence.

Diff inspection is required before making a completion claim.

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


Instruction: Add regression coverage for the case where the token retries a non-idempotent operation in the session service. The affected entry point is TokenPolicy49200; keep the change aligned with the existing HTTP API 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

go test ./token -run TokenRegression49200

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

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

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

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

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

Apply a localized change that follows existing abstractions.

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

Obtain executable evidence for the requested behavior.

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 cursor pagination in the pagination of the session service. The affected entry point is PaginationPolicy49201; keep the change aligned with the existing HTTP API 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

Respect scope and request approval only for materially risky actions.

Locate the implementation and callers associated with PaginationPolicy49201.

Search evidence identifies src/pagination/pagination_492_01.rs as the narrow implementation boundary.

Unnecessary approval requests would reduce agent usefulness without improving safety.

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

correct state-isolation defect while preserving the public contract


Instruction: Correct the configuration and operator guidance for request cancellation in the session service. The affected entry point is CachePolicy49202; keep the change aligned with the existing HTTP API 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: CachePolicy49202|identity_comparison_defect

Locate the implementation and callers associated with CachePolicy49202.

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


Instruction: Add guarded support for structured errors in the queue of the session service. The affected entry point is QueuePolicy49203; keep the change aligned with the existing HTTP API 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

repair diagnosed cause without broadening scope

Locate the implementation and callers associated with QueuePolicy49203.

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

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


Instruction: Add regression coverage for the case where the webhook uses a broad filesystem permission in the session service. The affected entry point is WebhookPolicy49204; keep the change aligned with the existing HTTP API 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

./gradlew test --tests WebhookRegression49204

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

Question: WebhookPolicy49204|least_privilege_defect

Locate the implementation and callers associated with WebhookPolicy49204.

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

Diff inspection is required before making a completion claim.


Instruction: Add guarded support for dry-run mode in the permission of the session service. The affected entry point is PermissionPolicy49205; keep the change aligned with the existing HTTP API boundary.

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

The permission no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/permission/test_permission_492_05.ts

Locate the implementation and callers associated with PermissionPolicy49205.

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

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

Apply a localized change that follows existing abstractions.

Obtain executable evidence for the requested behavior.

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


Instruction: Add guarded support for explicit timeouts in the configuration of the session service. The affected entry point is ConfigurationPolicy49206; keep the change aligned with the existing HTTP API boundary.

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

The configuration no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests ConfigurationRegression49206


Instruction: Fix the defect where the parser uses seconds where milliseconds are expected in the session service. The affected entry point is ParserPolicy49207; keep the change aligned with the existing HTTP API boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The parser no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/parser/test_parser_492_07.ts

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

Question: ParserPolicy49207|unit_conversion_defect

Locate the implementation and callers associated with ParserPolicy49207.

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


Instruction: Refactor the serializer in the session service to remove duplicated retry decisions without changing behavior. The affected entry point is SerializerPolicy49208; keep the change aligned with the existing HTTP API boundary.

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

The serializer no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/serializer/test_serializer_492_08.ts

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

Confirm the local module boundary before searching for implementation details.

Locate the implementation and callers associated with SerializerPolicy49208.

Search evidence identifies src/serializer/serializer_492_08.ts as the narrow implementation boundary.

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

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

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


Instruction: Review the proposed validator change in the session service for correctness, scope, and regressions. The affected entry point is ValidatorPolicy49209; keep the change aligned with the existing HTTP API boundary.

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

The validator no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Locate the implementation and callers associated with ValidatorPolicy49209.

Search evidence identifies src/validator/validator_492_09.py 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.

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

Check static constraints relevant to the modified code.


Instruction: Review the proposed retry change in the session service for correctness, scope, and regressions. The affected entry point is RetryPolicy49210; keep the change aligned with the existing HTTP API 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

Locate the implementation and callers associated with RetryPolicy49210.

Search evidence identifies src/retry/retry_492_10.php as the narrow implementation boundary.

correct compatibility defect while preserving the public contract

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

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


Instruction: Fix the defect where the timeout skips cleanup after cancellation in the session service. The affected entry point is TimeoutPolicy49211; keep the change aligned with the existing HTTP API 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

npm test -- test/timeout/test_timeout_492_11.ts

Question: TimeoutPolicy49211|resource_cleanup_defect

correct resource-cleanup defect while preserving the public contract

Ground every decision in repository evidence before editing.


Instruction: Fix the defect where the search rejects valid boundary values in the session service. The affected entry point is SearchPolicy49212; keep the change aligned with the existing HTTP API 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

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

Question: SearchPolicy49212|boundary_condition_defect

Locate the implementation and callers associated with SearchPolicy49212.

Search evidence identifies src/search/search_492_12.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.

correct boundary-condition defect while preserving the public contract

Diff inspection is required before making a completion claim.


Instruction: Fix the defect where the index drops the original error context in the session service. The affected entry point is IndexPolicy49213; keep the change aligned with the existing HTTP API 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

Question: IndexPolicy49213|error_propagation_defect

Locate the implementation and callers associated with IndexPolicy49213.

Search evidence identifies src/index/index_492_13.py as the narrow implementation 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.


Instruction: Add guarded support for request cancellation in the migration of the session service. The affected entry point is MigrationPolicy49214; keep the change aligned with the existing HTTP API 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

npm test -- test/migration/test_migration_492_14.ts

Locate the implementation and callers associated with MigrationPolicy49214.

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

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

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

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.

Obtain executable evidence for the requested behavior.


Instruction: Add guarded support for structured errors in the upload of the session service. The affected entry point is UploadPolicy49215; keep the change aligned with the existing HTTP API boundary.

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

The upload no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/upload/test_upload_492_15.ts

Question: UploadPolicy49215|sensitive_data_exposure

Locate the implementation and callers associated with UploadPolicy49215.

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

correct sensitive-data exposure while preserving the public contract

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


Instruction: Fix the defect where the download creates duplicate jobs under concurrent delivery in the session service. The affected entry point is DownloadPolicy49216; keep the change aligned with the existing HTTP API 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

dotnet test --filter DownloadRegression49216

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

Search evidence identifies src/download/DownloadService492.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 idempotency defect while preserving the public contract

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


Instruction: Add regression coverage for the case where the audit loads an unbounded result set in the session service. The affected entry point is AuditPolicy49217; keep the change aligned with the existing HTTP API 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

npm test -- test/audit/test_audit_492_17.ts

Report changed behavior, verification evidence, and remaining uncertainty precisely.

Question: AuditPolicy49217|resource_bounding_defect

correct resource-bounding defect while preserving the public contract


Instruction: Correct the configuration and operator guidance for explicit timeouts in the session service. The affected entry point is WorkerPolicy49218; keep the change aligned with the existing HTTP API 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

Question: WorkerPolicy49218|failure_classification_defect

Locate the implementation and callers associated with WorkerPolicy49218.

Search evidence identifies src/worker/worker_492_18.py 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 failure-classification defect while preserving the public contract


Instruction: Harden the scheduler in the session service against path traversal while preserving valid behavior. The affected entry point is SchedulerPolicy49219; keep the change aligned with the existing HTTP API 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 SchedulerRegression49219

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

Locate the implementation and callers associated with SchedulerPolicy49219.

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

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

Diff inspection is required before making a completion claim.


Instruction: Fix the defect where the queue silently truncates an oversized payload in the rate-limit gateway. The affected entry point is QueuePolicy49300; keep the change aligned with the existing background processor 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

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

Question: QueuePolicy49300|input_size_handling_defect

Locate the implementation and callers associated with QueuePolicy49300.

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

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


Instruction: Review the proposed webhook change in the rate-limit gateway for correctness, scope, and regressions. The affected entry point is WebhookPolicy49301; keep the change aligned with the existing background processor boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The webhook no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests WebhookRegression49301

Locate the implementation and callers associated with WebhookPolicy49301.

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

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

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: Refactor the permission in the rate-limit gateway to remove duplicated cleanup logic without changing behavior. The affected entry point is PermissionPolicy49302; keep the change aligned with the existing background processor 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

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


Instruction: Fix the defect where the configuration rejects valid boundary values in the rate-limit gateway. The affected entry point is ConfigurationPolicy49303; keep the change aligned with the existing background processor 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

./gradlew test --tests ConfigurationRegression49303

Locate the implementation and callers associated with ConfigurationPolicy49303.

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

Obtain executable evidence for the requested behavior.


Instruction: Refactor the parser in the rate-limit gateway to remove duplicated validation logic without changing behavior. The affected entry point is ParserPolicy49304; 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 parser no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

ctest -R ParserRegression49304 --output-on-failure

Question: ParserPolicy49304|error_propagation_defect

Locate the implementation and callers associated with ParserPolicy49304.

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


Instruction: Fix the defect where the serializer fails when an optional field is absent in the rate-limit gateway. The affected entry point is SerializerPolicy49305; keep the change aligned with the existing background processor boundary.

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

The serializer no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/serializer/test_serializer_493_05.ts

Locate the implementation and callers associated with SerializerPolicy49305.

Search evidence identifies src/serializer/serializer_493_05.ts as the narrow implementation boundary.

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


Instruction: Refactor the validator in the rate-limit gateway to remove duplicated validation logic without changing behavior. The affected entry point is ValidatorPolicy49306; keep the change aligned with the existing background processor boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The validator no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/validator/test_validator_493_06.ts

Locate the implementation and callers associated with ValidatorPolicy49306.

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

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

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

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


Instruction: Fix the defect where the retry creates duplicate jobs under concurrent delivery in the rate-limit gateway. The affected entry point is RetryPolicy49307; keep the change aligned with the existing background processor boundary.

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

The retry no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests RetryRegression49307

Locate the implementation and callers associated with RetryPolicy49307.

Search evidence identifies src/main/java/retry/RetryService493.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: Harden the timeout in the rate-limit gateway against authorization bypass while preserving valid behavior. The affected entry point is TimeoutPolicy49308; keep the change aligned with the existing background processor boundary.

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

The timeout no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

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: TimeoutPolicy49308|resource_bounding_defect

Locate the implementation and callers associated with TimeoutPolicy49308.

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

Diff inspection is required before making a completion claim.


Instruction: Add regression coverage for the case where the search misclassifies transient failures as permanent in the rate-limit gateway. The affected entry point is SearchPolicy49309; 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 search no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: SearchPolicy49309|failure_classification_defect


Instruction: Harden the index in the rate-limit gateway against secret leakage while preserving valid behavior. The affected entry point is IndexPolicy49310; keep the change aligned with the existing background processor 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

Question: IndexPolicy49310|validation_order_defect

Locate the implementation and callers associated with IndexPolicy49310.

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

Question: authorize|permission|sanitize|validate

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


Instruction: Add guarded support for audit metadata in the migration of the rate-limit gateway. The affected entry point is MigrationPolicy49311; keep the change aligned with the existing background processor 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

npm test -- test/migration/test_migration_493_11.ts

Locate the implementation and callers associated with MigrationPolicy49311.

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

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

correct retry-safety defect while preserving the public contract


Instruction: Refactor the upload in the rate-limit gateway to remove duplicated retry decisions without changing behavior. The affected entry point is UploadPolicy49312; keep the change aligned with the existing background processor 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: UploadPolicy49312|state_isolation_defect

Locate the implementation and callers associated with UploadPolicy49312.

Search evidence identifies src/upload/upload_493_12.php as the narrow implementation boundary.

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

Produce only evidence-backed findings with severity and confidence.


Instruction: Refactor the download in the rate-limit gateway to remove duplicated configuration parsing without changing behavior. The affected entry point is DownloadPolicy49313; keep the change aligned with the existing background processor 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

./gradlew test --tests DownloadRegression49313

Question: DownloadPolicy49313|identity_comparison_defect

Locate the implementation and callers associated with DownloadPolicy49313.

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

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

correct identity-comparison 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.


Instruction: Add regression coverage for the case where the audit marks partial work as successful in the rate-limit gateway. The affected entry point is AuditPolicy49314; 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 audit no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

go test ./audit -run AuditRegression49314

Locate the implementation and callers associated with AuditPolicy49314.

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

correct false-success defect while preserving the public contract

The first targeted test fails and provides a concrete counterexample.

Repeating the same patch would ignore the new test evidence.

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

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

Apply the second bounded patch addressing the diagnosed cause.

The repaired behavior must be re-executed before completion.

Confirm the revised patch satisfies the original acceptance criterion.

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

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


Instruction: Add regression coverage for the case where the worker uses a broad filesystem permission in the rate-limit gateway. The affected entry point is WorkerPolicy49315; keep the change aligned with the existing background processor 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_493_15.ts

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

Question: WorkerPolicy49315|least_privilege_defect

Locate the implementation and callers associated with WorkerPolicy49315.

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

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

Diff inspection is required before making a completion claim.


Instruction: Fix the defect where the scheduler does not verify the persisted state in the rate-limit gateway. The affected entry point is SchedulerPolicy49316; keep the change aligned with the existing background processor 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

./gradlew test --tests SchedulerRegression49316

correct verification defect while preserving the public contract


Instruction: Refactor the router in the rate-limit gateway to remove duplicated authorization checks without changing behavior. The affected entry point is RouterPolicy49317; keep the change aligned with the existing background processor 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

npm test -- test/router/test_router_493_17.ts

Question: RouterPolicy49317|cache_invalidation_defect

correct cache-invalidation defect while preserving the public contract


Instruction: Fix the defect where the metrics uses seconds where milliseconds are expected in the rate-limit gateway. The affected entry point is MetricsPolicy49318; keep the change aligned with the existing background processor 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

go test ./metrics -run MetricsRegression49318

Question: MetricsPolicy49318|unit_conversion_defect

correct unit-conversion defect while preserving the public contract

Verify the claimed behavior with targeted checks before completion.


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

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests LoggingRegression49319

Question: LoggingPolicy49319|authorization_order_defect

Locate the implementation and callers associated with LoggingPolicy49319.

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

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


Instruction: Harden the configuration in the webhook dispatcher against unsafe deserialization while preserving valid behavior. The affected entry point is ConfigurationPolicy49400; keep the change aligned with the existing library package 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

npm test -- test/configuration/test_configuration_494_00.ts

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

Confirm the local module boundary before searching for implementation details.

Locate the implementation and callers associated with ConfigurationPolicy49400.

Search evidence identifies src/configuration/configuration_494_00.ts as the narrow implementation boundary.

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

Apply a localized change that follows existing abstractions.

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


Instruction: Add guarded support for dry-run mode in the parser of the webhook dispatcher. The affected entry point is ParserPolicy49401; keep the change aligned with the existing library package boundary.

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

The parser no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/parser/test_parser_494_01.ts

Question: ParserPolicy49401|validation_order_defect

Locate the implementation and callers associated with ParserPolicy49401.

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

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

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


Instruction: Refactor the serializer in the webhook dispatcher to remove duplicated state transitions without changing behavior. The affected entry point is SerializerPolicy49402; keep the change aligned with the existing library package 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

npm test -- test/serializer/test_serializer_494_02.ts

Locate the implementation and callers associated with SerializerPolicy49402.

Search evidence identifies src/serializer/serializer_494_02.ts as the narrow implementation boundary.

Obtain executable evidence for the requested behavior.


Instruction: Add guarded support for audit metadata in the validator of the webhook dispatcher. The affected entry point is ValidatorPolicy49403; 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 validator no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/validator/test_validator_494_03.ts

correct state-isolation defect while preserving the public contract

revise the failed assumption without expanding scope


Instruction: Fix the defect where the retry matches identifiers case-insensitively in the webhook dispatcher. The affected entry point is RetryPolicy49404; keep the change aligned with the existing library package 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

Question: RetryPolicy49404|identity_comparison_defect

Locate the implementation and callers associated with RetryPolicy49404.

Search evidence identifies src/retry/retry_494_04.php as the narrow implementation boundary.


Instruction: Add regression coverage for the case where the timeout marks partial work as successful in the webhook dispatcher. The affected entry point is TimeoutPolicy49405; keep the change aligned with the existing library package boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The timeout no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests TimeoutRegression49405

Locate the implementation and callers associated with TimeoutPolicy49405.

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

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

Check static constraints relevant to the modified code.

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


Instruction: Correct the configuration and operator guidance for per-tenant configuration in the webhook dispatcher. The affected entry point is SearchPolicy49406; keep the change aligned with the existing library package boundary.

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

The search no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests SearchRegression49406

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

Question: SearchPolicy49406|least_privilege_defect

Locate the implementation and callers associated with SearchPolicy49406.

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

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

Produce only evidence-backed findings with severity and confidence.

Diff inspection is required before making a completion claim.


Instruction: Add guarded support for safe fallback behavior in the index of the webhook dispatcher. The affected entry point is IndexPolicy49407; keep the change aligned with the existing library package boundary.

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

The index no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Locate the implementation and callers associated with IndexPolicy49407.

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


Instruction: Fix the defect where the migration returns stale state after an update in the webhook dispatcher. The affected entry point is MigrationPolicy49408; 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 migration no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/migration/test_migration_494_08.ts


Instruction: Harden the upload in the webhook dispatcher against replay attacks while preserving valid behavior. The affected entry point is UploadPolicy49409; keep the change aligned with the existing library package boundary.

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

The upload no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/upload/test_upload_494_09.ts

Question: UploadPolicy49409|unit_conversion_defect

Locate the implementation and callers associated with UploadPolicy49409.

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


Instruction: Fix the defect where the download performs authorization after the side effect in the webhook dispatcher. The affected entry point is DownloadPolicy49410; keep the change aligned with the existing library package 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

Question: DownloadPolicy49410|authorization_order_defect

Locate the implementation and callers associated with DownloadPolicy49410.

Search evidence identifies src/download/download_494_10.py as the narrow implementation boundary.

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

Hard tasks require caller evidence to control compatibility risk.

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

Apply a localized change that follows existing abstractions.

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: Harden the audit in the webhook dispatcher against cross-tenant access while preserving valid behavior. The affected entry point is AuditPolicy49411; keep the change aligned with the existing library package 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

Question: AuditPolicy49411|input_size_handling_defect

Locate the implementation and callers associated with AuditPolicy49411.

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

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

correct input-size handling defect while preserving the public contract

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

Question: authorize|permission|sanitize|validate

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

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.

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


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

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

Confirm the local module boundary before searching for implementation details.

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

Locate the implementation and callers associated with WorkerPolicy49412.

Search evidence identifies src/worker/worker_494_12.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 compatibility defect while preserving the public contract

Obtain executable evidence for the requested behavior.

Diff inspection is required before making a completion claim.


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

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/scheduler/test_scheduler_494_13.ts

Locate the implementation and callers associated with SchedulerPolicy49413.

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

correct resource-cleanup 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: Add guarded support for explicit timeouts in the router of the webhook dispatcher. The affected entry point is RouterPolicy49414; keep the change aligned with the existing library package 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

npm test -- test/router/test_router_494_14.ts

repair diagnosed cause without broadening scope

Question: RouterPolicy49414|boundary_condition_defect

Locate the implementation and callers associated with RouterPolicy49414.

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

correct boundary-condition defect while preserving the public contract

Apply a localized change that follows existing abstractions.


Instruction: Add guarded support for audit metadata in the metrics of the webhook dispatcher. The affected entry point is MetricsPolicy49415; keep the change aligned with the existing library package 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: MetricsPolicy49415|error_propagation_defect

Locate the implementation and callers associated with MetricsPolicy49415.

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

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

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

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 logging fails when an optional field is absent in the webhook dispatcher. The affected entry point is LoggingPolicy49416; keep the change aligned with the existing library package 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

./gradlew test --tests LoggingRegression49416

Locate the implementation and callers associated with LoggingPolicy49416.

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

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


Instruction: Review the proposed sandbox change in the webhook dispatcher for correctness, scope, and regressions. The affected entry point is SandboxPolicy49417; keep the change aligned with the existing library package boundary.

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

The sandbox no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/sandbox/test_sandbox_494_17.ts

Question: SandboxPolicy49417|sensitive_data_exposure

Locate the implementation and callers associated with SandboxPolicy49417.

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

Unnecessary approval requests would reduce agent usefulness without improving safety.

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

correct sensitive-data exposure while preserving the public contract

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

Question: authorize|permission|sanitize|validate

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

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


Instruction: Fix the defect where the session creates duplicate jobs under concurrent delivery in the webhook dispatcher. The affected entry point is SessionPolicy49418; 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 session no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

go test ./session -run SessionRegression49418

Locate the implementation and callers associated with SessionPolicy49418.

Search evidence identifies internal/session/session_494_18.go as the narrow implementation boundary.

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

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


Instruction: Add guarded support for safe fallback behavior in the token of the webhook dispatcher. The affected entry point is TokenPolicy49419; keep the change aligned with the existing library package 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

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

Question: TokenPolicy49419|resource_bounding_defect

Locate the implementation and callers associated with TokenPolicy49419.

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

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

correct resource-bounding defect while preserving the public contract

Obtain executable evidence for the requested behavior.

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

Check static constraints relevant to the modified code.


Instruction: Add regression coverage for the case where the validator uses seconds where milliseconds are expected in the access-control service. The affected entry point is ValidatorPolicy49500; 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 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 ValidatorRegression49500

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

Search evidence identifies internal/validator/validator_495_00.go as the narrow implementation boundary.

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

Identify existing test style and the nearest regression boundary.

Apply a localized change that follows existing abstractions.

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 retry performs authorization after the side effect in the access-control service. The affected entry point is RetryPolicy49501; keep the change aligned with the existing plugin-based service 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

Question: RetryPolicy49501|authorization_order_defect


Instruction: Refactor the timeout in the access-control service to remove duplicated authorization checks without changing behavior. The affected entry point is TimeoutPolicy49502; 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 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 TimeoutRegression49502

Question: TimeoutPolicy49502|input_size_handling_defect

Locate the implementation and callers associated with TimeoutPolicy49502.

Search evidence identifies internal/timeout/timeout_495_02.go as the narrow implementation boundary.

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

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


Instruction: Refactor the search in the access-control service to remove duplicated serialization logic without changing behavior. The affected entry point is SearchPolicy49503; 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 search no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Respect scope and request approval only for materially risky actions.


Instruction: Correct the configuration and operator guidance for idempotency keys in the access-control service. The affected entry point is IndexPolicy49504; keep the change aligned with the existing plugin-based service 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

npm test -- test/index/test_index_495_04.ts

Question: IndexPolicy49504|resource_cleanup_defect


Instruction: Fix the defect where the migration rejects valid boundary values in the access-control service. The affected entry point is MigrationPolicy49505; 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 migration 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 explicit timeouts in the upload of the access-control service. The affected entry point is UploadPolicy49506; keep the change aligned with the existing plugin-based service 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

Question: UploadPolicy49506|error_propagation_defect

Locate the implementation and callers associated with UploadPolicy49506.

Search evidence identifies src/upload/upload_495_06.rs 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.

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


Instruction: Fix the defect where the download fails when an optional field is absent in the access-control service. The affected entry point is DownloadPolicy49507; 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 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_495_07.ts

Locate the implementation and callers associated with DownloadPolicy49507.

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

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

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


Instruction: Add guarded support for input size limits in the audit of the access-control service. The affected entry point is AuditPolicy49508; 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 audit no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests AuditRegression49508

Question: AuditPolicy49508|sensitive_data_exposure

Locate the implementation and callers associated with AuditPolicy49508.

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

Diff inspection is required before making a completion claim.


Instruction: Add guarded support for graceful shutdown in the worker of the access-control service. The affected entry point is WorkerPolicy49509; keep the change aligned with the existing plugin-based service 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_495_09.ts

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

Locate the implementation and callers associated with WorkerPolicy49509.

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

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

Obtain executable evidence for the requested behavior.


Instruction: Add guarded support for per-tenant configuration in the scheduler of the access-control service. The affected entry point is SchedulerPolicy49510; 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 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 SchedulerPolicy49510.

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

Unnecessary approval requests would reduce agent usefulness without improving safety.

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


Instruction: Add guarded support for safe fallback behavior in the router of the access-control service. The affected entry point is RouterPolicy49511; keep the change aligned with the existing plugin-based service 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_495_11.ts

Question: RouterPolicy49511|failure_classification_defect

Locate the implementation and callers associated with RouterPolicy49511.

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

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

Identify existing test style and the nearest regression boundary.

correct failure-classification defect while preserving the public contract

Apply a localized change that follows existing abstractions.


Instruction: Add regression coverage for the case where the metrics accepts malformed input after normalization in the access-control service. The affected entry point is MetricsPolicy49512; 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 metrics no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: MetricsPolicy49512|validation_order_defect

correct validation-order defect while preserving the public contract


Instruction: Correct the configuration and operator guidance for cursor pagination in the access-control service. The affected entry point is LoggingPolicy49513; 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 logging no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests LoggingRegression49513

Locate the implementation and callers associated with LoggingPolicy49513.

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

correct retry-safety defect while preserving the public contract


Instruction: Fix the defect where the sandbox mutates shared state across requests in the access-control service. The affected entry point is SandboxPolicy49514; keep the change aligned with the existing plugin-based service 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_495_14.ts

Question: SandboxPolicy49514|state_isolation_defect

Locate the implementation and callers associated with SandboxPolicy49514.

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

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

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


Instruction: Add regression coverage for the case where the session matches identifiers case-insensitively in the access-control service. The affected entry point is SessionPolicy49515; 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 session no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: SessionPolicy49515|identity_comparison_defect

correct identity-comparison defect while preserving the public contract


Instruction: Harden the token in the access-control service against path traversal while preserving valid behavior. The affected entry point is TokenPolicy49516; keep the change aligned with the existing plugin-based service 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

npm test -- test/token/test_token_495_16.ts

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

Confirm the local module boundary before searching for implementation details.

Locate the implementation and callers associated with TokenPolicy49516.

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

Hard tasks require caller evidence to control compatibility risk.

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

correct false-success defect while preserving the public contract

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

Check static constraints relevant to the modified code.

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


Instruction: Add regression coverage for the case where the pagination uses a broad filesystem permission in the access-control service. The affected entry point is PaginationPolicy49517; 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 pagination no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/pagination/test_pagination_495_17.ts

correct least-privilege defect while preserving the public contract


Instruction: Fix the defect where the cache does not verify the persisted state in the access-control service. The affected entry point is CachePolicy49518; 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 cache 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: Fix the defect where the queue returns stale state after an update in the access-control service. The affected entry point is QueuePolicy49519; keep the change aligned with the existing plugin-based service boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The queue no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/queue/test_queue_495_19.ts

Question: QueuePolicy49519|cache_invalidation_defect

correct cache-invalidation defect while preserving the public contract


Instruction: Harden the search in the cache coordinator against authorization bypass while preserving valid behavior. The affected entry point is SearchPolicy49600; keep the change aligned with the existing layered service boundary.

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

The search no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests SearchRegression49600

Locate the implementation and callers associated with SearchPolicy49600.

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

Diff inspection is required before making a completion claim.


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

A targeted verification path is identified

The final change remains inside the requested scope

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

Question: IndexPolicy49601|resource_bounding_defect

Locate the implementation and callers associated with IndexPolicy49601.

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

Confirm the current control flow, local conventions, and error 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.


Instruction: Add guarded support for per-tenant configuration in the migration of the cache coordinator. The affected entry point is MigrationPolicy49602; keep the change aligned with the existing layered service boundary.

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

The migration no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Locate the implementation and callers associated with MigrationPolicy49602.

Search evidence identifies src/migration/migration_496_02.py as the narrow implementation boundary.

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

Identify existing test style and the nearest regression boundary.

Apply a localized change that follows existing abstractions.