max / makenotwork

Point pom's prod backup check at the directory that exists Two problems with the hetzner config, both found while deploying pom 0.4.0 to prod and reading the first status.json it served. The backup check watched /opt/makenotwork/backups, which does not exist on that host. The nightly job writes /var/lib/mnw/backups/makenotwork/, the app lives at /opt/mnw/current, and nothing is under /opt/makenotwork at all, so the old path reads as a leftover from before a rename. The effect was worse than a wrong path: the target sat degraded citing a missing directory while the real backups, which are healthy and daily, went unwatched. A check that cannot find what it watches is not monitoring it. This file was also missing the [targets.mnw.tests] block that prod's live config carries, which made it unsafe to install: deploy.sh copies it over /etc/pom/pom.toml, so deploying would have silently dropped prod's remote CI check. Both are now in step, and the only difference left against prod is the corrected path.