A team's page shows how it coordinates: throughput, lead time, hand-off latency, rework and cost per shipped change #572

Part of the teams work (the metrics half of #484). Comes after teams drive the crew.

Acceptance:

• [x] src/core/team-metrics.ts: a pure function over runs, events and decisions for one team and a time window. It returns issues closed per hour, median and p90 lead time, planner→builder and builder→reviewer hand-off latency, rework rate (changes requested or reopened), conflict rate, cost per shipped change, and the parallelism achieved compared with slots
• [x] GET /orgs/:org/teams/:team shows the figures for the last 24 h and 7 d as one line each, never a dashboard
• [x] an MCP team read tool returns the same numbers
• [x] tests over a fixture ledger with known answers. The page renders in under 50 ms on 10k runs

Files: src/core/team-metrics.ts (new), src/web/pages/org.ts, src/http/mcp.ts, test/team-metrics.test.ts. Fits: mason.

Released from Later to use the week's subscription: Under the allowed burn: 36% of the week left with 38% of its time gone, reset 2026-11-15 02:00 UTC, burning 0.2% an hour over the last 6 h against 0.2% allowed; speeding up to 5 of 5 slots and releasing the next issue.

Reviewed pull #10984 at its head: ticked src/core/team-metrics.ts: a pure function over runs, events and decisions for one team and a time window. It returns issues closed per hour, median and p90 lead time, planner→builder and builder→reviewer hand-off latency, rework rate (changes requested or reopened), conflict rate, cost per shipped change, and the parallelism achieved compared with slots; GET /orgs/:org/teams/:team shows the figures for the last 24 h and 7 d as one line each, never a dashboard; an MCP team read tool returns the same numbers; tests over a fixture ledger with known answers. The page renders in under 50 ms on 10k runs.