Instruction: Add guarded support for bounded retries in the session of the identity gateway. The affected entry point is SessionPolicy45000; keep the change aligned with the existing event-driven worker boundary.

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

The session no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests SessionRegression45000

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

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

Confirm the local module boundary before searching for implementation details.

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

Question: SessionPolicy45000|identity_comparison_defect

Locate the implementation and callers associated with SessionPolicy45000.

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

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

Hard tasks require caller evidence to control compatibility risk.

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

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

correct identity-comparison defect while preserving the public contract

Apply a localized change that follows existing abstractions.

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

Obtain executable evidence for the requested behavior.

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

Check static constraints relevant to the modified code.

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

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

Diff inspection is required before making a completion claim.

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: Review the proposed token change in the identity gateway for correctness, scope, and regressions. The affected entry point is TokenPolicy45001; keep the change aligned with the existing event-driven worker boundary.

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

The token no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/token/test_token_450_01.ts

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

correct false-success defect while preserving the public contract

revise the failed assumption without expanding scope


Instruction: Fix the defect where the pagination uses a broad filesystem permission in the identity gateway. The affected entry point is PaginationPolicy45002; keep the change aligned with the existing event-driven worker boundary.

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

The pagination no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Respect scope and request approval only for materially risky actions.

Locate the implementation and callers associated with PaginationPolicy45002.

Search evidence identifies src/pagination/pagination_450_02.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: Refactor the cache in the identity gateway to remove duplicated error mapping without changing behavior. The affected entry point is CachePolicy45003; keep the change aligned with the existing event-driven worker boundary.

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

The cache no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/cache/test_cache_450_03.ts

Use a bounded, updateable plan proportional to task complexity.

Locate the implementation and callers associated with CachePolicy45003.

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

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

confirm behavior
apply bounded patch
run targeted test
inspect diff

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

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

Identify existing test style and the nearest regression boundary.

correct verification defect while preserving the public contract


Instruction: Harden the queue in the identity gateway against command injection while preserving valid behavior. The affected entry point is QueuePolicy45004; keep the change aligned with the existing event-driven worker boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The queue no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

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

Question: QueuePolicy45004|cache_invalidation_defect

Locate the implementation and callers associated with QueuePolicy45004.

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

correct cache-invalidation 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.


Instruction: Fix the defect where the webhook uses seconds where milliseconds are expected in the identity gateway. The affected entry point is WebhookPolicy45005; keep the change aligned with the existing event-driven worker boundary.

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

The webhook no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

ctest -R WebhookRegression45005 --output-on-failure

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

Question: WebhookPolicy45005|unit_conversion_defect

correct unit-conversion defect while preserving the public contract


Instruction: Refactor the permission in the identity gateway to remove duplicated retry decisions without changing behavior. The affected entry point is PermissionPolicy45006; keep the change aligned with the existing event-driven worker boundary.

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

The permission no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests PermissionRegression45006

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

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

Locate the implementation and callers associated with PermissionPolicy45006.

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

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

correct authorization-order defect while preserving the public contract

Apply a localized change that follows existing abstractions.

Obtain executable evidence for the requested behavior.


Instruction: Add guarded support for audit metadata in the configuration of the identity gateway. The affected entry point is ConfigurationPolicy45007; keep the change aligned with the existing event-driven worker boundary.

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

The configuration no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

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

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

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

repair diagnosed cause without broadening scope

Locate the implementation and callers associated with ConfigurationPolicy45007.

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

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

correct input-size handling defect while preserving the public contract

Hard tasks require caller evidence to control compatibility risk.

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

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

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

Check static constraints relevant to the modified code.

Diff inspection is required before making a completion claim.

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

The original acceptance criterion passes

The failure signal is no longer reproduced

The final report distinguishes executed evidence from assumptions


Instruction: Review the proposed parser change in the identity gateway for correctness, scope, and regressions. The affected entry point is ParserPolicy45008; keep the change aligned with the existing event-driven worker boundary.

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

The parser no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/parser/test_parser_450_08.ts

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

Confirm the local module boundary before searching for implementation details.

Locate the implementation and callers associated with ParserPolicy45008.

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

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

Identify existing test style and the nearest regression boundary.

correct compatibility defect while preserving the public contract


Instruction: Fix the defect where the serializer skips cleanup after cancellation in the identity gateway. The affected entry point is SerializerPolicy45009; keep the change aligned with the existing event-driven worker boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The serializer no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Locate the implementation and callers associated with SerializerPolicy45009.

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

correct resource-cleanup defect while preserving the public contract


Instruction: Add guarded support for per-tenant configuration in the validator of the identity gateway. The affected entry point is ValidatorPolicy45010; keep the change aligned with the existing event-driven worker boundary.

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

The validator no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Respect scope and request approval only for materially risky actions.


Instruction: Add guarded support for safe fallback behavior in the retry of the identity gateway. The affected entry point is RetryPolicy45011; keep the change aligned with the existing event-driven worker boundary.

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

The retry no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

dotnet test --filter RetryRegression45011

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

Question: RetryPolicy45011|error_propagation_defect

correctness security compatibility test_coverage


Instruction: Fix the defect where the timeout fails when an optional field is absent in the identity gateway. The affected entry point is TimeoutPolicy45012; keep the change aligned with the existing event-driven worker boundary.

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

The timeout no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Locate the implementation and callers associated with TimeoutPolicy45012.

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

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

correct nullability defect while preserving the public contract


Instruction: Correct the configuration and operator guidance for cursor pagination in the identity gateway. The affected entry point is SearchPolicy45013; keep the change aligned with the existing event-driven worker boundary.

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

The search no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

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

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

Question: SearchPolicy45013|sensitive_data_exposure

Locate the implementation and callers associated with SearchPolicy45013.

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

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

Produce only evidence-backed findings with severity and confidence.


Instruction: Fix the defect where the index creates duplicate jobs under concurrent delivery in the identity gateway. The affected entry point is IndexPolicy45014; keep the change aligned with the existing event-driven worker boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The index no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Locate the implementation and callers associated with IndexPolicy45014.

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


Instruction: Fix the defect where the migration loads an unbounded result set in the identity gateway. The affected entry point is MigrationPolicy45015; keep the change aligned with the existing event-driven worker boundary.

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

The migration no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests MigrationRegression45015

The diff includes a configuration change outside the requested boundary.

Locate the implementation and callers associated with MigrationPolicy45015.

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

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

Unnecessary approval requests would reduce agent usefulness without improving safety.

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

correct resource-bounding defect while preserving the public contract

Apply a localized change that follows existing abstractions.

Obtain executable evidence for the requested behavior.


Instruction: Add guarded support for idempotency keys in the upload of the identity gateway. The affected entry point is UploadPolicy45016; keep the change aligned with the existing event-driven worker 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

npm test -- test/upload/test_upload_450_16.ts

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

Question: UploadPolicy45016|failure_classification_defect

Locate the implementation and callers associated with UploadPolicy45016.

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

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

correct failure-classification defect while preserving the public contract


Instruction: Add regression coverage for the case where the download accepts malformed input after normalization in the identity gateway. The affected entry point is DownloadPolicy45017; keep the change aligned with the existing event-driven worker boundary.

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

The download no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

dotnet test --filter DownloadRegression45017

Question: DownloadPolicy45017|validation_order_defect

Locate the implementation and callers associated with DownloadPolicy45017.

Search evidence identifies src/download/DownloadService450.cs as the narrow implementation boundary.

correct validation-order defect while preserving the public contract

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

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


Instruction: Fix the defect where the audit retries a non-idempotent operation in the identity gateway. The affected entry point is AuditPolicy45018; keep the change aligned with the existing event-driven worker boundary.

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

The audit no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

go test ./audit -run AuditRegression45018

correct retry-safety defect while preserving the public contract

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


Instruction: Add guarded support for audit metadata in the worker of the identity gateway. The affected entry point is WorkerPolicy45019; keep the change aligned with the existing event-driven worker 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

./gradlew test --tests WorkerRegression45019

Question: WorkerPolicy45019|state_isolation_defect

Locate the implementation and callers associated with WorkerPolicy45019.

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

Hard tasks require caller evidence to control compatibility risk.

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

Diff inspection is required before making a completion claim.


Instruction: Add guarded support for input size limits in the cache of the dataset pipeline. The affected entry point is CachePolicy45100; keep the change aligned with the existing CLI application boundary.

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

The cache no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/cache/test_cache_451_00.ts

Ground every decision in repository evidence before editing.

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

Confirm the local module boundary before searching for implementation details.

Question: CachePolicy45100|resource_cleanup_defect

Locate the implementation and callers associated with CachePolicy45100.

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

Identify existing test style and the nearest regression boundary.

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

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

The 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 queue rejects valid boundary values in the dataset pipeline. The affected entry point is QueuePolicy45101; keep the change aligned with the existing CLI application boundary.

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

The queue no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: QueuePolicy45101|boundary_condition_defect

Locate the implementation and callers associated with QueuePolicy45101.

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

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

correct boundary-condition defect while preserving the public contract

The first targeted test fails and provides a concrete counterexample.

Repeating the same patch would ignore the new test evidence.

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

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

Apply the second bounded patch addressing the diagnosed cause.

The repaired behavior must be re-executed before completion.

Confirm the revised patch satisfies the original acceptance criterion.


Instruction: Fix the defect where the webhook drops the original error context in the dataset pipeline. The affected entry point is WebhookPolicy45102; keep the change aligned with the existing CLI application boundary.

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

The webhook no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/webhook/test_webhook_451_02.ts

Question: WebhookPolicy45102|error_propagation_defect

correct error-propagation defect while preserving the public contract


Instruction: Fix the defect where the permission fails when an optional field is absent in the dataset pipeline. The affected entry point is PermissionPolicy45103; keep the change aligned with the existing CLI application boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The permission no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

ctest -R PermissionRegression45103 --output-on-failure

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

Locate the implementation and callers associated with PermissionPolicy45103.

Search evidence identifies src/permission/permission_451_03.cpp as the narrow implementation boundary.

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

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

Apply a localized change that follows existing abstractions.

Obtain executable evidence for the requested behavior.

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: Fix the defect where the configuration logs a secret-bearing request field in the dataset pipeline. The affected entry point is ConfigurationPolicy45104; keep the change aligned with the existing CLI application boundary.

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

The configuration no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Locate the implementation and callers associated with ConfigurationPolicy45104.

Search evidence identifies src/configuration/configuration_451_04.rs as the narrow implementation boundary.

Unnecessary approval requests would reduce agent usefulness without improving safety.

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

correct sensitive-data exposure while preserving the public contract

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


Instruction: Harden the parser in the dataset pipeline against authorization bypass while preserving valid behavior. The affected entry point is ParserPolicy45105; keep the change aligned with the existing CLI application boundary.

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

The parser no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/parser/test_parser_451_05.ts

Locate the implementation and callers associated with ParserPolicy45105.

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

correct idempotency defect while preserving the public contract

Diff inspection is required before making a completion claim.


Instruction: Correct the configuration and operator guidance for request cancellation in the dataset pipeline. The affected entry point is SerializerPolicy45106; keep the change aligned with the existing CLI application boundary.

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

The serializer no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

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

Locate the implementation and callers associated with SerializerPolicy45106.

Search evidence identifies src/serializer/serializer_451_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.

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 structured errors in the validator of the dataset pipeline. The affected entry point is ValidatorPolicy45107; keep the change aligned with the existing CLI application boundary.

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

The validator no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

dotnet test --filter ValidatorRegression45107

Locate the implementation and callers associated with ValidatorPolicy45107.

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


Instruction: Fix the defect where the retry accepts malformed input after normalization in the dataset pipeline. The affected entry point is RetryPolicy45108; keep the change aligned with the existing CLI application boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The retry no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests RetryRegression45108

Repository evidence contradicts the initial assumption about the data representation.

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

Confirm the local module boundary before searching for implementation details.

Question: RetryPolicy45108|validation_order_defect

Locate the implementation and callers associated with RetryPolicy45108.

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


Instruction: Harden the timeout in the dataset pipeline against authorization bypass while preserving valid behavior. The affected entry point is TimeoutPolicy45109; keep the change aligned with the existing CLI application boundary.

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

The timeout no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Locate the implementation and callers associated with TimeoutPolicy45109.

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


Instruction: Fix the defect where the search mutates shared state across requests in the dataset pipeline. The affected entry point is SearchPolicy45110; keep the change aligned with the existing CLI application boundary.

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

The search no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/search/test_search_451_10.ts

Question: SearchPolicy45110|state_isolation_defect

correct state-isolation defect while preserving the public contract

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


Instruction: Fix the defect where the index matches identifiers case-insensitively in the dataset pipeline. The affected entry point is IndexPolicy45111; keep the change aligned with the existing CLI application boundary.

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

The index no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/index/test_index_451_11.ts

Question: IndexPolicy45111|identity_comparison_defect

Locate the implementation and callers associated with IndexPolicy45111.

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

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

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

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

Identify existing test style and the nearest regression boundary.

correct identity-comparison defect while preserving the public contract


Instruction: Fix the defect where the migration marks partial work as successful in the dataset pipeline. The affected entry point is MigrationPolicy45112; keep the change aligned with the existing CLI application boundary.

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

The migration no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

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

Locate the implementation and callers associated with MigrationPolicy45112.

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

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

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

correct false-success defect while preserving the public contract

Apply a localized change that follows existing abstractions.

Obtain executable evidence for the requested behavior.

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


Instruction: Review the proposed upload change in the dataset pipeline for correctness, scope, and regressions. The affected entry point is UploadPolicy45113; keep the change aligned with the existing CLI application boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The upload no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/upload/test_upload_451_13.ts

Question: UploadPolicy45113|least_privilege_defect

Locate the implementation and callers associated with UploadPolicy45113.

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

correct least-privilege defect while preserving the public contract

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

Diff inspection is required before making a completion claim.


Instruction: Fix the defect where the download does not verify the persisted state in the dataset pipeline. The affected entry point is DownloadPolicy45114; keep the change aligned with the existing CLI application boundary.

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

The download no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Verify the claimed behavior with targeted checks before completion.

Locate the implementation and callers associated with DownloadPolicy45114.

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

correct verification defect while preserving the public contract


Instruction: Review the proposed audit change in the dataset pipeline for correctness, scope, and regressions. The affected entry point is AuditPolicy45115; keep the change aligned with the existing CLI application boundary.

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

The audit no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests AuditRegression45115

Question: AuditPolicy45115|cache_invalidation_defect

correct cache-invalidation defect while preserving the public contract


Instruction: Harden the worker in the dataset pipeline against secret leakage while preserving valid behavior. The affected entry point is WorkerPolicy45116; 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 worker no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: WorkerPolicy45116|unit_conversion_defect

Question: authorize|permission|sanitize|validate

correct unit-conversion defect while preserving the public contract


Instruction: Add guarded support for cursor pagination in the scheduler of the dataset pipeline. The affected entry point is SchedulerPolicy45117; keep the change aligned with the existing CLI application 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

Locate the implementation and callers associated with SchedulerPolicy45117.

Search evidence identifies src/scheduler/scheduler_451_17.php as the narrow implementation boundary.

correct authorization-order defect while preserving the public contract


Instruction: Add regression coverage for the case where the router silently truncates an oversized payload in the dataset pipeline. The affected entry point is RouterPolicy45118; keep the change aligned with the existing CLI application 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

./gradlew test --tests RouterRegression45118

Question: RouterPolicy45118|input_size_handling_defect

correct input-size handling defect while preserving the public contract


Instruction: Add regression coverage for the case where the metrics does not preserve the public error contract in the dataset pipeline. The affected entry point is MetricsPolicy45119; keep the change aligned with the existing CLI application boundary.

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

The metrics no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/metrics/test_metrics_451_19.ts

Locate the implementation and callers associated with MetricsPolicy45119.

Search evidence identifies src/metrics/metrics_451_19.ts 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 permission retries a non-idempotent operation in the code search service. The affected entry point is PermissionPolicy45200; keep the change aligned with the existing HTTP API boundary.

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

The permission no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

revise the failed assumption without expanding scope


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

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

The configuration no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope


Instruction: Fix the defect where the parser matches identifiers case-insensitively in the code search service. The affected entry point is ParserPolicy45202; keep the change aligned with the existing HTTP API boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The parser no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

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

repair diagnosed cause without broadening scope

Question: ParserPolicy45202|identity_comparison_defect

Locate the implementation and callers associated with ParserPolicy45202.

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


Instruction: Fix the defect where the serializer marks partial work as successful in the code search service. The affected entry point is SerializerPolicy45203; keep the change aligned with the existing HTTP API boundary.

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

The serializer no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Locate the implementation and callers associated with SerializerPolicy45203.

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


Instruction: Refactor the validator in the code search service to remove duplicated state transitions without changing behavior. The affected entry point is ValidatorPolicy45204; keep the change aligned with the existing HTTP API boundary.

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

The validator no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests ValidatorRegression45204

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

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


Instruction: Add guarded support for graceful shutdown in the retry of the code search service. The affected entry point is RetryPolicy45205; keep the change aligned with the existing HTTP API boundary.

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

The retry no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Locate the implementation and callers associated with RetryPolicy45205.

Search evidence identifies src/retry/retry_452_05.py as the narrow implementation boundary.

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

Identify existing test style and the nearest regression boundary.

Hard tasks require caller evidence to control compatibility risk.

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

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

Apply a localized change that follows existing abstractions.

Obtain executable evidence for the requested behavior.

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

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

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


Instruction: Fix the defect where the timeout returns stale state after an update in the code search service. The affected entry point is TimeoutPolicy45206; keep the change aligned with the existing HTTP API boundary.

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

The timeout no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/timeout/test_timeout_452_06.ts

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

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

Question: TimeoutPolicy45206|cache_invalidation_defect

Locate the implementation and callers associated with TimeoutPolicy45206.

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

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

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

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

Check static constraints relevant to the modified code.

Diff inspection is required before making a completion claim.


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

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The search no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: SearchPolicy45207|unit_conversion_defect

Locate the implementation and callers associated with SearchPolicy45207.

Search evidence identifies src/search/search_452_07.php as the narrow implementation boundary.

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

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


Instruction: Add regression coverage for the case where the index performs authorization after the side effect in the code search service. The affected entry point is IndexPolicy45208; keep the change aligned with the existing HTTP API boundary.

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

The index no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/index/test_index_452_08.ts

Question: IndexPolicy45208|authorization_order_defect

Locate the implementation and callers associated with IndexPolicy45208.

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


Instruction: Fix the defect where the migration silently truncates an oversized payload in the code search service. The affected entry point is MigrationPolicy45209; keep the change aligned with the existing HTTP API boundary.

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

The migration no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/migration/test_migration_452_09.ts


Instruction: Harden the upload in the code search service against replay attacks while preserving valid behavior. The affected entry point is UploadPolicy45210; keep the change aligned with the existing HTTP API boundary.

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

The upload no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Locate the implementation and callers associated with UploadPolicy45210.

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

correct compatibility defect while preserving the public contract


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

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

The download no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: DownloadPolicy45211|resource_cleanup_defect

Locate the implementation and callers associated with DownloadPolicy45211.

Search evidence identifies src/download/download_452_11.rs as the narrow implementation boundary.

correct resource-cleanup defect while preserving the public contract

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

Question: authorize|permission|sanitize|validate

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

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


Instruction: Fix the defect where the audit rejects valid boundary values in the code search service. The affected entry point is AuditPolicy45212; keep the change aligned with the existing HTTP API boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The audit no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/audit/test_audit_452_12.ts

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

Confirm the local module boundary before searching for implementation details.

Question: AuditPolicy45212|boundary_condition_defect

Locate the implementation and callers associated with AuditPolicy45212.

Search evidence identifies src/audit/audit_452_12.ts as the narrow implementation boundary.

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

Identify existing test style and the nearest regression boundary.

correct boundary-condition 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 worker drops the original error context in the code search service. The affected entry point is WorkerPolicy45213; keep the change aligned with the existing HTTP API boundary.

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

The worker no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: WorkerPolicy45213|error_propagation_defect

Locate the implementation and callers associated with WorkerPolicy45213.

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

Obtain executable evidence for the requested behavior.

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


Instruction: Add regression coverage for the case where the scheduler fails when an optional field is absent in the code search service. The affected entry point is SchedulerPolicy45214; keep the change aligned with the existing HTTP API boundary.

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

The scheduler no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

ctest -R SchedulerRegression45214 --output-on-failure

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

Locate the implementation and callers associated with SchedulerPolicy45214.

Search evidence identifies src/scheduler/scheduler_452_14.cpp as the narrow implementation boundary.

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

correct nullability defect while preserving the public contract

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


Instruction: Review the proposed router change in the code search service for correctness, scope, and regressions. The affected entry point is RouterPolicy45215; 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 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_452_15.ts

Question: RouterPolicy45215|sensitive_data_exposure

Locate the implementation and callers associated with RouterPolicy45215.

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

correct sensitive-data exposure 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.

Diff inspection is required before making a completion claim.


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

Locate the implementation and callers associated with MetricsPolicy45216.

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

correct idempotency defect while preserving the public contract


Instruction: Refactor the logging in the code search service to remove duplicated configuration parsing without changing behavior. The affected entry point is LoggingPolicy45217; keep the change aligned with the existing HTTP API 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

./gradlew test --tests LoggingRegression45217

Question: LoggingPolicy45217|resource_bounding_defect

Locate the implementation and callers associated with LoggingPolicy45217.

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

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


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

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

The sandbox no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: SandboxPolicy45218|failure_classification_defect

correct failure-classification defect while preserving the public contract


Instruction: Fix the defect where the session accepts malformed input after normalization in the code search service. The affected entry point is SessionPolicy45219; keep the change aligned with the existing HTTP API 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

Question: SessionPolicy45219|validation_order_defect

correct validation-order defect while preserving the public contract


Instruction: Refactor the serializer in the artifact registry to remove duplicated authorization checks without changing behavior. The affected entry point is SerializerPolicy45300; keep the change aligned with the existing background processor boundary.

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

The serializer no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

go test ./serializer -run SerializerRegression45300

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

Search evidence identifies internal/serializer/serializer_453_00.go as the narrow implementation boundary.

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

Check static constraints relevant to the modified code.


Instruction: Add guarded support for cursor pagination in the validator of the artifact registry. The affected entry point is ValidatorPolicy45301; keep the change aligned with the existing background processor boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The validator no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/validator/test_validator_453_01.ts

Locate the implementation and callers associated with ValidatorPolicy45301.

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

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

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

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

Identify existing test style and the nearest regression boundary.

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

Apply a localized change that follows existing abstractions.

Obtain executable evidence for the requested behavior.

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


Instruction: Fix the defect where the retry skips cleanup after cancellation in the artifact registry. The affected entry point is RetryPolicy45302; keep the change aligned with the existing background processor boundary.

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

The retry no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/retry/test_retry_453_02.ts

Question: RetryPolicy45302|resource_cleanup_defect


Instruction: Correct the configuration and operator guidance for structured errors in the artifact registry. The affected entry point is TimeoutPolicy45303; keep the change aligned with the existing background processor boundary.

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

The timeout no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

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

Question: TimeoutPolicy45303|boundary_condition_defect

Locate the implementation and callers associated with TimeoutPolicy45303.

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

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

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


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

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

The search no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: SearchPolicy45304|error_propagation_defect

Locate the implementation and callers associated with SearchPolicy45304.

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

Diff inspection is required before making a completion claim.


Instruction: Add guarded support for dry-run mode in the index of the artifact registry. The affected entry point is IndexPolicy45305; keep the change aligned with the existing background processor boundary.

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

The index no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/index/test_index_453_05.ts

Locate the implementation and callers associated with IndexPolicy45305.

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

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

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


Instruction: Correct the configuration and operator guidance for explicit timeouts in the artifact registry. The affected entry point is MigrationPolicy45306; keep the change aligned with the existing background processor boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The migration no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Locate the implementation and callers associated with MigrationPolicy45306.

Search evidence identifies src/migration/migration_453_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.


Instruction: Add regression coverage for the case where the upload creates duplicate jobs under concurrent delivery in the artifact registry. The affected entry point is UploadPolicy45307; keep the change aligned with the existing background processor boundary.

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

The upload no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/upload/test_upload_453_07.ts

Locate the implementation and callers associated with UploadPolicy45307.

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


Instruction: Fix the defect where the download loads an unbounded result set in the artifact registry. The affected entry point is DownloadPolicy45308; keep the change aligned with the existing background processor boundary.

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

The download no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/download/test_download_453_08.ts

Question: DownloadPolicy45308|resource_bounding_defect


Instruction: Review the proposed audit change in the artifact registry for correctness, scope, and regressions. The affected entry point is AuditPolicy45309; keep the change aligned with the existing background processor boundary.

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

The audit no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

go test ./audit -run AuditRegression45309

Question: AuditPolicy45309|failure_classification_defect

Locate the implementation and callers associated with AuditPolicy45309.

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

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

Question: authorize|permission|sanitize|validate

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

The first targeted test fails and provides a concrete counterexample.

Repeating the same patch would ignore the new test evidence.

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

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

Apply the second bounded patch addressing the diagnosed cause.

The repaired behavior must be re-executed before completion.

Confirm the revised patch satisfies the original acceptance criterion.


Instruction: Fix the defect where the worker accepts malformed input after normalization in the artifact registry. The affected entry point is WorkerPolicy45310; keep the change aligned with the existing background processor boundary.

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

The worker no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/worker/test_worker_453_10.ts

Question: WorkerPolicy45310|validation_order_defect

Locate the implementation and callers associated with WorkerPolicy45310.

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

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

Apply a localized change that follows existing abstractions.

Obtain executable evidence for the requested behavior.

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

Check static constraints relevant to the modified code.

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


Instruction: Harden the scheduler in the artifact registry against unbounded resource use while preserving valid behavior. The affected entry point is SchedulerPolicy45311; keep the change aligned with the existing background processor boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The scheduler no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

correct retry-safety defect while preserving the public contract

Verify the claimed behavior with targeted checks before completion.


Instruction: Correct the configuration and operator guidance for bounded retries in the artifact registry. The affected entry point is RouterPolicy45312; keep the change aligned with the existing background processor boundary.

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

The router no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

dotnet test --filter RouterRegression45312

Question: RouterPolicy45312|state_isolation_defect

correct state-isolation defect while preserving the public contract

Ground every decision in repository evidence before editing.


Instruction: Refactor the metrics in the artifact registry to remove duplicated validation logic without changing behavior. The affected entry point is MetricsPolicy45313; keep the change aligned with the existing background processor boundary.

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

The metrics no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

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

Question: MetricsPolicy45313|identity_comparison_defect

Locate the implementation and callers associated with MetricsPolicy45313.

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

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

correct identity-comparison defect while preserving the public contract

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

Diff inspection is required before making a completion claim.


Instruction: Add regression coverage for the case where the logging marks partial work as successful in the artifact registry. The affected entry point is LoggingPolicy45314; keep the change aligned with the existing background processor boundary.

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

The logging no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Locate the implementation and callers associated with LoggingPolicy45314.

Search evidence identifies src/logging/logging_453_14.php as the narrow implementation boundary.

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

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

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

Identify existing test style and the nearest regression boundary.

correct false-success defect while preserving the public contract


Instruction: Fix the defect where the sandbox uses a broad filesystem permission in the artifact registry. The affected entry point is SandboxPolicy45315; keep the change aligned with the existing background processor 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

go test ./sandbox -run SandboxRegression45315

Question: SandboxPolicy45315|least_privilege_defect

Locate the implementation and callers associated with SandboxPolicy45315.

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

Hard tasks require caller evidence to control compatibility risk.

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

correct least-privilege 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 error mapping without changing behavior. The affected entry point is SessionPolicy45316; keep the change aligned with the existing background processor boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The session no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/session/test_session_453_16.ts

repair diagnosed cause without broadening scope

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

Confirm the local module boundary before searching for implementation details.

Locate the implementation and callers associated with SessionPolicy45316.

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

correct verification defect while preserving the public contract


Instruction: Refactor the token in the artifact registry to remove duplicated error mapping without changing behavior. The affected entry point is TokenPolicy45317; keep the change aligned with the existing background processor boundary.

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

The token no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/token/test_token_453_17.ts

Question: TokenPolicy45317|cache_invalidation_defect

correct cache-invalidation defect while preserving the public contract

revise the failed assumption without expanding scope


Instruction: Correct the configuration and operator guidance for explicit timeouts in the artifact registry. The affected entry point is PaginationPolicy45318; keep the change aligned with the existing background processor boundary.

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

The pagination no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests PaginationRegression45318

Locate the implementation and callers associated with PaginationPolicy45318.

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

correct unit-conversion 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 cache performs authorization after the side effect in the artifact registry. The affected entry point is CachePolicy45319; 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 cache no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

dotnet test --filter CacheRegression45319

Question: CachePolicy45319|authorization_order_defect

Locate the implementation and callers associated with CachePolicy45319.

Search evidence identifies src/cache/CacheService453.cs as the narrow implementation boundary.

correct authorization-order defect while preserving the public contract


Instruction: Fix the defect where the timeout misclassifies transient failures as permanent in the billing worker. The affected entry point is TimeoutPolicy45400; keep the change aligned with the existing library package boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The timeout no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: TimeoutPolicy45400|failure_classification_defect

Locate the implementation and callers associated with TimeoutPolicy45400.

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

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

Apply a localized change that follows existing abstractions.

The first targeted test fails and provides a concrete counterexample.

Repeating the same patch would ignore the new test evidence.

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

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

Apply the second bounded patch addressing the diagnosed cause.

The repaired behavior must be re-executed before completion.

Confirm the revised patch satisfies the original acceptance criterion.

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


Instruction: Add guarded support for graceful shutdown in the search of the billing worker. The affected entry point is SearchPolicy45401; keep the change aligned with the existing library package boundary.

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

The search no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

go test ./search -run SearchRegression45401

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

Question: SearchPolicy45401|validation_order_defect

Locate the implementation and callers associated with SearchPolicy45401.

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

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

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

Obtain executable evidence for the requested behavior.

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

Check static constraints relevant to the modified code.

Diff inspection is required before making a completion claim.


Instruction: Add regression coverage for the case where the index retries a non-idempotent operation in the billing worker. The affected entry point is IndexPolicy45402; keep the change aligned with the existing library package boundary.

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

The index no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Locate the implementation and callers associated with IndexPolicy45402.

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

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

Identify existing test style and the nearest regression boundary.

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

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


Instruction: Fix the defect where the migration mutates shared state across requests in the billing worker. The affected entry point is MigrationPolicy45403; keep the change aligned with the existing library package boundary.

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

The migration no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests MigrationRegression45403

rewrite subsystem
replace dependencies
change API

Use a bounded, updateable plan proportional to task complexity.


Instruction: Add guarded support for bounded retries in the upload of the billing worker. The affected entry point is UploadPolicy45404; keep the change aligned with the existing library package boundary.

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

The upload no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/upload/test_upload_454_04.ts

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

Confirm the local module boundary before searching for implementation details.

Question: UploadPolicy45404|identity_comparison_defect

Locate the implementation and callers associated with UploadPolicy45404.

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


Instruction: Fix the defect where the download marks partial work as successful in the billing worker. The affected entry point is DownloadPolicy45405; keep the change aligned with the existing library package boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The download no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: DownloadPolicy45405|false_success_defect

Locate the implementation and callers associated with DownloadPolicy45405.

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

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

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


Instruction: Add regression coverage for the case where the audit uses a broad filesystem permission in the billing worker. The affected entry point is AuditPolicy45406; keep the change aligned with the existing library package boundary.

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

The audit no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Locate the implementation and callers associated with AuditPolicy45406.

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

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

Apply a localized change that follows existing abstractions.


Instruction: Add regression coverage for the case where the worker does not verify the persisted state in the billing worker. The affected entry point is WorkerPolicy45407; keep the change aligned with the existing library package boundary.

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

The worker no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests WorkerRegression45407

Locate the implementation and callers associated with WorkerPolicy45407.

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


Instruction: Add guarded support for idempotency keys in the scheduler of the billing worker. The affected entry point is SchedulerPolicy45408; keep the change aligned with the existing library package boundary.

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

The scheduler no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Locate the implementation and callers associated with SchedulerPolicy45408.

Search evidence identifies src/scheduler/scheduler_454_08.php as the narrow implementation boundary.

The first targeted test fails and provides a concrete counterexample.

Repeating the same patch would ignore the new test evidence.

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

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

Apply the second bounded patch addressing the diagnosed cause.

The repaired behavior must be re-executed before completion.

Confirm the revised patch satisfies the original acceptance criterion.

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


Instruction: Fix the defect where the router uses seconds where milliseconds are expected in the billing worker. The affected entry point is RouterPolicy45409; keep the change aligned with the existing library package boundary.

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

The router no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/router/test_router_454_09.ts

Question: RouterPolicy45409|unit_conversion_defect


Instruction: Add guarded support for explicit timeouts in the metrics of the billing worker. The affected entry point is MetricsPolicy45410; keep the change aligned with the existing library package boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The metrics no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

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

Question: MetricsPolicy45410|authorization_order_defect

Locate the implementation and callers associated with MetricsPolicy45410.

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

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

Obtain executable evidence for the requested behavior.

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

Check static constraints relevant to the modified code.

Diff inspection is required before making a completion claim.


Instruction: Refactor the logging in the billing worker to remove duplicated state transitions without changing behavior. The affected entry point is LoggingPolicy45411; keep the change aligned with the existing library package boundary.

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

The logging no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: LoggingPolicy45411|input_size_handling_defect

Locate the implementation and callers associated with LoggingPolicy45411.

Search evidence identifies src/logging/logging_454_11.php as the narrow implementation boundary.

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

correct input-size handling defect while preserving the public contract


Instruction: Add guarded support for input size limits in the sandbox of the billing worker. The affected entry point is SandboxPolicy45412; keep the change aligned with the existing library package boundary.

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

The sandbox no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests SandboxRegression45412

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

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

correct compatibility defect while preserving the public contract


Instruction: Refactor the session in the billing worker to remove duplicated cleanup logic without changing behavior. The affected entry point is SessionPolicy45413; keep the change aligned with the existing library package boundary.

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

The session no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/session/test_session_454_13.ts

Question: SessionPolicy45413|resource_cleanup_defect

correct resource-cleanup defect while preserving the public contract


Instruction: Fix the defect where the token rejects valid boundary values in the billing worker. The affected entry point is TokenPolicy45414; keep the change aligned with the existing library package boundary.

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

The token no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

go test ./token -run TokenRegression45414

Question: TokenPolicy45414|boundary_condition_defect


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

go test ./pagination -run PaginationRegression45415

Locate the implementation and callers associated with PaginationPolicy45415.

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

correct error-propagation 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 cache fails when an optional field is absent in the billing worker. The affected entry point is CachePolicy45416; keep the change aligned with the existing library package 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_454_16.ts

correct nullability defect while preserving the public contract


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

Question: QueuePolicy45417|sensitive_data_exposure

Locate the implementation and callers associated with QueuePolicy45417.

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

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

correct sensitive-data exposure while preserving the public contract

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.

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


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

A targeted verification path is identified

The final change remains inside the requested scope

correct idempotency defect while preserving the public contract


Instruction: Add regression coverage for the case where the permission loads an unbounded result set in the billing worker. The affected entry point is PermissionPolicy45419; keep the change aligned with the existing library package boundary.

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

The permission no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/permission/test_permission_454_19.ts

Locate the implementation and callers associated with PermissionPolicy45419.

Search evidence identifies src/permission/permission_454_19.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 resource-bounding defect while preserving the public contract

Obtain executable evidence for the requested behavior.


Instruction: Add guarded support for idempotency keys in the migration of the notification router. The affected entry point is MigrationPolicy45500; keep the change aligned with the existing plugin-based service boundary.

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

The migration no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

dotnet test --filter MigrationRegression45500

Locate the implementation and callers associated with MigrationPolicy45500.

Search evidence identifies src/migration/MigrationService455.cs 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: Fix the defect where the upload performs authorization after the side effect in the notification router. The affected entry point is UploadPolicy45501; keep the change aligned with the existing plugin-based service boundary.

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

The upload no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: UploadPolicy45501|authorization_order_defect

Locate the implementation and callers associated with UploadPolicy45501.

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

Check static constraints relevant to the modified code.


Instruction: Fix the defect where the download silently truncates an oversized payload in the notification router. The affected entry point is DownloadPolicy45502; keep the change aligned with the existing plugin-based service boundary.

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

The download no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

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

Question: DownloadPolicy45502|input_size_handling_defect

Locate the implementation and callers associated with DownloadPolicy45502.

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

Apply a localized change that follows existing abstractions.

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: Add guarded support for audit metadata in the audit of the notification router. The affected entry point is AuditPolicy45503; keep the change aligned with the existing plugin-based service boundary.

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

The audit no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Locate the implementation and callers associated with AuditPolicy45503.

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

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

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

Produce only evidence-backed findings with severity and confidence.


Instruction: Refactor the worker in the notification router to remove duplicated retry decisions without changing behavior. The affected entry point is WorkerPolicy45504; keep the change aligned with the existing plugin-based service boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The worker no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests WorkerRegression45504

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

Confirm the local module boundary before searching for implementation details.

Question: WorkerPolicy45504|resource_cleanup_defect

Locate the implementation and callers associated with WorkerPolicy45504.

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

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


Instruction: Fix the defect where the scheduler rejects valid boundary values in the notification router. The affected entry point is SchedulerPolicy45505; keep the change aligned with the existing plugin-based service boundary.

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

The scheduler no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

correct boundary-condition defect while preserving the public contract


Instruction: Fix the defect where the router drops the original error context in the notification router. The affected entry point is RouterPolicy45506; keep the change aligned with the existing plugin-based service boundary.

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

The router no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/router/test_router_455_06.ts

Question: RouterPolicy45506|error_propagation_defect

Locate the implementation and callers associated with RouterPolicy45506.

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

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


Instruction: Fix the defect where the metrics fails when an optional field is absent in the notification router. The affected entry point is MetricsPolicy45507; keep the change aligned with the existing plugin-based service boundary.

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

The metrics no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/metrics/test_metrics_455_07.ts

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

Locate the implementation and callers associated with MetricsPolicy45507.

Search evidence identifies src/metrics/metrics_455_07.ts as the narrow implementation boundary.

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

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

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