docs(w6d): record Patchwarden policy bundle dogfood #496

Merged
Iskra merged 1 commit from codex/patchwarden-dogfood-note into main 2026-05-26 01:46:13 +02:00
Collaborator

Canary status: missing — boring state/cycle docs-only calibration PR.

Canary Context Pack

Product story

W6d needs boring calibration PRs after #495 so we can measure whether the Patchwarden-backed lane behaves usefully on safe docs/status changes.

What changed

Adds #495 to the W6d proven-runs table as the manual workflow/governance PR that wired platform dry-run to Patchwarden platform.v0 policy bundle.

Why it changed

This PR is intentionally tiny and boring so the lane can dogfood safe state/cycle changes without touching workflow, runtime, secrets, or control-plane code.

Files touched

  • state/cycle/W6d-autonomous-merge-pilot.md

Relevant context

  • #495 merged manually because it touched .forgejo/workflows/**.
  • This PR only records that outcome in the existing W6d cycle note.

Runtime evidence

No runtime mutation.

Known constraints

This PR should be eligible for the narrow docs/status lane if Forgejo checks and Patchwarden client dry-run are healthy.

Explicit out-of-scope

No policy changes, no workflow changes, no automerge code changes.

Requested decision

Approve/merge if checks are green. This is a calibration/dogfood PR.

Merge blockers

Any non-docs/status classification, stale branch, failing required check, or Patchwarden sanity blocker.

Spec sources read

  • state/cycle/W6d-autonomous-merge-pilot.md — target status note
  • .forgejo/workflows/patchwarden-client-dry-run.yml — source for #495 behavior

Tests

  • git diff --check
  • python3 control-plane/platformctl/ci/lint_workflows.py --workflows .forgejo/workflows --markdown /tmp/platform-dogfood-workflow-lint.md --json /tmp/platform-dogfood-workflow-lint.json → passed, 0 findings
Canary status: missing — boring state/cycle docs-only calibration PR. ## Canary Context Pack ### Product story W6d needs boring calibration PRs after #495 so we can measure whether the Patchwarden-backed lane behaves usefully on safe docs/status changes. ### What changed Adds #495 to the W6d proven-runs table as the manual workflow/governance PR that wired platform dry-run to Patchwarden `platform.v0` policy bundle. ### Why it changed This PR is intentionally tiny and boring so the lane can dogfood safe state/cycle changes without touching workflow, runtime, secrets, or control-plane code. ### Files touched - `state/cycle/W6d-autonomous-merge-pilot.md` ### Relevant context - #495 merged manually because it touched `.forgejo/workflows/**`. - This PR only records that outcome in the existing W6d cycle note. ### Runtime evidence No runtime mutation. ### Known constraints This PR should be eligible for the narrow docs/status lane if Forgejo checks and Patchwarden client dry-run are healthy. ### Explicit out-of-scope No policy changes, no workflow changes, no automerge code changes. ### Requested decision Approve/merge if checks are green. This is a calibration/dogfood PR. ### Merge blockers Any non-docs/status classification, stale branch, failing required check, or Patchwarden sanity blocker. ## Spec sources read - `state/cycle/W6d-autonomous-merge-pilot.md` — target status note - `.forgejo/workflows/patchwarden-client-dry-run.yml` — source for #495 behavior ## Tests - `git diff --check` - `python3 control-plane/platformctl/ci/lint_workflows.py --workflows .forgejo/workflows --markdown /tmp/platform-dogfood-workflow-lint.md --json /tmp/platform-dogfood-workflow-lint.json` → passed, 0 findings
docs(w6d): record Patchwarden policy bundle dogfood
All checks were successful
canary-required / collect-diff (pull_request) Successful in 4s
patchwarden-client-dry-run / collect-diff (pull_request) Successful in 4s
canary-required / canary (pull_request) Has been skipped
patchwarden-client-dry-run / dry-run (pull_request) Successful in 19s
base-is-main / guard (pull_request) Successful in 1s
patchwarden-pr-sanity / collect-diff (pull_request) Successful in 4s
patchwarden-pr-sanity / sanity (pull_request) Successful in 20s
94af9e969b
Iskra approved these changes 2026-05-26 01:46:12 +02:00
Iskra left a comment

Approved by Iskra after W6d Matrix approval and deterministic readiness for the current PR head SHA.

Approved by Iskra after W6d Matrix approval and deterministic readiness for the current PR head SHA.
Iskra merged commit 613a362ff0 into main 2026-05-26 01:46:13 +02:00
Iskra referenced this pull request from a commit 2026-05-26 01:46:14 +02:00
Sign in to join this conversation.
No reviewers
No labels
W6d-automerge-calibration
agent/claude-code
agent/codex
agent/hermes
agent/iskra
agent/ollama
agent/patchwarden
automerge-candidate
class/security-sensitive
cutover-gate
dependency/blocked
dependency/blocks-others
dependency/cross-repo
dependency/needs-confirmation
domain:agents
domain:ci
domain:docs
domain:forgejo
domain:infra
domain:memory
domain:runtime
domain:signal
domain:ux
flow/architecture
flow/blocked
flow/deployed
flow/done
flow/implementation
flow/intake
flow/maintained
flow/observed
flow/ready
flow/refining
flow/retired
flow/review
iterating
judge/codex-candidate
judge/hermes-candidate
judge/low-confidence
judge/needs-refinement
judge/operator-needed
judge/p0
judge/p1
judge/p2
judge/p3
judge/park
judge/patchwarden-candidate
judge/stale-priority
kind/adr
kind/bug
kind/chore
kind/feature
kind/infra
kind/ops
kind/refactor
kind/research
large-impact
merge/auto
merge/manual
merge/manual-dependency-conflict
merge/manual-failing-tests
merge/manual-merge-conflict
merge/manual-missing-review
merge/manual-operator-preference
merge/manual-red-zone
merge/manual-security-sensitive
merge/manual-unclear-scope
merge/manual-unknown
meta
mode:operator-only
mode:patchwarden-iskra-approved
mode:safe-auto
needs-operator-decision
needs-triage
not-ready
observed/erroring
observed/needs-followup
observed/pending
observed/retire-candidate
observed/unused
observed/used
operator-emotional
owner-attention
phase/02
phase/03
priority:p0
priority:p1
priority:p2
priority:p3
proposed
ready-for-agent
ready-for-operator
recovery
review:claude-reviewed
review:codex-reviewed
review:dziadek-reviewed
review:needs-human
risk/exposure
risk/process
risk/product
risk/runtime
safety:external-write
safety:no-prod-mutation
safety:prod-impact
safety:secret-touch
size/large
size/medium
size/small
size/tiny
size/unknown
source/adr
source/agent-generated
source/manual
source/operator-chat
source/voice-note
status:blocked
status:codex-ready
status:merged:pending-evidence
status:needs-evidence
status:operator-needed
status:parked
tier/full
tier/lite
tier/stacked
tier:0-platform-substrate
tier:1-iskra-value-layer
tier:2-tools-products-modules
type:bug
type:chore
type:docs
type:feat
type:policy
type:research
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pdurlej/platform!496
No description provided.