reports(uber-eats): add October 2026 report, correct historical timestamps to Perth time

- Add 2026-10 report: 9 orders, $301.04 total, $33.45 avg
- Regenerate 2026-07/08/09 with correct Australia/Perth timestamps
  (Camofox browser TZ was hardcoded to America/Los_Angeles, making
  Uber's DOM render receipt times 15h behind with AM/PM stripped)
- Totals unchanged for historical months; only timestamps corrected
- Preserve original 'created' frontmatter date on regeneration
- Fix cron job 066bb5191280 delivery target + port reference
This commit is contained in:
Tony0410
2026-11-01 05:56:18 +08:00
parent a0b3734c95
commit 8bb3d196b1
10 changed files with 248 additions and 71 deletions
+43 -15
View File
@@ -3,8 +3,8 @@ title: Uber Eats Monthly Reports
type: collection
status: active
created: 2026-08-02
updated: 2026-10-21
verified_on: 2026-10-21
updated: 2026-11-01
verified_on: 2026-11-01
confidence: high
tags: [reports, uber-eats, finance]
---
@@ -15,29 +15,57 @@ 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
- Opens a Camofox tab (profile `anthony`) and navigates to `ubereats.com/orders`
- Captures the `getPastOrdersV1` API 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
- 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`
- 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
- Delivers a formatted Telegram digest to Anthony's DM (`telegram:1793951355`)
> **Output path note (verified 2026-10-21):** the generator writes to `~/wiki/reports/uber-eats/`
> (the `~/wiki` repo), **not** directly into this wiki tree. The monthly pages were therefore absent
> from `agent-estate-wiki` for 2026-08 and 2026-09 until they were copied in on 2026-10-21.
> **Output path note (verified 2026-10-21):** the generator writes to
> `~/workspace/agent-estate-wiki/reports/uber-eats/` **and** mirrors to
> `~/wiki/reports/uber-eats/`. Both trees are kept in sync.
## Reports
| Month | Spend | Orders | Avg/Order | Report |
|---|---|---|---|---|
| 2026-10 | $301.04 | 9 | $33.45 | [[reports/uber-eats/2026-10]] |
| 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.
## Resolved issues (2026-11-01)
- **Timezone — fixed at the source.** Camofox hardcoded `en-US` /
`America/Los_Angeles` / San Francisco geolocation, so Uber rendered Perth
orders 15 hours off and the older reports carried wrong dates (the 2026-09
page showed "10:35" for an order placed at 10:35 **PM**). The browser context
identity is now configurable (`CAMOFOX_BROWSER_LOCALE`,
`CAMOFOX_BROWSER_TIMEZONE`, `CAMOFOX_BROWSER_LATITUDE`,
`CAMOFOX_BROWSER_LONGITUDE`) and the service runs as `en-AU` /
`Australia/Perth` / Perth. Defaults are unchanged for other deployments.
- **Wrong API port in the cron prompt.** It said `localhost:9093`; the service
listens on **9377** (9093 has never existed on this host).
- **Delivery target.** The job inherited `TELEGRAM_HOME_CHANNEL_THREAD_ID=34795`,
a topic that no longer exists, so runs were recorded `delivery_failed`
("configured thread_id 34795 … was not found"). It now targets
`telegram:1793951355` explicitly, matching the other healthy jobs.
- **Pagination truncation.** An early scrape kept only 130 of 156 orders
because the `lastWorkflowUUID` cursor was advanced incorrectly. The scraper
now guards the loop, de-duplicates by order uuid and warns if fewer than
100 unique orders come back.
- **Report month.** The builder now picks the most recent *complete* calendar
month, so a stray order placed on the 1st before the cron fires cannot
produce a one-day "month" report.
## 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.
August ($211.16 / 7 orders) and September ($51.29 / 2 orders / $25.65 avg)
match the previously published figures.
## Related
- [[systems/scheduled-tasks]] — cron job `066bb5191280`