fix(w6d): allow evidence and prep notes #484

Merged

pdurlej merged 1 commit from codex/w6d-expand-evidence-scope into main

2026-05-25 12:55:24 +02:00

codex commented

2026-05-25 12:45:01 +02:00

Collaborator

Canary status: missing — control-plane W6d policy change; rely on required Forgejo checks before merge and run deeper review if desired

Canary Context Pack

Product story

W6d is now proven for narrow docs/status PRs. To make it useful for daily platform work, it should also handle boring evidence and prep notes that agents produce while keeping cutover/runtime/security policy changes manual.

What changed

Added state/reports/ and state/codex-prep/ to the W6d safe path allowlist.
Kept state/cutover/ outside W6d automerge.
Added tests for the new allowed evidence/prep paths and the cutover negative case.
Updated the W6d pilot note to match the new scope.

Why it changed

The calibrated lane worked, but it was still too narrow for recurring evidence/checkpoint/prep work. This expansion keeps the safe surface boring while reducing operator clicks for metadata-only reports.

Files touched

control-plane/platformctl/ci/automerge_readiness.py
control-plane/platformctl/tests/test_automerge_readiness.py
state/cycle/W6d-autonomous-merge-pilot.md

Relevant context

W6d calibration PRs #479-#483 merged by Iskra.
Existing W6d constraints: automerge-candidate, required checks green, Patchwarden clean, Iskra Matrix approval, formal Forgejo approval, merge by Iskra.

Runtime evidence

None. This is CI/policy code and documentation only. No RS2000 runtime mutation.

Known constraints

This PR itself is not W6d-automergeable because it changes control-plane/ and tests. It needs normal review/merge.

Explicit out-of-scope

No workflow changes, branch protection changes, runtime changes, secrets changes, ADR changes, module/schema changes, or cutover-plan automerge eligibility.

Requested decision

Merge if tests and required checks pass. After merge, use a tiny state/reports/ PR as the first expanded-lane smoke.

Merge blockers

Any failure in test_automerge_readiness.py.
Any path expansion beyond state/reports/ and state/codex-prep/.
Any accidental allowance of state/cutover/ or sensitive paths.

Spec sources read

control-plane/platformctl/ci/automerge_readiness.py — W6d deterministic eligibility checker
control-plane/platformctl/tests/test_automerge_readiness.py — W6d readiness tests
state/cycle/W6d-autonomous-merge-pilot.md — pilot policy note

Tests

PYTHONPATH=control-plane pytest control-plane/platformctl/tests/test_automerge_readiness.py — 12 passed
git diff --check

Canary status: missing — control-plane W6d policy change; rely on required Forgejo checks before merge and run deeper review if desired ## Canary Context Pack ### Product story W6d is now proven for narrow docs/status PRs. To make it useful for daily platform work, it should also handle boring evidence and prep notes that agents produce while keeping cutover/runtime/security policy changes manual. ### What changed - Added `state/reports/` and `state/codex-prep/` to the W6d safe path allowlist. - Kept `state/cutover/` outside W6d automerge. - Added tests for the new allowed evidence/prep paths and the cutover negative case. - Updated the W6d pilot note to match the new scope. ### Why it changed The calibrated lane worked, but it was still too narrow for recurring evidence/checkpoint/prep work. This expansion keeps the safe surface boring while reducing operator clicks for metadata-only reports. ### Files touched - `control-plane/platformctl/ci/automerge_readiness.py` - `control-plane/platformctl/tests/test_automerge_readiness.py` - `state/cycle/W6d-autonomous-merge-pilot.md` ### Relevant context - W6d calibration PRs #479-#483 merged by `Iskra`. - Existing W6d constraints: `automerge-candidate`, required checks green, Patchwarden clean, Iskra Matrix approval, formal Forgejo approval, merge by `Iskra`. ### Runtime evidence None. This is CI/policy code and documentation only. No RS2000 runtime mutation. ### Known constraints This PR itself is not W6d-automergeable because it changes `control-plane/` and tests. It needs normal review/merge. ### Explicit out-of-scope No workflow changes, branch protection changes, runtime changes, secrets changes, ADR changes, module/schema changes, or cutover-plan automerge eligibility. ### Requested decision Merge if tests and required checks pass. After merge, use a tiny `state/reports/` PR as the first expanded-lane smoke. ### Merge blockers - Any failure in `test_automerge_readiness.py`. - Any path expansion beyond `state/reports/` and `state/codex-prep/`. - Any accidental allowance of `state/cutover/` or sensitive paths. ## Spec sources read - `control-plane/platformctl/ci/automerge_readiness.py` — W6d deterministic eligibility checker - `control-plane/platformctl/tests/test_automerge_readiness.py` — W6d readiness tests - `state/cycle/W6d-autonomous-merge-pilot.md` — pilot policy note ## Tests - `PYTHONPATH=control-plane pytest control-plane/platformctl/tests/test_automerge_readiness.py` — 12 passed - `git diff --check`

codex added 1 commit

2026-05-25 12:45:01 +02:00

fix(w6d): allow evidence and prep notes

base-is-main / guard (pull_request) Successful in 2s

Details

canary-required / collect-diff (pull_request) Successful in 5s

Details

infra-docs-drift / docs-drift (pull_request) Successful in 5s

Details

patchwarden-pr-sanity / collect-diff (pull_request) Successful in 4s

Details

python-ci / Python 3.11 (pull_request) Successful in 44s