How do their APIs compare?

Both repos don't expose "APIs" in a comparable REST/library-SDK sense — they operate at very different layers. Let me clarify what each actually offers based on the retrieved evidence.

tw93/pake — a Rust/Tauri-based CLI tool that wraps webpages into desktop apps. It doesn't have a formal external API; its "interface" is:

• A CLI surface built with commander-style option handling — e.g. [bin/dev.ts:L1-L28] shows the CLI program parsing options via getCliProgram(), then flowing through handleInputOptions → BuilderProvider.create(appOptions) → builder.prepare()/builder.start(url).
• An internal builder abstraction (BaseBuilder.ts, flagged by RepoPilot's import graph as the most-depended-on file with 4 importers), suggesting a plugin/strategy pattern for platform-specific packaging rather than a public API.
• A JS injection layer for the webview itself, e.g. helper functions like isChineseLanguage in [src-tauri/src/inject/event.js:L463-L473] and auth-popup detection in [src-tauri/src/inject/auth.js:L67-L90], which are injected into the wrapped page's runtime and exposed on window (window.isAuthPopup, etc.) — this is the closest thing Pake has to a runtime-facing "API," and it's a browser-side JS surface, not a network/service API.
• Rust-side helpers like reload_window in [src-tauri/src/app/navigation.rs:L8-L14] are internal Tauri command implementations, not public API endpoints.

vadimcn/codelldb — by contrast, has a genuine, formally specified API: the Debug Adapter Protocol (DAP), implemented/extended in [src/adapter-protocol/src/debugAdapterProtocol.json]. This is a JSON Schema-style spec defining:

• Request/Response/Event object shapes (e.g. CancelRequest/CancelResponse at [src/adapter-protocol/src/debugAdapterProtocol.json:L106-L145] and [L159-L180], LaunchRequest/LaunchRequestArguments at [L1016-L1055], SetBreakpointsResponse at [L1296-L1335], BreakpointLocationsRequest/Arguments at [L1191-L1230], ConfigurationDoneRequest at [L981-L1006]).
• Standardized ErrorResponse structure with a Message body [L110-L124].
• Event types like InitializedEvent [L165-L180] and BreakpointEvent [L409-L425], and OutputEvent-style body fields (locationReference, data) [L386-L401].

This is a wire-protocol API meant for consumption by DAP clients (e.g. VS Code), following Microsoft's Debug Adapter Protocol conventions, extended by codelldb for LLDB-specific behavior.

Summary comparison:

• Pake has no formal external API — it's a CLI tool with internal TypeScript builder abstractions and browser-injected JS helper functions.
• codelldb's core interface is an API: a strict, versioned DAP schema governing requests, responses, and events over a structured protocol, used for IDE debugger integration.
• They're not really peer comparables: Pake's "API surface" is closer to CLI options and internal module boundaries (per RepoPilot's import graph showing BaseBuilder.ts, output.ts, error.ts as central hubs), while codelldb's is a formal, documented wire protocol.

If you want, I can dig deeper into either Pake's CLI option handling (bin/options/index, bin/helpers/config-file.ts) or codelldb's Rust-side DAP request handling to see how the protocol schema is actually implemented.

FOLLOW_UPS:

• How does Pake's BuilderProvider pattern work?
• What does codelldb's build.rs do with LLDB symbols?
• How is config validated in bin/helpers/config-file.ts?