test(rest): the read-scope boundary double spells routes, not the retired endpoints (#5674)

`analytics-read-scope-refusal-envelope.test.ts` was written from a sibling
analytics test before #5674 landed, so its `getDiscovery` double carried
`endpoints: {}` -- the dispatcher-only copy of `routes` that #4828 retired under
ADR-0049 and that no producer ever emitted. #5674 corrected the 26 existing
doubles and added `discovery-double-retired-key.test.ts` to pin the key out of
the fixture layer; this file arrived after that sweep and reintroduced it.

Corrected to the producer's real shape -- `routes: { data: '', metadata: '' }`,
`ApiRoutesSchema` as `DiscoverySchema` requires it -- matching the three sibling
analytics doubles verbatim. The key was inert here (nothing in this file drives
discovery), which is exactly the reason it kept surviving retirement, so this is
the double being made faithful to its producer rather than a guard being
satisfied.

Author: claude

packages/rest/src/analytics-read-scope-refusal-envelope.test.ts

@@ -71,7 +71,14 @@ function mockServer() {
 }
 function mockProtocol() {
   return {
-    getDiscovery: vi.fn().mockResolvedValue({ version: 'v0', endpoints: {} }),
+    // [#5674] `routes` (ApiRoutesSchema) is what the producer emits and what
+    // `DiscoverySchema` requires. This double was copy-pasted from a sibling
+    // before #5674 landed and spelled `endpoints` — the dispatcher-only copy of
+    // `routes` that #4828 retired under ADR-0049, and which no producer ever
+    // emitted. It was inert here (nothing in this file drives discovery), which
+    // is exactly why the key kept surviving; `discovery-double-retired-key.test.ts`
+    // pins it out of the fixture layer so the next copy-paste cannot regrow it.
+    getDiscovery: vi.fn().mockResolvedValue({ version: 'v0', routes: { data: '', metadata: '' } }),
     getMetaTypes: vi.fn().mockResolvedValue([]),
     getMetaItems: vi.fn().mockResolvedValue([]),
   };