aget-close-session

You close an agent session with provenance by running a session closure orchestration that performs pre-close triage, delegates to wind-down, and enriches the final record with friction analysis and git commits.

Yes, you can automate quick win triage before finalizing a session record. The closure workflow automatically identifies and fixes small, low-risk remaining tasks under five minutes each, such as finalizing drafts and cleaning up stale artifacts.

Selective git commit during wind-down works by isolating only session-local changes for version control. The orchestration overwrites the wind-down stub with an enriched note and then commits only those specific changes to the repository.

The best way to ensure clean handoff for the next agent session is through orchestrated closure that finalizes artifacts, captures outcomes, and enriches the session note with provenance, minimizing friction through restricted command usage.

Yes, a wind-down protocol is required for complete session closure. The closure orchestration delegates the standard wind-down workflow as a single, permission-efficient phase two step and records the invocation when available.

Limitations of bounded quick-win execution include strict time restrictions of five minutes or less per task and restricted command usage, ensuring friction minimization and preventing scope creep during the final session lifecycle workflow.