docs(mcp): fix page-bridge examples to match the real API - #351

Summary

The MCP guide's page-bridge examples document an API that does not exist:

// ❌ what the guide showed
const bridge = createAskableMcpPageBridge(ctx, { resourceUri: 'askable://current', name: '…' });
bridge.destroy();
bridge.promptContext();
bridge.contextPacket();

The real API (verified against packages/mcp/src/index.ts) takes a single options object with a provider and returns { dispose() } — there is no resourceUri/name option and no destroy()/promptContext()/contextPacket() method.

Fix

// ✅ corrected
const bridge = createAskableMcpPageBridge({
  provider: createAskableMcpContextProvider(ctx),
});
bridge.dispose();

• Fixed both the Browser-local page bridge example and the React example with page bridge.
• Replaced the bogus "prompt-ready vs structured" bridge.promptContext()/contextPacket() snippet with an accurate table of how the companion selects output via the request type (get_current_context / format_context_for_prompt / read_current_resource).
• Mentioned the requireRedacted option.

Docs-only; no code changes.

Test plan

• vitepress build clean (no dead links)
• swept site/docs/ — no remaining references to the non-existent API in source
• CI preview/build green

🤖 Generated with Claude Code

Generated by Claude Code