Starts the binary from the project directory with automatic
restart on failure. Install with:
  cp wikiapiserver.service ~/.config/systemd/user/
  systemctl --user daemon-reload
  systemctl --user start wikiapiserver
  systemctl --user enable wikiapiserver

The structured contents API requires a POST request with the filter
in the JSON body to narrow results:
  {"filters": [{"field": "in_language.identifier", "value": "en"}]}

Replaces the non-functional query-string filter parameter.

The filters[project]=en.wikipedia.org parameter caused timeouts and
empty responses. The filter value was incorrect for the Wikimedia
Enterprise API.

Articles from 404-list.test that genuinely don't exist on Wikipedia
(e.g. TV episodes without standalone articles) still return 404 —
this is expected behavior from the upstream API.

- Non-2xx responses (404, 429, 5xx) are now forwarded to the
  client with their original status code and response body
- Increased WriteTimeout to 45s to accommodate slow upstream API
- Added explicit resp.Body.Close() and response flush before return

- sql/000_widen_tokens.sql: widen token columns to TEXT, add
  refresh_token_created and access_token_created timestamps
- sql/001_add_api_logs.sql: create api_logs table for request logging

- Created api_logs table (username, article_name, status_code,
  response_time_ms, error, request_url)
- GetArticle logs failures (network errors and non-2xx responses)
  with timing, status code, and response body
- Successful requests are not logged

Binary was tracked for several commits, bloating the repo.
Removed all references via git filter-repo.

Add limit=1&filters[project]=en.wikipedia.org to structured
contents API call.

GET /article?username=alice&name=en.wikipedia/Sun
→ proxies to api.enterprise.wikimedia.com/v2/structured-contents/{name}
with Authorization: Bearer <access_token>

Returns 401 for unknown users, 400 if params missing,
and passes through the upstream HTTP status on errors.

Returns access_token and valid_until for a given username.
GET /token?username=foo → {"access_token": "...", "valid_until": "2026-06-26T15:00:51Z"}