tribunal-vote-invalid-decision.json carried an accidental second violation (literal unexpanded $1 in subject) alongside its named enum violation; indigo reports whichever field Go's randomized map iteration reaches first, so the task-1 expected-error pin was a latent coin flip that passed three CI runs on luck. Fixture now has exactly its one named violation; table re-pinned to the enum message. Found because the base branch failed CI on it while task-4 passed — both failures predate this diff. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>