Extend the LFS track-forward policy from GIFs to documentation and marketing PNG screenshots (docs/screenshots, demo, top-level screenshots). Scoped to doc/demo dirs only; app-runtime/build images (PWA icons, Electron tray icons, the served Nerd Font) stay as real blobs so LFS-less build envs never embed a pointer stub. No history rewrite / force-push. Stacks on the GIF LFS change. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Demo scripts
Seed a sample board
node_modules/.bin/tsx demo/seed.ts /absolute/path/to/demo-project
The seeded board now includes a custom Browser Demo Lifecycle workflow with cards staged across:
- Todo
- In Progress
- In Review
- QA
- Publish
This makes it easy to verify browser board rendering for a simple end-to-end lifecycle walkthrough.
Simulate live activity
node_modules/.bin/tsx demo/simulate.ts /absolute/path/to/demo-project
When the seeded workflow is present, the simulator advances demo cards from In Review → QA → Publish while keeping legacy tasks flowing through the standard board lifecycle.