Problem
Lead Protocol sessions need a clear ordering rule for branch-based work: operational state updates must be completed before the branch is merged. If handoff or decision state is written only after merge, protected branches make the state update awkward and can create unnecessary follow-up PRs.
Proposed change
Add an explicit protocol rule:
Session close must be the final operational step on the feature branch. Complete handoff, decisions, lessons, and journal updates before opening or merging the PR.
Acceptance criteria
- The rule is documented in the session-close procedure.
- The checklist makes the ordering visible to agents.
- Validation or documentation warns against writing operational closeout state directly on the default branch after merge.
Problem
Lead Protocol sessions need a clear ordering rule for branch-based work: operational state updates must be completed before the branch is merged. If handoff or decision state is written only after merge, protected branches make the state update awkward and can create unnecessary follow-up PRs.
Proposed change
Add an explicit protocol rule:
Acceptance criteria