Is your feature request related to a problem? Please describe.
On the web, comments on podcast/TV episodes can carry a playback position (the comment form accepts an H:M:S timestamp, stored in seconds). The shelf-mark API only has comment_text — no way to read or write the position — so podcast-oriented clients can't attach "at 32:10" style comments or display existing ones correctly.
Describe the solution you'd like
An optional position (seconds) field on POST /api/me/shelf/item/{item_uuid} for episode items, and included in the relevant response schemas.
Describe alternatives you've considered
Embedding the timestamp in the comment text — not machine-readable and inconsistent with what the web UI produces.
Additional context
Split from #1671 (one issue per request).
Is your feature request related to a problem? Please describe.
On the web, comments on podcast/TV episodes can carry a playback position (the comment form accepts an
H:M:Stimestamp, stored in seconds). The shelf-mark API only hascomment_text— no way to read or write the position — so podcast-oriented clients can't attach "at 32:10" style comments or display existing ones correctly.Describe the solution you'd like
An optional
position(seconds) field onPOST /api/me/shelf/item/{item_uuid}for episode items, and included in the relevant response schemas.Describe alternatives you've considered
Embedding the timestamp in the comment text — not machine-readable and inconsistent with what the web UI produces.
Additional context
Split from #1671 (one issue per request).