docs: add Step 10 rapidapi-proxy-secret to secrets-checklist.md

Add checklist item 10 and full detail section for the rapidapi-proxy-secret
Kubernetes secret that must be created in each API namespace (zip-enrichment,
holidays, air-quality) before the Phase 3 server middleware can validate
incoming RapidAPI requests.

Includes:
- Checklist item 10 in the summary list
- Full detail section with kubectl commands for all 3 namespaces
- Note about placeholder ExternalSecret manifests and ESO (issue #61)
- Updated dependency-order diagram

Closes leeworks-agents/api-company#60

STATUS.md

@@ -1,6 +1,6 @@
 # Company Status
 
-_Last updated: 2026-05-26 (agent cycle — afternoon)_
+_Last updated: 2026-05-27 (agent cycle — evening triage)_
 
 ## APIs
 | API            | Spec | Code | Deployed | Listed on RapidAPI | Paying Users | MRR |
@@ -18,9 +18,33 @@ Legend: [x]=done, [~]=in-progress, [ ]=not started
 - **Container registry:** Gitea built-in registry selected; docs/registry.md committed — PENDING Gitea packages enabled (issue #4)
 - **Prometheus + Grafana:** Flux HelmRelease at `flux/monitoring/` — PENDING Flux wiring + Grafana secret (issue #7)
 - **Gatus status page:** Flux HelmRelease at `flux/monitoring/gatus-helmrelease.yaml` — PENDING Flux wiring (issue #8)
-- **API service manifests (NEW):** `flux/zip-enrichment/`, `flux/holidays/`, `flux/air-quality/` scaffolded (PR #48, closes #46)
+- **API service manifests:** `flux/zip-enrichment/`, `flux/holidays/`, `flux/air-quality/` scaffolded (PR #48, closes #46)
+- **Image automation:** `flux/image-automation/` — ImageRepository + ImagePolicy + ImageUpdateAutomation for all three APIs
 
-## Completed This Cycle (2026-05-26 PM)
+## Completed This Cycle (2026-05-27 — Evening Triage)
+- **Triage pass** — all 15 open agent-ready issues reviewed; status comments posted on each.
+- **No open PRs** — nothing to merge or review.
+- **No new feature work** — all issues remain blocked on operator actions or cross-repo prerequisites.
+- **`kustomize build flux/` = PASS** — no regressions.
+
+## Completed Previous Cycle (2026-05-27 — Ship/Afternoon)
+- **PRs reviewed** — 0 open PRs on fork; nothing to merge.
+- **Upstream sync** — `0xWheatyz/api-company` does not yet exist (blocker #41/#47); `git fetch upstream` failed as expected. Fork `origin/main` is current (SHA `9a1639f`).
+- **`kustomize build flux/` = PASS** — all sub-trees validate cleanly; no regressions.
+- **Deployment PR** — skipped; upstream repo must be created by operator first (#41, #47).
+- **No new feature work** — all 15 open agent-ready issues remain blocked on operator actions.
+
+## Completed Previous Cycle (2026-05-27 — Morning)
+- **Triage pass** — all 15 open agent-ready issues reviewed; status comments posted/confirmed on each.
+- **#19** — First triage comment posted: RapidAPI/PayPal operator task fully documented; all agent-side prerequisites (OpenAPI specs, listing copy, proxy-secret placeholders) confirmed ready.
+- **No PRs to review** — fork had no open PRs.
+- **No new feature work** — all open issues blocked on operator actions.
+
+## Completed Previous Cycle (2026-05-26 Evening)
+- **#50** — `docs/operator-runbook.md` added: ordered phase-by-phase manual for operator. PR #52 merged.
+- **#51** — Flux image automation: `ImageRepository` + `ImagePolicy` + `ImageUpdateAutomation` for all three API services; setter markers added to HelmReleases. PR #52 merged. `kustomize build flux/ = PASS`.
+
+## Completed Previous Cycle (2026-05-26 PM)
 - **#46** — Scaffolded Flux deployment manifests for all three API services (zip-enrichment, holidays, air-quality). PR #48 merged.
 
 ## Completed Previous Cycle (2026-05-26 AM)
@@ -33,19 +57,22 @@ Legend: [x]=done, [~]=in-progress, [ ]=not started
 - **#34** — Cluster audit PR merged
 
 ## Flux Manifests (kustomize build flux/ = PASS)
-All flux manifests validate successfully. Deployed components pending Flux activation:
+All flux manifests validate successfully. Committed components pending Flux activation:
 - `gitea-runner` namespace + HelmRelease (gitea-act-runner chart)
 - `monitoring` namespace + kube-prometheus-stack HelmRelease
 - `monitoring` Gatus HelmRelease (status.leeworks.dev, 90-day retention)
 - `docs-site` HelmRelease (docs.leeworks.dev)
-- `zip-enrichment` namespace + HelmRelease (zip.leeworks.dev) + rapidapi-proxy-secret placeholder ← NEW
-- `holidays` namespace + HelmRelease (holidays.leeworks.dev) + rapidapi-proxy-secret placeholder ← NEW
-- `air-quality` namespace + HelmRelease (aqi.leeworks.dev) + rapidapi-proxy-secret placeholder ← NEW
+- `zip-enrichment` namespace + HelmRelease (zip.leeworks.dev) + rapidapi-proxy-secret placeholder
+- `holidays` namespace + HelmRelease (holidays.leeworks.dev) + rapidapi-proxy-secret placeholder
+- `air-quality` namespace + HelmRelease (aqi.leeworks.dev) + rapidapi-proxy-secret placeholder
+- `image-automation` ImageRepository + ImagePolicy + ImageUpdateAutomation for all three APIs
 
 ## Blockers (human operator action required)
-1. **Create `0xWheatyz/api-company` repo on Gitea** — every ship cycle fails until this exists (#41, #47)
+1. **Create `0xWheatyz/api-company` repo on Gitea** — every ship cycle fails until this exists (#41, #47) **<-- DO THIS FIRST**
 2. **Add api-company GitRepository+Kustomization to 0xWheatyz/Talos** at `testing1/first-cluster/cluster/flux/` — reference manifests ready in `flux/api-company-source/` (#2)
 3. **Create `gitea-leeworks-agents-token` secret** in `flux-system` namespace (HTTPS token for Gitea)
-4. **Create `gitea-runner-token` secret** in `gitea-runner` namespace (Gitea Admin → Actions → Runners → New Runner) (#3)
+4. **Create `gitea-runner-token` secret** in `gitea-runner` namespace (Gitea Admin -> Actions -> Runners -> New Runner) (#3)
 5. **Enable Gitea packages** (for container registry at `registry.leeworks.dev`) (#4)
 6. **RapidAPI + PayPal setup** — manual, gated on operator turning 18 (#19, #44)
+
+> Full ordered runbook with copy-paste commands: `docs/operator-runbook.md`

docs/secrets-checklist.md

@@ -16,6 +16,9 @@ Follow this list top-to-bottom; each step unblocks the next.
 - [ ] 5. `GITEA_TOKEN` in each API repo's Actions Secrets — unblocks CI image push
 - [ ] 6. Gitea packages enabled + DNS record for `registry.leeworks.dev` — unblocks image push to registry
 - [ ] 7. Add api-company Flux source + kustomization to 0xWheatyz/Talos — unblocks all GitOps reconciliation
+- [ ] 8. `gitea-registry` (zip-enrichment, holidays, air-quality, docs-site) — imagePullSecret for pods pulling from `registry.leeworks.dev`
+- [ ] 9. `gitea-image-automation-token` (flux-system) — write-scoped token for Flux ImageUpdateAutomation to push image-tag commits
+- [ ] 10. `rapidapi-proxy-secret` (zip-enrichment, holidays, air-quality) — RapidAPI Proxy Secret for server-side request validation
 
 ---
 
@@ -153,6 +156,44 @@ Unblocks: Issue #2 (Flux reconciliation of all `flux/` manifests in this repo).
 
 ---
 
+---
+
+### 10. `rapidapi-proxy-secret` — RapidAPI Proxy Secret (per API namespace)
+
+| Field     | Value |
+|-----------|-------|
+| Name      | `rapidapi-proxy-secret` |
+| Namespaces | `zip-enrichment`, `holidays`, `air-quality` |
+| Purpose   | Every API service validates the `X-RapidAPI-Proxy-Secret` header on every route. Requests without a valid secret return HTTP 403. |
+| Source    | RapidAPI dashboard → API Settings → Security → **Proxy Secret** (generated after each API listing is created) |
+| Unblocks  | Phase 3 server middleware; API services will start but reject all traffic without this secret |
+
+```bash
+for NS in zip-enrichment holidays air-quality; do
+  kubectl create secret generic rapidapi-proxy-secret \
+    --namespace=$NS \
+    --from-literal=X-RapidAPI-Proxy-Secret=<value-from-rapidapi-dashboard>
+done
+```
+
+**Source:** RapidAPI dashboard → select your API → Settings → Security → Proxy Secret
+
+> **Note:** Placeholder `ExternalSecret` manifests are committed at
+> `flux/zip-enrichment/externalsecret.yaml`, `flux/holidays/externalsecret.yaml`,
+> and `flux/air-quality/externalsecret.yaml`. These will auto-sync this secret
+> from the configured backend once the External Secrets Operator (ESO) is
+> deployed (see issue #61). Until then, create manually using the commands above.
+
+Verify:
+```bash
+for NS in zip-enrichment holidays air-quality; do
+  echo -n "$NS: "
+  kubectl get secret rapidapi-proxy-secret -n $NS -o jsonpath='{.data.X-RapidAPI-Proxy-Secret}' | base64 -d | wc -c
+  echo " chars"
+done
+```
+
+
 ## Dependency Order
 
 ```
@@ -162,6 +203,66 @@ Unblocks: Issue #2 (Flux reconciliation of all `flux/` manifests in this repo).
 3 (grafana-admin)        → Grafana login works
 4 (gatus-slack-webhook)  → Gatus alerting works
 5 + 6 (GITEA_TOKEN + registry packages) → CI pushes images → API services deploy
+8 (gitea-registry)       → pods can pull images from registry.leeworks.dev → services start
+9 (gitea-image-automation-token) → Flux ImageUpdateAutomation pushes tag-update commits
+10 (rapidapi-proxy-secret × 3)  → API server middleware validates RapidAPI requests → revenue enabled
 ```
 
-Once all seven items are complete, the full stack (runner, registry, Prometheus, Grafana, Gatus, docs-site, three API services) reconciles automatically via FluxCD with no further manual steps.
+Once all nine items are complete, the full stack (runner, registry, Prometheus, Grafana, Gatus, docs-site, three API services) reconciles automatically via FluxCD with no further manual steps.
+
+---
+
+### 8. `gitea-registry` — imagePullSecret for API service namespaces
+
+| Field     | Value |
+|-----------|-------|
+| Name      | `gitea-registry` |
+| Namespaces | `zip-enrichment`, `holidays`, `air-quality`, `docs-site` |
+| Type      | `kubernetes.io/dockerconfigjson` |
+| Purpose   | Allows pods to pull images from `registry.leeworks.dev` without ImagePullBackOff |
+| Source    | Gitea token with `read:packages` scope (can reuse the same token as step 1 if it has that scope) |
+| Unblocks  | Issues #58 (Phase 0 hard deploy blocker) and transitively Phase 3 service deploys |
+
+```bash
+for NS in zip-enrichment holidays air-quality docs-site; do
+  kubectl create secret docker-registry gitea-registry \
+    --namespace=$NS \
+    --docker-server=registry.leeworks.dev \
+    --docker-username=leeworks-agents \
+    --docker-password=<GITEA_TOKEN_WITH_READ_PACKAGES> \
+    --docker-email=agent@leeworks.dev
+done
+```
+
+Verify:
+```bash
+kubectl get secret gitea-registry -n zip-enrichment -o jsonpath='{.type}'
+# expected: kubernetes.io/dockerconfigjson
+```
+
+---
+
+### 9. `gitea-image-automation-token` — Flux ImageUpdateAutomation write token
+
+| Field     | Value |
+|-----------|-------|
+| Name      | `gitea-image-automation-token` |
+| Namespace | `flux-system` |
+| Purpose   | Allows Flux `ImageUpdateAutomation` to push image-tag update commits back to `leeworks-agents/api-company` |
+| Source    | Gitea token with **`write:repository`** scope (the existing `gitea-leeworks-agents-token` only has `read:repository` — create a separate token or verify scope) |
+| Unblocks  | Issue #57 (Flux ImageUpdateAutomation for api-company) |
+
+```bash
+kubectl create secret generic gitea-image-automation-token \
+  -n flux-system \
+  --from-literal=username=leeworks-agents \
+  --from-literal=password=<TOKEN_WITH_WRITE_REPO_SCOPE>
+```
+
+Verify after creation:
+```bash
+flux get imageupdateautomations -n flux-system
+# Expected: api-company shows READY=True
+```
+
+> **Note:** If you create a new token with `write:repository` scope, keep the existing `gitea-leeworks-agents-token` for read-only Flux GitRepository pulls and use this new secret exclusively for `ImageUpdateAutomation`.

flux/image-automation/imageupdateautomation.yaml

@@ -32,6 +32,8 @@ spec:
         chore(image): update {{range .Updated.Images}}{{.Repository}}:{{.NewTag}} {{end}}
     push:
       branch: main
+      secretRef:
+        name: gitea-image-automation-token  # must pre-exist in flux-system ns — see docs/secrets-checklist.md item 9
   update:
     path: ./flux
     strategy: Setters