feat(agent-org): flatten Team definitions and freeze capabilities

[ShiboSheng]

Problem

Agent Org Team definitions still used the recursive hierarchy contract while the long-lived runtime introduced by PR #824 needs a stable, flat launch contract. Writer grants and Member communication policy were not represented as independent, validated capabilities, and the legacy Agent Org runtime schema could prevent upgraded installations from starting a new Team. The superseded PR #786 also mixed its PR2 work with an incomplete PR1 merge and audit follow-ups that were not all intended to ship.

Solution

This PR is a clean PR2 stack on the exact current head of PR #824. It replaces recursive Team definitions with Coordinator + flat Members, assigns stable Member IDs, persists independent additional TaskGraphWriter grants and canonical undirected Member communication links, and freezes roster/grants/links into the immutable launch snapshot used by PR1 materialization and recovery.

The Team settings UI uses one canonical pair draft set: each Member row shows its Writer state and connected count, while a right-side panel edits at most the other 49 Members. The panel has no independent save action; the main Team form performs the single trusted full-replace save. New Teams and newly added Members explicitly materialize all default communication pairs.

The PR also retains the narrowly scoped P0 fixes from the original PR2: exact recognition and transactional reset of the official 15-column legacy Agent Org runtime envelope, plus exclusion of orphan Agent Org Member sessions from standalone SDE pagination. Ordinary Rust/CLI Sessions and all non-Agent-Org data remain untouched.

Supersedes #786

Fixes #757

Potential risks

• This PR is stacked on Draft PR feat(agent-org): add authoritative Team lifecycle #824 and must not merge before that PR. Its base branch is codex/issue-756-pr1-clean-rebuild so the review diff contains PR2 only.
• An exact v1.2.3-v1.2.5 15-column agent_org_runs fingerprint causes the four Agent Org runtime envelope tables to be rebuilt. Old Team runs are intentionally abandoned and are not recoverable by reverting this code; ordinary Rust/CLI Sessions are preserved. Unknown schemas fail closed and are never destructively reset.
• Legacy recursive Team definition files are backed up byte-for-byte and reset to the new built-ins rather than guessed into a flat topology.
• Writer grants and communication links are stored and frozen but remain inactive until their dedicated later PRs; this PR does not grant PR7 graph-write authority or enable PR9 peer messaging.
• Focused Rust and frontend checks passed, but packaged/rendered WDIO acceptance and screenshots were not rerun for this clean-history rebuild. The PR remains Draft until that risk-proportionate UI evidence is completed.

Architecture and performance audit

• Reviewed the relevant ownership, types, FSM integration, persistence, wire, initialization parity, resolver symmetry, naming, and dead-code layers against the two design documents.
• No recursive hierarchy, communication matrix, new virtualization adapter, frontend dependency, polling loop, timer, or subscription was added.
• Store mutations use one bounded spawn_blocking ownership boundary; no latency improvement is claimed from static inspection alone.
• Team payloads remain bounded at 50 Members and 1,225 canonical edges. Runtime capability checks compile into HashSet indexes, and a communication panel renders at most 49 peers.

Verification

Passed:

cargo check -p agent_core --all-targets
cargo clippy -p agent_core --all-targets -- -D warnings
cargo test -p agent_core agent_org_runs                         # 43 passed
cargo test -p agent_core model_update                           # 2 passed
cargo test -p agent_core launch_validation_rejects              # 5 passed
cargo test -p agent_core core::definitions::orgs::tests         # 11 passed
cargo test -p org2 orphan_org_members_do_not_break_standalone_cursor_or_has_more
npm run typecheck
npm run lint -- --quiet
vitest: Agent Org RPC schema, canonical pair helpers, communication panel # 16 passed
vitest: Agent Org Run View store/hooks                              # 23 passed
node --check on the three changed Agent Org E2E/support files
git diff --check

cargo fmt --all -- --check was also run. It reports three pre-existing formatting differences in PR #824 files outside this PR diff:

• core/tools/impls/coding/render_inline_canvas.rs
• core/tools/tests/ui_metadata_tests.rs
• session-persistence/src/turn_window.rs

Not run in this rebuild:

• Packaged Tauri / rendered WDIO Agent Org acceptance
• Live-provider Team launch and crash-recovery walkthrough
• UI screenshots for theme and narrow viewport states

Commit provenance

Cherry-picking and adapting the selected work onto the current PR #824 head produced new commit hashes. The exact mapping is:

Original commit	Commit in this PR	Author	Purpose / adaptation
5738470865863d4364704aa3f9a45326cc4edc5c	b0ceb1df3	Shibo Sheng	Flat Team capabilities, stable Member IDs, immutable capability snapshot, and Team communication UI.
8aa187a70d9b68e88c6cf040b6c523d844b00f3b	ba47fe237	Shibo Sheng	Exact legacy runtime reset and orphan Agent Org Session pagination fix.
f10afc2	2f0abb8da	Neonforge	Reject malformed model-update Members and preserve survivor runtime configuration; adapted so malformed IDs fail before unknown-ID lookup.
e228c83	d6c82b184	Neonforge	Reuse the shared write-path snapshot serializer without taking the rejected read-path changes.
226bdba	a7656df0f	Neonforge	Route store mutations through one spawn_blocking owner.
a40a169	7b99d0f5a	Neonforge	Shared constant, frontend cap mirror, locale copy, and participant naming cleanup.
3413595	335b8ca3b	Neonforge	Separate the empty-ID test from the reserved-ID test without depending on the rejected validator commit.
N/A — new integration commit	d4ab6de9c	Shibo Sheng	Adapt the selected work to the latest PR1 flat snapshot and async store contracts.

Intentionally excluded commits have no corresponding commit in this PR:

• 4ac8568 — excluded because this PR is rebuilt directly on the selected, current PR feat(agent-org): add authoritative Team lifecycle #824 stack instead of using the old merge commit.
• ce3f5d3 — excluded in its entirety; none of its validator, read-path, quarantine, or migration changes are included.

Rollback

The branch can be reverted as a unit before merge. After an exact legacy runtime reset has committed, reverting the application cannot reconstruct discarded old Team run envelopes; recovery is to continue with newly created Team runs. Ordinary Session data is outside the reset scope.