Everything I could decide myself is decided. What's left needs
you. Each one carries the recommendation of the session that raised it — if you
agree, pick it and press Done. A model's opinion, where there is one, appears on the card
as a receipt line; cards with no receipt were never put to a model. "I'm not sure" is a real answer and becomes work for me.
You don't need to open the session — pressing Done sends your answer back and it picks up.
1Lift the work_orders park (lambda/appfolio-sync/schedules.json, DISABLED since 2026-09-12 after the 429 storm)? Its recorded re-enable condition — the per-account request budget — is enforced on jpco and westernslopepm since 09-13, and the WORK_ORDERS_PORTFOLIO arm (whole account in ≤3 requests per tick instead of one call per property, ~258 req/min at the flood) is ON for both since 09-13/09-14 (Trinity read propflow-prod CONFIG rows just now). The only thing NOT done: nobody has run scripts/work-orders-portfolio-dryrun.ts against jpco — the 09-14 grouping proof was unit_vacancy, a different report. The script header says a jpco run needs Fede's explicit go. Un-parking is a one-line state flip via PR; the deploy re-arms the every-minute sync.
In plain terms. Do you want to turn the every-minute AppFolio work-order sync back on — with one small read-only test on the JP&Co account first, right away, or not at all? It has been off since the 09-12 flood, and both protections that keep it from flooding again are now on.
The session raising this recommends: Fede does one read-only test on JP&Co first, then turn it on The dry-run is ≤5 read-only requests and is the only check that proves the work_order report groups by property the same way the per-property walk did; without it the first live tick on jpco is the test. Tried first, unsuccessfully: Confirmed on origin/main: schedules.json work_orders state=DISABLED; scripts/work-orders-portfolio-dryrun.ts exists (hard cap 3 requests, refuses to arm). Asked Trinity (q-0a9183db) to read the prod CONFIG rows: all 8 portfolio arms ON on both accounts, budget enforce=true on both. Did NOT run the dry-run — its header forbids a jpco run without Fede's go. No open block on the ledger covers this park (checked outstanding).