docs(scope): enforce requested sidebar order

SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: corp-v1-channel-scope
 description: "Use when operating or synchronizing a Corp v1 project's Scope channel. Owns Roadmap, Epics, Features, and Ideas; correlates all six same-project channels; proactively improves evidence-based product scope; and records human approval before work enters Architecture solution design."
-version: 1.3.1
+version: 1.3.2
 author: Hermes Agent
 license: MIT
 metadata:
@@ -62,18 +62,18 @@ Record approver identity, decision evidence, date, resulting status, and conditi
 ```text
 Overview
 Roadmap
-Epics
-  <CODE>-EP-1
-    <CODE>-FT-1
-    <CODE>-FT-2
-  <CODE>-EP-2
-    ...
 Ideas
   <CODE>-IDEA-1
   ...
 Questions
   Q-0001
   ...
+Epics
+  <CODE>-EP-1
+    <CODE>-FT-1
+    <CODE>-FT-2
+  <CODE>-EP-2
+    ...
 ```
 
 The project documentation's **Ways of Working** area must contain a separate first sidebar item named **Scope** explaining the ticket hierarchy, delivery statuses, exact/derived authority, roll-up, blockers, cancellation, dependencies, gates, and evidence rules.
@@ -284,7 +284,7 @@ Requires human approval for:
 
 - [ ] Only the six same-project channels were inspected.
 - [ ] Scope appears immediately before Architecture with its own sidebar.
-- [ ] Sidebar order is Overview, Roadmap, Epics with nested Features, Ideas with child pages, then Questions with child pages.
+- [ ] Sidebar order is Overview, Roadmap, Ideas with child pages, Questions with child pages, then Epics with nested Features.
 - [ ] Ways of Working starts with a separate Scope page explaining the ticket hierarchy and governed statuses.
 - [ ] Ideas and Questions use table-free parent/child pages; no Product Register page exists.
 - [ ] Roadmap distinguishes verified current state from predicted plans.