Instruction: Add regression coverage for the case where the upload drops the original error context in the notification router. The affected entry point is UploadPolicy48001; keep the change aligned with the existing layered 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: UploadPolicy48001|error_propagation_defect

Locate the implementation and callers associated with UploadPolicy48001.

Search evidence identifies src/upload/upload_480_01.rs as the narrow implementation boundary.

The first targeted test fails and provides a concrete counterexample.

Repeating the same patch would ignore the new test evidence.

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

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

Apply the second bounded patch addressing the diagnosed cause.

The repaired behavior must be re-executed before completion.

Confirm the revised patch satisfies the original acceptance criterion.

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


Instruction: Add guarded support for request cancellation in the download of the notification router. The affected entry point is DownloadPolicy48002; keep the change aligned with the existing layered service boundary.

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

The download no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

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

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

Locate the implementation and callers associated with DownloadPolicy48002.

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

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

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

Identify existing test style and the nearest regression boundary.

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

correct nullability defect while preserving the public contract

Apply a localized change that follows existing abstractions.

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

revise the failed assumption without expanding scope

Diff inspection is required before making a completion claim.

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


Instruction: Refactor the audit in the notification router to remove duplicated error mapping without changing behavior. The affected entry point is AuditPolicy48003; keep the change aligned with the existing layered service boundary.

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

The audit no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests AuditRegression48003

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

The diff includes a configuration change outside the requested boundary.

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

repair diagnosed cause without broadening scope

Question: AuditPolicy48003|sensitive_data_exposure

Locate the implementation and callers associated with AuditPolicy48003.

Search evidence identifies src/main/java/audit/AuditService480.java as the narrow implementation boundary.

correct sensitive-data exposure while preserving the public contract

The original acceptance criterion passes

The failure signal is no longer reproduced

The final report distinguishes executed evidence from assumptions


Instruction: Fix the defect where the worker creates duplicate jobs under concurrent delivery in the notification router. The affected entry point is WorkerPolicy48004; keep the change aligned with the existing layered 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

ctest -R WorkerRegression48004 --output-on-failure

Use a bounded, updateable plan proportional to task complexity.

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

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

correct idempotency defect while preserving the public contract

Obtain executable evidence for the requested behavior.


Instruction: Add regression coverage for the case where the scheduler loads an unbounded result set in the notification router. The affected entry point is SchedulerPolicy48005; keep the change aligned with the existing layered 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

./gradlew test --tests SchedulerRegression48005

Ground every decision in repository evidence before editing.

correct resource-bounding defect while preserving the public contract


Instruction: Add regression coverage for the case where the router misclassifies transient failures as permanent in the notification router. The affected entry point is RouterPolicy48006; keep the change aligned with the existing layered 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_480_06.ts

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

Question: RouterPolicy48006|failure_classification_defect

Locate the implementation and callers associated with RouterPolicy48006.

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

correct failure-classification defect while preserving the public contract

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

Check static constraints relevant to the modified code.


Instruction: Fix the defect where the metrics accepts malformed input after normalization in the notification router. The affected entry point is MetricsPolicy48007; keep the change aligned with the existing layered service boundary.

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

The metrics no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

go test ./metrics -run MetricsRegression48007

Respect scope and request approval only for materially risky actions.

Question: MetricsPolicy48007|validation_order_defect

Locate the implementation and callers associated with MetricsPolicy48007.

Search evidence identifies internal/metrics/metrics_480_07.go as the narrow implementation boundary.

Unnecessary approval requests would reduce agent usefulness without improving safety.

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

correct validation-order defect while preserving the public contract


Instruction: Add guarded support for input size limits in the logging of the notification router. The affected entry point is LoggingPolicy48008; keep the change aligned with the existing layered service boundary.

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

The logging no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

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

correct retry-safety defect while preserving the public contract

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


Instruction: Harden the sandbox in the notification router against replay attacks while preserving valid behavior. The affected entry point is SandboxPolicy48009; keep the change aligned with the existing layered service boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The sandbox no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

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

Question: SandboxPolicy48009|state_isolation_defect

Locate the implementation and callers associated with SandboxPolicy48009.

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

correct state-isolation defect while preserving the public contract

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

Question: authorize|permission|sanitize|validate

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


Instruction: Harden the session in the notification router against replay attacks while preserving valid behavior. The affected entry point is SessionPolicy48010; keep the change aligned with the existing layered service boundary.

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

The session no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/session/test_session_480_10.ts

Ground every decision in repository evidence before editing.

Question: SessionPolicy48010|identity_comparison_defect

Locate the implementation and callers associated with SessionPolicy48010.

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

correct identity-comparison defect while preserving the public contract

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

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

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


Instruction: Refactor the token in the notification router to remove duplicated configuration parsing without changing behavior. The affected entry point is TokenPolicy48011; keep the change aligned with the existing layered service boundary.

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

The token no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

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

Locate the implementation and callers associated with TokenPolicy48011.

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

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

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

Identify existing test style and the nearest regression boundary.

Hard tasks require caller evidence to control compatibility risk.

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

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

correct false-success defect while preserving the public contract

Apply a localized change that follows existing abstractions.

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

Diff inspection is required before making a completion claim.


Instruction: Add regression coverage for the case where the pagination uses a broad filesystem permission in the notification router. The affected entry point is PaginationPolicy48012; keep the change aligned with the existing layered service boundary.

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

The pagination no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests PaginationRegression48012

Verify the claimed behavior with targeted checks before completion.

correct least-privilege defect while preserving the public contract


Instruction: Fix the defect where the cache does not verify the persisted state in the notification router. The affected entry point is CachePolicy48013; keep the change aligned with the existing layered service boundary.

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

The cache no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/cache/test_cache_480_13.ts

Locate the implementation and callers associated with CachePolicy48013.

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

correct verification defect while preserving the public contract

The first targeted test fails and provides a concrete counterexample.

Repeating the same patch would ignore the new test evidence.

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

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

Apply the second bounded patch addressing the diagnosed cause.

The repaired behavior must be re-executed before completion.

Confirm the revised patch satisfies the original acceptance criterion.


Instruction: Refactor the queue in the notification router to remove duplicated authorization checks without changing behavior. The affected entry point is QueuePolicy48014; keep the change aligned with the existing layered service boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The queue no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/queue/test_queue_480_14.ts

Question: QueuePolicy48014|cache_invalidation_defect

Locate the implementation and callers associated with QueuePolicy48014.

Search evidence identifies src/queue/queue_480_14.ts as the narrow implementation boundary.

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

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

correct cache-invalidation defect while preserving the public contract

Obtain executable evidence for the requested behavior.


Instruction: Correct the configuration and operator guidance for structured errors in the notification router. The affected entry point is WebhookPolicy48015; keep the change aligned with the existing layered service 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

Question: WebhookPolicy48015|unit_conversion_defect

correct unit-conversion defect while preserving the public contract


Instruction: Fix the defect where the permission performs authorization after the side effect in the notification router. The affected entry point is PermissionPolicy48016; keep the change aligned with the existing layered service 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

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

Search evidence identifies src/permission/permission_480_16.rs as the narrow implementation boundary.

correct authorization-order defect while preserving the public contract

revise the failed assumption without expanding scope

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


Instruction: Refactor the configuration in the notification router to remove duplicated serialization logic without changing behavior. The affected entry point is ConfigurationPolicy48017; keep the change aligned with the existing layered service boundary.

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

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

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

correct input-size handling defect while preserving the public contract

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


Instruction: Fix the defect where the parser does not preserve the public error contract in the notification router. The affected entry point is ParserPolicy48018; keep the change aligned with the existing layered service 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_480_18.ts

Locate the implementation and callers associated with ParserPolicy48018.

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

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

correct compatibility defect while preserving the public contract

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

Check static constraints relevant to the modified code.


Instruction: Harden the serializer in the notification router against command injection while preserving valid behavior. The affected entry point is SerializerPolicy48019; keep the change aligned with the existing layered service boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The serializer no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/serializer/test_serializer_480_19.ts

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

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

Locate the implementation and callers associated with SerializerPolicy48019.

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

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

correctness security compatibility test_coverage

Produce only evidence-backed findings with severity and confidence.


Instruction: Add guarded support for input size limits in the audit of the feature flag service. The affected entry point is AuditPolicy48100; keep the change aligned with the existing modular monolith 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

Locate the implementation and callers associated with AuditPolicy48100.

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

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

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

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

Diff inspection is required before making a completion claim.


Instruction: Harden the worker in the feature flag service against command injection while preserving valid behavior. The affected entry point is WorkerPolicy48101; keep the change aligned with the existing modular monolith boundary.

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

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

Question: WorkerPolicy48101|identity_comparison_defect

Locate the implementation and callers associated with WorkerPolicy48101.

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

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

Question: authorize|permission|sanitize|validate

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


Instruction: Review the proposed scheduler change in the feature flag service for correctness, scope, and regressions. The affected entry point is SchedulerPolicy48102; keep the change aligned with the existing modular monolith 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

dotnet test --filter SchedulerRegression48102

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


Instruction: Review the proposed router change in the feature flag service for correctness, scope, and regressions. The affected entry point is RouterPolicy48103; keep the change aligned with the existing modular monolith 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

Verify the claimed behavior with targeted checks before completion.

Question: RouterPolicy48103|least_privilege_defect

Locate the implementation and callers associated with RouterPolicy48103.

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

Obtain executable evidence for the requested behavior.


Instruction: Add guarded support for bounded retries in the metrics of the feature flag service. The affected entry point is MetricsPolicy48104; keep the change aligned with the existing modular monolith 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


Instruction: Harden the logging in the feature flag service against unbounded resource use while preserving valid behavior. The affected entry point is LoggingPolicy48105; keep the change aligned with the existing modular monolith boundary.

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

The logging no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/logging/test_logging_481_05.ts

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

repair diagnosed cause without broadening scope

Question: LoggingPolicy48105|cache_invalidation_defect

Locate the implementation and callers associated with LoggingPolicy48105.

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

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

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


Instruction: Add guarded support for request cancellation in the sandbox of the feature flag service. The affected entry point is SandboxPolicy48106; keep the change aligned with the existing modular monolith boundary.

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

The sandbox no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: SandboxPolicy48106|unit_conversion_defect

Locate the implementation and callers associated with SandboxPolicy48106.

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

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


Instruction: Fix the defect where the session performs authorization after the side effect in the feature flag service. The affected entry point is SessionPolicy48107; keep the change aligned with the existing modular monolith boundary.

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

The session no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: SessionPolicy48107|authorization_order_defect

Locate the implementation and callers associated with SessionPolicy48107.

Search evidence identifies src/session/session_481_07.py as the narrow implementation boundary.

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

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

Check static constraints relevant to the modified code.


Instruction: Add guarded support for idempotency keys in the token of the feature flag service. The affected entry point is TokenPolicy48108; keep the change aligned with the existing modular monolith boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The token no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

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

Locate the implementation and callers associated with TokenPolicy48108.

Search evidence identifies src/token/token_481_08.rs as the narrow implementation boundary.

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

Identify existing test style and the nearest regression boundary.


Instruction: Fix the defect where the pagination does not preserve the public error contract in the feature flag service. The affected entry point is PaginationPolicy48109; keep the change aligned with the existing modular monolith boundary.

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

The pagination no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests PaginationRegression48109

Locate the implementation and callers associated with PaginationPolicy48109.

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

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

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

Hard tasks require caller evidence to control compatibility risk.

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


Instruction: Fix the defect where the cache skips cleanup after cancellation in the feature flag service. The affected entry point is CachePolicy48110; keep the change aligned with the existing modular monolith 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

Question: CachePolicy48110|resource_cleanup_defect

Locate the implementation and callers associated with CachePolicy48110.

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

Unnecessary approval requests would reduce agent usefulness without improving safety.

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

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

correct resource-cleanup defect while preserving the public contract

Apply a localized change that follows existing abstractions.

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

Obtain executable evidence for the requested behavior.

Diff inspection is required before making a completion claim.


Instruction: Add guarded support for audit metadata in the queue of the feature flag service. The affected entry point is QueuePolicy48111; keep the change aligned with the existing modular monolith boundary.

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

The queue no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: QueuePolicy48111|boundary_condition_defect

Locate the implementation and callers associated with QueuePolicy48111.

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

correct boundary-condition defect while preserving the public contract


Instruction: Fix the defect where the webhook drops the original error context in the feature flag service. The affected entry point is WebhookPolicy48112; keep the change aligned with the existing modular monolith 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_481_12.ts

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

Question: WebhookPolicy48112|error_propagation_defect

Locate the implementation and callers associated with WebhookPolicy48112.

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

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 feature flag service. The affected entry point is PermissionPolicy48113; keep the change aligned with the existing modular monolith boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The permission no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests PermissionRegression48113

Locate the implementation and callers associated with PermissionPolicy48113.

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

correct nullability defect while preserving the public contract

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


Instruction: Refactor the configuration in the feature flag service to remove duplicated configuration parsing without changing behavior. The affected entry point is ConfigurationPolicy48114; keep the change aligned with the existing modular monolith 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 ConfigurationPolicy48114.

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

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

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

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

correct sensitive-data exposure while preserving the public contract


Instruction: Review the proposed parser change in the feature flag service for correctness, scope, and regressions. The affected entry point is ParserPolicy48115; keep the change aligned with the existing modular monolith 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_481_15.ts

Locate the implementation and callers associated with ParserPolicy48115.

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

correct idempotency defect while preserving the public contract

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

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


Instruction: Refactor the serializer in the feature flag service to remove duplicated authorization checks without changing behavior. The affected entry point is SerializerPolicy48116; keep the change aligned with the existing modular monolith boundary.

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

The serializer no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

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

Confirm the local module boundary before searching for implementation details.

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

Locate the implementation and callers associated with SerializerPolicy48116.

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

correct resource-bounding defect while preserving the public contract

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

Check static constraints relevant to the modified code.


Instruction: Add guarded support for cursor pagination in the validator of the feature flag service. The affected entry point is ValidatorPolicy48117; keep the change aligned with the existing modular monolith 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

npm test -- test/validator/test_validator_481_17.ts

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


Instruction: Add guarded support for request cancellation in the retry of the feature flag service. The affected entry point is RetryPolicy48118; keep the change aligned with the existing modular monolith 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 RetryRegression48118

Question: RetryPolicy48118|validation_order_defect

Locate the implementation and callers associated with RetryPolicy48118.

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

correct validation-order defect while preserving the public contract

Apply a localized change that follows existing abstractions.

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

Obtain executable evidence for the requested behavior.

Diff inspection is required before making a completion claim.


Instruction: Add regression coverage for the case where the timeout retries a non-idempotent operation in the feature flag service. The affected entry point is TimeoutPolicy48119; keep the change aligned with the existing modular monolith 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

npm test -- test/timeout/test_timeout_481_19.ts

Locate the implementation and callers associated with TimeoutPolicy48119.

Search evidence identifies src/timeout/timeout_481_19.ts 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 idempotency keys in the router of the audit log processor. The affected entry point is RouterPolicy48200; 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 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_482_00.ts

Locate the implementation and callers associated with RouterPolicy48200.

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

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


Instruction: Correct the configuration and operator guidance for dry-run mode in the audit log processor. The affected entry point is MetricsPolicy48201; 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 metrics no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: MetricsPolicy48201|resource_cleanup_defect

Locate the implementation and callers associated with MetricsPolicy48201.

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

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

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

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


Instruction: Review the proposed logging change in the audit log processor for correctness, scope, and regressions. The affected entry point is LoggingPolicy48202; keep the change aligned with the existing event-driven worker boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The logging no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: LoggingPolicy48202|boundary_condition_defect

Locate the implementation and callers associated with LoggingPolicy48202.

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

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

Question: authorize|permission|sanitize|validate

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

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: Add guarded support for audit metadata in the sandbox of the audit log processor. The affected entry point is SandboxPolicy48203; 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 sandbox 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: SandboxPolicy48203|error_propagation_defect

Locate the implementation and callers associated with SandboxPolicy48203.

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

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

Identify existing test style and the nearest regression boundary.

Apply a localized change that follows existing abstractions.


Instruction: Fix the defect where the session fails when an optional field is absent in the audit log processor. The affected entry point is SessionPolicy48204; keep the change aligned with the existing event-driven worker boundary.

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

The session no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

go test ./session -run SessionRegression48204

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

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

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

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

Obtain executable evidence for the requested behavior.

Diff inspection is required before making a completion claim.


Instruction: Refactor the token in the audit log processor to remove duplicated cleanup logic without changing behavior. The affected entry point is TokenPolicy48205; 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 token no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: TokenPolicy48205|sensitive_data_exposure

Locate the implementation and callers associated with TokenPolicy48205.

Search evidence identifies src/token/token_482_05.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 targeted check establishes the fix; the wider suite provides additional regression evidence.

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

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


Instruction: Add regression coverage for the case where the pagination creates duplicate jobs under concurrent delivery in the audit log processor. The affected entry point is PaginationPolicy48206; 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 pagination 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 PaginationPolicy48206.

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

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


Instruction: Review the proposed cache change in the audit log processor for correctness, scope, and regressions. The affected entry point is CachePolicy48207; keep the change aligned with the existing event-driven worker boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The cache no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: CachePolicy48207|resource_bounding_defect

Locate the implementation and callers associated with CachePolicy48207.

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

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

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


Instruction: Refactor the queue in the audit log processor to remove duplicated validation logic without changing behavior. The affected entry point is QueuePolicy48208; 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 queue no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: QueuePolicy48208|failure_classification_defect

Locate the implementation and callers associated with QueuePolicy48208.

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

correct failure-classification defect while preserving the public contract


Instruction: Add guarded support for cursor pagination in the webhook of the audit log processor. The affected entry point is WebhookPolicy48209; keep the change aligned with the existing event-driven worker boundary.

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

The webhook no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: WebhookPolicy48209|validation_order_defect

Locate the implementation and callers associated with WebhookPolicy48209.

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

The first targeted test fails and provides a concrete counterexample.

Repeating the same patch would ignore the new test evidence.

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

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

Apply the second bounded patch addressing the diagnosed cause.

The repaired behavior must be re-executed before completion.

Confirm the revised patch satisfies the original acceptance criterion.


Instruction: Harden the permission in the audit log processor against secret leakage while preserving valid behavior. The affected entry point is PermissionPolicy48210; 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 permission no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests PermissionRegression48210

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

Locate the implementation and callers associated with PermissionPolicy48210.

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

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

Identify existing test style and the nearest regression boundary.

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

correct retry-safety defect while preserving the public contract

Apply a localized change that follows existing abstractions.

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

Obtain executable evidence for the requested behavior.

Diff inspection is required before making a completion claim.


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

A targeted verification path is identified

The final change remains inside the requested scope

Question: authorize|permission|sanitize|validate

correct state-isolation defect while preserving the public contract

rewrite subsystem
replace dependencies
change API

Use a bounded, updateable plan proportional to task complexity.


Instruction: Add guarded support for idempotency keys in the parser of the audit log processor. The affected entry point is ParserPolicy48212; keep the change aligned with the existing event-driven worker boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The parser no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: ParserPolicy48212|identity_comparison_defect

correct identity-comparison defect while preserving the public contract


Instruction: Add regression coverage for the case where the serializer marks partial work as successful in the audit log processor. The affected entry point is SerializerPolicy48213; 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 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 SerializerPolicy48213.

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

correct false-success defect while preserving the public contract

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


Instruction: Harden the validator in the audit log processor against unsafe deserialization while preserving valid behavior. The affected entry point is ValidatorPolicy48214; keep the change aligned with the existing event-driven worker 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

go test ./validator -run ValidatorRegression48214

Question: authorize|permission|sanitize|validate

correct least-privilege defect while preserving the public contract


Instruction: Review the proposed retry change in the audit log processor for correctness, scope, and regressions. The affected entry point is RetryPolicy48215; 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 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 RetryPolicy48215.

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

correct verification defect while preserving the public contract

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

Check static constraints relevant to the modified code.

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 audit log processor. The affected entry point is TimeoutPolicy48216; 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 timeout no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: TimeoutPolicy48216|cache_invalidation_defect

correct cache-invalidation defect while preserving the public contract


Instruction: Fix the defect where the search uses seconds where milliseconds are expected in the audit log processor. The affected entry point is SearchPolicy48217; keep the change aligned with the existing event-driven worker 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

npm test -- test/search/test_search_482_17.ts

repair diagnosed cause without broadening scope

Question: SearchPolicy48217|unit_conversion_defect

Locate the implementation and callers associated with SearchPolicy48217.

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

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

Hard tasks require caller evidence to control compatibility risk.

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

correct unit-conversion defect while preserving the public contract

revise the failed assumption without expanding scope


Instruction: Add guarded support for per-tenant configuration in the index of the audit log processor. The affected entry point is IndexPolicy48218; 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 index no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: IndexPolicy48218|authorization_order_defect

Locate the implementation and callers associated with IndexPolicy48218.

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

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

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

correct authorization-order defect while preserving the public contract


Instruction: Fix the defect where the migration silently truncates an oversized payload in the audit log processor. The affected entry point is MigrationPolicy48219; keep the change aligned with the existing event-driven worker 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_482_19.ts

Locate the implementation and callers associated with MigrationPolicy48219.

Search evidence identifies src/migration/migration_482_19.ts 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 sandbox accepts malformed input after normalization in the developer portal. The affected entry point is SandboxPolicy48300; keep the change aligned with the existing CLI application 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

npm test -- test/sandbox/test_sandbox_483_00.ts

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

Question: SandboxPolicy48300|validation_order_defect


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

Locate the implementation and callers associated with SessionPolicy48301.

Search evidence identifies src/session/session_483_01.py as the narrow implementation boundary.


Instruction: Refactor the token in the developer portal to remove duplicated authorization checks without changing behavior. The affected entry point is TokenPolicy48302; keep the change aligned with the existing CLI application 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

./gradlew test --tests TokenRegression48302


Instruction: Fix the defect where the pagination matches identifiers case-insensitively in the developer portal. The affected entry point is PaginationPolicy48303; keep the change aligned with the existing CLI application 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

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

Locate the implementation and callers associated with PaginationPolicy48303.

Search evidence identifies src/pagination/pagination_483_03.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 implementation boundary and acceptance criterion are now supported by repository evidence.

Apply a localized change that follows existing abstractions.

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

The first targeted test fails and provides a concrete counterexample.

Repeating the same patch would ignore the new test evidence.

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

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

Apply the second bounded patch addressing the diagnosed cause.

The repaired behavior must be re-executed before completion.

Confirm the revised patch satisfies the original acceptance criterion.

Diff inspection is required before making a completion claim.


Instruction: Harden the cache in the developer portal against replay attacks while preserving valid behavior. The affected entry point is CachePolicy48304; 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 cache no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

go test ./cache -run CacheRegression48304

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

Search evidence identifies internal/cache/cache_483_04.go as the narrow implementation boundary.

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: Fix the defect where the queue uses a broad filesystem permission in the developer portal. The affected entry point is QueuePolicy48305; keep the change aligned with the existing CLI application boundary.

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

The queue no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

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

Locate the implementation and callers associated with QueuePolicy48305.

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

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

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

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


Instruction: Fix the defect where the webhook does not verify the persisted state in the developer portal. The affected entry point is WebhookPolicy48306; keep the change aligned with the existing CLI application boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The webhook no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/webhook/test_webhook_483_06.ts

Locate the implementation and callers associated with WebhookPolicy48306.

Search evidence identifies src/webhook/webhook_483_06.ts 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 permission returns stale state after an update in the developer portal. The affected entry point is PermissionPolicy48307; keep the change aligned with the existing CLI application boundary.

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

The permission no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope


Instruction: Correct the configuration and operator guidance for input size limits in the developer portal. The affected entry point is ConfigurationPolicy48308; keep the change aligned with the existing CLI application boundary.

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

The configuration no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/configuration/test_configuration_483_08.ts

Locate the implementation and callers associated with ConfigurationPolicy48308.

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

Identify existing test style and the nearest regression boundary.

Apply a localized change that follows existing abstractions.


Instruction: Add regression coverage for the case where the parser performs authorization after the side effect in the developer portal. The affected entry point is ParserPolicy48309; 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 parser 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: ParserPolicy48309|authorization_order_defect

Locate the implementation and callers associated with ParserPolicy48309.

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

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

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

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


Instruction: Refactor the serializer in the developer portal to remove duplicated cleanup logic without changing behavior. The affected entry point is SerializerPolicy48310; keep the change aligned with the existing CLI application boundary.

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

The serializer no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/serializer/test_serializer_483_10.ts

Locate the implementation and callers associated with SerializerPolicy48310.

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

correct input-size handling defect while preserving the public contract


Instruction: Fix the defect where the validator does not preserve the public error contract in the developer portal. The affected entry point is ValidatorPolicy48311; keep the change aligned with the existing CLI application boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The validator no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests ValidatorRegression48311

Locate the implementation and callers associated with ValidatorPolicy48311.

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

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

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

correct compatibility defect while preserving the public contract

Diff inspection is required before making a completion claim.


Instruction: Add regression coverage for the case where the retry skips cleanup after cancellation in the developer portal. The affected entry point is RetryPolicy48312; keep the change aligned with the existing CLI application 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

ctest -R RetryRegression48312 --output-on-failure

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

Confirm the local module boundary before searching for implementation details.

Question: RetryPolicy48312|resource_cleanup_defect

Locate the implementation and callers associated with RetryPolicy48312.

Search evidence identifies src/retry/retry_483_12.cpp as the narrow implementation boundary.

correct resource-cleanup defect while preserving the public contract

Obtain executable evidence for the requested behavior.


Instruction: Review the proposed timeout change in the developer portal for correctness, scope, and regressions. The affected entry point is TimeoutPolicy48313; keep the change aligned with the existing CLI application 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

dotnet test --filter TimeoutRegression48313

Question: TimeoutPolicy48313|boundary_condition_defect

Locate the implementation and callers associated with TimeoutPolicy48313.

Search evidence identifies src/timeout/TimeoutService483.cs as the narrow implementation boundary.

Hard tasks require caller evidence to control compatibility risk.

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

correct boundary-condition defect while preserving the public contract

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


Instruction: Refactor the search in the developer portal to remove duplicated validation logic without changing behavior. The affected entry point is SearchPolicy48314; 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 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 SearchRegression48314

Question: SearchPolicy48314|error_propagation_defect

Locate the implementation and callers associated with SearchPolicy48314.

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

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

correct error-propagation defect while preserving the public contract

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

Check static constraints relevant to the modified code.


Instruction: Refactor the index in the developer portal to remove duplicated error mapping without changing behavior. The affected entry point is IndexPolicy48315; keep the change aligned with the existing CLI application 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_483_15.ts

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

Locate the implementation and callers associated with IndexPolicy48315.

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

correct nullability defect while preserving the public contract

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

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


Instruction: Correct the configuration and operator guidance for idempotency keys in the developer portal. The affected entry point is MigrationPolicy48316; keep the change aligned with the existing CLI application 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

dotnet test --filter MigrationRegression48316

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

Locate the implementation and callers associated with MigrationPolicy48316.

Search evidence identifies src/migration/MigrationService483.cs as the narrow implementation boundary.

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

Identify existing test style and the nearest regression boundary.

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

correct sensitive-data exposure while preserving the public contract

Apply a localized change that follows existing abstractions.

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


Instruction: Refactor the upload in the developer portal to remove duplicated error mapping without changing behavior. The affected entry point is UploadPolicy48317; keep the change aligned with the existing CLI application 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

go test ./upload -run UploadRegression48317

Locate the implementation and callers associated with UploadPolicy48317.

Search evidence identifies internal/upload/upload_483_17.go as the narrow implementation boundary.

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

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


Instruction: Add regression coverage for the case where the download loads an unbounded result set in the developer portal. The affected entry point is DownloadPolicy48318; keep the change aligned with the existing CLI application boundary.

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

The download no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: DownloadPolicy48318|resource_bounding_defect

Locate the implementation and callers associated with DownloadPolicy48318.

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

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

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

correct resource-bounding defect while preserving the public contract

Diff inspection is required before making a completion claim.


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

A targeted verification path is identified

The final change remains inside the requested scope

Question: AuditPolicy48319|failure_classification_defect

correct failure-classification defect while preserving the public contract


Instruction: Refactor the pagination in the package index to remove duplicated retry decisions without changing behavior. The affected entry point is PaginationPolicy48400; keep the change aligned with the existing HTTP API boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The pagination no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/pagination/test_pagination_484_00.ts

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

Confirm the local module boundary before searching for implementation details.

Locate the implementation and callers associated with PaginationPolicy48400.

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

Obtain executable evidence for the requested behavior.

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


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

Question: CachePolicy48401|input_size_handling_defect

Question: authorize|permission|sanitize|validate


Instruction: Fix the defect where the queue does not preserve the public error contract in the package index. The affected entry point is QueuePolicy48402; keep the change aligned with the existing HTTP API 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

./gradlew test --tests QueueRegression48402

Locate the implementation and callers associated with QueuePolicy48402.

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

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


Instruction: Add regression coverage for the case where the webhook skips cleanup after cancellation in the package index. The affected entry point is WebhookPolicy48403; 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 webhook no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: WebhookPolicy48403|resource_cleanup_defect

Locate the implementation and callers associated with WebhookPolicy48403.

Search evidence identifies src/webhook/webhook_484_03.py as the narrow implementation boundary.

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

The first targeted test fails and provides a concrete counterexample.

Repeating the same patch would ignore the new test evidence.

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

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

Apply the second bounded patch addressing the diagnosed cause.

The repaired behavior must be re-executed before completion.

Confirm the revised patch satisfies the original acceptance criterion.


Instruction: Add regression coverage for the case where the permission rejects valid boundary values in the package index. The affected entry point is PermissionPolicy48404; keep the change aligned with the existing HTTP API 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_484_04.ts


Instruction: Add guarded support for cursor pagination in the configuration of the package index. The affected entry point is ConfigurationPolicy48405; keep the change aligned with the existing HTTP API boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The configuration no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/configuration/test_configuration_484_05.ts

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

Locate the implementation and callers associated with ConfigurationPolicy48405.

Search evidence identifies src/configuration/configuration_484_05.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.

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.

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

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

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


Instruction: Fix the defect where the parser fails when an optional field is absent in the package index. The affected entry point is ParserPolicy48406; keep the change aligned with the existing HTTP API boundary.

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

The parser no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests ParserRegression48406

Locate the implementation and callers associated with ParserPolicy48406.

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

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

Check static constraints relevant to the modified code.

Diff inspection is required before making a completion claim.


Instruction: Refactor the serializer in the package index to remove duplicated serialization logic without changing behavior. The affected entry point is SerializerPolicy48407; keep the change aligned with the existing HTTP API boundary.

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

The serializer no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope


Instruction: Fix the defect where the validator creates duplicate jobs under concurrent delivery in the package index. The affected entry point is ValidatorPolicy48408; 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 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_484_08.ts

correct idempotency defect while preserving the public contract


Instruction: Fix the defect where the retry loads an unbounded result set in the package index. The affected entry point is RetryPolicy48409; keep the change aligned with the existing HTTP API boundary.

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

The retry no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/retry/test_retry_484_09.ts

Question: RetryPolicy48409|resource_bounding_defect

Locate the implementation and callers associated with RetryPolicy48409.

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

Obtain executable evidence for the requested behavior.


Instruction: Add regression coverage for the case where the timeout misclassifies transient failures as permanent in the package index. The affected entry point is TimeoutPolicy48410; keep the change aligned with the existing HTTP API boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The timeout no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests TimeoutRegression48410

Question: TimeoutPolicy48410|failure_classification_defect

Locate the implementation and callers associated with TimeoutPolicy48410.

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

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


Instruction: Fix the defect where the search accepts malformed input after normalization in the package index. The affected entry point is SearchPolicy48411; keep the change aligned with the existing HTTP API boundary.

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

The search no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: SearchPolicy48411|validation_order_defect

Locate the implementation and callers associated with SearchPolicy48411.

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

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

correct validation-order defect while preserving the public contract


Instruction: Refactor the index in the package index to remove duplicated state transitions without changing behavior. The affected entry point is IndexPolicy48412; keep the change aligned with the existing HTTP API 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

ctest -R IndexRegression48412 --output-on-failure

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

Confirm the local module boundary before searching for implementation details.

Locate the implementation and callers associated with IndexPolicy48412.

Search evidence identifies src/index/index_484_12.cpp as the narrow implementation boundary.

correct retry-safety defect while preserving the public contract


Instruction: Fix the defect where the migration mutates shared state across requests in the package index. The affected entry point is MigrationPolicy48413; 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 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_484_13.ts

correct state-isolation defect while preserving the public contract

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


Instruction: Fix the defect where the upload matches identifiers case-insensitively in the package index. The affected entry point is UploadPolicy48414; keep the change aligned with the existing HTTP API boundary.

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

The upload no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: UploadPolicy48414|identity_comparison_defect

correct identity-comparison defect while preserving the public contract


Instruction: Fix the defect where the download marks partial work as successful in the package index. The affected entry point is DownloadPolicy48415; keep the change aligned with the existing HTTP API 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

repair diagnosed cause without broadening scope

Question: DownloadPolicy48415|false_success_defect

Locate the implementation and callers associated with DownloadPolicy48415.

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

correct false-success defect while preserving the public contract


Instruction: Add guarded support for bounded retries in the audit of the package index. The affected entry point is AuditPolicy48416; keep the change aligned with the existing HTTP API 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

correct least-privilege defect while preserving the public contract


Instruction: Fix the defect where the worker does not verify the persisted state in the package index. The affected entry point is WorkerPolicy48417; keep the change aligned with the existing HTTP API 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

ctest -R WorkerRegression48417 --output-on-failure

Locate the implementation and callers associated with WorkerPolicy48417.

Search evidence identifies src/worker/worker_484_17.cpp as the narrow implementation boundary.

correct verification defect while preserving the public contract

The first targeted test fails and provides a concrete counterexample.

Repeating the same patch would ignore the new test evidence.

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

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

revise the failed assumption without expanding scope

Apply the second bounded patch addressing the diagnosed cause.

The repaired behavior must be re-executed before completion.

Confirm the revised patch satisfies the original acceptance criterion.


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

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/scheduler/test_scheduler_484_18.ts

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

Locate the implementation and callers associated with SchedulerPolicy48418.

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

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

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

Check static constraints relevant to the modified code.


Instruction: Refactor the router in the package index to remove duplicated error mapping without changing behavior. The affected entry point is RouterPolicy48419; keep the change aligned with the existing HTTP API 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

ctest -R RouterRegression48419 --output-on-failure

Question: RouterPolicy48419|unit_conversion_defect

Locate the implementation and callers associated with RouterPolicy48419.

Search evidence identifies src/router/router_484_19.cpp 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 unit-conversion defect while preserving the public contract

Obtain executable evidence for the requested behavior.

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

Diff inspection is required before making a completion claim.

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


Instruction: Add guarded support for idempotency keys in the webhook of the job scheduler. The affected entry point is WebhookPolicy48500; keep the change aligned with the existing background processor 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

./gradlew test --tests WebhookRegression48500

Question: WebhookPolicy48500|resource_bounding_defect


Instruction: Add regression coverage for the case where the permission misclassifies transient failures as permanent in the job scheduler. The affected entry point is PermissionPolicy48501; keep the change aligned with the existing background processor boundary.

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

The permission no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/permission/test_permission_485_01.ts

Locate the implementation and callers associated with PermissionPolicy48501.

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

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

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

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


Instruction: Add guarded support for explicit timeouts in the configuration of the job scheduler. The affected entry point is ConfigurationPolicy48502; 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 configuration no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/configuration/test_configuration_485_02.ts

Locate the implementation and callers associated with ConfigurationPolicy48502.

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


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

dotnet test --filter ParserRegression48503

Locate the implementation and callers associated with ParserPolicy48503.

Search evidence identifies src/parser/ParserService485.cs as the narrow implementation boundary.


Instruction: Add guarded support for input size limits in the serializer of the job scheduler. The affected entry point is SerializerPolicy48504; keep the change aligned with the existing background processor 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

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

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


Instruction: Add guarded support for graceful shutdown in the validator of the job scheduler. The affected entry point is ValidatorPolicy48505; keep the change aligned with the existing background processor 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


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

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

The retry no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests RetryRegression48506

Locate the implementation and callers associated with RetryPolicy48506.

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


Instruction: Add regression coverage for the case where the timeout uses a broad filesystem permission in the job scheduler. The affected entry point is TimeoutPolicy48507; 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 timeout no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: TimeoutPolicy48507|least_privilege_defect


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

npm test -- test/search/test_search_485_08.ts

Locate the implementation and callers associated with SearchPolicy48508.

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