Patchhound publishes the security receipts

Field notes

The published exhibits use code diffs alongside repeatable checks rather than relying only on summary claims. One example adds authMiddleware to a proposal POST route and records 401 behavior without a token, 201 behavior with one, and a test progression from 1/3 to 3/3. The hunt log also covers an idempotency race involving PostgreSQL and payment integrity, while client work is stated to remain confidential by default.