Skip to content

[TS PBT] Project properties and search violations with USVM - #387

Merged
CaelmBleidd merged 11 commits into
mainfrom
caelmbleidd/issues-351-352-usvm-property-search
Oct 13, 2026
Merged

CaelmBleidd merged 11 commits into
mainfrom
caelmbleidd/issues-351-352-usvm-property-search

Conversation

@CaelmBleidd

@CaelmBleidd CaelmBleidd commented Sep 8, 2026 •

Copy link
Copy Markdown
Member

Project declared PBT domains into USVM and search mapped predicates/preconditions for violations. Independent branch against current main; preserves source constructor constraints and catch routing.

Projection now supports bounded symbolic UTF-16 string contents, nested arrays and optional reference/collection domains. Array regions retain their immediate component type through reads and writes. Witnesses use the final solver model with initial input memory, preserving nested and dynamic payloads before predicate mutation. Configured string/collection bounds are checked before allocation and capped by engine capacity. Reachable unsupported paths retain their reasons and any supported sibling witness.

Preconditions execute before the predicate and keep rejection, escaping exception and non-boolean results distinct. Entry-state configuration and precondition completion are isolated from ordinary interpreter dispatch; runtime/SDK constructor guards remain in place.

Validation: 36 focused USVM projection/search tests, 13 FastCheck contract/conformance tests, and FastCheck backend tests passed locally; usvm-ts and usvm-ts-pbt detektMain/detektTest passed. Regression cases cover nested/optional array mutations, string-array input snapshots, lone surrogates, supplementary characters, configured bounds, catches and mixed unsupported paths. Fresh CI on the published head remains the broader gate.

Review focus: source parameter constraints before configuration, component types versus storage descriptors, snapshot/model selection, UTF-16 bounds and explicit incomplete outcomes. Local witness checks do not establish lone-surrogate JSON wire fidelity; that codec is a separate follow-up. Asynchronous properties and unsupported engine paths remain explicitly classified.

@CaelmBleidd
CaelmBleidd force-pushed the caelmbleidd/issues-351-352-usvm-property-search branch from 2d9b65a to 0e2dcb1 Compare September 17, 2026 20:31
@CaelmBleidd
CaelmBleidd force-pushed the caelmbleidd/issues-351-352-usvm-property-search branch 2 times, most recently from be966ff to 1beacb7 Compare September 17, 2026 21:05
@CaelmBleidd
CaelmBleidd force-pushed the caelmbleidd/issue-384-property-contract branch from 1a46c28 to b2f7786 Compare September 19, 2026 09:53
@CaelmBleidd
CaelmBleidd force-pushed the caelmbleidd/issue-384-property-contract branch from 0ecfda6 to ee88851 Compare September 30, 2026 12:41
@CaelmBleidd
CaelmBleidd force-pushed the caelmbleidd/issues-351-352-usvm-property-search branch 2 times, most recently from 9dfbf85 to 2ac0342 Compare September 30, 2026 16:04
Base automatically changed from caelmbleidd/issue-384-property-contract to main September 30, 2026 16:11
@CaelmBleidd
CaelmBleidd force-pushed the caelmbleidd/issues-351-352-usvm-property-search branch from 2ac0342 to 6f4f690 Compare September 30, 2026 16:15
@CaelmBleidd
CaelmBleidd force-pushed the caelmbleidd/issues-351-352-usvm-property-search branch 2 times, most recently from dff981d to fa3b0fe Compare October 13, 2026 21:06
@CaelmBleidd
CaelmBleidd force-pushed the caelmbleidd/issues-351-352-usvm-property-search branch from fa3b0fe to ed24ca9 Compare October 13, 2026 21:09
@CaelmBleidd
CaelmBleidd merged commit 9cb8f1c into main Oct 13, 2026
@CaelmBleidd
CaelmBleidd deleted the caelmbleidd/issues-351-352-usvm-property-search branch October 13, 2026 21:11
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.

2 participants