mesh: restore folder preservation in catalog gossip + Pull

[mrjeeves]

Yes, folders used to transfer — two regressions

The user reported "didn't folders used to transfer over [in the sidebar]?". Confirmed: two related drops from the daemon migration.

1. Sidebar peer view: flat instead of folder-tree

The legacy mesh-client.svelte.ts::refreshLocalCatalog shipped path on every CatalogEntry. Receivers' src/ui/Sidebar.svelte::buildRemoteTree (still in place, unchanged) reads e.path and groups peer conversations into nested RemoteNodes — that's how the user's Work/Projects/Q4 planning on the source rendered as a folder tree on every other device.

mesh-gossip.ts::snapshotLocalCatalog shipped in PR #203 dropped the field on the map:

return conversations.map((c) => ({
  guid: c.id,
  title: c.title,
  mode: c.mode,
  updated_at: c.updated_at,
})) as CatalogEntry[];                  // ← no path

Every receiver saw every remote conversation at root. A peer's Work/Projects/Q4 planning showed up as a flat Q4 planning row alongside top-level conversations — visually indistinguishable from a root-level chat.

Fix: thread c.path through the snapshot's map. Empty (root) omitted from the wire payload via spread-only-when-truthy, matching the legacy || undefined shape.

2. Pull lands conversations at root regardless of source

pullConversation was calling saveConversation(conversation) with no targetFolder arg. The Conversation JSON the source returns doesn't carry path (filesystem fact, not conversation content), so the receiver had no way to know where on the source the conversation lived → every Pull flattened to root.

Push (moveConversation) was already correct: it looks up c.path from the local listing and ships it as move_take.source_folder, which handleMoveTake forwards into saveConversation(conversation, source_folder). The Pull path was the missing half.

Fix: pullConversation looks the source folder up from the cached catalog of the source peer (now that the catalog carries path again — both fixes need each other). Passes it as the second arg to saveConversation, which calls pathFor → mkdir({ recursive: true }) to create intermediate folders. Falls back to root when the catalog hasn't caught up.

MoveClient gains a read-only peers accessor (with the minimum shape needed for the lookup: device_pubkey, peer_id, catalog[].guid, catalog[].path).

Validation

• pnpm run check: 164 files, 0 errors, 0 warnings.
• pnpm run build: clean.
• Sidebar tree on peer view: A has Work/Q4 planning; B's sidebar Network section nests Work as a folder containing Q4 planning (was a flat row before).
• Push folder preservation: push Foo/Bar/baz from A to B → arrives at Foo/Bar/baz on B (already worked, sanity check).
• Pull folder preservation: pull Foo/Bar/baz from A → arrives at Foo/Bar/baz locally (was landing at root before).
• Pull when catalog hasn't caught up (e.g. mid-handshake pull): conversation lands at root rather than erroring out. Cosmetic only; the next catalog announce + manual move will resolve.

https://claude.ai/code/session_01RLu1LdTgtxEDdzhybzqFrk

---

Generated by Claude Code