Instruction: Fix the defect where the session uses seconds where milliseconds are expected in the identity gateway. The affected entry point is SessionPolicy47500; keep the change aligned with the existing CLI application 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

dotnet test --filter SessionRegression47500

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

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: SessionPolicy47500|unit_conversion_defect

Locate the implementation and callers associated with SessionPolicy47500.

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

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

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

Identify existing test style and the nearest regression boundary.

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

correct unit-conversion defect while preserving the public contract

Apply a localized change that follows existing abstractions.

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

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.

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

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

Diff inspection is required before making a completion claim.

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

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


Instruction: Refactor the token in the identity gateway to remove duplicated cleanup logic without changing behavior. The affected entry point is TokenPolicy47501; keep the change aligned with the existing CLI application 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

Ground every decision in repository evidence before editing.

Question: TokenPolicy47501|authorization_order_defect

Locate the implementation and callers associated with TokenPolicy47501.

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

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

confirm behavior
apply bounded patch
run targeted test
inspect diff

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

correct authorization-order defect while preserving the public contract

Obtain executable evidence for the requested behavior.


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

A targeted verification path is identified

The final change remains inside the requested scope

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

Locate the implementation and callers associated with PaginationPolicy47502.

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

correct input-size handling defect while preserving the public contract

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

Check static constraints relevant to the modified code.


Instruction: Refactor the cache in the identity gateway to remove duplicated cleanup logic without changing behavior. The affected entry point is CachePolicy47503; keep the change aligned with the existing CLI application 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

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

correct compatibility defect while preserving the public contract


Instruction: Refactor the queue in the identity gateway to remove duplicated validation logic without changing behavior. The affected entry point is QueuePolicy47504; keep the change aligned with the existing CLI application 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

./gradlew test --tests QueueRegression47504

Confirm the local module boundary before searching for implementation details.

Question: QueuePolicy47504|resource_cleanup_defect

Locate the implementation and callers associated with QueuePolicy47504.

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

correct resource-cleanup defect while preserving the public contract

Apply a localized change that follows existing abstractions.

The first targeted test fails and provides a concrete counterexample.

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

Apply the second bounded patch addressing the diagnosed cause.

Confirm the revised patch satisfies the original acceptance criterion.


Instruction: Review the proposed webhook change in the identity gateway for correctness, scope, and regressions. The affected entry point is WebhookPolicy47505; keep the change aligned with the existing CLI application boundary.

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

The webhook no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

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

Verify the claimed behavior with targeted checks before completion.

Question: WebhookPolicy47505|boundary_condition_defect

Locate the implementation and callers associated with WebhookPolicy47505.

Search evidence identifies src/webhook/webhook_475_05.rs as the narrow implementation boundary.

correct boundary-condition defect while preserving the public contract

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

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


Instruction: Add regression coverage for the case where the permission drops the original error context in the identity gateway. The affected entry point is PermissionPolicy47506; keep the change aligned with the existing CLI application boundary.

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

The permission no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/permission/test_permission_475_06.ts

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

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

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

repair diagnosed cause without broadening scope

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

Locate the implementation and callers associated with PermissionPolicy47506.

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

correct error-propagation defect while preserving the public contract

The original acceptance criterion passes

The failure signal is no longer reproduced

The final report distinguishes executed evidence from assumptions


Instruction: Fix the defect where the configuration fails when an optional field is absent in the identity gateway. The affected entry point is ConfigurationPolicy47507; 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 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 ConfigurationRegression47507

Locate the implementation and callers associated with ConfigurationPolicy47507.

Search evidence identifies internal/configuration/configuration_475_07.go as the narrow implementation boundary.

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

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.

Repeating the same patch would ignore the new test evidence.

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

The repaired behavior must be re-executed before completion.

Diff inspection is required before making a completion claim.


Instruction: Fix the defect where the parser logs a secret-bearing request field in the identity gateway. The affected entry point is ParserPolicy47508; keep the change aligned with the existing CLI application boundary.

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

The parser no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

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

Question: ParserPolicy47508|sensitive_data_exposure

Locate the implementation and callers associated with ParserPolicy47508.

Search evidence identifies src/parser/parser_475_08.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.

correct sensitive-data exposure while preserving the public contract

Obtain executable evidence for the requested behavior.

Check static constraints relevant to the modified code.


Instruction: Review the proposed serializer change in the identity gateway for correctness, scope, and regressions. The affected entry point is SerializerPolicy47509; keep the change aligned with the existing CLI application boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The serializer no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Locate the implementation and callers associated with SerializerPolicy47509.

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

Apply a localized change that follows existing abstractions.

The first targeted test fails and provides a concrete counterexample.

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

Apply the second bounded patch addressing the diagnosed cause.

Confirm the revised patch satisfies the original acceptance criterion.


Instruction: Fix the defect where the validator loads an unbounded result set in the identity gateway. The affected entry point is ValidatorPolicy47510; keep the change aligned with the existing CLI application 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

npm test -- test/validator/test_validator_475_10.ts

Locate the implementation and callers associated with ValidatorPolicy47510.

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

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

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


Instruction: Add regression coverage for the case where the retry misclassifies transient failures as permanent in the identity gateway. The affected entry point is RetryPolicy47511; keep the change aligned with the existing CLI application 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

dotnet test --filter RetryRegression47511

Use a bounded, updateable plan proportional to task complexity.

Question: RetryPolicy47511|failure_classification_defect

Locate the implementation and callers associated with RetryPolicy47511.

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

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

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

correct failure-classification defect while preserving the public contract


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

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests TimeoutRegression47512

Respect scope and request approval only for materially risky actions.

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: TimeoutPolicy47512|validation_order_defect

Locate the implementation and callers associated with TimeoutPolicy47512.

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

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

Unnecessary approval requests would reduce agent usefulness without improving safety.

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

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

correct validation-order defect while preserving the public contract

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

Obtain executable evidence for the requested behavior.


Instruction: Fix the defect where the search retries a non-idempotent operation in the identity gateway. The affected entry point is SearchPolicy47513; keep the change aligned with the existing CLI application 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

ctest -R SearchRegression47513 --output-on-failure

Locate the implementation and callers associated with SearchPolicy47513.

Search evidence identifies src/search/search_475_13.cpp 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 retry-safety defect while preserving the public contract

Apply a localized change that follows existing abstractions.


Instruction: Harden the index in the identity gateway against unbounded resource use while preserving valid behavior. The affected entry point is IndexPolicy47514; keep the change aligned with the existing CLI application 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

Locate the implementation and callers associated with IndexPolicy47514.

Search evidence identifies src/index/index_475_14.php as the narrow implementation boundary.

correct state-isolation 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: Harden the migration in the identity gateway against unbounded resource use while preserving valid behavior. The affected entry point is MigrationPolicy47515; keep the change aligned with the existing CLI application 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

correct identity-comparison defect while preserving the public contract

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


Instruction: Fix the defect where the upload marks partial work as successful in the identity gateway. The affected entry point is UploadPolicy47516; keep the change aligned with the existing CLI application 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

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

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

Locate the implementation and callers associated with UploadPolicy47516.

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

Hard tasks require caller evidence to control compatibility risk.

correct false-success defect while preserving the public contract

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


Instruction: Fix the defect where the download uses a broad filesystem permission in the identity gateway. The affected entry point is DownloadPolicy47517; 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 download no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

go test ./download -run DownloadRegression47517

Question: DownloadPolicy47517|least_privilege_defect

Locate the implementation and callers associated with DownloadPolicy47517.

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

correct least-privilege defect while preserving the public contract


Instruction: Add guarded support for request cancellation in the audit of the identity gateway. The affected entry point is AuditPolicy47518; keep the change aligned with the existing CLI application 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

correct verification defect while preserving the public contract


Instruction: Fix the defect where the worker returns stale state after an update in the identity gateway. The affected entry point is WorkerPolicy47519; keep the change aligned with the existing CLI application 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

Question: WorkerPolicy47519|cache_invalidation_defect

Locate the implementation and callers associated with WorkerPolicy47519.

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

correct cache-invalidation defect while preserving the public contract

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


Instruction: Refactor the cache in the dataset pipeline to remove duplicated serialization logic without changing behavior. The affected entry point is CachePolicy47600; keep the change aligned with the existing HTTP API 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

Respect scope and request approval only for materially risky actions.

Locate the implementation and callers associated with CachePolicy47600.

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

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

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


Instruction: Correct the configuration and operator guidance for dry-run mode in the dataset pipeline. The affected entry point is QueuePolicy47601; 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 queue no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

go test ./queue -run QueueRegression47601

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

Question: QueuePolicy47601|resource_bounding_defect

Locate the implementation and callers associated with QueuePolicy47601.

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

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


Instruction: Add regression coverage for the case where the webhook misclassifies transient failures as permanent in the dataset pipeline. The affected entry point is WebhookPolicy47602; keep the change aligned with the existing HTTP API boundary.

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

The webhook no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: WebhookPolicy47602|failure_classification_defect

rewrite subsystem
replace dependencies
change API

Use a bounded, updateable plan proportional to task complexity.


Instruction: Fix the defect where the permission accepts malformed input after normalization in the dataset pipeline. The affected entry point is PermissionPolicy47603; keep the change aligned with the existing HTTP API 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

./gradlew test --tests PermissionRegression47603

Ground every decision in repository evidence before editing.


Instruction: Review the proposed configuration change in the dataset pipeline for correctness, scope, and regressions. The affected entry point is ConfigurationPolicy47604; keep the change aligned with the existing HTTP API boundary.

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

The configuration no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests ConfigurationRegression47604

Confirm the local module boundary before searching for implementation details.

Locate the implementation and callers associated with ConfigurationPolicy47604.

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

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

Obtain executable evidence for the requested behavior.


Instruction: Fix the defect where the parser mutates shared state across requests in the dataset pipeline. The affected entry point is ParserPolicy47605; keep the change aligned with the existing HTTP API 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

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

Question: ParserPolicy47605|state_isolation_defect

Locate the implementation and callers associated with ParserPolicy47605.

Search evidence identifies src/parser/parser_476_05.rs as the narrow implementation boundary.

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

Identify existing test style and the nearest regression boundary.

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

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.


Instruction: Fix the defect where the serializer matches identifiers case-insensitively in the dataset pipeline. The affected entry point is SerializerPolicy47606; 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 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_476_06.ts

Locate the implementation and callers associated with SerializerPolicy47606.

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

Apply a localized change that follows existing abstractions.

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

Check static constraints relevant to the modified code.


Instruction: Add guarded support for safe fallback behavior in the validator of the dataset pipeline. The affected entry point is ValidatorPolicy47607; keep the change aligned with the existing HTTP API boundary.

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

The validator no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

go test ./validator -run ValidatorRegression47607

Locate the implementation and callers associated with ValidatorPolicy47607.

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

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


Instruction: Fix the defect where the retry uses a broad filesystem permission in the dataset pipeline. The affected entry point is RetryPolicy47608; keep the change aligned with the existing HTTP API 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


Instruction: Refactor the timeout in the dataset pipeline to remove duplicated validation logic without changing behavior. The affected entry point is TimeoutPolicy47609; keep the change aligned with the existing HTTP API 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


Instruction: Fix the defect where the search returns stale state after an update in the dataset pipeline. The affected entry point is SearchPolicy47610; keep the change aligned with the existing HTTP API 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

Question: SearchPolicy47610|cache_invalidation_defect

Locate the implementation and callers associated with SearchPolicy47610.

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

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

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


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

A targeted verification path is identified

The final change remains inside the requested scope

dotnet test --filter IndexRegression47611

Locate the implementation and callers associated with IndexPolicy47611.

Search evidence identifies src/index/IndexService476.cs as the narrow implementation boundary.

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 unit-conversion defect while preserving the public contract


Instruction: Fix the defect where the migration performs authorization after the side effect in the dataset pipeline. The affected entry point is MigrationPolicy47612; keep the change aligned with the existing HTTP API 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 MigrationRegression47612

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

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

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

correct authorization-order defect while preserving the public contract

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.

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: Correct the configuration and operator guidance for dry-run mode in the dataset pipeline. The affected entry point is UploadPolicy47613; keep the change aligned with the existing HTTP API 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_476_13.ts

Question: UploadPolicy47613|input_size_handling_defect

Locate the implementation and callers associated with UploadPolicy47613.

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

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

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

Identify existing test style and the nearest regression boundary.

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: Harden the download in the dataset pipeline against secret leakage while preserving valid behavior. The affected entry point is DownloadPolicy47614; keep the change aligned with the existing HTTP API 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

npm test -- test/download/test_download_476_14.ts

Question: DownloadPolicy47614|compatibility_defect

Locate the implementation and callers associated with DownloadPolicy47614.

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

correct compatibility defect while preserving the public contract

Apply a localized change that follows existing abstractions.

Question: authorize|permission|sanitize|validate

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


Instruction: Add regression coverage for the case where the audit skips cleanup after cancellation in the dataset pipeline. The affected entry point is AuditPolicy47615; keep the change aligned with the existing HTTP API boundary.

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

The audit no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: AuditPolicy47615|resource_cleanup_defect

Locate the implementation and callers associated with AuditPolicy47615.

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

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

correct resource-cleanup defect while preserving the public contract

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: Fix the defect where the worker rejects valid boundary values in the dataset pipeline. The affected entry point is WorkerPolicy47616; 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 worker no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests WorkerRegression47616

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

Question: WorkerPolicy47616|boundary_condition_defect

Locate the implementation and callers associated with WorkerPolicy47616.

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

correct boundary-condition defect while preserving the public contract

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

Check static constraints relevant to the modified code.


Instruction: Fix the defect where the scheduler drops the original error context in the dataset pipeline. The affected entry point is SchedulerPolicy47617; keep the change aligned with the existing HTTP API boundary.

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

The scheduler no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

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

Locate the implementation and callers associated with SchedulerPolicy47617.

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


Instruction: Refactor the router in the dataset pipeline to remove duplicated configuration parsing without changing behavior. The affected entry point is RouterPolicy47618; keep the change aligned with the existing HTTP API boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The router no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/router/test_router_476_18.ts

Locate the implementation and callers associated with RouterPolicy47618.

Search evidence identifies src/router/router_476_18.ts 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: Fix the defect where the metrics logs a secret-bearing request field in the dataset pipeline. The affected entry point is MetricsPolicy47619; keep the change aligned with the existing HTTP API boundary.

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

The metrics no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: MetricsPolicy47619|sensitive_data_exposure

Locate the implementation and callers associated with MetricsPolicy47619.

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

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

correct sensitive-data exposure while preserving the public contract


Instruction: Add regression coverage for the case where the permission does not verify the persisted state in the code search service. The affected entry point is PermissionPolicy47700; 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 permission no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

ctest -R PermissionRegression47700 --output-on-failure

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

Confirm the local module boundary before searching for implementation details.

Locate the implementation and callers associated with PermissionPolicy47700.

Search evidence identifies src/permission/permission_477_00.cpp 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 cursor pagination in the configuration of the code search service. The affected entry point is ConfigurationPolicy47701; keep the change aligned with the existing background processor 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 ConfigurationRegression47701

Locate the implementation and callers associated with ConfigurationPolicy47701.

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

Apply a localized change that follows existing abstractions.

The first targeted test fails and provides a concrete counterexample.

Repeating the same patch would ignore the new test evidence.

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

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

Apply the second bounded patch addressing the diagnosed cause.

The repaired behavior must be re-executed before completion.

Confirm the revised patch satisfies the original acceptance criterion.

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


Instruction: Fix the defect where the parser uses seconds where milliseconds are expected in the code search service. The affected entry point is ParserPolicy47702; keep the change aligned with the existing background processor boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The parser no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: ParserPolicy47702|unit_conversion_defect

Locate the implementation and callers associated with ParserPolicy47702.

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

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

Obtain executable evidence for the requested behavior.


Instruction: Review the proposed serializer change in the code search service for correctness, scope, and regressions. The affected entry point is SerializerPolicy47703; keep the change aligned with the existing background processor 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

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

Locate the implementation and callers associated with SerializerPolicy47703.

Search evidence identifies src/serializer/serializer_477_03.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: Refactor the validator in the code search service to remove duplicated serialization logic without changing behavior. The affected entry point is ValidatorPolicy47704; keep the change aligned with the existing background processor 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

./gradlew test --tests ValidatorRegression47704

Confirm the local module boundary before searching for implementation details.

Locate the implementation and callers associated with ValidatorPolicy47704.

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

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

correct input-size handling defect while preserving the public contract

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


Instruction: Fix the defect where the retry does not preserve the public error contract in the code search service. The affected entry point is RetryPolicy47705; 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 retry no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

go test ./retry -run RetryRegression47705

Locate the implementation and callers associated with RetryPolicy47705.

Search evidence identifies internal/retry/retry_477_05.go 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 first targeted test fails and provides a concrete counterexample.

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

Apply the second bounded patch addressing the diagnosed cause.

Confirm the revised patch satisfies the original acceptance criterion.

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

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

Diff inspection is required before making a completion claim.

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


Instruction: Add guarded support for explicit timeouts in the timeout of the code search service. The affected entry point is TimeoutPolicy47706; keep the change aligned with the existing background processor 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

Question: TimeoutPolicy47706|resource_cleanup_defect

Locate the implementation and callers associated with TimeoutPolicy47706.

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

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

Obtain executable evidence for the requested behavior.


Instruction: Add guarded support for audit metadata in the search of the code search service. The affected entry point is SearchPolicy47707; keep the change aligned with the existing background processor boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The search no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: SearchPolicy47707|boundary_condition_defect

Locate the implementation and callers associated with SearchPolicy47707.

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

Check static constraints relevant to the modified code.


Instruction: Correct the configuration and operator guidance for input size limits in the code search service. The affected entry point is IndexPolicy47708; keep the change aligned with the existing background processor boundary.

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

The index no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

go test ./index -run IndexRegression47708

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

Confirm the local module boundary before searching for implementation details.

Question: IndexPolicy47708|error_propagation_defect

Locate the implementation and callers associated with IndexPolicy47708.

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

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

Identify existing test style and the nearest regression boundary.

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

correct error-propagation defect while preserving the public contract


Instruction: Correct the configuration and operator guidance for graceful shutdown in the code search service. The affected entry point is MigrationPolicy47709; keep the change aligned with the existing background processor 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_477_09.ts

The diff includes a configuration change outside the requested boundary.

repair diagnosed cause without broadening scope

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

Locate the implementation and callers associated with MigrationPolicy47709.

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

Apply a localized change that follows existing abstractions.


Instruction: Add guarded support for per-tenant configuration in the upload of the code search service. The affected entry point is UploadPolicy47710; 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 upload no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: UploadPolicy47710|sensitive_data_exposure

Locate the implementation and callers associated with UploadPolicy47710.

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


Instruction: Add guarded support for safe fallback behavior in the download of the code search service. The affected entry point is DownloadPolicy47711; keep the change aligned with the existing background processor boundary.

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

The download no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/download/test_download_477_11.ts

Locate the implementation and callers associated with DownloadPolicy47711.

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

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


Instruction: Fix the defect where the audit loads an unbounded result set in the code search service. The affected entry point is AuditPolicy47712; keep the change aligned with the existing background processor boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The audit no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: AuditPolicy47712|resource_bounding_defect

Locate the implementation and callers associated with AuditPolicy47712.

Search evidence identifies src/audit/audit_477_12.rs as the narrow implementation boundary.

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

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

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

correct resource-bounding defect while preserving the public contract

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

Obtain executable evidence for the requested behavior.

Diff inspection is required before making a completion claim.

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


Instruction: Fix the defect where the worker misclassifies transient failures as permanent in the code search service. The affected entry point is WorkerPolicy47713; keep the change aligned with the existing background processor boundary.

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

The worker no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/worker/test_worker_477_13.ts

Question: WorkerPolicy47713|failure_classification_defect

correct failure-classification defect while preserving the public contract

Verify the claimed behavior with targeted checks before completion.


Instruction: Review the proposed scheduler change in the code search service for correctness, scope, and regressions. The affected entry point is SchedulerPolicy47714; keep the change aligned with the existing background processor 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

Locate the implementation and callers associated with SchedulerPolicy47714.

Search evidence identifies src/scheduler/scheduler_477_14.py 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 router in the code search service to remove duplicated error mapping without changing behavior. The affected entry point is RouterPolicy47715; 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 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_477_15.ts

Locate the implementation and callers associated with RouterPolicy47715.

Search evidence identifies src/router/router_477_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 retry-safety defect while preserving the public contract

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 metrics mutates shared state across requests in the code search service. The affected entry point is MetricsPolicy47716; keep the change aligned with the existing background processor boundary.

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

The metrics no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

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: MetricsPolicy47716|state_isolation_defect

Locate the implementation and callers associated with MetricsPolicy47716.

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

correct state-isolation defect while preserving the public contract

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

Check static constraints relevant to the modified code.


Instruction: Fix the defect where the logging matches identifiers case-insensitively in the code search service. The affected entry point is LoggingPolicy47717; keep the change aligned with the existing background processor boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The logging no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: LoggingPolicy47717|identity_comparison_defect

Locate the implementation and callers associated with LoggingPolicy47717.

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

correct identity-comparison defect while preserving the public contract


Instruction: Add guarded support for explicit timeouts in the sandbox of the code search service. The affected entry point is SandboxPolicy47718; keep the change aligned with the existing background processor boundary.

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

The sandbox no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Locate the implementation and callers associated with SandboxPolicy47718.

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

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

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

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


Instruction: Review the proposed session change in the code search service for correctness, scope, and regressions. The affected entry point is SessionPolicy47719; keep the change aligned with the existing background processor boundary.

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

The session no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

go test ./session -run SessionRegression47719

Question: SessionPolicy47719|least_privilege_defect

Locate the implementation and callers associated with SessionPolicy47719.

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

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

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


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

./gradlew test --tests SerializerRegression47800

Locate the implementation and callers associated with SerializerPolicy47800.

Search evidence identifies src/main/java/serializer/SerializerService478.java as the narrow implementation boundary.

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

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

Obtain executable evidence for the requested behavior.

Diff inspection is required before making a completion claim.


Instruction: Correct the configuration and operator guidance for graceful shutdown in the artifact registry. The affected entry point is ValidatorPolicy47801; keep the change aligned with the existing library package 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

./gradlew test --tests ValidatorRegression47801

Locate the implementation and callers associated with ValidatorPolicy47801.

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

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

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


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

Locate the implementation and callers associated with RetryPolicy47802.

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

Apply a localized change that follows existing abstractions.


Instruction: Fix the defect where the timeout loads an unbounded result set in the artifact registry. The affected entry point is TimeoutPolicy47803; keep the change aligned with the existing library package 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

npm test -- test/timeout/test_timeout_478_03.ts

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

Question: TimeoutPolicy47803|resource_bounding_defect

Locate the implementation and callers associated with TimeoutPolicy47803.

Search evidence identifies src/timeout/timeout_478_03.ts as the narrow implementation boundary.


Instruction: Fix the defect where the search misclassifies transient failures as permanent in the artifact registry. The affected entry point is SearchPolicy47804; 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 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 SearchRegression47804

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: SearchPolicy47804|failure_classification_defect

Locate the implementation and callers associated with SearchPolicy47804.

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


Instruction: Add guarded support for cursor pagination in the index of the artifact registry. The affected entry point is IndexPolicy47805; keep the change aligned with the existing library package 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

npm test -- test/index/test_index_478_05.ts

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

Question: IndexPolicy47805|validation_order_defect

Locate the implementation and callers associated with IndexPolicy47805.

Search evidence identifies src/index/index_478_05.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 validation-order defect while preserving the public contract


Instruction: Add guarded support for request cancellation in the migration of the artifact registry. The affected entry point is MigrationPolicy47806; keep the change aligned with the existing library package 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

Locate the implementation and callers associated with MigrationPolicy47806.

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

Hard tasks require caller evidence to control compatibility risk.

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

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 upload mutates shared state across requests in the artifact registry. The affected entry point is UploadPolicy47807; keep the change aligned with the existing library package 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: UploadPolicy47807|state_isolation_defect

Locate the implementation and callers associated with UploadPolicy47807.

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

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

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

Obtain executable evidence for the requested behavior.

Diff inspection is required before making a completion claim.


Instruction: Refactor the download in the artifact registry to remove duplicated serialization logic without changing behavior. The affected entry point is DownloadPolicy47808; keep the change aligned with the existing library package 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

Question: DownloadPolicy47808|identity_comparison_defect

Locate the implementation and callers associated with DownloadPolicy47808.

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

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

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

Identify existing test style and the nearest regression boundary.

Apply a localized change that follows existing abstractions.


Instruction: Fix the defect where the audit marks partial work as successful in the artifact registry. The affected entry point is AuditPolicy47809; 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 audit no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope


Instruction: Review the proposed worker change in the artifact registry for correctness, scope, and regressions. The affected entry point is WorkerPolicy47810; keep the change aligned with the existing library package boundary.

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

The worker no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: WorkerPolicy47810|least_privilege_defect

correct least-privilege defect while preserving the public contract

Question: authorize|permission|sanitize|validate


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

go test ./scheduler -run SchedulerRegression47811

correct verification defect while preserving the public contract


Instruction: Correct the configuration and operator guidance for input size limits in the artifact registry. The affected entry point is RouterPolicy47812; keep the change aligned with the existing library package 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

Question: RouterPolicy47812|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 artifact registry. The affected entry point is MetricsPolicy47813; keep the change aligned with the existing library package 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 MetricsRegression47813

Question: MetricsPolicy47813|unit_conversion_defect

Locate the implementation and callers associated with MetricsPolicy47813.

Search evidence identifies internal/metrics/metrics_478_13.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.

correct unit-conversion defect while preserving the public contract


Instruction: Harden the logging in the artifact registry against unbounded resource use while preserving valid behavior. The affected entry point is LoggingPolicy47814; 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 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 LoggingRegression47814

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

Question: LoggingPolicy47814|authorization_order_defect

Locate the implementation and callers associated with LoggingPolicy47814.

Search evidence identifies internal/logging/logging_478_14.go as the narrow implementation boundary.

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

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


Instruction: Fix the defect where the sandbox silently truncates an oversized payload in the artifact registry. The affected entry point is SandboxPolicy47815; keep the change aligned with the existing library package boundary.

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

The sandbox no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: SandboxPolicy47815|input_size_handling_defect

Locate the implementation and callers associated with SandboxPolicy47815.

Search evidence identifies src/sandbox/sandbox_478_15.py as the narrow implementation boundary.

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

correct input-size handling defect while preserving the public contract

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

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


Instruction: Refactor the session in the artifact registry to remove duplicated validation logic without changing behavior. The affected entry point is SessionPolicy47816; keep the change aligned with the existing library package boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The session no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

ctest -R SessionRegression47816 --output-on-failure

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

Confirm the local module boundary before searching for implementation details.

Locate the implementation and callers associated with SessionPolicy47816.

Search evidence identifies src/session/session_478_16.cpp as the narrow implementation boundary.

correct compatibility 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: Harden the token in the artifact registry against path traversal while preserving valid behavior. The affected entry point is TokenPolicy47817; keep the change aligned with the existing library package boundary.

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

The token no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

dotnet test --filter TokenRegression47817

repair diagnosed cause without broadening scope

Question: TokenPolicy47817|resource_cleanup_defect

Locate the implementation and callers associated with TokenPolicy47817.

Search evidence identifies src/token/TokenService478.cs as the narrow implementation boundary.

correct resource-cleanup defect while preserving the public contract

Obtain executable evidence for the requested behavior.


Instruction: Add regression coverage for the case where the pagination rejects valid boundary values in the artifact registry. The affected entry point is PaginationPolicy47818; keep the change aligned with the existing library package boundary.

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

The pagination no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

dotnet test --filter PaginationRegression47818

correct boundary-condition defect while preserving the public contract

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


Instruction: Correct the configuration and operator guidance for structured errors in the artifact registry. The affected entry point is CachePolicy47819; 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 cache no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: CachePolicy47819|error_propagation_defect

Locate the implementation and callers associated with CachePolicy47819.

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

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

correct error-propagation defect while preserving the public contract

Apply a localized change that follows existing abstractions.

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

Diff inspection is required before making a completion claim.

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


Instruction: Refactor the timeout in the billing worker to remove duplicated error mapping without changing behavior. The affected entry point is TimeoutPolicy47900; keep the change aligned with the existing plugin-based service 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

npm test -- test/timeout/test_timeout_479_00.ts

Repository evidence contradicts the initial assumption about the data representation.

Locate the implementation and callers associated with TimeoutPolicy47900.

Search evidence identifies src/timeout/timeout_479_00.ts as the narrow implementation boundary.

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

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


Instruction: Add guarded support for dry-run mode in the search of the billing worker. The affected entry point is SearchPolicy47901; 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 search no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: SearchPolicy47901|least_privilege_defect

Locate the implementation and callers associated with SearchPolicy47901.

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


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

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

The index no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/index/test_index_479_02.ts

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

Locate the implementation and callers associated with IndexPolicy47902.

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


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

A targeted verification path is identified

The final change remains inside the requested scope


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

A targeted verification path is identified

The final change remains inside the requested scope

Question: UploadPolicy47904|unit_conversion_defect


Instruction: Fix the defect where the download performs authorization after the side effect in the billing worker. The affected entry point is DownloadPolicy47905; keep the change aligned with the existing plugin-based service 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: DownloadPolicy47905|authorization_order_defect

Locate the implementation and callers associated with DownloadPolicy47905.

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

correct authorization-order defect while preserving the public contract

Check static constraints relevant to the modified code.

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

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

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


Instruction: Fix the defect where the audit silently truncates an oversized payload in the billing worker. The affected entry point is AuditPolicy47906; 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 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_479_06.ts

Question: AuditPolicy47906|input_size_handling_defect

Locate the implementation and callers associated with AuditPolicy47906.

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

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.


Instruction: Harden the worker in the billing worker against authorization bypass while preserving valid behavior. The affected entry point is WorkerPolicy47907; keep the change aligned with the existing plugin-based service 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

dotnet test --filter WorkerRegression47907


Instruction: Add guarded support for bounded retries in the scheduler of the billing worker. The affected entry point is SchedulerPolicy47908; 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 scheduler no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests SchedulerRegression47908

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

Search evidence identifies src/main/java/scheduler/SchedulerService479.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: Fix the defect where the router rejects valid boundary values in the billing worker. The affected entry point is RouterPolicy47909; 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 router no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

go test ./router -run RouterRegression47909

Question: RouterPolicy47909|boundary_condition_defect

Locate the implementation and callers associated with RouterPolicy47909.

Search evidence identifies internal/router/router_479_09.go as the narrow implementation boundary.

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

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

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

Obtain executable evidence for the requested behavior.


Instruction: Add regression coverage for the case where the metrics drops the original error context in the billing worker. The affected entry point is MetricsPolicy47910; keep the change aligned with the existing plugin-based service 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: MetricsPolicy47910|error_propagation_defect

Locate the implementation and callers associated with MetricsPolicy47910.

Search evidence identifies src/metrics/metrics_479_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 regression coverage for the case where the logging fails when an optional field is absent in the billing worker. The affected entry point is LoggingPolicy47911; 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 logging no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

correct nullability defect while preserving the public contract


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

go test ./sandbox -run SandboxRegression47912

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

Question: SandboxPolicy47912|sensitive_data_exposure

Locate the implementation and callers associated with SandboxPolicy47912.

Search evidence identifies internal/sandbox/sandbox_479_12.go as the narrow implementation boundary.

correct sensitive-data exposure while preserving the public contract

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


Instruction: Add guarded support for dry-run mode in the session of the billing worker. The affected entry point is SessionPolicy47913; 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 session 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 SessionPolicy47913.

Search evidence identifies src/session/session_479_13.php as the narrow implementation boundary.

correct idempotency defect while preserving the public contract


Instruction: Add regression coverage for the case where the token loads an unbounded result set in the billing worker. The affected entry point is TokenPolicy47914; 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 token no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests TokenRegression47914

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

Question: TokenPolicy47914|resource_bounding_defect

Locate the implementation and callers associated with TokenPolicy47914.

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

correct resource-bounding defect while preserving the public contract

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


Instruction: Harden the pagination in the billing worker against secret leakage while preserving valid behavior. The affected entry point is PaginationPolicy47915; keep the change aligned with the existing plugin-based service boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The pagination no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/pagination/test_pagination_479_15.ts

Locate the implementation and callers associated with PaginationPolicy47915.

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

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

correct failure-classification defect while preserving the public contract

Hard tasks require caller evidence to control compatibility risk.

Check static constraints relevant to the modified code.

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

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


Instruction: Refactor the cache in the billing worker to remove duplicated state transitions without changing behavior. The affected entry point is CachePolicy47916; 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 cache no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/cache/test_cache_479_16.ts

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

Question: CachePolicy47916|validation_order_defect

Locate the implementation and callers associated with CachePolicy47916.

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

correct validation-order defect while preserving the public contract

Apply a localized change that follows existing abstractions.

Diff inspection is required before making a completion claim.


Instruction: Fix the defect where the queue retries a non-idempotent operation in the billing worker. The affected entry point is QueuePolicy47917; keep the change aligned with the existing plugin-based service boundary.

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

The queue no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Locate the implementation and callers associated with QueuePolicy47917.

Search evidence identifies src/queue/queue_479_17.rs as the narrow implementation boundary.

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

Identify existing test style and the nearest regression boundary.

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

correct retry-safety defect while preserving the public contract

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


Instruction: Fix the defect where the webhook mutates shared state across requests in the billing worker. The affected entry point is WebhookPolicy47918; 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 webhook no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: WebhookPolicy47918|state_isolation_defect

correct state-isolation defect while preserving the public contract

revise the failed assumption without expanding scope


Instruction: Review the proposed permission change in the billing worker for correctness, scope, and regressions. The affected entry point is PermissionPolicy47919; 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 permission 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 PermissionPolicy47919.

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

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

correct identity-comparison defect while preserving the public contract

Obtain executable evidence for the requested behavior.


Instruction: Add regression coverage for the case where the migration rejects valid boundary values in the notification router. The affected entry point is MigrationPolicy48000; keep the change aligned with the existing layered 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

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

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