docs(multiplayer): map U7 parity requirements to evidence

[Bakar404]

Description

Map all six original U7 acceptance items to implementation owners, inspected source,
reusable regressions and the evidence still required. This is a one-file
documentation/verification-design PR, not completed U7 acceptance or a second backlog.

Refs #316; part of #246 and #239. Keep all three issues open for their full acceptance.

• Source base: main 30ec3fab6acd566cc1fc1e574c8a6343d0ce0596.
• Head: 81d07b0659f9ee911755a120be97ae2dce5c3be2.
• Branch: codex/issue-316-parity-map -> main; no stacked parent.
• Only changed file: docs/multiplayer/U7_PARITY_MATRIX.md (216 lines).
• No runtime, backend, UI, migrations, dependencies or lockfile changes relative to main.
• Includes landed feat(web): surface Factory run activity, freshness, and blockers #265 activity/freshness, fix: reject incompatible Factory cost budgets before claims #307 cost preflight, fix(server): validate startup configuration before migrations #288 startup,
  fix(store): prevent steering and runner status deadlocks #290 steering, docs: add the contributor pull-request template #278 template and docs: correct migrated repository and planning links #275 planning guidance. Separately pins PR feat(web): add mission-centered multiplayer collaboration #306's
  tested UI candidate 9df9f072467040e16561db9073908108d880c801 and fresh evidence.
• Either PR can land independently: this map explicitly distinguishes the unmerged
  collaboration candidate from main. It does not import that code or claim it landed.

Type of change

• Documentation update

How Has This Been Tested?

• Document audit: AC1–AC6 coverage, 30 reference definitions, 19 immutable Git blob
  links, and 18 local links/heading anchors verified. Current protocol fields and
  native MCP request entry point inspected; no accidental closing references.
• node --experimental-strip-types --test apps/web/src/*.test.mjs apps/web/src/office/*.test.mjs: 279 passed on this main-based branch.
• node tools/check_migrations.mjs: passed, 41 immutable migrations unchanged.
• cargo fmt --check: passed.
• cargo clippy --workspace --all-targets --offline --locked -- -D warnings: passed.
• cargo test --workspace --offline --locked -- --quiet: 554 passed, 343 ignored, zero failures (ignored: 1 runner, 5 server, 337 store).
• pnpm build:web, pnpm lint:web and committed whitespace checks: passed.

No browser/server/runner rehearsal was executed by this documentation change.
The map links the separate #306 candidate's actual native local rehearsal and
screenshots, with source/identity/provider limits retained. Historical hosted CI
is not represented as a pass for either new head. The map's audit helper remains
operator-local under ignored output; it is not a production dependency.

Test Configuration:

• Firmware: N/A.
• Hardware: Windows ARM64; isolated contribution worktree.
• Toolchain: Node 24.19.0, pnpm 11.19.0, Cargo 1.98.1; locked/offline Rust gates.
• SDK: No harness/provider changes or real inference.

AI agent integration handoff — UI/backend dependencies

• This documentation PR has no unmerged backend prerequisite. It records main
  and separately pins the unmerged feat(web): add mission-centered multiplayer collaboration #306 source; a reference is not acceptance.
• [Multiplayer UI] Select shared machines and agents using authoritative readiness #314/[Multiplayer UI] Carry shared launch context across web, CLI, Factory and gateways #315 require Multiplayer U5: synchronize authorized repositories safely across runners #244/Multiplayer U6: make scheduling capacity- and ownership-aware #245 source-readiness and ownership/capacity-aware
  scheduling contracts, which remain pending and depend on Multiplayer U3: complete browser sign-in, invitations, and member management #242/Multiplayer U4: deliver machine join and owner-controlled agent import #243.
• Multiplayer U3: complete browser sign-in, invitations, and member management #242 is blocked on its explicit browser-auth review decision. Existing OIDC,
  synthetic actors, open OBO Human-delegated protected-resource jobs with Entra OBO adapter (#285) #320 and isolated preflight Define multiplayer development gates and isolated U1 preflight #319 do not resolve it.
• Before consumer implementation, read current contributor/product/security/eval
  guidance and both backend/UI changes. Pin actual contracts, status enums,
  nullability, ordering, scope/error/idempotency semantics and landing order.
• Reuse the existing runtime, snapshot coalescer, control/approval paths, feat(web): surface Factory run activity, freshness, and blockers #265
  exact-run/freshness behavior and owned fixtures. Never invent API fields or
  bypass native authority because a UI element exists.
• [Multiplayer UI] Verify U7 multi-actor and single-user parity on the integrated candidate #316 still requires independent authenticated identities, revoked/open-client
  cases, cross-owner/source/scheduling cases, complete consumer parity and a
  reviewed evidence verdict. Keep [Multiplayer UI] Verify U7 multi-actor and single-user parity on the integrated candidate #316/[Feature] Multiplayer UI: collaboration and single-user parity (U7) #246/[Epic] True multiplayer: shared ECorp web app and control plane across users and agents #239 open.

Checklist:

• Follows current CONTRIBUTING.md and PR template
• Self-reviewed source references and evidence claims
• Preserves the original acceptance criteria and dependency ownership
• Adds no runtime behavior or schema
• Document audit and all six repository gates pass; ignored cases are explicit
• No unmerged runtime work or historical CI is claimed as current acceptance

Ready for All-The-Vibes/ecorp-team review under the author's current approval.
Required human review remains outstanding. No issue closure, dispatch, merge,
auto-merge or deployment is authorized by this publication.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[shyamsridhar123]

Reviewed commit 81d07b0659f9ee911755a120be97ae2dce5c3be2 against current main 30ec3fab6acd566cc1fc1e574c8a6343d0ce0596 and the product, architecture, security, and evidence contracts.

The matrix faithfully maps all six original U7 acceptance criteria, separates current-main capabilities from the unmerged #306 work, and keeps #239/#246/#316 and the #242 production-identity gate open. Checked the 19 immutable source references and 18 local path/anchor references. No blocking findings for this documentation-only change.

Validation on the reviewed revision: migration integrity, Rust formatting, all-target workspace Clippy with warnings denied, full workspace tests (554 passed; 343 intentionally ignored), web build/lint, and 279 frontend tests passed. An initial runner regression failed because Git exceeded Windows path limits; the unchanged focused test and complete workspace rerun passed using a shorter isolated temporary root. Web dependencies retained their locked versions and integrity hashes; only tarball locations in an isolated fixture were translated to the verified mirror. All 11 hosted checks are successful, with no unresolved review threads or open code-scanning alerts. This review does not claim runtime acceptance or completion of the broader U7 feature.

[Bakar404]

Adam's contract handoff is addressed by PR #322, a one-file follow-up because #321 merged while the approved update was pending. It pins proposed MP1 source 6fe6668, maps U7 acceptance to its new test families, and separates G0-after-adoption from runtime/release gates. No spec adoption or runtime authorization is claimed. All six local repository gates and the link audit passed for the documentation candidate; prior UI evidence retains its original scope. The five still-open affected issue handoffs were updated. PR #306 has since merged and #313 closed through the team process, so their history was preserved and the AI integration follow-up was posted as a comment on #306 instead. No ownership, Project status or backend dependency was changed by this batch.