@leadbay/mcp 0.39.4 → 0.39.5

package/dist/bin.js

@@ -1895,6 +1895,8 @@ to pick, then re-call with the id/exact name.
 
 Restrict (or expand) the lens audience by sector / size. Free-text sectors are auto-resolved against the sector taxonomy; ambiguous matches are surfaced to the agent rather than guessed silently. Permission routing is hidden: the default lens auto-clones to a new user lens; an org-level lens defaults to a per-user draft (admins can override with \`save_for_org:true\`). Filter MERGES with existing criteria (unrelated criteria are not dropped).
 
+**A complaint about relevance is not a filter request.** "The leads aren't relevant", "they don't look like my customers", "I keep getting the wrong companies" says the OUTPUT is wrong \u2014 it does not say which sector to add. Read \`leadbay_get_qualification_questions\` first (it returns the questions, the ideal buyer profile AND the targeting prompt), and find out WHICH leads were wrong, ideally by pulling some and pointing at them. Sector and size are only one of the places the answer can live; editing them blind fixes the wrong thing and leaves the real cause in place.
+
 **Targeting a lens \u2014 READ THIS.** By default this edits the user's ACTIVE lens. **If the user names a lens** ("add fintech to my **Joinery** lens", "in my Nordics lens, exclude retail"), you MUST pass \`lensName\` with that name (\`lensName:"Joinery"\`). Do NOT silently edit the active lens when a different one was named \u2014 that corrupts the wrong audience and is a top friction source. The name resolves against the user's lenses (case-insensitive, exact then unique-substring); it is edit-only and does NOT change which lens is active. An unmatched name returns \`status:"lens_not_found"\` with the lens list, and a name matching several returns \`status:"ambiguous_lens"\` with the candidates \u2014 surface them and re-call with the exact \`lensName\` or a \`lensId\`. Use \`leadbay_my_lenses\` if the user first wants to SEE or SWITCH lenses. To CREATE a brand-new lens, use \`leadbay_new_lens\` \u2014 not this tool.
 
 **Geography \u2014 scope a sales territory.** Pass \`locations\` (free text like \`["Indre-et-Loire"]\`, \`["Texas"]\`, \`["Austin"]\`, or admin-area ids) to restrict the lens to a region, and \`exclude_locations\` to carve one out. Free text auto-resolves via \`/geo/search\` at any level from state down to city \u2014 state, *r\xE9gion*, *d\xE9partement*, county, city. Unresolved/ambiguous text returns \`status:"ambiguous_locations"\` with candidates \u2014 surface them and re-call the chosen id via the SAME axis it came from: an INCLUDE pick \u2192 \`location_ids\`; an EXCLUDE pick \u2192 \`exclude_locations\` (**NOT** \`location_ids\`, which would include the area the user asked to exclude). The returned \`message\` names the right param per text. This is how a director scopes a rep's territory and then asks for net-new accounts there.
@@ -2766,7 +2768,7 @@ Do NOT use for: "show me today's leads / what's new today" \u2192 \`leadbay_pull
 Prefer when: the user describes a target profile or names a count of NEW companies \u2014 craft the example_lead per the seed rules below BEFORE calling; never pass the user's raw sentence as query.
 
 Examples that SHOULD invoke this tool:
-- "Find me 10 gyms around Dallas that would buy our flooring, with someone I can call."
+- "Find me 10 gyms around Dallas that would buy our flooring, with a contact."
 - "Get me 20 new US SaaS companies, 50-2000 employees, with the VP People's email."
 - "We're launching in Lyon \u2014 find 15 hotels that fit our ICP."
 
@@ -2777,11 +2779,10 @@ Examples that should NOT invoke this tool (sound similar, route elsewhere):
 
 ## RENDER (quick)
 
-3-col table of delivered leads in returned order: col 1 = 10-segment fit
-bar + linked company \xB7 location \xB7 size; col 2 = why-fits \u226420 words; col 3
-= contact + found channels. ALWAYS close with the honest funnel line
-(matched/examined/delivered/stop reason) \u2014 especially on 0
-delivered. Full algorithm below.
+3-col table of delivered leads in returned order: col 1 = 10-segment fit bar
++ linked company \xB7 location \xB7 size; col 2 = why-fits \u226420 words; col 3 =
+contact + found channels. ALWAYS close with the honest funnel line
+(matched/examined/delivered/stop reason), especially on 0 delivered.
 
 ---
 
@@ -2790,27 +2791,25 @@ company universe, applies hard filters, skips what the org already knows
 (\`novelty: org\`), optionally qualifies against the org's own intelligence
 (questions, tags, ideal buyer profile \u2014 frozen at submit), and optionally reveals
 contact channels. Polls up to \`wait_seconds\` (default 45); a longer job returns
-\`still_running\` + \`next_poll\` \u2014 hand off to \`leadbay_lead_job_status\`. Jobs run
+\`still_running\` + \`next_poll\` \u2014 hand to \`leadbay_lead_job_status\`. Jobs run
 \u226430 min, results kept 30 days.
 
 **Free vs usage quota \u2014 never use quota silently.** Default (\`qualify: false\`,
 \`channels: []\`) is FREE: company profile + fit score + cached research +
 contact identity. \`qualify: true\` (per candidate EXAMINED, capped by
 \`exploration_cap\`/\`max_cost\`) and \`channels\` (only when a value is found) draw
-on the org's usage quota; nothing is invoiced. Enforced in code: such a call is WITHHELD unless it
-carries \`confirm: true\` \u2014 nothing is submitted and you get
+on the org's usage quota; nothing is invoiced. Enforced in code: such a call is
+WITHHELD unless it carries \`confirm: true\` \u2014 nothing is submitted and you get
 \`mode: "needs_confirmation"\` with a real quote to show the user. Re-call with
 \`confirm: true\` on their go-ahead ("go ahead / get their emails" counts).
-\`confirm: false\` vetoes. Free needs no consent. **Preview free first** \u2014
-reshaping an off-profile seed is free, exploring it with \`qualify: true\` is
-not.
+\`confirm: false\` vetoes. **Preview free first** \u2014 reshaping an off-profile seed
+is free, exploring it with \`qualify: true\` is not.
 
 **Ad-hoc exclusions ("no chains") are enforced by NO tier** \u2014 \`filters\` has no
-exclusion key, and \`qualify\` scores against the org's FROZEN questions and IBP,
-which need not mention chains; the seed's inverse only shifts ranking.
-Violators can survive, use quota and be delivered \u2014 post-filter them yourself
-and say the tier didn't enforce it. Durable enforcement \u2192
-\`leadbay_refine_prompt\`.
+exclusion key, and \`qualify\` scores against the org's FROZEN questions and IBP.
+Violators survive, use quota and get delivered: post-filter them yourself and
+say the tier didn't enforce it. Durable enforcement \u2192
+\`leadbay_set_qualification_questions\` / \`leadbay_refine_prompt\`.
 
 ### Crafting the \`example_lead\` seed \u2014 the input that decides result quality
 
@@ -2830,13 +2829,13 @@ measured:
    model, what they sell or operate, who they serve, observable scale. Write
    it like the first paragraph of their About-Us page.
    - STRONG: "Operator of full-service fitness centers offering strength
-     areas, group classes and personal training to members across multiple
-     clubs."
-   - WEAK (generic): "A gym in Texas."
-   - WRONG (seller-side): "Supplier of durable modular flooring for gyms."
-4. **No event language.** "hiring", "expanding", "just raised" are not
-   filters \u2014 registry descriptions never contain them, so they dilute the
-   profile. Purchase triggers belong in the org's qualification questions.
+     areas, group classes and personal training to members across clubs."
+   - WEAK: "A gym in Texas." WRONG: "Supplier of gym flooring." (seller-side)
+4. **NO event language \u2014 in \`description\` or \`query\`.** "recrute", "hiring",
+   "expanding", "just raised" never appear in registry text, so they match
+   nothing. Send the trigger to \`leadbay_set_qualification_questions\` or
+   \`leadbay_refine_prompt\` and say so. "companies hiring a senior SDR" seeds as
+   "B2B software company operating an in-house outbound sales team."
 5. **No meta-markers.** Never "(example)", "(fictional)", "(placeholder)".
 6. **Hard constraints go in \`filters\`, not prose \u2014 exact keys:**
    \`sectors: string[]\`, \`locations: string[]\`, \`employees_min: number\`,
@@ -2846,24 +2845,22 @@ measured:
    never a country: this workspace's own is dropped, any other is refused.
 7. **Prefer \`example_lead\` over \`query\`.** Query matches topic *vocabulary*:
    "gyms that need durable flooring" surfaced flooring VENDORS, 0 delivered.
-   Use \`query\` only for signal an example can't express.
 8. **One seed per buyer archetype.** An ask spanning two segments ("gyms and
    warehouses") needs one search each with its own description and
-   \`request_id\` \u2014 a blended seed lands between the clusters and matches
-   neither.
+   \`request_id\` \u2014 a blended seed lands between the clusters, matching neither.
 
 
 **Parameter notes**
 - \`request_id\` (REQUIRED) is the retry contract: SAME value retrying the same
   ask (same live job, no double launch); NEW for a changed ask. Derive from ask
   + archetype + date: \`gyms-dallas-2026-07-28\`.
-- Never lower \`min_ai_score\` together with \`channels\` \u2014 that reveals emails for
-  leads the AI just scored as junk.
-- \`count\` \u2264 50; \u22643 active jobs/org; \u226410 submits/hour (429 + Retry-After \u2014
-  wait, don't hammer).
+- Never lower \`min_ai_score\` with \`channels\` \u2014 that reveals emails for leads
+  the AI just scored as junk.
+- \`count\` \u2264 50; \u22643 active jobs/org; \u226410 submits/hour (429 + Retry-After \u2014 wait,
+  don't hammer).
 
 **Read the result honestly** \u2014 \`funnel\` + \`explain.scope_notes\` tell the story;
-zero delivered gets a cause and a next move (rules in RENDERING).
+zero delivered gets a cause and a next move (RENDERING).
 
 ---
 
@@ -3344,26 +3341,28 @@ WHEN NOT TO USE: when the lead summary's \`prospecting_actions_count\` is 0.
 `;
     leadbay_get_qualification_questions = `## WHEN TO USE
 
-Trigger phrases: "what are my qualification questions", "what questions does Leadbay ask about each lead", "show me the org qualification questions", "how are my leads being qualified", "what's the qualification criteria".
+Trigger phrases: "what are my qualification questions", "what questions does Leadbay ask about each lead", "show me the org qualification questions", "how are my leads being qualified", "what's the qualification criteria", "(before any settings change) what is configured today", "why am I getting these leads", "the leads aren't relevant \u2014 what are my settings".
 
-Do NOT use for: "how did this lead score on the qualification questions" \u2192 \`leadbay_research_lead_by_id\`; "show my ideal buyer profile and intent tags" \u2192 \`leadbay_get_taste_profile\`.
+Do NOT use for: "how did this lead score on the qualification questions" \u2192 \`leadbay_research_lead_by_id\`; "change / add / remove a qualification question" \u2192 \`leadbay_set_qualification_questions\`; "answer a pending clarification" \u2192 \`leadbay_answer_clarification\`.
 
-Prefer when: user wants the ORG-level qualification questions catalog, no lead and no buyer profile
+Prefer when: user wants the ORG-level qualification settings, or you are about to change any of them \u2014 read this FIRST to see whether their rule is already covered
 
 Examples that SHOULD invoke this tool:
 - "What qualification questions does Leadbay use to score my leads?"
 - "Show me my org's qualification questions."
+- "Why do I keep getting these companies? What are my settings?"
 
 Examples that should NOT invoke this tool (sound similar, route elsewhere):
 - "How did Acme Corp answer the qualification questions?"
-- "What's my ideal buyer profile?"
+- "Add a question about install crews."
 
 ## RENDER (quick)
 
-Numbered list of the questions (chat-native markdown), each one line. When
-\`is_admin\` is true, append the \`hint\` as a footnote (points at
-leadbay_set_qualification_questions for editing). When the list is empty,
-render the \`hint\` instead.
+Numbered list of the questions (chat-native markdown), each one line,
+verbatim. Below it, the ideal buyer profile summary + anti-patterns and the
+targeting prompt when set. When \`is_admin\` is true, append the \`hint\` as a
+footnote (points at leadbay_set_qualification_questions). When the question
+list is empty, say so explicitly and render the \`hint\` instead.
 
 ---
 
@@ -3376,7 +3375,15 @@ Returns:
 
 - **\`qualification_questions\`** \u2014 the catalog. Each: \`{question, created_at,
   lang}\`. Ordered as the backend returns them.
-- **\`count\`** \u2014 number of configured questions.
+- **\`count\`** \u2014 number of configured questions. **Zero is a finding, not a
+  blank** \u2014 an org with no questions scores every lead on firmographics alone.
+  Say so and offer a starter set.
+- **\`ideal_buyer_profile\`** \u2014 \`{summary, key_characteristics, anti_patterns}\`
+  or null. The questions score against THIS. A rule the user states is often
+  already an \`anti_pattern\` here.
+- **\`targeting_prompt\`** \u2014 the org's free-text instruction to the AI agent, or
+  null. Qualitative rules that no single yes/no can express live here; change
+  it with \`leadbay_refine_prompt\`.
 - **\`is_admin\`** \u2014 whether the current user is an org admin. Modifying the
   questions (\`leadbay_set_qualification_questions\`) is an org-admin action; for
   admins a \`hint\` points there.
@@ -3384,25 +3391,132 @@ Returns:
   when no questions are configured.
 
 This tool only READS. To change the questions, use
-**leadbay_set_qualification_questions** (add / remove / replace). The result is
-cached on the client (it reuses the same taste-profile fetch as
-\`leadbay_get_taste_profile\`), so repeated calls in a session are cheap.
+**leadbay_set_qualification_questions**; to change the targeting prompt, use
+**leadbay_refine_prompt**; for sector / size / territory, use
+**leadbay_adjust_audience**. **leadbay_research_lead_by_id** shows how a
+SPECIFIC lead answered these questions.
+
+### A stated fit rule is a SETTING \u2014 read, decide, propose, then write
+
+**Never answer a stated rule from memory.** "C'est not\xE9", "already applied",
+"I'll keep that in mind", "the rule is now active" \u2014 every one of those is a
+claim about the user's ACCOUNT, and it is false unless a tool call made it
+true. The rule lives in the org's settings or it does not exist: your context
+window ends with this conversation, and the next session, the scheduled run and
+the user's colleague all read the account, not your memory. If you have not
+called a tool, do not say the rule is in place.
+
+When the user says what makes a lead good or bad \u2014 *"\xE9carte les soci\xE9t\xE9s
+liquid\xE9es"*, *"je ne veux pas d'associations"*, *"our best customers run their
+own maintenance crews"*, *"les leads ne sont pas pertinents"* \u2014 they are
+describing their account, not just this batch. Filter the batch and they say
+it again next week; their questions, buyer profile and targeting prompt never
+move.
+
+**1 \u2014 Read before you decide.** Call \`leadbay_get_qualification_questions\`
+first. It returns the question set PLUS the ideal buyer profile and the
+targeting prompt those questions sit beside. You cannot judge whether a rule is
+already covered without seeing them.
+
+**2 \u2014 Decide WHERE the rule belongs.** One rule, one destination:
+
+| What the user stated | Where it belongs |
+|---|---|
+| A sector, a headcount band, a territory | \`leadbay_adjust_audience\` / \`leadbay_new_lens\` filters \u2014 never a question |
+| A company trait a stranger could estimate from that company's own website or registry record \u2014 "runs its own maintenance crew", "operates a large vehicle fleet", "is legally active and not in liquidation" | a qualification question |
+| A qualitative orientation too broad for one yes/no \u2014 "we sell to the private sector, not the public one", "harden the exclusion on the business model" | the targeting prompt, \`leadbay_refine_prompt\` |
+| Named companies \u2014 "exclude Groupe Solidum, Dentego" | \`leadbay_dislike_lead\` / \`leadbay_set_lead_status\` on those leads. A question must NEVER name a company |
+| CRM state \u2014 "already contacted", "already in a campaign", "already excluded" | read it: \`leadbay_pull_followups\`, \`leadbay_list_campaigns\`. A question cannot observe your own history |
+| A delivery requirement \u2014 "email AND phone mandatory", "only score 54\u201395" | enrichment plus your own post-filter of the result. A question scores the COMPANY; it cannot see whether Leadbay holds a phone number for a contact |
+| An event or purchase trigger \u2014 "currently hiring an SDR", "just opened a site" | a qualification question or the targeting prompt. NEVER an \`example_lead\` description or a \`query\`: those match stable registry text, which never mentions events |
+
+**3 \u2014 Decide whether to change anything at all.** Touching a question
+re-scores every lead in the pipeline and draws on the org's quota, so a change
+that surfaces the same companies is a pure loss. Four reasons to write NOTHING
+and say why:
+
+1. **An existing question already covers the rule.** Quote that question back
+   and stop. **Never reword a question that already means the same thing** \u2014
+   even when the user asks you to "clarify" or "improve" the wording. A reword
+   is a removal plus an addition: it re-scores every lead, spends quota, and
+   surfaces exactly the same companies. Offer instead to find out whether any
+   question is testing the WRONG thing.
+2. **The audience filter already enforces it** \u2014 sector, headcount, territory.
+3. **An existing question already tests that dimension.** Two questions on one
+   dimension waste a slot and add no signal.
+4. **The question the user asked for is not decisive.** See step 4: say so,
+   offer the sharper version, and write only what they then choose. Adding a
+   question you know separates nothing is worse than adding none.
+
+**The ceiling is 5 questions.** Read the count before you answer an "add a
+question" request: at 5 the honest answer is not "sure, I'll add it". Say in
+that same turn that the set is full, list the five, and let the USER name which
+one goes. Never pre-pick the casualty.
+
+**4 \u2014 Write a DECISIVE question.** Check all six before you propose the text:
+
+1. **The estimative marker is literal and mandatory.** English questions start
+   \`Is the company likely to \u2026\`. French questions start
+   \`L'entreprise est-elle susceptible de/d' \u2026\`. There is no third form. The
+   scorer works from public text it cannot verify, so a verifiable question
+   scores almost everything as no.
+   - \u2705 \`Is the company likely to run its own in-house maintenance crew?\`
+   - \u274C \`Does the company run its own maintenance crew?\`
+   - \u274C \`Is the company a cold-storage plant?\` \u2014 no \`likely to\`
+   - \u2705 \`L'entreprise est-elle susceptible d'\xEAtre en liquidation judiciaire ?\`
+   - \u274C \`L'entreprise est-elle en liquidation ?\` \u2014 no \`susceptible\`
+2. **It tests the lead as a BUYER.** Before you write a question, ask: would
+   a company answering yes write a cheque to THIS user? A question that only
+   describes what the lead's own business does \u2014 "Is the company likely to
+   manufacture branded pharmaceuticals?" for a seller of advertising \u2014 is a
+   category test, not a buying test, and it scores the user's competitors and
+   suppliers as well as their prospects. Test the need the user's offering
+   meets: "Is the company likely to run consumer campaigns that need paid media
+   placement?"
+3. **Estimable from public material** \u2014 the company's website, its about page,
+   its job postings, its registry entry. Never its budget, its internal plans
+   or its future intentions. When the user's rule is un-observable ("has budget
+   for copywriting"), propose the observable proxy, and tell them you swapped
+   it and why.
+4. **One dimension each.** \`Is the company likely to operate a cold-storage
+   plant AND run its own maintenance crew?\` is two questions. Split it into
+   two, or pick the one that discriminates better.
+5. **Decisive.** It should split companies in general roughly 30/70 while the
+   user's own customers answer yes. A question nearly everyone answers yes to
+   \u2014 "has a website", "uses email", "is a company" \u2014 separates nobody. Do NOT
+   write it as asked: say it would add no signal, and offer the sharper version
+   you would write instead.
+6. **\u2264120 characters, in the user's language.**
+
+An org with **zero** questions scores every lead on firmographics alone. That
+is a finding worth stating, and the fix is a starter set of **3** questions on
+three different dimensions \u2014 not one. Propose all three at once.
+
+**5 \u2014 The change is the user's call, not yours.** This holds for the questions,
+the targeting prompt and the buyer profile alike. Show the exact text you
+propose and what it will change, then get an explicit yes before calling
+\`leadbay_set_qualification_questions\` or \`leadbay_refine_prompt\`. Ask through
+\`ask_user_input_v0\` when the host offers it. A removal or a swap additionally
+needs \`confirm:true\`. Do not write an org setting in the same turn the user
+first stated the rule \u2014 and once they have said yes, actually write it:
+describing the change is not making it.
+
+**Answer the ask as well.** A rule stated in passing \u2014 *"sors-moi les leads du
+jour, et arr\xEAte de me remonter des h\xF4pitaux publics"* \u2014 does not replace the
+ask. Deliver the leads first, then raise the setting.
 
-Companion tools: **leadbay_set_qualification_questions** to modify the questions;
-**leadbay_get_taste_profile** when the user also wants the Ideal Buyer Profile +
-purchase-intent tags; **leadbay_research_lead_by_id** for how a SPECIFIC lead
-answered these questions; **leadbay_refine_prompt** to shape the AI agent's
-behaviour.
 
 ### RENDERING
 
 Render \`qualification_questions\` as a numbered list \u2014 one question per line, in
 the order returned. Lead with a short heading like **"Qualification questions
-(N)"**. When \`qualification_questions\` is empty, render the \`hint\` sentence
-instead of an empty list. When \`is_admin\` is true and there are questions,
-append the \`hint\` as a one-line footnote (points at
-leadbay_set_qualification_questions). Do not invent questions or reword them \u2014
-render verbatim.
+(N)"**. Then, when present, the \`ideal_buyer_profile\` summary with its
+\`anti_patterns\` as a short bulleted list, and the \`targeting_prompt\` as a
+blockquote. When \`qualification_questions\` is empty, say **"You have no
+qualification questions \u2014 leads are scored on firmographics alone"** and render
+the \`hint\`. When \`is_admin\` is true and there are questions, append the \`hint\`
+as a one-line footnote. Do not invent questions or reword them \u2014 render
+verbatim.
 `;
     leadbay_get_quota = `Read quota / spend across daily, weekly, and monthly windows. The response has two scope groups: **\`user\`** (present for every caller) and **\`org\`** (admin-only \u2014 \`null\` for non-admins). **Read from \`user\` first**, falling back to \`org\` only when \`user\` is absent. Each group carries \`spend[]\` (the dollar-spend gauge: \`current_units\` / \`max_units\` in dollar_cents \u2192 % used = the ratio, $ = \`/100\`) and \`resources[]\` (per-resource usage: \`{resource_type, count (used), max_units (cap or null), window_type, resets_at}\`). \`spend[]\` is empty for orgs with no OVERALL_SPEND quota \u2014 fall back to the \`resources[]\` counts then. There is also a top-level \`topup\` ({remaining_cents, total_credit_cents}) when present. Resource types may arrive lowercase (\`lens_extra_refill\`) or uppercase \u2014 match case-insensitively. Present quota as a percentage / dollar figure, never raw "credits".
 
@@ -5490,20 +5604,22 @@ WHEN NOT TO USE: when you already know the exact titles you want to enrich.
 `;
     leadbay_refine_prompt = `## WHEN TO USE
 
-Trigger phrases: "focus on companies that <qualitative trait>", "I prefer leads that <behavior/characteristic>", "prioritize companies running their own IT", "deprioritize companies that just raised".
+Trigger phrases: "focus on companies that <qualitative trait>", "I prefer leads that <behavior/characteristic>", "prioritize companies running their own IT", "deprioritize companies that just raised", "stop showing me <kind of company>", "we only sell to the private sector, not the public one", "harden the exclusion on <business model>, not the keyword", "competitors / resellers are never prospects for us".
 
-Do NOT use for: "create a new lens / a lens specialized into <X>" \u2192 \`leadbay_new_lens\`; "add/remove <sector> to/from my <name> lens" \u2192 \`leadbay_adjust_audience\`; "narrow the audience to <sector> / <size>" \u2192 \`leadbay_adjust_audience\`; "show me / list / switch my lenses" \u2192 \`leadbay_my_lenses\`.
+Do NOT use for: "create a new lens / a lens specialized into <X>" \u2192 \`leadbay_new_lens\`; "add/remove <sector> to/from my <name> lens" \u2192 \`leadbay_adjust_audience\`; "narrow the audience to <sector> / <size>" \u2192 \`leadbay_adjust_audience\`; "show me / list / switch my lenses" \u2192 \`leadbay_my_lenses\`; "a company trait one yes/no question could estimate from their website" \u2192 \`leadbay_set_qualification_questions\`; "exclude <named company>" \u2192 \`leadbay_dislike_lead\`.
 
-Prefer when: ADMIN-ONLY. Qualitative refinement of the active lens that sector/size can't express. Creating/naming/listing/switching/sector-editing a lens routes elsewhere. Non-admin user \u2192 do NOT pick this.
+Prefer when: ADMIN-ONLY. A qualitative ORIENTATION too broad for one yes/no \u2014 a segment to avoid, a business model to rule out. One estimable company trait goes to set_qualification_questions; a named company to dislike_lead.
 
 Examples that SHOULD invoke this tool:
 - "Focus on hospitals that run their own IT in-house."
 - "Prioritize companies that have recently expanded headcount."
+- "On ne vend qu'au priv\xE9 \u2014 arr\xEAte de me remonter des h\xF4pitaux publics."
 
 Examples that should NOT invoke this tool (sound similar, route elsewhere):
 - "Create a lens specialized in automobile."
 - "Add fintech to my Joinery lens."
 - "Show me my lenses."
+- "Exclude Groupe Solidum, we had an unpaid invoice with them."
 
 ## RENDER (quick)
 
@@ -5514,6 +5630,121 @@ clarification was raised, surface its question (route via ask_user_input_v0).
 
 Refine the kind of leads Leadbay surfaces, beyond firmographics. Free-text instruction (e.g. "focus on hospitals running their own IT"). Sets the org's \`user_prompt\`; if the new prompt produces ambiguous criteria, Leadbay raises a clarification question, which this composite polls for and surfaces. Admin-only on the backend (will return 403 for non-admins).
 
+**Read \`leadbay_get_qualification_questions\` first.** It returns the current
+targeting prompt alongside the questions and the buyer profile. Setting a
+prompt REPLACES the previous one \u2014 write the combined instruction, not just the
+new clause, or you silently drop rules the user set earlier.
+
+### A stated fit rule is a SETTING \u2014 read, decide, propose, then write
+
+**Never answer a stated rule from memory.** "C'est not\xE9", "already applied",
+"I'll keep that in mind", "the rule is now active" \u2014 every one of those is a
+claim about the user's ACCOUNT, and it is false unless a tool call made it
+true. The rule lives in the org's settings or it does not exist: your context
+window ends with this conversation, and the next session, the scheduled run and
+the user's colleague all read the account, not your memory. If you have not
+called a tool, do not say the rule is in place.
+
+When the user says what makes a lead good or bad \u2014 *"\xE9carte les soci\xE9t\xE9s
+liquid\xE9es"*, *"je ne veux pas d'associations"*, *"our best customers run their
+own maintenance crews"*, *"les leads ne sont pas pertinents"* \u2014 they are
+describing their account, not just this batch. Filter the batch and they say
+it again next week; their questions, buyer profile and targeting prompt never
+move.
+
+**1 \u2014 Read before you decide.** Call \`leadbay_get_qualification_questions\`
+first. It returns the question set PLUS the ideal buyer profile and the
+targeting prompt those questions sit beside. You cannot judge whether a rule is
+already covered without seeing them.
+
+**2 \u2014 Decide WHERE the rule belongs.** One rule, one destination:
+
+| What the user stated | Where it belongs |
+|---|---|
+| A sector, a headcount band, a territory | \`leadbay_adjust_audience\` / \`leadbay_new_lens\` filters \u2014 never a question |
+| A company trait a stranger could estimate from that company's own website or registry record \u2014 "runs its own maintenance crew", "operates a large vehicle fleet", "is legally active and not in liquidation" | a qualification question |
+| A qualitative orientation too broad for one yes/no \u2014 "we sell to the private sector, not the public one", "harden the exclusion on the business model" | the targeting prompt, \`leadbay_refine_prompt\` |
+| Named companies \u2014 "exclude Groupe Solidum, Dentego" | \`leadbay_dislike_lead\` / \`leadbay_set_lead_status\` on those leads. A question must NEVER name a company |
+| CRM state \u2014 "already contacted", "already in a campaign", "already excluded" | read it: \`leadbay_pull_followups\`, \`leadbay_list_campaigns\`. A question cannot observe your own history |
+| A delivery requirement \u2014 "email AND phone mandatory", "only score 54\u201395" | enrichment plus your own post-filter of the result. A question scores the COMPANY; it cannot see whether Leadbay holds a phone number for a contact |
+| An event or purchase trigger \u2014 "currently hiring an SDR", "just opened a site" | a qualification question or the targeting prompt. NEVER an \`example_lead\` description or a \`query\`: those match stable registry text, which never mentions events |
+
+**3 \u2014 Decide whether to change anything at all.** Touching a question
+re-scores every lead in the pipeline and draws on the org's quota, so a change
+that surfaces the same companies is a pure loss. Four reasons to write NOTHING
+and say why:
+
+1. **An existing question already covers the rule.** Quote that question back
+   and stop. **Never reword a question that already means the same thing** \u2014
+   even when the user asks you to "clarify" or "improve" the wording. A reword
+   is a removal plus an addition: it re-scores every lead, spends quota, and
+   surfaces exactly the same companies. Offer instead to find out whether any
+   question is testing the WRONG thing.
+2. **The audience filter already enforces it** \u2014 sector, headcount, territory.
+3. **An existing question already tests that dimension.** Two questions on one
+   dimension waste a slot and add no signal.
+4. **The question the user asked for is not decisive.** See step 4: say so,
+   offer the sharper version, and write only what they then choose. Adding a
+   question you know separates nothing is worse than adding none.
+
+**The ceiling is 5 questions.** Read the count before you answer an "add a
+question" request: at 5 the honest answer is not "sure, I'll add it". Say in
+that same turn that the set is full, list the five, and let the USER name which
+one goes. Never pre-pick the casualty.
+
+**4 \u2014 Write a DECISIVE question.** Check all six before you propose the text:
+
+1. **The estimative marker is literal and mandatory.** English questions start
+   \`Is the company likely to \u2026\`. French questions start
+   \`L'entreprise est-elle susceptible de/d' \u2026\`. There is no third form. The
+   scorer works from public text it cannot verify, so a verifiable question
+   scores almost everything as no.
+   - \u2705 \`Is the company likely to run its own in-house maintenance crew?\`
+   - \u274C \`Does the company run its own maintenance crew?\`
+   - \u274C \`Is the company a cold-storage plant?\` \u2014 no \`likely to\`
+   - \u2705 \`L'entreprise est-elle susceptible d'\xEAtre en liquidation judiciaire ?\`
+   - \u274C \`L'entreprise est-elle en liquidation ?\` \u2014 no \`susceptible\`
+2. **It tests the lead as a BUYER.** Before you write a question, ask: would
+   a company answering yes write a cheque to THIS user? A question that only
+   describes what the lead's own business does \u2014 "Is the company likely to
+   manufacture branded pharmaceuticals?" for a seller of advertising \u2014 is a
+   category test, not a buying test, and it scores the user's competitors and
+   suppliers as well as their prospects. Test the need the user's offering
+   meets: "Is the company likely to run consumer campaigns that need paid media
+   placement?"
+3. **Estimable from public material** \u2014 the company's website, its about page,
+   its job postings, its registry entry. Never its budget, its internal plans
+   or its future intentions. When the user's rule is un-observable ("has budget
+   for copywriting"), propose the observable proxy, and tell them you swapped
+   it and why.
+4. **One dimension each.** \`Is the company likely to operate a cold-storage
+   plant AND run its own maintenance crew?\` is two questions. Split it into
+   two, or pick the one that discriminates better.
+5. **Decisive.** It should split companies in general roughly 30/70 while the
+   user's own customers answer yes. A question nearly everyone answers yes to
+   \u2014 "has a website", "uses email", "is a company" \u2014 separates nobody. Do NOT
+   write it as asked: say it would add no signal, and offer the sharper version
+   you would write instead.
+6. **\u2264120 characters, in the user's language.**
+
+An org with **zero** questions scores every lead on firmographics alone. That
+is a finding worth stating, and the fix is a starter set of **3** questions on
+three different dimensions \u2014 not one. Propose all three at once.
+
+**5 \u2014 The change is the user's call, not yours.** This holds for the questions,
+the targeting prompt and the buyer profile alike. Show the exact text you
+propose and what it will change, then get an explicit yes before calling
+\`leadbay_set_qualification_questions\` or \`leadbay_refine_prompt\`. Ask through
+\`ask_user_input_v0\` when the host offers it. A removal or a swap additionally
+needs \`confirm:true\`. Do not write an org setting in the same turn the user
+first stated the rule \u2014 and once they have said yes, actually write it:
+describing the change is not making it.
+
+**Answer the ask as well.** A rule stated in passing \u2014 *"sors-moi les leads du
+jour, et arr\xEAte de me remonter des h\xF4pitaux publics"* \u2014 does not replace the
+ask. Deliver the leads first, then raise the setting.
+
+
 WHEN TO USE: when audience filters (leadbay_adjust_audience) aren't enough.
 
 WHEN NOT TO USE: to answer a pending clarification \u2014 that's leadbay_answer_clarification.
@@ -6565,7 +6796,35 @@ WHEN NOT TO USE: the user is just skipping ONE outreach attempt \u2014 that's a
 
 This tool MUTATES state. The caller (agent or human-in-the-loop) is responsible for confirming intent before invocation; the MCP server does not soft-prompt for confirmation. See \`annotations.destructiveHint\`.
 `;
-    leadbay_set_qualification_questions = `Modify the organization's **qualification questions** \u2014 the AI-agent questions Leadbay scores every lead against. Use when the user wants to add, remove, or rewrite their qualification questions \u2014 e.g. "add a question about whether they run install crews", "remove the flooring question", "replace my questions with these three".
+    leadbay_set_qualification_questions = `## WHEN TO USE
+
+Trigger phrases: "add / remove / replace a qualification question", "update my qualification so Leadbay looks for <trait>", "my best customers are <trait> \u2014 target those", "I don't want <kind of company> at all", "the leads aren't relevant, fix my criteria".
+
+Do NOT use for: "what are my qualification questions" \u2192 \`leadbay_get_qualification_questions\`; "narrow to <sector> / <headcount> / <territory>" \u2192 \`leadbay_adjust_audience\`; "a qualitative orientation one yes/no can't express" \u2192 \`leadbay_refine_prompt\`; "exclude <named company>" \u2192 \`leadbay_dislike_lead\`; "only leads that already have an email and a phone" \u2192 \`leadbay_enrich_titles\`.
+
+Prefer when: the user stated a durable company TRAIT a stranger could estimate from that company's public material, and get_qualification_questions shows nothing covering it. Read first, propose the text, write only on a yes.
+
+Examples that SHOULD invoke this tool:
+- "Our best customers are cold-storage plants that run their own maintenance crews \u2014 update my qualification for that."
+- "\xC9carte les soci\xE9t\xE9s en liquidation, je ne veux plus les voir."
+- "Remove the flooring question and add one about install crews."
+
+Examples that should NOT invoke this tool (sound similar, route elsewhere):
+- "What qualification questions does Leadbay use?"
+- "Add fintech to my Joinery lens."
+- "Exclude Groupe Solidum, we had an unpaid invoice with them."
+
+## RENDER (quick)
+
+Before writing: show the exact question text you propose, say what it
+changes, and ask for a yes (route via ask_user_input_v0). After writing:
+one confirmation line ("Added 1 question \u2014 you now score leads against 4
+questions.") then the resulting questions as a numbered list. On a
+non-changing preview, surface the \`hint\` and ask \u2014 never auto-confirm.
+
+---
+
+Modify the organization's **qualification questions** \u2014 the AI-agent questions Leadbay scores every lead against. Use when the user wants to add, remove, or rewrite them \u2014 e.g. "add a question about whether they run install crews", "remove the flooring question", "replace my questions with these three".
 
 The backend stores the list as a whole, so this tool reads the current questions and applies your change:
 
@@ -6577,11 +6836,142 @@ Leadbay allows **at most 5** qualification questions. If a change would exceed 5
 
 **Dropping any existing question is destructive** \u2014 it changes how every lead is scored. Any change that removes a current question requires \`confirm:true\` \u2014 including a same-count **swap** (remove one + add one) or a \`questions\` replacement that omits a current question, not only when the list gets shorter. Without \`confirm\`, the tool previews what would be removed and applies nothing. Pure additions never need confirm.
 
-Returns the resulting \`{qualification_questions, count, previous_count, changed}\`. Phrase questions as the yes/no scoring prompts Leadbay uses (e.g. "Is the company likely to \u2026?").
+Returns the resulting \`{qualification_questions, count, previous_count, changed}\`.
+
+### A stated fit rule is a SETTING \u2014 read, decide, propose, then write
+
+**Never answer a stated rule from memory.** "C'est not\xE9", "already applied",
+"I'll keep that in mind", "the rule is now active" \u2014 every one of those is a
+claim about the user's ACCOUNT, and it is false unless a tool call made it
+true. The rule lives in the org's settings or it does not exist: your context
+window ends with this conversation, and the next session, the scheduled run and
+the user's colleague all read the account, not your memory. If you have not
+called a tool, do not say the rule is in place.
+
+When the user says what makes a lead good or bad \u2014 *"\xE9carte les soci\xE9t\xE9s
+liquid\xE9es"*, *"je ne veux pas d'associations"*, *"our best customers run their
+own maintenance crews"*, *"les leads ne sont pas pertinents"* \u2014 they are
+describing their account, not just this batch. Filter the batch and they say
+it again next week; their questions, buyer profile and targeting prompt never
+move.
+
+**1 \u2014 Read before you decide.** Call \`leadbay_get_qualification_questions\`
+first. It returns the question set PLUS the ideal buyer profile and the
+targeting prompt those questions sit beside. You cannot judge whether a rule is
+already covered without seeing them.
+
+**2 \u2014 Decide WHERE the rule belongs.** One rule, one destination:
+
+| What the user stated | Where it belongs |
+|---|---|
+| A sector, a headcount band, a territory | \`leadbay_adjust_audience\` / \`leadbay_new_lens\` filters \u2014 never a question |
+| A company trait a stranger could estimate from that company's own website or registry record \u2014 "runs its own maintenance crew", "operates a large vehicle fleet", "is legally active and not in liquidation" | a qualification question |
+| A qualitative orientation too broad for one yes/no \u2014 "we sell to the private sector, not the public one", "harden the exclusion on the business model" | the targeting prompt, \`leadbay_refine_prompt\` |
+| Named companies \u2014 "exclude Groupe Solidum, Dentego" | \`leadbay_dislike_lead\` / \`leadbay_set_lead_status\` on those leads. A question must NEVER name a company |
+| CRM state \u2014 "already contacted", "already in a campaign", "already excluded" | read it: \`leadbay_pull_followups\`, \`leadbay_list_campaigns\`. A question cannot observe your own history |
+| A delivery requirement \u2014 "email AND phone mandatory", "only score 54\u201395" | enrichment plus your own post-filter of the result. A question scores the COMPANY; it cannot see whether Leadbay holds a phone number for a contact |
+| An event or purchase trigger \u2014 "currently hiring an SDR", "just opened a site" | a qualification question or the targeting prompt. NEVER an \`example_lead\` description or a \`query\`: those match stable registry text, which never mentions events |
+
+**3 \u2014 Decide whether to change anything at all.** Touching a question
+re-scores every lead in the pipeline and draws on the org's quota, so a change
+that surfaces the same companies is a pure loss. Four reasons to write NOTHING
+and say why:
+
+1. **An existing question already covers the rule.** Quote that question back
+   and stop. **Never reword a question that already means the same thing** \u2014
+   even when the user asks you to "clarify" or "improve" the wording. A reword
+   is a removal plus an addition: it re-scores every lead, spends quota, and
+   surfaces exactly the same companies. Offer instead to find out whether any
+   question is testing the WRONG thing.
+2. **The audience filter already enforces it** \u2014 sector, headcount, territory.
+3. **An existing question already tests that dimension.** Two questions on one
+   dimension waste a slot and add no signal.
+4. **The question the user asked for is not decisive.** See step 4: say so,
+   offer the sharper version, and write only what they then choose. Adding a
+   question you know separates nothing is worse than adding none.
+
+**The ceiling is 5 questions.** Read the count before you answer an "add a
+question" request: at 5 the honest answer is not "sure, I'll add it". Say in
+that same turn that the set is full, list the five, and let the USER name which
+one goes. Never pre-pick the casualty.
+
+**4 \u2014 Write a DECISIVE question.** Check all six before you propose the text:
+
+1. **The estimative marker is literal and mandatory.** English questions start
+   \`Is the company likely to \u2026\`. French questions start
+   \`L'entreprise est-elle susceptible de/d' \u2026\`. There is no third form. The
+   scorer works from public text it cannot verify, so a verifiable question
+   scores almost everything as no.
+   - \u2705 \`Is the company likely to run its own in-house maintenance crew?\`
+   - \u274C \`Does the company run its own maintenance crew?\`
+   - \u274C \`Is the company a cold-storage plant?\` \u2014 no \`likely to\`
+   - \u2705 \`L'entreprise est-elle susceptible d'\xEAtre en liquidation judiciaire ?\`
+   - \u274C \`L'entreprise est-elle en liquidation ?\` \u2014 no \`susceptible\`
+2. **It tests the lead as a BUYER.** Before you write a question, ask: would
+   a company answering yes write a cheque to THIS user? A question that only
+   describes what the lead's own business does \u2014 "Is the company likely to
+   manufacture branded pharmaceuticals?" for a seller of advertising \u2014 is a
+   category test, not a buying test, and it scores the user's competitors and
+   suppliers as well as their prospects. Test the need the user's offering
+   meets: "Is the company likely to run consumer campaigns that need paid media
+   placement?"
+3. **Estimable from public material** \u2014 the company's website, its about page,
+   its job postings, its registry entry. Never its budget, its internal plans
+   or its future intentions. When the user's rule is un-observable ("has budget
+   for copywriting"), propose the observable proxy, and tell them you swapped
+   it and why.
+4. **One dimension each.** \`Is the company likely to operate a cold-storage
+   plant AND run its own maintenance crew?\` is two questions. Split it into
+   two, or pick the one that discriminates better.
+5. **Decisive.** It should split companies in general roughly 30/70 while the
+   user's own customers answer yes. A question nearly everyone answers yes to
+   \u2014 "has a website", "uses email", "is a company" \u2014 separates nobody. Do NOT
+   write it as asked: say it would add no signal, and offer the sharper version
+   you would write instead.
+6. **\u2264120 characters, in the user's language.**
+
+An org with **zero** questions scores every lead on firmographics alone. That
+is a finding worth stating, and the fix is a starter set of **3** questions on
+three different dimensions \u2014 not one. Propose all three at once.
+
+**5 \u2014 The change is the user's call, not yours.** This holds for the questions,
+the targeting prompt and the buyer profile alike. Show the exact text you
+propose and what it will change, then get an explicit yes before calling
+\`leadbay_set_qualification_questions\` or \`leadbay_refine_prompt\`. Ask through
+\`ask_user_input_v0\` when the host offers it. A removal or a swap additionally
+needs \`confirm:true\`. Do not write an org setting in the same turn the user
+first stated the rule \u2014 and once they have said yes, actually write it:
+describing the change is not making it.
+
+**Answer the ask as well.** A rule stated in passing \u2014 *"sors-moi les leads du
+jour, et arr\xEAte de me remonter des h\xF4pitaux publics"* \u2014 does not replace the
+ask. Deliver the leads first, then raise the setting.
+
+
+WHEN TO USE: the user stated a durable company trait no existing question covers, and they have agreed to the exact text you proposed.
+
+WHEN NOT TO USE: to READ the questions (use leadbay_get_qualification_questions), to change a single lead's data, or for any rule the table above sends elsewhere. This is org-level \u2014 it affects scoring for ALL leads.
+
+## GATE \u2014 PREFER BUILT-IN HOST WIDGETS
+
+Modern chat hosts (Claude, ChatGPT) expose first-party widgets the agent can route into. These ALWAYS produce a better UX than markdown tables / inline prose for the data shapes they support \u2014 they're tappable on mobile, persistent across turns, and integrate with the host's quick-actions.
+
+**The Big Three** \u2014 when a tool result fits, route there:
+
+| Host widget | Use when | Field map (from Leadbay payload) |
+|---|---|---|
+| \`places_map_display_v0\` + \`places_search\` (Claude) | \u22652 leads with coords / \`location.city\`, geographic / "in person" / travel intent | **Two-step**: \`places_search\` each lead (query = company + full street address) \u2192 real \`place_id\`/coords, THEN render with \`places_map_display_v0\` (Itinerary mode for a tour). Skipping \`places_search\` \u2192 schematic scatter, not a street map. |
+| \`message_compose_v1\` (Claude) | You're about to draft outreach (email / message / call opener) | \`{kind: "email", summary_title, variants: [{label, body, subject}]}\` \u2014 2\u20133 variants, labels describe STRATEGY ("Push for alignment", "Reference the M&A signal"), not tone ("Friendly", "Formal") |
+| \`ask_user_input_v0\` (Claude chat / ChatGPT) **or** \`AskUserQuestion\` (Claude cowork / Claude Code) \u2014 whichever is in your tool set; their schemas differ, match the one you have | The tool's NEXT STEPS block has 2\u20134 mutually-exclusive next moves and the user hasn't already chosen | Per-tool schema in the server instructions + NEXT STEPS routing block. Max 3 questions. |
+
+ChatGPT exposes the same routing pattern via \`_meta.openai/outputTemplate\`. We don't ship any custom widgets ourselves \u2014 this gate is exclusively about routing into the host's first-party widgets when the data shape fits.
 
-WHEN TO USE: the user wants to change the org's qualification questions.
+**Rules:**
+- The widget IS the visual. Do NOT emit a markdown table or prose list of the same data alongside \u2014 that produces two competing UIs.
+- Pass identifiers (place_id, lead.id, contact_id) verbatim. Don't rewrite.
+- When the host doesn't expose the named widget, the agent falls back to the prose/table rendering the per-tool description already specifies. The directive is host-conditional; the fallback is automatic.
+- One short intro sentence in chat is enough \u2014 "Here are your 5 NYC follow-ups." Then route into the widget.
 
-WHEN NOT TO USE: to READ the questions (use leadbay_get_qualification_questions) or to change a single lead's data. This is org-level \u2014 it affects scoring for ALL leads.
 
 ### RENDERING
 
@@ -7175,7 +7565,7 @@ Do NOT use for: "show me today's leads / what's new today" \u2192 \`leadbay_pull
 Prefer when: the user describes a target profile or names a count of NEW companies \u2014 craft the example_lead per the seed rules below BEFORE calling; never pass the user's raw sentence as query.
 
 Examples that SHOULD invoke this tool:
-- "Find me 10 gyms around Dallas that would buy our flooring, with someone I can call."
+- "Find me 10 gyms around Dallas that would buy our flooring, with a contact."
 - "Get me 20 new US SaaS companies, 50-2000 employees, with the VP People's email."
 - "We're launching in Lyon \u2014 find 15 hotels that fit our ICP."
 
@@ -7186,11 +7576,10 @@ Examples that should NOT invoke this tool (sound similar, route elsewhere):
 
 ## RENDER (quick)
 
-3-col table of delivered leads in returned order: col 1 = 10-segment fit
-bar + linked company \xB7 location \xB7 size; col 2 = why-fits \u226420 words; col 3
-= contact + found channels. ALWAYS close with the honest funnel line
-(matched/examined/delivered/stop reason) \u2014 especially on 0
-delivered. Full algorithm below.
+3-col table of delivered leads in returned order: col 1 = 10-segment fit bar
++ linked company \xB7 location \xB7 size; col 2 = why-fits \u226420 words; col 3 =
+contact + found channels. ALWAYS close with the honest funnel line
+(matched/examined/delivered/stop reason), especially on 0 delivered.
 
 ---
 
@@ -7199,27 +7588,25 @@ company universe, applies hard filters, skips what the org already knows
 (\`novelty: org\`), optionally qualifies against the org's own intelligence
 (questions, tags, ideal buyer profile \u2014 frozen at submit), and optionally reveals
 contact channels. Polls up to \`wait_seconds\` (default 45); a longer job returns
-\`still_running\` + \`next_poll\` \u2014 hand off to \`leadbay_lead_job_status\`. Jobs run
+\`still_running\` + \`next_poll\` \u2014 hand to \`leadbay_lead_job_status\`. Jobs run
 \u226430 min, results kept 30 days.
 
 **Free vs usage quota \u2014 never use quota silently.** Default (\`qualify: false\`,
 \`channels: []\`) is FREE: company profile + fit score + cached research +
 contact identity. \`qualify: true\` (per candidate EXAMINED, capped by
 \`exploration_cap\`/\`max_cost\`) and \`channels\` (only when a value is found) draw
-on the org's usage quota; nothing is invoiced. Enforced in code: such a call is WITHHELD unless it
-carries \`confirm: true\` \u2014 nothing is submitted and you get
+on the org's usage quota; nothing is invoiced. Enforced in code: such a call is
+WITHHELD unless it carries \`confirm: true\` \u2014 nothing is submitted and you get
 \`mode: "needs_confirmation"\` with a real quote to show the user. Re-call with
 \`confirm: true\` on their go-ahead ("go ahead / get their emails" counts).
-\`confirm: false\` vetoes. Free needs no consent. **Preview free first** \u2014
-reshaping an off-profile seed is free, exploring it with \`qualify: true\` is
-not.
+\`confirm: false\` vetoes. **Preview free first** \u2014 reshaping an off-profile seed
+is free, exploring it with \`qualify: true\` is not.
 
 **Ad-hoc exclusions ("no chains") are enforced by NO tier** \u2014 \`filters\` has no
-exclusion key, and \`qualify\` scores against the org's FROZEN questions and IBP,
-which need not mention chains; the seed's inverse only shifts ranking.
-Violators can survive, use quota and be delivered \u2014 post-filter them yourself
-and say the tier didn't enforce it. Durable enforcement \u2192
-\`leadbay_refine_prompt\`.
+exclusion key, and \`qualify\` scores against the org's FROZEN questions and IBP.
+Violators survive, use quota and get delivered: post-filter them yourself and
+say the tier didn't enforce it. Durable enforcement \u2192
+\`leadbay_set_qualification_questions\` / \`leadbay_refine_prompt\`.
 
 ### Crafting the \`example_lead\` seed \u2014 the input that decides result quality
 
@@ -7239,13 +7626,13 @@ measured:
    model, what they sell or operate, who they serve, observable scale. Write
    it like the first paragraph of their About-Us page.
    - STRONG: "Operator of full-service fitness centers offering strength
-     areas, group classes and personal training to members across multiple
-     clubs."
-   - WEAK (generic): "A gym in Texas."
-   - WRONG (seller-side): "Supplier of durable modular flooring for gyms."
-4. **No event language.** "hiring", "expanding", "just raised" are not
-   filters \u2014 registry descriptions never contain them, so they dilute the
-   profile. Purchase triggers belong in the org's qualification questions.
+     areas, group classes and personal training to members across clubs."
+   - WEAK: "A gym in Texas." WRONG: "Supplier of gym flooring." (seller-side)
+4. **NO event language \u2014 in \`description\` or \`query\`.** "recrute", "hiring",
+   "expanding", "just raised" never appear in registry text, so they match
+   nothing. Send the trigger to \`leadbay_set_qualification_questions\` or
+   \`leadbay_refine_prompt\` and say so. "companies hiring a senior SDR" seeds as
+   "B2B software company operating an in-house outbound sales team."
 5. **No meta-markers.** Never "(example)", "(fictional)", "(placeholder)".
 6. **Hard constraints go in \`filters\`, not prose \u2014 exact keys:**
    \`sectors: string[]\`, \`locations: string[]\`, \`employees_min: number\`,
@@ -7255,24 +7642,22 @@ measured:
    never a country: this workspace's own is dropped, any other is refused.
 7. **Prefer \`example_lead\` over \`query\`.** Query matches topic *vocabulary*:
    "gyms that need durable flooring" surfaced flooring VENDORS, 0 delivered.
-   Use \`query\` only for signal an example can't express.
 8. **One seed per buyer archetype.** An ask spanning two segments ("gyms and
    warehouses") needs one search each with its own description and
-   \`request_id\` \u2014 a blended seed lands between the clusters and matches
-   neither.
+   \`request_id\` \u2014 a blended seed lands between the clusters, matching neither.
 
 
 **Parameter notes**
 - \`request_id\` (REQUIRED) is the retry contract: SAME value retrying the same
   ask (same live job, no double launch); NEW for a changed ask. Derive from ask
   + archetype + date: \`gyms-dallas-2026-07-28\`.
-- Never lower \`min_ai_score\` together with \`channels\` \u2014 that reveals emails for
-  leads the AI just scored as junk.
-- \`count\` \u2264 50; \u22643 active jobs/org; \u226410 submits/hour (429 + Retry-After \u2014
-  wait, don't hammer).
+- Never lower \`min_ai_score\` with \`channels\` \u2014 that reveals emails for leads
+  the AI just scored as junk.
+- \`count\` \u2264 50; \u22643 active jobs/org; \u226410 submits/hour (429 + Retry-After \u2014 wait,
+  don't hammer).
 
 **Read the result honestly** \u2014 \`funnel\` + \`explain.scope_notes\` tell the story;
-zero delivered gets a cause and a next move (rules in RENDERING).
+zero delivered gets a cause and a next move (RENDERING).
 
 ---
 
@@ -16852,12 +17237,188 @@ var init_research_lead_by_name_fuzzy = __esm({
   }
 });
 
+// ../core/dist/composite/set-qualification-questions.js
+function formWarnings(questions) {
+  const out = [];
+  for (const q of questions) {
+    const low = q.trim().toLowerCase();
+    if (!ESTIMATIVE_MARKERS.some((m) => low.startsWith(m))) {
+      out.push(`"${q}" is not in the estimative form. Leadbay scores from public text it cannot verify, so this will mark most leads no. Rewrite it to start "Is the company likely to ..." / "L'entreprise est-elle susceptible de ...".`);
+    }
+    if (q.length > 120) {
+      out.push(`"${q.slice(0, 60)}\u2026" is ${q.length} chars; keep a question under 120.`);
+    }
+  }
+  return out;
+}
+var MAX_QUESTIONS, ESTIMATIVE_MARKERS, setQualificationQuestions;
+var init_set_qualification_questions = __esm({
+  "../core/dist/composite/set-qualification-questions.js"() {
+    "use strict";
+    init_tool_descriptions_generated();
+    MAX_QUESTIONS = 5;
+    ESTIMATIVE_MARKERS = [
+      "is the company likely to",
+      "l'entreprise est-elle susceptible",
+      "l\u2019entreprise est-elle susceptible"
+    ];
+    setQualificationQuestions = {
+      name: "leadbay_set_qualification_questions",
+      annotations: {
+        title: "Modify the org's qualification questions",
+        readOnlyHint: false,
+        destructiveHint: true,
+        idempotentHint: false,
+        openWorldHint: true
+      },
+      description: leadbay_set_qualification_questions,
+      write: true,
+      inputSchema: {
+        type: "object",
+        properties: {
+          questions: {
+            type: "array",
+            items: { type: "string", maxLength: 255 },
+            description: `Full replacement list of qualification questions (replaces ALL current questions). Mutually exclusive with add/remove. A question Leadbay can score has ALL of: the estimative marker \u2014 it starts "Is the company likely to " in English or "L'entreprise est-elle susceptible de/d' " in French (never "Does the company ..." or a bare "L'entreprise est-elle <X> ?", which the scorer cannot verify and marks no); ONE dimension, not two joined by AND; something estimable from the company's public material, never its budget or its internal plans; and enough bite to split companies roughly 30/70 \u2014 a question nearly everyone answers yes to ("has a website") adds no signal, so say that and propose a sharper one rather than writing it. Max 120 chars, in the user's language. Never name a specific company in a question. Never re-send an existing question with reworded text that means the same thing \u2014 a reword is a delete plus an add, it re-scores every lead in the pipeline against the org's quota, and it surfaces exactly the same companies.`
+          },
+          add: {
+            type: "array",
+            items: { type: "string", maxLength: 255 },
+            description: `Questions to append to the current list (deduped). Mutually exclusive with \`questions\`. A question Leadbay can score has ALL of: the estimative marker \u2014 it starts "Is the company likely to " in English or "L'entreprise est-elle susceptible de/d' " in French (never "Does the company ..." or a bare "L'entreprise est-elle <X> ?", which the scorer cannot verify and marks no); ONE dimension, not two joined by AND; something estimable from the company's public material, never its budget or its internal plans; and enough bite to split companies roughly 30/70 \u2014 a question nearly everyone answers yes to ("has a website") adds no signal, so say that and propose a sharper one rather than writing it. Max 120 chars, in the user's language. Never name a specific company in a question. Read leadbay_get_qualification_questions first: skip anything an existing question already tests, and anything the lens already filters by sector, headcount or territory.`
+          },
+          remove: {
+            type: "array",
+            items: { type: "string" },
+            description: "Exact question strings to remove from the current list. Mutually exclusive with `questions`. A removal requires confirm:true."
+          },
+          confirm: {
+            type: "boolean",
+            description: "Required whenever the change DROPS ANY existing question \u2014 including a same-count swap or a `questions` replacement that omits a current question, not only when the list gets shorter (removing a question changes how every lead is scored). Without it, such a change is previewed and not applied. Pure additions never need confirm."
+          }
+        },
+        additionalProperties: false
+      },
+      outputSchema: {
+        type: "object",
+        properties: {
+          qualification_questions: {
+            type: "array",
+            description: "The questions AFTER the change. Each: {question}.",
+            items: { type: "object" }
+          },
+          count: { type: "number" },
+          previous_count: { type: "number" },
+          changed: {
+            type: "boolean",
+            description: "True when the list was actually written; false on a no-op or an unconfirmed shrink."
+          },
+          region: { type: "string" },
+          form_warnings: {
+            type: "array",
+            items: { type: "string" },
+            description: "Present when a written question will score poorly \u2014 not in the estimative 'Is the company likely to ...' form, or over 120 chars. The change WAS applied; tell the user and offer the rewrite."
+          },
+          hint: {
+            type: "string",
+            description: "Operator note \u2014 confirm prompt on a shrink, or a no-op explanation."
+          },
+          _meta: { type: "object" }
+        },
+        required: ["qualification_questions", "count", "changed"]
+      },
+      execute: async (client, params, ctx) => {
+        const hasSet = Array.isArray(params.questions);
+        const hasAdd = Array.isArray(params.add) && params.add.length > 0;
+        const hasRemove = Array.isArray(params.remove) && params.remove.length > 0;
+        if (hasSet && (hasAdd || hasRemove)) {
+          throw client.makeError("QUALIFICATION_QUESTIONS_BAD_ARGS", "`questions` (full replace) is mutually exclusive with add/remove", "Pass EITHER `questions` (the full new list) OR `add`/`remove`, not both.", "POST /organizations/{orgId}");
+        }
+        if (!hasSet && !hasAdd && !hasRemove) {
+          throw client.makeError("QUALIFICATION_QUESTIONS_NO_CHANGE", "nothing to change \u2014 pass `questions`, `add`, or `remove`", "Provide a full `questions` list, or `add`/`remove` entries.", "POST /organizations/{orgId}");
+        }
+        const orgId = await client.resolveOrgId();
+        const current = await client.request("GET", `/organizations/${orgId}/ai_agent_questions`);
+        const currentQs = (current ?? []).map((q) => q.question);
+        const norm = (s) => s.trim();
+        let next;
+        if (hasSet) {
+          next = params.questions.map(norm).filter((s) => s.length > 0);
+        } else {
+          next = [...currentQs];
+          if (hasRemove) {
+            const drop = new Set(params.remove.map(norm));
+            next = next.filter((q) => !drop.has(norm(q)));
+          }
+          if (hasAdd) {
+            const seen2 = new Set(next.map(norm));
+            for (const q of params.add.map(norm)) {
+              if (q.length > 0 && !seen2.has(q)) {
+                next.push(q);
+                seen2.add(q);
+              }
+            }
+          }
+        }
+        const seen = /* @__PURE__ */ new Set();
+        next = next.filter((q) => {
+          const k = norm(q);
+          if (seen.has(k))
+            return false;
+          seen.add(k);
+          return true;
+        });
+        if (next.length > MAX_QUESTIONS) {
+          throw client.makeError("QUALIFICATION_QUESTIONS_LIMIT", `too many questions: ${next.length} (max ${MAX_QUESTIONS})`, `Leadbay allows at most ${MAX_QUESTIONS} qualification questions. Remove some first (pass fewer in \`questions\`, or use \`remove\`), then add.`, "POST /organizations/{orgId}");
+        }
+        const previousCount = currentQs.length;
+        const noChange = next.length === currentQs.length && next.every((q, i) => norm(q) === norm(currentQs[i] ?? ""));
+        if (noChange) {
+          return {
+            qualification_questions: currentQs.map((q) => ({ question: q })),
+            count: currentQs.length,
+            previous_count: previousCount,
+            changed: false,
+            region: client.region,
+            hint: "No change \u2014 the resulting list is identical to the current one. Pass different `add`/`remove` entries, or call leadbay_get_qualification_questions to review the current questions."
+          };
+        }
+        const removed = currentQs.filter((q) => !next.some((n) => norm(n) === norm(q)));
+        if (removed.length > 0 && params.confirm !== true) {
+          return {
+            qualification_questions: currentQs.map((q) => ({ question: q })),
+            count: currentQs.length,
+            previous_count: previousCount,
+            changed: false,
+            region: client.region,
+            hint: `Re-call with confirm:true to apply. This would remove ${removed.length} question(s): ${removed.map((q) => `"${q}"`).join(", ")}. Removing a question changes how every lead is scored.`
+          };
+        }
+        await client.requestVoid("POST", `/organizations/${orgId}`, {
+          ai_agent_lead_questions: next
+        });
+        client.invalidateTasteProfile();
+        const written = hasSet ? next : (params.add ?? []).map(norm).filter((q) => next.includes(q));
+        const warnings = formWarnings(written);
+        return {
+          qualification_questions: next.map((q) => ({ question: q })),
+          count: next.length,
+          previous_count: previousCount,
+          changed: true,
+          region: client.region,
+          ...warnings.length > 0 ? { form_warnings: warnings } : {}
+        };
+      }
+    };
+  }
+});
+
 // ../core/dist/composite/get-qualification-questions.js
 var getQualificationQuestions;
 var init_get_qualification_questions = __esm({
   "../core/dist/composite/get-qualification-questions.js"() {
     "use strict";
     init_tool_descriptions_generated();
+    init_set_qualification_questions();
     getQualificationQuestions = {
       name: "leadbay_get_qualification_questions",
       annotations: {
@@ -16885,6 +17446,13 @@ var init_get_qualification_questions = __esm({
             type: "number",
             description: "Number of qualification questions configured."
           },
+          ideal_buyer_profile: {
+            description: "The org's Ideal Buyer Profile {summary, key_characteristics, anti_patterns}, or null when none is configured. The questions score against this profile \u2014 read it before judging whether a user's stated rule is already covered."
+          },
+          targeting_prompt: {
+            type: ["string", "null"],
+            description: "The org's free-text targeting prompt (user_prompt) the AI agent follows, or null when unset. Qualitative rules live here rather than in a question; change it with leadbay_refine_prompt."
+          },
           is_admin: {
             type: "boolean",
             description: "Whether the current bearer-token holder is an org admin. Admins can modify the questions via leadbay_set_qualification_questions."
@@ -16903,11 +17471,21 @@ var init_get_qualification_questions = __esm({
         const isAdmin = me?.admin ?? false;
         const orgId = me?.organization?.id ?? await client.resolveOrgId();
         const questions = await client.request("GET", `/organizations/${orgId}/ai_agent_questions`) ?? [];
+        const [ibpResult, promptResult] = await Promise.allSettled([
+          client.request("GET", `/organizations/${orgId}/ideal_buyer_profile`),
+          client.request("GET", `/organizations/${orgId}/user_prompt`)
+        ]);
+        const ibp = ibpResult.status === "fulfilled" ? ibpResult.value ?? null : null;
+        const targetingPrompt = promptResult.status === "fulfilled" ? promptResult.value?.prompt ?? null : null;
         let hint;
-        if (questions.length === 0) {
-          hint = "No qualification questions configured yet. Use leadbay_set_qualification_questions to add some, or leadbay_refine_prompt to shape the AI agent.";
+        if (questions.length >= MAX_QUESTIONS && isAdmin) {
+          hint = `${questions.length} of ${MAX_QUESTIONS} question slots are used \u2014 the set is FULL. An addition is a SWAP: tell the user the set is full, list these ${questions.length} and let THEM choose which one goes, then call leadbay_set_qualification_questions with confirm:true. Never pre-pick the one to drop.`;
+        } else if (questions.length >= MAX_QUESTIONS) {
+          hint = `${questions.length} of ${MAX_QUESTIONS} question slots are used \u2014 the set is FULL. Changing it means dropping one, and that is an org-admin action. Tell the user which question they would need an admin to swap out.`;
+        } else if (questions.length === 0) {
+          hint = `No qualification questions configured \u2014 every lead is scored on firmographics alone. Propose a starter set of exactly 3 questions in ONE leadbay_set_qualification_questions call \u2014 one question is too thin to separate anything, each on a DIFFERENT buying dimension, each starting "Is the company likely to ..." / "L'entreprise est-elle susceptible de ...", and none restating a sector or size the lens already filters on. Get the user's yes first.`;
         } else if (isAdmin) {
-          hint = "You're an org admin \u2014 use leadbay_set_qualification_questions to add, remove, or replace these questions.";
+          hint = `You're an org admin \u2014 use leadbay_set_qualification_questions to add, remove, or replace these questions. ${MAX_QUESTIONS - questions.length} of ${MAX_QUESTIONS} slots are still free.`;
         }
         return {
           qualification_questions: questions.map((q) => ({
@@ -16916,6 +17494,12 @@ var init_get_qualification_questions = __esm({
             lang: q.lang
           })),
           count: questions.length,
+          ideal_buyer_profile: ibp ? {
+            summary: ibp.summary,
+            key_characteristics: ibp.key_characteristics,
+            anti_patterns: ibp.anti_patterns
+          } : null,
+          targeting_prompt: targetingPrompt,
           is_admin: isAdmin,
           region: client.region,
           ...hint ? { hint } : {}
@@ -17149,155 +17733,6 @@ var init_getting_started = __esm({
   }
 });
 
-// ../core/dist/composite/set-qualification-questions.js
-var setQualificationQuestions;
-var init_set_qualification_questions = __esm({
-  "../core/dist/composite/set-qualification-questions.js"() {
-    "use strict";
-    init_tool_descriptions_generated();
-    setQualificationQuestions = {
-      name: "leadbay_set_qualification_questions",
-      annotations: {
-        title: "Modify the org's qualification questions",
-        readOnlyHint: false,
-        destructiveHint: true,
-        idempotentHint: false,
-        openWorldHint: true
-      },
-      description: leadbay_set_qualification_questions,
-      write: true,
-      inputSchema: {
-        type: "object",
-        properties: {
-          questions: {
-            type: "array",
-            items: { type: "string", maxLength: 255 },
-            description: "Full replacement list of qualification questions (replaces ALL current questions). Mutually exclusive with add/remove."
-          },
-          add: {
-            type: "array",
-            items: { type: "string", maxLength: 255 },
-            description: "Questions to append to the current list (deduped). Mutually exclusive with `questions`."
-          },
-          remove: {
-            type: "array",
-            items: { type: "string" },
-            description: "Exact question strings to remove from the current list. Mutually exclusive with `questions`. A removal requires confirm:true."
-          },
-          confirm: {
-            type: "boolean",
-            description: "Required whenever the change DROPS ANY existing question \u2014 including a same-count swap or a `questions` replacement that omits a current question, not only when the list gets shorter (removing a question changes how every lead is scored). Without it, such a change is previewed and not applied. Pure additions never need confirm."
-          }
-        },
-        additionalProperties: false
-      },
-      outputSchema: {
-        type: "object",
-        properties: {
-          qualification_questions: {
-            type: "array",
-            description: "The questions AFTER the change. Each: {question}.",
-            items: { type: "object" }
-          },
-          count: { type: "number" },
-          previous_count: { type: "number" },
-          changed: {
-            type: "boolean",
-            description: "True when the list was actually written; false on a no-op or an unconfirmed shrink."
-          },
-          region: { type: "string" },
-          hint: {
-            type: "string",
-            description: "Operator note \u2014 confirm prompt on a shrink, or a no-op explanation."
-          },
-          _meta: { type: "object" }
-        },
-        required: ["qualification_questions", "count", "changed"]
-      },
-      execute: async (client, params, ctx) => {
-        const hasSet = Array.isArray(params.questions);
-        const hasAdd = Array.isArray(params.add) && params.add.length > 0;
-        const hasRemove = Array.isArray(params.remove) && params.remove.length > 0;
-        if (hasSet && (hasAdd || hasRemove)) {
-          throw client.makeError("QUALIFICATION_QUESTIONS_BAD_ARGS", "`questions` (full replace) is mutually exclusive with add/remove", "Pass EITHER `questions` (the full new list) OR `add`/`remove`, not both.", "POST /organizations/{orgId}");
-        }
-        if (!hasSet && !hasAdd && !hasRemove) {
-          throw client.makeError("QUALIFICATION_QUESTIONS_NO_CHANGE", "nothing to change \u2014 pass `questions`, `add`, or `remove`", "Provide a full `questions` list, or `add`/`remove` entries.", "POST /organizations/{orgId}");
-        }
-        const orgId = await client.resolveOrgId();
-        const current = await client.request("GET", `/organizations/${orgId}/ai_agent_questions`);
-        const currentQs = (current ?? []).map((q) => q.question);
-        const norm = (s) => s.trim();
-        let next;
-        if (hasSet) {
-          next = params.questions.map(norm).filter((s) => s.length > 0);
-        } else {
-          next = [...currentQs];
-          if (hasRemove) {
-            const drop = new Set(params.remove.map(norm));
-            next = next.filter((q) => !drop.has(norm(q)));
-          }
-          if (hasAdd) {
-            const seen2 = new Set(next.map(norm));
-            for (const q of params.add.map(norm)) {
-              if (q.length > 0 && !seen2.has(q)) {
-                next.push(q);
-                seen2.add(q);
-              }
-            }
-          }
-        }
-        const seen = /* @__PURE__ */ new Set();
-        next = next.filter((q) => {
-          const k = norm(q);
-          if (seen.has(k))
-            return false;
-          seen.add(k);
-          return true;
-        });
-        const MAX_QUESTIONS = 5;
-        if (next.length > MAX_QUESTIONS) {
-          throw client.makeError("QUALIFICATION_QUESTIONS_LIMIT", `too many questions: ${next.length} (max ${MAX_QUESTIONS})`, `Leadbay allows at most ${MAX_QUESTIONS} qualification questions. Remove some first (pass fewer in \`questions\`, or use \`remove\`), then add.`, "POST /organizations/{orgId}");
-        }
-        const previousCount = currentQs.length;
-        const noChange = next.length === currentQs.length && next.every((q, i) => norm(q) === norm(currentQs[i] ?? ""));
-        if (noChange) {
-          return {
-            qualification_questions: currentQs.map((q) => ({ question: q })),
-            count: currentQs.length,
-            previous_count: previousCount,
-            changed: false,
-            region: client.region,
-            hint: "No change \u2014 the resulting list is identical to the current one. Pass different `add`/`remove` entries, or call leadbay_get_qualification_questions to review the current questions."
-          };
-        }
-        const removed = currentQs.filter((q) => !next.some((n) => norm(n) === norm(q)));
-        if (removed.length > 0 && params.confirm !== true) {
-          return {
-            qualification_questions: currentQs.map((q) => ({ question: q })),
-            count: currentQs.length,
-            previous_count: previousCount,
-            changed: false,
-            region: client.region,
-            hint: `Re-call with confirm:true to apply. This would remove ${removed.length} question(s): ${removed.map((q) => `"${q}"`).join(", ")}. Removing a question changes how every lead is scored.`
-          };
-        }
-        await client.requestVoid("POST", `/organizations/${orgId}`, {
-          ai_agent_lead_questions: next
-        });
-        client.invalidateTasteProfile();
-        return {
-          qualification_questions: next.map((q) => ({ question: q })),
-          count: next.length,
-          previous_count: previousCount,
-          changed: true,
-          region: client.region
-        };
-      }
-    };
-  }
-});
-
 // ../core/dist/composite/get-lead-custom-fields.js
 var getLeadCustomFields;
 var init_get_lead_custom_fields = __esm({
@@ -22409,11 +22844,11 @@ var init_find_new_leads = __esm({
         properties: {
           query: {
             type: "string",
-            description: "Natural-language ICP ask. Matches topic VOCABULARY \u2014 can surface vendors of a product as easily as buyers of it. Prefer example_lead; use query only when the user's wording carries signal an example can't."
+            description: "Natural-language ICP ask. Matches topic VOCABULARY \u2014 can surface vendors of a product as easily as buyers of it. Prefer example_lead. NO event language ('hiring', 'recrute', 'expanding', 'just raised'): registry text never says what a company is DOING, so an event word matches nothing here. Send the trigger to leadbay_set_qualification_questions or leadbay_refine_prompt instead, and tell the user that is where it went."
           },
           example_lead: {
             type: "object",
-            description: "A FICTIONAL typical ideal customer used as a look-alike seed \u2014 the highest-leverage input. Put everything in `description` (registry 'About Us' style, what the company IS); leave `name` unset (a distinctive invented name pulls matches toward name-lookalikes).",
+            description: "A FICTIONAL typical ideal customer used as a look-alike seed \u2014 the highest-leverage input. Put everything in `description` (registry 'About Us' style, what the company IS, never what it is DOING and never what the seller sells); leave `name` unset (a distinctive invented name pulls matches toward name-lookalikes).",
             properties: {
               name: { type: "string" },
               description: { type: "string" },
@@ -29230,6 +29665,7 @@ var FRICTION = `Problem reports: when the user asks you to report a Leadbay prob
 var MENTAL_MODEL = `How Leadbay works (mental model): Leadbay is a sales inbox, not a queryable database. Each day the user logs back in, a fresh batch of leads is delivered. Batch size is paced by how many leads the user has actually acted on recently \u2014 some workflows produce a big stream of smaller prospects, others a narrow stream of bigger ones. Pulling more won't produce more; the user acting on leads (outreach, skips, saves) does.`;
 var QUOTA_REFRESH = `Show the refreshed quota AFTER a quota-using action only when it matters: the user asks where they now stand, the action stopped on an exhausted window, or a top-up the user confirmed landed. Otherwise report the result and say nothing about quota. When you do show it, wait for genuine completion \u2014 leadbay_bulk_enrich_status reports the job done (all_done, OR a plateau you've decided is terminal: overall_progress.done stopped climbing across spaced polls, so some contacts are unresolvable and all_done stays false) \u2014 then call leadbay_account_status once and render the per-window %/$ gauge (Daily/Weekly/Monthly) it returns. leadbay_enrich_contacts only LAUNCHES an async reveal (it returns a hint to check back in ~60s), so do NOT refresh quota right after it \u2014 the usage isn't reflected yet. For that single-contact flow, refresh only once a re-read of the lead's contacts (leadbay_research_lead_by_id; leadbay_get_contacts where exposed) shows the REQUESTED channel actually landed \u2014 the requested email and/or phone_number present \u2014 NOT enrichment.done alone (that flag is already true for a contact enriched on the other channel earlier, so a phone reveal could otherwise trigger the refresh before phone_number arrives). This is the canonical quota surface; do NOT hand-roll a 'credits' line in its place. Skip it when account_status reports unlimited_credits, quota_error, or a null quota (nothing to show), or when billing is genuinely unavailable. Do it ONCE per completed action \u2014 not after every poll while work is still in progress.`;
 var QUOTA_TOPUP = `Quota & top-ups: when a tool returns QUOTA_EXCEEDED / 429, the user has TWO options \u2014 wait for the window reset (daily / weekly / monthly resets shown in leadbay_account_status), OR top up AI credits (top-ups clear the throttle IMMEDIATELY \u2014 they are not subject to the same window). Always offer BOTH options; default-recommending 'wait until tomorrow' is wrong when a 30-second top-up unblocks the same call. If the host exposes leadbay_create_topup_link, OFFER it on every quota wall: 'Want me to generate a top-up link?' \u2014 when the user says yes, call leadbay_create_topup_link and surface the returned Stripe URL as a clickable link for the user to open in their browser. (Sibling leadbay_open_billing_portal is for ongoing subscription changes, not one-shot top-ups.) AFTER the user has topped up: do NOT keep refusing operations. A top-up invalidates every prior 429 and every stale 'you're at your quota' snapshot. The moment the user signals they topped up / bought credits / added credits \u2014 even WITHOUT re-calling account_status \u2014 treat the previous quota state as void and RETRY the originally failed call. (Best practice: re-call leadbay_account_status to surface the fresh state to the user, then retry; but the retry itself does NOT require a successful account_status check first. If the retry hits the wall again, THEN you have evidence the top-up didn't land; only then re-offer top-up / wait.) The agent's job after a top-up is to RESUME the workflow the user was on, not gate-keep.`;
+var STATED_RULES = `Stated fit rules live in the account, not in your memory: when the user tells you what makes a lead good or bad ("\xE9carte les soci\xE9t\xE9s liquid\xE9es", "I don't want associations", "our best customers run their own maintenance crews", "the leads aren't relevant"), that is a change to their Leadbay settings. NEVER answer it with "c'est not\xE9", "already saved", "the rule is active" or "I'll keep that in mind" \u2014 those are claims about their account that are false unless a tool call made them true, and the next session, the scheduled run and their colleague all read the account, not your context. Call leadbay_get_qualification_questions first \u2014 it returns the questions, the ideal buyer profile and the targeting prompt together \u2014 then decide where the rule belongs, decide whether anything needs to change at all, propose the exact text, and write only on an explicit yes.`;
 var TRANSIENT_401 = `Transient 401s (DO NOT narrate as an auth problem): Leadbay bearer tokens do NOT expire on a timer, and the client already auto-retried this call once before surfacing it. So a lone AUTH_EXPIRED / 401 from a tool is almost always a brief Leadbay-side hiccup, NOT a sign the user must sign in again. When you see ONE, just silently retry the operation once more and carry on \u2014 do NOT tell the user to log in again, reconnect the connector, reauthorize, or 're-load Leadbay', and do NOT surface the bare '401' to them at all. Only if calls keep failing across several attempts should you mention it \u2014 and then frame it as a possible Leadbay-side issue or a possible logout (you cannot tell which from here), and offer to report it to the team. Never turn a one-off 401 into a 'your connection needs re-authenticating' message; that is the wrong read on a connection that is actually working.`;
 var TRIGGERED_BY = `Trigger provenance (MANDATORY): every Leadbay composite-tool call MUST carry a non-empty \`_triggered_by\` argument \u2014 the verbatim slice of the user's most recent message that this call is acting upon. Quote literally; do NOT paraphrase, summarize, or substitute a one-word label like "leads" or "request" (those are rejected). If you are acting WITHOUT a fresh user message (a memory recall, a scheduled run, a self-initiated retry), pass the actual instruction you are acting on \u2014 the recalled directive, the schedule's intent, or the original request being retried \u2014 so the value is always a real, auditable trace. Strip any secrets the user pasted (API keys, passwords, card numbers, full home addresses) \u2014 replace with [REDACTED]. A composite call missing or blanking this field is rejected with LAST_PROMPT_REQUIRED; just re-call with the field set. This is a protocol requirement on EVERY composite invocation (not just the first), independent of any telemetry setting.`;
 var VERIFICATION = `After every email, call, message, or meeting with a lead's contact, you MUST call leadbay_report_outreach with verification={source, ref} (gmail_message_id from the Gmail send, calendar_event_id from a booking, or user_confirmed='<the user's literal confirmation>'). Skipping or fabricating verification poisons the human team's pipeline.`;
@@ -29398,6 +29834,9 @@ function buildServerInstructions(exposed) {
   }
   parts.push(TRIGGERED_BY);
   parts.push(MENTAL_MODEL);
+  if (has("leadbay_get_qualification_questions")) {
+    parts.push(STATED_RULES);
+  }
   if (has("leadbay_create_topup_link")) {
     parts.push(QUOTA_TOPUP);
   }
@@ -31596,7 +32035,7 @@ var OAUTH_BASE_URLS = {
     fr: "https://staging.api.leadbay.app"
   }
 };
-var VERSION = "0.39.4";
+var VERSION = "0.39.5";
 var HELP = `
 leadbay-mcp ${VERSION} \u2014 Leadbay Model Context Protocol server