home-v1-skills-code-agent/corp-v1-channel-uat
6
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge pull request 'policy: keep image and Helm tooling out of E2E' (#6) from policy/functional-tests-only into test

Browse Source
This commit was merged in pull request #6.
This commit is contained in:
jarvis-at-skic
2026-09-26 05:15:21 -07:00
parent ac6f696f19 794881e18b
commit 8e6547659c
2 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
SKILL.md
+4 -4
View File
@@ -1,7 +1,7 @@
--- ---
name: corp-v1-channel-uat name: corp-v1-channel-uat
description: Use when validating a deployed Corp v1 environment through UAT journeys. description: Use when validating a deployed Corp v1 environment through UAT journeys.
version: 1.2.2 version: 1.3.0
author: Hermes Agent author: Hermes Agent
license: MIT license: MIT
metadata: metadata:
@@ -42,9 +42,9 @@ If any identity is mutable, missing, or contradictory, record `BLOCKED` rather t
## Responsibilities ## Responsibilities
1. Maintain a dedicated pnpm E2E repository as the authoritative home for every non-unit test and its fixtures, configuration, runner, and evidence contract. 1. Maintain a dedicated pnpm E2E repository as the authoritative home for functional non-unit tests and their fixtures, configuration, runner, and evidence contract.
2. Keep the application repository limited to application source and unit tests. Browser, network/socket, database, container/image, Helm/rendering, cross-package integration, performance, deployed-environment, security-boundary, and user-observable acceptance testing belongs to UAT/E2E. 2. Keep application image/container/Helm build, rendering, publication, and static artifact validation in Delivery. The E2E repository must not build/publish application images, install Helm, render charts, or validate artifact publication.
3. Execute source-coupled non-unit suites against an exact application-source checkout and black-box journeys against the exact deployed environment supplied by Delivery. 3. Execute source-coupled functional non-unit suites against an exact application-source checkout and black-box journeys against the exact deployed environment supplied by Delivery.
4. Collect machine-readable and human-reviewable evidence. 4. Collect machine-readable and human-reviewable evidence.
5. Distinguish product failures, environment failures, and test defects. 5. Distinguish product failures, environment failures, and test defects.
6. Return product/environment failures to Kanban and Delivery with reproducible evidence. 6. Return product/environment failures to Kanban and Delivery with reproducible evidence.
references/journey-repository-contract.md
+1 -1
View File
@@ -1,6 +1,6 @@
# Journey repository contract # Journey repository contract
The UAT repository is a standalone pnpm/Playwright project and the authoritative home for all non-unit tests. It may contain source-coupled integration, container-contract, and Helm-rendering tests, but contains no application implementation, deployable Kubernetes/Helm desired state, image publication, Argo CD mutation, or deployment logic. The UAT repository is a standalone pnpm/Playwright project and the authoritative home for functional non-unit tests. It may contain source-coupled integration, browser, database-backed, performance, acceptance, and deployed-environment suites. It contains no application implementation, image/container publication validation, Helm installation/rendering, deployable Kubernetes/Helm desired state, image publication, Argo CD mutation, or deployment logic.
## Required baseline ## Required baseline