the naming form is about naming, and it had been wired to the wrong question

Two conditions with similar names got conflated by a search-and-replace.
`settled` means the databases are named and exist, which is when the form has
done its job. `settledNow` means everything including BACKUPS is configured,
which is when the whole block can fold away. The form/rows branch was using the
second.

That deadlocked it. The component reporting whether backups are configured lives
inside the rows branch — so showing the form meant it never mounted, never
reported, and the form could never be replaced. The panel went back to asking
for names it already had, with no way out.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

web/DatabaseBlock.tsx

@@ -319,7 +319,15 @@ export const DatabaseBlock = () => {
         ) : undefined
       }
     >
-      {summaryReady === null || !status ? null : settledNow ? (
+      {/*
+        `settled`, NOT `settledNow`. These answer different questions and conflating them deadlocked
+        this block: `settledNow` includes whether BACKUPS are configured, but the component that
+        reports that lives inside this branch — so showing the form meant it never mounted, never
+        reported, and the form stayed forever.
+
+        The form is about NAMING. Once both databases are named and exist, it has done its job.
+      */}
+      {summaryReady === null || !status ? null : settled ? (
         <>
           {row('Production', 'production', status.production)}
           {row('Development', 'development', status.development)}