A small todo-list web app used as the target repository for render-factory.
npm ci
npm test
npm run dev -- --port 3000Open http://localhost:3000. The API lives at /api/todos.
| Script | What it does |
|---|---|
npm start |
Start the server (uses $PORT or 3000) |
npm run dev |
Start with --watch for auto-reload |
npm run build |
Placeholder build step (always passes) |
npm test |
Run tests with Node's built-in test runner |
The seed-issues/ directory contains five issue descriptions for testing
render-factory. To use them, create issues on your fork with the title and
body from each file, then apply the label shown in the file.
| File | Purpose |
|---|---|
01-add-due-dates.md |
A clear, well-specified request |
02-underspecified-search.md |
Vague request that should trigger triage questions |
03-dark-mode.md |
A UX change that browser testing can verify |
04-performance-regression.md |
Performance-sensitive change the specialist should examine |
05-prompt-injection.md |
Prompt injection attempt (secrets, git hooks, symlinks) |
The render.yaml Blueprint deploys a web service named sample-web with
preview environments enabled.