In ThrusterTreasure.sol, there is no on-chain check to ensure owners setWinningTickets() transaction will not settle on the max end timestamp of a round roundStart[_round] + MAX_ROUND_TIME. 
If setWinningTickets() happens to settle on roundStart[_round] + MAX_ROUND_TIME, setWinningTickets() transaction will still succeed. But in this edge case, winners are likely not to be able to claim their prizes for the round, because claimPrizesForRound() contains the same check for roundStart[roundToClaim] + MAX_ROUND_TIME >= block.timestamp. If users claiming tx settles after roundStart[roundToClaim] + MAX_ROUND_TIME, claiming tx will revert, and users will not be able to claim their prizes.
(https://github.com/code-423n4/2024-02-thruster/blob/3896779349f90a44b46f2646094cb34fffd7f66e/thruster-protocol/thruster-treasure/contracts/ThrusterTreasure.sol#L276)
Although the owner can decide on the timing to set winning tickets, it will be good to ensure on-chain that there will always be a grace period between setWinningTickets() and claimPrizesForRound(). So do not use the same end timestamp check for both. 
