resign() posted a Bluesky farewell and updated local/SQLite state but never touched the on-chain boo.sky.go.game record, so a resigned game stayed status:"active" forever — a restart would replay the same board, find zero valid placements again, and resign a second time. Post a boo.sky.go.action resign record (works from either player role, same pattern as join) and, when we own the game record, putRecord it back with status:"completed" and winner set, via swap_record CAS.