Remap channels: project-dashboard→feed, add #reports channel

docs/hq/13-TASKBOARD-KANBAN-DYNAMIC-PROJECT-ORCHESTRATION.md

@@ -118,7 +118,7 @@ Format:
 #### Manager (orchestrator)
 - **ONLY writer** of `taskboard.json` (creates, assigns, updates status)
 - Posts orchestration plans to `orchestration-log.md` before delegating
-- Posts orchestration summaries to Discord `#project-dashboard`
+- Posts orchestration summaries to Discord `#feed`
 - Reviews deliverables before marking tasks `done`
 - Reads `project_log.md` for agent status updates
 
@@ -155,7 +155,7 @@ Manager can override the default channel per task.
 | Channel | Purpose | Who Posts |
 |---------|---------|-----------|
 | `#reports` | Final summaries, orchestration distillates | Secretary (primary), Manager |
-| `#project-dashboard` | Orchestration plans, sprint status, kanban snapshots | Manager |
+| `#feed` | Orchestration plans, sprint status, kanban snapshots | Manager |
 | `#technical` | Technical work, analysis results, code | Tech-Lead, Optimizer, NX-Expert, Webster |
 | `#knowledge-base` | Permanent reference data, lessons learned | Any agent |
 | `#announcements` | Major decisions, milestones | Manager, Antoine |
@@ -180,7 +180,7 @@ Manager can override the default channel per task.
 ### Phase 2: Workflow enforcement
 1. Manager HEARTBEAT checks taskboard for stale tasks (in-progress > 4h with no updates)
 2. Secretary HEARTBEAT checks for completed orchestration chains needing condensation
-3. Kanban snapshot posted to `#project-dashboard` by Manager (daily or on-demand)
+3. Kanban snapshot posted to `#feed` by Manager (daily or on-demand)
 
 ### Phase 3: Dashboard integration (later, CEO view)
 1. Dashboard backend reads `taskboard.json` directly