wp-typia 0.16.14 → 0.17.0

package/README.md

@@ -5,6 +5,7 @@ Canonical CLI package for `wp-typia`.
 Use this package for new installs:
 
 - `npx wp-typia create my-block`
+- `npx wp-typia create my-books --template query-loop --query-post-type book`
 - `bunx wp-typia create my-block`
 - `npx wp-typia create my-plugin --template @wp-typia/create-workspace-template`
 - `wp-typia add block counter-card --template basic`
@@ -18,9 +19,8 @@ argument.
 Compatibility notes:
 
 - `@wp-typia/project-tools` is the canonical programmatic project orchestration package
-- `@wp-typia/create` is the deprecated legacy package shell
-- `create-wp-typia` is archived and should not be used for new installs
 - the published CLI now ships built `dist-bunli` runtimes, and the canonical Node bin uses a Node-safe fallback runtime for non-TUI `create`/`add`/`migrate`, `doctor`, `sync`, `--version`, `--help`, and template inspection without requiring a locally installed Bun binary
+- when that Node fallback prompts interactively, it intentionally stays lighter than the Bun/OpenTUI flow: numbered lists, option label/value matching, inline validation retries, and redraw commands for the current choices: `?` for the short reprint shortcut, `help` for the explicit redraw command, and `list` for users who expect option listing semantics
 - Bunli-specific command surfaces such as `skills`, `completions`, and `mcp` still run through the built `dist-bunli/cli.js` artifact and require Bun; if you need the full Bunli/OpenTUI runtime story, prefer `bunx wp-typia` or install Bun locally
 - any future `curl`-style installer should reuse the same published `dist-bunli` runtime instead of reintroducing a Bun bootstrap path
 - internal runtime-bridge helper modules are implementation details; integrations