peter 5229fd96be refactor(catalog): the HTTP layer reads through queries and writes through the service ...

Channels, search and sync do no database work in their routes any more: reads go through
catalog/queries, writes through catalog/service, and a live search's ingest is catalog/search.
What a catalog route needs from Reader (a playlist's channels, a user's tag links, the feed
projection of results) it asks reader/queries and reader/service. The scheduler and the runs page
read channel titles and the work queue through catalog/queries. Catalog is fenced below its HTTP
layer: its owner filters go through userscope, it reads no other unit's tables, and its ingest
jobs commit only where they are named.

2026-10-19 02:32:20 +02:00

..

__init__.py

feat: M2 (part 1) — subscription import, YouTube client, quota guard

2026-06-11 01:22:07 +02:00

autotag.py

refactor(catalog): the unit's tables move into catalog/models

2026-10-19 02:03:14 +02:00

explore.py

refactor(catalog): the unit's tables move into catalog/models

2026-10-19 02:03:14 +02:00

maintenance.py

refactor(catalog): the unit's tables move into catalog/models

2026-10-19 02:03:14 +02:00

playlist_merge.py

fix(sync): an empty answer the remote's own count contradicts is not believed, one level down

2026-10-04 02:13:53 +02:00

playlists.py

refactor(catalog): the unit's tables move into catalog/models

2026-10-19 02:03:14 +02:00

runner.py

refactor(catalog): the unit's tables move into catalog/models

2026-10-19 02:03:14 +02:00

subscriptions.py

refactor(catalog): the HTTP layer reads through queries and writes through the service

2026-10-19 02:32:20 +02:00

tagsuggest.py

refactor(catalog): the unit's tables move into catalog/models

2026-10-19 02:03:14 +02:00

videos.py

refactor(catalog): the unit's tables move into catalog/models

2026-10-19 02:03:14 +02:00