test: add Qiskit oracle semantics reports - #9
Merged
Merged
Conversation
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
1 participant
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.
Summary
Adds an explicit Qiskit oracle semantic report for the v0.2 gate-model boundary.
The report compares direct
BoolExpr.evaluatetruth tables with symbolic oracle truth tables, records reversibility and cleanup checks, tracks logical variables, ancilla count, cleanup gate count, gate count, depth estimate, truth-table hash, true rows, and optional localQuantumCircuitsummary metadata when Qiskit is available.The optional Qiskit path remains a local export boundary: the circuit summary is synthesized from the verified local truth table and records
backend_execution: false.Closes #3.
Validation
Local result: focused tests passed;
bash scripts/run_audit.shpassed with58 passedin pytest and Lean build successful.Boundary
This PR does not use IBM Runtime, backend queues, hardware execution, noise modeling, transpilation benchmarking, or quantum advantage claims. The semantic authority remains the local truth table.