supabase / mcp / 42632197371

98%

push

github

feat: agent feedback capabilities including docs (#488)

## What kind of change does this PR introduce?

feature

## What is the current behavior?

- the `submit_feedback` description covers only feedback about supabase
tools, so an agent can decide that a wrong docs page does not belong in
the tool

## What is the new behavior?

- changes the `submit_feedback` description to cover documentation and a
wrong docs page, so an agent can report a docs problem with the tool

## How to Review

<!--
A reviewer should understand what this PR does within 15-30 seconds,
then know where to start reading.

Non-trivial or multi-file PRs must fill in the reading path below.
Trivial single-file changes may delete this section when the review path
is obvious.

- Start from the main public entrypoint or request handler, and follow
the actual execution path before reading tests.
- Use bold numbered areas, each with one or two indented bullets: the
exact files, then what to inspect.
- Use exact repository-relative paths, and avoid line numbers while the
branch is still changing.
- Prefer project-facing language such as `interface`, `extension point`,
or `contract` over internal design jargon.
- Don't repeat the PR purpose or the verification commands here. Keep
the section scannable.
-->

1. **Tool contract**
   - `packages/mcp-server-supabase/src/tools/feedback-tools.ts`
- the first two sentences of the `submit_feedback` description, and the
unchanged rule to ask the user before sending feedback that the user did
not request

**Review questions**

<!-- Four to six short questions covering the reviewer's judgment calls.
-->

- [x] Is the public contract minimal and intentional?
- [x] Do the main execution paths preserve existing behavior?
- [x] Do failures stop safely?
- [x] Do tests protect observable behavior rather than implementation
details?

## Verification

1. run `pnpm test:unit` in `packages/mcp-server-supabase`, and make sure
that all 869 tests pass
2. run `pn... (continued)

1277 of 1324 branches covered (96.45%)

Branch coverage included in aggregate %.

1 of 1 new or added line in 1 file covered. (100.0%)

6105 of 6204 relevant lines covered (98.4%)

278.1 hits per line