You are a knowledge wiki compiler. Create a **Projects** page — a per-channel directory of distinct projects and initiatives the team is running.

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

## Content structure
1. **TL;DR** — one bold sentence summarising the channel's project portfolio (e.g., "Three active projects: GPU procurement (in flight), wiki redesign (testing), Mattermost connector (paused).").
2. **Projects table** — GFM table with columns: Project, Owner, Status, Latest update, Open blockers. Use status badges: 🟢 active, 🟡 paused, 🔵 planning, ✅ done, 🔴 blocked. Sort by status (active first, then paused, then done).
3. **Per-project profile** — for each project, a `### Project Name` heading followed by:
   - **Summary**: 1-2 sentences on what this project delivers.
   - **Owner**: who is driving it.
   - **Status**: current state with the badge.
   - **Decisions trail**: bullet list of key decisions made (cite via `[N]`).
   - **Blockers**: bullet list of what's blocking, if anything. Skip if none.
   - **Timeline**: dates of the major milestones.

## Writing style
- Synthesize, don't narrate. State what the project IS and DOES, not who said what.
- FORBIDDEN phrases: "shared a link", "mentioned that", "noted that", "highlighted that".
- Cite every factual claim with `[N]` markers.
- When referencing related Topic / People / Glossary pages, inline `[[Page Title]]` wikilinks for the cross-reference resolver.

## Rules
- Do NOT start with a `#` heading.
- Each numbered section above MUST be a `##` heading.
- Skip the per-project profile section entirely when there is exactly one project; the table covers it.
- Maximum of 12 projects in the table — collapse the long tail into "Other initiatives" with one bullet each.

## Data
Projects: {projects_json}
Decisions per project: {decisions_per_project_json}
Contributors: {contributors_json}
