Apply property coverage closure across adapters#18
Merged
Conversation
Review SummaryI reviewed the diff and did not identify any actionable in-scope findings to flag.
Variant: convergence-v2 Candidates: 0 | Posted: 0 | Suppressed: 0 0 comments posted · Model: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Extends the property-coverage call-graph closure beyond OCaml to Go, TypeScript, and Swift, and documents the adapter contract in
AGENTS.md.Details
quick.Checkproperty builders as API references, follows returned property functions, and filters helper/predeclared names from coverage evidence.fc.property(...)construction.propertyCheck(...)construction while keeping generated-input evidence tied to closure parameters.Verification
just testNeed help on this PR? Tag
/codesmithwith what you need. Autofix is disabled.