Opt-in telemetry in 2.6.0, and why

[bndct-devops]

2.6.0 adds a telemetry card on Home for admins. I want to say plainly what it is before anyone finds it on their own.

Why: I have no idea how many Tome installs exist or which features get used. GitHub stars and image pulls don't tell me that. Knowing whether anyone uses OPDS, or how many libraries are mostly manga, decides where I spend my evenings.

How it works:

• You are asked once. The answer is stored in your database and never asked again, not after updates either.
• The only "yes" is a button under the exact report Tome would send, generated from your instance right then. There is no switch you can flip without seeing it.
• "No thanks" sends nothing, not even the decline. TOME_TELEMETRY=false hides the card entirely.
• If a later version changes what the report contains, sending pauses until you have looked at the new shape.
• Every send lands in your audit log with a hash of what left.

What is in it: version, platform, bucketed counts (users, books, libraries), the format and language mix as shares, and which features were used in the last 30 days. Never a title, an author, a username or a hostname. One report a month.

Everything, including the full example report, is on the docs page: https://tome.bndct.sh/docs/telemetry
The receiver is public and small: https://github.com/bndct-devops/tome-pulse
The numbers it produces are public too: https://tome.bndct.sh/stats

If something about this feels wrong to you, say so here. I would rather hear it than have people quietly set the env var.