Testing

Testing

npm test     # node scripts/validate-skill.mjs

scripts/validate-skill.mjs runs, in order:

1. SKILL.md frontmatter (only name, description) and directory name for html-prototype-build.
2. Every relative Markdown link and heading anchor in the skill, examples/, root READMEs and docs/.
3. Syntax check of browser scripts (VM compile; sketch ESM via node --check; vendor skipped).
4. validate-pack.mjs on each pack in .html-prototype/packs/.
5. generate-registry.mjs --check for registry.json and ui/pack-registry.fallback.json at the pinned defaultRef.
6. node:test suites:

Area	Files
Pack scripts	tests/scripts/: resolve-pack, install-pack, pack-install-ref, schema-versions
End-to-end	tests/e2e/: pack-publish, pack-install, pack-validate, pack-resolve
Packs	tests/packs/admin-desktop/charts.test.mjs
Runtime	tests/runtime/index.test.mjs (aggregates author/, client/, server/, cli/ tests)
Contracts	tests/contracts/runtime.test.mjs
Example	tests/examples/minimal-notes-system/prototype.test.mjs

Fixtures: tests/fixtures/{pack-root/mini-pack,chart-pack}; helpers in tests/helpers/.

There is no GitHub Actions workflow in the repo; run npm test locally before submitting (per CONTRIBUTING).