Instruction: Correct the configuration and operator guidance for idempotency keys in the job scheduler. The affected entry point is SearchPolicy46008; keep the change aligned with the existing HTTP API boundary.

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

The search no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

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

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

correct retry-safety defect while preserving the public contract


Instruction: Add guarded support for dry-run mode in the index of the job scheduler. The affected entry point is IndexPolicy46009; keep the change aligned with the existing HTTP API boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The index no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/index/test_index_460_09.ts

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

correctness security compatibility test_coverage


Instruction: Correct the configuration and operator guidance for explicit timeouts in the job scheduler. The affected entry point is MigrationPolicy46010; keep the change aligned with the existing HTTP API boundary.

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

The migration no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

ctest -R MigrationRegression46010 --output-on-failure

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

Search evidence identifies src/migration/migration_460_10.cpp as the narrow implementation boundary.

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

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

correct identity-comparison defect while preserving the public contract

Apply a localized change that follows existing abstractions.

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.

Obtain executable evidence for the requested behavior.

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

Check static constraints relevant to the modified code.

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

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

Diff inspection is required before making a completion claim.

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

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


Instruction: Correct the configuration and operator guidance for audit metadata in the job scheduler. The affected entry point is UploadPolicy46011; keep the change aligned with the existing HTTP API boundary.

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

The upload no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Locate the implementation and callers associated with UploadPolicy46011.

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

correct false-success defect while preserving the public contract


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

A targeted verification path is identified

The final change remains inside the requested scope

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

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

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

repair diagnosed cause without broadening scope

Question: DownloadPolicy46012|least_privilege_defect

Locate the implementation and callers associated with DownloadPolicy46012.

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

correct least-privilege 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: Correct the configuration and operator guidance for graceful shutdown in the job scheduler. The affected entry point is AuditPolicy46013; keep the change aligned with the existing HTTP API boundary.

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

The audit no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

go test ./audit -run AuditRegression46013

Locate the implementation and callers associated with AuditPolicy46013.

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

correct verification defect while preserving the public contract


Instruction: Add guarded support for per-tenant configuration in the worker of the job scheduler. The affected entry point is WorkerPolicy46014; keep the change aligned with the existing HTTP API boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The worker no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

dotnet test --filter WorkerRegression46014

Verify the claimed behavior with targeted checks before completion.

Question: WorkerPolicy46014|cache_invalidation_defect

Locate the implementation and callers associated with WorkerPolicy46014.

Search evidence identifies src/worker/WorkerService460.cs as the narrow implementation boundary.

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

Identify existing test style and the nearest regression boundary.

correct cache-invalidation defect while preserving the public contract


Instruction: Review the proposed scheduler change in the job scheduler for correctness, scope, and regressions. The affected entry point is SchedulerPolicy46015; keep the change aligned with the existing HTTP API boundary.

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

The scheduler no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Respect scope and request approval only for materially risky actions.

Locate the implementation and callers associated with SchedulerPolicy46015.

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

correct unit-conversion defect while preserving the public contract


Instruction: Harden the router in the job scheduler against replay attacks while preserving valid behavior. The affected entry point is RouterPolicy46016; keep the change aligned with the existing HTTP API boundary.

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

The router no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/router/test_router_460_16.ts

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

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

Confirm the local module boundary before searching for implementation details.

Question: RouterPolicy46016|authorization_order_defect

Locate the implementation and callers associated with RouterPolicy46016.

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

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

Question: authorize|permission|sanitize|validate

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

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


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

A targeted verification path is identified

The final change remains inside the requested scope

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

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

Question: MetricsPolicy46017|input_size_handling_defect

Locate the implementation and callers associated with MetricsPolicy46017.

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

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

Produce only evidence-backed findings with severity and confidence.

Diff inspection is required before making a completion claim.

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


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

npm test -- test/logging/test_logging_460_18.ts

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

Locate the implementation and callers associated with LoggingPolicy46018.

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

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

correct compatibility defect while preserving the public contract

Apply a localized change that follows existing abstractions.

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

Obtain executable evidence for the requested behavior.


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

dotnet test --filter SandboxRegression46019

Ground every decision in repository evidence before editing.

Question: SandboxPolicy46019|resource_cleanup_defect

Locate the implementation and callers associated with SandboxPolicy46019.

Search evidence identifies src/sandbox/SandboxService460.cs as the narrow implementation boundary.

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

Identify existing test style and the nearest regression boundary.

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

confirm behavior
apply bounded patch
run targeted test
inspect diff

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

correct resource-cleanup defect while preserving the public contract


Instruction: Add guarded support for idempotency keys in the parser of the observability collector. The affected entry point is ParserPolicy46100; keep the change aligned with the existing background processor 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_461_00.ts

Use a bounded, updateable plan proportional to task complexity.

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

Confirm the local module boundary before searching for implementation details.

Question: ParserPolicy46100|state_isolation_defect

Locate the implementation and callers associated with ParserPolicy46100.

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

correct state-isolation 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 serializer matches identifiers case-insensitively in the observability collector. The affected entry point is SerializerPolicy46101; keep the change aligned with the existing background processor boundary.

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

The serializer no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests SerializerRegression46101

Locate the implementation and callers associated with SerializerPolicy46101.

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


Instruction: Fix the defect where the validator marks partial work as successful in the observability collector. The affected entry point is ValidatorPolicy46102; keep the change aligned with the existing background processor boundary.

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

The validator no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/validator/test_validator_461_02.ts

Locate the implementation and callers associated with ValidatorPolicy46102.

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

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

Check static constraints relevant to the modified code.


Instruction: Add regression coverage for the case where the retry uses a broad filesystem permission in the observability collector. The affected entry point is RetryPolicy46103; keep the change aligned with the existing background processor 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

go test ./retry -run RetryRegression46103

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

Locate the implementation and callers associated with RetryPolicy46103.

Search evidence identifies internal/retry/retry_461_03.go as the narrow implementation boundary.

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


Instruction: Fix the defect where the timeout does not verify the persisted state in the observability collector. The affected entry point is TimeoutPolicy46104; keep the change aligned with the existing background processor boundary.

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

The timeout no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Locate the implementation and callers associated with TimeoutPolicy46104.

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

Diff inspection is required before making a completion claim.

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


Instruction: Refactor the search in the observability collector to remove duplicated configuration parsing without changing behavior. The affected entry point is SearchPolicy46105; keep the change aligned with the existing background processor boundary.

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

The search no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

The diff includes a configuration change outside the requested boundary.

Question: SearchPolicy46105|cache_invalidation_defect

Locate the implementation and callers associated with SearchPolicy46105.

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

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

Apply a localized change that follows existing abstractions.

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

Obtain executable evidence for the requested behavior.


Instruction: Refactor the index in the observability collector to remove duplicated configuration parsing without changing behavior. The affected entry point is IndexPolicy46106; keep the change aligned with the existing background processor boundary.

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

The index no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests IndexRegression46106

Verify the claimed behavior with targeted checks before completion.


Instruction: Add regression coverage for the case where the migration performs authorization after the side effect in the observability collector. The affected entry point is MigrationPolicy46107; keep the change aligned with the existing background processor boundary.

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

The migration no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Locate the implementation and callers associated with MigrationPolicy46107.

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

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

Identify existing test style and the nearest regression boundary.

Hard tasks require caller evidence to control compatibility risk.

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

The 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 upload change in the observability collector for correctness, scope, and regressions. The affected entry point is UploadPolicy46108; keep the change aligned with the existing background processor boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The upload no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/upload/test_upload_461_08.ts

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

Confirm the local module boundary before searching for implementation details.

Question: UploadPolicy46108|input_size_handling_defect

Locate the implementation and callers associated with UploadPolicy46108.

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

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

Question: authorize|permission|sanitize|validate

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

correct input-size handling defect while preserving the public contract

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

Check static constraints relevant to the modified code.


Instruction: Review the proposed download change in the observability collector for correctness, scope, and regressions. The affected entry point is DownloadPolicy46109; keep the change aligned with the existing background processor boundary.

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

The download no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/download/test_download_461_09.ts

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

Question: DownloadPolicy46109|compatibility_defect

Locate the implementation and callers associated with DownloadPolicy46109.

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

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

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


Instruction: Fix the defect where the audit skips cleanup after cancellation in the observability collector. The affected entry point is AuditPolicy46110; keep the change aligned with the existing background processor 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

npm test -- test/audit/test_audit_461_10.ts

Question: AuditPolicy46110|resource_cleanup_defect

Locate the implementation and callers associated with AuditPolicy46110.

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

Apply a localized change that follows existing abstractions.

Obtain executable evidence for the requested behavior.

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

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

Diff inspection is required before making a completion claim.


Instruction: Refactor the worker in the observability collector to remove duplicated serialization logic without changing behavior. The affected entry point is WorkerPolicy46111; keep the change aligned with the existing background processor boundary.

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

The worker no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: WorkerPolicy46111|boundary_condition_defect

correct boundary-condition defect while preserving the public contract

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


Instruction: Harden the scheduler in the observability collector against command injection while preserving valid behavior. The affected entry point is SchedulerPolicy46112; keep the change aligned with the existing background processor 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 SchedulerRegression46112

Locate the implementation and callers associated with SchedulerPolicy46112.

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

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

Identify existing test style and the nearest regression boundary.

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

correct error-propagation defect while preserving the public contract

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


Instruction: Add guarded support for dry-run mode in the router of the observability collector. The affected entry point is RouterPolicy46113; keep the change aligned with the existing background processor 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

correct nullability defect while preserving the public contract

Ground every decision in repository evidence before editing.


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

./gradlew test --tests MetricsRegression46114

Question: MetricsPolicy46114|sensitive_data_exposure

Locate the implementation and callers associated with MetricsPolicy46114.

Search evidence identifies src/main/java/metrics/MetricsService461.java as the narrow implementation boundary.

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

correct sensitive-data exposure while preserving the public contract

Question: authorize|permission|sanitize|validate

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


Instruction: Add regression coverage for the case where the logging creates duplicate jobs under concurrent delivery in the observability collector. The affected entry point is LoggingPolicy46115; keep the change aligned with the existing background processor 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

ctest -R LoggingRegression46115 --output-on-failure

Locate the implementation and callers associated with LoggingPolicy46115.

Search evidence identifies src/logging/logging_461_15.cpp as the narrow implementation boundary.

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

Produce only evidence-backed findings with severity and confidence.


Instruction: Fix the defect where the sandbox loads an unbounded result set in the observability collector. The affected entry point is SandboxPolicy46116; keep the change aligned with the existing background processor boundary.

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

The sandbox 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: SandboxPolicy46116|resource_bounding_defect

Locate the implementation and callers associated with SandboxPolicy46116.

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

correct resource-bounding defect while preserving the public contract

The first targeted test fails and provides a concrete counterexample.

Repeating the same patch would ignore the new test evidence.

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

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

Apply the second bounded patch addressing the diagnosed cause.

The repaired behavior must be re-executed before completion.

Confirm the revised patch satisfies the original acceptance criterion.

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


Instruction: Add guarded support for graceful shutdown in the session of the observability collector. The affected entry point is SessionPolicy46117; keep the change aligned with the existing background processor boundary.

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

The session no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

go test ./session -run SessionRegression46117

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

Question: SessionPolicy46117|failure_classification_defect

Locate the implementation and callers associated with SessionPolicy46117.

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

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

correct failure-classification defect while preserving the public contract

Apply a localized change that follows existing abstractions.

Hard tasks require caller evidence to control compatibility risk.

Obtain executable evidence for the requested behavior.

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

Check static constraints relevant to the modified code.

Diff inspection is required before making a completion claim.


Instruction: Fix the defect where the token accepts malformed input after normalization in the observability collector. The affected entry point is TokenPolicy46118; keep the change aligned with the existing background processor boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The token no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests TokenRegression46118

Question: TokenPolicy46118|validation_order_defect


Instruction: Refactor the pagination in the observability collector to remove duplicated cleanup logic without changing behavior. The affected entry point is PaginationPolicy46119; keep the change aligned with the existing background processor 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

correct retry-safety defect while preserving the public contract

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


Instruction: Correct the configuration and operator guidance for bounded retries in the configuration service. The affected entry point is RetryPolicy46200; keep the change aligned with the existing library package boundary.

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

The retry no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests RetryRegression46200


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

./gradlew test --tests TimeoutRegression46201

Question: TimeoutPolicy46201|resource_cleanup_defect

Locate the implementation and callers associated with TimeoutPolicy46201.

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

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

Identify existing test style and the nearest regression boundary.

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

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


Instruction: Add guarded support for request cancellation in the search of the configuration service. The affected entry point is SearchPolicy46202; keep the change aligned with the existing library package boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The search no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/search/test_search_462_02.ts

Question: SearchPolicy46202|boundary_condition_defect

Locate the implementation and callers associated with SearchPolicy46202.

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

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


Instruction: Add guarded support for structured errors in the index of the configuration service. The affected entry point is IndexPolicy46203; keep the change aligned with the existing library package 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

ctest -R IndexRegression46203 --output-on-failure

Question: IndexPolicy46203|error_propagation_defect

Locate the implementation and callers associated with IndexPolicy46203.

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


Instruction: Refactor the migration in the configuration service to remove duplicated error mapping without changing behavior. The affected entry point is MigrationPolicy46204; keep the change aligned with the existing library package boundary.

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

The migration no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/migration/test_migration_462_04.ts

rewrite subsystem
replace dependencies
change API

Use a bounded, updateable plan proportional to task complexity.


Instruction: Review the proposed upload change in the configuration service for correctness, scope, and regressions. The affected entry point is UploadPolicy46205; keep the change aligned with the existing library package boundary.

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

The upload no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

ctest -R UploadRegression46205 --output-on-failure

Question: UploadPolicy46205|sensitive_data_exposure

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


Instruction: Add guarded support for explicit timeouts in the download of the configuration service. The affected entry point is DownloadPolicy46206; keep the change aligned with the existing library package boundary.

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

The download no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

ctest -R DownloadRegression46206 --output-on-failure

Locate the implementation and callers associated with DownloadPolicy46206.

Search evidence identifies src/download/download_462_06.cpp as the narrow implementation boundary.

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

Produce only evidence-backed findings with severity and confidence.


Instruction: Fix the defect where the audit loads an unbounded result set in the configuration service. The affected entry point is AuditPolicy46207; keep the change aligned with the existing library package boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The audit no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: AuditPolicy46207|resource_bounding_defect

Locate the implementation and callers associated with AuditPolicy46207.

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


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

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

The worker no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

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

Confirm the local module boundary before searching for implementation details.

Question: WorkerPolicy46208|failure_classification_defect

Locate the implementation and callers associated with WorkerPolicy46208.

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

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


Instruction: Add guarded support for graceful shutdown in the scheduler of the configuration service. The affected entry point is SchedulerPolicy46209; keep the change aligned with the existing library package boundary.

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

The scheduler no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests SchedulerRegression46209

correct validation-order defect while preserving the public contract


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

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

The router no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope


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

go test ./metrics -run MetricsRegression46211

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

repair diagnosed cause without broadening scope

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

Question: MetricsPolicy46211|state_isolation_defect

Locate the implementation and callers associated with MetricsPolicy46211.

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

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

Apply a localized change that follows existing abstractions.

Obtain executable evidence for the requested behavior.


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

npm test -- test/logging/test_logging_462_12.ts

Question: LoggingPolicy46212|identity_comparison_defect

correct identity-comparison defect while preserving the public contract


Instruction: Refactor the sandbox in the configuration service to remove duplicated authorization checks without changing behavior. The affected entry point is SandboxPolicy46213; keep the change aligned with the existing library package 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

ctest -R SandboxRegression46213 --output-on-failure

Locate the implementation and callers associated with SandboxPolicy46213.

Search evidence identifies src/sandbox/sandbox_462_13.cpp as the narrow implementation boundary.

correct false-success defect while preserving the public contract


Instruction: Refactor the session in the configuration service to remove duplicated authorization checks without changing behavior. The affected entry point is SessionPolicy46214; keep the change aligned with the existing library package 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

./gradlew test --tests SessionRegression46214

Question: SessionPolicy46214|least_privilege_defect

Locate the implementation and callers associated with SessionPolicy46214.

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

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

correct least-privilege defect while preserving the public contract

Diff inspection is required before making a completion claim.


Instruction: Fix the defect where the token does not verify the persisted state in the configuration service. The affected entry point is TokenPolicy46215; keep the change aligned with the existing library package boundary.

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

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

Locate the implementation and callers associated with TokenPolicy46215.

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

Identify existing test style and the nearest regression boundary.

Hard tasks require caller evidence to control compatibility risk.

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


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

go test ./pagination -run PaginationRegression46216

Locate the implementation and callers associated with PaginationPolicy46216.

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

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

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

correct cache-invalidation defect while preserving the public contract

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


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


Instruction: Add regression coverage for the case where the queue performs authorization after the side effect in the configuration service. The affected entry point is QueuePolicy46218; keep the change aligned with the existing library package 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

./gradlew test --tests QueueRegression46218

Question: QueuePolicy46218|authorization_order_defect

Locate the implementation and callers associated with QueuePolicy46218.

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

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

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: Fix the defect where the webhook silently truncates an oversized payload in the configuration service. The affected entry point is WebhookPolicy46219; keep the change aligned with the existing library package 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

npm test -- test/webhook/test_webhook_462_19.ts

Question: WebhookPolicy46219|input_size_handling_defect

Locate the implementation and callers associated with WebhookPolicy46219.

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

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

correct input-size handling defect while preserving the public contract

Apply a localized change that follows existing abstractions.

Obtain executable evidence for the requested behavior.

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

Check static constraints relevant to the modified code.


Instruction: Add guarded support for input size limits in the index of the repository indexer. The affected entry point is IndexPolicy46300; 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 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: IndexPolicy46300|validation_order_defect

Locate the implementation and callers associated with IndexPolicy46300.

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

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

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

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

Diff inspection is required before making a completion claim.


Instruction: Add regression coverage for the case where the migration retries a non-idempotent operation in the repository indexer. The affected entry point is MigrationPolicy46301; keep the change aligned with the existing plugin-based service 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 MigrationPolicy46301.

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

Identify existing test style and the nearest regression boundary.

Hard tasks require caller evidence to control compatibility risk.

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

The first targeted test fails and provides a concrete counterexample.

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

Apply the second bounded patch addressing the diagnosed cause.

Confirm the revised patch satisfies the original acceptance criterion.

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


Instruction: Harden the upload in the repository indexer against unsafe deserialization while preserving valid behavior. The affected entry point is UploadPolicy46302; 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 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_463_02.ts

Question: UploadPolicy46302|state_isolation_defect

Locate the implementation and callers associated with UploadPolicy46302.

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

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

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.


Instruction: Harden the download in the repository indexer against unsafe deserialization while preserving valid behavior. The affected entry point is DownloadPolicy46303; keep the change aligned with the existing plugin-based service boundary.

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

The download no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: DownloadPolicy46303|identity_comparison_defect

Locate the implementation and callers associated with DownloadPolicy46303.

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

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


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

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests AuditRegression46304

Confirm the local module boundary before searching for implementation details.

Locate the implementation and callers associated with AuditPolicy46304.

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

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


Instruction: Add regression coverage for the case where the worker uses a broad filesystem permission in the repository indexer. The affected entry point is WorkerPolicy46305; 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 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 WorkerRegression46305

Question: WorkerPolicy46305|least_privilege_defect


Instruction: Harden the scheduler in the repository indexer against unsafe deserialization while preserving valid behavior. The affected entry point is SchedulerPolicy46306; keep the change aligned with the existing plugin-based service boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The scheduler no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Locate the implementation and callers associated with SchedulerPolicy46306.

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

correct verification defect while preserving the public contract


Instruction: Add guarded support for structured errors in the router of the repository indexer. The affected entry point is RouterPolicy46307; 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 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_463_07.ts

Question: RouterPolicy46307|cache_invalidation_defect


Instruction: Refactor the metrics in the repository indexer to remove duplicated error mapping without changing behavior. The affected entry point is MetricsPolicy46308; keep the change aligned with the existing plugin-based service boundary.

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

The metrics no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: MetricsPolicy46308|unit_conversion_defect

Locate the implementation and callers associated with MetricsPolicy46308.

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

Identify existing test style and the nearest regression boundary.

correct unit-conversion defect while preserving the public contract

Repeating the same patch would ignore the new test evidence.

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

The repaired behavior must be re-executed before completion.


Instruction: Fix the defect where the logging performs authorization after the side effect in the repository indexer. The affected entry point is LoggingPolicy46309; 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 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_463_09.ts

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

Question: LoggingPolicy46309|authorization_order_defect

Locate the implementation and callers associated with LoggingPolicy46309.

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

Diff inspection is required before making a completion claim.


Instruction: Add regression coverage for the case where the sandbox silently truncates an oversized payload in the repository indexer. The affected entry point is SandboxPolicy46310; 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 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_463_10.ts

Question: SandboxPolicy46310|input_size_handling_defect


Instruction: Fix the defect where the session does not preserve the public error contract in the repository indexer. The affected entry point is SessionPolicy46311; keep the change aligned with the existing plugin-based service boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The session no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Locate the implementation and callers associated with SessionPolicy46311.

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

correct compatibility defect while preserving the public contract

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

Check static constraints relevant to the modified code.

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


Instruction: Review the proposed token change in the repository indexer for correctness, scope, and regressions. The affected entry point is TokenPolicy46312; 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 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_463_12.ts

Question: TokenPolicy46312|resource_cleanup_defect

correct resource-cleanup defect while preserving the public contract


Instruction: Add guarded support for graceful shutdown in the pagination of the repository indexer. The affected entry point is PaginationPolicy46313; keep the change aligned with the existing plugin-based service 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_463_13.ts

Locate the implementation and callers associated with PaginationPolicy46313.

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

correct boundary-condition defect while preserving the public contract

The first targeted test fails and provides a concrete counterexample.

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

Apply the second bounded patch addressing the diagnosed cause.

Confirm the revised patch satisfies the original acceptance criterion.

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


Instruction: Fix the defect where the cache drops the original error context in the repository indexer. The affected entry point is CachePolicy46314; 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 cache no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: CachePolicy46314|error_propagation_defect

Locate the implementation and callers associated with CachePolicy46314.

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

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

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

Produce only evidence-backed findings with severity and confidence.


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

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/queue/test_queue_463_15.ts

Locate the implementation and callers associated with QueuePolicy46315.

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

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

correct nullability defect while preserving the public contract

Apply a localized change that follows existing abstractions.

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

Obtain executable evidence for the requested behavior.

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

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


Instruction: Refactor the webhook in the repository indexer to remove duplicated authorization checks without changing behavior. The affected entry point is WebhookPolicy46316; keep the change aligned with the existing plugin-based service 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_463_16.ts

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

Confirm the local module boundary before searching for implementation details.

Question: WebhookPolicy46316|sensitive_data_exposure

Locate the implementation and callers associated with WebhookPolicy46316.

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

Hard tasks require caller evidence to control compatibility risk.

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

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

Identify existing test style and the nearest regression boundary.

correct sensitive-data exposure while preserving the public contract

Check static constraints relevant to the modified code.


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

A targeted verification path is identified

The final change remains inside the requested scope

Locate the implementation and callers associated with PermissionPolicy46317.

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


Instruction: Review the proposed configuration change in the repository indexer for correctness, scope, and regressions. The affected entry point is ConfigurationPolicy46318; keep the change aligned with the existing plugin-based service 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

correct resource-bounding defect while preserving the public contract


Instruction: Correct the configuration and operator guidance for structured errors in the repository indexer. The affected entry point is ParserPolicy46319; 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 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_463_19.ts

Question: ParserPolicy46319|failure_classification_defect

correct failure-classification defect while preserving the public contract


Instruction: Harden the download in the test orchestration service against cross-tenant access while preserving valid behavior. The affected entry point is DownloadPolicy46400; keep the change aligned with the existing layered service boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The download no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

go test ./download -run DownloadRegression46400

Repository evidence contradicts the initial assumption about the data representation.

repair diagnosed cause without broadening scope

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

Question: DownloadPolicy46400|authorization_order_defect

Locate the implementation and callers associated with DownloadPolicy46400.

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

Diff inspection is required before making a completion claim.


Instruction: Correct the configuration and operator guidance for dry-run mode in the test orchestration service. The affected entry point is AuditPolicy46401; keep the change aligned with the existing layered service boundary.

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

The audit no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: AuditPolicy46401|input_size_handling_defect

Locate the implementation and callers associated with AuditPolicy46401.

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

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


Instruction: Fix the defect where the worker does not preserve the public error contract in the test orchestration service. The affected entry point is WorkerPolicy46402; keep the change aligned with the existing layered service boundary.

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

The worker no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Locate the implementation and callers associated with WorkerPolicy46402.

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

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

The first targeted test fails and provides a concrete counterexample.

Repeating the same patch would ignore the new test evidence.

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

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

Apply the second bounded patch addressing the diagnosed cause.

The repaired behavior must be re-executed before completion.

Confirm the revised patch satisfies the original acceptance criterion.


Instruction: Add guarded support for audit metadata in the scheduler of the test orchestration service. The affected entry point is SchedulerPolicy46403; 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 scheduler no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Locate the implementation and callers associated with SchedulerPolicy46403.

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

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

Produce only evidence-backed findings with severity and confidence.


Instruction: Refactor the router in the test orchestration service to remove duplicated state transitions without changing behavior. The affected entry point is RouterPolicy46404; keep the change aligned with the existing layered service boundary.

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

The router no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

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

Confirm the local module boundary before searching for implementation details.

Question: RouterPolicy46404|boundary_condition_defect

Locate the implementation and callers associated with RouterPolicy46404.

Search evidence identifies src/router/router_464_04.rs as the narrow implementation boundary.

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

Identify existing test style and the nearest regression boundary.

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

Apply a localized change that follows existing abstractions.

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

Obtain executable evidence for the requested behavior.


Instruction: Add regression coverage for the case where the metrics drops the original error context in the test orchestration service. The affected entry point is MetricsPolicy46405; keep the change aligned with the existing layered service boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The metrics no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests MetricsRegression46405

Question: MetricsPolicy46405|error_propagation_defect

Locate the implementation and callers associated with MetricsPolicy46405.

Search evidence identifies src/main/java/metrics/MetricsService464.java as the narrow implementation boundary.

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

Hard tasks require caller evidence to control compatibility risk.

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

correct error-propagation defect while preserving the public contract

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

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

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


Instruction: Fix the defect where the logging fails when an optional field is absent in the test orchestration service. The affected entry point is LoggingPolicy46406; keep the change aligned with the existing layered service boundary.

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

The logging no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

ctest -R LoggingRegression46406 --output-on-failure

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

Locate the implementation and callers associated with LoggingPolicy46406.

Search evidence identifies src/logging/logging_464_06.cpp as the narrow implementation boundary.

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

Diff inspection is required before making a completion claim.


Instruction: Refactor the sandbox in the test orchestration service to remove duplicated cleanup logic without changing behavior. The affected entry point is SandboxPolicy46407; keep the change aligned with the existing layered service boundary.

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

The sandbox no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/sandbox/test_sandbox_464_07.ts

Question: SandboxPolicy46407|sensitive_data_exposure


Instruction: Refactor the session in the test orchestration service to remove duplicated validation logic without changing behavior. The affected entry point is SessionPolicy46408; 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 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 SessionRegression46408

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

Locate the implementation and callers associated with SessionPolicy46408.

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

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

Check static constraints relevant to the modified code.


Instruction: Review the proposed token change in the test orchestration service for correctness, scope, and regressions. The affected entry point is TokenPolicy46409; keep the change aligned with the existing layered service boundary.

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

The token no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/token/test_token_464_09.ts

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

Question: TokenPolicy46409|resource_bounding_defect

Locate the implementation and callers associated with TokenPolicy46409.

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


Instruction: Refactor the pagination in the test orchestration service to remove duplicated validation logic without changing behavior. The affected entry point is PaginationPolicy46410; keep the change aligned with the existing layered service boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The pagination no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/pagination/test_pagination_464_10.ts

Locate the implementation and callers associated with PaginationPolicy46410.

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

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


Instruction: Fix the defect where the cache accepts malformed input after normalization in the test orchestration service. The affected entry point is CachePolicy46411; keep the change aligned with the existing layered service boundary.

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

The cache no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

dotnet test --filter CacheRegression46411

Question: CachePolicy46411|validation_order_defect

Locate the implementation and callers associated with CachePolicy46411.

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

correct validation-order defect while preserving the public contract


Instruction: Review the proposed queue change in the test orchestration service for correctness, scope, and regressions. The affected entry point is QueuePolicy46412; keep the change aligned with the existing layered service boundary.

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

The queue no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/queue/test_queue_464_12.ts

Confirm the local module boundary before searching for implementation details.

Locate the implementation and callers associated with QueuePolicy46412.

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

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

correct retry-safety defect while preserving the public contract

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


Instruction: Refactor the webhook in the test orchestration service to remove duplicated error mapping without changing behavior. The affected entry point is WebhookPolicy46413; 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 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_464_13.ts

Question: WebhookPolicy46413|state_isolation_defect


Instruction: Add regression coverage for the case where the permission matches identifiers case-insensitively in the test orchestration service. The affected entry point is PermissionPolicy46414; keep the change aligned with the existing layered service boundary.

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

The permission no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests PermissionRegression46414

Locate the implementation and callers associated with PermissionPolicy46414.

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

Identify existing test style and the nearest regression boundary.

Hard tasks require caller evidence to control compatibility risk.

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

correct identity-comparison defect while preserving the public contract

Apply a localized change that follows existing abstractions.

Obtain executable evidence for the requested behavior.


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

./gradlew test --tests ConfigurationRegression46415

Locate the implementation and callers associated with ConfigurationPolicy46415.

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

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

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

correct false-success defect while preserving the public contract

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

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

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


Instruction: Add regression coverage for the case where the parser uses a broad filesystem permission in the test orchestration service. The affected entry point is ParserPolicy46416; keep the change aligned with the existing layered service 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

go test ./parser -run ParserRegression46416

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

Question: ParserPolicy46416|least_privilege_defect

Locate the implementation and callers associated with ParserPolicy46416.

Search evidence identifies internal/parser/parser_464_16.go as the narrow implementation boundary.

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

correct least-privilege 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.

Diff inspection is required before making a completion claim.


Instruction: Refactor the serializer in the test orchestration service to remove duplicated configuration parsing without changing behavior. The affected entry point is SerializerPolicy46417; keep the change aligned with the existing layered service 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

correct verification defect while preserving the public contract


Instruction: Fix the defect where the validator returns stale state after an update in the test orchestration service. The affected entry point is ValidatorPolicy46418; 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 validator no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

dotnet test --filter ValidatorRegression46418

Locate the implementation and callers associated with ValidatorPolicy46418.

Search evidence identifies src/validator/ValidatorService464.cs 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

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


Instruction: Refactor the retry in the test orchestration service to remove duplicated configuration parsing without changing behavior. The affected entry point is RetryPolicy46419; keep the change aligned with the existing layered service 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

Locate the implementation and callers associated with RetryPolicy46419.

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

correct unit-conversion defect while preserving the public contract


Instruction: Fix the defect where the scheduler loads an unbounded result set in the release manager. The affected entry point is SchedulerPolicy46500; keep the change aligned with the existing modular monolith boundary.

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

The scheduler no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

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

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

Identify existing test style and the nearest regression boundary.

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

Apply a localized change that follows existing abstractions.

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

Obtain executable evidence for the requested behavior.


Instruction: Harden the router in the release manager against path traversal while preserving valid behavior. The affected entry point is RouterPolicy46501; keep the change aligned with the existing modular monolith boundary.

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

The router no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/router/test_router_465_01.ts

Question: RouterPolicy46501|failure_classification_defect

Locate the implementation and callers associated with RouterPolicy46501.

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


Instruction: Add guarded support for request cancellation in the metrics of the release manager. The affected entry point is MetricsPolicy46502; 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 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_465_02.ts

Question: MetricsPolicy46502|validation_order_defect

Locate the implementation and callers associated with MetricsPolicy46502.

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

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


Instruction: Refactor the logging in the release manager to remove duplicated serialization logic without changing behavior. The affected entry point is LoggingPolicy46503; keep the change aligned with the existing modular monolith boundary.

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

The logging no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests LoggingRegression46503

Locate the implementation and callers associated with LoggingPolicy46503.

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

Hard tasks require caller evidence to control compatibility risk.

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

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


Instruction: Fix the defect where the sandbox mutates shared state across requests in the release manager. The affected entry point is SandboxPolicy46504; keep the change aligned with the existing modular monolith 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_465_04.ts

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

Question: SandboxPolicy46504|state_isolation_defect

Locate the implementation and callers associated with SandboxPolicy46504.

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

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

correct state-isolation defect while preserving the public contract

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

Check static constraints relevant to the modified code.


Instruction: Add guarded support for dry-run mode in the session of the release manager. The affected entry point is SessionPolicy46505; keep the change aligned with the existing modular monolith boundary.

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

The session no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: SessionPolicy46505|identity_comparison_defect

Locate the implementation and callers associated with SessionPolicy46505.

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

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

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

Diff inspection is required before making a completion claim.


Instruction: Review the proposed token change in the release manager for correctness, scope, and regressions. The affected entry point is TokenPolicy46506; keep the change aligned with the existing modular monolith boundary.

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

The token no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/token/test_token_465_06.ts

Locate the implementation and callers associated with TokenPolicy46506.

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

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

Question: authorize|permission|sanitize|validate

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


Instruction: Fix the defect where the pagination uses a broad filesystem permission in the release manager. The affected entry point is PaginationPolicy46507; 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 pagination 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 cache does not verify the persisted state in the release manager. The affected entry point is CachePolicy46508; keep the change aligned with the existing modular monolith 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

go test ./cache -run CacheRegression46508

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

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

Identify existing test style and the nearest regression boundary.

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

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

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

Apply a localized change that follows existing abstractions.

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

Obtain executable evidence for the requested behavior.


Instruction: Refactor the queue in the release manager to remove duplicated cleanup logic without changing behavior. The affected entry point is QueuePolicy46509; keep the change aligned with the existing modular monolith 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

Question: QueuePolicy46509|cache_invalidation_defect

Locate the implementation and callers associated with QueuePolicy46509.

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

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


Instruction: Fix the defect where the webhook uses seconds where milliseconds are expected in the release manager. The affected entry point is WebhookPolicy46510; keep the change aligned with the existing modular monolith 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_465_10.ts

Question: WebhookPolicy46510|unit_conversion_defect


Instruction: Fix the defect where the permission performs authorization after the side effect in the release manager. The affected entry point is PermissionPolicy46511; keep the change aligned with the existing modular monolith 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

go test ./permission -run PermissionRegression46511

Locate the implementation and callers associated with PermissionPolicy46511.

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

correct authorization-order defect while preserving the public contract


Instruction: Correct the configuration and operator guidance for bounded retries in the release manager. The affected entry point is ConfigurationPolicy46512; 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 configuration no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

correct input-size handling defect while preserving the public contract