@leadbay/mcp 0.18.0 → 0.18.1

package/CHANGELOG.md

@@ -1,5 +1,10 @@
 # Changelog — @leadbay/mcp
 
+## 0.18.1 — 2026-06-09
+
+- **Quota rendering fix**: `leadbay_account_status` now renders the per-resource Daily / Weekly / Monthly **usage** table the API actually returns, instead of collapsing to "quota: null / no limits". Root cause: `quota_status` returns `count` (amount **used**) per resource per window with no cap field and a possibly-`null` `plan`; the old render hint tried to draw `used / cap` and gave up when there was no cap. The hint is now usage-only and explicitly warns that a missing cap / `null` plan is **not** "unlimited" or "no quota". `get-quota.ts` `outputSchema` corrected to the real `org` / `user.resources[]` shape (`{resource_type, count, window_type, resets_at}`, `count` = used), and a failed quota fetch is now distinguished from an empty quota.
+- **Enrichment credit spend**: `leadbay_enrich_titles` surfaces the credit balance before and the actual spend after a run, reported discreetly rather than as a callout. Dropped the per-run "credits used" figure that conflated prior enrichments.
+
 ## 0.18.0 — 2026-06-08
 
 Backend long-task notifications are now consumed by the MCP. When the user (or agent) initiates a bulk operation — contact enrichment, lead qualification, CSV / CRM import — the MCP listens to the backend WebSocket for the completion event and surfaces it on the agent's next tool call so prior outputs that depended on the now-finished data can be revised.

package/dist/bin.js

@@ -5103,6 +5103,7 @@ var init_composite_file_names = __esm({
   "../core/dist/composite/_composite-file-names.js"() {
     "use strict";
     COMPOSITE_FILE_TOOL_NAMES = /* @__PURE__ */ new Set([
+      "leadbay_account_history",
       "leadbay_account_status",
       "leadbay_add_leads_to_campaign",
       "leadbay_adjust_audience",
@@ -5438,10 +5439,156 @@ var init_notifications = __esm({
 });
 
 // ../core/dist/tool-descriptions.generated.js
-var leadbay_account_status, leadbay_acknowledge_notification, leadbay_add_leads_to_campaign, leadbay_add_note, leadbay_adjust_audience, leadbay_agent_memory_capture, leadbay_agent_memory_recall, leadbay_agent_memory_review, leadbay_answer_clarification, leadbay_bulk_enrich_status, leadbay_bulk_qualify_leads, leadbay_campaign_call_sheet, leadbay_campaign_progression, leadbay_clear_selection, leadbay_clear_user_prompt, leadbay_create_campaign, leadbay_create_custom_field, leadbay_create_lens, leadbay_create_lens_draft, leadbay_create_topup_link, leadbay_deselect_leads, leadbay_discover_leads, leadbay_dislike_lead, leadbay_dismiss_clarification, leadbay_enrich_contacts, leadbay_enrich_titles, leadbay_extend_lens, leadbay_followups_map, leadbay_get_clarification, leadbay_get_contacts, leadbay_get_enrichment_job_titles, leadbay_get_epilogue_responses, leadbay_get_lead_activities, leadbay_get_lead_notes, leadbay_get_lead_profile, leadbay_get_lens_filter, leadbay_get_lens_scoring, leadbay_get_prospecting_actions, leadbay_get_quota, leadbay_get_selection_ids, leadbay_get_taste_profile, leadbay_get_user_prompt, leadbay_get_web_fetch, leadbay_import_and_qualify, leadbay_import_leads, leadbay_import_status, leadbay_launch_bulk_enrichment, leadbay_like_lead, leadbay_list_campaigns, leadbay_list_lenses, leadbay_list_locations, leadbay_list_mappable_fields, leadbay_list_sectors, leadbay_login, leadbay_my_lenses, leadbay_new_lens, leadbay_open_billing_portal, leadbay_pick_clarification, leadbay_prepare_outreach, leadbay_preview_bulk_enrichment, leadbay_promote_lens, leadbay_pull_followups, leadbay_pull_leads, leadbay_qualify_lead, leadbay_qualify_status, leadbay_recall_ordered_titles, leadbay_refine_prompt, leadbay_remove_epilogue, leadbay_remove_leads_from_campaign, leadbay_remove_pushback, leadbay_report_friction, leadbay_report_outreach, leadbay_research_lead_by_id, leadbay_research_lead_by_name_fuzzy, leadbay_resolve_import_rows, leadbay_seed_candidates, leadbay_select_leads, leadbay_set_active_lens, leadbay_set_epilogue_status, leadbay_set_pushback, leadbay_set_user_prompt, leadbay_tour_plan, leadbay_update_lens, leadbay_update_lens_filter;
+var leadbay_account_history, leadbay_account_status, leadbay_acknowledge_notification, leadbay_add_leads_to_campaign, leadbay_add_note, leadbay_adjust_audience, leadbay_agent_memory_capture, leadbay_agent_memory_recall, leadbay_agent_memory_review, leadbay_answer_clarification, leadbay_bulk_enrich_status, leadbay_bulk_qualify_leads, leadbay_campaign_call_sheet, leadbay_campaign_progression, leadbay_clear_selection, leadbay_clear_user_prompt, leadbay_create_campaign, leadbay_create_custom_field, leadbay_create_lens, leadbay_create_lens_draft, leadbay_create_topup_link, leadbay_deselect_leads, leadbay_discover_leads, leadbay_dislike_lead, leadbay_dismiss_clarification, leadbay_enrich_contacts, leadbay_enrich_titles, leadbay_extend_lens, leadbay_followups_map, leadbay_get_clarification, leadbay_get_contacts, leadbay_get_enrichment_job_titles, leadbay_get_epilogue_responses, leadbay_get_lead_activities, leadbay_get_lead_notes, leadbay_get_lead_profile, leadbay_get_lens_filter, leadbay_get_lens_scoring, leadbay_get_prospecting_actions, leadbay_get_quota, leadbay_get_selection_ids, leadbay_get_taste_profile, leadbay_get_user_prompt, leadbay_get_web_fetch, leadbay_import_and_qualify, leadbay_import_leads, leadbay_import_status, leadbay_launch_bulk_enrichment, leadbay_like_lead, leadbay_list_campaigns, leadbay_list_lenses, leadbay_list_locations, leadbay_list_mappable_fields, leadbay_list_sectors, leadbay_login, leadbay_my_lenses, leadbay_new_lens, leadbay_open_billing_portal, leadbay_pick_clarification, leadbay_prepare_outreach, leadbay_preview_bulk_enrichment, leadbay_promote_lens, leadbay_pull_followups, leadbay_pull_leads, leadbay_qualify_lead, leadbay_qualify_status, leadbay_recall_ordered_titles, leadbay_refine_prompt, leadbay_remove_epilogue, leadbay_remove_leads_from_campaign, leadbay_remove_pushback, leadbay_report_friction, leadbay_report_outreach, leadbay_research_lead_by_id, leadbay_research_lead_by_name_fuzzy, leadbay_resolve_import_rows, leadbay_seed_candidates, leadbay_select_leads, leadbay_set_active_lens, leadbay_set_epilogue_status, leadbay_set_pushback, leadbay_set_user_prompt, leadbay_tour_plan, leadbay_update_lens, leadbay_update_lens_filter;
 var init_tool_descriptions_generated = __esm({
   "../core/dist/tool-descriptions.generated.js"() {
     "use strict";
+    leadbay_account_history = `## WHEN TO USE
+
+Trigger phrases: "what's the history on this account", "why should I revisit this account", "summarize everything we've done with <Company>", "has this account gone cold", "give me the back-story on lead <UUID>".
+
+**Memory:** recall + capture via \`leadbay_agent_memory_*\` tools.
+
+Do NOT use for: "live signals only, no history" \u2192 \`leadbay_research_lead_by_id\`; "which accounts should I follow up with" \u2192 \`leadbay_pull_followups\`.
+
+Prefer when: user wants ONE account's full back-story \u2014 notes + past activity + current signals together; pass \`leadId\`
+
+Examples that SHOULD invoke this tool:
+- "What's the full history on this account \u2014 why did it resurface?"
+- "Summarize everything we've logged on that lead and whether it's worth another visit."
+
+Examples that should NOT invoke this tool (sound similar, route elsewhere):
+- "Tell me the current AI take on this lead."
+- "Which accounts should I follow up with this week?"
+
+## RENDER (quick)
+
+Single resurfaced-account card. Lead the card with the current signal/trigger
+line (from \`signals\`), then a "History" section: notes digest
+(chronological) + the activity timeline. Close with a one-line "why revisit
+now" synthesis and a suggested outreach angle tied to the freshest signal.
+
+---
+
+Give me one account's full back-story in a single call. This is the tool for
+the **reprioritize-a-neglected-account** workflow: the user has an account
+that was contacted or quoted long ago and wants to know, in one shot, whether
+a fresh signal makes it worth another visit.
+
+It bundles three reads on one \`leadId\`:
+
+1. **Current state** \u2014 passed through verbatim from \`leadbay_research_lead_by_id\`:
+   \`signals\` (web-research signals with hot flags + sources), \`firmographics\`,
+   \`qualification\` answers, \`contacts\`, and \`engagement\` counts. This is the
+   "why is this account hot NOW" layer.
+2. **\`notes\`** \u2014 the FULL list of notes logged on the record (note body +
+   \`created_at\`), chronological. \`leadbay_research_lead_by_id\` only returns a
+   \`notes_count\`; this tool returns the bodies so you can summarize the
+   historical context.
+3. **\`activities\`** \u2014 the interaction timeline (\`{type, date}\` entries, newest
+   first) plus the total count. Drives the "no contact in N months" judgement.
+
+\`notes\` and \`activities\` **degrade gracefully**: if either read fails the card
+still returns with that section empty (\`notes: []\` /
+\`activities.total: 0\`). The current-state block is load-bearing \u2014 if research
+itself errors the whole call fails, because there is nothing to narrate.
+
+Params: \`leadId\` (required UUID) and \`activityCount\` (optional, default 50,
+max 100).
+
+Companion tools: **leadbay_research_lead_by_id** when the user only wants the
+live AI take with no history; **leadbay_pull_followups** when the user wants a
+LIST of accounts to act on rather than one account's deep history.
+
+## RENDERING \u2014 single-record research card, mode-adaptive
+
+Present as a single-record card, not a table. This tool gets invoked in two distinct user contexts \u2014 detect which and adapt the body density accordingly.
+
+**MODE A \u2014 Discovery.** The user is evaluating whether to pursue this company as a target. Signals: "tell me about", "what do they do", "is this a fit", "research [company]", arrival via a click-through from \`leadbay_pull_leads\`, no prior outreach context in the conversation. Next step is usually qualify, deep-dive via \`leadbay_research_lead_by_id\`, or decide whether to start outreach.
+
+**MODE B \u2014 Contact preparation.** The user is about to call or email someone at this company and needs the talking points. Signals: "I'm calling them", "draft an email", "before my call", "outreach prep", "what should I say", or the conversation has already touched on a specific contact. Next step is usually \`leadbay_prepare_outreach\`.
+
+Default to MODE A when uncertain. Always offer the cross-mode pivot at the end so the user can redirect if you guessed wrong.
+
+### Common structure (both modes)
+
+- **Header** (H4 or H5): \`<10-segment score bar>\` \`[Company name](website)\`. Use the score-bar algorithm; the bar lives in a single inline-code span. Prefix \`https://\` to website if it's a bare hostname.
+- **Pill row** (immediately below the header): short location \xB7 compact size \xB7 social pill chips iterated over \`social_urls\` (each non-null platform becomes \`[<platform-label>](<url>)\`) \xB7 \`[website-domain](website)\` \xB7 \`\u260E phone\` when \`phone_numbers[]\` is non-empty (use the first number). All \` \xB7 \`-separated.
+- **Blurb**: render \`description\` (preferred) or \`short_description\` as a single blockquoted paragraph.
+- **Staleness line**: italic, \`"Researched <relative time>"\` from \`web_insights_fetched_at\`. Use \`"today"\` / \`"yesterday"\` / \`"N days ago"\` up to 30 days, then absolute date. Prefix with \`\u26A0\` if older than 30 days.
+- **Contacts table** (always at the bottom):
+  \`\`\`
+  |   | Name | Title | LinkedIn |
+  \`\`\`
+  Markers in column 1:
+  - \`\u2605\` \u2014 \`recommended_contact\` match.
+  - \`\u{1F48E}\` \u2014 name fuzzy-matches a \`hot: true\` entry in \`web_insights\` key_people. (Use \`\u{1F48E}\`, not \`\u{1F525}\`, to avoid glyph collision with the follow-up status badge.)
+  Sort \`\u2605\` first, then \`\u{1F48E}\`-only rows, then API order. Link the name via \`linkedin_page\` first; fall back to LinkedIn people-search with \`<First>+<Last>+<Company>\`. Append \`\xB0\` only when the fallback is in use AND \`social_presence.linkedin == false\`. Cap to 6 rows; if \`contacts_count > shown\`, end with \`"+N more \u2014 ask to see the full list"\`.
+
+### MODE A body (Discovery, fuller, scannable)
+
+Render each non-empty \`web_insights\` section as H5 with the emoji + label intact. Section order: \`\u{1F3E2} company profile\` \u2192 \`\u{1F4C8} business signals\` \u2192 \`\u{1F4A1} prospecting clues\` \u2192 \`\u{1F9E9} strategic positioning\` \u2192 \`\u{1F50E} technologies & innovation\`. Inside each, bullet 3\u20135 items. Sort \`hot: true\` items first. **Bold** the description text of hot items; leave cold items plain. Render \`source\` as \`[source](url)\` at the end; include \`date\` when present. Omit empty sections. Skip \`\u{1F517} social links\` (already in the pill row) and \`\u{1F464} key people\` (already in the contacts table).
+
+### MODE B body (Contact preparation, tighter)
+
+Render exactly two H5 sections:
+
+##### \u{1F3AF} Conversation hooks
+
+Distill the 3 most recent / most hot signals from \`\u{1F4C8} business signals\` and \`\u{1F4A1} prospecting clues\` into one-sentence talking points in salesperson voice. Strip the academic framing. Cite the source inline.
+
+##### \u{1F464} About the person *(only when recommended_contact is non-empty)*
+
+2-line summary: their title + any context from \`web_insights\` key_people. If they appear in a hot signal ("X appointed CEO"), surface that prominently.
+
+Skip \u{1F3E2} profile, \u{1F9E9} strategic positioning, \u{1F50E} technologies in MODE B \u2014 context the user doesn't need for the next 30 seconds.
+
+If \`qualification[]\` is non-empty, append one collapsed line: \`"Qualification: N questions answered, avg boost X"\` and offer to expand in NEXT STEPS.
+
+**Hide:** \`id\`, \`lead.id\`, \`contact.id\`, \`lead.location.pos\`, \`web_fetch_in_progress\`, \`enrichment_in_progress\`, \`recommended_contact_title\` (duplicates \`recommended_contact.job_title\`), empty arrays, fields whose value is the string \`"null"\`, \`contact.source\` (internal), insights whose \`source\` is empty.
+
+**Legend (print once below the card):** \`\` \`\u25B0\` firmographic \xB7 \`\u2756\` AI booster \xB7 \`\u25B1\` unfilled \xB7 \u2605 recommended \xB7 \u{1F48E} hot in web_insights \xB7 \xB0 = no company LinkedIn (fallback link only) \`\`
+
+## Linking a contact's name
+
+**MANDATORY: every contact name in your output \u2014 table cells, prose, headers, "Reach <Name>" callouts \u2014 MUST be wrapped in markdown link syntax \`[Name](URL)\`. Never render a contact name as bare text. A plain-text name is a broken contact card; the underlined name is the user's primary affordance for "take me to this person's profile". No "no URL available" exception \u2014 the search URL below is always constructable from name + company.**
+
+URL priority (first applicable wins):
+
+1. **Real profile** \u2014 \`contact.linkedin_page\` when it's a string starting with \`https://\` (the MCP coerces the legacy literal \`"null"\` string to real null before you see it).
+2. **Constructed people-search** \u2014 \`https://www.linkedin.com/search/results/people/?keywords=<First>+<Last>+<Company>\`. URL-encode params. Strip Inc / LLC / Corp / Ltd / GmbH / Co / S.A. / S.L. / PLC / AG / SAS / SARL suffixes from the company. Append a trailing \` \xB0\` to the rendered name ONLY when this fallback is in use AND \`social_presence.linkedin == false\`. Never append \`\xB0\` when a real \`linkedin_page\` was used.
+
+Never link a person's name to the company's LinkedIn page (and vice versa) \u2014 the two surfaces are different and conflating them quietly degrades the workflow.
+
+## Linking the company
+
+Use the lead's \`website\` as the company-name link target \u2014 prefix \`https://\` if the value is a bare hostname. (The MCP does NOT synthesize a Leadbay-app deep-link URL; the team has not standardized one. Linking to \`website\` is always real data.)
+
+When the response carries \`social_urls\` (the post-fix multi-platform URL block on rich-lead responses), render every non-null platform as a pill chip in the company-info row. Iterate over \`social_urls\`'s keys \u2014 never hardcode a fixed list \u2014 and emit each as \`[<platform-label>](<url>)\`. Skip platforms whose URL is null.
+
+\`social_presence\` carries booleans for the same 6 platforms (crunchbase, facebook, instagram, linkedin, tiktok, twitter) \u2014 useful when you only care that the company has a profile somewhere. Use it as the \xB0-flag signal in the contact people-search fallback (see linking/contact-linkedin).
+
+
+
+### RENDERING \u2014 the history layer (on top of the card above)
+
+After the research card, add a **History** section so the user sees why this
+account resurfaced:
+
+- **##### \u{1F5D2} Notes** \u2014 render \`notes\` chronologically (oldest \u2192 newest). Each
+  as a bullet: \`**<relative date from created_at>** \u2014 <note body>\`. Cap at 8;
+  if \`_meta.notes_count > shown\`, end with \`"+N more notes"\`. Omit the section
+  entirely when \`notes\` is empty.
+- **##### \u{1F553} Timeline** \u2014 render \`activities.activities\` newest-first as a
+  compact bullet list: \`<relative date> \xB7 <type>\`. Cap at 10; if
+  \`activities.total > shown\`, end with \`"+N earlier"\`. Omit when empty.
+- **##### \u21BB Why revisit now** \u2014 one or two sentences synthesizing the freshest
+  HOT signal from \`signals\` against the gap in \`activities\` (e.g. "Won a public
+  tender last month; no logged contact since the 2024 quote \u2014 strong re-open
+  angle"). Then one suggested outreach angle tied to that signal. This
+  synthesis is the payload of the whole tool \u2014 always include it when there is
+  at least one hot signal.
+`;
     leadbay_account_status = `## WHEN TO USE
 
 Trigger phrases: "what's my account status", "how much quota do I have", "what lens am I on", "I topped up / I bought credits / I added credits".
@@ -5462,10 +5609,13 @@ Examples that should NOT invoke this tool (sound similar, route elsewhere):
 
 ## RENDER (quick)
 
-Compact markdown: org name + admin badge on line 1; active lens on
-line 2; per-window quota usage as \`(used / cap)\` chips for
-llm_completion \xB7 ai_rescore \xB7 web_fetch. Surface regeneration flag
-prominently if mid-regen.
+If \`quota_error\` is set the call FAILED \u2014 quota unreadable; on 401/403 tell
+the user to reconnect. NEVER report zero usage or "no limits". Else render
+\`quota.org.resources\` (usage lives there, NOT at quota.resources) as a
+table, never prose: rows = resources (llm_completion \xB7 ai_rescore \xB7
+web_fetch + others), cols = Daily/Weekly/Monthly used \`count\` (= amount
+USED; no cap field, \`plan\` may be null \u2014 never invent a denominator).
+Empty = a 0 table, not "unlimited". Above: org + admin, lens.
 
 ---
 
@@ -5652,6 +5802,10 @@ This tool MUTATES state. The caller (agent or human-in-the-loop) is responsible
 WHEN TO USE: poll this after leadbay_enrich_titles returns a \`bulk_id\`. Default \`include_contacts=false\` for cheap status polls; set \`include_contacts=true\` once \`all_done\` flips for the final read.
 
 WHEN NOT TO USE: as a substitute for leadbay_research_lead_by_id \u2014 that already includes enriched contacts for a single lead.
+
+## CREDIT COST \u2014 show the balance, discreetly
+
+Once \`all_done\` is true the result carries \`credits_remaining\` (the post-spend AI-credit balance). Don't make a fuss \u2014 no sentence, no callout. Just append ONE small italic line in parentheses at the very END of your reply: \`_(N credits remaining)_\`. If \`credits_remaining\` is null (billing unavailable), omit the line \u2014 don't print 0. Do NOT report a "credits used" figure for this run: the per-contact cost can't be scoped to this specific enrichment (a lead's contact list mixes in earlier runs), so any "X used" number would be misleading.
 `;
     leadbay_bulk_qualify_leads = `Pick the next N unqualified leads in the active lens and qualify them (run AI rescore + web fetch). Pass \`wait_for_completion:false\` to return quickly with \`{status:'running', qualify_id}\`; poll leadbay_qualify_status with that id. With \`wait_for_completion\` omitted/true, the legacy behavior polls until the answers are populated or a budget is exhausted. Already-qualified leads (those with a non-null \`ai_agent_lead_score\`) are silently no-ops on the backend, so this composite paginates past them to find fresh candidates. On 429 mid-fanout, stops launching but keeps polling already-launched leads.
 
@@ -6116,6 +6270,10 @@ WHEN TO USE: when you have a specific \`contact_id\` (from leadbay_get_contacts)
 
 WHEN NOT TO USE: for bulk enrichment by job title across many leads \u2014 use leadbay_enrich_titles, which handles the selection lifecycle and returns a clean preview/launch flow.
 
+## CREDIT COST \u2014 discreet
+
+This is a paid call. The result returns \`credits_remaining\` (billing.ai_credits, read before the spend). Don't make a fuss about credits: only flag the balance if it's low (e.g. \u2264 a few credits) so the user can decide. Otherwise append it quietly as a small italic parenthetical at the END of your reply \u2014 \`_(N credits remaining)_\`. Don't quote an exact per-contact cost (the rate is backend-only). The actual per-contact cost (enrichment.credits_used) appears on the contact via leadbay_get_contacts after enrichment. If \`credits_remaining\` is null, omit the line \u2014 don't assume zero.
+
 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_enrich_titles = `Order contact enrichments by job title across many leads. Contacts are NOT returned by default with a lead (Leadbay keeps enrichment out-of-band to control cost); the agent requests them on demand via this tool when it's ready to actually reach out. Two modes: (A) NO \`titles\` param \u2014 returns the available titles + Leadbay's \`title_suggestions\` + \`auto_included_titles\` + a count of enrichable contacts, so the agent can ask the user which titles to enrich. (B) \`titles\` given \u2014 calls preview, then launches if there's anything enrichable. On 429 returns \`{status:'quota_exceeded'}\` cleanly. Selection lifecycle is wrapped in a try/finally so the user's selection is left clean even on error.
@@ -6124,6 +6282,35 @@ WHEN TO USE: as the agent's go-to enrichment entry point, immediately before pro
 
 WHEN NOT TO USE: to enrich a single contact \u2014 that's leadbay_enrich_contacts (granular). Speculatively, before the user has committed to outreaching \u2014 enrichment spends credits.
 
+## CREDIT COST \u2014 make spend visible
+
+Enrichment is the main PAID operation. Surface cost both before and after.
+
+**BEFORE (confirm before launching).** The discover / preview_only / dry_run modes return \`credits_remaining\` (the balance) and \`enrichable_contacts\` (the volume that would be enriched). Tell the user plainly: **"You have {credits_remaining} credits. This will enrich {enrichable_contacts} contacts."** then ask them to confirm before you launch the paid run. Route that confirmation through \`ask_user_input_v0\` ("Enrich {enrichable_contacts} contacts now?" \u2192 ["Yes, enrich", "No, cancel"]). Do NOT state an exact estimated cost \u2014 the per-contact credit rate lives backend-side and is not in the preview; show the balance and the count, never a fabricated "will cost N credits". If \`credits_remaining\` is null, billing is unavailable \u2014 say the balance is unknown, don't assume zero or unlimited.
+
+**AFTER (show the balance, discreetly).** Once the job finishes \u2014 poll \`leadbay_bulk_enrich_status\`, which returns \`credits_remaining\` (the post-spend balance). Don't make a fuss: append ONE small italic line in parentheses at the very END of your reply \u2014 \`_(N credits remaining)_\`. Omit it if \`credits_remaining\` is null. Do NOT report a "credits used" figure: per-run cost can't be scoped reliably (a lead's contacts mix earlier enrichments), so only the balance is shown.
+
+## 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\` (Claude) | Result has \u22652 leads with \`location.city\` set, and the user's intent is geographic / "in person" / travel | \`{name: lead.company_name, address: "<city>, <country>", place_id: lead.location.place_id ?? omit, notes: <one-sentence pitch>}\` per location |
+| \`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) | The tool's NEXT STEPS block has 2\u20134 mutually-exclusive next moves and the user hasn't already chosen | \`{questions: [{question: "What next?", type: "single_select", options: [<2-4 short button labels>]}]}\`; max 3 questions per call |
+
+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.
+
+**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.
+
+
 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_extend_lens = `## WHEN TO USE
@@ -8934,10 +9121,36 @@ var init_get_quota = __esm({
       outputSchema: {
         type: "object",
         properties: {
-          plan: { type: ["string", "null"], description: "Org plan tier (e.g., FREE, PRO)." },
+          plan: {
+            type: ["string", "null"],
+            description: "Org plan tier (e.g., FREE, TIER1, TIER2). May be null."
+          },
+          org: {
+            type: "object",
+            description: "Org-level quota state.",
+            properties: {
+              spend: { type: "array", description: "Reserved; empty in practice.", items: { type: "object" } },
+              resources: {
+                type: "array",
+                description: "Per-resource per-window USAGE. Each: {resource_type, count, window_type, resets_at}. `count` is the amount USED in that window (not remaining, not a cap). No cap field is returned by the API.",
+                items: { type: "object" }
+              }
+            }
+          },
+          user: {
+            type: "object",
+            description: "User-level quota state, same shape as `org`. May be absent.",
+            properties: {
+              spend: { type: "array", items: { type: "object" } },
+              resources: { type: "array", items: { type: "object" } }
+            }
+          },
+          // Legacy/compat: the live API does NOT return a top-level `windows`
+          // array — usage lives in org/user.resources[]. Declared only so older
+          // recorded fixtures still conform; do not rely on it.
           windows: {
             type: "array",
-            description: "Per-resource per-window limits. Each: {resource, window, current_units, max_units, resets_at}.",
+            description: "Deprecated \u2014 not returned by the live API. Use org/user.resources[].",
             items: { type: "object" }
           }
         }
@@ -15028,6 +15241,86 @@ var init_research_lead_by_name_fuzzy = __esm({
   }
 });
 
+// ../core/dist/composite/account-history.js
+var accountHistory;
+var init_account_history = __esm({
+  "../core/dist/composite/account-history.js"() {
+    "use strict";
+    init_research_lead_by_id();
+    init_tool_descriptions_generated();
+    accountHistory = {
+      name: "leadbay_account_history",
+      annotations: {
+        title: "One account's full back-story",
+        readOnlyHint: true,
+        destructiveHint: false,
+        idempotentHint: true,
+        openWorldHint: true
+      },
+      description: leadbay_account_history,
+      inputSchema: {
+        type: "object",
+        properties: {
+          leadId: { type: "string", description: "Lead UUID (required)" },
+          activityCount: {
+            type: "number",
+            description: "Number of activity-timeline entries to return, max 100 (default: 50)."
+          },
+          lensId: {
+            type: "number",
+            description: "Lens id the lead came from (escape hatch \u2014 normally omit; defaults to the active lens). Pass it when researching a lead from a lens other than the current default, so the underlying /lenses/{lensId}/leads/{leadId} fetch doesn't 404 after the active lens changed."
+          }
+        },
+        required: ["leadId"],
+        additionalProperties: false
+      },
+      execute: async (client, params, ctx) => {
+        const leadId = params.leadId;
+        const count = Math.max(1, Math.min(Math.floor(params.activityCount ?? 50), 100));
+        const [research, notes, activities] = await Promise.all([
+          researchLeadById.execute(client, { leadId, lensId: params.lensId, response_format: "json" }, ctx),
+          client.request("GET", `/leads/${leadId}/notes`).catch(() => []),
+          client.request("GET", `/leads/${leadId}/activities?count=${count}`).catch(() => ({ items: [], pagination: { total: 0 } }))
+        ]);
+        const r = research;
+        const noteList = Array.isArray(notes) ? notes : [];
+        const activityItems = Array.isArray(activities?.items) ? activities.items : [];
+        return {
+          lead: {
+            id: r.firmographics?.id ?? leadId,
+            name: r.firmographics?.name ?? null
+          },
+          // Current state — signals, firmographics, qualification, contacts,
+          // engagement: passed through verbatim from research_lead_by_id so the
+          // agent gets the live "why is this account hot NOW" picture.
+          signals: r.signals ?? null,
+          firmographics: r.firmographics ?? null,
+          qualification: r.qualification ?? [],
+          contacts: r.contacts ?? null,
+          engagement: r.engagement ?? null,
+          // Historical context — the part research only counts/summarizes.
+          notes: noteList,
+          activities: {
+            activities: activityItems.map((a) => ({ type: a.type, date: a.date })),
+            total: activities?.pagination?.total ?? 0
+          },
+          // Preserve research's pass-through metadata (agent_memory summary,
+          // lens_id, web_fetch_in_progress, has_reachable_contact, …) — the
+          // generated description advertises the memory protocol, so dropping
+          // _meta.agent_memory would make history narratives miss stored
+          // preferences. Spread research _meta first, then layer our counts.
+          _meta: {
+            ...r._meta ?? {},
+            region: client.region,
+            notes_count: noteList.length,
+            activities_returned: activityItems.length
+          }
+        };
+      }
+    };
+  }
+});
+
 // ../core/dist/composite/recall-ordered-titles.js
 var recallOrderedTitles;
 var init_recall_ordered_titles = __esm({
@@ -15208,7 +15501,16 @@ var init_account_status = __esm({
           },
           quota: {
             type: ["object", "null"],
-            description: "Per-resource quota state (llm_completion, ai_rescore, web_fetch, LENS_EXTRA_REFILL) across daily/weekly/monthly windows. Null if /quota_status failed (logged in stderr). Pre-check the LENS_EXTRA_REFILL entry before calling leadbay_extend_lens."
+            description: "Per-resource quota state (llm_completion, ai_rescore, web_fetch, LENS_EXTRA_REFILL) across daily/weekly/monthly windows. Null if /quota_status failed (see quota_error) or genuinely returned nothing. Pre-check the LENS_EXTRA_REFILL entry before calling leadbay_extend_lens."
+          },
+          quota_error: {
+            type: ["object", "null"],
+            description: "Non-null ONLY when the quota_status call FAILED \u2014 {code, http_status, message}. A 401/403 means the token lacks quota scope: tell the user to reconnect / re-run OAuth. Treat as 'quota unreadable', NEVER as zero usage or 'no limits'.",
+            properties: {
+              code: { type: "string" },
+              http_status: { type: ["number", "null"] },
+              message: { type: "string" }
+            }
           },
           notifications: {
             type: "array",
@@ -15249,9 +15551,15 @@ var init_account_status = __esm({
       execute: async (client, _params, ctx) => {
         const me = await client.resolveMe();
         let quota = null;
+        let quota_error = null;
         try {
           quota = await client.request("GET", `/organizations/${me.organization.id}/quota_status`);
         } catch (err) {
+          quota_error = {
+            code: err?.code ?? "QUOTA_STATUS_FAILED",
+            http_status: err?._meta?.http_status ?? null,
+            message: err?.message ?? "quota_status request failed"
+          };
           ctx?.logger?.warn?.(`account_status: quota_status failed: ${err?.message ?? err?.code ?? err}`);
         }
         return withAgentMemoryMeta(client, {
@@ -15281,6 +15589,9 @@ var init_account_status = __esm({
           // Empty array when the WS listener isn't wired (OpenClaw, tests) OR
           // when nothing has completed since the last ack.
           notifications: ctx?.notificationsInbox?.list() ?? [],
+          // Non-null ONLY when the quota_status call failed. The agent must treat
+          // this as "could not read quota" (reauth on 401/403) — NOT as zero usage.
+          quota_error,
           _meta: {
             region: client.region
           }
@@ -17661,11 +17972,27 @@ var init_qualify_status = __esm({
   }
 });
 
+// ../core/dist/composite/_credits-helpers.js
+async function readCreditsRemaining(client, force = false) {
+  try {
+    const me = await client.resolveMe(force);
+    return me.organization.billing?.ai_credits ?? null;
+  } catch {
+    return null;
+  }
+}
+var init_credits_helpers = __esm({
+  "../core/dist/composite/_credits-helpers.js"() {
+    "use strict";
+  }
+});
+
 // ../core/dist/composite/enrich-titles.js
 var DEFAULT_CANDIDATE_COUNT, enrichTitles;
 var init_enrich_titles = __esm({
   "../core/dist/composite/enrich-titles.js"() {
     "use strict";
+    init_credits_helpers();
     init_tool_descriptions_generated();
     DEFAULT_CANDIDATE_COUNT = 25;
     enrichTitles = {
@@ -17749,6 +18076,10 @@ var init_enrich_titles = __esm({
             type: "number",
             description: "Count of enrichable contacts at preview time."
           },
+          credits_remaining: {
+            type: ["number", "null"],
+            description: "AI-credit balance BEFORE launching (billing.ai_credits). Present in discover / preview_only / dry_run modes. Pair with enrichable_contacts to tell the user 'you have N credits, this will enrich M contacts' \u2014 do NOT estimate an exact cost (the per-contact rate is backend-only). Null = billing unavailable."
+          },
           selected_lead_count: {
             type: "number",
             description: "How many leads the selection covers."
@@ -17872,6 +18203,10 @@ var init_enrich_titles = __esm({
                 previously_enriched: previouslyEnriched,
                 enrichable_contacts: enrichableContacts,
                 selected_lead_count: leadIds.length,
+                // BEFORE: show balance + volume. We can't estimate exact cost
+                // (the per-contact rate is backend-only), so surface the balance
+                // and the count, not a fabricated "will cost N".
+                credits_remaining: await readCreditsRemaining(client),
                 next_action: "Pick titles to enrich and call leadbay_enrich_titles again with titles=[...]"
               };
             }
@@ -17894,7 +18229,8 @@ var init_enrich_titles = __esm({
                 preview,
                 launched: false,
                 message: "No enrichable contacts for the chosen titles. Try other titles from available_titles or recommendations.",
-                available_titles: availableTitles
+                available_titles: availableTitles,
+                credits_remaining: await readCreditsRemaining(client)
               };
             }
             if (params.dry_run) {
@@ -17902,7 +18238,12 @@ var init_enrich_titles = __esm({
                 mode: "dry_run",
                 preview,
                 launched: false,
-                would_launch: { titles: params.titles, email, phone }
+                would_launch: { titles: params.titles, email, phone },
+                // BEFORE confirmation gate: balance + how many contacts WOULD be
+                // enriched. enrichable_contacts is the volume; credits_remaining
+                // the balance. No estimated cost — that rate is backend-only.
+                enrichable_contacts: preview.enrichable_contacts,
+                credits_remaining: await readCreditsRemaining(client)
               };
             }
             const tracker = ctx?.bulkTracker;
@@ -18053,6 +18394,7 @@ var init_bulk_enrich_status = __esm({
     "use strict";
     init_get_contacts();
     init_bulk_store();
+    init_credits_helpers();
     init_tool_descriptions_generated();
     STATUS_FETCH_CONCURRENCY = 5;
     bulkEnrichStatus = {
@@ -18119,6 +18461,10 @@ var init_bulk_enrich_status = __esm({
             type: "boolean",
             description: "True when overall_progress.done === total AND no partial_failures."
           },
+          credits_remaining: {
+            type: ["number", "null"],
+            description: "AI-credit balance re-read after the spend (force-refreshed /users/me \u2192 billing.ai_credits). Present only when all_done. Null = billing unavailable (don't read as zero). NOTE: a per-run 'credits used' figure is intentionally NOT returned \u2014 getContacts can't scope cost to this bulk, so any sum would conflate historical enrichments."
+          },
           partial_failures: {
             type: "array",
             description: "Per-lead errors observed during contacts fan-out (omitted when no failures).",
@@ -18225,6 +18571,7 @@ var init_bulk_enrich_status = __esm({
               leads2 = record.lead_ids.map((id) => ({ lead_id: id }));
             }
             ctx?.logger?.info?.(`bulk.status_checked_via_notification bulk_id=${record.bulk_id} notification_id=${notifId} done=${bp.success_count}/${bp.total_count} in_progress=${inProgress} wall_ms=${Date.now() - startMs}`);
+            const creditsRemaining2 = !inProgress ? await readCreditsRemaining(client, true) : null;
             return {
               bulk_id: record.bulk_id,
               notification_id: notifId,
@@ -18244,6 +18591,7 @@ var init_bulk_enrich_status = __esm({
               bulk_progress: bp,
               in_progress: inProgress,
               all_done: !inProgress,
+              ...!inProgress ? { credits_remaining: creditsRemaining2 } : {},
               ...bp.quota_hit_count > 0 ? {
                 quota_hit_hint: "Some contacts could not be enriched because the AI-credits quota was hit. Top up via leadbay_create_topup_link or wait for the window reset."
               } : {}
@@ -18316,6 +18664,10 @@ var init_bulk_enrich_status = __esm({
         };
         const allDone = totalAll > 0 && totalDone === totalAll && partialFailures.length === 0;
         ctx?.logger?.info?.(`bulk.status_checked bulk_id=${record.bulk_id} done=${totalDone} total=${totalAll} wall_ms=${Date.now() - startMs}`);
+        let creditsRemaining = null;
+        if (allDone) {
+          creditsRemaining = await readCreditsRemaining(client, true);
+        }
         return {
           bulk_id: record.bulk_id,
           launched_at: record.launched_at,
@@ -18328,6 +18680,7 @@ var init_bulk_enrich_status = __esm({
           leads,
           overall_progress: overallProgress,
           all_done: allDone,
+          ...allDone ? { credits_remaining: creditsRemaining } : {},
           ...partialFailures.length > 0 ? { partial_failures: partialFailures } : {}
         };
       }
@@ -20022,6 +20375,7 @@ __export(dist_exports, {
   NotificationsInbox: () => NotificationsInbox,
   NotificationsWsClient: () => NotificationsWsClient,
   REGIONS: () => REGIONS,
+  accountHistory: () => accountHistory,
   accountStatus: () => accountStatus,
   acknowledgeNotification: () => acknowledgeNotification,
   addLeadsToCampaign: () => addLeadsToCampaign,
@@ -20219,6 +20573,7 @@ var init_dist = __esm({
     init_campaign_call_sheet();
     init_research_lead_by_id();
     init_research_lead_by_name_fuzzy();
+    init_account_history();
     init_recall_ordered_titles();
     init_account_status();
     init_bulk_qualify_leads();
@@ -20311,6 +20666,13 @@ var init_dist = __esm({
       campaignCallSheet,
       researchLeadById,
       researchLeadByNameFuzzy,
+      // accountHistory layers FULL notes + activity timeline on top of research
+      // so the agent can write the US4 "why has this dormant account resurfaced"
+      // narrative in ONE call. ALWAYS exposed (compositeReadTools) — the underlying
+      // get_lead_notes / get_lead_activities are ADVANCED-gated, but the
+      // reprioritize-a-neglected-account workflow (#3630 GAP C) must work in a
+      // default deployment without LEADBAY_MCP_ADVANCED=1.
+      accountHistory,
       recallOrderedTitles,
       accountStatus,
       bulkEnrichStatus,
@@ -24276,7 +24638,7 @@ var OAUTH_BASE_URLS = {
     fr: "https://staging.api.leadbay.app"
   }
 };
-var VERSION = "0.18.0";
+var VERSION = "0.18.1";
 var HELP = `
 leadbay-mcp ${VERSION} \u2014 Leadbay Model Context Protocol server
 

package/dist/http-server.js

@@ -6188,6 +6188,7 @@ function makeAgentMemoryTombstone(input) {
 
 // ../core/dist/composite/_composite-file-names.js
 var COMPOSITE_FILE_TOOL_NAMES = /* @__PURE__ */ new Set([
+  "leadbay_account_history",
   "leadbay_account_status",
   "leadbay_add_leads_to_campaign",
   "leadbay_adjust_audience",
@@ -6226,6 +6227,152 @@ var COMPOSITE_FILE_TOOL_NAMES = /* @__PURE__ */ new Set([
 var DEFAULT_TTL_MS = 24 * 60 * 60 * 1e3;
 
 // ../core/dist/tool-descriptions.generated.js
+var leadbay_account_history = `## WHEN TO USE
+
+Trigger phrases: "what's the history on this account", "why should I revisit this account", "summarize everything we've done with <Company>", "has this account gone cold", "give me the back-story on lead <UUID>".
+
+**Memory:** recall + capture via \`leadbay_agent_memory_*\` tools.
+
+Do NOT use for: "live signals only, no history" \u2192 \`leadbay_research_lead_by_id\`; "which accounts should I follow up with" \u2192 \`leadbay_pull_followups\`.
+
+Prefer when: user wants ONE account's full back-story \u2014 notes + past activity + current signals together; pass \`leadId\`
+
+Examples that SHOULD invoke this tool:
+- "What's the full history on this account \u2014 why did it resurface?"
+- "Summarize everything we've logged on that lead and whether it's worth another visit."
+
+Examples that should NOT invoke this tool (sound similar, route elsewhere):
+- "Tell me the current AI take on this lead."
+- "Which accounts should I follow up with this week?"
+
+## RENDER (quick)
+
+Single resurfaced-account card. Lead the card with the current signal/trigger
+line (from \`signals\`), then a "History" section: notes digest
+(chronological) + the activity timeline. Close with a one-line "why revisit
+now" synthesis and a suggested outreach angle tied to the freshest signal.
+
+---
+
+Give me one account's full back-story in a single call. This is the tool for
+the **reprioritize-a-neglected-account** workflow: the user has an account
+that was contacted or quoted long ago and wants to know, in one shot, whether
+a fresh signal makes it worth another visit.
+
+It bundles three reads on one \`leadId\`:
+
+1. **Current state** \u2014 passed through verbatim from \`leadbay_research_lead_by_id\`:
+   \`signals\` (web-research signals with hot flags + sources), \`firmographics\`,
+   \`qualification\` answers, \`contacts\`, and \`engagement\` counts. This is the
+   "why is this account hot NOW" layer.
+2. **\`notes\`** \u2014 the FULL list of notes logged on the record (note body +
+   \`created_at\`), chronological. \`leadbay_research_lead_by_id\` only returns a
+   \`notes_count\`; this tool returns the bodies so you can summarize the
+   historical context.
+3. **\`activities\`** \u2014 the interaction timeline (\`{type, date}\` entries, newest
+   first) plus the total count. Drives the "no contact in N months" judgement.
+
+\`notes\` and \`activities\` **degrade gracefully**: if either read fails the card
+still returns with that section empty (\`notes: []\` /
+\`activities.total: 0\`). The current-state block is load-bearing \u2014 if research
+itself errors the whole call fails, because there is nothing to narrate.
+
+Params: \`leadId\` (required UUID) and \`activityCount\` (optional, default 50,
+max 100).
+
+Companion tools: **leadbay_research_lead_by_id** when the user only wants the
+live AI take with no history; **leadbay_pull_followups** when the user wants a
+LIST of accounts to act on rather than one account's deep history.
+
+## RENDERING \u2014 single-record research card, mode-adaptive
+
+Present as a single-record card, not a table. This tool gets invoked in two distinct user contexts \u2014 detect which and adapt the body density accordingly.
+
+**MODE A \u2014 Discovery.** The user is evaluating whether to pursue this company as a target. Signals: "tell me about", "what do they do", "is this a fit", "research [company]", arrival via a click-through from \`leadbay_pull_leads\`, no prior outreach context in the conversation. Next step is usually qualify, deep-dive via \`leadbay_research_lead_by_id\`, or decide whether to start outreach.
+
+**MODE B \u2014 Contact preparation.** The user is about to call or email someone at this company and needs the talking points. Signals: "I'm calling them", "draft an email", "before my call", "outreach prep", "what should I say", or the conversation has already touched on a specific contact. Next step is usually \`leadbay_prepare_outreach\`.
+
+Default to MODE A when uncertain. Always offer the cross-mode pivot at the end so the user can redirect if you guessed wrong.
+
+### Common structure (both modes)
+
+- **Header** (H4 or H5): \`<10-segment score bar>\` \`[Company name](website)\`. Use the score-bar algorithm; the bar lives in a single inline-code span. Prefix \`https://\` to website if it's a bare hostname.
+- **Pill row** (immediately below the header): short location \xB7 compact size \xB7 social pill chips iterated over \`social_urls\` (each non-null platform becomes \`[<platform-label>](<url>)\`) \xB7 \`[website-domain](website)\` \xB7 \`\u260E phone\` when \`phone_numbers[]\` is non-empty (use the first number). All \` \xB7 \`-separated.
+- **Blurb**: render \`description\` (preferred) or \`short_description\` as a single blockquoted paragraph.
+- **Staleness line**: italic, \`"Researched <relative time>"\` from \`web_insights_fetched_at\`. Use \`"today"\` / \`"yesterday"\` / \`"N days ago"\` up to 30 days, then absolute date. Prefix with \`\u26A0\` if older than 30 days.
+- **Contacts table** (always at the bottom):
+  \`\`\`
+  |   | Name | Title | LinkedIn |
+  \`\`\`
+  Markers in column 1:
+  - \`\u2605\` \u2014 \`recommended_contact\` match.
+  - \`\u{1F48E}\` \u2014 name fuzzy-matches a \`hot: true\` entry in \`web_insights\` key_people. (Use \`\u{1F48E}\`, not \`\u{1F525}\`, to avoid glyph collision with the follow-up status badge.)
+  Sort \`\u2605\` first, then \`\u{1F48E}\`-only rows, then API order. Link the name via \`linkedin_page\` first; fall back to LinkedIn people-search with \`<First>+<Last>+<Company>\`. Append \`\xB0\` only when the fallback is in use AND \`social_presence.linkedin == false\`. Cap to 6 rows; if \`contacts_count > shown\`, end with \`"+N more \u2014 ask to see the full list"\`.
+
+### MODE A body (Discovery, fuller, scannable)
+
+Render each non-empty \`web_insights\` section as H5 with the emoji + label intact. Section order: \`\u{1F3E2} company profile\` \u2192 \`\u{1F4C8} business signals\` \u2192 \`\u{1F4A1} prospecting clues\` \u2192 \`\u{1F9E9} strategic positioning\` \u2192 \`\u{1F50E} technologies & innovation\`. Inside each, bullet 3\u20135 items. Sort \`hot: true\` items first. **Bold** the description text of hot items; leave cold items plain. Render \`source\` as \`[source](url)\` at the end; include \`date\` when present. Omit empty sections. Skip \`\u{1F517} social links\` (already in the pill row) and \`\u{1F464} key people\` (already in the contacts table).
+
+### MODE B body (Contact preparation, tighter)
+
+Render exactly two H5 sections:
+
+##### \u{1F3AF} Conversation hooks
+
+Distill the 3 most recent / most hot signals from \`\u{1F4C8} business signals\` and \`\u{1F4A1} prospecting clues\` into one-sentence talking points in salesperson voice. Strip the academic framing. Cite the source inline.
+
+##### \u{1F464} About the person *(only when recommended_contact is non-empty)*
+
+2-line summary: their title + any context from \`web_insights\` key_people. If they appear in a hot signal ("X appointed CEO"), surface that prominently.
+
+Skip \u{1F3E2} profile, \u{1F9E9} strategic positioning, \u{1F50E} technologies in MODE B \u2014 context the user doesn't need for the next 30 seconds.
+
+If \`qualification[]\` is non-empty, append one collapsed line: \`"Qualification: N questions answered, avg boost X"\` and offer to expand in NEXT STEPS.
+
+**Hide:** \`id\`, \`lead.id\`, \`contact.id\`, \`lead.location.pos\`, \`web_fetch_in_progress\`, \`enrichment_in_progress\`, \`recommended_contact_title\` (duplicates \`recommended_contact.job_title\`), empty arrays, fields whose value is the string \`"null"\`, \`contact.source\` (internal), insights whose \`source\` is empty.
+
+**Legend (print once below the card):** \`\` \`\u25B0\` firmographic \xB7 \`\u2756\` AI booster \xB7 \`\u25B1\` unfilled \xB7 \u2605 recommended \xB7 \u{1F48E} hot in web_insights \xB7 \xB0 = no company LinkedIn (fallback link only) \`\`
+
+## Linking a contact's name
+
+**MANDATORY: every contact name in your output \u2014 table cells, prose, headers, "Reach <Name>" callouts \u2014 MUST be wrapped in markdown link syntax \`[Name](URL)\`. Never render a contact name as bare text. A plain-text name is a broken contact card; the underlined name is the user's primary affordance for "take me to this person's profile". No "no URL available" exception \u2014 the search URL below is always constructable from name + company.**
+
+URL priority (first applicable wins):
+
+1. **Real profile** \u2014 \`contact.linkedin_page\` when it's a string starting with \`https://\` (the MCP coerces the legacy literal \`"null"\` string to real null before you see it).
+2. **Constructed people-search** \u2014 \`https://www.linkedin.com/search/results/people/?keywords=<First>+<Last>+<Company>\`. URL-encode params. Strip Inc / LLC / Corp / Ltd / GmbH / Co / S.A. / S.L. / PLC / AG / SAS / SARL suffixes from the company. Append a trailing \` \xB0\` to the rendered name ONLY when this fallback is in use AND \`social_presence.linkedin == false\`. Never append \`\xB0\` when a real \`linkedin_page\` was used.
+
+Never link a person's name to the company's LinkedIn page (and vice versa) \u2014 the two surfaces are different and conflating them quietly degrades the workflow.
+
+## Linking the company
+
+Use the lead's \`website\` as the company-name link target \u2014 prefix \`https://\` if the value is a bare hostname. (The MCP does NOT synthesize a Leadbay-app deep-link URL; the team has not standardized one. Linking to \`website\` is always real data.)
+
+When the response carries \`social_urls\` (the post-fix multi-platform URL block on rich-lead responses), render every non-null platform as a pill chip in the company-info row. Iterate over \`social_urls\`'s keys \u2014 never hardcode a fixed list \u2014 and emit each as \`[<platform-label>](<url>)\`. Skip platforms whose URL is null.
+
+\`social_presence\` carries booleans for the same 6 platforms (crunchbase, facebook, instagram, linkedin, tiktok, twitter) \u2014 useful when you only care that the company has a profile somewhere. Use it as the \xB0-flag signal in the contact people-search fallback (see linking/contact-linkedin).
+
+
+
+### RENDERING \u2014 the history layer (on top of the card above)
+
+After the research card, add a **History** section so the user sees why this
+account resurfaced:
+
+- **##### \u{1F5D2} Notes** \u2014 render \`notes\` chronologically (oldest \u2192 newest). Each
+  as a bullet: \`**<relative date from created_at>** \u2014 <note body>\`. Cap at 8;
+  if \`_meta.notes_count > shown\`, end with \`"+N more notes"\`. Omit the section
+  entirely when \`notes\` is empty.
+- **##### \u{1F553} Timeline** \u2014 render \`activities.activities\` newest-first as a
+  compact bullet list: \`<relative date> \xB7 <type>\`. Cap at 10; if
+  \`activities.total > shown\`, end with \`"+N earlier"\`. Omit when empty.
+- **##### \u21BB Why revisit now** \u2014 one or two sentences synthesizing the freshest
+  HOT signal from \`signals\` against the gap in \`activities\` (e.g. "Won a public
+  tender last month; no logged contact since the 2024 quote \u2014 strong re-open
+  angle"). Then one suggested outreach angle tied to that signal. This
+  synthesis is the payload of the whole tool \u2014 always include it when there is
+  at least one hot signal.
+`;
 var leadbay_account_status = `## WHEN TO USE
 
 Trigger phrases: "what's my account status", "how much quota do I have", "what lens am I on", "I topped up / I bought credits / I added credits".
@@ -6246,10 +6393,13 @@ Examples that should NOT invoke this tool (sound similar, route elsewhere):
 
 ## RENDER (quick)
 
-Compact markdown: org name + admin badge on line 1; active lens on
-line 2; per-window quota usage as \`(used / cap)\` chips for
-llm_completion \xB7 ai_rescore \xB7 web_fetch. Surface regeneration flag
-prominently if mid-regen.
+If \`quota_error\` is set the call FAILED \u2014 quota unreadable; on 401/403 tell
+the user to reconnect. NEVER report zero usage or "no limits". Else render
+\`quota.org.resources\` (usage lives there, NOT at quota.resources) as a
+table, never prose: rows = resources (llm_completion \xB7 ai_rescore \xB7
+web_fetch + others), cols = Daily/Weekly/Monthly used \`count\` (= amount
+USED; no cap field, \`plan\` may be null \u2014 never invent a denominator).
+Empty = a 0 table, not "unlimited". Above: org + admin, lens.
 
 ---
 
@@ -6436,6 +6586,10 @@ var leadbay_bulk_enrich_status = `Check status + per-lead contacts for a bulk en
 WHEN TO USE: poll this after leadbay_enrich_titles returns a \`bulk_id\`. Default \`include_contacts=false\` for cheap status polls; set \`include_contacts=true\` once \`all_done\` flips for the final read.
 
 WHEN NOT TO USE: as a substitute for leadbay_research_lead_by_id \u2014 that already includes enriched contacts for a single lead.
+
+## CREDIT COST \u2014 show the balance, discreetly
+
+Once \`all_done\` is true the result carries \`credits_remaining\` (the post-spend AI-credit balance). Don't make a fuss \u2014 no sentence, no callout. Just append ONE small italic line in parentheses at the very END of your reply: \`_(N credits remaining)_\`. If \`credits_remaining\` is null (billing unavailable), omit the line \u2014 don't print 0. Do NOT report a "credits used" figure for this run: the per-contact cost can't be scoped to this specific enrichment (a lead's contact list mixes in earlier runs), so any "X used" number would be misleading.
 `;
 var leadbay_bulk_qualify_leads = `Pick the next N unqualified leads in the active lens and qualify them (run AI rescore + web fetch). Pass \`wait_for_completion:false\` to return quickly with \`{status:'running', qualify_id}\`; poll leadbay_qualify_status with that id. With \`wait_for_completion\` omitted/true, the legacy behavior polls until the answers are populated or a budget is exhausted. Already-qualified leads (those with a non-null \`ai_agent_lead_score\`) are silently no-ops on the backend, so this composite paginates past them to find fresh candidates. On 429 mid-fanout, stops launching but keeps polling already-launched leads.
 
@@ -6900,6 +7054,10 @@ WHEN TO USE: when you have a specific \`contact_id\` (from leadbay_get_contacts)
 
 WHEN NOT TO USE: for bulk enrichment by job title across many leads \u2014 use leadbay_enrich_titles, which handles the selection lifecycle and returns a clean preview/launch flow.
 
+## CREDIT COST \u2014 discreet
+
+This is a paid call. The result returns \`credits_remaining\` (billing.ai_credits, read before the spend). Don't make a fuss about credits: only flag the balance if it's low (e.g. \u2264 a few credits) so the user can decide. Otherwise append it quietly as a small italic parenthetical at the END of your reply \u2014 \`_(N credits remaining)_\`. Don't quote an exact per-contact cost (the rate is backend-only). The actual per-contact cost (enrichment.credits_used) appears on the contact via leadbay_get_contacts after enrichment. If \`credits_remaining\` is null, omit the line \u2014 don't assume zero.
+
 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\`.
 `;
 var leadbay_enrich_titles = `Order contact enrichments by job title across many leads. Contacts are NOT returned by default with a lead (Leadbay keeps enrichment out-of-band to control cost); the agent requests them on demand via this tool when it's ready to actually reach out. Two modes: (A) NO \`titles\` param \u2014 returns the available titles + Leadbay's \`title_suggestions\` + \`auto_included_titles\` + a count of enrichable contacts, so the agent can ask the user which titles to enrich. (B) \`titles\` given \u2014 calls preview, then launches if there's anything enrichable. On 429 returns \`{status:'quota_exceeded'}\` cleanly. Selection lifecycle is wrapped in a try/finally so the user's selection is left clean even on error.
@@ -6908,6 +7066,35 @@ WHEN TO USE: as the agent's go-to enrichment entry point, immediately before pro
 
 WHEN NOT TO USE: to enrich a single contact \u2014 that's leadbay_enrich_contacts (granular). Speculatively, before the user has committed to outreaching \u2014 enrichment spends credits.
 
+## CREDIT COST \u2014 make spend visible
+
+Enrichment is the main PAID operation. Surface cost both before and after.
+
+**BEFORE (confirm before launching).** The discover / preview_only / dry_run modes return \`credits_remaining\` (the balance) and \`enrichable_contacts\` (the volume that would be enriched). Tell the user plainly: **"You have {credits_remaining} credits. This will enrich {enrichable_contacts} contacts."** then ask them to confirm before you launch the paid run. Route that confirmation through \`ask_user_input_v0\` ("Enrich {enrichable_contacts} contacts now?" \u2192 ["Yes, enrich", "No, cancel"]). Do NOT state an exact estimated cost \u2014 the per-contact credit rate lives backend-side and is not in the preview; show the balance and the count, never a fabricated "will cost N credits". If \`credits_remaining\` is null, billing is unavailable \u2014 say the balance is unknown, don't assume zero or unlimited.
+
+**AFTER (show the balance, discreetly).** Once the job finishes \u2014 poll \`leadbay_bulk_enrich_status\`, which returns \`credits_remaining\` (the post-spend balance). Don't make a fuss: append ONE small italic line in parentheses at the very END of your reply \u2014 \`_(N credits remaining)_\`. Omit it if \`credits_remaining\` is null. Do NOT report a "credits used" figure: per-run cost can't be scoped reliably (a lead's contacts mix earlier enrichments), so only the balance is shown.
+
+## 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\` (Claude) | Result has \u22652 leads with \`location.city\` set, and the user's intent is geographic / "in person" / travel | \`{name: lead.company_name, address: "<city>, <country>", place_id: lead.location.place_id ?? omit, notes: <one-sentence pitch>}\` per location |
+| \`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) | The tool's NEXT STEPS block has 2\u20134 mutually-exclusive next moves and the user hasn't already chosen | \`{questions: [{question: "What next?", type: "single_select", options: [<2-4 short button labels>]}]}\`; max 3 questions per call |
+
+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.
+
+**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.
+
+
 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\`.
 `;
 var leadbay_extend_lens = `## WHEN TO USE
@@ -9675,10 +9862,36 @@ var getQuota = {
   outputSchema: {
     type: "object",
     properties: {
-      plan: { type: ["string", "null"], description: "Org plan tier (e.g., FREE, PRO)." },
+      plan: {
+        type: ["string", "null"],
+        description: "Org plan tier (e.g., FREE, TIER1, TIER2). May be null."
+      },
+      org: {
+        type: "object",
+        description: "Org-level quota state.",
+        properties: {
+          spend: { type: "array", description: "Reserved; empty in practice.", items: { type: "object" } },
+          resources: {
+            type: "array",
+            description: "Per-resource per-window USAGE. Each: {resource_type, count, window_type, resets_at}. `count` is the amount USED in that window (not remaining, not a cap). No cap field is returned by the API.",
+            items: { type: "object" }
+          }
+        }
+      },
+      user: {
+        type: "object",
+        description: "User-level quota state, same shape as `org`. May be absent.",
+        properties: {
+          spend: { type: "array", items: { type: "object" } },
+          resources: { type: "array", items: { type: "object" } }
+        }
+      },
+      // Legacy/compat: the live API does NOT return a top-level `windows`
+      // array — usage lives in org/user.resources[]. Declared only so older
+      // recorded fixtures still conform; do not rely on it.
       windows: {
         type: "array",
-        description: "Per-resource per-window limits. Each: {resource, window, current_units, max_units, resets_at}.",
+        description: "Deprecated \u2014 not returned by the live API. Use org/user.resources[].",
         items: { type: "object" }
       }
     }
@@ -15317,6 +15530,78 @@ var researchLeadByNameFuzzy = {
   }
 };
 
+// ../core/dist/composite/account-history.js
+var accountHistory = {
+  name: "leadbay_account_history",
+  annotations: {
+    title: "One account's full back-story",
+    readOnlyHint: true,
+    destructiveHint: false,
+    idempotentHint: true,
+    openWorldHint: true
+  },
+  description: leadbay_account_history,
+  inputSchema: {
+    type: "object",
+    properties: {
+      leadId: { type: "string", description: "Lead UUID (required)" },
+      activityCount: {
+        type: "number",
+        description: "Number of activity-timeline entries to return, max 100 (default: 50)."
+      },
+      lensId: {
+        type: "number",
+        description: "Lens id the lead came from (escape hatch \u2014 normally omit; defaults to the active lens). Pass it when researching a lead from a lens other than the current default, so the underlying /lenses/{lensId}/leads/{leadId} fetch doesn't 404 after the active lens changed."
+      }
+    },
+    required: ["leadId"],
+    additionalProperties: false
+  },
+  execute: async (client, params, ctx) => {
+    const leadId = params.leadId;
+    const count = Math.max(1, Math.min(Math.floor(params.activityCount ?? 50), 100));
+    const [research, notes, activities] = await Promise.all([
+      researchLeadById.execute(client, { leadId, lensId: params.lensId, response_format: "json" }, ctx),
+      client.request("GET", `/leads/${leadId}/notes`).catch(() => []),
+      client.request("GET", `/leads/${leadId}/activities?count=${count}`).catch(() => ({ items: [], pagination: { total: 0 } }))
+    ]);
+    const r = research;
+    const noteList = Array.isArray(notes) ? notes : [];
+    const activityItems = Array.isArray(activities?.items) ? activities.items : [];
+    return {
+      lead: {
+        id: r.firmographics?.id ?? leadId,
+        name: r.firmographics?.name ?? null
+      },
+      // Current state — signals, firmographics, qualification, contacts,
+      // engagement: passed through verbatim from research_lead_by_id so the
+      // agent gets the live "why is this account hot NOW" picture.
+      signals: r.signals ?? null,
+      firmographics: r.firmographics ?? null,
+      qualification: r.qualification ?? [],
+      contacts: r.contacts ?? null,
+      engagement: r.engagement ?? null,
+      // Historical context — the part research only counts/summarizes.
+      notes: noteList,
+      activities: {
+        activities: activityItems.map((a) => ({ type: a.type, date: a.date })),
+        total: activities?.pagination?.total ?? 0
+      },
+      // Preserve research's pass-through metadata (agent_memory summary,
+      // lens_id, web_fetch_in_progress, has_reachable_contact, …) — the
+      // generated description advertises the memory protocol, so dropping
+      // _meta.agent_memory would make history narratives miss stored
+      // preferences. Spread research _meta first, then layer our counts.
+      _meta: {
+        ...r._meta ?? {},
+        region: client.region,
+        notes_count: noteList.length,
+        activities_returned: activityItems.length
+      }
+    };
+  }
+};
+
 // ../core/dist/composite/recall-ordered-titles.js
 var recallOrderedTitles = {
   name: "leadbay_recall_ordered_titles",
@@ -15484,7 +15769,16 @@ var accountStatus = {
       },
       quota: {
         type: ["object", "null"],
-        description: "Per-resource quota state (llm_completion, ai_rescore, web_fetch, LENS_EXTRA_REFILL) across daily/weekly/monthly windows. Null if /quota_status failed (logged in stderr). Pre-check the LENS_EXTRA_REFILL entry before calling leadbay_extend_lens."
+        description: "Per-resource quota state (llm_completion, ai_rescore, web_fetch, LENS_EXTRA_REFILL) across daily/weekly/monthly windows. Null if /quota_status failed (see quota_error) or genuinely returned nothing. Pre-check the LENS_EXTRA_REFILL entry before calling leadbay_extend_lens."
+      },
+      quota_error: {
+        type: ["object", "null"],
+        description: "Non-null ONLY when the quota_status call FAILED \u2014 {code, http_status, message}. A 401/403 means the token lacks quota scope: tell the user to reconnect / re-run OAuth. Treat as 'quota unreadable', NEVER as zero usage or 'no limits'.",
+        properties: {
+          code: { type: "string" },
+          http_status: { type: ["number", "null"] },
+          message: { type: "string" }
+        }
       },
       notifications: {
         type: "array",
@@ -15525,9 +15819,15 @@ var accountStatus = {
   execute: async (client, _params, ctx) => {
     const me = await client.resolveMe();
     let quota = null;
+    let quota_error = null;
     try {
       quota = await client.request("GET", `/organizations/${me.organization.id}/quota_status`);
     } catch (err) {
+      quota_error = {
+        code: err?.code ?? "QUOTA_STATUS_FAILED",
+        http_status: err?._meta?.http_status ?? null,
+        message: err?.message ?? "quota_status request failed"
+      };
       ctx?.logger?.warn?.(`account_status: quota_status failed: ${err?.message ?? err?.code ?? err}`);
     }
     return withAgentMemoryMeta(client, {
@@ -15557,6 +15857,9 @@ var accountStatus = {
       // Empty array when the WS listener isn't wired (OpenClaw, tests) OR
       // when nothing has completed since the last ack.
       notifications: ctx?.notificationsInbox?.list() ?? [],
+      // Non-null ONLY when the quota_status call failed. The agent must treat
+      // this as "could not read quota" (reauth on 401/403) — NOT as zero usage.
+      quota_error,
       _meta: {
         region: client.region
       }
@@ -17279,6 +17582,16 @@ var qualifyStatus = {
   }
 };
 
+// ../core/dist/composite/_credits-helpers.js
+async function readCreditsRemaining(client, force = false) {
+  try {
+    const me = await client.resolveMe(force);
+    return me.organization.billing?.ai_credits ?? null;
+  } catch {
+    return null;
+  }
+}
+
 // ../core/dist/composite/enrich-titles.js
 var DEFAULT_CANDIDATE_COUNT = 25;
 var enrichTitles = {
@@ -17362,6 +17675,10 @@ var enrichTitles = {
         type: "number",
         description: "Count of enrichable contacts at preview time."
       },
+      credits_remaining: {
+        type: ["number", "null"],
+        description: "AI-credit balance BEFORE launching (billing.ai_credits). Present in discover / preview_only / dry_run modes. Pair with enrichable_contacts to tell the user 'you have N credits, this will enrich M contacts' \u2014 do NOT estimate an exact cost (the per-contact rate is backend-only). Null = billing unavailable."
+      },
       selected_lead_count: {
         type: "number",
         description: "How many leads the selection covers."
@@ -17485,6 +17802,10 @@ var enrichTitles = {
             previously_enriched: previouslyEnriched,
             enrichable_contacts: enrichableContacts,
             selected_lead_count: leadIds.length,
+            // BEFORE: show balance + volume. We can't estimate exact cost
+            // (the per-contact rate is backend-only), so surface the balance
+            // and the count, not a fabricated "will cost N".
+            credits_remaining: await readCreditsRemaining(client),
             next_action: "Pick titles to enrich and call leadbay_enrich_titles again with titles=[...]"
           };
         }
@@ -17507,7 +17828,8 @@ var enrichTitles = {
             preview,
             launched: false,
             message: "No enrichable contacts for the chosen titles. Try other titles from available_titles or recommendations.",
-            available_titles: availableTitles
+            available_titles: availableTitles,
+            credits_remaining: await readCreditsRemaining(client)
           };
         }
         if (params.dry_run) {
@@ -17515,7 +17837,12 @@ var enrichTitles = {
             mode: "dry_run",
             preview,
             launched: false,
-            would_launch: { titles: params.titles, email, phone }
+            would_launch: { titles: params.titles, email, phone },
+            // BEFORE confirmation gate: balance + how many contacts WOULD be
+            // enriched. enrichable_contacts is the volume; credits_remaining
+            // the balance. No estimated cost — that rate is backend-only.
+            enrichable_contacts: preview.enrichable_contacts,
+            credits_remaining: await readCreditsRemaining(client)
           };
         }
         const tracker = ctx?.bulkTracker;
@@ -17723,6 +18050,10 @@ var bulkEnrichStatus = {
         type: "boolean",
         description: "True when overall_progress.done === total AND no partial_failures."
       },
+      credits_remaining: {
+        type: ["number", "null"],
+        description: "AI-credit balance re-read after the spend (force-refreshed /users/me \u2192 billing.ai_credits). Present only when all_done. Null = billing unavailable (don't read as zero). NOTE: a per-run 'credits used' figure is intentionally NOT returned \u2014 getContacts can't scope cost to this bulk, so any sum would conflate historical enrichments."
+      },
       partial_failures: {
         type: "array",
         description: "Per-lead errors observed during contacts fan-out (omitted when no failures).",
@@ -17829,6 +18160,7 @@ var bulkEnrichStatus = {
           leads2 = record.lead_ids.map((id) => ({ lead_id: id }));
         }
         ctx?.logger?.info?.(`bulk.status_checked_via_notification bulk_id=${record.bulk_id} notification_id=${notifId} done=${bp.success_count}/${bp.total_count} in_progress=${inProgress} wall_ms=${Date.now() - startMs}`);
+        const creditsRemaining2 = !inProgress ? await readCreditsRemaining(client, true) : null;
         return {
           bulk_id: record.bulk_id,
           notification_id: notifId,
@@ -17848,6 +18180,7 @@ var bulkEnrichStatus = {
           bulk_progress: bp,
           in_progress: inProgress,
           all_done: !inProgress,
+          ...!inProgress ? { credits_remaining: creditsRemaining2 } : {},
           ...bp.quota_hit_count > 0 ? {
             quota_hit_hint: "Some contacts could not be enriched because the AI-credits quota was hit. Top up via leadbay_create_topup_link or wait for the window reset."
           } : {}
@@ -17920,6 +18253,10 @@ var bulkEnrichStatus = {
     };
     const allDone = totalAll > 0 && totalDone === totalAll && partialFailures.length === 0;
     ctx?.logger?.info?.(`bulk.status_checked bulk_id=${record.bulk_id} done=${totalDone} total=${totalAll} wall_ms=${Date.now() - startMs}`);
+    let creditsRemaining = null;
+    if (allDone) {
+      creditsRemaining = await readCreditsRemaining(client, true);
+    }
     return {
       bulk_id: record.bulk_id,
       launched_at: record.launched_at,
@@ -17932,6 +18269,7 @@ var bulkEnrichStatus = {
       leads,
       overall_progress: overallProgress,
       all_done: allDone,
+      ...allDone ? { credits_remaining: creditsRemaining } : {},
       ...partialFailures.length > 0 ? { partial_failures: partialFailures } : {}
     };
   }
@@ -19616,6 +19954,13 @@ var compositeReadTools = [
   campaignCallSheet,
   researchLeadById,
   researchLeadByNameFuzzy,
+  // accountHistory layers FULL notes + activity timeline on top of research
+  // so the agent can write the US4 "why has this dormant account resurfaced"
+  // narrative in ONE call. ALWAYS exposed (compositeReadTools) — the underlying
+  // get_lead_notes / get_lead_activities are ADVANCED-gated, but the
+  // reprioritize-a-neglected-account workflow (#3630 GAP C) must work in a
+  // default deployment without LEADBAY_MCP_ADVANCED=1.
+  accountHistory,
   recallOrderedTitles,
   accountStatus,
   bulkEnrichStatus,
@@ -20909,7 +21254,7 @@ function parseWriteEnv(env = process.env) {
 }
 
 // src/http-server.ts
-var VERSION = true ? "0.18.0" : "0.0.0-dev";
+var VERSION = true ? "0.18.1" : "0.0.0-dev";
 var PORT = Number(process.env.PORT ?? 8080);
 var HOST = process.env.HOST ?? "0.0.0.0";
 var sseSessions = /* @__PURE__ */ new Map();

package/dist/installer-electron.js

@@ -1466,7 +1466,7 @@ var init_installer_gui = __esm({
     init_install_dxt();
     init_install_shared();
     init_oauth();
-    VERSION = "0.18.0";
+    VERSION = "0.18.1";
     PORT = Number(process.env.LEADBAY_INSTALLER_PORT ?? 0);
     sessions = /* @__PURE__ */ new Map();
     OAUTH_BASE_URLS = {

package/dist/installer-gui.js

@@ -873,7 +873,7 @@ async function oauthLogin(opts) {
 }
 
 // installer/installer-gui.ts
-var VERSION = "0.18.0";
+var VERSION = "0.18.1";
 var PORT = Number(process.env.LEADBAY_INSTALLER_PORT ?? 0);
 var sessions = /* @__PURE__ */ new Map();
 var OAUTH_BASE_URLS = {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@leadbay/mcp",
-  "version": "0.18.0",
+  "version": "0.18.1",
   "mcpName": "io.github.leadbay/leadbay-mcp",
   "description": "Model Context Protocol (MCP) server for Leadbay — AI lead discovery, qualification, and enrichment for Claude Desktop, Cursor, and Claude Code.",
   "type": "module",