docs: define simple dual-host MI50 development workflow

[GionaGranchelli]

Summary

Document a minimal two-host development workflow for the current single-MI50 roadmap.

The two systems are:

• mi50-a: HP Z840 + MI50 32 GB
• mi50-b: Machinist X99 + MI50 32 GB

Key decision

Before running roadmap work in parallel, establish one reproducible OCI-based gfx906 development environment that can run on both hosts via Podman or Docker.

The shared environment should pin the MIInfer userspace/toolchain, ROCm/HIP userspace and compiler, build dependencies, benchmark tooling, model hash, benchmark inputs and relevant environment variables. Host-specific kernel/CPU/PCIe/cooling characteristics remain recorded evidence rather than pretending the physical systems are identical.

Parallel workflow

After environment parity passes:

• mi50-a starts M29.0 long-context baseline
• mi50-b starts M29.0A gfx906 external-reference calibration
• when M29.0A closes, mi50-b can move to M29.1 HIP-VMM feasibility

Codex workstreams use small goal packets with host, base SHA, branch, scope, evidence and exit condition. Performance comparisons remain same-host A/B; shared architectural contracts are frozen before dependent work is split.

Scope

Documentation only. No scheduler, orchestration service, distributed runtime, or new implementation framework is introduced.

Next implementation goal

Create and qualify the shared OCI gfx906 environment on both Z840 and Machinist. Parallel M29 work starts only after both hosts pass the same smoke/baseline contract.

[Copilot]

Copilot review overview

🟢 Approval recommended

The changes are documentation-only, internally consistent, with correctly resolving links and milestone references that match the existing roadmap.

Review effort: Balanced
Findings: None

What changed in this PR

This PR adds documentation describing a minimal two-host MI50 development workflow for the current single-MI50 roadmap. It introduces a new docs/parallel-development.md guide and links to it from both docs/roadmap.md and AGENTS.md. The workflow emphasizes establishing one reproducible OCI-based gfx906 environment on both hosts (mi50-a: HP Z840, mi50-b: Machinist X99) before any parallel M29 work begins, and enforces same-host A/B performance comparisons. It is purely documentation — no scheduler, orchestration, or distributed runtime is introduced, consistent with the project's scope constraints.

Changes:

• Add docs/parallel-development.md defining the two-host prerequisite environment-parity gate, parallel work rules, initial M29 split, and end-of-phase consolidation into one machine for V3.
• Add a paragraph in docs/roadmap.md requiring a shared reproducible environment before splitting M29 work, with a link to the new doc.
• Add section "35. Parallel MI50 development" to AGENTS.md summarizing the two-host rules and linking to the new doc.

File	Description
docs/​parallel-development.md	New guide detailing the dual-host workflow, environment-parity exit gate, same-host A/B comparison rules, and milestone phasing.
docs/​roadmap.md	Adds a paragraph gating parallel M29 work on a shared reproducible environment and links to the new workflow doc.
AGENTS.md	Adds section 35 summarizing parallel MI50 development rules and referencing the new doc.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.