docs: reference shared channel workspace standard

SKILL.md

@@ -1,16 +1,16 @@
 ---
-name: corp-v1-channel-scope
+name: channel-scope-skic
 description: "Use when operating or synchronizing a Corp v1 project's Scope channel. Owns Roadmap, Epics, Features, and Ideas; correlates all eight same-project channels; proactively improves evidence-based product scope; and records human approval before work enters Architecture solution design."
-version: 1.8.0
+version: 1.8.1
 author: Hermes Agent
 license: MIT
 metadata:
   hermes:
     tags: [corp-v1, discord, channel, scope, roadmap, epics, features, discovery]
-    related_skills: [corp-v1-main, home-v1-discord, documentation-docusaurus, corp-v1-glossary]
+    related_skills: [channel-board-skic, home-v1-discord, documentation-docusaurus, corp-v1-glossary]
 ---
 
-# Corp v1 Scope Channel
+# SKIC Scope Channel Reference
 
 ## Overview
 
@@ -28,7 +28,7 @@ Load the global `corp-v1-glossary` skill from `https://gitea.lego-cloud.eu/home-
 
 ## Shared Corp v1 System Login
 
-When an authorized task requires login to a Corp v1 system being built or operated, follow the shared policy in `corp-v1-main` and use only the Bitwarden-injected runtime secrets named:
+When an authorized task requires login to a Corp v1 system being built or operated, follow the shared policy in `channel-board-skic` and use only the Bitwarden-injected runtime secrets named:
 
 ```text
 HL_V1_SSO_EMAIL
@@ -41,7 +41,7 @@ Secret availability is capability, not authorization. Verify the destination ori
 
 Use this skill when:
 
-- operating in `corp-v1-<code>-scope`;
+- operating in `<code>-scope`;
 - running its recurring synchronization job;
 - maintaining Overview, Roadmap, Epics, Features, canonical Task reader pages, Ideas, or Questions;
 - discovering user/project problems and opportunities;
@@ -53,19 +53,19 @@ Do not use it to design architecture, approve solution entry, approve implementa
 
 ## Approved Information Boundary
 
-Follow the eight-channel topology in `corp-v1-main`, approved by Board message `1552966246591365123`; include UAT between Delivery and Releases. Verify mapped IDs and effective access before reading.
+Follow the eight-channel topology in `channel-board-skic`, approved by Board message `1552966246591365123`; include UAT between Delivery and Releases. Verify mapped IDs and effective access before reading.
 
 Inspect only:
 
 ```text
-corp-v1-<code>-general
-corp-v1-<code>-scope
-corp-v1-<code>-architecture
-corp-v1-<code>-ui-ux
-corp-v1-<code>-kanban
-corp-v1-<code>-delivery
-corp-v1-<code>-uat
-corp-v1-<code>-releases
+<code>-general
+<code>-scope
+<code>-architecture
+<code>-ui-ux
+<code>-kanban
+<code>-delivery
+<code>-uat
+<code>-releases
 ```
 
 Read enough Scope history to avoid duplicates and only relevant new activity from the other seven channels. Never inspect or correlate another project's channels.
@@ -393,3 +393,16 @@ Source comparison and exclusions: [AeroSim lessons review](references/aerosim-le
 - [ ] A successful unrequested completion report contains only substantive changes and documentation links; technical delivery evidence appears only on request or for an actionable exception.
 - [ ] When React Flow is used, its graph and semantic table share one canonical-YAML selector and pass accessibility, build, browser, and remote exact-head checks.
 - [ ] Completed work includes exact message, path, commit, URL, or run evidence.
+
+## Canonical naming and compatibility
+
+- Canonical installed and repository name: `channel-scope-skic`.
+- Source: `https://gitea.lego-cloud.eu/home-v1-skills-code-agent/channel-scope-skic`.
+- Previous name: `corp-v1-channel-scope`; retained locally only as a compatibility alias. New guidance and presentations use the canonical name.
+- Naming-only migration authorized by RootAtSkic in [presentation message 1562523679223578705](https://discord.com/channels/1518726359512387766/1543922127898415154/1562523679223578705). Repository ID, history, support files, project authority and organization ownership are preserved.
+- This is a reusable central reference, not a new shared Discord channel. Project adoptions use `channel-scope-skic-<code>` and remain separately owned.
+- Current project channel: `<code>-scope` inside `skic-<code>`.
+
+## Channel workspace standard
+
+Load `channel-workspace-organization` for channel setup, file placement, and authorized workspace migration. Canonical standard: https://gitea.lego-cloud.eu/global-skills/channel-workspace-organization . Follow that shared policy rather than duplicating it here. Existing workspace bindings below remain current until an authorized migration is completed and verified; this reference alone does not relocate files or change bindings.

references/aerosim-lessons-review.md

@@ -2,13 +2,13 @@
 
 ## Evidence boundary
 
-Source repository: [corp-v1-aerosim-skills-code-agent/corp-v1-channel-scope-aerosim](https://gitea.lego-cloud.eu/corp-v1-aerosim-skills-code-agent/corp-v1-channel-scope-aerosim)
+Source repository: [corp-v1-aerosim-skills-code-agent/channel-scope-skic-aerosim](https://gitea.lego-cloud.eu/corp-v1-aerosim-skills-code-agent/channel-scope-skic-aerosim)
 
 Source commit: `3eb7a2a530d63e4ad20f7bff36cf435dc98eb7d6` (branch `test`, pinned clone; not the earlier adoption-base SHA).
 
 Central baseline: `602b1a0afdac56f4b8a10def4bd241b53495c3e3`. Reviewed the full source package: `SKILL.md`, `ADOPTION.md`, and `references/data-backed-scope-integrity.md`, `references/decision-readiness.md`, `references/feature-set-completeness.md`, `references/react-flow-governed-state.md`, `references/roadmap-multidimensional-state.md`. All existing source reference files were byte-identical to central at baseline; changes below address omissions or contradictions, not wholesale copying.
 
-The installed `corp-v1-channel-scope-aerosim/SKILL.md` was also compared read-only. Runtime SHA-256: `78d2e5c1a192184cf2edd6d056182631297a9f1cb97e18cffbc402399c215b47`. Runtime differs from the pinned repository and has no verified source commit for its local-only changes; it is observation, not remote or Board approval evidence. This delegated review did not change any installed package or AeroSim/other project copy. The coordinating session owns authorized central publication and central runtime refresh.
+The installed `channel-scope-skic-aerosim/SKILL.md` was also compared read-only. Runtime SHA-256: `78d2e5c1a192184cf2edd6d056182631297a9f1cb97e18cffbc402399c215b47`. Runtime differs from the pinned repository and has no verified source commit for its local-only changes; it is observation, not remote or Board approval evidence. This delegated review did not change any installed package or AeroSim/other project copy. The coordinating session owns authorized central publication and central runtime refresh.
 
 Review authority: Board-owner request message `1562171939961966693` authorizes central reference improvement and remote publication; the coordinating session also owns the authorized central runtime refresh. Central source publication must be verified before refreshing its installed package. No project adoption, project permission/authority expansion or naming migration is authorized.
 
@@ -25,7 +25,7 @@ No Jira mandate, API recovery operations, release-instance migration, cumulative
 
 ## Central topology authority
 
-The coordinating review record `GUILD-IMP-20261020-aerosim-reference-lessons` confirms central-only maintenance. `corp-v1-main` v4.5.0, **Board Authority** / **Naming Model** / **Hermes access and Corp project automation policy**, records Board message `1552966246591365123` approving eight lifecycle channels, with UAT between Delivery and Releases. Align ordinary synchronization and references to that existing policy. Historical seven-channel bootstrap overrides are not widened; only separately reauthorized overrides may add UAT. Runtime seven-channel wording is stale, not promoted authority.
+The coordinating review record `GUILD-IMP-20261020-aerosim-reference-lessons` confirms central-only maintenance. `channel-board-skic` v4.5.0, **Board Authority** / **Naming Model** / **Hermes access and Corp project automation policy**, records Board message `1552966246591365123` approving eight lifecycle channels, with UAT between Delivery and Releases. Align ordinary synchronization and references to that existing policy. Historical seven-channel bootstrap overrides are not widened; only separately reauthorized overrides may add UAT. Runtime seven-channel wording is stale, not promoted authority.
 
 ## Verification
 

tests/test_contracts.py

@@ -34,7 +34,7 @@ class Contracts(unittest.TestCase):
 
     def test_eight_channel_boundary(self):
         boundary = SKILL.split('## Approved Information Boundary')[1].split('## ', 1)[0]
-        channels = re.findall(r'^corp-v1-<code>-(.+)$', boundary, re.M)
+        channels = re.findall(r'^<code>-(.+)$', boundary, re.M)
         self.assertEqual(channels, ['general', 'scope', 'architecture', 'ui-ux', 'kanban', 'delivery', 'uat', 'releases'])
         self.assertIn('1552966246591365123', boundary)