@leadbay/mcp 0.33.3 → 0.34.0

package/CHANGELOG.md

@@ -1,5 +1,94 @@
 # Changelog — @leadbay/mcp
 
+## 0.34.0 — 2026-09-02
+
+The OpenAI app directory rejects an app that sells digital goods — "plugins may
+conduct commerce only for physical goods. Selling digital products or services
+— including subscriptions, digital content, tokens, or credits — is not
+allowed" — and separately forbids promoting the purchase: a plugin "must not
+display subscription plans, initiate new subscriptions, or promote upgrades" or
+"link directly to a checkout". Signing in to an existing paid account and using
+what it entitles you to IS allowed. Anthropic's Software Directory Policy has
+no equivalent clause; its nearest rule bars software that "executes financial
+transactions on behalf of users", which our Stripe-URL handoff does not do.
+
+`POST /chatgpt/mcp` is the URL submitted to OpenAI. Same Hono app, same auth,
+same handler, built with `includeCommerce: false`. Four things go away
+together — the tools, and every text that would promote buying them, since
+removing only the tools left the agent still pushing a top-up it could no
+longer produce:
+
+- `leadbay_create_topup_link` and `leadbay_open_billing_portal` are not
+  registered (filtered after the catalogue arrays merge — both appear in
+  `compositeReadTools` and `granularReadTools`).
+- Tool descriptions lose their `{{commerce}}` blocks
+  (`NO_COMMERCE_TOOL_DESCRIPTIONS`, emitted by promptforge).
+- The `QUOTA_TOPUP` instruction paragraph is not pushed. `quota-topup.md` was
+  split verbatim: the selling paragraph is gated, and the neutral one that says
+  when to re-render the quota gauge became `quota-refresh.md`, pushed on both.
+- `LeadbayClient.commerce` drops the two selling sentences from the
+  QUOTA_EXCEEDED hint ("OR top up AI credits…", "…or direct them to
+  app.leadbay.ai → Billing"). One client per session on hosted, so the flag
+  cannot leak across tenants.
+
+Nothing is reworded for ChatGPT. `{{commerce}}` only ever DELETES — there is no
+second, softened wording anywhere to drift out of sync, and the Claude surface
+keeps selling exactly as hard as before. Enforced two ways:
+`commerce-gate.test.ts` asserts the gated description and instruction strings
+are pure character-level *subsequences* of the Claude ones (any reworded
+character fails), and the generated descriptions were diffed against `main` to
+confirm the default rendering did not move by a byte.
+
+A path rather than an `initialize` clientInfo sniff, and rather than a query
+parameter: the OAuth protected-resource identifier IS the path
+(`/.well-known/oauth-protected-resource/chatgpt/mcp` → `resource:
+https://mcp.leadbay.app/chatgpt/mcp`). A `?commerce=off` flag would leave both
+URLs advertising the same resource, so a client reconnecting to the audience it
+registered would get the selling tools back. RFC 8707 also says a resource URI
+should carry no query component.
+
+`RESOURCE_PATHS` gains the path so OAuth discovery resolves for it, and the
+installer's ChatGPT Desktop entry now hands out `HOSTED_MCP_URL_CHATGPT`.
+
+## 0.33.4 — 2026-09-02
+
+`leadbay_enrich_contacts` moves from `granularWriteTools` to
+`compositeWriteTools` (product#4050).
+
+It is the only tool that enriches ONE chosen person — `leadId` + `contactId`,
+paid-candidate path first, org-contact path on `NOT_FOUND` — but it sat behind
+`LEADBAY_MCP_ADVANCED=1`, which hosted never sets. No granular tool has been
+called from a hosted IP in 30 days. The daily check-in prompt and the pull-leads
+NEXT STEPS table already told the agent to call it, so on hosted they named a
+tool that was not registered. `zoe+dogfood@leadbay.ai`'s scheduled agent
+reached for `leadbay_pin_contact` instead (41 `contact not found` over 12 days;
+see 0.33.3). Same registration pattern as add/remove/pin/unpin/update_contact
+and set_lead_status: granular-shaped, lives in `tools/`, default write surface,
+still hidden by `LEADBAY_MCP_WRITE=0`. Not in `COMPOSITE_FILE_TOOL_NAMES`, so
+`_triggered_by` stays optional.
+
+What moved with it, so the tool works on the surface it now lands on:
+
+- **The result hint names a read that exists there.** It said "re-check
+  `leadbay_get_contacts`", which is advanced-only. It now says re-read the
+  lead's contacts via `leadbay_research_lead_by_id` (or `get_contacts` where
+  exposed).
+- **The description carries routing.** `routing` + `rendering_hint`
+  frontmatter, added to `TOOLS_WITH_ROUTING`; the `prefer_when` states that a
+  `source:"paid"` candidate id from `research_lead_by_id` is valid input and
+  that pinning does not enrich anyone. Cross-routes to `enrich_titles`
+  (by title, many leads), `pin_contact`, `prepare_outreach`.
+- **The pin/unpin 404 hint and `heuristics/pinnable-contacts` name it** as the
+  direct route alongside `enrich_titles` and `add_contact`. `enrich_titles`'s
+  WHEN NOT TO USE drops the "(granular)" label.
+
+Tests: `packages/mcp/test/enrich-contacts-default-surface.test.ts` drives the
+real MCP `tools/list` — present with `includeWrite:true, includeAdvanced:false`,
+absent with `includeWrite:false`, and every `leadbay_*` the description and
+the call hint name is itself registered on that surface.
+`packages/core/test/unit/tools/pin-contact-hint-names-enrich-contacts.test.ts`
+pins the hint.
+
 ## 0.33.3 — 2026-09-02
 
 `leadbay_pin_contact` failed 43 of its 48 production calls.

package/README.md

@@ -634,7 +634,7 @@ Use `dry_run: true` to validate domain formatting and wizard reachability withou
 
 - Tokens live only in your MCP client's config file — they never traverse the network except to `api-{region}.leadbay.app`.
 - The `leadbay_login` tool from the OpenClaw adapter is **not** registered on MCP: exposing a credential-taking tool to an LLM is a prompt-injection risk. Use the token path above.
-- The `leadbay_add_note` tool is a write action flagged `optional: true`. If your client supports per-tool opt-in, leave it disabled until you need it. `leadbay_enrich_contacts` is a granular tool exposed only when `LEADBAY_MCP_ADVANCED=1`.
+- The `leadbay_add_note` tool is a write action flagged `optional: true`. If your client supports per-tool opt-in, leave it disabled until you need it. `leadbay_enrich_contacts` (enrich one named contact) is on the default write surface since 0.33.4; it was advanced-only before.
 
 ### Privacy & telemetry