Deploy Checklist — light up the bot upgrades

Everything else is done (code pushed, pulse fixed + re-enabled, queue cleaned, committed). These 4 need you at a keyboard.
Generated: Wed, May 27 2026 · 12:40 PM EDT (NY)
Open the Apps Script editor:
script.google.com → command-inbox project

1. Run setupRichContext

Function dropdown (top toolbar) → pick setupRichContextRun. (If it asks for permission: Review → Allow.)
→ Bot knows your 24 facts: your world, businesses, people, grocery baseline, kids' schools.

2. Run runBrainTests  (optional)

dropdown → runBrainTestsRun → open Execution log (View → Logs).
→ Proves the eyes work — log prints the tangerine link + your "hot coffee" fact. No API cost. Delete the few TEST rows after.

3. Redeploy (New version)

Top-right Deploy → Manage deployments → ✏️ pencil (edit) → Version: New version → Deploy.
→ Turns on the eyes (search/retrieval) + the no-duplicates / no-auto-done / day-aware fix for the live bot.

4. Test it

In Telegram, text the bot: "give me the tangerine link" — then try "what do you know about my coffee?" and "anything open on Eden?"
→ If it searches and answers, the bot went from one-shot-glance to actually-can-look.
One caution on step 3: use New version on the existing deployment — do NOT create a new deployment. A new deployment changes the URL and breaks the bot webhook + your notifications.

After this works, the next build is your call: (a) the self-digest cadence (bot summarizes itself on a cadence + briefs you + stages for commit — now possible because of the eyes) or (b) v3 cashflow (money in the brief — the v3 engine is already coded, just needs to be run).