Stop the terminal and Files panes refusing drops onto their own chrome

The z-order gate added last round asked `el.contains(elementFromPoint(x, y))`
— "is the thing painted here mine?" — and was handed `TerminalView`'s inner
xterm host while every overlay in that pane is a *sibling* of it. So any point
under the pane's own chrome answered "not mine" and the drop was refused, with
no message and no log line. The "▼ Following / ▽ Paused" toggle is rendered
unconditionally at `absolute top-2 right-4`, and `ToastHost` is `fixed
bottom-4 right-4` 24rem wide with error cards that never time out: two corners
of the terminal, and one of the Files pane, that could not accept a file for
as long as the app was running.

It shipped green because jsdom has no `elementFromPoint`, so not one of the 81
drop tests entered that branch. The tests here install one.

The question the gate asks is now "is a *blocking overlay* painted here?".
Chrome the pane paints over itself is not one; a dialog backdrop is, and
`ui/Modal` marks its own backdrop so the element `elementFromPoint` actually
returns is the one carrying the marker. `classifyDrop` also separates "aimed at
me and swallowed" from "not my drop", so the first gets a toast and a log line
and the second stays silent.

Three defects around it:

- **A dialog now refuses only the points it covers.** `dropIsBlocked` is
  document-wide and `ui/Modal` portals to `document.body`, so any open dialog
  refused every drop in the window. The deeper half of that is that a dialog
  opened in project A really was still on screen after a tab switch — the pane
  hides itself with a `hidden` class, which a portal does not inherit — so
  `PaneVisibility` lets `App` tell a `Modal` its pane stepped aside, and a
  hidden one paints nothing, traps no focus, answers no Escape and blocks no
  drop while staying mounted with its state intact.

- **`devicePixelRatio` is applied on Windows only.** Only wry's WebView2
  backend hands over physical pixels; the macOS and GTK ones deliver logical
  points and `tauri-runtime-wry` does not rescale them. Halving those was
  survivable while the test was a bare rect and is a refused drop once z-order
  joins in. Read from the wry/tauri sources, not verified on a HiDPI Mac or
  GTK box.

- **`isFileExistsError` can no longer be forged by a filename.** It matched
  `fileexists` anywhere in a normalised error, so uploading a host file called
  `file-exists.txt` turned *any* failure into a collision — and Replace
  re-invoked the upload with `overwrite: true`. The marker now has to stand
  alone in the backend's canonical form, or be a whole discriminant value.

- **A refused compaction or cache-clear keeps its dialog.** `reclaim` reports
  refusals inside `Ok`, so "did it throw" read one as success: the dialog
  closed, the tick list was dropped, and the explanation appeared in the
  outcome panel several screens above the row that was clicked. The dialog now
  stays put and renders the backend's own sentence verbatim.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GBq2rGum6GX7xXgsas1fDc

app/src/components/projects/home/FilesTab.tsx

@@ -3,7 +3,7 @@ import { getCurrentWebview } from "@tauri-apps/api/webview";
 import { startDrag } from "@crabnebula/tauri-plugin-drag";
 import type { FileEntry, Project } from "../../../lib/types";
 import { useFileManager } from "../../../hooks/useFileManager";
-import { isDropTarget } from "../../../lib/dropTarget";
+import { classifyDrop, isDropTarget } from "../../../lib/dropTarget";
 import { useAppState } from "../../../store/appState";
 import Button from "../../ui/Button";
 import FileViewerModal from "./FileViewerModal";
@@ -413,8 +413,11 @@ export default function FilesTab({ project }: Props) {
   // reason `TerminalView` uses it: `dragDropEnabled` is on (the terminal needs
   // it), which blocks HTML5 drag inside the webview on Windows, and only the
   // native payload carries real file *paths*. The listener is window-wide, so
-  // routing is `isDropTarget` — the rect hit test, in CSS pixels, *plus* the
-  // z-order and "is anything modal on screen" questions a rect cannot answer.
+  // routing is `classifyDrop` — the rect hit test *plus* the z-order question
+  // a rect cannot answer: is a modal or a blocking overlay painted at that
+  // point? (Not "is that element mine": chrome painted over a pane — a toast,
+  // a button — is not something that swallows a drop, and treating it as such
+  // made permanent dead zones.)
   //
   // Two further filters sit in front of it, both about our own drag-out:
   // `dragOutInFlight`, and the staged-path check, which is exact because
@@ -440,7 +443,23 @@ export default function FilesTab({ project }: Props) {
         if (payload.type !== "drop") return;
         setDragOver(false);
         if (dragOutInFlight.current) return;
-        if (!isDropTarget(paneRef.current, payload.position)) return;
+        const verdict = classifyDrop(paneRef.current, payload.position);
+        // Aimed at this pane and refused anyway: say so. Nothing else would —
+        // the file just never appears in the listing.
+        if (verdict === "blocked") {
+          console.warn(
+            "[drop] refused: an overlay is covering the drop point",
+            payload.position,
+          );
+          useAppState.getState().pushToast({
+            kind: "info",
+            message: "File drop ignored",
+            detail:
+              "A dialog or full-window overlay is covering that point. Close it and drop the file again.",
+          });
+          return;
+        }
+        if (verdict !== "accept") return;
         // Anything we staged for a drag-out is our own copy of a file that is
         // already in the container; re-importing it would overwrite the
         // original with a snapshot.