Mission Run Overview
Mission Run: Topology-Aware Legacy Warning
The legacy-topology migration warning stops over-firing on intentional coordination-less (single_branch/lanes) missions.
Issue #2351 (bug): _is_legacy_mission() keys on coordination_branch absence, but single_branch/lanes topologies intentionally omit it (per #2218), so new coordination-less missions are misclassified as legacy and shown a migration warning they don't need. Fix: make the warning read the stored MissionTopology (SSOT per the topology-ssot ADR) — warn only when coordination_branch is absent AND topology is null/absent AND not flattened. Write-path routing is unchanged. Coupled runbook update to docs/migrations/legacy-to-coordination.md.
Total Tasks
1
0 planned
In Progress
0
Review
0
Approved
0
Completed
1
100% done
Available Artifacts
📄 Specification: ✅ Available🏗️ Implementation Plan: ✅ Available📋 Task List: ✅ Available🎯 Kanban Board: ✅ Available🔬 Research: ✅ Available📜 Contracts: ✅ Available
✅ Checklists: ❌ Not created
🚀 Quickstart Guide: ❌ Not created
💾 Data Model: ❌ Not created