Files that outlived the chats that held them, and a page that led with its footnotes

The second audit pass. Four things, and the first two were reported.

The Prompts page put a screen of variables and a screen of preview above
the editor, so the tabs began two screens down and switching one had to
drag the whole page to be any use -- and on a short tab it could not drag
far enough, leaving the panel stranded above a screenful of nothing.
Editor first, reference after, bar sticky. Custom themes were three fixed
slots: fifty-seven empty colour boxes on a fresh instance and no way to
make a fourth theme. One block per theme plus a blank one, colours behind
a disclosure. Both measured rather than argued about -- rendered through
TestClient and driven under headless Chromium, where the tab bar moved
385->642px before and does not move now, and the themes page went from
5495px to 2820px.

Asking where generated images go found the other two. Deleting a chat
cascades to the attachment rows and leaves every file on disk; the helper
written for exactly that was called from one place, and it was not the
delete button, a schedule's chat, a helper's chat or deleting an account.
Underneath it, `claim` bound message_id and never chat_id, so anything
picked before a chat existed kept an empty chat_id forever -- which six
readers filter on, so those files were also unnamed in the prompt,
unopenable in the canvas, and invisible to the one caller the cleanup had.

And folders nest now. The route has handled parent_id since folders
existed, with a cycle guard and a depth cap the move path never applied;
the sidebar has always drawn a tree. Nothing could ask for one.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

src/lembas/web/templates/folders/edit.html

@@ -64,6 +64,33 @@
               For you, not for any model. It is never sent anywhere.
             </p>
           </div>
+          {#
+            Nesting has worked at the route since folders existed -- with a cycle
+            guard and a depth cap -- and the sidebar template has always
+            recursed to draw it. Nothing anywhere submitted `parent_id`, so the
+            README advertised "arbitrarily nested" folders that could not be
+            nested. This is that control.
+
+            The options are `candidate_parents`, which is the cycle guard stated
+            as a list rather than as a refusal: a picker offering a move the
+            route will reject is a control that looks like it works.
+          #}
+          <div class="field">
+            <label class="field__label" for="folder-parent">Inside</label>
+            <select class="select" id="folder-parent" name="parent_id">
+              <option value="">Nothing — a folder at the top</option>
+              {% for candidate in parents %}
+              <option value="{{ candidate.id }}"
+                      {{ 'selected' if folder.parent_id == candidate.id }}>
+                {{ candidate.name }}
+              </option>
+              {% endfor %}
+            </select>
+            <p class="field__hint">
+              A folder inside another inherits its system prompt where it has
+              none of its own.
+            </p>
+          </div>
         </div>
 
         <div class="card">