docs: promote reusable AeroSim channel lessons
This commit is contained in:
1 parent
2844c4a5f7
commit
4a7c9bfcf7
4 files changed
+111
-14
No files matched your search
@@ -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.6.0
|
||||
version: 1.7.0
|
||||
author: Hermes Agent
|
||||
license: MIT
|
||||
metadata:
|
||||
@@ -18,7 +18,7 @@ metadata:
|
||||
|
||||
Whenever a response mentions a Hermes Kanban board, initiative, card, or task, it must include a direct dashboard link in the form `[descriptive board label](<dashboard-public-url>/kanban?board=<board-slug>)`. Resolve the dashboard public URL and exact board slug before reporting; never provide only a board name, slug, card count, “visible cards,” or “available in the dashboard.” If no task-specific deep link exists, link the board and include the exact task ID or title in the same statement. Project-adopted skills must replace this generic form with their verified project board URL.
|
||||
|
||||
This skill owns release readiness and the controlled release-change workflow for a Corp v1 project. It monitors the project's `general`, `scope`, `architecture`, `ui-ux`, `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`, `ui-ux`, `kanban`, `delivery`, `uat`, 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.
|
||||
|
||||
@@ -78,10 +78,11 @@ 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
|
||||
```
|
||||
|
||||
Use mapped-channel history to avoid duplicate work and new relevant activity from the other six channels. Never inspect another project's channels.
|
||||
Use mapped-channel history to avoid duplicate work and new relevant activity from the other seven channels. Never inspect another project's channels.
|
||||
|
||||
## Release Readiness
|
||||
|
||||
@@ -105,7 +106,7 @@ Readiness reporting does not itself authorize deployment.
|
||||
|
||||
### Gate 1 — explicit request
|
||||
|
||||
Require an unambiguous request from the project team identifying the project and intended release. If version, environment, artifact, or scope is missing, prepare a readiness summary and ask for the missing decision rather than guessing.
|
||||
Require an unambiguous request from the project team identifying the project and intended release, and satisfy the UAT promotion gate below. If version, environment, artifact, scope, or required UAT evidence is missing, prepare a readiness summary and route the missing decision or evidence rather than guessing.
|
||||
|
||||
### Gate 2 — discover repositories and instructions
|
||||
|
||||
@@ -164,18 +165,25 @@ Read back the PR URL, number, head/base SHAs, state, checks, and review status.
|
||||
|
||||
Opening the PR completes autonomous release preparation. Do not merge, synchronize GitOps, or deploy unless the team separately approves that action and the applicable deployment workflow explicitly authorizes execution.
|
||||
|
||||
## UAT promotion gate
|
||||
|
||||
For runtime releases, independently verify `UAT_PASSED` against the exact application commit, immutable image/chart identities, rendered non-production GitOps revision, controller revisions/sync/health, environment/base URL, E2E commit, and complete required journey set. Reject failed, blocked, stale, partial, or mismatched evidence and return it to UAT/Delivery. A release request does not waive UAT; a UAT pass does not authorize release. Non-runtime work may use only an explicitly justified, verified non-applicability record under the project release policy.
|
||||
|
||||
Promotion preserves the tested application/artifact identity but creates a distinct production desired-state revision. Record the mapping and verify production separately; the UAT environment's GitOps commit or healthy state is not production deployment evidence.
|
||||
|
||||
## Post-Approval and Deployment Evidence
|
||||
|
||||
When separately authorized after approval:
|
||||
|
||||
- verify approval and required checks still apply to the exact head SHA;
|
||||
- follow Gondor/GitOps deployment instructions;
|
||||
- monitor actual deployment state;
|
||||
- verify health and release-specific acceptance checks;
|
||||
- verify the owning controller's deployed revision, runtime source/chart identity, pod image digests, and endpoint against the approved production desired state; for app-of-apps, reconcile through the owning root rather than directly patching a managed child;
|
||||
- verify release-specific acceptance through ordinary user-visible controls and meaningful runtime outcomes; forced interactions or hidden state/API bypasses are diagnostic only, and healthy infrastructure cannot excuse an unusable journey;
|
||||
- record technical deployment health, automated acceptance, and human post-release acceptance separately; the latter remains `PENDING` until explicit confirmation, and a human-reported blocking defect makes it `FAILED`;
|
||||
- post version, commit, PR, deployment, and rollback evidence;
|
||||
- record post-release outcomes and unresolved follow-up.
|
||||
|
||||
Never claim deployment from a merged PR alone.
|
||||
Never claim deployment from a merged PR alone, or human acceptance from release authorization. If a deployed release fails a core journey, record it as rejected but still deployed until containment is verified. Preserve its immutable version, artifacts, and failure evidence; agree authorized rollback or maintenance with the release owner and route a new immutable corrective release through Delivery, UAT, and Releases. Do not silently retag or overwrite the rejected version. Unapproved containment remains an explicit risk, not an action this skill authorizes.
|
||||
|
||||
## UI/UX Coordination
|
||||
|
||||
@@ -183,12 +191,12 @@ For frontend-affecting releases, Releases verifies the approved UI/UX acceptance
|
||||
|
||||
## Synchronization Workflow
|
||||
|
||||
1. Read new same-project activity and enough release history to avoid duplicates.
|
||||
1. Read new activity from all eight mapped same-project channels and enough release history to avoid duplicates.
|
||||
2. Identify readiness changes, version/changelog drift, deployment evidence, migration/rollback risk, and release requests.
|
||||
3. Without an explicit release request, proactively improve readiness documentation, version/changelog evidence, rollback planning, or a concrete blocker/approval request only.
|
||||
4. With an explicit request, execute the controlled workflow through PR creation.
|
||||
5. Verify every repository, branch, commit, render, check, and PR claim.
|
||||
6. Post a concise release update with documentation and verification evidence, or the concrete gate that prevented useful work.
|
||||
6. Return a concise release update with evidence or the blocking gate. If the execution context auto-delivers the final response, do not post a duplicate message. Claim message delivery only with a verified receipt; repository readback is not message delivery evidence.
|
||||
|
||||
## Authority and Escalation
|
||||
|
||||
@@ -213,13 +221,15 @@ Requires separate approval for:
|
||||
|
||||
## Mined Project-Adoption Improvements
|
||||
|
||||
Review provenance and exclusions: [AeroSim lessons review](references/aerosim-lessons-review.md).
|
||||
|
||||
## Dedicated Project Channel Workspace
|
||||
|
||||
Every project adoption must bind this channel to a dedicated local workspace under the active working root. Keep clones, worktrees, plans, reports, screenshots, generated artifacts, retained logs, and channel inputs inside that channel root. Use run-unique or task-specific children under `workspace/`; keep durable project truth in approved repositories. A local folder boundary organizes execution only—it neither broadens authority nor replaces remote evidence. Delivery adoptions should additionally use a channel-level `cache/` for reusable pinned toolchains and dependencies, while keeping Task evidence isolated by Task.
|
||||
|
||||
## Project-Adoption Release Lessons
|
||||
|
||||
Releases—not Delivery—owns the final `TO_BE_RELEASED → DONE` transition. Apply it only after the approved release/deployment is promoted and verified. Record the actual version, immutable artifact/digest where applicable, deployment revision, runtime health, acceptance evidence, actor/time, and append-only history linkage. The exit gate is remote documentation showing `DONE` after the release-specific checks pass; merged code, green integration CI, or a published image alone is insufficient.
|
||||
Releases—not Delivery—owns the final `TO_BE_RELEASED → DONE` transition. Apply it only from canonical `TO_BE_RELEASED`, after the approved release/deployment is promoted and verified and the UAT promotion gate passes. Record the actual version, immutable artifact/digest where applicable, deployment revision, runtime health, acceptance evidence, actor/time, and append-only history linkage. The exit gate is remote documentation showing `DONE` after the release-specific checks pass; merged code, green integration CI, or a published image alone is insufficient.
|
||||
|
||||
Recurring readiness work must refresh mutable owner PR heads and the latest exact-head CI tasks, prevent self-stale references to the readiness PR's own head, guard against concurrent writers, replace stale open/pending wording after merges, and verify exact remote artifact bytes before reporting. Follow [references/recurring-readiness-pr-refresh.md](references/recurring-readiness-pr-refresh.md).
|
||||
|
||||
|
||||
Reference in new issue
Block a user