Use grammy-dialog

Build against the package's single public entrypoint and preserve its MVVM and persistence boundaries. Prefer the high-level, immutable DialogKit DSL over internal factories.

Establish the API version

Treat the library as experimental and verify the installed or checked-out version before coding.

• In this repository, inspect src/index.ts, the relevant public contracts, README.md, and examples/showcase/.
• In a consumer project, inspect the installed declarations for @ppsh/grammy-dialog and its package version.
• Import application APIs only from @ppsh/grammy-dialog; never depend on package internals.
• Retain .js specifiers on relative TypeScript imports when editing this repository.

Choose the resource model

• Use a Dialog for a multi-window workflow with one shared ViewModel, state, and navigation stack.
• Use a standalone Window for an independent surface. Omit its ViewModel when it is static.
• Use a custom widget for reusable UI behavior nested inside windows.
• Export reusable widgets as JSX components; use extensions to package registered dialogs/windows for multiple DialogKits.