refactor(auto-title): Untangle auto-title generator

[charlesvien]

Problem

The auto-title generator was broken. Layers of edge-case guards and duplicated rename logic across components had papered over the real flow until nothing worked reliably. This rips out the patches and rewires it end to end.

Closes #2397

Changes

1. Pass the Task into useChatTitleGenerator so it can run off description, not just session prompts
2. Drop the manual "Untitled" fallback in task-creation.ts so the generator is the single source of truth
3. Gate generation on auth state and skip when the user has manually renamed (isAutoTitleLocked)
4. Collapse the duplicated rename flows in SidebarMenu and TaskDetail into one useRenameTask hook
5. Thread currentTitle through onTaskEditSubmit so rename can no-op on unchanged input

How did you test this?

Manually

Automatic notifications

• Publish to changelog?
• Alert Sales and Marketing teams?

[charlesvien]

• feat: update defautls #2431
• feat: add enthropic packages to exlude list #2430
• feat: Upgrade Claude adapter to SDK 0.3 with native binary #2385
• fix: Gate unsupported-slash-command on SDK command list #2425
• refactor(auto-title): Untangle auto-title generator #2428 👈 (View in Graphite)
• refactor(auto-updater): Introduce state machine and guard staged updates #2427
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[greptile-apps]

T-Rex Logs

What T-Rex did

• Set up a focused renderer test harness for the task rename hook and confirmed the existing rename tests pass.
• Added targeted checks for rapid consecutive renames, unchanged-title submission, and summary cache keys with different task-id arrays.
• Observed that the rapid-rename check demonstrated a timing sequence where after rename Original -> A was in flight, rename A -> B succeeded, then the first request failed and the cached title was restored to Original.
• The summary cache key check passed and unchanged-title submission was recorded as an observation rather than a verified condition.

Artifacts

Verbose rename edge-case test output

• Detailed test run output for the rename edge-case tests, used to inspect rapid-consecutive-renames behavior and cache-key checks.

_{Ran code and verified through T-Rex}

Prompt To Fix All With AI

Fix the following 2 code review issues. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 2
apps/code/src/renderer/features/sessions/hooks/useChatTitleGenerator.ts:111
**Preserve manual titles** The manual-title lock only checks `getCachedTask(taskId)`, but that helper scans task list queries and can return `undefined` when the detail page has the task but the sidebar list cache is missing or stale. In that state a task whose `task` prop already has `title_manually_set: true` is treated as unlocked, so the next generated title can overwrite a user rename.

```suggestion
          const titleLocked = isAutoTitleLocked(getCachedTask(taskId) ?? task);
```

### Issue 2 of 2
apps/code/src/renderer/features/sessions/hooks/useChatTitleGenerator.ts:161-167
**Keep prompt counter** Description-based generation currently advances `lastGeneratedAtCount` to `1`. When the first real prompt event arrives, the `promptCount === 1 && lastGeneratedAtCount.current === 0` branch no longer runs, so the first prompt is skipped and prompt-based title/summary generation waits until several more prompts arrive. This can leave the session summary missing or stale after the conversation starts.

```suggestion
        if (shouldGenerateFromTaskDescription) {
          initialDescriptionHandled.current = true;
        }
```

_{Reviews (1): Last reviewed commit: "clean up auto-title path and add rename ..." | Re-trigger Greptile}

[k11kirky]

nice

[k11kirky]

Merge activity

• May 29, 10:26 AM UTC: A user started a stack merge that includes this pull request via Graphite.
• May 29, 10:28 AM UTC: Graphite rebased this pull request as part of a merge.
• May 29, 10:35 AM UTC: @k11kirky merged this pull request with Graphite.