Pin OpenStatus monitor IDs

[ComputelessComputer]

What

• replace temporary config keys with the real OpenStatus monitor IDs
• add matching lockfile entries for all 11 managed monitors
• keep the three public subsystem components bound to their original monitor IDs

Why

The first IaC apply treated the temporary keys as new resources and created three duplicate subsystem monitors instead of updating the existing monitors. Pinning the IDs makes future applies update in place.

Validation

• openstatus.yaml and openstatus.lock contain the same 11 IDs
• every lock entry matches its YAML monitor definition
• the three accidental duplicate IDs will be removed from OpenStatus after this apply succeeds

---

Note

Low Risk
Config-only changes to OpenStatus IaC; risk is limited to apply-time monitor create/update/delete behavior in the external OpenStatus project.

Overview
Pins all 11 OpenStatus monitors to their real remote IDs in openstatus.yaml, replacing temporary slug keys (e.g. anarlog-sync-api) with numeric keys (11509, etc.) so openstatus monitors apply updates existing monitors instead of creating duplicates.

Expands openstatus.lock to cover every managed monitor (not just the three public components 11026–11028), with quoted YAML keys normalized and a document header added. Lock entries mirror the YAML definitions for sync, transcription, LLM health checks, auth-guard probes, MCP OAuth discovery, and billing.

After apply, stray duplicate monitors from the first IaC run should be removable while the three original subsystem IDs stay bound to API, Web, and Docs.

^{Reviewed by Cursor Bugbot for commit d4f97d7. Bugbot is set up for automated code reviews on this repo. Configure here.}

[netlify]

✅ Deploy Preview for anarlog canceled.

Name	Link
🔨 Latest commit	d4f97d7
🔍 Latest deploy log	https://app.netlify.com/projects/anarlog/deploys/6a96d0edadd4f80007ec840b