fix(server): stale toolBroker test; activity-label no-op clears + bounded maps (GHE #341, #202, #203)

[johnnyelwailer]

Distro issues: nexplore.ghe.com/pj/nexi-distribution#341, #202, #203.

What

• feat(cloud-sessions): reach cloud sessions through the Nexi broker (Entra), T3 Connect as fallback #341 — test expectation adds t3team.orchestration.status / .resume (live since 58c8d66); was red on pristine main.
• feat(t3team): kill the inter-agent chatter loop + idle-aware wake policy #202 — clear() skips the meta.update persist when the thread never had pending label state.
• feat(t3team): kill the inter-agent chatter loop (port onto evolved delivery tiers) #203 — createBoundedThreadMap (new sibling, FIFO cap 500, onEvict) backs both per-thread maps; reactor forgets state on thread.deleted (pattern copied from t3team-threadToolContextEvictionReactor).

Receipts

• pnpm exec vp test run src/t3team-toolBroker.test.ts src/t3team-activityLabelSummarizer.test.ts src/t3team-boundedThreadMap.test.ts → 33/33
• typecheck: no errors in touched files
• LOC: reactor 261→279, summarizer 301→337 (both already over the 200 cap on main; the map logic was extracted to keep growth to the new subscription + forget(); a proper split of these two files is separate debt)

Codex review pending.

🤖 Generated with Claude Code

[johnnyelwailer]

Codex review (refute-first) — 1 confirmed bug + 1 partial; NOT fixed yet, PR stays draft

1. Stranded label after FIFO eviction (t3team-activityLabelSummarizer.ts:130-132, 180, 185, 260): pending lives on after a successful persist (kept alive for TTL), eviction deletes it and cancels the TTL, and the new clear() early-return then bails on idle → a persisted real label is never cleared. Repro: persist label for t1, push 500 other threads, t1 idles. Fix direction: track "label persisted" separately from pending, and on evict either persist {activityLabel: null} or keep a tiny persisted-set so clear() still fires. Test: eviction-after-persist then idle → meta.update null dispatched.
2. Persist after thread.deleted (reactor.ts:247, 273-275; run() :176/:180): generation is detached and does not re-check after await persist; forget() clears maps only, so a thread.meta.update can land on a deleted thread. Low impact (no state resurrection); fix: re-check a per-thread generation token after the await.

Verified clean: FIFO cap + eviction tests; timer cancellation on evict/forget; idle/deletion ordering is sequential in one stream fiber.

[johnnyelwailer]

Both Codex findings fixed in the 2nd commit (new sibling t3team-activityLabelPersistTracker.ts; summarizer 337→346 lines, reactor unchanged). Tests 35/35 incl. eviction-after-persist → null clear, and forget-during-persist → result discarded. Still draft: no live-app run.

[github-actions]

Thread transfer impact

⚠️ The latest CI run did not produce a thread transfer result for 6c4d4d3.

This comment will update automatically after the next completed run.