Refine Teams overviews, shared conversations and scoped deletion

[ZeroPoint95]

🆕 All teams and chat teams

What changed

Teams now provides a dedicated overview and management surface: nested team cards, faithful conversation previews, paged interactions, actionable questions, and an optional global manager. Recent interactions has persistent Prev and Next controls for paging in both directions through six-row pages. Active manager, member and Global manager cards show a working spinner that stops for questions and idle work, with static marks for ASCII and screen-reader views. Nested children stack in one column with parent labels, counts, and branch guides. Deeper or narrow hierarchies switch to expandable tree rows so descendants remain reachable without shrinking boxes indefinitely.

Chats meanwhile uses one synchronized team overlay selector and a fixed All button for the complete saved conversation library, including conversations without open tabs. A selected team appears as a chip: its name reopens the dropdown and its independent x restores ordinary Chats, synchronizing Teams to All teams. The dropdown lists actual teams only, without a None option.

Team creation uses a searchable Name/Project multi-select picker on Teams and card selection on Chats; both share the same catalog and creation flow. Membership removal preserves conversations and work.

Disbanding recursively ends coordination while retaining history; team deletion removes metadata but preserves conversations. Conversations can be deleted outright.

Conversation deletion stops work and removes its tasks, while task deletion removes only its containment subtree. Ordinary managers must be reassigned in Teams before conversation deletion, and one conversation cannot newly manage unrelated teams.

Deletion now enforces manager reassignment at the store boundary, validates task paths before mutation, waits for cancelled workers to finish, and keeps interrupted cleanup reachable from Home with startup recovery. Normal shutdown retains journal ownership through the cancelled run and releases it before run completion is published, allowing immediate restart. Replacing a parent manager explains the child-first reassignment order when that conversation also manages sibling subteams. Saved profile memories remain independent of transcript deletion.

Closing-report acceptance records its terminal interaction under the lifecycle lock and can retry a failed append without duplicating history. Hosted membership writes require a compatibility capability; current builds preserve unknown member fields and existing join boundaries. Team sheets and the Teams own-answer box retain typed stop-key letters, including with an empty underlying chat draft; cancelling restores the stop shortcut. Scrolled-off targets cannot intercept clicks on blank narrow-frame rows. Obsolete disband undo code was removed. Manuals, retrieval probes and the design record describe the final controls and refusals.

How it was checked

• Merged current dev (362174a92), preserving contextual-memory changes alongside deletion.
• make pr-ready: light gate plus fresh complete suites for every changed package against origin/dev. No exemptions or test skips added.
• Focused fresh regressions for deletion preflight/recovery, worker completion, manager reassignment, terminal history, hosted membership compatibility, modal typing, narrow pointer targets and manual retrieval.
• Focused -race -count=1 checks for worker completion, immediate restart, terminal-history retry and membership round-trips. Canonical temporary roots repair inherited macOS contextual-memory fixtures without changing their assertions.
• make build produces the canonical bin/codeaf. Isolated terminal checks confirm modal typing, bidirectional six-row paging and the complete saved-conversation grid without the owner's profile or live model requests.
• The own-answer follow-up reproduced the lost x before the fix and passed BASE=326efd58c make pr-ready after it, with fresh UI and manual suites.
• Independent adversarial review and follow-up review of its revisions; no remaining actionable findings.

Checklist

• A feature-level change entry is included (1750-teams-ux-cleanup.md).
• The manual describes the changed controls, routing, capabilities, limits and refusals.
• No known-red exemptions added.
• Only explicit feature paths staged.

For owner review; no merge is requested.

[ZeroPoint95]

converting to draft for now so we can implement a couple additional changes after team review

[ZeroPoint95]

ready to merge after two rounds of adversarial review