John O'Keefe
85cdaf7196
New frontmatter'd docs with handler-compatible shapes:
- get_library_types.md (public; []LibraryTypes)
- list_libraries.md (admin; {data: ListLibrariesRow})
- get_library_folders.md (admin; []LibraryFolders)
- list/get stats/resolve/delete processing issues (admin; family-lens 403s
documented)
- scan_library.md (202 + 409 coalescing with active_job_id)
- get/update scan-settings (ScanSettingsResponse)
Gate improvements forced by this batch:
- Array responses: registered slice -> doc example must be a JSON array; key
set compared against the element type
- RawMessage pins may now be arrays
- update scan-settings uses a RawMessage pin: handler always sets Message but
the struct's omitempty would reject correct docs via zero-value marshal
Registry: sqlc models pinned directly (LibraryTypes, LibraryFolders,
ListLibrariesRow — json tags verified in the generated code).
800 B
800 B
method, path, auth, area
| method | path | auth | area |
|---|---|---|---|
| POST | /api/libraries/:id/issues/:issueId/:mediaItemId/resolve | jwt+admin | libraries |
Resolve Processing Issue
Marks one processing issue as resolved. The issue's library must be in the requester's visible set.
Example response
{
"success": true,
"message": "Issue marked as resolved"
}
Errors
| Status | Body | When |
|---|---|---|
| 400 | {"error": "Invalid issue ID"} / {"error": "Invalid media item ID"} |
malformed path params |
| 403 | — | issue's library not in requester's visible set |
| 404 | — | no such issue |
| 500 | {"error": "Failed to resolve issue"} |
unexpected server error |