fix(meetings): preserve   entities in meeting notes rendering

[superterran]

Summary

Two bugs fixed in the meetings rendering pipeline:

1.   entities show as literal text

• renderMarkdown() calls escapeHtml() which converts & → &, turning   in raw markdown into the literal text   on the website
• Fix: convert   → U+00A0 (non-breaking space character) before HTML escaping so it survives the pipeline

2. June 2026 meeting (and others) returns 404

• Zoom UUIDs can contain / (a base64 character). The frontend builds /api/meetings/${id} without URL-encoding, so a UUID like 8BxNGkCyRPeBVxvMc/8qjA== becomes /api/meetings/8BxNGkCyRPeBVxvMc/8qjA== — Hono sees a two-segment path, not a single ID, and returns 404
• Fix: encodeURIComponent(id) in meetings-api.js before putting the ID in the URL path

Content fix already shipped:   entities in the July 10 notes were replaced with regular spaces directly on meetings-service main.

Test plan

• View the July 10 open meeting — indentation should render as spaces, not   text
• View the June 5 open meeting — page should now load and show notes
• Spot-check a few other meetings to confirm no regressions
• No screenshots needed — content rendering changes only

🔥 Ember