chore(ts): drop two more redundant casts

- RouteMapThumbnail.client.tsx: `{ type: 'Feature', ... } as unknown
  as GeoJsonObject` → `as GeoJsonObject`. The literal already
  satisfies the type; the unknown bridge was unnecessary.

- use-yjs.ts:102: keep the coercion (y-websocket's `.on()` signature
  doesn't include the legacy `"synced"` event even though the
  runtime still fires it), but document why with a comment so future
  readers don't try to drop it.

apps/journal/app/components/RouteMapThumbnail.client.tsx

@@ -142,7 +142,7 @@ function DayColoredRoute({ data, dayBreaks, highlightedDay }: { data: GeoJsonObj
           type: "Feature",
           geometry: { type: "LineString", coordinates: seg.coords },
           properties: {},
-        } as unknown as GeoJsonObject;
+        } as GeoJsonObject;
         return (
           <GeoJSON
             key={`${i}-${highlightedDay}`}

apps/planner/app/lib/use-yjs.ts

@@ -99,6 +99,10 @@ export function useYjs(
 
     // Initialize waypoints once after first sync
     if (initialWaypoints?.length && !initializedWaypoints.current) {
+      // y-websocket emits both "sync" and "synced" (legacy alias). We
+      // keep "synced" for backwards-compat with older versions; the
+      // typed `.on` signature in the current lib version omits it
+      // even though the runtime still fires it, so we coerce.
       (provider as unknown as { on(event: string, cb: () => void): void }).on("synced", () => {
         // Only add if the doc is empty (avoid duplicating on reconnect)
         if (waypoints.length === 0 && !initializedWaypoints.current) {