fix: update Corp v1 skill references

docs/governance/decisions/board-and-aerosim-membership-expansion.md

@@ -21,7 +21,7 @@ sidebar_position: 1
 
 ## Applied state
 
-- Eduard is listed in `corp-v1--main` and the Board registry with authority to approve project kickoff, project closure, and changes to `corp-v1--main`.
+- Eduard is listed in `corp-v1-main` and the Board registry with authority to approve project kickoff, project closure, and changes to `corp-v1-main`.
 - Discord identity and effective channel access are verified for all requested members. Existing permission overwrites already covered `corp-v1-board` and all six AeroSim channels; no additional Discord permission mutation was required.
 - The applied team update was announced in `corp-v1-aerosim-general` as message `1537793704465801256`.
 - Gitea identity `martynas-pazusis` is verified and was added to `aerosim-maintainers` and `aerosim-skill-maintainers`.

docs/governance/decisions/corp-v1-board-migration.md

@@ -15,14 +15,14 @@ slug: /decisions/corp-v1-board-migration/
 ## Decision
 
 1. Replace the steering committee channel with the Corp v1 Board channel. Discord canonicalized the requested `corp-v1--board` text-channel name to `corp-v1-board`; the immutable channel ID remains `1537070875503886356`.
-2. Rename the global governance skill and repository to `corp-v1--main`.
+2. Rename the global governance skill and repository to `corp-v1-main`.
 3. Rename `corp-v1/sterring-commitee` to `corp-v1/portal` and deploy it at `https://pages.apps.lego-cloud.eu/corp-v1/portal/`.
 4. Establish exactly these Board members:
    - RootAtSkic (`<@1518725627845283888>`)
    - Panther Skeleton (`<@476287310627864587>`)
    - MartynasP (`<@773109855497093191>`)
-5. Only these Board members may approve a project kickoff, project closure, or a change to `corp-v1--main`.
-6. Central `corp-v1-channel-*` reference-skill changes require Board approval. After publication, every affected project channel must be asked to review and synchronize its project-adopted `corp-v1-channel-*--<code>` skill; synchronization must preserve project-specific decisions.
+5. Only these Board members may approve a project kickoff, project closure, or a change to `corp-v1-main`.
+6. Central `corp-v1-channel-*` reference-skill changes require Board approval. After publication, every affected project channel must be asked to review and synchronize its project-adopted `corp-v1-channel-*-<code>` skill; synchronization must preserve project-specific decisions.
 
 ## Consequences
 

docs/governance/decisions/corp-v1-guild-establishment.md

@@ -11,21 +11,21 @@ On 2026-08-27, RootAtSkic (`discord:1518725627845283888`) established `corp-v1-g
 The approved implementation includes:
 
 - Discord channel `corp-v1-guild` (`1542596418215092264`) under the `corp-v1` category;
-- central operating skill `corp-v1--guild`;
-- private Gitea source repository [`home-v1-skills-code-agent/corp-v1--guild`](https://gitea.lego-cloud.eu/home-v1-skills-code-agent/corp-v1--guild) on default branch `test`;
+- central operating skill `corp-v1-guild`;
+- private Gitea source repository [`home-v1-skills-code-agent/corp-v1-guild`](https://gitea.lego-cloud.eu/home-v1-skills-code-agent/corp-v1-guild) on default branch `test`;
 - runtime installation of the published skill;
 - Guild guidance linked and pinned in the channel;
 - Corp v1 portal architecture updates that distinguish Guild improvement coordination from Board governance and the seven project delivery channels.
 
 ## Evidence
 
-The approving instruction is Discord message `1542596833266761748` in channel `1542596418215092264`. RootAtSkic requested a skill similar in durability to `corp-v1--main`, defined the channel's purpose as improvements across channels, their skills, and reference skills, and required both portal architecture and Gitea publication.
+The approving instruction is Discord message `1542596833266761748` in channel `1542596418215092264`. RootAtSkic requested a skill similar in durability to `corp-v1-main`, defined the channel's purpose as improvements across channels, their skills, and reference skills, and required both portal architecture and Gitea publication.
 
 ## Authority boundary
 
 The Guild coordinates improvement discovery, impact inventory, ownership routing, implementation, rollout, and verification. It does not replace:
 
-- the Corp v1 Board for project lifecycle, membership, `corp-v1--main`, or central channel-reference approvals;
+- the Corp v1 Board for project lifecycle, membership, `corp-v1-main`, or central channel-reference approvals;
 - project Scope, Architecture, UI/UX, Kanban, Delivery, or Releases decisions;
 - preserved project-local authorization overrides;
 - repository validation, review, exact-head CI, deployed readback, or destructive-action safeguards.

docs/governance/decisions/managed-project-six-channel-alignment.md

@@ -10,7 +10,7 @@ Corp v1 lifecycle policy requires each managed project to operate six Discord wo
 
 ## Decision
 
-Align every currently managed Corp v1 project to the six-channel lifecycle. For AeroSim, create and verify `corp-v1-aerosim-kanban`, attach `corp-v1-channel-kanban--aerosim`, create its staggered hourly job, and update every existing AeroSim synchronization job to the exact six-channel same-project boundary.
+Align every currently managed Corp v1 project to the six-channel lifecycle. For AeroSim, create and verify `corp-v1-aerosim-kanban`, attach `corp-v1-channel-kanban-aerosim`, create its staggered hourly job, and update every existing AeroSim synchronization job to the exact six-channel same-project boundary.
 
 Human gates remain unchanged: only a human team member may approve an Epic or Feature for solution, approve a Feature for implementation, admit an exact task to Focus `InBacklog`, approve final version allocation, or request a release.
 

docs/governance/decisions/project-discord-category-separation.md

@@ -20,7 +20,7 @@ RootAtSkic (`discord:1518725627845283888`) approved one dedicated top-level Disc
 
 ## Implementation
 
-The central [`corp-v1--main`](https://gitea.lego-cloud.eu/home-v1-skills-code-agent/corp-v1--main) skill was updated to version `4.3.0` and merged through PR [8](https://gitea.lego-cloud.eu/home-v1-skills-code-agent/corp-v1--main/pulls/8) at `785e57d6381f60a0caacefdedec791aa3b1fe2fd`.
+The central [`corp-v1-main`](https://gitea.lego-cloud.eu/home-v1-skills-code-agent/corp-v1-main) skill was updated to version `4.3.0` and merged through PR [8](https://gitea.lego-cloud.eu/home-v1-skills-code-agent/corp-v1-main/pulls/8) at `785e57d6381f60a0caacefdedec791aa3b1fe2fd`.
 
 Three categories were created with the existing approved permission-overwrite model:
 

docs/governance/decisions/shared-system-sso-credentials.md

@@ -29,7 +29,7 @@ Credential values, Bitwarden object identifiers, and account metadata must not b
 
 ## Implementation and verification
 
-The central `corp-v1--main` skill was updated to version `4.4.0` and merged through PR [9](https://gitea.lego-cloud.eu/home-v1-skills-code-agent/corp-v1--main/pulls/9) at `b11b0e521dab6b7a920337feed37c5a849d507bd`.
+The central `corp-v1-main` skill was updated to version `4.4.0` and merged through PR [9](https://gitea.lego-cloud.eu/home-v1-skills-code-agent/corp-v1-main/pulls/9) at `b11b0e521dab6b7a920337feed37c5a849d507bd`.
 
 The same secret-safe login section was published central-first to all seven `corp-v1-channel-*` reference skills, then semantically adopted into all 21 project channel skills across AeroSim, Maze Next Gen, and E-Shop v1. Every project-local authorization override was hash-checked before and after adoption, project bindings and supporting files were preserved, and every pushed default ref and `SKILL.md` marker was read back. All 21 installed Hermes runtime packages were refreshed from the resulting project repositories. The exact repository, branch, commit, and override coverage is recorded in the [shared SSO skill rollout ledger](/governance/sso-skill-rollout/).