finish-agent-sessionslisted

# Finish Agent Sessions Recover genuine unfinished outcomes from local agent history, reconcile them with current repositories, and finish them from present truth. A transcript ending mid-task is evidence to inspect, not an instruction to execute blindly. ## Safety - Use the privacy and coverage rules from `agent-session-auditor`: read-only stores, user prompts only, redacted reporting, local processing, and explicit unsupported coverage. - Current repository, remote, issue, PR, deployment, and provider state outrank old plans, checklists, claims, and test output. - Do not inherit stale permission for deployments, publishing, purchases, external messages, deletion, OAuth, credentials, or destructive cleanup. Require current authorization for consequential actions. - Coordinate one repository lane at a time. Preserve dirty work, worktrees, stashes, sequencer state, and unclear ownership; never overwrite them to make a session appear resolved. - Do not invent work from TODOs, brainstorming, rejected proposals, or broad roadmap language. Recover only an explicit requested outcome with concrete remaining acceptance criteria. ## Workflow 1. Discover and inventory every supported local agent store in scope. Produce detected, parsed, skipped, errored, archived, encrypted, and unsupported counts with date range. 2. Extract candidate interrupted tasks from user intent, assistant status, tool outcomes, handoffs, plans, and terminal markers. Retain source agent/session IDs and repo