[verified] refactor: reference diagrams-drawio

SKILL.md

@@ -7,7 +7,7 @@ license: MIT
 metadata:
   hermes:
     tags: [corp-v1, discord, channel, architecture, c4, adr, requirements]
-    related_skills: [corp-v1--main, home-v1-discord, drawio-main, documentation-docusaurus, corp-v1--glossary]
+    related_skills: [corp-v1--main, home-v1-discord, diagrams-drawio, documentation-docusaurus, corp-v1--glossary]
 ---
 
 # Corp v1 Architecture Channel
@@ -16,13 +16,13 @@ metadata:
 
 This skill owns the solution phase and architecture coherence for a Corp v1 project. It monitors the project's `general`, `scope`, `architecture`, `ui-ux`, `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:
+The default architecture model is C4. Architecture diagrams must be authored and validated using the global `diagrams-drawio` skill from:
 
 ```text
-https://gitea.lego-cloud.eu/home-v1-skills-code-agent/drawio-main
+https://gitea.lego-cloud.eu/home-v1-skills-code-agent/diagrams-drawio
 ```
 
-Do not duplicate `drawio-main` into each project by default. A project team may explicitly decide to adopt its own copy; that decision must also update the project's channel skills and steering record.
+Do not duplicate `diagrams-drawio` into each project by default. A project team may explicitly decide to adopt its own copy; that decision must also update the project's channel skills and steering record.
 
 Load the global `documentation-docusaurus` skill before changing project documentation structure, navigation, MDX, Draw.io embedding, or Docusaurus configuration. Its authoritative source is:
 
@@ -152,11 +152,11 @@ Every diagram must include a title, scope, element names, responsibilities, rela
 
 ## Draw.io Workflow
 
-1. Load global `drawio-main` before creating or modifying a diagram.
+1. Load global `diagrams-drawio` before creating or modifying a diagram.
 2. Load global `documentation-docusaurus` before changing the site or embedding a diagram.
 3. Store editable `.drawio` source in the documentation repository.
 4. Onboard the source through `docusaurus-plugin-drawio` using the MDX source-import workflow from `documentation-docusaurus`; do not publish only a static export.
-5. Export an additional review format only when `drawio-main` or project policy requires it.
+5. Export an additional review format only when `diagrams-drawio` or project policy requires it.
 6. Validate Draw.io source, Docusaurus build, source import, selected page/pageId, browser rendering, and console/network output.
 7. Link diagrams from Context, Overview, Container Registry entries, and FR/NFR pages as applicable.
 8. Commit source, MDX/configuration, lockfile, and any required rendered output together.
@@ -261,7 +261,7 @@ Architecture supplies UI/UX with system boundaries, interfaces, data availabilit
 3. Identify changed assumptions, requirements, interfaces, constraints, infrastructure, deployment topology, or runtime behavior.
 4. Compare evidence with the required Architecture information architecture, C4 views, ADRs, FR/NFR registries and pages, Scope-hosted task records, dependencies, readiness, and version evidence.
 5. Add or materially improve at least one useful solution artifact for an eligible Feature.
-6. Use `drawio-main` for every diagram change and `documentation-docusaurus` for every documentation, navigation, MDX, plugin, or embedding change.
+6. Use `diagrams-drawio` for every diagram change and `documentation-docusaurus` for every documentation, navigation, MDX, plugin, or embedding change.
 7. Validate the exact Architecture sidebar, FR/NFR registries and reader pages, absence of Architecture Feature/task navigation, reciprocal Scope traceability, links, Draw.io source embedding, Docusaurus build, and browser rendering; then perform remote readback.
 8. Post a concise update with changed artifacts, implications, unresolved decisions, approval gate, and exact evidence.
 
@@ -283,12 +283,12 @@ Requires team approval for:
 - finalizing which Feature belongs to which version;
 - changing system boundaries, major technologies, security posture, data handling, or deployment topology;
 - resolving genuine contradictions in product requirements;
-- adopting a project-specific `drawio-main` copy;
+- adopting a project-specific `diagrams-drawio` copy;
 - irreversible or high-impact implementation/deployment work.
 
 ## Common Pitfalls
 
-1. Drawing architecture without loading `drawio-main`.
+1. Drawing architecture without loading `diagrams-drawio`.
 2. Duplicating the global Draw.io skill without a team decision.
 3. Treating every C4 level as mandatory regardless of value.
 4. Marking draft decisions or requirements as approved.
@@ -311,7 +311,7 @@ Requires team approval for:
 - [ ] Only the seven same-project channels were inspected.
 - [ ] Architecture documentation reflects verified status.
 - [ ] C4 scope and level are appropriate.
-- [ ] `drawio-main` governed every diagram change.
+- [ ] `diagrams-drawio` governed every diagram change.
 - [ ] `documentation-docusaurus` governed navigation, MDX, plugin, and source embedding changes.
 - [ ] Architecture has its dedicated sidebar ordered Context, Overview, Container Registry, Requirements - Functional → Registry + FR pages, Requirements - Non-Functional → Registry + NFR pages.
 - [ ] Architecture has no Features menu/pages and no task registry/reader navigation.