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: assign all non-unit tests to UAT' (#5) from policy/all-non-unit-tests into test

Browse Source
This commit was merged in pull request #5.
This commit is contained in:
jarvis-at-skic
2026-09-26 03:35:30 -07:00
parent e8ddf82040 84225828bd
commit ac6f696f19
2 changed files with 10 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
SKILL.md
+9 -8
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.1.3 version: 1.2.2
author: Hermes Agent author: Hermes Agent
license: MIT license: MIT
metadata: metadata:
@@ -42,13 +42,14 @@ If any identity is mutable, missing, or contradictory, record `BLOCKED` rather t
## Responsibilities ## Responsibilities
1. Maintain a dedicated pnpm E2E repository with versioned journeys. 1. Maintain a dedicated pnpm E2E repository as the authoritative home for every non-unit test and its fixtures, configuration, runner, and evidence contract.
2. Execute journeys against the exact deployed environment supplied by Delivery. 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.
3. Collect machine-readable and human-reviewable evidence. 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.
4. Distinguish product failures, environment failures, and test defects. 4. Collect machine-readable and human-reviewable evidence.
5. Return product/environment failures to Kanban and Delivery with reproducible evidence. 5. Distinguish product failures, environment failures, and test defects.
6. Rerun the affected journey set after a verified redeployment. 6. Return product/environment failures to Kanban and Delivery with reproducible evidence.
7. Hand a `UAT_PASSED` or `UAT_FAILED` verdict to Releases without implying release approval. 7. Rerun the affected journey set after a verified redeployment.
8. Hand a `UAT_PASSED` or `UAT_FAILED` verdict to Releases without implying release approval.
## Required E2E repository pipeline ## Required E2E repository pipeline
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. It contains no Kubernetes, Helm, Argo CD, application implementation, image publication, or deployment logic. 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.
## Required baseline ## Required baseline