damacus
spec.yaml and generated models predate parts of the API audit and contain historical inaccuracies. For example, account-manager responses document name, while the existing model exposes first_name and last_name. Dedicated wrappers currently preserve raw JSON to avoid depending on speculative generated schemas. Audit schema and route discrepancies against current official documentation, correct spec.yaml and regenerate models using the repository workflow. Preserve established command compatibility and raw JSON fields; add targeted fixtures for confirmed model discrepancies. Record unresolved documentation conflicts separately rather than guessing. Keep docs/api-coverage.md consistent with the resulting specification. Sources: https://dev.freeagent.com/docs/accountancy_practice_api and the official resource links in docs/api-coverage.md.