feat: consume approved Scope features

SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: corp-v1-channel-architecture
-description: "Use when operating or synchronizing a Corp v1 project's architecture channel. Maintains C4-based architecture documentation, Draw.io diagrams, architecture decisions, and functional/non-functional requirement registries while correlating verified activity across the project's five channels."
+description: "Use when operating or synchronizing a Corp v1 project's architecture channel. Maintains C4-based architecture documentation, Draw.io diagrams, architecture decisions, and requirements while correlating verified activity across the project's six channels."
-version: 1.3.0
+version: 1.4.0
 author: Hermes Agent
 license: MIT
 metadata:
@@ -14,7 +14,7 @@ metadata:
 
 ## Overview
 
-This skill owns the solution phase and architecture coherence for a Corp v1 project. It monitors the project's `general`, `architecture`, `kanban`, `delivery`, and `releases` channels, transforms human-approved Features into requirements and solution artifacts, breaks them into dependency-aware implementation tasks, assigns approved Features to versions, and maintains the Architecture section of the project documentation.
+This skill owns the solution phase and architecture coherence for a Corp v1 project. It monitors the project's `general`, `scope`, `architecture`, `kanban`, `delivery`, and `releases` channels, transforms human-approved Features into requirements and solution artifacts, breaks them into dependency-aware implementation tasks, assigns approved Features to versions, and maintains the Architecture section of the project documentation.
 
 The default architecture model is C4. Architecture diagrams must be authored and validated using the global `drawio-main` skill from:
 
@@ -49,7 +49,7 @@ Only Features explicitly marked `Approved for Solution` by a human team member m
 
 Hermes participates proactively in analysis and artifact creation but cannot satisfy either gate:
 
-1. **General → Solution:** a human team member explicitly approves an Epic/Feature for solution work.
+1. **Scope → Solution:** a human team member explicitly approves an Epic/Feature for solution work.
 2. **Solution → Implementation:** after requirements, architecture, tasks, dependencies, and version allocation are reviewable, a human team member explicitly approves the Feature for implementation.
 
 Record approver identity, decision message or documentation reference, date, and resulting status. Silence, an agent statement, CI success, or an old informal discussion is not approval.
@@ -60,13 +60,14 @@ Inspect only:
 
 ```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
 ```
 
-Use mapped-channel history to avoid duplicate work and new relevant activity from the other four channels. Never inspect another project's channels.
+Use mapped-channel history to avoid duplicate work and new relevant activity from the other five channels. Never inspect another project's channels.
 
 ## Architecture Documentation Contract
 
@@ -255,7 +256,7 @@ Requires team approval for:
 
 ## Verification Checklist
 
-- [ ] Only the five same-project channels were inspected.
+- [ ] Only the six same-project channels were inspected.
 - [ ] Architecture documentation reflects verified status.
 - [ ] C4 scope and level are appropriate.
 - [ ] `drawio-main` governed every diagram change.