make verify: the external checks as a Target #33

New issue

Closed

opened 2026-10-06 15:01:14 +00:00 by pit · 0 comments

pit commented

2026-10-06 15:01:14 +00:00

Owner

Parent

#27

What to build

make verify runs the external checks that establish a deploy actually worked, rather than trusting that the playbook exited zero: the redirect and the success on the site, an SSH clone from outside, and the clone URLs the UI shows. It mutates nothing. The 0 changed idempotence check stays a documented manual second run, because baking it into this Target would double a Prod run. The runbook's "the Makefile" section gains this Target's entry.

Acceptance criteria

make verify runs the external checks and reports each one's result.
It mutates nothing.
The runbook documents the Target and keeps the idempotence check as a manual step.

Blocked by

##29 — the Makefile scaffold and its apply gate.

## Parent #27 ## What to build `make verify` runs the external checks that establish a deploy actually worked, rather than trusting that the playbook exited zero: the redirect and the success on the site, an SSH clone from outside, and the clone URLs the UI shows. It mutates nothing. The `0 changed` idempotence check stays a documented manual second run, because baking it into this Target would double a Prod run. The runbook's "the Makefile" section gains this Target's entry. ## Acceptance criteria - [ ] `make verify` runs the external checks and reports each one's result. - [ ] It mutates nothing. - [ ] The runbook documents the Target and keeps the idempotence check as a manual step. ## Blocked by - ##29 — the Makefile scaffold and its apply gate.

pit added the

ready-for-agent

label

2026-10-06 15:01:14 +00:00

pit added a new dependency

2026-10-06 15:01:15 +00:00

#29 The Makefile: help, the apply gate, and the Guest Stack as the first Target

pit added a new dependency

2026-10-06 15:01:15 +00:00

#34 make prod: the whole Prod deploy in one command

pit referenced this issue

2026-10-06 15:03:14 +00:00