Nick SzaunigandClaude Sonnet 5
cc46fa4d9e
A very common real-world event - a queen dying over winter, absconding, being superseded, sold, or replaced - had no side effect on the colony record at all. Colony.currentQueenId kept pointing at a queen who was no longer really there, colony.status stayed whatever it was, and the QUEENLESS dashboard alert could never fire from this path. QueensService.update() now detects a transition into LOST/DECEASED/REPLACED/SOLD and, inside the same transaction, clears currentQueenId on whichever colony currently points at that queen, flips its status to QUEENLESS (unless the colony is already in a terminal lifecycle status like DISSOLVED, which is left alone), and closes the open QueenColonyHistory row - mirroring the bookkeeping assignColony() already does when a queen changes colonies. Co-Authored-By: Claude Sonnet 5 <[email protected]>