[Direction]: Operator surface and IM integration

[huangruiteng]

Outcome

Make long-running agent work legible and operable through a coherent personal
workspace, control-plane projections, session records, and bounded IM/Lark
integration. The UI renders LoopX state; it must not become a second goal,
todo, quota, or authority store.

Current stage

Incubating on an integration branch; not shipped from main.

• Integration branch:
  frontend-control-plane-im-prototype-rfc
• Current primary implementation package:
  #3167, led by
  @maxliux5
• Event-driven control-plane proposal under requested changes:
  #3200
• Lark subsystem review route:
  @steven-kid, within the scope recorded in
  project governance and CODEOWNERS

The lead maintainer retains mainline promotion, cross-subsystem contract, first
screen, release, and repository-governance decisions.

Promotion ledger

Promote behavior to main as independently reviewable units rather than
merging the incubation branch as one permanent parallel product:

1. characterize shared projection and session contracts with focused fixtures;
2. isolate provider-neutral backend and chat/receipt boundaries;
3. promote cohesive runtime or projection slices with parity checks;
4. promote operator UI only after its source projections and authority
   boundaries are stable, with owner preview for first-screen changes;
5. keep Lark credentials, provider payloads, private receipts, local paths, and
   raw sessions outside public fixtures and browser state.

Contributor-ready cuts

• projection parity, deterministic fixtures, accessibility, and localization;
• bounded UI components built from existing public-safe projections;
• session-record recovery and error-state tests;
• narrow IM/Lark readback, retry, idempotency, and routing improvements within
  the existing extension boundary.

Before starting, comment with the intended base branch and promotion unit.
Work targeting this incubator should not silently target main, and work meant
for main should not depend on an unpromoted branch-only contract.

[huangruiteng]

Direction governance is now merged in
#3248.

• Canonical map: English · 中文
• Pinned community projection: Discussion #2851
• Claimable work: Contributor Task Board

This issue remains the long-lived direction and decision tracker. Concrete
implementation should use a separate bounded issue or task-board row with an
explicit base branch, smallest slice, non-goals, and validation plan.