Skip to content

fix: align session handling with upstream gastown#19

Merged
web3dev1337 merged 2 commits intomasterfrom
docs/orchestrator-sync-audit
Mar 19, 2026
Merged

fix: align session handling with upstream gastown#19
web3dev1337 merged 2 commits intomasterfrom
docs/orchestrator-sync-audit

Conversation

@web3dev1337
Copy link
Copy Markdown
Owner

@web3dev1337 web3dev1337 commented Mar 19, 2026

Summary

This PR fixes the main remaining drift between gastown-gui and upstream steveyegge/gastown.

Upstream gastown now uses tmux session names derived from rig prefixes in mayor/rigs.json instead of hardcoded legacy gt-* names. The GUI still had multiple server-side assumptions built around the old naming, which broke running-state detection and tmux-backed actions against current upstream towns.

Changes:

  • add registry-aware session-name parsing and generation in server/domain/session/SessionNames.js
  • update server.js tmux-backed routes to resolve current upstream session names
  • update StatusService running-state detection to parse current upstream tmux sessions
  • require rig prefixes when deriving agent session names
  • document the upstream sync audit in docs/ORCHESTRATOR-SYNC-AUDIT-2026-03.md
  • add unit coverage for registry-based session naming and status parsing

Verification

  • npm test
    • 37 test files passed
    • 321 tests passed

Upstream References

Checked against:

  • steveyegge/gastown 3b4460b
  • steveyegge/beads 27b24a2

@web3dev1337 web3dev1337 changed the title docs: audit orchestrator sync since v0.9.4 fix: align session handling with upstream gastown Mar 19, 2026
@web3dev1337 web3dev1337 merged commit e0a8ecb into master Mar 19, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant