Problem

Project-wide test coverage is 90.91%, but several modules are significantly below that average. The Codecov project threshold is already catching small drops on PRs, and these low-coverage files are the primary drag.

Files below 85% coverage

Files in the 85-88% range (lower priority)

Notes

• vera/browser/emit.py (0%) is the browser bundle emitter — it writes files to disk and is only exercised by vera compile --target browser, which the test suite doesn't call directly. Likely needs a targeted integration test or pragma: no cover if it's inherently side-effectful.
• vera/wasm/markdown.py (46%) is the WASM host binding for Markdown operations — many branches handle edge cases in the Markdown AST that existing conformance tests don't exercise.
• vera/cli.py (68%) has many subcommands and error paths that aren't tested. The CLI tests exist but don't cover all flags and error conditions.
• vera/wasm/inference.py (75%) and vera/wasm/operators.py (78%) have many type-specific branches in the WASM codegen that aren't hit by current test programs.
• vera/checker/resolution.py and vera/checker/control.py likely have uncovered error-reporting branches.

Approach

For each file, assess whether the uncovered code is:

1. Testable — write targeted unit tests
2. Defensive/unreachable — add pragma: no cover with rationale
3. Dead code — remove it

Goal: bring all files above 85%, overall project coverage above 91%.

Codecov dashboard

https://app.codecov.io/gh/aallan/vera?displayType=list