Allow Richese reveals with unrelated public deals
Verify and publish checkpoint container / container (push) Successful in 11m19s

This commit is contained in:
Quintine committed 2026-11-16 15:24:41 +11:00
1 parent d7d0f89625
commit d169740adf
7 files changed
+275 -3

No files matched your search

+6 -2
View File
@@ -67,8 +67,12 @@ export function richeseRevealInterruptSupported(g: Game): boolean {
live(g.leaderRevivalPromises) || live(g.revivalExpressionPromises) || live(g.bribePromises) ||
live(g.pledgePromises) || live(g.bribeExpressionPromises) || live(g.alliancePromises) ||
live(g.allianceExpressionPromises) || live(g.movementPromises) || live(g.movementExpressionPromises) ||
g.futureBattleLeaderPromises?.some(row => row.turn === g.turn && (row.status === 'waiting' || row.status === 'bound')) ||
g.deals?.some(deal => deal.status === 'active')) return false;
g.futureBattleLeaderPromises?.some(row => row.turn === g.turn && (row.status === 'waiting' || row.status === 'bound'))) return false;
// Active agreements alone are not a reason to block this reveal: writing or
// paying a public deal does not spend or move the marker's reserves. Their
// independently recorded current-turn travel commitments remain fenced by
// the same live-ledger check above as other binding movement promises.
// Mixed-question receipts can own binding state separately from the ordinary
// residual lists. Conservatively retain their whole current-turn boundary.