Verify

The full command list with what each command proves is in Commands. Run it from the repository root after bun install. On a clean checkout build examples/vue-simple once before the editor typecheck: it prepares the Nuxt UI theme aliases the typecheck needs.

Rules

• After touching a package entry (a new export, a moved import): run bun run check:editor-entries. It builds the editor, makes one production build per fixture and proves the module-graph isolation and the schema snapshot.
• After adding or changing a user-facing string: run bun run check:editor-i18n. It fails on a literal in src outside src/i18n and on a catalog key that is unused or missing in en.
• After renaming or documenting a concept: run bun run check:editor-legacy-names. It fails on a former name of the block vocabulary (the glossary's _Avoid_ terms and the removed API names) in the library sources, the app, the examples and the docs; the migration guide's tables, the glossary's _Avoid_ lines and the changelog may name them.
• After changing defineEditor, a feature's requires or a composition: run bun run check:editor-composition.
• After any type-level change: run bun run typecheck:editor, and the typecheck of the consumer you touched (bun run --cwd examples/vue-simple typecheck, examples/react-simple, examples/react-advanced, or bun run typecheck for the Nuxt demo app).
• After adding a feature: add a fixture folder packages/editor/checks/fixtures/<name>/ and one FIXTURES entry in packages/editor/checks/entries.ts; see Commands and Dependency rules.
• After editing these docs or a source file they quote: run bun run check:docs-snippets (bun run docs:snippets rewrites stale blocks).