feat(feedback): add post-merge feedback contract #156

Merged

pdurlej merged 1 commit from codex/post-merge-feedback into main

2026-06-23 22:57:44 +02:00

codex commented

2026-06-23 22:55:05 +02:00

Collaborator

Summary

Closes #147.

Adds a read-only patchwarden post-merge-feedback-check contract for the June 2026 analytics feedback loop. The command consumes a passing contract-pr result, an external merge outcome, and optional post-merge signals, then emits a head-bound patchwarden.post_merge_feedback.v1 artifact with one of:

recorded
follow_up_needed
trust_signal
blocked

The contract keeps Patchwarden inside its policy/planner boundary: no issue creation, no job dispatch, no trust-state writes, no approvals, no merges, and all external write fields stay false.

What changed

New src/patchwarden/post_merge_feedback.py evaluator and CLI command.
New public schema and example under spec/schemas/.
New external handoff registry entry for analytics/issue/job/trust-state writers.
Updated patchwarden status, docs/status.html, STATUS, architecture, PR passage contracts, and June vision docs.
Tests for clean merge recording, follow-up candidates, trust signals, stale SHA fail-closed behavior, CLI errors, schema contracts, handoff registry, and status drift.

Verification

PYTHONPATH=src:. python3 -m unittest discover -s tests — 656 tests OK
git diff --check — clean

Boundaries

Read-only only.
Exact-head binding against the passing Contract PR head.
External controllers must recheck live state before persisting analytics, creating issues/jobs, or applying trust-state updates.

## Summary Closes #147. Adds a read-only `patchwarden post-merge-feedback-check` contract for the June 2026 analytics feedback loop. The command consumes a passing `contract-pr` result, an external merge outcome, and optional post-merge signals, then emits a head-bound `patchwarden.post_merge_feedback.v1` artifact with one of: - `recorded` - `follow_up_needed` - `trust_signal` - `blocked` The contract keeps Patchwarden inside its policy/planner boundary: no issue creation, no job dispatch, no trust-state writes, no approvals, no merges, and all external write fields stay false. ## What changed - New `src/patchwarden/post_merge_feedback.py` evaluator and CLI command. - New public schema and example under `spec/schemas/`. - New external handoff registry entry for analytics/issue/job/trust-state writers. - Updated `patchwarden status`, `docs/status.html`, STATUS, architecture, PR passage contracts, and June vision docs. - Tests for clean merge recording, follow-up candidates, trust signals, stale SHA fail-closed behavior, CLI errors, schema contracts, handoff registry, and status drift. ## Verification - `PYTHONPATH=src:. python3 -m unittest discover -s tests` — 656 tests OK - `git diff --check` — clean ## Boundaries - Read-only only. - Exact-head binding against the passing Contract PR head. - External controllers must recheck live state before persisting analytics, creating issues/jobs, or applying trust-state updates.

codex added the

labels

2026-06-23 22:55:05 +02:00

codex added 1 commit

2026-06-23 22:55:05 +02:00

feat(feedback): add post-merge feedback contract

fallow-py / fallow-py-advisory (pull_request) Successful in 15s

Details

504cdc2df0

codex commented

2026-06-23 22:57:06 +02:00

Author

Collaborator

Patchwarden pre-merge audit for #156:

Local verification: PYTHONPATH=src:. python3 -m unittest discover -s tests -> 656 tests OK.
Whitespace: git diff --check -> clean.
Forgejo head status for 504cdc2df04b0838cbe90b01e85d40e1cf136118: fallow-py / fallow-py-advisory (pull_request) -> success.
contract-pr dry-run with metadata-file returned policy_governance / governance_tier_path because this slice intentionally changes Patchwarden governance surfaces (src/, tests/, spec/, status/docs). This is the expected operator-owned class, not a failing check in the implementation.

Scope is aligned with #147 and the June 2026 Patchwarden mission: read-only post-merge analytics feedback contract; no issue/job/trust-state writes, no approvals, no merges from Patchwarden itself.

Patchwarden pre-merge audit for #156: - Local verification: `PYTHONPATH=src:. python3 -m unittest discover -s tests` -> 656 tests OK. - Whitespace: `git diff --check` -> clean. - Forgejo head status for `504cdc2df04b0838cbe90b01e85d40e1cf136118`: `fallow-py / fallow-py-advisory (pull_request)` -> success. - `contract-pr` dry-run with metadata-file returned `policy_governance` / `governance_tier_path` because this slice intentionally changes Patchwarden governance surfaces (`src/`, `tests/`, `spec/`, status/docs). This is the expected operator-owned class, not a failing check in the implementation. Scope is aligned with #147 and the June 2026 Patchwarden mission: read-only post-merge analytics feedback contract; no issue/job/trust-state writes, no approvals, no merges from Patchwarden itself.