feat(agents): bring beta teams over with Import from old Buzz

[wpfleger96]

🤖 Import from old Buzz now brings each agent's beta team over as a 1.0 team, with beta's name and shared instructions. Agents imported before this change can be restored into their teams.

Builds on #775 (editable agent teams) and #774 (strip old team text from imported prompts), both merged.

Controller (native)

• Import: each imported agent records imported.betaTeam: the beta team ID, the 1.0 team ID, the name, whether old Buzz still had the team, which old Buzz install it came from, the original beta text (betaText, never changed afterwards) and a status (pending, completed or skipped). A team old Buzz had already deleted starts as skipped.

• Team ID: beta- plus the SHA-256 hex of the beta team ID, so importing more members later joins the same team and a re-import never creates a copy. Names are trimmed, fall back to "Team from old Buzz", and are cut to the app's 120 UTF-16 code unit limit without splitting a character.

• Previews: the import preview and the agent summary show {teamId, name, status}. The text is never included.

• agent_control_beta_teams: this account's pending agents in a community, grouped by team.

• agent_control_beta_team_finish: finishes one agent in one native write, after checking its revision, community and owner. completed requires a readable team that lists the agent. It adds the team to the agent's team links without removing any, then runs feat(teams): edit shared team instructions in their own record #775's team-text resolver (now the shared sync_doc) on the same document. skipped requires the team's current catalog head to be a deleted-team marker; catalog decoding now keeps that deletion flag, and heads saved without it still read as live. Any refusal writes nothing, and the agent stays pending.

• Restore for earlier imports: agent_control_beta_team_restore_preview groups selected agents by their beta team, using old Buzz's files when they still list every member, or otherwise the agents' own unlinked copies, marked as inferred. An inferred group with no text is never offered. agent_control_beta_team_restore then starts the whole group in one all-or-nothing write, checked against the preview's token, texts and every member's revision, owner and community. After that, members finish like any pending agent.

• Known limit: the app checks for clashing team texts before it saves the member list. If another device edits only the text of an overlapping team between that check and the save, the step doesn't catch it. Native finish still refuses the conflicting texts, so the agent stays pending instead of getting the wrong instructions.

App

• Import from old Buzz has a rerunnable team step and labels each agent "Joins team X".
• From old Buzz section on the Agents page: finds the beta teams of agents imported earlier and restores them, and offers "Finish team setup" for pending teams. When members had different beta texts, "Choose instructions…" asks which to keep. Both old Buzz libraries are offered unless the host reports exactly one; older hosts that report none get both. "All teams from old Buzz are set up" shows only after pending teams were read successfully. If that read fails, its error shows a Try again button that reads pending teams again, even when no agent is left to find teams for; a successful read clears that error without hiding a Finish or Restore error. While a team is being set up the section doesn't say it is reading teams, and only finding teams spins Find teams; every control stays disabled while either runs.
• Focus: after a successful Finish setup or Restore, focus moves to the section once that action's own row is gone, but only if focus was left on the page body. A pending row and a restore preview for the same team are told apart, so a surviving preview doesn't hold the handoff. While the section is hidden (for example during a team catalog reload) the handoff waits and runs when the section returns. It ends without moving focus when the action fails or is refused (a refused restore puts focus on Find teams again) or when the person moves focus to another control or clicks anywhere outside the row (clicking empty space moves no focus, so the click itself cancels it). A successful Try again, whose button goes away with the error, hands focus to the section under the same conditions: only from the body, and only if the person hasn't moved focus or clicked elsewhere meanwhile.
• Shared header (content-header.css): when space runs out, every Header and InlineHeader now wraps its actions as whole controls below the title and explanation (which keep at least 12rem) instead of squeezing the text, and header actions get a --space-2 gap. This matches what Settings already did. On the Agents page, Refresh teams and Create team are now 8px further apart.

[kalvinnchau]

🤖 One retry-path defect found; see inline comment.

[wesbillman]

One change needed: keep restore discovery rerunnable after empty results and stale-preview refusals. The existing empty-result finding is confirmed; the inline comment covers the stale-preview path that the same recovery fix should handle.

Star Lord’s automated source review via Wes’s account — head fcfd0472453d836579cf77149cc92099c83ff9b1, base 8cef21d09b5723b102a036a8fd3d1ee24d02470f.

Source-only: no tests or app execution; native/live-relay migration and rendered focus behavior remain unverified. The hosted CI snapshot is red (JavaScript 2/2); its cause is not established.

[wesbillman]

One change remains: preserve the new focus handoff across the controller’s error → ready transition (inline). The persistent Find/source controls address the previous retry dead end.

Star Lord’s automated source review via Wes’s account — head ad232d64b8cd644cd48a680d9afb33445bc2db18, base 82d165d5b6fd7dc1f3e9784675d27c04aacdbeae.

Follow-up scope: the retry fix, its controller integration, and merge resolution. Source-only: tests and app not run; native migration, rendered keyboard behavior, and current CI remain unverified.

[wesbillman]

No changes requested in this follow-up: the remaining focus finding is addressed by retaining the handoff until readiness and a mounted Find button. The new real-controller regression covers error → ready recovery, and changing libraries or starting another Find now discards the previous preview.

Star Lord’s automated source review via Wes’s account — head b0a307eef56025984b66ca49427fb8e50aa4c680, base 82d165d5b6fd7dc1f3e9784675d27c04aacdbeae.

Source-only: tests/app not run; rendered keyboard behavior and native migration remain unverified, and JavaScript, browser journeys, and Rust checks were still running in the hosted CI snapshot.

[wesbillman]

One change needed: the new completion state can report “All teams from old Buzz are set up” when the pending-team read failed (inline). The earlier retry/focus fix remains intact through the layout move.

Star Lord’s automated source review via Wes’s account — head 7f1089c57628435bae1beccdb77e752bf8110827, base 82d165d5b6fd7dc1f3e9784675d27c04aacdbeae.

Follow-up scope: the permanent section, source controls, and instruction-choice dialog. Source-only: tests/app not run; native migration and rendered keyboard behavior remain unverified. JavaScript and Rust checks passed in the hosted snapshot; four browser-journey checks were still running.

[kalvinnchau]

🤖 One minor progress-state defect found; see inline. The existing pending-read completion finding remains unresolved.

[wesbillman]

The false-completion state is fixed, but the retry portion of the previous finding remains unresolved; see the inline follow-up. No additional changes requested in this delta.

Star Lord automated source review via Wes’s account. Head 88218bb32529421fe65a2b13b4ca54b6ac84eccf; base 82d165d5b6fd7dc1f3e9784675d27c04aacdbeae. No tests or app/native workflows run; rendered focus/layout and CI unverified.

[kalvinnchau]

🤖 One minor focus-lifecycle regression found; see inline. The existing pending-team read retry finding remains unresolved.

[wesbillman]

One prior change remains: complete the pending-team read retry/error-clear path. This focus-only update leaves it unchanged. The stale-focus finding is addressed in source by binding the handoff to one row and clearing it on failure or focus moving elsewhere; no new findings in this delta.

Star Lord’s automated source review via Wes’s account — head fad36e6f6ad79085c557b9331a6535f5d071fce7; base 82d165d5b6fd7dc1f3e9784675d27c04aacdbeae.

Source-only: tests/app not run; rendered keyboard behavior and native migration remain unverified. Current CI not checked.

[wesbillman]

One change needed: preserve focus when the new pending-team retry succeeds (inline). The previous retry/error-clear request is otherwise addressed, and setup no longer presents discovery progress.

Star Lord’s automated source review via Wes’s account — head bb3c540d30024aa5ad59220edf58efddac2f6147; base 82d165d5b6fd7dc1f3e9784675d27c04aacdbeae.

Source-only: tests/app not run; rendered keyboard behavior, native migration, and current CI remain unverified.

[wesbillman]

[P2] Preserve focus when the retry clears its error

Keyboard activation of Try again leaves focus on this button while betaTeams runs. A successful read calls setReadProblem(null) (line 233), so this conditional removes the focused button. The existing settle handoff is armed only by Finish/Restore (settled, line 263), not by retry, and refind only handles a refused restore. Thus an ordinary failed read → keyboard retry → success drops focus onto the page body instead of keeping it with the restored teams. The new test uses fireEvent.click, so it never focuses the removed control.

Keep the focused retry control mounted, or transfer focus to a surviving row/section only if the user has not moved elsewhere. Add a keyboard-activated retry regression asserting a surviving focus target after success. This follows DESIGN.md’s “States, feedback, and motion” requirement to preserve a focused retry control when results become empty or populated.

[wesbillman]

No changes requested in this follow-up. The retry-focus finding is addressed; distinct pending/preview keys and waiting for the mounted section also preserve the intended completion handoff.

Star Lord’s automated source review via Wes’s account — head 2c14693b79a3ba2737f325bd6a53cac2998d2a57; base 82d165d5b6fd7dc1f3e9784675d27c04aacdbeae.

Source-only: tests/app not run; native migration and rendered keyboard/layout behavior remain unverified. JavaScript, Rust, and browser journeys were still running in the hosted CI snapshot.

[wesbillman]

No changes requested in this follow-up: the click-away listener clears the pending handoff during catalog reloads and retry reads without cancelling the initiating instruction choice.

Star Lord’s automated source review via Wes’s account — head d1b34951a672a6124ee99c205a0544d9a66821c7; base 82d165d5b6fd7dc1f3e9784675d27c04aacdbeae.

Source-only: tests/app not run; native migration and rendered keyboard/pointer/layout behavior remain unverified. Hosted CI snapshot: JavaScript (2/2) and browser journeys still running.