Create a mod called team-dash: a team flow dashboard that opens in a side pane with /team.

WHO AND WHICH DECISION
It is for Solomon, team lead at Mankind Margin, deciding each Monday who is overloaded, what is stuck, and whether we can take on new work this week.
It measures how work flows through the team, not how good each person is. Do not rank people. No leaderboard.

DATA
Read ./data/tasks.csv with columns:
id, title, owner, status (todo | doing | blocked | done), created, started, finished, estimate_hours, actual_hours, type.
Dates are ISO. Re-read every 30 minutes and on /team refresh.

METRICS (compute exactly like this)
- Throughput = tasks finished per week, last 6 weeks
- Cycle time = finished − started, in working days; show median and the slowest 15%
- Work in progress (WIP) per person = tasks in doing + blocked
- Blocked age = days since a blocked task was last started or created
- Estimate accuracy = sum(actual_hours) / sum(estimate_hours) for tasks finished in the last 4 weeks, per type
- Capacity check = this week's committed estimate_hours / 32 hours × people

LAYOUT (top to bottom)
1. Tiles: Throughput this week, Median cycle time, Items blocked, Capacity used %.
2. A 6-week throughput bar chart, one bar per week, in block characters.
3. A row per person: WIP as filled dots against the limit ●●●○, tasks blocked, oldest open task age. Alphabetical, never sorted by output.
4. "Stuck" list: every blocked task older than the threshold, with owner and age.
5. Estimate accuracy by task type ("Design runs 1.6× estimate").

THRESHOLDS
- WIP above 3 for a person: amber. Above 5: red.
- Blocked for more than 2 working days: amber; 5: red.
- Capacity above 90%: amber, with the line "Don't take new work without dropping something."
- Cycle time median up more than 30% against the previous 4 weeks: amber.

INTERACTION
/team opens or closes the pane. /team name shows one person's open tasks. /team stuck shows the stuck list only.

ONE-LINE READ (optional)
One sentence from the model on where the work is piling up and the single conversation to have this week. Give it computed numbers only. Mark it "AI read". It must never describe a person's performance or effort.

GUARDRAILS
Read-only. If a task has no started date, leave it out of cycle time and count it under "missing dates".
Never invent hours. Show the date range on the header.
Write a test with a fixture CSV that checks median cycle time, WIP counts and blocked age.
