feat(document-client): regenerate from prod spec — validateTemplate

[jpinho]

Summary

Regenerates @epilot/document-client from the Document API spec as deployed to production (npm run openapi → typegen → build). One new operation and its types:

• validateTemplate — POST /v2/templates:validate. Checks a docx/xlsx/pptx template for tag and delimiter errors and, with fix: true, returns a corrected copy as a presigned download plus the issue list.
• TemplateValidationRequest (template_document, fix, fix_level: safe | aggressive), TemplateValidationResponse (valid, fixed, issues, unresolved_errors, fixed_document), TemplateIssue (id, file, location such as Tabelle1!N4, before / after, confidence, fixable).

Backend: document-api !310 (merged, in prod). First consumer: epilot360-document-generation, which currently calls the path with a raw post() and local types and will switch to client.validateTemplate() once this is published.

Also picked up from the prod spec: the error_code description text and two example values on the generate response changed. No operation was removed.

Changeset: @epilot/document-client minor, @epilot/sdk minor (same shape as the last client regen).

Test plan

• npm test in clients/document-client — 3 passed
• npm run lint (biome) clean, npm run build green
• Publish: pnpm version-packages + pnpm publish-packages (2FA) after merge; @epilot/sdk auto-releases on the openapi.json change

🤖 Generated with Claude Code

https://claude.ai/code/session_01HqKX86eMjbax2MWeJWNXBB

---

Generated by Claude Code