Back to Search-quality baseline: acronym / synonym recall (Phase 1.4, v1.2.0 candidate)

For the AI agent consumer: if the agent issues a bare `NFC` query expecting the CoreNFC framework reference, it gets an authentication-services deep page instead. The agent that grounds on top-1 will be looking at a transport-property documentation page rather than the framework introduction, which gives the agent the wrong context for generating CoreNFC API calls.

However, this is partially mitigated by the way agents typically construct queries: an agent looking for CoreNFC will more likely issue `CoreNFC` or `Core NFC` (the full framework name) rather than `NFC` alone. The canonical-lookup baseline already showed `CoreNFC` likely ranks the framework root at top-1.

The acronym path is more relevant for a HUMAN consumer typing `NFC` interactively. For the agent consumer, the impact is bounded.