Maintenance script ran clean (skills-index 346 -> 347, freshness audit, Quartz rebuilt 596 files and deployed, hermes-wiki-serve.service restarted). infrastructure/tailscale.md — node table rebuilt from live `tailscale status --json`. The 2026-10-19 table had drifted: octop (100.92.163.122) and springroll (100.100.153.125) missing entirely, openmausbot / openmausbot-vm present in prose but absent from the table body, omarchymac now offline, all offline ages stale. Rebuilt keyed on DNS name rather than the JSON HostName — HostName is `ct260` for the freshrss node and BOTH OmniRoute nodes report the hostname `omniroute`, which collides silently. Now 51 non-funnel nodes. Container states cross-checked against live `pct list` on pve and m93p: CT255 stopped, CT601 stopped, CT299 running. reports/uber-eats/ — 2026-08 and 2026-09 recovered. The generator wrote only to ~/wiki/reports/uber-eats/ and never to the canonical tree, so both months were missing from the published wiki. Root cause fixed in ~/.hermes/cron/scripts/generate-uber-eats-report.py: it now targets ~/workspace/agent-estate-wiki/reports/uber-eats/ and mirrors to the legacy tree, and now emits YAML frontmatter (without it the pages landed in the audit's "no updated DATE" bucket and Quartz could not read the page date). 2026-08 previous-month column corrected from $0.00 to $264.51 / 11 orders. incidents/2026-08-15-skills-index-drift.md — re-verified live; the named regenerate-skills-index.sh no longer exists on disk (regeneration now lives in wiki-maintain.sh step 1/3). Incident prevention confirmed working: 347 skills. incidents/2026-09-02-sftpgo-outage.md — re-verified live: CT299 running, health endpoint HTTP 401 (auth required, service up), no recurrence. reports/communities-wa-social-media-audit-2026.md — left stale (54d). Its source document no longer exists on disk, so the baseline cannot be re-verified against a live source. Flagged, not edited. Freshness after this run: 1 stale, 94 fresh, 6 no-date of 101 pages.
1.7 KiB
1.7 KiB
title, type, status, created, updated, verified_on, confidence, tags
| title | type | status | created | updated | verified_on | confidence | tags | |||
|---|---|---|---|---|---|---|---|---|---|---|
| Uber Eats Monthly Reports | collection | active | 2026-08-02 | 2026-10-21 | 2026-10-21 | high |
|
Uber Eats Monthly Reports
Monthly spend reports generated from Camofox-authenticated Uber Eats sessions.
How it works
- Cron job
066bb5191280runs on the 1st of each month at 02:00 AWST - Opens a Camofox tab (profile
anthony) and navigates toubereats.com/orders - Captures the
getPastOrdersV1API response - Saves JSON to
~/.hermes/uber_eats_report.json - Generates HTML report + markdown page via
~/.hermes/cron/scripts/generate-uber-eats-report.py - Delivers a formatted Telegram digest
Output path note (verified 2026-10-21): the generator writes to
~/wiki/reports/uber-eats/(the~/wikirepo), not directly into this wiki tree. The monthly pages were therefore absent fromagent-estate-wikifor 2026-08 and 2026-09 until they were copied in on 2026-10-21.
Reports
| Month | Spend | Orders | Avg/Order | Report |
|---|---|---|---|---|
| 2026-09 | $51.29 | 2 | $25.65 | reports/uber-eats/2026-09 |
| 2026-08 | $211.16 | 7 | $30.17 | reports/uber-eats/2026-08 |
| 2026-07 | $264.51 | 11 | $24.05 | reports/uber-eats/2026-07 |
Known issue
The 2026-10-01 run (2026-09 report) generated its data correctly but failed delivery:
configured thread_id 34795 for telegram:1793951355 was not found — the job delivers to a bare
telegram target that no longer resolves to that topic. The 2026-10 report is therefore missing
and the 2026-11-01 run is still pointed at the same broken target.
Related
- systems/scheduled-tasks — cron job
066bb5191280 - runbooks/job-radar