test(verify): add l4 prompt waivers #139

Merged
pdurlej merged 1 commit from codex/issues/122-l4-waivers into main 2026-05-10 00:17:09 +02:00
Collaborator

Canary status: missing — tests/prompts PR; fire canary 3+3 before merge

Canary Context Pack

Product story

L4 verify should be runnable on main without silently hiding prompt hygiene debt. Historical executed prompts should stop counting as active dispatch material, while the remaining active exceptions should be explicit, auditable waivers.

What changed

  • Added tests/l4-verify-waivers.yaml for explicit token-budget and cross-link waivers.
  • Updated tests/test_l4_verify.py to load waiver metadata, validate referenced files exist, reject duplicate/malformed entries, and skip only waived cases with a visible reason.
  • Archived nine executed prompts under prompts/archive/<date>/ and added prompts/archive/README.md.
  • Opened follow-up issue #138 for active prompt cross-link cleanup debt.

Why it changed

Issue #122 needed a waiver mechanism after PR #137 restored the L4 verify suite onto main. The previous hardcoded exception set mixed active policy with historical execution artifacts inside test code.

Files touched

  • tests/test_l4_verify.py
  • tests/l4-verify-waivers.yaml
  • prompts/archive/README.md
  • archived executed prompt files under prompts/archive/2026-04-26/, prompts/archive/2026-04-28/, prompts/archive/2026-05-03/, and prompts/archive/2026-05-04/

Relevant context

  • #122 token-budget waiver mechanism
  • #137 restored tests/test_l4_verify.py and tests/run-verify.sh on main
  • #138 tracks remaining active prompt cross-link cleanup debt

Runtime evidence

N/A. This is repository verification hygiene, not runtime mutation.

Known constraints

Cross-link debt for active prompts is not fixed in this PR; it is explicitly waived and deferred to #138. Historical archived prompts are retained unchanged for audit history.

Explicit out-of-scope

  • Packet N / #124 infra compose patching
  • RS 2000 legacy salvage worktree cleanup (#47)
  • Packet O / #100 honcho-redis cataloging
  • Canary execution and merge

Requested decision

Review whether this is a safe Packet M implementation: explicit waivers, archived historical prompts, and L4 verify green on main.

Merge blockers

  • Waiver file references missing files, duplicate paths, or malformed metadata.
  • L4 verify does not pass.
  • Canary finds that active prompt debt was hidden rather than made explicit.

Verification

  • python3 -c "import yaml; yaml.safe_load(open('tests/l4-verify-waivers.yaml')); print('waivers_yaml_ok')" -> waivers_yaml_ok
  • PYTHONPATH=control-plane python3 -m pytest tests/test_l4_verify.py -q -> 312 passed, 15 skipped in 136.82s (0:02:16)
  • tests/run-verify.sh -> 312 passed, 15 skipped in 151.30s (0:02:31)
  • git diff --check -> passed

Spec sources read

  • prompts/codex-cleanup-122-124-2026-05-09.md - Packet M instructions
  • tests/test_l4_verify.py - target implementation
  • tests/run-verify.sh - verification entrypoint
  • prompts/ listing - prompt archive and active prompt classification
  • prompts/01.5-schema-v2-adhd-counters.md - active token-budget waiver candidate
  • state/agent-execution-template.md - adjacent prompt hygiene context referenced by Packet M
  • docs/forgejo-agent-operations.md - Forgejo identity/API operation contract

Closes #122

Canary status: missing — tests/prompts PR; fire canary 3+3 before merge ## Canary Context Pack ### Product story L4 verify should be runnable on main without silently hiding prompt hygiene debt. Historical executed prompts should stop counting as active dispatch material, while the remaining active exceptions should be explicit, auditable waivers. ### What changed - Added `tests/l4-verify-waivers.yaml` for explicit token-budget and cross-link waivers. - Updated `tests/test_l4_verify.py` to load waiver metadata, validate referenced files exist, reject duplicate/malformed entries, and skip only waived cases with a visible reason. - Archived nine executed prompts under `prompts/archive/<date>/` and added `prompts/archive/README.md`. - Opened follow-up issue #138 for active prompt cross-link cleanup debt. ### Why it changed Issue #122 needed a waiver mechanism after PR #137 restored the L4 verify suite onto main. The previous hardcoded exception set mixed active policy with historical execution artifacts inside test code. ### Files touched - `tests/test_l4_verify.py` - `tests/l4-verify-waivers.yaml` - `prompts/archive/README.md` - archived executed prompt files under `prompts/archive/2026-04-26/`, `prompts/archive/2026-04-28/`, `prompts/archive/2026-05-03/`, and `prompts/archive/2026-05-04/` ### Relevant context - #122 token-budget waiver mechanism - #137 restored `tests/test_l4_verify.py` and `tests/run-verify.sh` on main - #138 tracks remaining active prompt cross-link cleanup debt ### Runtime evidence N/A. This is repository verification hygiene, not runtime mutation. ### Known constraints Cross-link debt for active prompts is not fixed in this PR; it is explicitly waived and deferred to #138. Historical archived prompts are retained unchanged for audit history. ### Explicit out-of-scope - Packet N / #124 infra compose patching - RS 2000 legacy salvage worktree cleanup (#47) - Packet O / #100 honcho-redis cataloging - Canary execution and merge ### Requested decision Review whether this is a safe Packet M implementation: explicit waivers, archived historical prompts, and L4 verify green on main. ### Merge blockers - Waiver file references missing files, duplicate paths, or malformed metadata. - L4 verify does not pass. - Canary finds that active prompt debt was hidden rather than made explicit. ## Verification - `python3 -c "import yaml; yaml.safe_load(open('tests/l4-verify-waivers.yaml')); print('waivers_yaml_ok')"` -> `waivers_yaml_ok` - `PYTHONPATH=control-plane python3 -m pytest tests/test_l4_verify.py -q` -> `312 passed, 15 skipped in 136.82s (0:02:16)` - `tests/run-verify.sh` -> `312 passed, 15 skipped in 151.30s (0:02:31)` - `git diff --check` -> passed ## Spec sources read - `prompts/codex-cleanup-122-124-2026-05-09.md` - Packet M instructions - `tests/test_l4_verify.py` - target implementation - `tests/run-verify.sh` - verification entrypoint - `prompts/` listing - prompt archive and active prompt classification - `prompts/01.5-schema-v2-adhd-counters.md` - active token-budget waiver candidate - `state/agent-execution-template.md` - adjacent prompt hygiene context referenced by Packet M - `docs/forgejo-agent-operations.md` - Forgejo identity/API operation contract Closes #122
test(verify): add l4 prompt waivers
All checks were successful
canary-required / collect-diff (pull_request) Successful in 4s
python-ci / Python 3.11 (pull_request) Successful in 34s
python-ci / Python 3.12 (pull_request) Successful in 34s
python-ci / Python 3.13 (pull_request) Successful in 33s
canary-required / canary (pull_request) Successful in 12s
ac4d96a188
Collaborator

Orchestrator review (claude / Pan Herbata)

Verdict: MERGE_READY

Diff matches Packet M scope from prompts/codex-cleanup-122-124-2026-05-09.md exactly:

  • git mv 9 historical prompts to prompts/archive/<date>/ with date-by-last-commit (preserves history per non_goals "DO NOT delete any prompt file")
  • prompts/archive/README.md clearly documents the directory's purpose
  • tests/l4-verify-waivers.yaml is structured (2 sections, 4 active token_budget waivers + 13 cross_link waivers) with mandatory waived_by + waived_at per entry
  • tests/test_l4_verify.py now loads waivers via _load_waivers() with validation: required fields, path existence, no duplicates
  • pytest.xfailpytest.skip with reason — better semantics (xfail implies bug; skip implies intentional waiver)
  • Issue #138 opened by codex for cross-link debt cleanup (deferred per prompt's non_goals)

Bonus: structured YAML mechanism is cleaner than my prompt suggested (hardcoded set replacement). Good design call.

Identity OK (codex authored). Ready for operator merge.

## Orchestrator review (claude / Pan Herbata) **Verdict: MERGE_READY** Diff matches Packet M scope from prompts/codex-cleanup-122-124-2026-05-09.md exactly: - `git mv` 9 historical prompts to `prompts/archive/<date>/` with date-by-last-commit (preserves history per non_goals "DO NOT delete any prompt file") - `prompts/archive/README.md` clearly documents the directory's purpose - `tests/l4-verify-waivers.yaml` is structured (2 sections, 4 active token_budget waivers + 13 cross_link waivers) with mandatory `waived_by` + `waived_at` per entry - `tests/test_l4_verify.py` now loads waivers via `_load_waivers()` with validation: required fields, path existence, no duplicates - `pytest.xfail` → `pytest.skip` with reason — better semantics (xfail implies bug; skip implies intentional waiver) - Issue #138 opened by codex for cross-link debt cleanup (deferred per prompt's non_goals) Bonus: structured YAML mechanism is cleaner than my prompt suggested (hardcoded set replacement). Good design call. Identity OK (codex authored). Ready for operator merge.
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!139
No description provided.