You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
teams: a local launch writes no Close/Reopen note to the team's Traffic #1524
On a plain codeaf launch (no --host), closing a team and reopening it on the teams page writes no Close/Reopen note to that team's Traffic log. teamsUndoClose in internal/tui3/teamclose.go sends the person reopened the team, and close sends its equivalent, but on a local launch neither reaches the log. This was found on 2026-09-25 while fixing #1516's item 6.
It has the same cause as #1516's item 6. The local launch's teams seam (localDoors in cmd/codeaf/chatv3_local.go) was not handed the door that the engine road uses. Item 6 fixed History; the Traffic write for these notes is still missing.
Replication
Deterministic: a cmd/codeaf test that builds the plain-launch doors (localDoors), closes a team through the seam and reopens it, then reads teams.ReadTraffic for that team. Today no close/reopen entry is there. TestPlainLaunchReadsClosedTeamReportFromEngineProfile (#1516) is the pattern to copy.
By hand:
Run codeaf.
Press alt+2, make a team with a manager, and close it with Close.
Reopen it with u.
Look at the manager's Traffic column. It shows no close or reopen line.
The fix
A local launch writes the same Close/Reopen notes to Traffic as the engine road does.
Acceptance
e2e: on a plain launch, the manager's Traffic shows the close and the reopen lines after the steps above.
Unit: the localDoors seam test sees both entries in teams.ReadTraffic.
Activity