fix: clarify mission control progress blockers

[ozand]

Summary

Fixes two Mission Control truth gaps found by the repeat live semantic audit.

Closes #452.
Closes #453.

Changes

• Treat every terminal latest subagent result (blocked, failed, error, etc.) as blocker evidence in Mission Control, even when the material-progress proof list contains only other qualifying proofs.
• Preserve canonical material-progress state from /api/system in /api/mission-control.last_material_progress instead of coercing explicit states such as proven to available.
• Add unambiguous material-progress projection fields:
  • canonical_state
  • available
  • blocking_reason
  • source_reason
  • reason_mismatch
• Add regressions for the live Mission Control must mark blocked latest subagent as blocker evidence #452/Mission Control material-progress state must match canonical system truth #453 shapes and reviewer-found edge cases.

Verification

Local:

Focused tests: passed
ops/dashboard tests: 164 passed
git diff --check: passed
root tests: 694 passed, 5 skipped

Subagent review:

• Delegated code-path analysis for Mission Control must mark blocked latest subagent as blocker evidence #452 and Mission Control material-progress state must match canonical system truth #453 before implementation.
• Delegated diff review after first green suite.
• Review found three edge cases; added RED regressions and fixed them before PR.

Live proof plan after merge

• Restart dashboard services.
• Run /collect.
• Fetch /api/mission-control, /api/system, /api/plan, /api/hypotheses, /api/experiments, /api/analytics, /api/subagents.
• Assert:
  • blocked latest subagent is blocker evidence;
  • blocked latest subagent is not material progress;
  • Mission Control material-progress state matches canonical system truth;
  • previous Mission Control must name concrete blocker instead of Blocked: unknown #446-Mission Control must not fabricate hypothesis identity from task id #450 invariants still pass.