Instruction: Fix the defect where the logging logs a secret-bearing request field in the notification router. The affected entry point is LoggingPolicy45508; keep the change aligned with the existing plugin-based service boundary.

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

The logging no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

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

Question: LoggingPolicy45508|sensitive_data_exposure

Locate the implementation and callers associated with LoggingPolicy45508.

Search evidence identifies src/logging/logging_455_08.py 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.

Identify existing test style and the nearest regression boundary.

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

Obtain executable evidence for the requested behavior.


Instruction: Fix the defect where the sandbox creates duplicate jobs under concurrent delivery in the notification router. The affected entry point is SandboxPolicy45509; keep the change aligned with the existing plugin-based service boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The sandbox no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/sandbox/test_sandbox_455_09.ts

Use a bounded, updateable plan proportional to task complexity.

Locate the implementation and callers associated with SandboxPolicy45509.

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

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

confirm behavior
apply bounded patch
run targeted test
inspect diff

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

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

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

correct idempotency defect while preserving the public contract

Apply a localized change that follows existing abstractions.

Diff inspection is required before making a completion claim.

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

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


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

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

The session no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/session/test_session_455_10.ts

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

Question: SessionPolicy45510|resource_bounding_defect

Locate the implementation and callers associated with SessionPolicy45510.

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

correct resource-bounding defect while preserving the public contract

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

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


Instruction: Fix the defect where the token misclassifies transient failures as permanent in the notification router. The affected entry point is TokenPolicy45511; keep the change aligned with the existing plugin-based service boundary.

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

The token no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

go test ./token -run TokenRegression45511

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

Question: TokenPolicy45511|failure_classification_defect

Locate the implementation and callers associated with TokenPolicy45511.

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

correct failure-classification 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: Fix the defect where the pagination accepts malformed input after normalization in the notification router. The affected entry point is PaginationPolicy45512; keep the change aligned with the existing plugin-based service boundary.

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

The pagination no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/pagination/test_pagination_455_12.ts

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

Repository evidence contradicts the initial assumption about the data representation.

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

repair diagnosed cause without broadening scope

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

Confirm the local module boundary before searching for implementation details.

Locate the implementation and callers associated with PaginationPolicy45512.

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

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

correct validation-order defect while preserving the public contract

The original acceptance criterion passes

The failure signal is no longer reproduced

The final report distinguishes executed evidence from assumptions


Instruction: Refactor the cache in the notification router to remove duplicated serialization logic without changing behavior. The affected entry point is CachePolicy45513; keep the change aligned with the existing plugin-based service boundary.

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

The cache no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

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

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

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

Locate the implementation and callers associated with CachePolicy45513.

Search evidence identifies src/cache/cache_455_13.rs as the narrow implementation boundary.

correct retry-safety defect while preserving the public contract

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

Check static constraints relevant to the modified code.


Instruction: Harden the queue in the notification router against command injection while preserving valid behavior. The affected entry point is QueuePolicy45514; keep the change aligned with the existing plugin-based service boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The queue no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Ground every decision in repository evidence before editing.

Locate the implementation and callers associated with QueuePolicy45514.

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

Identify existing test style and the nearest regression boundary.

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

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

Question: authorize|permission|sanitize|validate

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

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

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


Instruction: Add guarded support for audit metadata in the webhook of the notification router. The affected entry point is WebhookPolicy45515; keep the change aligned with the existing plugin-based service boundary.

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

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

Verify the claimed behavior with targeted checks before completion.

Question: WebhookPolicy45515|identity_comparison_defect

correct identity-comparison defect while preserving the public contract


Instruction: Add guarded support for input size limits in the permission of the notification router. The affected entry point is PermissionPolicy45516; keep the change aligned with the existing plugin-based 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

Verify the claimed behavior with targeted checks before completion.

Locate the implementation and callers associated with PermissionPolicy45516.

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

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

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

correct false-success defect while preserving the public contract

Diff inspection is required before making a completion claim.


Instruction: Refactor the configuration in the notification router to remove duplicated cleanup logic without changing behavior. The affected entry point is ConfigurationPolicy45517; keep the change aligned with the existing plugin-based service boundary.

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

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

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

Hard tasks require caller evidence to control compatibility risk.

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

correct least-privilege defect while preserving the public contract


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

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

The parser 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 ParserPolicy45518.

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

correct verification defect while preserving the public contract


Instruction: Fix the defect where the serializer returns stale state after an update in the notification router. The affected entry point is SerializerPolicy45519; keep the change aligned with the existing plugin-based 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

Locate the implementation and callers associated with SerializerPolicy45519.

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

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

correct cache-invalidation defect while preserving the public contract


Instruction: Fix the defect where the audit creates duplicate jobs under concurrent delivery in the feature flag service. The affected entry point is AuditPolicy45600; keep the change aligned with the existing layered service 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

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

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

Search evidence identifies src/audit/audit_456_00.php 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: Add regression coverage for the case where the worker loads an unbounded result set in the feature flag service. The affected entry point is WorkerPolicy45601; 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 worker no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Respect scope and request approval only for materially risky actions.

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

Question: WorkerPolicy45601|resource_bounding_defect

Locate the implementation and callers associated with WorkerPolicy45601.

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

Unnecessary approval requests would reduce agent usefulness without improving safety.

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


Instruction: Fix the defect where the scheduler misclassifies transient failures as permanent in the feature flag service. The affected entry point is SchedulerPolicy45602; keep the change aligned with the existing layered service 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

go test ./scheduler -run SchedulerRegression45602

Locate the implementation and callers associated with SchedulerPolicy45602.

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

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

Identify existing test style and the nearest regression boundary.

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.

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


Instruction: Add regression coverage for the case where the router accepts malformed input after normalization in the feature flag service. The affected entry point is RouterPolicy45603; keep the change aligned with the existing layered service boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The router no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests RouterRegression45603

Question: RouterPolicy45603|validation_order_defect

Locate the implementation and callers associated with RouterPolicy45603.

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

Diff inspection is required before making a completion claim.


Instruction: Add regression coverage for the case where the metrics retries a non-idempotent operation in the feature flag service. The affected entry point is MetricsPolicy45604; keep the change aligned with the existing layered service boundary.

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

The metrics no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/metrics/test_metrics_456_04.ts

Locate the implementation and callers associated with MetricsPolicy45604.

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


Instruction: Add guarded support for dry-run mode in the logging of the feature flag service. The affected entry point is LoggingPolicy45605; keep the change aligned with the existing layered service 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_456_05.ts

Question: LoggingPolicy45605|state_isolation_defect

Locate the implementation and callers associated with LoggingPolicy45605.

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


Instruction: Fix the defect where the sandbox matches identifiers case-insensitively in the feature flag service. The affected entry point is SandboxPolicy45606; 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 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_456_06.ts

Question: SandboxPolicy45606|identity_comparison_defect

Locate the implementation and callers associated with SandboxPolicy45606.

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

The first targeted test fails and provides a concrete counterexample.

Repeating the same patch would ignore the new test evidence.

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

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

Apply the second bounded patch addressing the diagnosed cause.

The repaired behavior must be re-executed before completion.

Confirm the revised patch satisfies the original acceptance criterion.


Instruction: Fix the defect where the session marks partial work as successful in the feature flag service. The affected entry point is SessionPolicy45607; keep the change aligned with the existing layered service 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

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

Locate the implementation and callers associated with SessionPolicy45607.

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

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


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

Locate the implementation and callers associated with TokenPolicy45608.

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


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

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

Locate the implementation and callers associated with PaginationPolicy45609.

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

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: Review the proposed cache change in the feature flag service for correctness, scope, and regressions. The affected entry point is CachePolicy45610; keep the change aligned with the existing layered service boundary.

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

The cache no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/cache/test_cache_456_10.ts

Question: CachePolicy45610|cache_invalidation_defect

Locate the implementation and callers associated with CachePolicy45610.

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

Hard tasks require caller evidence to control compatibility risk.

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

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.

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


Instruction: Refactor the queue in the feature flag service to remove duplicated configuration parsing without changing behavior. The affected entry point is QueuePolicy45611; 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 queue no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

go test ./queue -run QueueRegression45611

Locate the implementation and callers associated with QueuePolicy45611.

Search evidence identifies internal/queue/queue_456_11.go as the narrow implementation boundary.

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

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

correct unit-conversion defect while preserving the public contract

The first targeted test fails and provides a concrete counterexample.

Repeating the same patch would ignore the new test evidence.

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

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

Apply the second bounded patch addressing the diagnosed cause.

The repaired behavior must be re-executed before completion.

Confirm the revised patch satisfies the original acceptance criterion.


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

./gradlew test --tests WebhookRegression45612

Question: WebhookPolicy45612|authorization_order_defect

Locate the implementation and callers associated with WebhookPolicy45612.

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

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

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.

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: Add regression coverage for the case where the permission silently truncates an oversized payload in the feature flag service. The affected entry point is PermissionPolicy45613; keep the change aligned with the existing layered service 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

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

Locate the implementation and callers associated with PermissionPolicy45613.

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

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

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

Identify existing test style and the nearest regression boundary.

correct input-size handling defect while preserving the public contract

Obtain executable evidence for the requested behavior.


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

correct compatibility defect while preserving the public contract

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


Instruction: Fix the defect where the parser skips cleanup after cancellation in the feature flag service. The affected entry point is ParserPolicy45615; keep the change aligned with the existing layered service 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_456_15.ts

Question: ParserPolicy45615|resource_cleanup_defect

Locate the implementation and callers associated with ParserPolicy45615.

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

correct resource-cleanup defect while preserving the public contract

Apply a localized change that follows existing abstractions.

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

Check static constraints relevant to the modified code.

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

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

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


Instruction: Refactor the serializer in the feature flag service to remove duplicated serialization logic without changing behavior. The affected entry point is SerializerPolicy45616; 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 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 SerializerPolicy45616.

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

correct boundary-condition defect while preserving the public contract

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

Diff inspection is required before making a completion claim.


Instruction: Harden the validator in the feature flag service against authorization bypass while preserving valid behavior. The affected entry point is ValidatorPolicy45617; keep the change aligned with the existing layered service boundary.

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

The validator no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

dotnet test --filter ValidatorRegression45617

Locate the implementation and callers associated with ValidatorPolicy45617.

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

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

Hard tasks require caller evidence to control compatibility risk.

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

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

correct error-propagation defect while preserving the public contract


Instruction: Add guarded support for explicit timeouts in the retry of the feature flag service. The affected entry point is RetryPolicy45618; keep the change aligned with the existing layered service 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

ctest -R RetryRegression45618 --output-on-failure

Locate the implementation and callers associated with RetryPolicy45618.

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

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

correct nullability defect while preserving the public contract


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

./gradlew test --tests TimeoutRegression45619

Question: TimeoutPolicy45619|sensitive_data_exposure

Locate the implementation and callers associated with TimeoutPolicy45619.

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

correct sensitive-data exposure while preserving the public contract


Instruction: Fix the defect where the router does not verify the persisted state in the audit log processor. The affected entry point is RouterPolicy45700; 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 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_457_00.ts

Locate the implementation and callers associated with RouterPolicy45700.

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

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


Instruction: Refactor the metrics in the audit log processor to remove duplicated cleanup logic without changing behavior. The affected entry point is MetricsPolicy45701; keep the change aligned with the existing modular monolith 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

The diff includes a configuration change outside the requested boundary.

repair diagnosed cause without broadening scope

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

Question: MetricsPolicy45701|cache_invalidation_defect

Locate the implementation and callers associated with MetricsPolicy45701.

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

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

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


Instruction: Fix the defect where the logging uses seconds where milliseconds are expected in the audit log processor. The affected entry point is LoggingPolicy45702; keep the change aligned with the existing modular monolith 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: LoggingPolicy45702|unit_conversion_defect

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


Instruction: Correct the configuration and operator guidance for safe fallback behavior in the audit log processor. The affected entry point is SandboxPolicy45703; keep the change aligned with the existing modular monolith boundary.

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

The sandbox no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: SandboxPolicy45703|authorization_order_defect

Locate the implementation and callers associated with SandboxPolicy45703.

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

Identify existing test style and the nearest regression boundary.

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


Instruction: Review the proposed session change in the audit log processor for correctness, scope, and regressions. The affected entry point is SessionPolicy45704; keep the change aligned with the existing modular monolith boundary.

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

The session no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/session/test_session_457_04.ts

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

Question: SessionPolicy45704|input_size_handling_defect

Locate the implementation and callers associated with SessionPolicy45704.

Search evidence identifies src/session/session_457_04.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.

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.

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


Instruction: Fix the defect where the token does not preserve the public error contract in the audit log processor. The affected entry point is TokenPolicy45705; 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 token no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

go test ./token -run TokenRegression45705

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


Instruction: Harden the pagination in the audit log processor against secret leakage while preserving valid behavior. The affected entry point is PaginationPolicy45706; keep the change aligned with the existing modular monolith 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 PaginationPolicy45706.

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

Check static constraints relevant to the modified code.


Instruction: Add guarded support for structured errors in the cache of the audit log processor. The affected entry point is CachePolicy45707; keep the change aligned with the existing modular monolith 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

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

Question: CachePolicy45707|boundary_condition_defect


Instruction: Fix the defect where the queue drops the original error context in the audit log processor. The affected entry point is QueuePolicy45708; keep the change aligned with the existing modular monolith 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

Confirm the local module boundary before searching for implementation details.

Question: QueuePolicy45708|error_propagation_defect

Locate the implementation and callers associated with QueuePolicy45708.

Search evidence identifies src/queue/queue_457_08.py 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.

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 webhook fails when an optional field is absent in the audit log processor. The affected entry point is WebhookPolicy45709; keep the change aligned with the existing modular monolith 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


Instruction: Add regression coverage for the case where the permission logs a secret-bearing request field in the audit log processor. The affected entry point is PermissionPolicy45710; 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 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_457_10.ts


Instruction: Add guarded support for audit metadata in the configuration of the audit log processor. The affected entry point is ConfigurationPolicy45711; keep the change aligned with the existing modular monolith 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

dotnet test --filter ConfigurationRegression45711

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

Locate the implementation and callers associated with ConfigurationPolicy45711.

Search evidence identifies src/configuration/ConfigurationService457.cs as the narrow implementation boundary.

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

correct idempotency defect while preserving the public contract


Instruction: Fix the defect where the parser loads an unbounded result set in the audit log processor. The affected entry point is ParserPolicy45712; keep the change aligned with the existing modular monolith 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: ParserPolicy45712|resource_bounding_defect

Locate the implementation and callers associated with ParserPolicy45712.

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

Identify existing test style and the nearest regression boundary.

correct resource-bounding defect while preserving the public contract


Instruction: Add guarded support for graceful shutdown in the serializer of the audit log processor. The affected entry point is SerializerPolicy45713; keep the change aligned with the existing modular monolith 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 SerializerPolicy45713.

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

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

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

correct failure-classification defect while preserving the public contract

Obtain executable evidence for the requested behavior.


Instruction: Correct the configuration and operator guidance for per-tenant configuration in the audit log processor. The affected entry point is ValidatorPolicy45714; keep the change aligned with the existing modular monolith 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 ValidatorRegression45714

Locate the implementation and callers associated with ValidatorPolicy45714.

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

Hard tasks require caller evidence to control compatibility risk.

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

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

Produce only evidence-backed findings with severity and confidence.

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


Instruction: Harden the retry in the audit log processor against unsafe deserialization while preserving valid behavior. The affected entry point is RetryPolicy45715; 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 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_457_15.ts

Locate the implementation and callers associated with RetryPolicy45715.

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

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.

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

Check static constraints relevant to the modified code.

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

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

Diff inspection is required before making a completion claim.


Instruction: Fix the defect where the timeout mutates shared state across requests in the audit log processor. The affected entry point is TimeoutPolicy45716; keep the change aligned with the existing modular monolith 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

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

Confirm the local module boundary before searching for implementation details.

Question: TimeoutPolicy45716|state_isolation_defect

Locate the implementation and callers associated with TimeoutPolicy45716.

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

correct state-isolation defect while preserving the public contract


Instruction: Fix the defect where the search matches identifiers case-insensitively in the audit log processor. The affected entry point is SearchPolicy45717; keep the change aligned with the existing modular monolith boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The search no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

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

Question: SearchPolicy45717|identity_comparison_defect

Locate the implementation and callers associated with SearchPolicy45717.

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

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

correct identity-comparison defect while preserving the public contract

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


Instruction: Fix the defect where the index marks partial work as successful in the audit log processor. The affected entry point is IndexPolicy45718; keep the change aligned with the existing modular monolith 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

Locate the implementation and callers associated with IndexPolicy45718.

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

Identify existing test style and the nearest regression boundary.

correct false-success defect while preserving the public contract

The first targeted test fails and provides a concrete counterexample.

Repeating the same patch would ignore the new test evidence.

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

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

Apply the second bounded patch addressing the diagnosed cause.

The repaired behavior must be re-executed before completion.

Confirm the revised patch satisfies the original acceptance criterion.


Instruction: Fix the defect where the migration uses a broad filesystem permission in the audit log processor. The affected entry point is MigrationPolicy45719; keep the change aligned with the existing modular monolith 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

Locate the implementation and callers associated with MigrationPolicy45719.

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

Hard tasks require caller evidence to control compatibility risk.

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

correct least-privilege defect while preserving the public contract

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


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

A targeted verification path is identified

The final change remains inside the requested scope

Locate the implementation and callers associated with SandboxPolicy45800.

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

Apply a localized change that follows existing abstractions.

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

Obtain executable evidence for the requested behavior.

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

Check static constraints relevant to the modified code.

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

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

Diff inspection is required before making a completion claim.


Instruction: Add guarded support for dry-run mode in the session of the developer portal. The affected entry point is SessionPolicy45801; keep the change aligned with the existing event-driven worker 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

go test ./session -run SessionRegression45801

Question: SessionPolicy45801|sensitive_data_exposure

Locate the implementation and callers associated with SessionPolicy45801.

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


Instruction: Add regression coverage for the case where the token creates duplicate jobs under concurrent delivery in the developer portal. The affected entry point is TokenPolicy45802; 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 token no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/token/test_token_458_02.ts

Locate the implementation and callers associated with TokenPolicy45802.

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

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.


Instruction: Fix the defect where the pagination loads an unbounded result set in the developer portal. The affected entry point is PaginationPolicy45803; keep the change aligned with the existing event-driven worker 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

npm test -- test/pagination/test_pagination_458_03.ts

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

Locate the implementation and callers associated with PaginationPolicy45803.

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


Instruction: Add guarded support for input size limits in the cache of the developer portal. The affected entry point is CachePolicy45804; 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 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_458_04.ts

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

Confirm the local module boundary before searching for implementation details.

Question: CachePolicy45804|failure_classification_defect

Locate the implementation and callers associated with CachePolicy45804.

Search evidence identifies src/cache/cache_458_04.ts 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 graceful shutdown in the queue of the developer portal. The affected entry point is QueuePolicy45805; 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 queue no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests QueueRegression45805

Question: QueuePolicy45805|validation_order_defect

correct validation-order defect while preserving the public contract


Instruction: Add guarded support for per-tenant configuration in the webhook of the developer portal. The affected entry point is WebhookPolicy45806; keep the change aligned with the existing event-driven worker 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_458_06.ts

Locate the implementation and callers associated with WebhookPolicy45806.

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

Hard tasks require caller evidence to control compatibility risk.

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

Apply a localized change that follows existing abstractions.

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


Instruction: Refactor the permission in the developer portal to remove duplicated cleanup logic without changing behavior. The affected entry point is PermissionPolicy45807; 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 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_458_07.ts

rewrite subsystem
replace dependencies
change API

Use a bounded, updateable plan proportional to task complexity.


Instruction: Fix the defect where the configuration matches identifiers case-insensitively in the developer portal. The affected entry point is ConfigurationPolicy45808; keep the change aligned with the existing event-driven worker 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

Locate the implementation and callers associated with ConfigurationPolicy45808.

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

Diff inspection is required before making a completion claim.

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


Instruction: Fix the defect where the parser marks partial work as successful in the developer portal. The affected entry point is ParserPolicy45809; 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 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_458_09.ts

Locate the implementation and callers associated with ParserPolicy45809.

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

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.


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

A targeted verification path is identified

The final change remains inside the requested scope

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

Locate the implementation and callers associated with SerializerPolicy45810.

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

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

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


Instruction: Add regression coverage for the case where the validator does not verify the persisted state in the developer portal. The affected entry point is ValidatorPolicy45811; keep the change aligned with the existing event-driven worker boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The validator no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/validator/test_validator_458_11.ts

Locate the implementation and callers associated with ValidatorPolicy45811.

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

correct verification defect while preserving the public contract


Instruction: Fix the defect where the retry returns stale state after an update in the developer portal. The affected entry point is RetryPolicy45812; 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 retry 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.

Question: RetryPolicy45812|cache_invalidation_defect

Locate the implementation and callers associated with RetryPolicy45812.

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

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

Produce only evidence-backed findings with severity and confidence.

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


Instruction: Fix the defect where the timeout uses seconds where milliseconds are expected in the developer portal. The affected entry point is TimeoutPolicy45813; keep the change aligned with the existing event-driven worker 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

Question: TimeoutPolicy45813|unit_conversion_defect

Locate the implementation and callers associated with TimeoutPolicy45813.

Search evidence identifies src/timeout/timeout_458_13.rs as the narrow implementation boundary.

correct unit-conversion defect while preserving the public contract


Instruction: Harden the search in the developer portal against command injection while preserving valid behavior. The affected entry point is SearchPolicy45814; 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 search no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: SearchPolicy45814|authorization_order_defect

Locate the implementation and callers associated with SearchPolicy45814.

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

Apply a localized change that follows existing abstractions.

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

Obtain executable evidence for the requested behavior.


Instruction: Fix the defect where the index silently truncates an oversized payload in the developer portal. The affected entry point is IndexPolicy45815; 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 index no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

go test ./index -run IndexRegression45815

Question: IndexPolicy45815|input_size_handling_defect

Locate the implementation and callers associated with IndexPolicy45815.

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

correct input-size handling defect while preserving the public contract

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

Check static constraints relevant to the modified code.

Diff inspection is required before making a completion claim.


Instruction: Add guarded support for input size limits in the migration of the developer portal. The affected entry point is MigrationPolicy45816; keep the change aligned with the existing event-driven worker boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The migration no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Locate the implementation and callers associated with MigrationPolicy45816.

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

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

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

Identify existing test style and the nearest regression boundary.

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

correct compatibility defect while preserving the public contract

The first targeted test fails and provides a concrete counterexample.

Repeating the same patch would ignore the new test evidence.

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

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

Apply the second bounded patch addressing the diagnosed cause.

The repaired behavior must be re-executed before completion.

Confirm the revised patch satisfies the original acceptance criterion.


Instruction: Fix the defect where the upload skips cleanup after cancellation in the developer portal. The affected entry point is UploadPolicy45817; 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 upload no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/upload/test_upload_458_17.ts

repair diagnosed cause without broadening scope

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

Question: UploadPolicy45817|resource_cleanup_defect

Locate the implementation and callers associated with UploadPolicy45817.

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

correct resource-cleanup defect while preserving the public contract


Instruction: Fix the defect where the download rejects valid boundary values in the developer portal. The affected entry point is DownloadPolicy45818; keep the change aligned with the existing event-driven worker boundary.

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

The download no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests DownloadRegression45818

Question: DownloadPolicy45818|boundary_condition_defect

Locate the implementation and callers associated with DownloadPolicy45818.

Search evidence identifies src/main/java/download/DownloadService458.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 boundary-condition defect while preserving the public contract

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


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

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests AuditRegression45819

Question: AuditPolicy45819|error_propagation_defect

Locate the implementation and callers associated with AuditPolicy45819.

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

correct error-propagation defect while preserving the public contract


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

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

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

Apply a localized change that follows existing abstractions.

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

Obtain executable evidence for the requested behavior.

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

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

Diff inspection is required before making a completion claim.


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

Locate the implementation and callers associated with CachePolicy45901.

Search evidence identifies src/cache/cache_459_01.rs as the narrow implementation boundary.

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

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

Identify existing test style and the nearest regression boundary.

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


Instruction: Add guarded support for request cancellation in the queue of the package index. The affected entry point is QueuePolicy45902; keep the change aligned with the existing CLI application 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 QueueRegression45902


Instruction: Fix the defect where the webhook returns stale state after an update in the package index. The affected entry point is WebhookPolicy45903; 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 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_459_03.ts

Question: WebhookPolicy45903|cache_invalidation_defect

Locate the implementation and callers associated with WebhookPolicy45903.

Search evidence identifies src/webhook/webhook_459_03.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 regression coverage for the case where the permission uses seconds where milliseconds are expected in the package index. The affected entry point is PermissionPolicy45904; keep the change aligned with the existing CLI application boundary.

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

The permission no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

go test ./permission -run PermissionRegression45904

Locate the implementation and callers associated with PermissionPolicy45904.

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


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

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

Locate the implementation and callers associated with ConfigurationPolicy45905.

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

correct authorization-order defect while preserving the public contract

The first targeted test fails and provides a concrete counterexample.

Repeating the same patch would ignore the new test evidence.

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

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

revise the failed assumption without expanding scope

Apply the second bounded patch addressing the diagnosed cause.

The repaired behavior must be re-executed before completion.

Confirm the revised patch satisfies the original acceptance criterion.

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


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

Question: ParserPolicy45906|input_size_handling_defect

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


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

Locate the implementation and callers associated with SerializerPolicy45907.

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

Apply a localized change that follows existing abstractions.

Obtain executable evidence for the requested behavior.


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

A targeted verification path is identified

The final change remains inside the requested scope

Ground every decision in repository evidence before editing.


Instruction: Add regression coverage for the case where the retry rejects valid boundary values in the package index. The affected entry point is RetryPolicy45909; keep the change aligned with the existing CLI application boundary.

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

The retry no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: RetryPolicy45909|boundary_condition_defect

Locate the implementation and callers associated with RetryPolicy45909.

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

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

Diff inspection is required before making a completion claim.


Instruction: Refactor the timeout in the package index to remove duplicated cleanup logic without changing behavior. The affected entry point is TimeoutPolicy45910; keep the change aligned with the existing CLI application boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The timeout no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/timeout/test_timeout_459_10.ts

Question: TimeoutPolicy45910|error_propagation_defect

Locate the implementation and callers associated with TimeoutPolicy45910.

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

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

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

Identify existing test style and the nearest regression boundary.

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

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

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


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

Locate the implementation and callers associated with SearchPolicy45911.

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

correct nullability defect while preserving the public contract


Instruction: Add regression coverage for the case where the index logs a secret-bearing request field in the package index. The affected entry point is IndexPolicy45912; keep the change aligned with the existing CLI application 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

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: IndexPolicy45912|sensitive_data_exposure

Locate the implementation and callers associated with IndexPolicy45912.

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

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

Produce only evidence-backed findings with severity and confidence.


Instruction: Add guarded support for cursor pagination in the migration of the package index. The affected entry point is MigrationPolicy45913; 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 migration no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

go test ./migration -run MigrationRegression45913

Locate the implementation and callers associated with MigrationPolicy45913.

Search evidence identifies internal/migration/migration_459_13.go as the narrow implementation boundary.

correct idempotency defect while preserving the public contract


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

./gradlew test --tests UploadRegression45914

Question: UploadPolicy45914|resource_bounding_defect

Locate the implementation and callers associated with UploadPolicy45914.

Search evidence identifies src/main/java/upload/UploadService459.java as the narrow implementation boundary.

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


Instruction: Review the proposed download change in the package index for correctness, scope, and regressions. The affected entry point is DownloadPolicy45915; keep the change aligned with the existing CLI application boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The download no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: DownloadPolicy45915|failure_classification_defect

Locate the implementation and callers associated with DownloadPolicy45915.

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

correct failure-classification 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: Add guarded support for idempotency keys in the audit of the package index. The affected entry point is AuditPolicy45916; keep the change aligned with the existing CLI application boundary.

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

The audit no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: AuditPolicy45916|validation_order_defect

Locate the implementation and callers associated with AuditPolicy45916.

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

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

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

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 dry-run mode in the worker of the package index. The affected entry point is WorkerPolicy45917; keep the change aligned with the existing CLI application 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

go test ./worker -run WorkerRegression45917

Locate the implementation and callers associated with WorkerPolicy45917.

Search evidence identifies internal/worker/worker_459_17.go as the narrow implementation boundary.

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

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

Identify existing test style and the nearest regression boundary.


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

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests SchedulerRegression45918

Locate the implementation and callers associated with SchedulerPolicy45918.

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

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

correct state-isolation defect while preserving the public contract


Instruction: Add guarded support for audit metadata in the router of the package index. The affected entry point is RouterPolicy45919; keep the change aligned with the existing CLI application 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

Question: RouterPolicy45919|identity_comparison_defect

Locate the implementation and callers associated with RouterPolicy45919.

Search evidence identifies src/router/router_459_19.py as the narrow implementation boundary.

Hard tasks require caller evidence to control compatibility risk.

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

correct identity-comparison 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 webhook rejects valid boundary values in the job scheduler. The affected entry point is WebhookPolicy46000; keep the change aligned with the existing HTTP API 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

npm test -- test/webhook/test_webhook_460_00.ts

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: WebhookPolicy46000|boundary_condition_defect

Locate the implementation and callers associated with WebhookPolicy46000.

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

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

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

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


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

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

The permission no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests PermissionRegression46001

Locate the implementation and callers associated with PermissionPolicy46001.

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

The first targeted test fails and provides a concrete counterexample.

Repeating the same patch would ignore the new test evidence.

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

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

Apply the second bounded patch addressing the diagnosed cause.

The repaired behavior must be re-executed before completion.

Confirm the revised patch satisfies the original acceptance criterion.


Instruction: Fix the defect where the configuration fails when an optional field is absent in the job scheduler. The affected entry point is ConfigurationPolicy46002; 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 configuration no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

ctest -R ConfigurationRegression46002 --output-on-failure

Locate the implementation and callers associated with ConfigurationPolicy46002.

Search evidence identifies src/configuration/configuration_460_02.cpp 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 parser logs a secret-bearing request field in the job scheduler. The affected entry point is ParserPolicy46003; keep the change aligned with the existing HTTP API 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

./gradlew test --tests ParserRegression46003

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

Question: ParserPolicy46003|sensitive_data_exposure

Locate the implementation and callers associated with ParserPolicy46003.

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

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

correct sensitive-data exposure while preserving the public contract

Apply a localized change that follows existing abstractions.

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

Obtain executable evidence for the requested behavior.

Diff inspection is required before making a completion claim.

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


Instruction: Fix the defect where the serializer creates duplicate jobs under concurrent delivery in the job scheduler. The affected entry point is SerializerPolicy46004; keep the change aligned with the existing HTTP API 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_460_04.ts

Locate the implementation and callers associated with SerializerPolicy46004.

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

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

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 validator in the job scheduler against unsafe deserialization while preserving valid behavior. The affected entry point is ValidatorPolicy46005; keep the change aligned with the existing HTTP API 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

correct resource-bounding defect while preserving the public contract


Instruction: Fix the defect where the retry misclassifies transient failures as permanent in the job scheduler. The affected entry point is RetryPolicy46006; keep the change aligned with the existing HTTP API 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

npm test -- test/retry/test_retry_460_06.ts

Question: RetryPolicy46006|failure_classification_defect

Locate the implementation and callers associated with RetryPolicy46006.

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

Hard tasks require caller evidence to control compatibility risk.

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

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

Produce only evidence-backed findings with severity and confidence.

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


Instruction: Correct the configuration and operator guidance for structured errors in the job scheduler. The affected entry point is TimeoutPolicy46007; 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 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_460_07.ts

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

Question: TimeoutPolicy46007|validation_order_defect

Locate the implementation and callers associated with TimeoutPolicy46007.

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

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

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

correct validation-order defect while preserving the public contract