@flopod/cli

The Flopod engine + host package. Despite the cli name, it ships two things on top of one shared core:

• Core (library) — src/flopod.ts exports openFlopod() → a FlopodHandle (compile, run, resume, cancel, signal, observe, …). This is the reusable operations layer: compile() runs in-process via @flopod/compiler; anything that executes a workflow spawns it as a child process (the "spawn model"). It has no argv parsing and no HTTP — pure operations. src/lib.ts is its public library surface (the package exports), consumed by the @flopod/ui web server — the single ui → cli edge.
• CLI — src/commands/* parse argv and call into the handle (flopod run, flopod compile, flopod build, flopod deploy, …).

The web server no longer lives here — it moved into @flopod/ui (src/server/, the flopod-serve bin), which imports this package's engine as a library. This CLI no longer depends on @flopod/ui.

Dependency direction is one-way: commands/* → flopod.ts → @flopod/compiler, @flopod/runtime. The CLI is a thin consumer; the core never imports it. A cosmetic follow-up would rename this package to @flopod/core (CLI as its bin) so the ui → cli import reads as a library edge.