chore: refresh linuxserver.io catalog index

[castrojo]

Weekly refresh of docs/data/catalog/linuxserver.json from 2026-08-10T06:00:05Z.

[hanthor]

Verified the full diff programmatically: every changed line is a monthly_pulls, stars, or generated_at field update — no schema changes, no added/removed apps, no URL/image_ref changes. This is exactly what a routine weekly catalog refresh should look like. CI (lint/validate) is green.

---

Generated by Claude Code

[hanthor]

Superseded by #696 — recommend closing

This is the oldest of five open PRs that all regenerate docs/data/catalog/linuxserver.json and nothing else. Its snapshot is 2026-08-10T06:00:09Z; #696 carries 2026-09-07T06:00:23Z, four weeks newer.

PR	generated_at
main	2026-08-03T06:00:26Z
#640 (this)	2026-08-10T06:00:09Z
#657	2026-08-17T06:00:09Z
#668	2026-08-24T06:00:16Z
#670	2026-08-31T06:00:06Z
#696	2026-09-07T06:00:23Z

Every one of them rewrites the whole document from https://api.linuxserver.io/api/v1/images?include_config=true, so they replace rather than stack. Merging this after #696 would put a month-old catalog back on main.

No defect in the PR: it merges into main cleanly and python3 -m pytest tests/unit/ with it applied is 539 passed, 1 skipped, matching the baseline. It has simply been overtaken four times.

Recommend closing this, #657, #668 and #670, and merging #696 as the single current refresh — then fixing the generator to force-push one branch instead of opening a PR per weekly run, so this queue does not rebuild itself.

---

Generated by Claude Code

[hanthor]

Closing as superseded by #696, which I just merged (f2abd0a).

These catalog refreshes rewrite docs/data/catalog/linuxserver.json wholesale from the upstream API — they overwrite rather than compose — so they form a strict supersession chain by generated_at: main was at 2026-08-03, this PR carries 2026-08-10, and the merged #696 carries 2026-09-07.

Merging this now would replace the 09-07 catalog with the 08-10 one — a regression, not an update. The next scheduled refresh will produce a newer PR from current main anyway.

Nothing wrong with the change itself; it was correct when generated and simply aged out. Reopen if I've misread the supersession.

---

Generated by Claude Code