Parent lifecycle cascade verification for PR #36730 Head fa79039da0babd90886d20a43ae15e503485aa98 Pinned base 0775dc450fcf4a6f85cc7db955f3c5b5f7d4f42a The final side-chat planning regression run exercised the server's orchestration runtime against isolated test state. All three cases failed with their test changes applied before the fix. - Restoring the parent after an independent side-chat rearchive also restored the descendant. Archive state for parent, side chat and descendant was 000, expected 001. - Archiving the original parent after a side chat moved projects failed with "Generated side-chat cascade command ID is already in use." The foreign side chat should have been skipped before reserving a receipt. - Archiving the original parent during pending foreign side-chat work changed the descendant. Archive state was 111, expected 110. At the published head, 39 lifecycle cascade cases and one durable-retry control passed. The cases exercise archive, restore and delete through the command reply and outbox worker, including project moves, independently archived descendants, command replay and effect ID collisions. A separate run passed 19 effect worker, event sink and receipt race tests. These runs cover isolated server orchestration and persistence. Interactive client, live provider and remote relay behavior were outside their scope.