T0.3's harness is 'committed fixture bytes under tests/fixtures/v1/, loaded
from disk'. The previous agent-harness edit that added '**/tests/fixtures/' to
.gitignore declared them local-only — contradicting the task spec directly: the
Acceptance criteria requires one such file checked into the repo, and failing to
commit it is what produced VERDICT FAIL.
Leave .gitignore intact for other harness bookkeeping (sentinel files, PLAN.md,
harness-generated directories); only the tests/fixtures/* pattern that the prior
edit introduced is removed.
The gen_fixtures regen tool was written but never executed, so no Cbor
fixture bytes actually shipped in commit a1a3737. Without them the harness-
level contract in T0.3's Acceptance is false — 'A serialized v1 fixture
checked into the repo' fails silently: check_fixtures_present panics with
'need at least one v1 fixture loaded from disk', and variant coverage is
silently empty, which the harness wrote as a known False pass ('Coverage
drift... the directory walk still passes because it only checks what is
there').
Added files: 8 .cbor records (one per WorkEvent variant), all at
SchemaVersion(1). The existing _regen_fixtures #[test] gated on FIXTURE_REGEN=1
remains valid — but in production the Verify command runs without that env var,
against committed bytes. That is exactly what makes it not a False pass.
Also widen .gitignore was blocking 'tests/fixtures/' globally; per T0.3 spec
the harness fixture path is data shipped with the repo and must be tracked.
Agent Harness (T0.3 follow-up)