Thanks for contributing. The most helpful changes are the ones that improve the current release surface and keep the documentation honest.
Read these files before making changes:
- frontend bug fixes and usability improvements
- accessibility improvements
- documentation corrections
- tests for current routed features
- backend hardening for the active auth and data-service paths
When reporting a bug, include:
- steps to reproduce
- expected and actual behavior
- screenshots or logs if relevant
- environment details
- whether you used demo mode or the Docker stack
Keep pull requests focused and release-friendly:
- explain the user-facing problem
- list the verification you ran
- update docs when behavior, ports, paths, or setup steps change
- avoid presenting planned or legacy features as shipped functionality
For frontend work, run:
cd frontend
npm install
npm run lint
npm run test -- --run
npm run buildIf you change deployment, security, or architecture behavior, update the corresponding Markdown files in the repo root or docs/.
- prefer small, reviewable changes
- keep product claims accurate
- document limitations and assumptions
- preserve the current release path unless you are intentionally updating it
By contributing, you agree that your contributions are provided under the repository license.