(re)Standardize Session Name Attribute

[wpfleger96]

This PR reapplies all the same changes from #5085 that got reverted, except that this time the DB migration is 🤞 backwards-compatible:

• Instead of renaming description field to name in the session DB, we add name as a new column and use fallback logic for old sessions without a name
• This way the DB migration will be forwards and backwards compatible regardless of Goose version

Confirmed that after I ran the migration locally, I can resume a session by name using either new (local build) or old ("system" Goose v1.11.1) Goose

🐚 ~/Development/goose wpfleger/session-name ./target/debug/goose session --resume --name "Open team PagerDuty"
◇  WARNING: The original working directory of this session was set to /Users/wpfleger/Development/goose-fork. Your current directory is /Users/wpfleger/Development/goose. Do you want to switch back to the original working directory?
│  No
│
resuming session | provider: databricks model: goose-claude-4-5-sonnet
    session id: 20251001_94012
    working directory: /Users/wpfleger/Development/goose

goose is running! Enter your instructions, or try asking what goose can do.

Context: ●○○○○○○○○○ 14% (28569/200000 tokens)


~ goose session --resume --name "Open team PagerDuty"
◇  WARNING: The original working directory of this session was set to /Users/wpfleger/Development/goose-fork. Your current directory is /Users/wpfleger. Do you want to switch back to the original working directory?
│  No
│
resuming session | provider: databricks model: goose-claude-4-5-sonnet
    session id: 20251001_94012
    working directory: /Users/wpfleger

goose is running! Enter your instructions, or try asking what goose can do.

Context: ●○○○○○○○○○ 14% (28569/200000 tokens)
( O)>

Type of Change

• Feature
• Bug fix
• Refactor / Code quality
• Performance improvement
• Documentation
• Tests
• Security fix
• Build / Release
• Other (specify below)

Related Issues

Relates to #5044

[wpfleger96]

@DOsinga this is ready for review now, it has all the same changes from #5085 that got reverted but with this commit that:

• Create new name column instead of renaming description to name
• Add fallback logic for historical sessions in the DB that don't have a name

[wpfleger96]

CC: @michaelneale

[wpfleger96]

I've also validated backwards compatibility with net-new sessions:

~ goose
starting session | provider: databricks model: goose-claude-4-5-sonnet
    session id: 20251021_9
    working directory: /Users/wpfleger

goose is running! Enter your instructions, or try asking what goose can do.

Context: ○○○○○○○○○○ 0% (0/200000 tokens)
( O)> this is a test session to validate database backwards compatibility
I understand you want to test database backwards compatibility. To help you effectively, I need a bit more context:
...

~ goose session list | grep 20251021_9
20251021_9 - Validate DB compatibility - 2025-10-21 18:58:18 UTC

~ goose session --resume --name "Validate DB compatibility"
resuming session | provider: databricks model: goose-claude-4-5-sonnet
    session id: 20251021_9
    working directory: /Users/wpfleger

goose is running! Enter your instructions, or try asking what goose can do.

Context: ●○○○○○○○○○ 6% (11102/200000 tokens)
( O)> exit
Closing session. Session ID: 20251021_9

~ ~/Development/goose/target/debug/goose session --resume --name "Validate DB compatibility"
resuming session | provider: databricks model: goose-claude-4-5-sonnet
    session id: 20251021_9
    working directory: /Users/wpfleger

goose is running! Enter your instructions, or try asking what goose can do.

Context: ●○○○○○○○○○ 6% (11102/200000 tokens)
( O)>

[michaelneale]

When I run just run-ui with this - I only see names for new sessions:

But the good news is if I roll back (cli or GUI) I do see all names:

should this pick up the description as names for old sessions for display?

[wpfleger96]

@michaelneale this is now fixed 😄