Instruction: Add guarded support for cursor pagination in the parser of the release manager. The affected entry point is ParserPolicy46513; keep the change aligned with the existing modular monolith boundary.

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

The parser no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests ParserRegression46513

Locate the implementation and callers associated with ParserPolicy46513.

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

correct compatibility defect while preserving the public contract

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


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

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The serializer no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Use a bounded, updateable plan proportional to task complexity.

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

Locate the implementation and callers associated with SerializerPolicy46514.

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

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

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

confirm behavior
apply bounded patch
run targeted test
inspect diff

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

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.

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

correct resource-cleanup defect while preserving the public contract

Apply a localized change that follows existing abstractions.

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

Obtain executable evidence for the requested behavior.

Diff inspection is required before making a completion claim.

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


Instruction: Add regression coverage for the case where the validator rejects valid boundary values in the release manager. The affected entry point is ValidatorPolicy46515; keep the change aligned with the existing modular monolith boundary.

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

The validator no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests ValidatorRegression46515

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

Locate the implementation and callers associated with ValidatorPolicy46515.

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

correct boundary-condition 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 retry drops the original error context in the release manager. The affected entry point is RetryPolicy46516; keep the change aligned with the existing modular monolith boundary.

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

The retry no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Ground every decision in repository evidence before editing.

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

Repository evidence contradicts the initial assumption about the data representation.

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

repair diagnosed cause without broadening scope

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

Confirm the local module boundary before searching for implementation details.

Question: RetryPolicy46516|error_propagation_defect

Locate the implementation and callers associated with RetryPolicy46516.

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

correct error-propagation defect while preserving the public contract

The original acceptance criterion passes

The failure signal is no longer reproduced

The final report distinguishes executed evidence from assumptions


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

A targeted verification path is identified

The final change remains inside the requested scope

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

correct nullability defect while preserving the public contract

rewrite subsystem
replace dependencies
change API

Use a bounded, updateable plan proportional to task complexity.


Instruction: Add regression coverage for the case where the search logs a secret-bearing request field in the release manager. The affected entry point is SearchPolicy46518; keep the change aligned with the existing modular monolith 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

Question: SearchPolicy46518|sensitive_data_exposure

correct sensitive-data exposure while preserving the public contract


Instruction: Correct the configuration and operator guidance for audit metadata in the release manager. The affected entry point is IndexPolicy46519; keep the change aligned with the existing modular monolith 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

go test ./index -run IndexRegression46519

Locate the implementation and callers associated with IndexPolicy46519.

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

correct idempotency defect while preserving the public contract


Instruction: Review the proposed logging change in the knowledge graph API for correctness, scope, and regressions. The affected entry point is LoggingPolicy46600; keep the change aligned with the existing event-driven worker 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

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

Question: LoggingPolicy46600|cache_invalidation_defect

Locate the implementation and callers associated with LoggingPolicy46600.

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

correct cache-invalidation defect while preserving the public contract

The first targeted test fails and provides a concrete counterexample.

Repeating the same patch would ignore the new test evidence.

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

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

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 sandbox uses seconds where milliseconds are expected in the knowledge graph API. The affected entry point is SandboxPolicy46601; keep the change aligned with the existing event-driven worker boundary.

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

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

Ground every decision in repository evidence before editing.

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

Question: SandboxPolicy46601|unit_conversion_defect

Locate the implementation and callers associated with SandboxPolicy46601.

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

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

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

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

correct unit-conversion defect while preserving the public contract


Instruction: Add guarded support for per-tenant configuration in the session of the knowledge graph API. The affected entry point is SessionPolicy46602; keep the change aligned with the existing event-driven worker boundary.

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

The session no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

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

Question: SessionPolicy46602|authorization_order_defect

Locate the implementation and callers associated with SessionPolicy46602.

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

correct authorization-order 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: Review the proposed token change in the knowledge graph API for correctness, scope, and regressions. The affected entry point is TokenPolicy46603; keep the change aligned with the existing event-driven worker 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

go test ./token -run TokenRegression46603

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

Question: TokenPolicy46603|input_size_handling_defect

Locate the implementation and callers associated with TokenPolicy46603.

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

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

Identify existing test style and the nearest regression boundary.

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

correct input-size handling defect while preserving the public contract

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

Diff inspection is required before making a completion claim.


Instruction: Harden the pagination in the knowledge graph API against replay attacks while preserving valid behavior. The affected entry point is PaginationPolicy46604; keep the change aligned with the existing event-driven worker boundary.

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

The pagination no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Verify the claimed behavior with targeted checks before completion.

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

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

Hard tasks require caller evidence to control compatibility risk.

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

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

Question: authorize|permission|sanitize|validate

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


Instruction: Harden the cache in the knowledge graph API against replay attacks while preserving valid behavior. The affected entry point is CachePolicy46605; keep the change aligned with the existing event-driven worker boundary.

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

The cache no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

go test ./cache -run CacheRegression46605

Question: CachePolicy46605|resource_cleanup_defect

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


Instruction: Review the proposed queue change in the knowledge graph API for correctness, scope, and regressions. The affected entry point is QueuePolicy46606; keep the change aligned with the existing event-driven worker boundary.

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

The queue no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests QueueRegression46606

Question: QueuePolicy46606|boundary_condition_defect

Verify the claimed behavior with targeted checks before completion.


Instruction: Review the proposed webhook change in the knowledge graph API for correctness, scope, and regressions. The affected entry point is WebhookPolicy46607; keep the change aligned with the existing event-driven worker boundary.

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

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

The diff includes a configuration change outside the requested boundary.

Question: WebhookPolicy46607|error_propagation_defect

Locate the implementation and callers associated with WebhookPolicy46607.

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

Question: authorize|permission|sanitize|validate


Instruction: Add regression coverage for the case where the permission fails when an optional field is absent in the knowledge graph API. The affected entry point is PermissionPolicy46608; keep the change aligned with the existing event-driven worker boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The permission no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/permission/test_permission_466_08.ts

Locate the implementation and callers associated with PermissionPolicy46608.

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


Instruction: Add guarded support for dry-run mode in the configuration of the knowledge graph API. The affected entry point is ConfigurationPolicy46609; keep the change aligned with the existing event-driven worker boundary.

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

The configuration no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Locate the implementation and callers associated with ConfigurationPolicy46609.

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

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


Instruction: Fix the defect where the parser creates duplicate jobs under concurrent delivery in the knowledge graph API. The affected entry point is ParserPolicy46610; keep the change aligned with the existing event-driven worker 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

Respect scope and request approval only for materially risky actions.

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

Locate the implementation and callers associated with ParserPolicy46610.

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

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

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

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


Instruction: Fix the defect where the serializer loads an unbounded result set in the knowledge graph API. The affected entry point is SerializerPolicy46611; keep the change aligned with the existing event-driven worker boundary.

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

The serializer no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/serializer/test_serializer_466_11.ts

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

Locate the implementation and callers associated with SerializerPolicy46611.

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

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

correctness security compatibility test_coverage

Produce only evidence-backed findings with severity and confidence.


Instruction: Fix the defect where the validator misclassifies transient failures as permanent in the knowledge graph API. The affected entry point is ValidatorPolicy46612; keep the change aligned with the existing event-driven worker boundary.

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

The validator no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

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

Locate the implementation and callers associated with ValidatorPolicy46612.

Search evidence identifies src/validator/validator_466_12.rs as the narrow implementation boundary.

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

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

correct failure-classification defect while preserving the public contract

Apply a localized change that follows existing abstractions.

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

The first targeted test fails and provides a concrete counterexample.

Repeating the same patch would ignore the new test evidence.

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

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

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 retry in the knowledge graph API to remove duplicated cleanup logic without changing behavior. The affected entry point is RetryPolicy46613; keep the change aligned with the existing event-driven worker boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The retry no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests RetryRegression46613

Question: RetryPolicy46613|validation_order_defect

correct validation-order defect while preserving the public contract

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


Instruction: Refactor the timeout in the knowledge graph API to remove duplicated cleanup logic without changing behavior. The affected entry point is TimeoutPolicy46614; keep the change aligned with the existing event-driven worker boundary.

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

The timeout no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/timeout/test_timeout_466_14.ts

Locate the implementation and callers associated with TimeoutPolicy46614.

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

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

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

Identify existing test style and the nearest regression boundary.

correct retry-safety defect while preserving the public contract

Obtain executable evidence for the requested behavior.


Instruction: Fix the defect where the search mutates shared state across requests in the knowledge graph API. The affected entry point is SearchPolicy46615; keep the change aligned with the existing event-driven worker boundary.

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

The search no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: SearchPolicy46615|state_isolation_defect

correct state-isolation defect while preserving the public contract

Ground every decision in repository evidence before editing.


Instruction: Add regression coverage for the case where the index matches identifiers case-insensitively in the knowledge graph API. The affected entry point is IndexPolicy46616; keep the change aligned with the existing event-driven worker boundary.

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

The index no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

go test ./index -run IndexRegression46616

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

Confirm the local module boundary before searching for implementation details.

Question: IndexPolicy46616|identity_comparison_defect

Locate the implementation and callers associated with IndexPolicy46616.

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

Hard tasks require caller evidence to control compatibility risk.

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

correct identity-comparison defect while preserving the public contract

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

Check static constraints relevant to the modified code.

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

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


Instruction: Fix the defect where the migration marks partial work as successful in the knowledge graph API. The affected entry point is MigrationPolicy46617; keep the change aligned with the existing event-driven worker boundary.

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

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

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

Locate the implementation and callers associated with MigrationPolicy46617.

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

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

correct false-success defect while preserving the public contract


Instruction: Add guarded support for request cancellation in the upload of the knowledge graph API. The affected entry point is UploadPolicy46618; keep the change aligned with the existing event-driven worker 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

Question: UploadPolicy46618|least_privilege_defect

Locate the implementation and callers associated with UploadPolicy46618.

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

correct least-privilege defect while preserving the public contract

Apply a localized change that follows existing abstractions.

The first targeted test fails and provides a concrete counterexample.

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

Apply the second bounded patch addressing the diagnosed cause.

Confirm the revised patch satisfies the original acceptance criterion.


Instruction: Fix the defect where the download does not verify the persisted state in the knowledge graph API. The affected entry point is DownloadPolicy46619; keep the change aligned with the existing event-driven worker boundary.

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

The 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 DownloadRegression46619

Locate the implementation and callers associated with DownloadPolicy46619.

Search evidence identifies internal/download/download_466_19.go 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.

Identify existing test style and the nearest regression boundary.

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

correct verification defect while preserving the public contract

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

Obtain executable evidence for the requested behavior.


Instruction: Fix the defect where the token logs a secret-bearing request field in the session service. The affected entry point is TokenPolicy46700; keep the change aligned with the existing CLI application boundary.

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

The token no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Confirm the local module boundary before searching for implementation details.

Question: TokenPolicy46700|sensitive_data_exposure

Locate the implementation and callers associated with TokenPolicy46700.

Search evidence identifies src/token/token_467_00.php as the narrow implementation boundary.

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

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


Instruction: Fix the defect where the pagination creates duplicate jobs under concurrent delivery in the session service. The affected entry point is PaginationPolicy46701; keep the change aligned with the existing CLI application 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 PaginationRegression46701

Locate the implementation and callers associated with PaginationPolicy46701.

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

Diff inspection is required before making a completion claim.

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


Instruction: Add guarded support for explicit timeouts in the cache of the session service. The affected entry point is CachePolicy46702; keep the change aligned with the existing CLI application 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

npm test -- test/cache/test_cache_467_02.ts

Question: CachePolicy46702|resource_bounding_defect

correct resource-bounding defect while preserving the public contract


Instruction: Refactor the queue in the session service to remove duplicated retry decisions without changing behavior. The affected entry point is QueuePolicy46703; keep the change aligned with the existing CLI application 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 QueueRegression46703

Question: QueuePolicy46703|failure_classification_defect


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

./gradlew test --tests WebhookRegression46704

Question: WebhookPolicy46704|validation_order_defect


Instruction: Add guarded support for graceful shutdown in the permission of the session service. The affected entry point is PermissionPolicy46705; keep the change aligned with the existing CLI application boundary.

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

The permission no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/permission/test_permission_467_05.ts


Instruction: Add guarded support for per-tenant configuration in the configuration of the session service. The affected entry point is ConfigurationPolicy46706; keep the change aligned with the existing CLI application boundary.

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

The configuration no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests ConfigurationRegression46706

Locate the implementation and callers associated with ConfigurationPolicy46706.

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

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


Instruction: Fix the defect where the parser matches identifiers case-insensitively in the session service. The affected entry point is ParserPolicy46707; keep the change aligned with the existing CLI application boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The parser no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests ParserRegression46707

Question: ParserPolicy46707|identity_comparison_defect

Locate the implementation and callers associated with ParserPolicy46707.

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

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

Apply a localized change that follows existing abstractions.


Instruction: Add regression coverage for the case where the serializer marks partial work as successful in the session service. The affected entry point is SerializerPolicy46708; keep the change aligned with the existing CLI application boundary.

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

The serializer no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests SerializerRegression46708

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

Locate the implementation and callers associated with SerializerPolicy46708.

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

The first targeted test fails and provides a concrete counterexample.

Repeating the same patch would ignore the new test evidence.

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

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

Apply the second bounded patch addressing the diagnosed cause.

The repaired behavior must be re-executed before completion.

Confirm the revised patch satisfies the original acceptance criterion.


Instruction: Refactor the validator in the session service to remove duplicated authorization checks without changing behavior. The affected entry point is ValidatorPolicy46709; keep the change aligned with the existing CLI application boundary.

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

The validator no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/validator/test_validator_467_09.ts


Instruction: Add guarded support for request cancellation in the retry of the session service. The affected entry point is RetryPolicy46710; keep the change aligned with the existing CLI application boundary.

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

The retry no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/retry/test_retry_467_10.ts

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

Locate the implementation and callers associated with RetryPolicy46710.

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

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

Identify existing test style and the nearest regression boundary.

Hard tasks require caller evidence to control compatibility risk.

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

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

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.


Instruction: Refactor the timeout in the session service to remove duplicated serialization logic without changing behavior. The affected entry point is TimeoutPolicy46711; keep the change aligned with the existing CLI application boundary.

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

The timeout no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: TimeoutPolicy46711|cache_invalidation_defect


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

Confirm the local module boundary before searching for implementation details.

Question: SearchPolicy46712|unit_conversion_defect

Locate the implementation and callers associated with SearchPolicy46712.

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

Diff inspection is required before making a completion claim.


Instruction: Add regression coverage for the case where the index performs authorization after the side effect in the session service. The affected entry point is IndexPolicy46713; keep the change aligned with the existing CLI application boundary.

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

The index no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/index/test_index_467_13.ts

Question: IndexPolicy46713|authorization_order_defect

Locate the implementation and callers associated with IndexPolicy46713.

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

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


Instruction: Add guarded support for explicit timeouts in the migration of the session service. The affected entry point is MigrationPolicy46714; keep the change aligned with the existing CLI application boundary.

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

The migration no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Locate the implementation and callers associated with MigrationPolicy46714.

Search evidence identifies src/migration/migration_467_14.rs as the narrow implementation boundary.

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


Instruction: Fix the defect where the upload does not preserve the public error contract in the session service. The affected entry point is UploadPolicy46715; keep the change aligned with the existing CLI application boundary.

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

The upload no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

ctest -R UploadRegression46715 --output-on-failure

Locate the implementation and callers associated with UploadPolicy46715.

Search evidence identifies src/upload/upload_467_15.cpp as the narrow implementation boundary.

correct compatibility defect while preserving the public contract

Apply a localized change that follows existing abstractions.

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

Check static constraints relevant to the modified code.

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


Instruction: Add guarded support for input size limits in the download of the session service. The affected entry point is DownloadPolicy46716; keep the change aligned with the existing CLI application 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

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

Question: DownloadPolicy46716|resource_cleanup_defect

Locate the implementation and callers associated with DownloadPolicy46716.

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

correct resource-cleanup defect while preserving the public contract


Instruction: Add guarded support for graceful shutdown in the audit of the session service. The affected entry point is AuditPolicy46717; keep the change aligned with the existing CLI application 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: AuditPolicy46717|boundary_condition_defect

Respect scope and request approval only for materially risky actions.


Instruction: Fix the defect where the worker drops the original error context in the session service. The affected entry point is WorkerPolicy46718; keep the change aligned with the existing CLI application 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

./gradlew test --tests WorkerRegression46718

Question: WorkerPolicy46718|error_propagation_defect

correct error-propagation defect while preserving the public contract

revise the failed assumption without expanding scope

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


Instruction: Add guarded support for safe fallback behavior in the scheduler of the session service. The affected entry point is SchedulerPolicy46719; keep the change aligned with the existing CLI application boundary.

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

The scheduler no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Locate the implementation and callers associated with SchedulerPolicy46719.

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

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

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

correct nullability defect while preserving the public contract


Instruction: Add guarded support for bounded retries in the queue of the rate-limit gateway. The affected entry point is QueuePolicy46800; keep the change aligned with the existing HTTP API 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

ctest -R QueueRegression46800 --output-on-failure

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

Locate the implementation and callers associated with QueuePolicy46800.

Search evidence identifies src/queue/queue_468_00.cpp as the narrow implementation boundary.

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

Identify existing test style and the nearest regression boundary.

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 webhook does not verify the persisted state in the rate-limit gateway. The affected entry point is WebhookPolicy46801; keep the change aligned with the existing HTTP API 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_468_01.ts

Locate the implementation and callers associated with WebhookPolicy46801.

Search evidence identifies src/webhook/webhook_468_01.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.


Instruction: Fix the defect where the permission returns stale state after an update in the rate-limit gateway. The affected entry point is PermissionPolicy46802; keep the change aligned with the existing HTTP API 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

go test ./permission -run PermissionRegression46802

Locate the implementation and callers associated with PermissionPolicy46802.

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

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

correct cache-invalidation defect while preserving the public contract

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

The first targeted test fails and provides a concrete counterexample.

Repeating the same patch would ignore the new test evidence.

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

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

Apply the second bounded patch addressing the diagnosed cause.

The repaired behavior must be re-executed before completion.

Confirm the revised patch satisfies the original acceptance criterion.

Diff inspection is required before making a completion claim.

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


Instruction: Refactor the configuration in the rate-limit gateway to remove duplicated error mapping without changing behavior. The affected entry point is ConfigurationPolicy46803; keep the change aligned with the existing HTTP API boundary.

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

The configuration no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/configuration/test_configuration_468_03.ts

correct unit-conversion defect while preserving the public contract


Instruction: Add guarded support for idempotency keys in the parser of the rate-limit gateway. The affected entry point is ParserPolicy46804; 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 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_468_04.ts

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

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

Confirm the local module boundary before searching for implementation details.

Question: ParserPolicy46804|authorization_order_defect

Locate the implementation and callers associated with ParserPolicy46804.

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

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

correct authorization-order defect while preserving the public contract

Apply a localized change that follows existing abstractions.

Obtain executable evidence for the requested behavior.

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 serializer change in the rate-limit gateway for correctness, scope, and regressions. The affected entry point is SerializerPolicy46805; keep the change aligned with the existing HTTP API boundary.

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

The serializer no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests SerializerRegression46805

Locate the implementation and callers associated with SerializerPolicy46805.

Search evidence identifies src/main/java/serializer/SerializerService468.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 existing test style and the nearest regression boundary.

correct input-size handling defect while preserving the public contract

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

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


Instruction: Fix the defect where the validator does not preserve the public error contract in the rate-limit gateway. The affected entry point is ValidatorPolicy46806; keep the change aligned with the existing HTTP API boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The validator no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

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

Locate the implementation and callers associated with ValidatorPolicy46806.

Search evidence identifies src/validator/validator_468_06.py as the narrow implementation boundary.

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

Hard tasks require caller evidence to control compatibility risk.

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


Instruction: Harden the retry in the rate-limit gateway against secret leakage while preserving valid behavior. The affected entry point is RetryPolicy46807; keep the change aligned with the existing HTTP API boundary.

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

The retry no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: RetryPolicy46807|resource_cleanup_defect

Locate the implementation and callers associated with RetryPolicy46807.

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

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: Fix the defect where the timeout rejects valid boundary values in the rate-limit gateway. The affected entry point is TimeoutPolicy46808; keep the change aligned with the existing HTTP API boundary.

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

The timeout no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests TimeoutRegression46808

Question: TimeoutPolicy46808|boundary_condition_defect

Locate the implementation and callers associated with TimeoutPolicy46808.

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

correct boundary-condition defect while preserving the public contract


Instruction: Add guarded support for graceful shutdown in the search of the rate-limit gateway. The affected entry point is SearchPolicy46809; 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 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_468_09.ts

Question: SearchPolicy46809|error_propagation_defect

Locate the implementation and callers associated with SearchPolicy46809.

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

Diff inspection is required before making a completion claim.

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


Instruction: Refactor the index in the rate-limit gateway to remove duplicated configuration parsing without changing behavior. The affected entry point is IndexPolicy46810; keep the change aligned with the existing HTTP API 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

Locate the implementation and callers associated with IndexPolicy46810.

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


Instruction: Review the proposed migration change in the rate-limit gateway for correctness, scope, and regressions. The affected entry point is MigrationPolicy46811; keep the change aligned with the existing HTTP API 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

npm test -- test/migration/test_migration_468_11.ts

Locate the implementation and callers associated with MigrationPolicy46811.

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

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

correct sensitive-data exposure while preserving the public contract

Apply a localized change that follows existing abstractions.

Obtain executable evidence for the requested behavior.


Instruction: Add guarded support for bounded retries in the upload of the rate-limit gateway. The affected entry point is UploadPolicy46812; keep the change aligned with the existing HTTP API 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_468_12.ts

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

Confirm the local module boundary before searching for implementation details.

Locate the implementation and callers associated with UploadPolicy46812.

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

correct idempotency 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: Fix the defect where the download loads an unbounded result set in the rate-limit gateway. The affected entry point is DownloadPolicy46813; keep the change aligned with the existing HTTP API 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: DownloadPolicy46813|resource_bounding_defect

Locate the implementation and callers associated with DownloadPolicy46813.

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

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

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

Identify existing test style and the nearest regression boundary.


Instruction: Harden the audit in the rate-limit gateway against unsafe deserialization while preserving valid behavior. The affected entry point is AuditPolicy46814; 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 audit no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests AuditRegression46814

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

Question: AuditPolicy46814|failure_classification_defect

Locate the implementation and callers associated with AuditPolicy46814.

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

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

correct failure-classification defect while preserving the public contract


Instruction: Fix the defect where the worker accepts malformed input after normalization in the rate-limit gateway. The affected entry point is WorkerPolicy46815; keep the change aligned with the existing HTTP API 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

./gradlew test --tests WorkerRegression46815

Question: WorkerPolicy46815|validation_order_defect

Locate the implementation and callers associated with WorkerPolicy46815.

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

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

correct validation-order defect while preserving the public contract

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

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: Harden the scheduler in the rate-limit gateway against unsafe deserialization while preserving valid behavior. The affected entry point is SchedulerPolicy46816; keep the change aligned with the existing HTTP API 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

./gradlew test --tests SchedulerRegression46816

Locate the implementation and callers associated with SchedulerPolicy46816.

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

correct retry-safety defect while preserving the public contract

Diff inspection is required before making a completion claim.

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


Instruction: Fix the defect where the router mutates shared state across requests in the rate-limit gateway. The affected entry point is RouterPolicy46817; keep the change aligned with the existing HTTP API 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

go test ./router -run RouterRegression46817

Question: RouterPolicy46817|state_isolation_defect

Locate the implementation and callers associated with RouterPolicy46817.

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

correct state-isolation defect while preserving the public contract


Instruction: Fix the defect where the metrics matches identifiers case-insensitively in the rate-limit gateway. The affected entry point is MetricsPolicy46818; keep the change aligned with the existing HTTP API 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: MetricsPolicy46818|identity_comparison_defect

Locate the implementation and callers associated with MetricsPolicy46818.

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

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

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

A targeted verification path is identified

The final change remains inside the requested scope

correct false-success defect while preserving the public contract


Instruction: Fix the defect where the configuration drops the original error context in the webhook dispatcher. The affected entry point is ConfigurationPolicy46900; keep the change aligned with the existing background processor 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

go test ./configuration -run ConfigurationRegression46900

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

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

correct error-propagation defect while preserving the public contract

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

Check static constraints relevant to the modified code.


Instruction: Harden the parser in the webhook dispatcher against replay attacks while preserving valid behavior. The affected entry point is ParserPolicy46901; keep the change aligned with the existing background processor 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

Locate the implementation and callers associated with ParserPolicy46901.

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

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

Question: authorize|permission|sanitize|validate

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


Instruction: Harden the serializer in the webhook dispatcher against replay attacks while preserving valid behavior. The affected entry point is SerializerPolicy46902; keep the change aligned with the existing background processor 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

./gradlew test --tests SerializerRegression46902

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

Locate the implementation and callers associated with SerializerPolicy46902.

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


Instruction: Refactor the validator in the webhook dispatcher to remove duplicated cleanup logic without changing behavior. The affected entry point is ValidatorPolicy46903; 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 validator 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 ValidatorPolicy46903.

Search evidence identifies src/validator/validator_469_03.php as the narrow implementation boundary.

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

Identify existing test style and the nearest regression boundary.

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

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


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

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

The retry no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/retry/test_retry_469_04.ts

Question: RetryPolicy46904|resource_bounding_defect

Locate the implementation and callers associated with RetryPolicy46904.

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

Hard tasks require caller evidence to control compatibility risk.

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

correct resource-bounding defect while preserving the public contract

Diff inspection is required before making a completion claim.

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


Instruction: Harden the timeout in the webhook dispatcher against replay attacks while preserving valid behavior. The affected entry point is TimeoutPolicy46905; keep the change aligned with the existing background processor boundary.

Preserve error semantics
Reuse existing project abstractions
Verify the final diff

The timeout no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/timeout/test_timeout_469_05.ts

Question: TimeoutPolicy46905|failure_classification_defect

Locate the implementation and callers associated with TimeoutPolicy46905.

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

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

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

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

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


Instruction: Add guarded support for request cancellation in the search of the webhook dispatcher. The affected entry point is SearchPolicy46906; keep the change aligned with the existing background processor boundary.

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

The search no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: SearchPolicy46906|validation_order_defect

Locate the implementation and callers associated with SearchPolicy46906.

Search evidence identifies src/search/search_469_06.py 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: Add guarded support for structured errors in the index of the webhook dispatcher. The affected entry point is IndexPolicy46907; keep the change aligned with the existing background processor boundary.

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

The index no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/index/test_index_469_07.ts

Locate the implementation and callers associated with IndexPolicy46907.

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


Instruction: Add regression coverage for the case where the migration mutates shared state across requests in the webhook dispatcher. The affected entry point is MigrationPolicy46908; 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 migration 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 MigrationPolicy46908.

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


Instruction: Refactor the upload in the webhook dispatcher to remove duplicated error mapping without changing behavior. The affected entry point is UploadPolicy46909; keep the change aligned with the existing background processor boundary.

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

The upload no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: UploadPolicy46909|identity_comparison_defect

Locate the implementation and callers associated with UploadPolicy46909.

Search evidence identifies src/upload/upload_469_09.py 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: Harden the download in the webhook dispatcher against cross-tenant access while preserving valid behavior. The affected entry point is DownloadPolicy46910; keep the change aligned with the existing background processor 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

npm test -- test/download/test_download_469_10.ts

Question: DownloadPolicy46910|false_success_defect

Question: authorize|permission|sanitize|validate


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

./gradlew test --tests AuditRegression46911

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

Locate the implementation and callers associated with AuditPolicy46911.

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

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

Identify existing test style and the nearest regression boundary.

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

Produce only evidence-backed findings with severity and confidence.


Instruction: Add regression coverage for the case where the worker does not verify the persisted state in the webhook dispatcher. The affected entry point is WorkerPolicy46912; keep the change aligned with the existing background processor 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 WorkerPolicy46912.

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

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

correct verification defect while preserving the public contract

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

Diff inspection is required before making a completion claim.

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


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

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests SchedulerRegression46913

Locate the implementation and callers associated with SchedulerPolicy46913.

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

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

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

correct cache-invalidation defect while preserving the public contract


Instruction: Refactor the router in the webhook dispatcher to remove duplicated configuration parsing without changing behavior. The affected entry point is RouterPolicy46914; keep the change aligned with the existing background processor boundary.

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

The router no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: RouterPolicy46914|unit_conversion_defect

Locate the implementation and callers associated with RouterPolicy46914.

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

correct unit-conversion defect while preserving the public contract


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

go test ./metrics -run MetricsRegression46915

Question: MetricsPolicy46915|authorization_order_defect

Locate the implementation and callers associated with MetricsPolicy46915.

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

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

correct authorization-order defect while preserving the public contract

Apply a localized change that follows existing abstractions.

Obtain executable evidence for the requested behavior.

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

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


Instruction: Add regression coverage for the case where the logging silently truncates an oversized payload in the webhook dispatcher. The affected entry point is LoggingPolicy46916; keep the change aligned with the existing background processor 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

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

Confirm the local module boundary before searching for implementation details.

Question: LoggingPolicy46916|input_size_handling_defect

Locate the implementation and callers associated with LoggingPolicy46916.

Search evidence identifies src/logging/logging_469_16.rs as the narrow implementation boundary.


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

Locate the implementation and callers associated with SandboxPolicy46917.

Search evidence identifies src/sandbox/sandbox_469_17.rs as the narrow implementation boundary.

Hard tasks require caller evidence to control compatibility risk.

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

correct compatibility defect while preserving the public contract

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

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

Check static constraints relevant to the modified code.


Instruction: Harden the session in the webhook dispatcher against command injection while preserving valid behavior. The affected entry point is SessionPolicy46918; 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 session no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: SessionPolicy46918|resource_cleanup_defect

correct resource-cleanup defect while preserving the public contract


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

ctest -R TokenRegression46919 --output-on-failure

repair diagnosed cause without broadening scope

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

Question: TokenPolicy46919|boundary_condition_defect

Locate the implementation and callers associated with TokenPolicy46919.

Search evidence identifies src/token/token_469_19.cpp as the narrow implementation boundary.

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

Identify existing test style and the nearest regression boundary.

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

Produce only evidence-backed findings with severity and confidence.

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.

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


Instruction: Fix the defect where the validator matches identifiers case-insensitively in the access-control service. The affected entry point is ValidatorPolicy47000; keep the change aligned with the existing library package boundary.

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

The validator no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests ValidatorRegression47000

Locate the implementation and callers associated with ValidatorPolicy47000.

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

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

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

Diff inspection is required before making a completion claim.


Instruction: Add regression coverage for the case where the retry marks partial work as successful in the access-control service. The affected entry point is RetryPolicy47001; keep the change aligned with the existing library package boundary.

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

The retry no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

./gradlew test --tests RetryRegression47001

Locate the implementation and callers associated with RetryPolicy47001.

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


Instruction: Review the proposed timeout change in the access-control service for correctness, scope, and regressions. The affected entry point is TimeoutPolicy47002; 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 timeout no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/timeout/test_timeout_470_02.ts

Question: TimeoutPolicy47002|least_privilege_defect

Locate the implementation and callers associated with TimeoutPolicy47002.

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

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

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

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

Question: authorize|permission|sanitize|validate

correct least-privilege defect while preserving the public contract

Apply a localized change that follows existing abstractions.

Obtain executable evidence for the requested behavior.

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


Instruction: Add guarded support for audit metadata in the search of the access-control service. The affected entry point is SearchPolicy47003; keep the change aligned with the existing library package boundary.

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

The search no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

npm test -- test/search/test_search_470_03.ts

Locate the implementation and callers associated with SearchPolicy47003.

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


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

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

Confirm the local module boundary before searching for implementation details.

Question: IndexPolicy47004|cache_invalidation_defect

Locate the implementation and callers associated with IndexPolicy47004.

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


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

npm test -- test/migration/test_migration_470_05.ts

Locate the implementation and callers associated with MigrationPolicy47005.

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

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

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


Instruction: Add guarded support for per-tenant configuration in the upload of the access-control service. The affected entry point is UploadPolicy47006; keep the change aligned with the existing library package 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

ctest -R UploadRegression47006 --output-on-failure

Question: UploadPolicy47006|authorization_order_defect

revise the failed assumption without expanding scope


Instruction: Refactor the download in the access-control service to remove duplicated cleanup logic without changing behavior. The affected entry point is DownloadPolicy47007; 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 download no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

Question: DownloadPolicy47007|input_size_handling_defect

correct input-size handling defect while preserving the public contract


Instruction: Add regression coverage for the case where the audit does not preserve the public error contract in the access-control service. The affected entry point is AuditPolicy47008; keep the change aligned with the existing library package 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

npm test -- test/audit/test_audit_470_08.ts

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

Locate the implementation and callers associated with AuditPolicy47008.

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

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

Identify existing test style and the nearest regression boundary.


Instruction: Add guarded support for cursor pagination in the worker of the access-control service. The affected entry point is WorkerPolicy47009; keep the change aligned with the existing library package 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

npm test -- test/worker/test_worker_470_09.ts

Question: WorkerPolicy47009|resource_cleanup_defect

Locate the implementation and callers associated with WorkerPolicy47009.

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


Instruction: Fix the defect where the scheduler rejects valid boundary values in the access-control service. The affected entry point is SchedulerPolicy47010; keep the change aligned with the existing library package 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

npm test -- test/scheduler/test_scheduler_470_10.ts

Locate the implementation and callers associated with SchedulerPolicy47010.

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

correct boundary-condition defect while preserving the public contract

Hard tasks require caller evidence to control compatibility risk.

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

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

Check static constraints relevant to the modified code.

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


Instruction: Review the proposed router change in the access-control service for correctness, scope, and regressions. The affected entry point is RouterPolicy47011; keep the change aligned with the existing library package 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_470_11.ts

Question: RouterPolicy47011|error_propagation_defect

Question: authorize|permission|sanitize|validate


Instruction: Add regression coverage for the case where the metrics fails when an optional field is absent in the access-control service. The affected entry point is MetricsPolicy47012; 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 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 MetricsRegression47012

correct nullability defect while preserving the public contract


Instruction: Correct the configuration and operator guidance for dry-run mode in the access-control service. The affected entry point is LoggingPolicy47013; keep the change aligned with the existing library package 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

Question: LoggingPolicy47013|sensitive_data_exposure

Locate the implementation and callers associated with LoggingPolicy47013.

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

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

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

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

correct sensitive-data exposure while preserving the public contract

Apply a localized change that follows existing abstractions.

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

Obtain executable evidence for the requested behavior.

Diff inspection is required before making a completion claim.


Instruction: Refactor the sandbox in the access-control service to remove duplicated retry decisions without changing behavior. The affected entry point is SandboxPolicy47014; keep the change aligned with the existing library package 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

./gradlew test --tests SandboxRegression47014

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

Locate the implementation and callers associated with SandboxPolicy47014.

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

correct idempotency defect while preserving the public contract


Instruction: Fix the defect where the session loads an unbounded result set in the access-control service. The affected entry point is SessionPolicy47015; keep the change aligned with the existing library package 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: SessionPolicy47015|resource_bounding_defect

Locate the implementation and callers associated with SessionPolicy47015.

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

The first targeted test fails and provides a concrete counterexample.

Repeating the same patch would ignore the new test evidence.

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

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

Apply the second bounded patch addressing the diagnosed cause.

The repaired behavior must be re-executed before completion.

Confirm the revised patch satisfies the original acceptance criterion.

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

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


Instruction: Add guarded support for input size limits in the token of the access-control service. The affected entry point is TokenPolicy47016; keep the change aligned with the existing library package 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

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

Locate the implementation and callers associated with TokenPolicy47016.

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

correct failure-classification defect while preserving the public contract


Instruction: Add guarded support for graceful shutdown in the pagination of the access-control service. The affected entry point is PaginationPolicy47017; 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 pagination no longer exhibits the specified behavior

A targeted verification path is identified

The final change remains inside the requested scope

dotnet test --filter PaginationRegression47017

correct validation-order defect while preserving the public contract