What are the migration paths between them?

There are no migration paths between tw93/pake and vadimcn/codelldb — these are two entirely separate projects serving different purposes:

tw93/pake ([README excerpt]):

• A tool to convert webpages into cross-platform desktop applications
• Built with Rust + Tauri, focused on packaging web UIs as standalone apps
• Produces installers for macOS, Windows, and Linux
• CLI-driven, configuration-based workflow

vadimcn/codelldb ([src/codelldb/Cargo.toml]):

• A debugger adapter/IDE plugin for LLDB (Low Level Debugger)
• Built with Rust, designed as a backend debugging service
• Integrates with code editors via the Debug Adapter Protocol
• Handles symbol resolution, process debugging, and debugger communication

Why no migration paths exist:

1. Different problem domains: Pake solves app packaging; CodeLLDB solves debugging
2. Different users: Pake targets web developers wanting desktop apps; CodeLLDB targets IDE users needing native code debugging
3. Different architectures: Pake's pipeline involves Tauri builds and installers [bin/builders/BaseBuilder.ts]; CodeLLDB's involves LLDB symbol management and protocol handlers [src/lldb-stub/build.rs:L20-L69]
4. No shared dependencies or architecture: CodeLLDB has no Tauri or web-packaging dependencies; Pake has no debugger functionality

If you're working with both tools, they'd be used in complementary contexts (e.g., develop a Pake app, then debug native Tauri internals with CodeLLDB), but one doesn't migrate into the other.

FOLLOW_UPS:

• What's the CLI workflow for packaging with Pake?
• How does CodeLLDB integrate with VS Code debugging?
• What are Pake's platform-specific build differences?