Feature: Allow dynamic session naming for scheduled tasks based on execution content

Summary

When using scheduled tasks (cron triggers) in Claude Desktop, all sessions generated by the same schedule inherit the schedule's name (e.g., "Daily issue solver") regardless of what was actually executed. There is no way to programmatically rename a session to reflect the work done during that run.

Problem

When a scheduled pipeline runs hourly and processes different Linear/GitHub issues each time, the sidebar shows multiple sessions all named identically — making it impossible to quickly identify which session worked on which issue without opening each one.

Current behavior:

• Session 1: "Daily issue solver" (worked on SOM-93)
• Session 2: "Daily issue solver" (worked on SOM-94)
• Session 3: "Daily issue solver" (worked on SOM-95)

Desired behavior:

• Session 1: "Daily issue solver — SOM-93: Exclusão de agendamento não reverte tratamento"
• Session 2: "Daily issue solver — SOM-94: Remove sensitive console.log"
• Session 3: "Daily issue solver — SOM-95: Fix financial indicator fallback"

Proposed Solution

One or both of the following:

1. Expose a rename_session tool available to agents during execution, so pipelines can rename the session once they know what issue they're working on.

1. Support a session_title output field in hook JSON responses (e.g., from a Stop hook), so the final title can be set programmatically after execution completes.

Use Case

Automated development pipelines (e.g., scan backlog → pick issue → implement → open PR) run on a schedule. Each run handles a different issue. Being able to rename the session to include the issue ID/title would make it trivial to audit history, find a specific run, or correlate a session with its PR — without manually renaming dozens of sessions.

Environment

• Claude Desktop (Windows)
• Scheduled tasks / cron triggers