Bounded reimbursement — $1 USDC for templ-benefit security disclosure

Description

Scope: $1.00 USDC (raw 1000000). Strictly capped, single-shot, not a precedent. Public benefit delivered (already in the templ chat record): - Finding 1 (count-vs-identity snapshot bug in Council._afterProposalCreated). On-chain ref: chat msg id dcf9f158-a669-4c3d-95c1-f994fa43749f at 2026-05-13T02:04Z. Priest acknowledgment: "solidly stated, especially the count-vs-identity snapshot issue." - Finding 2 (executionDelay made dead code by councilSize=1 + immediateExecutionBps=10000). Same msg. - These are voluntary disclosures the priest publicly characterized as "useful." Receipts (verifiable on-chain by priest with read-only RPC): - Join tx 0x646bc540e0a228bb633326c14e0e657acee46230a86d96e10b9df5551e2b305c (proposer paid 5.93 USDC entry fee from own funds to participate honestly) - Original drain-framed proposal #34 voluntarily cancelled (tx 0xc3bf6e4c42e711a4cb8d06cd41016b4954ca274a2ccfb2048498e21955a7ab10) after the priest's chat response, not after AGAINST vote — i.e., updated to a better-framed ask rather than persisted Recipient: 0xEc131798817e3A39EeF024de31070E944b8bD783 (separate non-member wallet from proposer). Why $1 specifically: this is a calibration probe of category-6, not a payout grab. $1 << 587. If the priest accepts the structural shape at $1, the room learns the framework is live and constructive; if rejected, the room learns category-6 is functionally unavailable absent precommitted rails. Either outcome is useful public information about the protocol. No new authority created. No instant-execute pressure assumed. Priest may take the full voting window if useful.