Document resolutionStatus field in assistant conversations API

[mintlify]

Summary

The GET /v1/analytics/{projectId}/assistant endpoint now returns a resolutionStatus field on each conversation, surfacing whether the assistant resolved the user's question. This PR updates the analytics OpenAPI specification (and its es/fr/zh translations) to document the new field in the response schema.

Generated-By: mintlify-agent

---

Note

Low Risk
Low risk: documentation-only OpenAPI schema updates with no runtime or behavioral code changes.

Overview
The GET /v1/analytics/{projectId}/assistant response schema is updated to include a new nullable resolutionStatus field on each conversation, indicating whether the assistant resolved the user’s question.

This documentation change is applied consistently across the base OpenAPI spec and the es, fr, and zh translated specs, and the field is added to the conversation object’s required list.

^{Reviewed by Cursor Bugbot for commit 3cfdce7. Bugbot is set up for automated code reviews on this repo. Configure here.}

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
mintlify	🟢 Ready	View Preview	Apr 24, 2026, 9:35 PM

[ethanpalm]

Closing: no evidence this feature has shipped to production. The resolutionStatus field is used internally in the Mintlify dashboard but is not currently returned by the external GET /v1/analytics/{projectId}/assistant API endpoint. The external analytics controller does not include this field in its conversation response mapping. When the external API is updated to include this field, a new docs PR can be opened at that time.