[g-kamil]

Description

• Remove 44 redundant service rows from the root README, including the duplicated Productivity and collaboration table and repeated Bazarr, BookLore, and LubeLogger entries.
• Retain all 134 unique services, including entries present only in the duplicated table.
• Keep service entries in case-insensitive alphabetical order and preserve existing maintenance, licensing, and plan-limit notices.
• Change only the root README.md; no stack configuration or service README is modified.

Related Issues

• None.

Verification

• docker compose config --quiet from each changed service directory, with dummy values for required variables — Not applicable: no service directory or Compose configuration changed.
• The stack started, Tailscale is healthy, and the service is reachable through the Tailnet — Not applicable: documentation-only change; no runtime behavior changed.
• The main function of the service works, and its data survives a restart — Not applicable: no application or storage changes.
• rumdl check --config .markdownlint.yml . on the whole repository, and git diff --check
  • Ran uvx "rumdl@0.2.78" check --config .markdownlint.yml ., using the version pinned in .github/workflows/linting.yml: no issues in 142 files.
  • Ran git diff --check origin/main: passed. The origin remote points to tailscale-dev/ScaleTail.
• Ran an ad hoc catalog verification: exactly 134 unique service names and targets remain; all original service targets are preserved; each category is alphabetized; every Details link resolves to an existing service README; existing maintenance, licensing, and plan-limit notices remain.

Impact on existing users

• None. No configuration changes or migration steps are required.

Checklist

• I have performed a self-review of my code and followed the templates structure. No service-template changes apply to this root README repair.
• I did not commit a working auth key, password, token, or other credential.
• The service README uses the headings of the template, in the same order, and is up to date. — Not applicable: no service README changed.
• I added, removed, or renamed the service in the root README.md, in alphabetical order, or this PR does not change the list of services. The unique service set is unchanged; only duplicate entries were removed and misplaced rows reordered.

Additional Context

• All changes are contained in commit ef255e441de1ab85850467472b57cc3a0ce2877b on g-kamil:fix-readme.
• No labels have been applied; maintainers assign them as described in CONTRIBUTING.md.