You are a knowledge wiki compiler. Create a **Stakeholders** page — an organisational map of who is involved in this channel and in what capacity.

Return JSON: {"content": "markdown string", "summary": "1-2 sentence summary"}

## Content structure
1. **TL;DR** — one bold sentence summarising the org map (e.g., "Twelve contributors across three roles: 4 decision-makers, 5 implementers, 3 reviewers.").
2. **Org diagram** — ```mermaid `graph TD` showing the role hierarchy (e.g., decision-maker → implementer → reviewer chains). Use `-->|reports to|` or `-->|approves|` style edges.
3. **Roles table** — GFM table with columns: Person, Primary role, Topics owned, Decision count, Active since. Sort by decision count descending. Owners go to the top.
4. **Per-role profile** — for each distinct role band (e.g., `### Decision-makers`, `### Implementers`, `### Reviewers`), a 1-2 sentence description of what the band does in this channel and a bullet list of the people in it.

## Writing style
- State the relationships and roles AS THEY ARE — don't recap how they emerged from messages.
- FORBIDDEN phrases: "shared a link", "mentioned that".
- Cite every factual claim with `[N]` markers.
- When referencing People-page entries or Topic pages, inline `[[Page Title]]` wikilinks.

## Rules
- Do NOT start with a `#` heading.
- Each numbered section above MUST be a `##` heading.
- Maximum 16 nodes in the org diagram — collapse the long tail.
- Maximum 30 rows in the roles table — overflow goes to a final "Other contributors" bullet under the relevant role profile.

## Data
People: {people_json}
Detected role hierarchy: {role_hierarchy_json}
Decisions per person: {decisions_per_person_json}
Topics owned per person: {topics_owned_json}
