Quality and release checks

Run the repository checks, verify a packed consumer and browser behavior, and review publication boundaries.

Use these checks when contributing to the app, docs, examples, or packages. AGENTS.md states repository conventions. The architecture reference describes the package and session boundary. The dated docs/CODEX-HANDOFF.md in the repository records the original source transfer; it is historical context rather than the current setup guide.

Automated repository checks

Use Node.js 22–24 and pnpm 10.30.3. From the repository root:

pnpm install --frozen-lockfile
pnpm check
pnpm test
pnpm check:examples
pnpm build

check regenerates showcase data and type-checks the site. test exercises the engine, initializer, and project contracts. check:examples validates the example sessions. build prepares showcase data and builds the zfb site. CI runs these commands on pull requests and main with Node.js 24.13.0 and the pinned pnpm version.

When changing session loading, metadata, lineage, exports, or packaging, cover the relevant behavior and error path. Important boundaries include unique stable IDs, relative asset paths contained within a candidate directory, explicit theme assets, and a generated host resolving its installed engine.

Verify a packed consumer

For initializer, dependency, or package-content changes, run pnpm pack:local. Use the printed absolute engine archive path to initialize a new destination outside this repository, then install there, add a valid candidate, and run pnpm check and pnpm build. Also open the valid empty first round.

This check catches imports that work through workspace source links but fail in a real generated host. Keep the archive available at the path recorded in the consumer's dependency until installation is complete.

Inspect in a browser

For viewer changes, open a session at desktop and narrow widths in a real browser. Exercise overview, inspection, comparison, filters, keyboard focus, zoom and pan, placement size, theme availability, backdrop controls, shortlist, chosen direction, and feedback retention. Transfer a review by copy, download, and same-session import. Change an SVG to check stale feedback, and add, edit, and remove a candidate while the server runs. Open exported SVG and offline HTML independently of the source directory.

A passing build establishes that pages were generated; it does not establish that these interactions work. SVG validation also cannot judge whether labels, contrast, clipping, or the explanation are good. Record which browser checks were actually completed and give reproduction steps for any remaining area.

Release boundary

The packages are currently versioned 0.1.0 and unpublished. Local archives support development and consumer verification; their existence is not a registry release. Before publication, confirm registry ownership, repository/homepage/bugs metadata, license and copyright provenance, the exact release version, and a fresh packed-consumer build. The project site is deployed separately through Cloudflare Workers Static Assets. Its availability does not publish the packages; keep local archive instructions until a registry release is verified.

The /diagram-gen and /my-diagram-gen pages describe future skills. They do not indicate that skills were created or installed. Browser feedback is local state until the user copies or downloads a review; it does not write source files or resume a conversation automatically.