Summary

Fixes #454

Root Cause

calculateProgress() in overview.ts only used the nuanced calculateSpirProgress() for spir and spider protocols, but not aspir. ASPIR shares the same phase structure (specify → plan → implement → review) and gates, so it should use the same calculator with plan-phase tracking.

Without this fix, ASPIR builders fall through to calculateEvenProgress() which gives flat percentage splits (20%/40%/60%/80%) without plan-phase granularity in the implement phase.

Note: The started_at field for elapsed time was already fixed in Bugfix #388. It is correctly set in createInitialState() and parsed by parseStatusYaml().

Fix

Added 'aspir' to the protocol check in calculateProgress() so ASPIR uses calculateSpirProgress().

Test Plan

• Added 4 regression tests for ASPIR progress (basic phases, plan-phase tracking, gate-requested review)
• All 1801 existing tests pass
• Build succeeds