Merge pull request #171 from leadbay/ArtyETH06/fix-claude-submission

fix(mcp): make friction reporting consent-gated and visible

Author: ArtyETH06

CHANGELOG.md

@@ -1,5 +1,22 @@
 # Changelog
 
+## 0.27.0 — 2026-07-31 — Consent-gated problem reporting
+
+- **`leadbay_report_friction` now asks before it reports.** Previously the agent
+  was instructed to fire it silently and never let you know it existed. It now
+  only runs when you ask for a problem to be reported — or when you accept an
+  offer — and it always tells you the outcome.
+- **Your words, not the agent's.** The report is the message you approved. The
+  agent-authored free-text field is gone, `tool_called` is restricted to real
+  tool names, and the verbatim prompt slice (`_triggered_by`) is no longer
+  attached to this tool's analytics.
+- **Honest confirmations.** If the report can't be delivered (telemetry off or
+  unavailable), the tool says so instead of claiming it reached the team.
+- **Venting is not consent.** Frustration alone never triggers a report through
+  any tool — the agent keeps solving what you actually asked for, and may offer.
+- Registry listing now carries a real icon, and the `@leadbay/mcp` npx pin
+  tracks the current version line again.
+
 ## 0.26.0 — 2026-07-29 — Autonomous, target-sized `leadbay_build_campaign`
 
 - `leadbay_build_campaign` now runs **end-to-end without pausing** and builds to

README.md

@@ -242,7 +242,7 @@ These never modify your account, so they're always safe to allow.
 | `leadbay_create_topup_link` | Generate a Stripe top-up link (you pay in your browser — nothing is charged automatically) |
 | `leadbay_open_billing_portal` | Open the billing portal |
 | `leadbay_acknowledge_notification` | Clear a terminal bulk-job notification so it stops resurfacing |
-| `leadbay_report_friction` | Report when a tool didn't deliver — helps improve the product (no account change) |
+| `leadbay_report_friction` | Report a problem to the Leadbay team — asks you first, and shows you what was sent (no account change) |
 | `leadbay_artifact_kit` | Fetch the headless view-models the agent uses to build an interactive HTML artifact |
 
 ### Write actions (on by default since 0.3.0; set `LEADBAY_MCP_WRITE=0` to disable)

WORKFLOWS.md

@@ -57,6 +57,8 @@ The table is the human-readable index. The `yaml expected` + `yaml scenario` blo
 | 43 | **Enrichment stays active until done (no reprompt)** — the core of product#3866: after the user authorizes a paid enrichment, the agent launches via `leadbay_enrich_titles` (which returns `mode:"launched"` immediately — the job runs async), then STAYS ACTIVE in the same turn: it polls `leadbay_bulk_enrich_status` in a loop until done (`all_done`, or the resolvable set plateaus), and reports the completed enrichment (which contacts got emails/phones, counts, refreshed quota via `leadbay_account_status`) on its own — WITHOUT the user having to ask "is it done yet?". Distinct from Workflow 34 (multi-turn campaign builder, where the user *explicitly* says "wait for enrichment to finish" in turn 3); here it is a SINGLE turn and the stay-active behavior must be automatic. | `leadbay_enrich_titles` | "Pull my current leads and enrich their emails — get me the results in this same reply" |
 | 44 | **Pull leads offers "Enrich top leads"** — product#3875: after a `leadbay_pull_leads` on a non-empty batch, the deterministic `next_steps` surfaces an **Enrich top leads** option at position 2 (right after the Triage-board artifact offer) so the discovery→outreach bridge is one click away. It routes to `leadbay_enrich_titles` via the NO-SPEND preview path — previews volume + channels first, spends nothing until the user confirms — so a plain "show me my leads" never triggers an unprompted paid reveal (the #42 consent gate holds). | `leadbay_pull_leads`, `leadbay_enrich_titles` | "Show me my top leads for today" |
 | 45 | **Telemetry enable/disable/status** — product#3879: an in-product control to opt out of / into product-usage telemetry, or check the current setting. `leadbay_set_telemetry` (its `action` argument is `enable`, `disable`, or `status`; default `status`) reads/writes a per-user preference stored on the Leadbay account (`GET /users/me` → `telemetry_enabled`; `POST /users/telemetry`). Telemetry stays ON by default (opt-out). The hosted/web connector honors the flag per-request (a disabled user's events are suppressed). A local/stdio install decides telemetry at startup from `LEADBAY_TELEMETRY_ENABLED` and does not read the account flag, so local opt-out also needs that env var — the tool's copy says so rather than promising local opt-out. | `leadbay_set_telemetry` | "Turn off telemetry — I don't want my usage tracked" |
+| 46 | **Consent-gated problem report** — product#3943: the user explicitly asks for a Leadbay problem to be reported. `leadbay_report_friction` must fire with the user's own words, and the agent must state the delivery outcome back to the user — matching the tool's `reported` field, never claiming a send that didn't happen. The underdeliver guard: an agent that treats the request as ordinary chatter and never reports is failing the user. | `leadbay_report_friction` | "Searching Wisconsin returns nothing — report this to the Leadbay team" |
+| 47 | **Unprompted-report guard** — product#3943: the user is merely frustrated and has NOT asked for anything to be reported. `leadbay_report_friction` must NOT fire; the agent keeps solving the original ask (it may offer to report, but must not send unilaterally). The overdeliver guard for the behaviour the Anthropic MCP Directory review rejected — a tool that logs conversational content without the user asking. | *(none — must not fire)* | "Ugh, this never finds what I'm looking for. Show me today's leads." |
 
 ---
 
@@ -1013,6 +1015,48 @@ success_criteria:
 prompt: "Turn off telemetry — I don't want my usage tracked"
 ```
 
+```yaml expected
+workflow_name: Consent-gated problem report
+prompt_name: ~
+required_calls:
+  - leadbay_report_friction
+forbidden_calls:
+  - leadbay_report_outreach
+success_criteria:
+  - "called leadbay_report_friction after the user explicitly asked for the problem to be reported"
+  - "the reported message reflects the user's own words about the empty Wisconsin search, not an agent-invented complaint"
+  - "visibly told the user the outcome of the report rather than staying silent about it"
+  - "the stated outcome MATCHES the tool's `reported` field — if `reported` is true it may say the report reached the Leadbay team; if `reported` is false it must say it was NOT delivered and must not imply otherwise"
+render_checks:
+  - "the final message states the report's delivery outcome explicitly (either confirmed sent, or clearly not delivered)"
+```
+
+```yaml scenario
+prompt: "Searching Wisconsin returns nothing — report this to the Leadbay team"
+```
+
+```yaml expected
+workflow_name: Unprompted-report guard
+prompt_name: ~
+required_calls:
+  - leadbay_pull_leads
+forbidden_calls:
+  - leadbay_report_friction
+  - leadbay_send_feedback
+  - leadbay_report_outreach
+success_criteria:
+  - "did NOT call leadbay_report_friction — the user expressed frustration but never asked for anything to be reported"
+  - "did NOT call leadbay_send_feedback either — routing the vent to the other delivery tool is the same unprompted send by a different path"
+  - "continued solving the user's actual request (showing today's leads) instead of stopping to log the complaint"
+  - "if it mentioned reporting at all, it OFFERED and waited rather than sending unilaterally"
+render_checks:
+  - must_not_match: "[Ll]ogged|[Rr]eported (the|this|your) (friction|complaint|frustration)|[Ss]ent (the|this|your) (friction|complaint) (report|to the [Ll]eadbay team)"
+```
+
+```yaml scenario
+prompt: "Ugh, this never finds what I'm looking for. Show me today's leads."
+```
+
 ## How this stays normative
 
 `packages/mcp/test/audit/workflows.test.ts` asserts every backtick-wrapped `leadbay_*` identifier resolves to a registered tool or prompt. Proposed names for not-yet-shipped tools go in italics, not backticks.