fix(tests): carry the runtime's required detail field in status mocks

[jerelvelarde]

A fresh clone of main fails pnpm check-types (exit 2, four errors) and pnpm test (161/162 passing). Both trace to the detail field @copilotkit/channels@0.8.1 added to status(), which the bump in 356b6f6 did not carry into the test doubles.

app/server.test.ts(36,5): error TS2322: Property 'detail' is missing in type
  '{ overall: "online"; channels: { opentag: "online"; }; }' but required in type
  '{ overall: ChannelStatus; channels: Record<string, ChannelStatus>; detail: Record<string, ChannelLegs>; }'

makeControls is the source of all four type errors, so one detail: {} clears them. app/runtime-host.test.ts:55 then needed the real payload the runtime now returns.

Verified on a clean --depth 1 clone: red before (check-types exit 2, 1 failed | 161 passed), check-types exit 0 and 162/162 after.

Kept toEqual rather than relaxing to toMatchObject — its strictness about extra keys is what surfaced this drift, and it is worth keeping for the next one.

Found while verifying a review blocker on CopilotKit/website#467, which recommends cloning this repo as the fast path to a first Channel.

[jerelvelarde]

Context for whoever picks this up: main is currently red, and this is a two-file fix that restores it.

356b6f6 bumped @copilotkit/channels to 0.8.1, which made status() return a required detail field. The repo's own status doubles were not updated with it, so a fresh clone fails pnpm check-types (exit 2) and pnpm test (161/162) before anyone touches anything.

Surfaced while verifying a review blocker on CopilotKit/website#467, which is making a clone of this repo the recommended fast path to a first Channel — so a red main here is the first thing a new user hits.