FN-5733: enforce mission completion-gate assertions for live Goals mission

Realize the mission completion-gate contract by surfacing and enforcing structured assertion coverage for milestone completion.

- add milestone rollup signaling for prose-only acceptance criteria and wire it into mission-store completion gating
- update mission execution loop reliability paths so validator-trigger continuity is preserved across completion and startup recovery
- expose the new rollup flag in dashboard mission types/API and show an autopilot warning badge in MissionManager when prose exists without structured assertions
- extend core, engine, and dashboard tests plus mission docs, and add a patch changeset for @runfusion/fusion

Files changed:
 .changeset/fn-5733-mission-completion-gate.md      | 10 +++
 docs/missions-completion-contract.md               | 11 +++
 docs/missions.md                                   |  4 +
 packages/core/src/__tests__/mission-store.test.ts  | 81 ++++++++++++++++++++
 packages/core/src/mission-store.ts                 | 89 ++++++++++++++++++++++
 packages/core/src/mission-types.ts                 |  2 +
 packages/dashboard/app/api/legacy.ts               |  1 +
 .../dashboard/app/components/MissionManager.css    | 42 +++++++++-
 .../dashboard/app/components/MissionManager.tsx    | 22 +++++-
 .../components/__tests__/MissionManager.test.tsx   | 20 ++++-
 packages/dashboard/app/components/mission-types.ts |  1 +
 .../src/__tests__/mission-execution-loop.test.ts   | 23 ++++++
 .../mission-validation-trigger-gap.test.ts         | 41 ++++++++++
 packages/engine/src/mission-execution-loop.ts      | 21 ++++-
 14 files changed, 357 insertions(+), 11 deletions(-)

Fusion-Task-Id: FN-5733

Fusion-Task-Lineage: 259418c6-5404-4773-8fd2-db8d7e9cadd3

docs/missions-completion-contract.md

@@ -6,6 +6,7 @@
 - **Task:** FN-5718
 - **Depends on enforcement behavior from:** FN-5715 (reference implementation of the trigger/recovery path)
 - **Scope:** Product contract and implementation requirements only (no code changes in this task)
+- **Implementation status:** Realized by FN-5733 (loop auto-pass advancement, mission/store guard telemetry, MissionManager label reconciliation)
 
 ## Problem
 
@@ -92,6 +93,11 @@ This keeps completion logic deterministic and consistent with FN-5715 trigger/re
 
 ## UI Reconciliation Requirements (for follow-on engineering task)
 
+✅ Implemented in FN-5733 with MissionManager labels:
+- `Contract assertions (autopilot gate)` + enforced indicator
+- `Feature acceptance criteria (informational)` + not-enforced indicator
+- warning badge when `hasProseButNoAssertions === true`
+
 Target surface: `packages/dashboard/app/components/MissionManager.tsx`
 
 1. **Disambiguate labels**
@@ -120,6 +126,11 @@ Target surface: `packages/dashboard/app/components/MissionManager.tsx`
 
 ## Engineering Acceptance Criteria (follow-on implementation)
 
+✅ Implemented in FN-5733:
+- Auto-pass path now advances `loopState` to `passed` and emits mission event code `feature_auto_passed_no_assertions` while preserving the `validation:passed` emit contract (`"No assertions linked"` summary).
+- Milestone rollup/store guard now exposes `hasProseButNoAssertions` and emits warning mission event code `milestone_missing_structured_assertions` (debounced on transition into condition).
+- MissionManager UI now distinguishes enforced assertion gate vs informational feature acceptance criteria.
+
 1. **Data/model contract**
    - Preserve the canonical relationship: feature-authored criteria -> store-managed assertion -> linked assertion enforcement.
    - If any model/UI metadata is added for enforced-vs-informational badges, it must be backward compatible with existing mission rows.