gastown/crew/dennis bda1dc97c5 fix(namepool): only persist runtime state, not config in state file ...

The pool state file was saving CustomNames even though Load() ignored
them (CustomNames come from settings/config.json). This caused the
state file to have stale/incorrect custom names data.

Changes:
- Create namePoolState struct for persisting only OverflowNext/MaxSize
- Save() now only writes runtime state, not configuration
- Load() uses the same struct for consistency
- Removed redundant runtime pool update from runNamepoolAdd since
  the settings file is the source of truth for custom names

Fixes: gt-ofqzwv

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

2026-01-17 01:40:02 -08:00

..

manager_test.go

feat(namepool): auto-select theme per rig based on name hash

2026-01-16 15:35:10 -08:00

manager.go

fix(polecat): ensure nuke fully removes worktrees and branches

2026-01-17 00:37:51 -08:00

namepool_test.go

feat(namepool): auto-select theme per rig based on name hash

2026-01-16 15:35:10 -08:00

namepool.go

fix(namepool): only persist runtime state, not config in state file

2026-01-17 01:40:02 -08:00

pending.go

fix(polecat): remove pending.json tracking anti-pattern (ZFC)

2026-01-09 22:11:14 -08:00

session_manager_test.go

refactor: unify agent startup with Manager pattern

2026-01-06 22:32:35 -08:00

session_manager.go

fix(sling): verify session survives startup before returning success

2026-01-16 16:03:29 -08:00

types.go

docs: clarify polecat three-state model (working/stalled/zombie)

2026-01-12 02:20:30 -08:00