perf(rpc): performance + async lifecycle closure

[beruro]

Summary

Performance, lifecycle, and product-state closure across RPC, CLI/Rust agents, Team Inbox, onboarding, workstation/browser state, and shared UI ownership. The uncommitted work was audited and split into seven logical commits, then merged with origin/develop@82dc871e.

Added commit batches

• refactor(ui): consolidate shared component ownership
• feat(team-inbox): unify assignments and mentions
• feat(onboarding): streamline cloud entry and star prompt
• fix(session): preserve intent lifecycle and canvas isolation
• perf(runtime): bound caches, scans, and background work
• fix(workstation): restore terminal and replay state
• chore(runtime): add profiling contracts and audit gates
• merge: update branch to latest develop

Audit

• Architecture audit: pass with documented CLI intervention-atomicity limitation
• Frontend UI audit: 8 fixes, 8 keep-with-reason, 0 abstraction candidates
• Performance guard: code/lifecycle checks pass; real Tauri runtime measurement remains blocked/not collected
• Component boundaries: pass, 16 tracked legacy violations and no new violations

Reports are under:

• docs/architecture-audit-2026-07-27/
• docs/frontend-ui-audit-2026-07-27/
• docs/org2-performance-guard-2026-07-27/

Verification

• pnpm typecheck
• targeted ESLint over merge-touched frontend files
• focused post-merge frontend regression: 17 files / 118 tests
• changed frontend regression before develop merge: 33 files / 214 tests
• cargo check --workspace --all-targets --offline
• cargo test -p search --lib --offline: 52 passed
• cargo test -p org2 --lib --offline: 994 passed / 1 ignored
• changed Rust rustfmt --check
• git diff --check
• real Tauri visible/hidden/streaming/reopen performance measurement

Remaining risk

The CLI path still accepts a turn receipt before a separate best-effort Agent Org intervention call; it is not atomic with intervention persistence. The performance report therefore does not claim a runtime-measurement pass.