consolidated Python harness reintroduces mandatory Uniswap skips

[BitHighlander]

Summary

The consolidated Python harness reintroduced an emulator-wide setUp() skip for all three Uniswap V2 liquidity signing vectors. This regresses the prior explicit fix in BitHighlander/python-keepkey#32 (811520e8 / merge 9f3b1767) that removed those skips after they exposed and verified a real firmware recipient-confirmation defect.

At the same time, the 7.16 report catalog:

• describes E17-E19 as "PENDING" because of that skip;
• lists the module in MUST_RUN_MODULES from 7.16.0 and claims Uniswap liquidity approval path has no automated coverage anywhere: the only integration tests skip unconditionally on the emulator and the native tests only ever assert refusal #516 requires all three to execute.

A clean 7.16 Docker run therefore reports all three as skipped-but-required after 675 other tests pass.

Impact

• The branch claims to close Uniswap liquidity approval path has no automated coverage anywhere: the only integration tests skip unconditionally on the emulator and the native tests only ever assert refusal #516 while its only end-to-end liquidity vectors never execute.
• Catalog prose and validation policy contradict each other.
• The skip hides future regressions in approval, add-liquidity, and remove-liquidity signing paths on the only platform CI exercises.

Required remediation

• Remove the emulator-wide skip again.
• Run all three vectors against the exact companion firmware and verify their fixed signatures.
• Replace the pending catalog text with the actual verified behavior and retain their confirmation frames.
• Keep the module mandatory for full 7.16 builds.

[BitHighlander]

Fixed in BitHighlander/python-keepkey#59 at b9ab241c, pinned by firmware PR #587 at 7d3cf278e.

The emulator-wide skip is removed again. Against exact companion firmware 54b169a70, all three fixed-signature vectors pass in 11.28 seconds. Their 16 distinct retained screens were visually audited and catalogued exactly: approval 3, add-liquidity 7, remove-liquidity 6. Reconciling those results into the preserved full corpus makes the complete screenshot audit pass. Fresh clean-volume and remote gates are running before closure.

[BitHighlander]

Follow-up compatibility audit found that restoring all three emulator tests exposed one real RC18 boundary: approval and add-liquidity pass on RC18, but its external-recipient remove-liquidity flow intentionally cancels. The test now gates only that one post-RC18 behavior at firmware 7.16.0 while keeping all three flows mandatory for the alpha/full report.

Fixes pushed:

• python-keepkey 4641244f57af0967e7b97ca1aeb149b20aba54d3
• firmware pin 896743d95

Fresh RC18, current-firmware, and CircleCI gates are running against those heads.