trellis-finish-work

To archive completed tasks and record a session journal, you can run the finish-work command which inspects active tasks, archives finished ones via auto-commit, and writes a session journal using work-commit hashes.

During session wrap-up, dirty-path classification guardrails detect uncommitted changes, determine if they belong to the current task, and block the finish-work process if current-task code remains uncommitted.

The best way to ensure quality gates pass before archiving tasks is to run a deterministic cleanup process that inspects active tasks and git status, verifying all current-task changes are properly committed before archival.

Yes, the session wrap-up process classifies dirty git paths to determine whether uncommitted changes belong to the current task, preventing unrelated work from other terminals from being incorrectly mixed into the archival.

You need a deterministic cleanup process for end-of-session task archiving when you want to safely close out a coding session, verify quality gates, and record what happened without incorrectly committing or mixing unrelated work.

Finish-work blocks task archiving when current-task code is uncommitted because it needs to ensure quality gates have passed and current-task changes are safely committed, preventing accidental loss of work during the session journal recording.