Rebased onto 6320d244, which fixed the two schema bugs in these fixtures
(NOT NULL stacktrace, self-referencing canonical_id FK). This adds the third,
which that commit could not have seen.
`error_data` decodes as ATError on read and '{}' lacks its required `when` key.
With the guard intact the query returns no rows, so nothing is decoded and a
filtered run is green either way. The defect only manifests when the guard
regresses: the foreign row is returned, the decode throws, and the test dies
with a HasqlException instead of the disclosure assertion — same red, wrong
reason, wrong message.
Break-tested by neutralising each predicate as `AND (project_id = #{pid} OR
TRUE)`, which keeps pid used so it still compiles under -Weverything -Werror:
errorUnmerge_ expected: [False] but got: [True]
errorGroupMembers_ HTML with SecretTypeError: victim-only-message,
Hash: group-read-authz-hash, and a live Unmerge button
Predicates restored: 806 examples, 0 failures.
Notes record the audit method, the three vulnerabilities, and the general
lesson — a fixture defect that only manifests when the guard fails is
invisible to every run in which the guard works.