Rename the app from MangaParty to MangaCircus

docs/import.md

@@ -1,6 +1,6 @@
 # How the import works
 
-MangaParty does not copy or convert anything. "Import" means **indexing the library folder in place**. The scanner (`library.js`) walks the folder tree described in [library-format.md](library-format.md) and builds an in-memory index. The server (`server.js`) swaps that index in, compares it with what it has seen before, and notifies followers of new chapters. The library itself is only ever read.
+MangaCircus does not copy or convert anything. "Import" means **indexing the library folder in place**. The scanner (`library.js`) walks the folder tree described in [library-format.md](library-format.md) and builds an in-memory index. The server (`server.js`) swaps that index in, compares it with what it has seen before, and notifies followers of new chapters. The library itself is only ever read.
 
 ```
                  ┌───────────── triggers ─────────────┐
@@ -177,7 +177,7 @@ The scan uses asynchronous I/O one file at a time, so it never blocks request ha
 2. Otherwise, a chapter id not in `known` is new. It is appended; the list **only grows**, so a temporarily missing folder or an unmounted disk never causes a second round of notifications when it comes back.
 3. For every user following the manga:
    - one in-app notification per new chapter (text `Title · Ch. 7: Thaw`; at most 200 kept per user),
-   - if the user has a webhook URL, **one** `POST` per manga per scan, with a plain-text body (`New in Moon Garden: Ch. 7 Thaw, Ch. 8 Bloom`), header `Title: MangaParty`, and a 10 s timeout. Failures are logged, not retried.
+   - if the user has a webhook URL, **one** `POST` per manga per scan, with a plain-text body (`New in Moon Garden: Ch. 7 Thaw, Ch. 8 Bloom`), header `Title: MangaCircus`, and a 10 s timeout. Failures are logged, not retried.
 4. Opening a chapter marks its notifications as read.
 
 What counts as "new" follows from the chapter id (`book key/chapter key`):