fix(auth): mapping table still labels full-archive search Academic-only #507

Summary

The authentication mapping page limits full-archive search to Academic Research access, while the linked search introduction documents access for pay-per-use and Enterprise customers. This gives conflicting eligibility guidance for the same endpoint.

Runtime or environment

Documentation source: current default branch main at 5fcfe3da51461ef1c0b59a028da9c365547cad4c; the repository has no published releases. Fresh live Markdown fetches of both pages preserve the conflicting claims. These are documentation checks; no X API request was made.

Steps to reproduce

1. Read the full-archive search row at https://docs.x.com/fundamentals/authentication/guides/v2-authentication-mapping.
2. Observe its Academic Research restriction for GET /2/tweets/search/all.
3. Follow its search-introduction link and compare the access statement at https://docs.x.com/x-api/posts/search/introduction.

These page fetches and source comparisons were executed.

Expected behavior

The mapping's full-archive eligibility statement should agree with the linked endpoint introduction, which documents access for pay-per-use and Enterprise customers.

Actual behavior

The mapping says "Only available to those with Academic Research access". The search introduction instead identifies pay-per-use and Enterprise customers, both in its overview and its full-archive section. The live pages retain the same disagreement.

Evidence

• Expected source: x-api/posts/search/introduction.mdx, lines 119–125, the full-archive access statement.
• Failure source: fundamentals/authentication/guides/v2-authentication-mapping.mdx, line 21, the Academic-only claim, also present in fresh live Markdown.
• Evidence provenance: observed
• Local verification: reproduced
• Reproduction completeness: complete

Restoration check

Read the full-archive row and follow its introduction link. Both should describe compatible eligibility for GET /2/tweets/search/all; removing the contradictory restriction must preserve the endpoint identity and authentication information.

Triage assessment

• Impact level: P2
• Assessment status: provisional
• Impact basis: Conflicting eligibility guidance can incorrectly discourage supported customers from using full-archive search. No customer exclusion or runtime rejection was tested.
• Workaround status: available
• Workaround basis: Readers can follow the row's introduction link to obtain the documented pay-per-use and Enterprise eligibility.