Update with the change
When a feature, route, integration, data model, workflow, control, limitation or user-facing behavior changes, update the relevant article in this documentation area in the same work. Add a new article when the topic cannot fit naturally into an existing one.
Describe the real state
Say whether a capability is implemented, configurable, illustrative or planned. Keep screenshots and examples fictional. Never inherit a competitor’s certification, ROI figure or clinical/financial claim.
Verify
Check navigation, search, deep links, mobile layout and copied Markdown after significant docs changes. Verify technical statements against the source code and tests, and update setup commands when they change.
For repository maintenance, run npm run audit:unused, npm run typecheck, npm test, and npm run build from the web application directory. TypeScript rejects unused locals and parameters. The unused-code audit includes routes, tests, worker scripts and Remotion authoring; asset deletion additionally requires checking dynamic URLs and stored public-content references. Never infer that a database, uploaded document, manual authoring entry point or reference guide is unused merely because it has no import.