🔥 docs: strip legacy opds-sync rebrand notes; add F-Droid install link

The OPDS_SYNC_* env-compat shim and the legacy opds-sync image tag were
dropped in #40, so the surrounding narrative ("renamed from opds-sync",
"dual-published for one release cycle", volume-rename UPGRADING guide)
is now stale and only confuses new readers.

Stripped from public docs:
- README.md: "formerly named opds-sync" intro/why/repo-layout mentions
- docs/release.md: "Post-release cluster operator checklist" section
- docs/development.md: example DATABASE_URL switched off opds_sync
- server/README.md: "Migration from opds-sync" section
- server/UPGRADING.md: deleted (only contained the rename narrative)

Stale/contradictory inline comments cleaned in compose files, .env.example,
and config.py — the actual POSTGRES_USER/POSTGRES_DB value and default
database_url stay opds_sync (intentional persistent identifier).

CI rename-guard allowlists updated to match.

Also adds the F-Droid listing (link + badge) to the Install section, now
that io.theficos.quire is published.

Author: vitofico

.github/workflows/android-ci.yaml

@@ -144,17 +144,12 @@ jobs:
           if rg -n -P '\bopds[-_]sync\b|(?<![A-Z0-9_])OPDS_SYNC_[A-Z0-9_]*' \
                 -g '!.claude/**' \
                 -g '!CHANGELOG.md' \
-                -g '!docs/release.md' \
-                -g '!docs/development.md' \
                 -g '!server/migrations/versions/*.py' \
-                -g '!README.md' \
                 -g '!server/quire_server/config.py' \
                 -g '!server/docker-compose.yml' \
                 -g '!server/docker-compose.full.yml' \
-                -g '!server/UPGRADING.md' \
                 -g '!server/alembic.ini' \
                 -g '!server/migrations/env.py' \
-                -g '!server/.env.example' \
                 -g '!server/tests/conftest.py' \
                 -g '!server/tests/unit/test_no_stale_opds_sync_imports.py' \
                 . ; then

.github/workflows/server-ci.yaml

@@ -83,17 +83,12 @@ jobs:
           if rg -n -P '\bopds[-_]sync\b|(?<![A-Z0-9_])OPDS_SYNC_[A-Z0-9_]*' \
                 -g '!.claude/**' \
                 -g '!CHANGELOG.md' \
-                -g '!docs/release.md' \
-                -g '!docs/development.md' \
                 -g '!server/migrations/versions/*.py' \
-                -g '!README.md' \
                 -g '!server/quire_server/config.py' \
                 -g '!server/docker-compose.yml' \
                 -g '!server/docker-compose.full.yml' \
-                -g '!server/UPGRADING.md' \
                 -g '!server/alembic.ini' \
                 -g '!server/migrations/env.py' \
-                -g '!server/.env.example' \
                 -g '!server/tests/conftest.py' \
                 -g '!server/tests/unit/test_no_stale_opds_sync_imports.py' \
                 . ; then

README.md

@@ -28,10 +28,8 @@ A self-hosted reading stack for people who already run [calibre-web]:
 
 - **Quire** — native Android EPUB reader (Kotlin / Compose / Readium).
 - **Quire Server** — small FastAPI service that stores reading progress
-  (and later bookmarks) in Postgres. Formerly named `opds-sync`; the
-  Python package is now `quire_server` and the container image is
-  `ghcr.io/vitofico/quire-server` (the legacy `ghcr.io/vitofico/opds-sync`
-  tag is dual-published for one release cycle).
+  (and later bookmarks) in Postgres. The Python package is `quire_server`
+  and the container image is `ghcr.io/vitofico/quire-server`.
 
 calibre-web stays the source of truth for books. Quire Server is the
 source of truth for reading state. Quire reconciles both on the device.
@@ -61,12 +59,11 @@ That's harder than it sounds in the self-hosted world:
 - **Stock OPDS readers** on Android either don't sync reading position
   to a server you control, or sync it through a vendor cloud.
 
-So Quire Server (originally shipped as `opds-sync`) is the piece that
-was missing: a small, reader-agnostic progress server that speaks
-OPDS-style document identity and uses your **calibre-web account as
-the only credential** — no second IdP, no separate sync account. Quire
-is the Android client built against it; nothing in the server design
-is Quire-specific.
+So Quire Server is the piece that was missing: a small, reader-agnostic
+progress server that speaks OPDS-style document identity and uses your
+**calibre-web account as the only credential** — no second IdP, no
+separate sync account. Quire is the Android client built against it;
+nothing in the server design is Quire-specific.
 
 ## Privacy
 
@@ -120,8 +117,14 @@ For configuration details see [`server/README.md`](server/README.md).
 
 ## Install
 
-Grab the latest APK from [Releases], install it, and point it at your
-calibre-web URL on first launch. F-Droid listing is planned.
+Install Quire from [F-Droid] or grab the latest APK from [Releases],
+then point it at your calibre-web URL on first launch.
+
+<a href="https://f-droid.org/packages/io.theficos.quire/">
+  <img src="https://fdroid.gitlab.io/artwork/badge/get-it-on.png"
+       alt="Get it on F-Droid"
+       height="80">
+</a>
 
 For the sync server, see [`server/README.md`](server/README.md) — it
 ships two reference docker-compose files (`docker-compose.yml` for
@@ -179,7 +182,7 @@ data/opds/            calibre-web OPDS client
 data/sync/            quire-server REST client + WorkManager job
 data/library/         quire-server /library/v1 HTTP client (stats today)
 reader/               Readium navigator integration
-server/               quire-server (Python / FastAPI; formerly opds-sync)
+server/               quire-server (Python / FastAPI)
 docs/                 Architecture, development, sync API reference
 scripts/dgradle       Gradle wrapper that runs inside the project's Docker image
 Dockerfile            Reproducible Android build environment (linux/amd64)
@@ -218,3 +221,4 @@ If Quire is useful to you and you'd like to chip in, you can buy me a coffee:
 
 [calibre-web]: https://github.com/janeczku/calibre-web
 [Releases]: https://github.com/vitofico/quire/releases
+[F-Droid]: https://f-droid.org/packages/io.theficos.quire/

docs/development.md

@@ -114,7 +114,7 @@ Listens on `http://localhost:8000`. Configuration is via environment variables;
 see `quire_server/config.py` for the full list. At minimum:
 
 ```
-QUIRE_SERVER_DATABASE_URL=postgresql+asyncpg://postgres:postgres@localhost:5432/opds_sync
+QUIRE_SERVER_DATABASE_URL=postgresql+asyncpg://postgres:postgres@localhost:5432/quire
 QUIRE_SERVER_CWA_BASE_URL=https://library.example.com
 # Optional, defaults shown:
 QUIRE_SERVER_CWA_PROBE_PATH=/opds

docs/release.md

@@ -41,19 +41,6 @@ the unlabeled `0001..0004` backbone and then `alembic upgrade
 and `QUIRE_SERVER_AI_ENABLED`. Sync-only and AI-only deployments skip the
 other branch's migrations silently. See `server/migrations/README.md`.
 
-### Post-release cluster operator checklist (server rename)
-
-The rename release publishes both `ghcr.io/vitofico/quire-server:<sha>`
-and `ghcr.io/vitofico/quire-server:latest` AND keeps the legacy
-`ghcr.io/vitofico/opds-sync:<sha>` / `:latest` tags pointing at the same
-digest for one cycle. The Quire repo does **not** modify any cluster
-manifests; that work is an operational ticket against
-`theficos-cluster` covering, in order: (1) additive apply of the new
-Secret / ConfigMap / Deployment / Service for `quire-server`, (2)
-`/readyz` green on the new pod, (3) flip the calibre-web ingress
-backend, (4) remove the old `opds-sync` resources after the next
-release cycle confirms the new name is healthy.
-
 ## One-time keystore setup
 
 ```sh

server/.env.example

@@ -4,11 +4,6 @@
 # + quire-server) and `docker-compose.full.yml` (full stack: postgres +
 # calibre-web + quire-server + Caddy). Vars marked "full-only" are only
 # read by the full-stack compose.
-#
-# NOTE: For one release cycle the server ALSO reads OPDS_SYNC_* names
-# FROM REAL ENVIRONMENT VARIABLES ONLY (per Lock #21). Legacy names in
-# this .env file are NOT honored. Migrate any OPDS_SYNC_* keys you may
-# have used previously to QUIRE_SERVER_* before the next release.
 
 # --- Shared (minimal + full) ---
 POSTGRES_PASSWORD=change-me

server/README.md

@@ -224,30 +224,6 @@ Update the health-probe path: it moved from `/sync/v1/healthz` (pre-PR-A) to
 `/health` in PR-A. The k8s manifests in `theficos-cluster` need a one-line
 bump alongside this release.
 
-### Migration from opds-sync
-
-The server was renamed from `opds-sync` to `quire-server` in 2026-05.
-For one release cycle:
-
-- **Env vars** — `QUIRE_SERVER_*` is the preferred prefix. The legacy
-  prefix is still honored when set on **real environment variables**.
-  **Known limitation (Lock #21):** legacy values placed in a `.env`
-  file are NOT honored. To migrate a legacy `.env` file, rename the
-  keys; alternatively, export the legacy names as real env vars at
-  process start.
-- **Image** — `ghcr.io/vitofico/quire-server:<sha>` and
-  `ghcr.io/vitofico/quire-server:latest` are the new tags. The legacy
-  `ghcr.io/vitofico/opds-sync:<sha>` / `:latest` tags are dual-published
-  from the same digest for one release cycle to give operators a window
-  to repin.
-- **DB role / DB name** — these are explicitly **not renamed**. The
-  postgres role and database stay named `opds_sync` (matches the value
-  in `alembic.ini` and the `database_url` default). Renaming a
-  production DB is high-risk and out of scope for this PR.
-
-A future release will drop the legacy prefix, the legacy image tag, and
-the env-compat helper. The DB-name non-rename is permanent.
-
 ### Environment variables
 
 `QUIRE_SERVER_` prefix; full list in `quire_server/config.py`. Most-load-bearing:

server/UPGRADING.md

@@ -14,31 +14,16 @@
 #
 # See server/README.md "Full-stack reference compose" for smoke commands
 # and the TLS swap for production.
-#
-# Env-var compatibility: this compose uses the post-rename
-# QUIRE_SERVER_* prefix. The server also accepts legacy OPDS_SYNC_*
-# from REAL environment variables only (the back-compat shim does NOT
-# read .env files - see server/README.md "Migration from opds-sync").
-# Pick one prefix per deployment; do not mix.
 
 services:
   postgres:
     image: postgres:16-alpine
     restart: unless-stopped
     environment:
-      # DB role / DB name remain 'opds_sync' as a deliberate non-rename
-      # (Lock #20). The Python package and image are 'quire_server' /
-      # 'quire-server' respectively.
       POSTGRES_USER: opds_sync
       POSTGRES_PASSWORD: ${POSTGRES_PASSWORD:-changeme}
       POSTGRES_DB: opds_sync
     volumes:
-      # Volume name kept as `pg_data` for the back-compat window so
-      # existing deployments from v2026.05.17.95 onwards do not
-      # silently get an empty new volume. A future PR may rename it
-      # with an explicit upgrade banner; see README "Migration from
-      # opds-sync". Note: the minimal compose uses `opds_sync_pg` for
-      # the same reason - it shipped earlier with that name.
       - pg_data:/var/lib/postgresql/data
     healthcheck:
       test: ["CMD-SHELL", "pg_isready -U opds_sync"]

server/docker-compose.full.yml

@@ -1,24 +1,12 @@
-# NOTE FOR SELF-HOSTERS UPGRADING FROM A PREVIOUS RELEASE:
-# The Postgres named volume was renamed from `opds_sync_pg` to `pg_data` on
-# 2026-05-21. If you have an existing deployment, DO NOT simply `docker
-# compose up -d` — you must copy the old volume to the new name first or
-# Postgres will start with an empty data directory. See ./UPGRADING.md for
-# step-by-step instructions.
-
 services:
   postgres:
     image: postgres:16-alpine
     restart: unless-stopped
     environment:
-      # DB role / DB name remain 'opds_sync' as a deliberate non-rename
-      # (Lock #20). The Python package and image are 'quire_server' /
-      # 'quire-server' respectively.
       POSTGRES_USER: opds_sync
       POSTGRES_PASSWORD: ${POSTGRES_PASSWORD:-changeme}
       POSTGRES_DB: opds_sync
     volumes:
-      # Renamed from `opds_sync_pg` on 2026-05-21 to match
-      # docker-compose.full.yml. Existing deployments: see ./UPGRADING.md.
       - pg_data:/var/lib/postgresql/data
     healthcheck:
       test: ["CMD-SHELL", "pg_isready -U opds_sync"]