docs: standardize UAT repository workflows

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.0.0
+version: 1.1.0
 author: Hermes Agent
 license: MIT
 metadata:
@@ -50,6 +50,26 @@ If any identity is mutable, missing, or contradictory, record `BLOCKED` rather t
 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.
 
+## Required E2E repository pipeline
+
+Every project UAT repository uses two Gitea Actions workflows:
+
+```text
+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
+
+merge to the default `test` branch
+└── UAT / Integrated Regression
+    ├── repository validation
+    ├── smoke journeys
+    ├── complete regression journeys
+    └── immutable deployment-tuple evidence
+```
+
+Use one change workflow for both pre-PR branches and PR heads. A PR-open or PR-reopen event adds the first smoke-bearing run. Do not subscribe that workflow to `pull_request.synchronize`; later branch pushes are the single trigger and classify whether the exact commit is an open PR head. Cancel superseded runs for the same branch. Never run full regression on a PR, and never treat smoke as complete UAT. The integrated workflow runs only for the exact commit pushed to `test`, fails closed when its frozen deployment inputs are missing or unhealthy, and does not deploy or publish application artifacts.
+
 ## UAT verdicts
 
 These verdicts are acceptance dimensions; they do not replace the project's canonical Task status: