From a0ec3a1ec50dceffd75f78e97978d1df4ee39113 Mon Sep 17 00:00:00 2001 From: Tony0410 <47945770+Tony0410@users.noreply.github.com> Date: Fri, 13 Nov 2026 19:39:50 +0800 Subject: [PATCH] reports: document the 2026-11-13 digest-script fix and re-verification --- reports/uber-eats/index.md | 36 ++++++++++++++++++++++++++++++++---- 1 file changed, 32 insertions(+), 4 deletions(-) diff --git a/reports/uber-eats/index.md b/reports/uber-eats/index.md index 6c37cc7..f620202 100644 --- a/reports/uber-eats/index.md +++ b/reports/uber-eats/index.md @@ -3,8 +3,8 @@ title: Uber Eats Monthly Reports type: collection status: active created: 2026-08-02 -updated: 2026-11-01 -verified_on: 2026-11-01 +updated: 2026-11-13 +verified_on: 2026-11-13 confidence: high tags: [reports, uber-eats, finance] --- @@ -16,12 +16,16 @@ Monthly spend reports generated from Camofox-authenticated Uber Eats sessions. ## How it works - Cron job `066bb5191280` runs on the 1st of each month at 02:00 AWST - Scrape: `~/.hermes/cron/scripts/scrape-uber-eats-orders.py` - → paginates Uber's `getPastOrdersV1` API to the end of history (156 orders, - 16 pages as of 2026-11-01) → `~/.hermes/cache/scratch/uber_raw.json` + → paginates Uber's `getPastOrdersV1` API to the end of history (154 unique orders, + 16 pages as of 2026-11-13) → `~/.hermes/cache/scratch/uber_raw.json` - Build: `~/.hermes/cron/scripts/build-uber-eats-report.py` → `~/.hermes/uber_eats_report.json` - Publish: `~/.hermes/cron/scripts/generate-uber-eats-report.py` → this wiki tree + the `~/wiki` mirror +- Digest: `~/.hermes/cron/scripts/uber-eats-digest.py` + → prints the finished Telegram digest from the report JSON; the cron job + replies with it byte for byte (added 2026-11-13 — the model used to format + the digest itself and run out of turns before finishing) - Delivers a formatted Telegram digest to Anthony's DM (`telegram:1793951355`) > **Output path note (verified 2026-10-21):** the generator writes to @@ -61,6 +65,30 @@ Monthly spend reports generated from Camofox-authenticated Uber Eats sessions. month, so a stray order placed on the 1st before the cron fires cannot produce a one-day "month" report. +## Resolved issues (2026-11-13) + +- **Degraded digest — the real defect.** The 2026-11-01 run exhausted its turn + budget (its runtime prompt was ~88k characters because the job loaded two + heavy browser skills) *after* scraping but *before* formatting, so the + delivered October digest shipped placeholders ("remaining 4 in the report", + "see report (wiki link below)") plus a block of run commentary that the job + spec forbids. Fixes: the digest is now printed by + `~/.hermes/cron/scripts/uber-eats-digest.py`, so the numbers can never + degrade into placeholders; the job loads no skills (runtime prompt 3k) and the + prompt carries a hard output contract — reply with the script's stdout byte + for byte or the single BLOCKED line on any non-zero exit. +- **Stale `delivery_failed` label.** The `TELEGRAM_HOME_CHANNEL_THREAD_ID` + env-var fix required a gateway restart to take effect; the gateway restarted + 2026-11-13 13:14, so the 34795 thread is gone from the live process and the + 2026-11-13 18:58 run delivered cleanly (`last_status: ok`, + `hermes cron doctor` reports no issues). + +## Verification (2026-11-13) +Full pipeline re-run end to end: 154 unique orders scraped, 153 completed, +October = 9 orders / $301.04 — identical to the previously published figures, +re-verified against the freshly scraped data rather than the old artifact. +The 2026-10 wiki page was regenerated (only its timestamps changed) and pushed. + ## Verification (2026-11-01) All nine October orders were cross-checked against the live Uber Eats DOM (`ubereats.com/orders`): every date, time and amount matched exactly.