feat: include Scope in release context

SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: corp-v1-channel-releases
 description: "Use when operating or synchronizing a Corp v1 project's releases channel. Assesses release readiness and, only when the team requests a release, updates the Gondor v1 template source, renders it, pushes a separate branch to Gondor v1, and opens a pull request requiring team approval before deployment."
-version: 1.3.0
+version: 1.4.0
 author: Hermes Agent
 license: MIT
 metadata:
@@ -14,7 +14,7 @@ metadata:
 
 ## Overview
 
-This skill owns release readiness and the controlled release-change workflow for a Corp v1 project. It monitors the project's `general`, `architecture`, `kanban`, `delivery`, and `releases` channels for release implications, but it starts release execution only after an explicit team request.
+This skill owns release readiness and the controlled release-change workflow for a Corp v1 project. It monitors the project's `general`, `scope`, `architecture`, `kanban`, `delivery`, and `releases` channels for release implications, but it starts release execution only after an explicit team request.
 
 Load the global `documentation-docusaurus` skill from `https://gitea.lego-cloud.eu/home-v1-skills-code-agent/documentation-docusaurus` before changing documentation structure, navigation, Markdown/MDX, Docusaurus configuration, or builds.
 
@@ -56,13 +56,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.
 
 ## Release Readiness