Submit Insight Feedback

Body for POST /tokenwise/insights/{insight_id}/feedback.

verdict stays a plain str for the same reason as :attr:InsightOut.state — the gateway owns the closed set (helpful / not_helpful) and answers 422 on anything else, so widening it there doesn't force an api-server release.

comment is bounded at 1000 chars to mirror the gateway's own limit (and its varchar(1000) column) so an over-long body fails here instead of making the round trip just to come back 422. The gateway stays the authoritative enforcement point; keep this number in sync with it.

Response shape for one insight — GET /tokenwise/insights and the apply / dismiss / acknowledge transitions.

state, source and kind stay plain str (not enums) so a new gateway lifecycle state, source or insight kind doesn't force an api-server release — the same stance as :class:AgentOptimization. The gateway is the source of truth (ai21_intelligent_gateway_api.insights.schemas.InsightResponse).

Feedback is two columns, not three: verdict is required on submission, so a non-null feedback_verdict is itself the "has feedback" signal, and updated_at covers when it arrived.