bug: spec-kitty next reports discovery after finalized task board

[robertDouglass]

Observed

During mission release-320-workflow-reliability-01KQKV85, spec-kitty next kept returning the mission-type phase view (discovery) even though the task board was finalized with six planned work packages and later all six WPs were approved/done.

The task status board was authoritative for the implement-review loop; using next would have driven the agent back into the wrong mission phase.

Expected

When a mission has finalized tasks / WPs, spec-kitty next should advance from the task graph and current WP lanes, not from the earlier mission-type phase view.

Impact

Agents following the canonical next --agent loop can be routed to the wrong action after /tasks, causing duplicate discovery/spec work or blocking implementation.

Repro signal

Mission: release-320-workflow-reliability-01KQKV85
Task board: 6 WPs finalized; eventually 6/6 Done.
Observed workaround: ignore next and use spec-kitty agent tasks status --mission ... as authoritative.

[robertDouglass]

Closing as fixed by PR #969 (merged as 0a2c1bc) and released in v3.2.0a10.\n\nRelevant verification from the PR/release line:\n- review-cycle domain and artifact coverage: tests/review/test_cycle.py, tests/review/test_artifacts.py\n- rejection transition coverage: tests/integration/review/test_reject_from_in_review.py\n- fix-mode/canonical pointer coverage: tests/agent/test_workflow_review_cycle_pointer.py\n- finalized task-board routing coverage: tests/next/test_finalized_task_routing.py\n- missing retrospective record coverage: tests/cli/test_agent_retrospect_missing_record.py and tests/cli/test_agent_retrospect_synthesize.py\n- focused smoke coverage: tests/integration/test_implement_review_retrospect_smoke.py\n\nThe PR passed CI, diff coverage, and quality gate before merge; v3.2.0a10 was published to GitHub Releases and PyPI.