Problem
The `pytest11` entry point in `pyproject.toml` registers `sqlproof.pytest_plugin` so tests can use `@sqlproof(...)` and `proof.check(...)`, but the CLI flags (e.g. `--sqlproof-seed`, `--sqlproof-runs`), the reporter output format, and the failure-artifact path conventions are still in flux. The pytest plugin module is currently in the coverage `omit` list because its surface keeps changing.
Acceptance
- Decide on the public flag set and document it in `docs/api/check-options`.
- Move `pytest_plugin.py` out of the coverage omit list and add tests using pytest's own plugin testing harness.
- The `sqlproof` CLI script (`pyproject.toml` `[project.scripts]`) acquires real subcommands or is removed.
Problem
The `pytest11` entry point in `pyproject.toml` registers `sqlproof.pytest_plugin` so tests can use `@sqlproof(...)` and `proof.check(...)`, but the CLI flags (e.g. `--sqlproof-seed`, `--sqlproof-runs`), the reporter output format, and the failure-artifact path conventions are still in flux. The pytest plugin module is currently in the coverage `omit` list because its surface keeps changing.
Acceptance