Skip to content

[Multiplayer UI] Land the mission-centered collaboration foundation #313

Description

@Bakar404

Outcome

Land the bounded mission-centered collaboration slice already implemented in draft PR #306, with its exact local validation and screenshots. This issue records one existing implementation, not a request to rebuild it.

Parent feature: #246 (U7), under epic #239. Partial traceability: U7 acceptance items 3 and 5; contributes to item 6 but does not complete cross-user parity.

Current evidence

Draft PR #306 at e421377a49a6f1d3fbf3a3f71d00e20eba5e3f82: one commit, nine files. Dated evidence report.

273 frontend tests and 547 Rust tests passed at the recorded pre-commit checkpoint; 323 Rust tests were explicitly ignored. Web build/lint, migration checks, formatting and Clippy passed. An owned local PostgreSQL/API/runner/browser fixture exercised Alice/Bob/Eve development actors, comments, scoped drafts, control transfer, steering, independent outcome review, artifact authorization and restart. This is not production sign-in, independent real-user/provider identity, cross-owner execution or physical-device acceptance.

The implementation is published as a draft, not merged or accepted for full U7. Hosted CI was not reassessed at the initial planning preview. At issue creation, all six CI checks for the exact PR head are confirmed passed: quality, integration, Linux/Windows/macOS runner platforms, and desktop-windows. CI run. This does not change the draft/review boundary.

Acceptance criteria

  • Review and land the exact bounded implementation in feat(web): add mission-centered multiplayer collaboration #306, or an explicitly reviewed successor; preserve recorded source/evidence provenance.
  • Mission context shows requester/viewer, task and agent assignments, truthful runner/controller state, and exact-run navigation through existing controls.
  • Missions and Comms share Corp/actor/room/mission-scoped in-memory drafts; late responses cannot erase newer generations. No persistence across reload is promised.
  • Missing selected missions remain unavailable rather than selecting another mission; empty legacy descriptions retain a briefing destination.
  • Disconnect handling does not infer human presence or promote stale state to current control authority.
  • Retain the focused tests, exact repository gate results and desktop/390px screenshots; resolve applicable PR findings before integration.
  • Keep [Feature] Multiplayer UI: collaboration and single-user parity (U7) #246 and [Epic] True multiplayer: shared ECorp web app and control plane across users and agents #239 open after this task lands. This task closes on merge of its linked implementation PR, not merely on draft publication.

Why this is a separate issue

#246 owns the complete multi-surface U7 outcome. This child owns the already-delivered nine-file slice, allowing a small PR to link to a precise implementation task without closing the parent feature.

#145 remains the broader operating lane and contextual notifications/control-request work. #259 / PR #265 own richer run activity and freshness; #260 owns source/diff review; #266 owns HeroUI. No existing issue is reparented or superseded.

Delivery and safety boundary

Planning/tracking only. Use the existing ECorp Build Project #5; keep this issue unassigned and without factory:ready. A placeholder is not an execution-ready contract. Refine the exact source, file scope, prerequisites, native-capability checks and verification policy before implementation.

Preserve the centralized floor, existing agent-inspector modal and existing five workspace routes. Reuse the authoritative server/Corp/room state, native harnesses, owner-controlled runners, control leases, approved command paths and signed artifacts. Comments, steering, task submission, action approval, outcome review and publication remain distinct.

No new identity/message/memory store, scheduler, agent mesh, implicit cross-owner execution, credential transfer, automatic dispatch, cloud deployment, review request, merge or auto-merge. Preserve existing issue ownership, Factory lineage, source checkouts, credentials, worktrees and failed evidence. Keep PR #306 draft; the author owns readiness and the ecorp-team review request.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:webWeb and desktop experiencemultiplayerMulti-human realtime behaviorui-uxActual ECorp console user experience workstream

    Type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions