feat: route product scope to Scope channel

SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: corp-v1-channel-general
-description: "Use when operating or synchronizing a Corp v1 project's general channel. Correlates verified activity across the project's general, architecture, kanban, delivery, and releases channels; reports overall status, surfaces issues, proposes improvements, and maintains current project-level guidance."
-version: 1.4.0
+description: "Use when operating or synchronizing a Corp v1 project's general channel. Correlates verified activity across the project's general, scope, architecture, kanban, delivery, and releases channels; reports overall status, surfaces issues, and maintains project-level guidance."
+version: 1.5.0
 author: Hermes Agent
 license: MIT
 metadata:
@@ -14,7 +14,7 @@ metadata:
 
 ## Overview
 
-This skill owns project-level awareness and coordination for a Corp v1 project's `general` channel. It monitors the complete same-project channel set—`general`, `architecture`, `kanban`, `delivery`, and `releases`—and turns verified activity into concise overall updates, issue visibility, maintained guidance, and a durable project-documentation backlog of proposed Epics and Features.
+This skill owns project-level awareness and coordination for a Corp v1 project's `general` channel. It monitors the complete same-project channel set—`general`, `scope`, `architecture`, `kanban`, `delivery`, and `releases`—and turns verified activity into concise overall updates, issue visibility, and maintained guidance. Scope owns the authoritative Roadmap, Ideas, Epics, and Features; General may propose improvements and routes them to Scope instead of duplicating records.
 
 It is not a replacement for architecture, delivery, or release ownership. It connects those workstreams, makes their implications visible to the whole project, and routes specialized work to the corresponding channel.
 
@@ -35,17 +35,18 @@ Do not use it to approve architecture decisions, merge or release code, deploy,
 
 ## Approved Information Boundary
 
-Read only the five channels belonging to the same project:
+Read only the six channels belonging to the same project:
 
 ```text
 corp-v1-<code>-general
+corp-v1-<code>-scope
 corp-v1-<code>-architecture
 corp-v1-<code>-kanban
 corp-v1-<code>-delivery
 corp-v1-<code>-releases
 ```
 
-Read enough mapped-channel history to avoid duplicate updates and only new relevant messages from the other four channels since the previous useful synchronization. Never correlate another project's channels.
+Read enough mapped-channel history to avoid duplicate updates and only new relevant messages from the other five channels since the previous useful synchronization. Never correlate another project's channels.
 
 ## Core Responsibilities
 
@@ -188,8 +189,8 @@ General preserves authoritative Epic/Feature identity and Scope lifecycle eviden
 
 ## Synchronization Workflow
 
-1. Confirm the exact project code and five approved channel IDs.
-2. Read new messages from the other four channels and enough `general` history to avoid duplicates.
+1. Confirm the exact project code and six approved channel IDs.
+2. Read new messages from the other five channels and enough `general` history to avoid duplicates.
 3. Separate facts, approved decisions, proposals, unresolved questions, and failed work.
 4. Correlate impact across architecture, Kanban, delivery, and releases.
 5. Inspect Scope navigation, Roadmap, Epics, Features, Ideas, task links, and lifecycle status.
@@ -237,7 +238,7 @@ For completed work include exact evidence such as Discord message IDs, repositor
 
 ## Verification Checklist
 
-- [ ] Only the five same-project channels were inspected.
+- [ ] Only the six same-project channels were inspected.
 - [ ] The update is new, substantive, and deduplicated.
 - [ ] Overall status, issues, and cross-channel implications are accurate.
 - [ ] Proposals are clearly labeled and routed.