Sulkta 425c981682 fix(mcp): clamp vote validity_upper to voting_end_slot when range overshoots ... Same H-2-class issue as the advance Draft→VotingReady clamp. The vote MCP tool computed validity_upper = tip_slot + 1799 then errored if it overshot voting_end_check. On 30-min Sulkta-shape DAOs the voting window is 30 min wide, and the moment chain time crosses into the voting window the default 1799-slot upper bound lands ~30 min past tip — already past voting_end if voting_start was a few minutes ago. Now: when default upper would overshoot, clamp validity_upper_slot to voting_end_slot. Reject if remaining slots ≤ 5 (chain has no room to include). Caught 2026-05-08 trying to vote on preprod_test2 proposal #1 during a clean voting window — tx_upper landed 135s past voting_end. Clamp lets the vote tx fit. Cosign builder still has the same raw tip_slot pattern; deferred since cosign also requires within-Draft semantics and we don't have a multi-stake test yet to exercise it.		2026-05-08 11:48:36 -07:00
..
src	fix(mcp): clamp vote validity_upper to voting_end_slot when range overshoots	2026-05-08 11:48:36 -07:00
Cargo.toml	feat(dao): wire 8 dao_* MCP tools (Phase 1)	2026-05-05 13:51:04 -07:00