Skip to content

Validate completed symbolic inputs during search - #620

Open
CaelmBleidd wants to merge 1 commit into
caelmbleidd/pbt-campaign-external-deadlinefrom
caelmbleidd/pbt-live-input-validation
Open

CaelmBleidd wants to merge 1 commit into
caelmbleidd/pbt-campaign-external-deadlinefrom
caelmbleidd/pbt-live-input-validation

Conversation

@CaelmBleidd

Copy link
Copy Markdown
Member

Completed symbolic inputs were replayed only after search ended. A time-limited search could therefore return dozens of inputs that no longer fit the remaining native validation budget.

When capture is enabled, validate each newly captured passing input during search and reuse the existing same-phase replay cache for guidance and final collection. Search and native replay share the existing deadline; the per-operation replay does not subtract the validation reserve a second time. Inputs predicted to fail remain on the original canonical-confirmation path before final collection. Unknown results, conflicting predictions, source checks and incomplete-input accounting remain explicit. The previous public search signature is preserved.

Validation: 33 focused tests (UsvmPropertySearcherTest and SymbolicInputReplayTest), strict main/test Detekt in both modules, and diff checks. Tests cover the final operation crossing the search cutoff, cache reuse, unknown receipts, conflicting predictions, disabled capture and original fault confirmation. The initial Detekt method-length finding was corrected and the final source was checked again.

Based on #615. This is a native-validation fix; real-code readiness will be checked separately on a fresh assembled build. No comparative performance claim is made.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant