Run the schedule health check on a project (a 0-100 score and its issues)

Read-only, every plan, no AI call. The same computation as the MCP tool schedule_health_check: { projectId, projectName, score, severity (info|warning|critical), taskCount, issues, freshness, generatedAt }, where each issue is { severity, category, message, affectedTaskIds } (ids capped at 50). This route adds, on each issue, code (end_overrun, overdue, unassigned, near_done, blocked or stale) and count (every task the signal matched), and datedTaskCount on the report (tasks with a start or a due date). Needs read access to the project; otherwise 404.