mcp-v0.23.10
A freshly-created lens no longer reads as "empty" (product#3833).
leadbay_new_lens— creating a lens with criteria queues an asynchronous backend wishlist rebuild, so an immediateleadbay_pull_leadscan read empty for a few seconds while it computes. Thecreatedresult now carriescomputing_wishlist: trueand a "leads stream in — pull in ~30s" message so the agent waits instead of reporting an empty lens. A criteria-less clone inherits the base lens's leads immediately (computing_wishlist: false).leadbay_pull_leads— on an EMPTY page where the backend reports the lens is still computing (computing_wishlist/computing_scores),next_stepsnow carries a single "Re-pull in ~30s" option (kind: repull_computing) instead ofnull, so the agent renders a wait-and-retry widget rather than "no leads." An empty page with nothing computing still returnsnull(a genuinely empty / over-narrow lens — no fabricated leads).- Confirmed against
leadbay/backend(POST /lenses/:id/filter→queueRefreshJob→RefreshLens) and a live probe onapi-us: a bare clone shows leads instantly; a filtered clone showscomputing_wishlist: truethen settles within ~1–30s.