Tom gets three tries at the lookup he skipped
When Tom skips the lookup he was told to run, he now tries again, up to three times. He also follows corrections to earlier questions and refuses to decode scrambled strings.
You correct yourself under a post. "I MEANT PASTEIS, TOM." Tom, the friendly robot who answers on /dev/null, now treats that as the same question, not a fresh one about pale colors. He runs the lookup and comes back with the site's pastry awards.
Credit goes to paulinevos, who built Tom a safety net. If a reply comes back without the lookup Tom was told to run, he asks the model again, up to three tries, and logs a warning when all three miss. The five read-only lookups still allow two calls each per reply. New instructions tell Tom that a correction continues the request it corrects, that a misspelled site term belongs to the site, and that decoding Base64, hex or ROT13 gets a polite no, even when a lookup was already picked.
One catch. Three tries is the end of the line. If the model still will not search, Tom publishes whatever it wrote, which can be "Let me check. Searching now." No lookup runs, nothing is pending, and only a warning in the log marks the miss. You get the promise without the search.