monitor-scaffoldlisted

# Monitor scaffold ## Purpose Drop in a working supervisor configuration for each service in the project's `profile.monitors.targets` list. Operator picks the supervisor type once; the scaffold emits the right config per service. This skill is the first half of the soft+hard pairing for Standard 3 (monitors). The rule is the second half. ## Scope Operates on the operator's project repo. Adds: - A supervisor config file per service in `profile.monitors.targets` - A `/healthz` endpoint stub in each target service's source (if not already present) - `docs/runbooks/<service>-runbook.md` for each target service (skeleton — operator fills in) NOT in scope: - Cloud-specific supervisor variants (ECS, Cloud Run, Fly.io) — these vary too much; scaffold writes for the most common 4 (systemd, pm2, k8s, docker-compose) - Production observability dashboards (Grafana / Datadog UIs) - Auto-scaling configuration - Alert routing ## Automated pass 1. Read `.yakos.yml` `profile.monitors.targets` and `profile.monitors.supervisor` (default: ask interactively or take `--supervisor` flag). 2. For each service in targets: ### systemd variant - Writes `deploy/systemd/<service>.service`: ```ini [Unit] Description=<service> (yakOS-managed) After=network.target [Service] Type=simple User=<service> WorkingDirectory=/opt/<service> ExecStart=/opt/<service>/bin/<service> Restart=on-failure RestartSec=5 StandardOutpu