v0.5.4

0.5.4 — 2026-07-05

Upgrade notes for admins

• Rebuild the frontend after pulling: docker compose up -d --build frontend.
  No migrations, no new env vars.

Added

• /admin/databases/new now opens with a card-based engine picker, matching
  the existing "Add Doc Source" and "Add Agent" choice-menu pattern, instead
  of jumping straight into the connection form with a <select> dropdown.
  Cards are laid out two per row and show each engine's official logo
  (via simple-icons for PostgreSQL/MySQL/MariaDB/SQLite/ClickHouse/
  Snowflake/BigQuery, Font Awesome's brand icon for Microsoft SQL Server;
  Oracle falls back to a generic database icon since no official mark is
  available in either set) plus a one-line hint per engine. After picking
  an engine the form shows it as a static badge with a "Change" button to
  go back and pick a different one. Editing an existing connection is
  unchanged (still a <select> in the Connection card, since switching
  engines on an existing connection is a rarer, more deliberate edit).
• /admin/docsources/add renamed "Generate with AI" to "Generate single
  document" and grouped it together with "Generate a library" under a
  "Generate using AI" section heading, matching the categorized picker
  used on /admin/agents/new. "Register a folder" remains ungrouped above
  it.
• /admin/mcp-servers/new now opens with a picker to choose "Connection
  (Remote HTTP)" or "Local (subprocess)" before showing the Connection
  card, instead of always showing both sets of fields at once (URL/
  transport/auth/headers and command/args/env together). After picking,
  the form shows only the relevant fields plus a badge + "Change" button
  to go back. Editing an existing server is unchanged (still shows both
  subsections together, since the existing config may already indicate
  which one is in use).

Fixed

• Page headers' Cancel/primary-action button row (used on ~16 admin
  form pages) reused the .form-actions class from form footers, which
  carries a padding-top/border-top meant to divide it from form
  fields above. Nested inside .page-header, that pushed the buttons
  down and out of line with the title/description. Scoped an override
  (.page-header .form-actions) to zero out that spacing, and changed
  .page-header to align-items: flex-start so the buttons sit on the
  same line as the title instead of centered against the full two-line
  title+description block.
• The engine/connection-kind badge + "Change" button (database and MCP
  server "add" flows above) had no border on either the badge or the
  ghost button, so it read as plain metadata text rather than an
  interactive control. Introduced .picked-control, a single bordered,
  segmented wrapper (badge | Change) with a cyan hover state on the
  button side, matching the bordered-chip affordance used elsewhere
  (e.g. Mission Control's quick actions).
• The Port field on /admin/databases/new stayed at 5432 no matter
  which engine was picked. A one-time effect pre-filled the default
  port for the initial (PostgreSQL) engine before the picker even
  rendered, and onEngineChange only updated the port when it was
  still empty — so once pre-filled, switching engines (MySQL, MSSQL,
  ClickHouse, ...) never touched it. Added a portTouched flag that's
  only set when the admin edits the Port field directly; until then,
  switching engines keeps updating the port to that engine's default
  (or clears it for engines with none, e.g. SQLite/Snowflake/BigQuery).
  Once the admin types a port themselves, engine switches stop
  overwriting it.