Bug Description
Builder terminals survive Tower restarts via shellper-backed PTY sessions, but the architect terminal does not. When Tower is stopped and restarted (e.g., for a package update), builders reconnect seamlessly while the architect session is lost.
Steps to Reproduce
af dash start — start architect dashboard
- Open architect terminal, begin working
af tower stop && af tower start — restart Tower
- Architect terminal is gone; builders survive
Expected Behavior
Architect terminal should be shellper-backed and survive Tower restarts, just like builder terminals do.
Actual Behavior
Architect terminal dies on Tower restart. User must re-run af dash start to get a new session.
Context
Shellper (Spec 0104) was designed for terminal session persistence across restarts. It works correctly for builder sessions spawned via af spawn, but the architect terminal created by af dash start appears to not go through the same shellper path.
Bug Description
Builder terminals survive Tower restarts via shellper-backed PTY sessions, but the architect terminal does not. When Tower is stopped and restarted (e.g., for a package update), builders reconnect seamlessly while the architect session is lost.
Steps to Reproduce
af dash start— start architect dashboardaf tower stop && af tower start— restart TowerExpected Behavior
Architect terminal should be shellper-backed and survive Tower restarts, just like builder terminals do.
Actual Behavior
Architect terminal dies on Tower restart. User must re-run
af dash startto get a new session.Context
Shellper (Spec 0104) was designed for terminal session persistence across restarts. It works correctly for builder sessions spawned via
af spawn, but the architect terminal created byaf dash startappears to not go through the same shellper path.