end-with-targeted-make-report-verify.mdc

---
description: End implementation responses with targeted make screenshot-report verification commands for the operator.
alwaysApply: true
---

# End With Targeted Make Report Verify

For implementation responses in this repo:

0. **Do not run tests during agent or plan work.** Never run test, lint, or verification commands as part of implementation. Only instruct the operator in a fenced `bash` block at the end of the response.
1. **Give the user** one or more runnable `make` commands they can copy and run to verify the change; place them in a fenced `bash` code block at the end of your response.
2. **UI changes (apps/web, apps/management-web, packages/ui):** Instruct the operator to run the narrowest targeted screenshot report and where to open it (`.artifacts/e2e-reports/latest/web/index.html` or `.../management-web/index.html`). See **ui-e2e-screenshot-report** skill.
3. **MANDATORY when the change affects E2E:** If you modified UI (apps/web or apps/management-web), E2E spec files, or any code that E2E tests cover, you **MUST** end the response with a fenced `bash` block containing the **EXACT** command(s) needed to run the affected E2E test(s). Example: `make e2e_test_web_report_spec SPEC=e2e/smoke.spec.ts`.
4. Prefer screenshot-report targets scoped to the changed feature area.
5. Avoid suggesting unrelated full-suite runs by default.
6. Use full-suite report mode only when change scope is broad or cross-cutting.
7. Place final verification commands in a fenced `bash` code block so copy-to-clipboard is available.
8. Inside the code block, list plain commands (one per line), without bullets or inline backticks.
9. **When the change includes files under `infra/k8s/`:** Add a sentence in the response that the operator should push to the Argo CD–tracked branch (e.g. `develop`) for the cluster to sync. See **argocd-gitops-push** skill for details.

API gate (default: no API tests):

- **Always** give E2E verification commands **without** `E2E_API_GATE_MODE` so the default applies: API integration tests are **skipped**. Do not add `E2E_API_GATE_MODE=on` unless the change affected API or integration tests.
- To include API tests the user must pass the env var: `make E2E_API_GATE_MODE=on e2e_test_web_report_spec SPEC=...`

Preferred commands:

- Web: `make e2e_test_web_report_spec SPEC=e2e/<spec>.spec.ts`
- Management-web: `make e2e_test_management_web_report_spec SPEC=e2e/<spec>.spec.ts`
- Both: `make e2e_test_report_scoped WEB_SPEC=e2e/<web>.spec.ts MGMT_SPEC=e2e/<mgmt>.spec.ts`
- Broad smoke: `make e2e_test_home_report`
- Full regression: `make e2e_test_report`
- API only: `npm run test:e2e:api`

Spec variables (`SPEC`, `WEB_SPEC`, `MGMT_SPEC`) may contain comma-separated spec paths when multiple related specs should run.

**Final COPY-PASTA prompt:** When completing the last step in a plan set (`COPY-PASTA.md` / `00-EXECUTION-ORDER.md`), assume the operator ran all prompts without running tests until the end. List **all** cumulative verification commands for the whole set in one fenced `bash` block (dedupe; order: build/lint → unit → API → E2E). See **response-ending-make-verify**, **plan-completion**, and **plan-files-convention** skills.

Extended reference: **response-ending-make-verify**, **ui-e2e-screenshot-report**, and **plan-completion** skills.