capture-model-server

To align capture model server routes and repository queries, apply synchronized updates to router mappings, repository logic, and migration flows within services/madoc-ts to ensure consistent behavior across versions.

Migration-aware routing updates API endpoints alongside database migration logic to prevent data shape drift. It enforces consistent payload shapes and documents endpoint changes when modifying capture-model-server routes.

Document API endpoints and payload shapes by reviewing the router.ts and repository code under services/madoc-ts, then enforcing consistent payload structures and endpoint documentation during server-side route modifications.

Capture model server APIs break after migrations when routes and repository queries drift from updated data models. Coordinating migration logic with router mappings prevents these integration issues across services/madoc-ts versions.

Updating repository queries without modifying the API router risks data model drift and inconsistent payloads. Synchronizing repository changes with router mappings and migration flows maintains capture model server stability.