Drop the two Facebook tools Meta refuses, promote what is proven

[fajarhide]

Two of the three tools shipped in #21 cannot answer. Meta refuses both on a live connection where the third works:

facebook returned 400: {"error":{"message":"Permissions error","code":200,"error_subcode":2069030,
"error_user_title":"New Pages Experience Is Not Supported",
"error_user_msg":"This endpoint is not supported in the new Pages experience."}}

Identical for /me/posts and /me/likes, twice each, with the scopes granted and get_me succeeding on the same grant. Both had passed fixtures written from the documentation, which is exactly the gap experimental is meant to mark and exactly why the live run was worth doing.

So they go, and get_me stays and moves to beta:

$ curl -s -X POST localhost:8080/v1/tools/facebook__get_me/call -d '{}'
fields returned: ['id', 'link', 'name']

Real profile, on the real vendor, on 2026-08-17.

The pagination block goes with them. Nothing lists any more, so keeping it would be configuration held for a tool that does not exist. Scopes shrink to public_profile,user_link, which is what the surviving tool needs.

A test now pins the tool list to exactly ['get_me'], because fixtures alone already let these two through once.

One honest caveat, also in #28: the observation is solid and the reason Meta prints is not. The token is plainly a personal user token, since get_me returns a profile id and name, so "New Pages Experience" reads more like a generic refusal for personal timeline reading than a description of this account. What is certain is that both endpoints refuse.

$ npx vitest run
Test Files  36 passed (36)
     Tests  359 passed (359)

Closes #28