policy: keep artifact tooling out of E2E

SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: corp-v1-channel-uat
 description: Use when validating a deployed Corp v1 environment through UAT journeys.
-version: 1.1.2
+version: 1.3.0
 author: Hermes Agent
 license: MIT
 metadata:
@@ -42,13 +42,14 @@ If any identity is mutable, missing, or contradictory, record `BLOCKED` rather t
 
 ## Responsibilities
 
-1. Maintain a dedicated pnpm E2E repository with versioned journeys.
-2. Execute journeys against the exact deployed environment supplied by Delivery.
-3. Collect machine-readable and human-reviewable evidence.
-4. Distinguish product failures, environment failures, and test defects.
-5. Return product/environment failures to Kanban and Delivery with reproducible evidence.
-6. Rerun the affected journey set after a verified redeployment.
-7. Hand a `UAT_PASSED` or `UAT_FAILED` verdict to Releases without implying release approval.
+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 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 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.
+5. Distinguish product failures, environment failures, and test defects.
+6. Return product/environment failures to Kanban and Delivery with reproducible evidence.
+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
 
@@ -58,7 +59,7 @@ Every project UAT repository uses two Gitea Actions workflows:
 non-default branch push
 └── CI / Change Validation
     ├── repository validation for every exact pushed commit
-    └── smoke journeys only when that commit is an open PR head
+    └── smoke journeys for explicit PR events or exact review-associated commits
 
 merge to the default `test` branch
 └── UAT / Integrated Regression

references/journey-repository-contract.md

@@ -1,6 +1,6 @@
 # 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 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
 
@@ -36,7 +36,7 @@ A smaller standalone repository may keep `journeys/`, `fixtures/`, `helpers/`, a
 non-default branch push
 └── CI / Change Validation
     ├── formatting, linting, type checks, contract tests, journey discovery, build when applicable
-    └── smoke journeys only when the exact commit is an open PR head
+    └── smoke journeys for explicit PR events or exact review-associated commits
 
 PR opened or reopened
 └── CI / Change Validation