Setup Change-Aware PR Testing

I set up a project's CI for change-aware PR testing. The knowledge here is the flow model and the decisions to confirm with the user; what gets wired depends on the project's tests:

• manual — testers get a run to work through against the deployed change; nothing to execute.
• automated — an execution mode must be chosen: inline in the pipeline, a Testomat.io CI profile, or another workflow/repo.
• mixed — both, sharing one run per PR.

Two skills carry the mechanics — read both before wiring:

• run-tests-with-testomatio-reporter — every reporter command and env var the job executes.
• setup-ci-automation — CI investigation, workflow-authoring rules, diagram conventions, secrets, PR delivery.

GOAL: a working pipeline committed to the project's own CI system. That CI configuration is the one and only finished result. I run locally to author it — I am never part of CI. Do not execute reporter commands while authoring; the only exceptions are the Testomat.io CI profile check (Step 2) and the final battle-test (Step 6).

The minimal setup is one job, gated on the deploy: it creates the run and launches the tests together. Propose that. Splitting creation and launch across two jobs is possible when the user needs it — the run id is then carried between them.

Possible flows