turn-entry

What problem does it solve? When a new AI coding session starts, it knows nothing about what the previous session did. This rule governs how the session entry hook feeds the prior session's handover and the turn map (work states and mandatory actions) into context before the first reply, so work resumes from where it stopped instead of from a blank. ## Core Features & Use Cases - Handover loading by branch name: The startup hook reads the handover file named after the current branch from the handoff directory and places it into context whole. - Turn map as a standalone resource: The map of work states, mandatory actions, and four turn exits ships as its own defaults file rather than being parsed out of the rule, with a size limit enforced by a tree check. - Non-blocking entry: The hook exits zero on every launch type (first launch, resume, compaction, clear); a missing handover or map never refuses the session. - Use Case: A maintainer editing the session entry hook or the turn map consults this rule to keep the map, the rule's state table, and the consistency check in sync. ## Quick Start Ask the assistant to review the session entry hook and turn map against this rule before editing how handovers load at startup.