Mission Run Overview
Mission Run: Serialise concurrent next advance
Make advancing a mission run serialised: a stale advance is refused with a named reason, never silently re-planned as success; at most one next mutates a run at a time.
Concurrent spec-kitty next invocations on one run are not serialised (#5854), and two overlapping next --result success calls complete whatever step is issued at the second read (#5682). This mission closes both by recording the caller-evaluated step and refusing a stale advance, and by holding a per-run-dir lock across the read-modify-write of the run cursor.
Total Tasks
2
0 planned
In Progress
0
Review
0
Approved
0
Completed
2
100% done
Available Artifacts
📄 Specification: ✅ Available🏗️ Implementation Plan: ✅ Available📋 Task List: ✅ Available🎯 Kanban Board: ✅ Available🔬 Research: ✅ Available
📜 Contracts: ❌ Not created
✅ Checklists: ❌ Not created
🚀 Quickstart Guide: ✅ Available💾 Data Model: ✅ Available