Enable Cloud Sync on a local Workspace

[bholmesdev]

What to build

Add an action on an existing local-only Workspace that accepts a Convex deployment URL, creates/links the Convex workspace, persists the sync linkage in config, and backfills an initial push of all local files and assets. Afterwards the Workspace syncs.

Acceptance criteria

• Supplying a Convex URL links/creates the Convex workspace and persists linkage in config
• All existing local files + assets are pushed on enable
• Subsequent edits sync; the previously local-only Workspace now appears on web

Blocked by

• Create a local-only Workspace (no Convex) #36

[bholmesdev]

Automated Oz implementation started for #39. Oz follow-along link not available yet.

[bholmesdev]

I found the existing CLI Cloud Sync connect/create flow in packages/cli/src/index.ts and the shared sync engine already handles pushing local files/assets. I am wiring connect/create to run that initial sync immediately after writing the workspace linkage.

[bholmesdev]

Opened PR: #132

Implemented:

• hubble cloud create and hubble cloud connect now run an initial sync after writing the Cloud Sync linkage
• local files/assets are backfilled through the existing sync engine immediately
• command help and changelog updated

Validation:

• pnpm --filter @hubble.md/cli... build
• pnpm exec biome check packages/cli/src/index.ts CHANGELOG.md
• pnpm check
• pnpm build:desktop
• CLI help smoke with built packages/cli/dist/index.js

Notes:

• No desktop UI e2e needed; this is CLI Cloud Sync behavior.
• pnpm --filter @hubble.md/cli build alone still fails because workspace deps are not built first; dependency-inclusive @hubble.md/cli... passes.
• Build logs include the existing apps/web Node 22.x engine warning under Node v24.14.0.

[bholmesdev]

Closing as stale while Cloud Sync is redesigned from first principles. We’ll open new, scoped issues from the new plan.