[Yoldark34]

Draft. A step of the Repair epic, #1080: a stepping stone toward the Issues page (#1081), which is probably months away.

Question for maintainers: keep this band-aid, or wait for the Issues page?

This is a temporary quality-of-life shortcut, not the Issues page. It lets users find their broken books now, with the server's rules, while the Issues page waits for its groundwork: the backend search (#1076) and the backend tasks (#1078).

Would you rather:

1. keep the band-aid, removed once the Issues page lands; or
2. drop it and do it right the first time with the Issues page, accepting the delay?

Either is fine with me. It's one self-contained commit.

Change

Server: why a book is broken

• A book is broken when Audible, the only metadata source today, can't be asked for it: no title, no author, no ASIN (or one that isn't an ASIN), or no region for its ASIN. Later, any book not matched to a metadata provider would count.
• BrokenBookRules (application layer) gives the reasons, one code per problem: missing_title, missing_author, missing_asin, invalid_asin, missing_region. The Issues page will use the same codes.
• The library list (GET /library) gives each book its brokenReasons, empty when the book is fine. They're read from its main ASIN identifier and that identifier's region, with one query for the whole library (GetAsinIdentifiersGroupedByAudiobookIdAsync). There's no migration.

Front end: display only

• The group menu ends with "Broken books": the Books list narrowed to the books with reasons, each reason shown as an orange tag under the cover (or on the list row). The rules stay on the server; the front end only filters and shows.
• The front end has the same dictionary of codes, with a label each (utils/brokenBookReasons.ts). A backend test fails when the two dictionaries differ, so a code can't be added on one side only.
• The address and the saved choice use group=broken. With no broken book left, the page says so and offers all books. The group menu stays available when the filtered list is empty.

With the other PRs

• Independent of [Step][#1080] Repair: point books at the right Audible record, from the book page and the library #1054 (Repair buttons): it can be reviewed and merged alone. Both touch AudiobooksView.vue, so whichever goes second needs a small rebase.
• [Step][#1080] Issues: a page listing the books to repair #1081 (Issues page, draft) adds the same repository method. Whichever goes second drops its copy.

Tests

Backend: BrokenBookRulesTests (each reason, several at once), LibraryListServiceTests (reasons read from the main ASIN identifier, falling back to the ASIN field), BrokenBookReasonsDictionaryTests (front-end and server dictionaries match). 3783 passed. Front end: the group (last in the menu, filtering, address, saved choice, tags only in this group, empty state). 676 passed. dotnet format, type-check, eslint and prettier are clean.

Captures

Taken on a fresh instance running this branch, with one book whose ASIN has no region.

The group menu, "Broken books" last:

The "Broken books" group, with each book's reasons:

🤖 Generated with Claude Code