chore(v0): add dev extras and fail-closed docs #22

Merged

pdurlej merged 1 commit from codex/patchwarden-dev-extras-fail-closed-docs into main

2026-05-27 11:54:36 +02:00

codex commented

2026-05-26 00:11:38 +02:00

Collaborator

Canary status: missing — Patchwarden repo does not yet have platform canary wiring; rely on local tests for this small v0 hygiene PR.

Canary Context Pack

Product story

Patchwarden should be installable and testable by agents without relying on undeclared extras, and its finding resolver should state its fail-closed behavior plainly.

What changed

Added test and dev optional dependencies with pytest>=8.0.
Added a metadata test that locks those extras in pyproject.toml.
Documented that resolve-findings treats a missing --state-file as fail-closed: findings default to open, high/blocker findings hold, and unknown finding types are manual_only.

Why it changed

Dziadek/DeepSeek review correctly pointed out that extras were missing and that resolver state behavior should be explicit before Patchwarden grows more E2E machinery.

Files touched

README.md
pyproject.toml
tests/test_project_metadata.py

Runtime evidence

No runtime mutation. Repo-only Patchwarden change.

Known constraints

This intentionally does not add webhook mode, Forgejo API client, LLM integration, or policy DSL.

Explicit out-of-scope

Service/webhook runner
Automatic PR comment posting
Policy bundle parser
Reviewer model execution

Requested decision

Merge this as a small v0 hygiene fix.

Merge blockers

Extras do not parse/install.
Test suite fails.
Documentation contradicts resolver behavior.

Spec sources read

pyproject.toml — package metadata and extras.
README.md — public operator-facing status/docs.
src/patchwarden/resolve_findings.py — actual fail-closed behavior.
tests/test_resolve_findings.py — resolver behavior coverage.

Tests

PYTHONPATH=src python3 -m pytest -q → 20 passed
git diff --check origin/main...HEAD → clean
python3 -m pip install -e '.[test]' --dry-run → resolves patchwarden and pytest>=8.0

Canary status: missing — Patchwarden repo does not yet have platform canary wiring; rely on local tests for this small v0 hygiene PR. ## Canary Context Pack ### Product story Patchwarden should be installable and testable by agents without relying on undeclared extras, and its finding resolver should state its fail-closed behavior plainly. ### What changed - Added `test` and `dev` optional dependencies with `pytest>=8.0`. - Added a metadata test that locks those extras in `pyproject.toml`. - Documented that `resolve-findings` treats a missing `--state-file` as fail-closed: findings default to `open`, high/blocker findings hold, and unknown finding types are `manual_only`. ### Why it changed Dziadek/DeepSeek review correctly pointed out that extras were missing and that resolver state behavior should be explicit before Patchwarden grows more E2E machinery. ### Files touched - `README.md` - `pyproject.toml` - `tests/test_project_metadata.py` ### Runtime evidence No runtime mutation. Repo-only Patchwarden change. ### Known constraints This intentionally does not add webhook mode, Forgejo API client, LLM integration, or policy DSL. ### Explicit out-of-scope - Service/webhook runner - Automatic PR comment posting - Policy bundle parser - Reviewer model execution ### Requested decision Merge this as a small v0 hygiene fix. ### Merge blockers - Extras do not parse/install. - Test suite fails. - Documentation contradicts resolver behavior. ## Spec sources read - `pyproject.toml` — package metadata and extras. - `README.md` — public operator-facing status/docs. - `src/patchwarden/resolve_findings.py` — actual fail-closed behavior. - `tests/test_resolve_findings.py` — resolver behavior coverage. ## Tests - `PYTHONPATH=src python3 -m pytest -q` → `20 passed` - `git diff --check origin/main...HEAD` → clean - `python3 -m pip install -e '.[test]' --dry-run` → resolves `patchwarden` and `pytest>=8.0`

codex added 1 commit

2026-05-26 00:11:38 +02:00

chore(v0): add dev extras and fail-closed docs 46e46310a3