Two items were left on the Databases roadmap — a visual database browser and a set of maintenance tools. Both shipped, alongside two bugs found by clicking through the finished feature against a development server rather than trusting a green test suite.
The database browser goes further than “manage what the panel created.” It lists every database on the server, because that’s what a real database administration tool gives you, and pretending otherwise would just mean reaching for a terminal. Browsing tables and rows is the easy half. The query runner is the deliberate one: it is an admin-only tool that runs the SQL an admin submits. That doesn’t introduce a new trust tier, since the admin role already has other powerful actions like Server Setup and Panel Update.
Maintenance Tools adds a live server status view, the process list with a per-process Kill button, a slow query log toggle, and one-click repair/optimize for any database.
Two bugs turned up during live verification:
Escaped output shown raw. The row browser relied on the database client escaping special characters inside values, but nothing reversed that before display, so embedded newlines showed as literal text. Fixed with a single-pass unescape.
A permission gap blocking a feature’s own write. The slow query log toggle worked immediately, but saving its setting for persistence across restarts failed because the location hadn’t been permitted for the app. This is the same class of issue seen in earlier features, and it was fixed the same way.
One more thing surfaced that wasn’t new: the development server’s licence setting had been left in a bad state by an earlier test run, and cached settings meant a direct database repair didn’t apply until the cache was cleared. Both were fixed, and a fresh trial licence was requested from the real licence server rather than hand-writing values back in.