docs(playability): aggregate P1 and define staged P2

[blakinio]

Purpose

Aggregate the four merged and separately archived P1 contract producers, reconcile live architecture/capability/dependency state, and publish the smallest safe staged P2 minimum-visible-world wave.

Delivered scope

• durable P1 aggregation task;
• refreshed architecture handoff, capability matrix and dependency/parallelism model;
• staged WAVE_P2_MINIMUM_VISIBLE_WORLD.md;
• six bounded implementation prompts plus one separate controlled M2 acceptance prompt;
• explicit Canary development-baseline reconciliation for generated bc0068ab… evidence versus older runtime descriptor cuts;
• one simulation/snapshot producer, one Canary gameplay adapter, one asset decoder, one renderer-resource producer, one input-platform adapter, one serialized visible-world integration owner and one controlled runtime acceptance owner.

Material findings

P1-AGG-CANARY-REVISION-001

protocol-canary still names runtime source cuts 95b276db… / 4b2d6f43…, while the merged P1 generated source index is pinned to bc0068ab….

Disposition: P2 CANARY-WORLD-PROTOCOL must mechanically align the development descriptor/tests to the generated index before gameplay parser work, preserve real admission fail-closed and leave unsupported field layouts explicit. The inspected cut is not treated as deployed without controlled evidence.

P1-AGG-M2-ASSET-CLAIM-001

Fresh acceptance audit found that the first draft allowed a synthetic visual boundary to be interpreted as sufficient for controlled M2_PASS.

Disposition: repaired. Synthetic visual runs are partial technical evidence only. M2_PASS requires an approved compatible appearance source, provenance/rights boundary, exact runtime-pack identity and visibly correct controlled world.

Claim boundary

This PR authorizes no Rust implementation, staging access, credentials, deployment, production assets or M2 completion claim. Synthetic visible-world composition remains a partial consumer. M2 requires a separate controlled login -> visible world -> semantic movement -> server reconciliation -> safe logout acceptance on an exact named environment and compatible runtime pack.

Exact-head validation

exact_head: be59ec0f7583f03c5b8b948b477b22ccb0cf5f7e
exact_base: 5d3dec1037eef508782e369afef8e3b7f1291e6a
behind_by: 0
changed_paths: 12
unexpected_paths: 0
temporary_workflows_retained: false
product_code_changed: false
implementation_authorized: false
rust_client:
  run: 30772190456
  windows_job: 91561164137
  supply_chain_job: 91561164122
  result: PASS
repository_ci:
  run: 30772190563
  required_job: 91561261981
  result: PASS
comments: 0
reviews: 0
review_threads: 0

Windows exact-head validation passed locked metadata, pinned rustfmt, strict workspace Clippy, complete workspace tests and architecture policy. Supply Chain and repository CI / Required passed.

Temporary assertion-guarded workflows removed themselves before the final head:

• living-contract patch trigger 30772041402: PASS;
• initial patch attempt 30772003133: failed only on five new Markdown trailing-space line breaks and was causally repaired before commit;
• M2 asset-claim repair 30772143467, job 91561025436: PASS.

Content audit

• all four P1 producer and archive merge records reconciled;
• P1 evidence states moved only within exact synthetic/source/framework-neutral boundaries;
• sole-producer ownership and dependency directions are non-overlapping;
• initial P2 concurrency is simulation, Canary protocol, asset decode and input platform;
• renderer-resource follows asset-decode;
• visible-world integration follows all five producer archives and alone owns final app composition;
• controlled M2 acceptance remains a separate operational/runtime gate and requires compatible appearances;
• PR feat(ui): prototype Oteryn login shell #23-owned shared catalogue paths remain excluded;
• zero open material finding after both repairs.

Closeout

Ready for protected merge. After merge, create and merge the mandatory separate lifecycle archive; only the archived barrier authorizes launching the first P2 producer.

Task

OTC2-20260803-playability-p1-aggregation