|
|
|
@@ -1,16 +1,16 @@
|
|
|
|
|
---
|
|
|
|
|
name: corp-v1-channel-releases
|
|
|
|
|
name: channel-releases-skic
|
|
|
|
|
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.7.0
|
|
|
|
|
version: 1.7.1
|
|
|
|
|
author: Hermes Agent
|
|
|
|
|
license: MIT
|
|
|
|
|
metadata:
|
|
|
|
|
hermes:
|
|
|
|
|
tags: [corp-v1, discord, channel, releases, gondor-v1, gitops, pull-request]
|
|
|
|
|
related_skills: [corp-v1-main, home-v1-discord, gondor-v1-nodes, documentation-docusaurus, corp-v1-glossary]
|
|
|
|
|
related_skills: [channel-board-skic, home-v1-discord, gondor-v1-nodes, documentation-docusaurus, corp-v1-glossary]
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
# Corp v1 Releases Channel
|
|
|
|
|
# SKIC Releases Channel Reference
|
|
|
|
|
|
|
|
|
|
## Overview
|
|
|
|
|
|
|
|
|
@@ -40,7 +40,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
|
|
|
|
@@ -53,7 +53,7 @@ Secret availability is capability, not authorization. Verify the destination ori
|
|
|
|
|
|
|
|
|
|
Use this skill when:
|
|
|
|
|
|
|
|
|
|
- operating in `corp-v1-<code>-releases`;
|
|
|
|
|
- operating in `<code>-releases`;
|
|
|
|
|
- running its recurring synchronization job;
|
|
|
|
|
- assessing release readiness;
|
|
|
|
|
- preparing version/changelog/deployment evidence;
|
|
|
|
@@ -72,14 +72,14 @@ Every releases iteration must add or materially improve at least one useful, saf
|
|
|
|
|
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
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
Use mapped-channel history to avoid duplicate work and new relevant activity from the other seven channels. Never inspect another project's channels.
|
|
|
|
@@ -259,3 +259,16 @@ Recurring readiness work must refresh mutable owner PR heads and the latest exac
|
|
|
|
|
- [ ] The PR clearly requires team approval before deployment.
|
|
|
|
|
- [ ] No merge or deployment occurred without separate authorization.
|
|
|
|
|
- [ ] At least one useful release artifact was improved, or a concrete human-request/approval blocker was documented.
|
|
|
|
|
|
|
|
|
|
## Canonical naming and compatibility
|
|
|
|
|
|
|
|
|
|
- Canonical installed and repository name: `channel-releases-skic`.
|
|
|
|
|
- Source: `https://gitea.lego-cloud.eu/home-v1-skills-code-agent/channel-releases-skic`.
|
|
|
|
|
- Previous name: `corp-v1-channel-releases`; 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-releases-skic-<code>` and remain separately owned.
|
|
|
|
|
- Current project channel: `<code>-releases` 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.
|
jarvis-at-skic