test(platformctl): add provenance adversarial coverage #641

Merged
pdurlej merged 1 commit from codex/m06-provenance-adversarial-tests into main 2026-05-30 15:34:53 +02:00
Collaborator

Canary status: missing — fire canary 3+3 manually before merge

Canary Context Pack

Product story

The apply pipeline should fail closed under hostile provenance inputs, not only under happy-path malformed values.

What changed

Added adversarial coverage for corrupted plan JSON, type-confused plan payloads, forged clean env state, type-confused source SHA values, and fake manifest git roots.

Why it changed

Issue #194 closes the redaction/provenance hardening segment after #199, #200, #206, #192, and #193. These tests document the threat model before moving to plan-state/runtime-safety tasks.

Files touched

  • control-plane/platformctl/apply.py
  • control-plane/platformctl/tests/test_apply_phase3.py
  • control-plane/platformctl/tests/test_plan_phase3.py

Relevant context

  • Issue #194: PROVENANCE-ADVERSARIAL-TESTS-01
  • #199/#200/#206 redaction chain merged
  • #192/#193 provenance primitives merged

Runtime evidence

No runtime mutation. Local validation only.

Known constraints

This is intentionally test-heavy. The only code behavior change is fail-closed handling for invalid/non-object plan JSON before approval lookup.

Explicit out-of-scope

  • No plan-state changes (#196/#197 next)
  • No runtime apply or service restart
  • No destructive operations

Requested decision

Approve merge if tests and Patchwarden checks are green.

Merge blockers

  • Corrupted/type-confused plan JSON reaches approval/runtime gates
  • Env-var provenance forgery can mark a dirty tree clean
  • Existing plan/apply tests regress

Spec sources read

  • Forgejo issue #194
  • docs/forgejo-agent-operations.md
  • control-plane/platformctl/apply.py
  • control-plane/platformctl/plan.py
  • control-plane/platformctl/tests/test_apply_phase3.py
  • control-plane/platformctl/tests/test_plan_phase3.py
  • control-plane/platformctl/tests/test_apply_env_file.py

Validation

  • PYTHONPATH=control-plane control-plane/.venv/bin/python -m pytest control-plane/platformctl/tests/test_plan_phase3.py control-plane/platformctl/tests/test_apply_phase3.py control-plane/platformctl/tests/test_apply_env_file.py — 101 passed
  • PYTHONPATH=control-plane control-plane/.venv/bin/python -m platformctl.cli validate all --json — passed

Closes #194

Canary status: missing — fire canary 3+3 manually before merge ## Canary Context Pack ### Product story The apply pipeline should fail closed under hostile provenance inputs, not only under happy-path malformed values. ### What changed Added adversarial coverage for corrupted plan JSON, type-confused plan payloads, forged clean env state, type-confused source SHA values, and fake manifest git roots. ### Why it changed Issue #194 closes the redaction/provenance hardening segment after #199, #200, #206, #192, and #193. These tests document the threat model before moving to plan-state/runtime-safety tasks. ### Files touched - `control-plane/platformctl/apply.py` - `control-plane/platformctl/tests/test_apply_phase3.py` - `control-plane/platformctl/tests/test_plan_phase3.py` ### Relevant context - Issue #194: PROVENANCE-ADVERSARIAL-TESTS-01 - #199/#200/#206 redaction chain merged - #192/#193 provenance primitives merged ### Runtime evidence No runtime mutation. Local validation only. ### Known constraints This is intentionally test-heavy. The only code behavior change is fail-closed handling for invalid/non-object plan JSON before approval lookup. ### Explicit out-of-scope - No plan-state changes (#196/#197 next) - No runtime apply or service restart - No destructive operations ### Requested decision Approve merge if tests and Patchwarden checks are green. ### Merge blockers - Corrupted/type-confused plan JSON reaches approval/runtime gates - Env-var provenance forgery can mark a dirty tree clean - Existing plan/apply tests regress ## Spec sources read - Forgejo issue #194 - `docs/forgejo-agent-operations.md` - `control-plane/platformctl/apply.py` - `control-plane/platformctl/plan.py` - `control-plane/platformctl/tests/test_apply_phase3.py` - `control-plane/platformctl/tests/test_plan_phase3.py` - `control-plane/platformctl/tests/test_apply_env_file.py` ## Validation - `PYTHONPATH=control-plane control-plane/.venv/bin/python -m pytest control-plane/platformctl/tests/test_plan_phase3.py control-plane/platformctl/tests/test_apply_phase3.py control-plane/platformctl/tests/test_apply_env_file.py` — 101 passed - `PYTHONPATH=control-plane control-plane/.venv/bin/python -m platformctl.cli validate all --json` — passed Closes #194
test(platformctl): add provenance adversarial coverage
All checks were successful
platformctl plan / auto-apply scope (pull_request) Successful in 27s
python-ci / Python 3.11 (pull_request) Successful in 46s
python-ci / Python 3.12 (pull_request) Successful in 45s
python-ci / Python 3.13 (pull_request) Successful in 45s
base-is-main / guard (pull_request) Successful in 1s
patchwarden-pr-sanity / collect-diff (pull_request) Successful in 6s
canary-required / canary (pull_request) Successful in 15s
patchwarden-client-dry-run / dry-run (pull_request) Successful in 23s
canary-required / collect-diff (pull_request) Successful in 5s
patchwarden-client-dry-run / collect-diff (pull_request) Successful in 5s
pyfallow / Pyfallow gate (control-plane) (pull_request) Successful in 24s
patchwarden-pr-sanity / sanity (pull_request) Successful in 2m1s
55f33d3f5e
Author
Collaborator

Patchwarden PR sanity

  • Status: advisory_findings
  • PR: 641
  • Commit: 55f33d3f5ee9157cee948173d4b168e0be5a0bb8
  • Security-sensitive label: present
  • Authority: advisory model review plus deterministic blockers only
  • 3+3 canary: still alive; this does not replace it

Deterministic findings

  • info sensitive-path-touched Sensitive path touched — control-plane/platformctl/apply.py
    • Evidence: control-plane/platformctl/apply.py
    • Next: Route through the existing 3+3/risk-tier process; model review remains advisory.

Model reviewers

global-glm / glm-5.1:cloud

  • Status: ok
  • Verdict: OK
  • Findings: none

global-deepseek / deepseek-v4-pro:cloud

  • Status: ok
  • Verdict: OK
  • Findings: none

redteam / kimi-k2.6:cloud

  • Status: ok

  • Verdict: NOT_OK

  • high UnicodeDecodeError bypasses fail-closed plan parsing

    • Evidence: control-plane/platformctl/apply.py: the new try/except wraps plan = json.loads(plan_path.read_text())but only catchesjson.JSONDecodeError. If the plan file contains non-UTF-8 bytes, read_text()raisesUnicodeDecodeErrorbeforejs`
    • Next: Catch UnicodeDecodeError (and ideally OSError) alongside json.JSONDecodeError, or read bytes and decode explicitly, ensuring any plan-read failure returns the same structured error dict before the approval gate.

Policy notes

  • GLM 5.1 + DeepSeek V4 Pro are the operator-required model mix for this bot.
  • Optional red-team model is enabled only when PLATFORMCTL_PR_SANITY_REDTEAM_MODEL is configured.
  • Auto-merge is not enabled here.
<!-- patchwarden-pr-sanity:pdurlej/platform:PR-641 --> # Patchwarden PR sanity - Status: `advisory_findings` - PR: `641` - Commit: `55f33d3f5ee9157cee948173d4b168e0be5a0bb8` - Security-sensitive label: `present` - Authority: advisory model review plus deterministic blockers only - 3+3 canary: still alive; this does not replace it ## Deterministic findings - **`info` `sensitive-path-touched`** Sensitive path touched — `control-plane/platformctl/apply.py` - Evidence: `control-plane/platformctl/apply.py` - Next: Route through the existing 3+3/risk-tier process; model review remains advisory. ## Model reviewers ### `global-glm` / `glm-5.1:cloud` - Status: `ok` - Verdict: `OK` - Findings: none ### `global-deepseek` / `deepseek-v4-pro:cloud` - Status: `ok` - Verdict: `OK` - Findings: none ### `redteam` / `kimi-k2.6:cloud` - Status: `ok` - Verdict: `NOT_OK` - **`high`** UnicodeDecodeError bypasses fail-closed plan parsing - Evidence: `control-plane/platformctl/apply.py: the new try/except wraps `plan = json.loads(plan_path.read_text())` but only catches `json.JSONDecodeError`. If the plan file contains non-UTF-8 bytes, `read_text()` raises `UnicodeDecodeError` before `js` - Next: Catch `UnicodeDecodeError` (and ideally `OSError`) alongside `json.JSONDecodeError`, or read bytes and decode explicitly, ensuring any plan-read failure returns the same structured error dict before the approval gate. ## Policy notes - GLM 5.1 + DeepSeek V4 Pro are the operator-required model mix for this bot. - Optional red-team model is enabled only when `PLATFORMCTL_PR_SANITY_REDTEAM_MODEL` is configured. - Auto-merge is not enabled here.
pdurlej approved these changes 2026-05-30 15:34:52 +02:00
pdurlej left a comment

Owner-authorized admin approval after green checks. Scope: #194 adds hostile provenance input tests and fail-closed invalid plan JSON handling; no runtime mutation and no secrets printed.

Owner-authorized admin approval after green checks. Scope: #194 adds hostile provenance input tests and fail-closed invalid plan JSON handling; no runtime mutation and no secrets printed.
pdurlej referenced this pull request from a commit 2026-05-30 15:34:55 +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!641
No description provided.