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.2.2
+version: 1.3.0
 author: Hermes Agent
 license: MIT
 metadata:
@@ -42,9 +42,9 @@ If any identity is mutable, missing, or contradictory, record `BLOCKED` rather t
 
 ## 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.
-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. Execute source-coupled non-unit suites against an exact application-source checkout and black-box journeys against the exact deployed environment supplied by Delivery.
+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.