session-end

Closing a completed workstream involves capturing reusable insights into lessons documentation, updating plan status, and archiving completion evidence. This process ensures future sessions start with accurate context by preventing stale documentation and missing outcomes.

Archiving completed work requires creating dated archive entries for substantive tasks while refreshing feature-scoped plan status and review notes. This deterministic file operation approach records durable evidence without conflicting with concurrent agent operations across the repository.

Concurrent agent operations are supported by enforcing deterministic file operations and fan-in commit behavior. This approach prevents repo-wide conflicting operations, ensuring multiple agents can wrap up sessions independently without overwriting shared documentation or archive entries.

Session termination applies when a workstream is fully finished and requires capturing lessons and archiving outcomes, rather than transferring active context. This exclusivity ensures completed work is properly closed out instead of leaving stale plans or unarchived results for future sessions.

Orientation cache updates and cross-repo memo resolution are supported during wrap-up. A single pinboard line is written to cache critical transient gotchas, while optional memo hygiene prompts action on any resolved receiver-side inbox memos in the current repository.

Archive entries use YYYY-MM format to organize substantive completed work chronologically within the archive directory. This deterministic structure tracks shipped outcomes by month, ensuring completion evidence is preserved and easily retrievable for future session context.