root/fusion
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

FN-5645: fix mission autopilot progression to wait for assertion runs

Browse Source 
Fusion-Task-Id: FN-5645

Fusion-Task-Lineage: ed9d2045-2bfe-4070-a7e3-caca010e6cc6
This commit is contained in:
gsxdsm
2026-05-28 23:58:47 -07:00
parent 230efa1cdc
commit b8c8642cae
7 changed files with 229 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/missions.md
View File

@@ -166,11 +166,13 @@ State machine:
Typical flow:
1. Mission is watched
1. Mission is watched (missions created/updated with `autopilotEnabled: true` are watched immediately)
2. Task completion updates feature status
3. If a slice is complete, autopilot activates next pending slice
4. When milestones are all complete, mission transitions to complete
If validation cannot run (unexpected loop state, duplicate trigger, blocked validation, or validator error), Fusion logs a mission `warning`/`error` event with structured metadata so the stuck state is visible in mission events.
## `autopilotEnabled` vs `autoAdvance`
- **`autopilotEnabled`**: primary control for autopilot behavior — enables background monitoring, orchestration, and automatic slice activation when a slice completes. Also triggers auto-planning (converting features to tasks) when a slice is activated.