365-session-rotation-maintainerlisted

# 365 Session Rotation Maintainer / 365任务轮换 Treat rotation as one recoverable transfer of work and task identity. Preserve the predecessor until one successor has received, acknowledged, and presented a verified handoff. 把轮换当作一次可恢复的“工作状态 + 任务身份”转移。在唯一继任任务完成接收、确认和可见 交接前，始终保留原任务。 ## Core contract / 核心约定 - Rotation requires an explicit user request. Age, context length, inconvenience, or a new model release does not authorize replacement or archival. - Create at most one successor. Never create another because setup, acknowledgement, or readback is slow. - Preserve unrelated worktree changes. Do not reset, clean, stash, absorb, or silently move them to make rotation pass. - Never copy raw transcripts, hidden reasoning, credentials, tokens, private URLs, raw PII, or unnecessary logs into the handoff. - Rotation authority does not authorize merge, deployment, database, Shopify, messaging, production, or other protected actions. - Match the user's language and keep the owner-facing handoff understandable without logs. ## Modes / 模式 - **AUDIT_ONLY** — inspect readiness and report blockers without creating, renaming, or archiving tasks. - **EXECUTE** — perform one complete rotation after explicit authority. - **RECOVERY** — resume the same nonterminal rotation; never start a parallel replacement. ## Compatibility and fallback / 兼容性与降级 Select one implementation before inventory. If the current project maintains an exact rotation entry, follow that entry and its sel