PT-677 dashboard current cycle

GET 
/api/cycles/current

PT-677 dashboard current cycle. Returns the single "current" active cycle across every project the caller can read in the active org — the nearest checkpoint (soonest endDate, undated cycles last; ties broken by most-recent startDate, then cycle id ascending) since a cycle is one-active-per-project — plus its burndown, or { "data": null } when no readable project has an active cycle. The data source for the dashboard Current Cycle widget. Unlike the other cycle routes this is NOT project-scoped: it requires FULL tasks.read (a tasks.read.own-only caller is rejected — the cycle burndown is a cycle-wide aggregate with no per-assignee dimension to scope to; like the project-scoped burndown route, a bare tasks.read.own grant is rejected) AND projects.read | projects.read.own plus an active membership; a GUEST / projects.read.own caller is restricted to collaborator/creator projects. Archived (COMPLETED / CANCELLED) projects are excluded.

Request

Responses

200

Successful response

400

Bad Request — no active organisation in context

401

Unauthorized — no authenticated user

403

Forbidden — requires full tasks.read and projects.read | projects.read.own plus an active membership. The { error: { code, message } } envelope variant is the x-act-as-org non-member guard from the shared tenant handler.