v1.9.3 — Real hotfix: profile 500 was a template bug

The real cause of the /auth/profile 500

v1.9.1 and v1.9.2 fixed the migration plumbing, but the 500 the user
kept seeing was never about the database. It was this in
profile.html:

{{ telegram_form.submit(class="btn btn-primary", name="telegram_submit") }}

WTForms always injects the field's own name into html_params when
rendering a widget. Passing name= as an extra kwarg makes
html_params receive name twice:

TypeError: html_params() got multiple values for keyword argument 'name'

I introduced this in v1.8.1's refactor and the same mistake was
copied into the new Google API form in v1.9.0. The redundant
name="X_submit" was never doing anything anyway: the existing
<input type="hidden" name="X_submit" value="1"> is what
discriminates the form on submit.

Fix: drop the bad kwarg from both forms.

Migration hardening from v1.9.1/v1.9.2 stays

Even though it wasn't the cause, the bulletproof per-statement
transactions and information_schema-guarded column adds are real
improvements and stay in.

Image

ghcr.io/gonzalez8/checktime:1.9.3 / :1.9 / :latest

Upgrade

sed -i 's/^CHECK_TIME_VERSION=.*/CHECK_TIME_VERSION=1.9.3/' stack.env
docker compose pull app
docker compose up -d app

After the restart, /auth/profile should load again. The new "API Key
de Google" tab will show the Gemini model dropdown.