Add a status checklist as the authoritative plan-progress record

Completion status previously lived only in my in-session TodoWrite list
(ephemeral, doesn't survive the session) or had to be inferred from which
steps had an entry in the execution log. Neither is a durable, explicit
answer to "what's left."

Adds a markdown checklist at the top of each plans-executions file, one
line per plan step, checked in the same commit as that step's entry. A
new session resuming this plan can read the file alone and know exactly
where to pick up.

Co-Authored-By: Claude <noreply@anthropic.com>

CLAUDE.md

@@ -104,6 +104,15 @@ originating plan in `docs/plans/`, so the two files pair up 1:1. Create the file
 section per step after that, in chronological order (bottom of the file), not
 newest-first like `CHANGELOG.md`.
 
+**Status checklist.** The top of the file, above the first step's entry, is a markdown
+checklist with one line per step from the plan (`- [ ] Step 0 — <title>`), so a single
+glance shows what's done and what's left without reading prose or cross-referencing
+`git log`. Check a box in the same commit that adds that step's entry — never leave a
+completed step unchecked or a not-yet-done step checked. This checklist is the
+authoritative status record; an in-session todo list (e.g. `TodoWrite`) is ephemeral
+and does not substitute for it — a new session resuming this plan should be able to
+read this file alone and know exactly where to pick up.
+
 Keep the prose light — a few sentences on what was done, plus anything genuinely
 interesting or non-obvious about how it went (a judgment call made, a spec gap found,
 something that didn't work as expected). This is not a duplicate of the plan or the

docs/plans-executions/2026-08-07-1747-proxy-operator.md

@@ -2,6 +2,22 @@
 
 Pairs with [docs/plans/2026-08-07-1747-proxy-operator.md](../plans/2026-08-07-1747-proxy-operator.md).
 
+## Status
+
+- [x] Step 0 — Branch and scaffold
+- [ ] Step 1 — API types (`api/v1alpha1/proxy_types.go`)
+- [ ] Step 2 — Provider contract (`internal/provider/`)
+- [ ] Step 3 — Mock provider (`internal/provider/mock/`)
+- [ ] Step 4 — Reconciler (`internal/controller/`)
+- [ ] Step 5 — Health engine (`internal/health/`)
+- [ ] Step 6 — Lease store (`internal/lease/`)
+- [ ] Step 7 — Discovery API (`internal/discovery/`)
+- [ ] Step 8 — GCP provider (`internal/provider/gcp/`)
+- [ ] Step 9 — Orphan GC + metrics
+- [ ] Step 10 — Wiring, config, docs
+- [ ] Step 11 — Tests
+- [ ] Verification (vet/test/kind e2e) + commit, push, open MR
+
 ## Step 0 — Branch and scaffold
 
 Branched off the unborn `main`: