session-close

Closing a hermit run requires stopping active monitors, archiving the session report, and resetting runtime state. Running /session-close executes this full shutdown sequence and defines a clear Next Start Point to prepare the system for the next run.

The best way to prepare a clear starting point is to use a structured session closure process that archives outputs and resets tasks, blockers, and notes. This automatically defines a Next Start Point to ensure continuity and traceability across runs.

Session archiving works by capturing the active session report at shutdown to preserve context and lessons learned. It updates runtime state and stores the session report, ensuring traceability before preparing a fresh start for the next session.

Yes, you can reset tasks, blockers, and notes for a fresh start by initiating a full session closure. This workflow automation stops associated tasks and resets the environment, readying the system for the next session.

You should use a structured handoff to end a work session whenever an operator wants to stop a hermit's run and archive results. It ensures continuity by archiving the session report and defining a clear Next Start Point for the next session.