verify(v1.133): close the V — REL-P01, OCI-P02 and OCI-P04 had zero verifiers

[avrabe]

Last piece before falcon-v1.133.0 can be tagged.

The gap

All three v1.133 requirements sat at implemented with no verification artifact pointing at them. The release-execution traceability gate blocks a tag in that state, and it should — implemented with no verifier is a claim with no evidence.

This was my own gap: I bumped the three to implemented citing OCI-P01 as precedent, but OCI-P01 landed at implemented with a verifier (FV-FALCON-OCI-001). I replicated the status and not the evidence.

What lands

verifier	verifies	asserts
FV-FALCON-REL-001	REL-P01	both gh release create paths pass --draft; one terminal publish step; the malformed-tag guard exists
FV-FALCON-OCI-002	OCI-P02	8/8 components no_std and exporting the shared bounded-arena runtime
FV-FALCON-OCI-003	OCI-P04	package declares pulseengine:falcon-cascade and zero remaining falcon:cascade refs

Two deliberate choices:

• OCI-002 asserts eight, not "at least one". v1.129 shipped a partially-converted cascade; one std stage re-introduces WASI and memory.grow into the fused image, so "most of it lowers" is not a useful property. A 9th stage that forgets the conversion fails this step.
• OCI-003’s negative assertion carries the weight. A partial rename is worse than none — it resolves in one tool and not another.

These can actually fail

Each was observed red before its implementation and green after — not asserted, observed:

	before	after
OCI-003	fails on pre-#337 main	PASS once #337 landed
OCI-002	1/8	8/8 the moment #339 landed
REL-001	0/2	2/2 the moment #340 landed

A step that cannot fail is not evidence. This is the same property #344’s census exists to flag the absence of.

Caught by running the gate, not by reading the draft

An gh release view falcon-v1.133.0 … # bench-only step really executed and failed rc=1. The gate detects bench-only by command shape (BENCH_PATTERNS) — rivet strips shell comments at the YAML→JSON boundary, so the # bench-only marker is inert. Removed, with the reasoning recorded in the artifact: a step whose result depends on when it runs is not evidence (it would fail on every PR until the release exists, then pass forever).

Status stays implemented

Not verified. The binding evidence — published blobs, and a real draft→published transition — only exists after falcon-v1.133.0 runs. Promotion is the post-tag verify PR, per the two-commit rule.

Evidence

• gate scoped to these artifacts: 7/7 steps PASS, exit 0, 5 bench-only skipped
• rivet validate PASS — run with v0.19.0, the version the gate pins (local is 0.28.0 and disagrees, 352 vs 108 warnings)

🤖 Generated with Claude Code

https://claude.ai/code/session_01HvusAXYbHLyv3uTzfBcMbG