docs(wiki): bring the wiki in line with 4.0.0 (#2034)

* docs(wiki): correct the install and operations pages for 4.0.0

Quick Start passed docker an empty ENCRYPTION_KEY: an assignment prefix is not
expanded on the same command line, so the server silently generated its own key
instead of taking the one the page told you to set. The tag examples pinned to
the 3.x line, the documented tmpfs size did not match the shipped compose file,
and several .env values were described as reaching the container when compose
never interpolates them.

* docs(wiki): match the MCP reference to the registered surface

The scope table was missing the whole Collections group and the totals said 27
scopes across 13 groups where the code registers 29 across 14. The Cloudflare
link on the setup page pointed at an anchor on its own page instead of the
heading on Troubleshooting.

* docs(wiki): correct the plugin and admin pages

Three links to Plugin-Development carried a .md suffix, which does not resolve on
the wiki. The admin pages described tabs, permissions and storage behaviour that
had moved on.

* docs(wiki): bring the feature pages back in line with the app

Costs still documented the old panel, where categories could be added, renamed,
reordered and deleted; they are fixed now and the panel is a day-grouped ledger
with settlements. Trip sharing, journeys, maps, packing, reservations and the
account pages had all drifted in the same way.

* docs(wiki): cover the pages the first pass did not reach

The MCP catalog listed 168 of the 201 registered tools; the settlement tools and
rate_place were missing here and the Collections family from the addon page.
Several resource rows claimed a trips:* scope where the handler asks for
trips:read.

* docs(wiki): tighten the corrections a review picked apart

The audit-log resource is the row id, not the credential id; an admin password
reset does not bump password_version the way the page implied; and a few of the
new paragraphs described behaviour more confidently than the code supports.

* docs(wiki): fix what a last read-through caught

Costs shows every figure in your display currency, not the trip's, and an
expense with no payer still counts against the members it is split between.
Studio's cutoff is a 1024px viewport rather than phones alone, and the
Integrations tab is gated on the providers an admin has configured.

* docs(wiki): the last few the review caught

A passkey satisfies the MFA policy everywhere except the WebSocket handshake,
which still asks for TOTP, so a passkey-only account under that policy gets no
live updates. Mobile optimizes a day from two places, not three. The ctx.db row
carried an unescaped pipe that split the table, and the Backups table linked
with a wiki link whose pipe did the same.

wiki/Packing-Lists.md

@@ -6,13 +6,13 @@ Create categorized packing checklists with member assignments and optional bag t
 
 ## Where to find it
 
-Open the **Lists** tab inside the trip planner and select **Packing**. The tab is only visible when the Packing addon is enabled.
+Open the **Lists** tab inside the trip planner and select **Packing**. The tab is only visible when the Lists addon is enabled.
 
-> **Admin:** Enable the Packing addon and optionally turn on Bag Tracking in [Admin-Addons](Admin-Addons).
+> **Admin:** Enable the **Lists** addon (its internal id is `packing`, and it covers both Packing and Todo) and optionally turn on its nested **Bag Tracking** toggle in [Admin-Addons](Admin-Addons).
 
 ## Progress bar
 
-A progress bar shows how many items have been checked (packed) out of the total. It is hidden on small screens and visible on larger viewports. When all items are checked, a completion message replaces the bar.
+A progress bar shows how many items have been checked (packed) out of the total. It is hidden on small screens and visible on larger viewports. When all items are checked, an **All packed!** message replaces the packed/total counter and the bar turns green.
 
 ## Filters
 
@@ -24,14 +24,18 @@ Three filter buttons let you narrow the item view:
 
 ## Categories
 
-Items are grouped into categories. Each category has a colored dot that cycles through a 10-color palette. When you create a new packing list, suggested items are pre-populated in these categories: **Documents** (Passport, Travel Insurance, Visa Documents, Flight Tickets, Hotel Bookings, Vaccination Card), **Clothing** (T-Shirts (5x), Pants (2x), Underwear (7x), Socks (7x), Jacket, Swimwear, Sport Shoes), **Toiletries** (Toothbrush, Toothpaste, Shampoo, Sunscreen, Deodorant, Razor), **Electronics** (Phone Charger, Travel Adapter, Headphones, Camera, Power Bank), **Health** (First Aid Kit, Prescription Medication, Pain Medication, Insect Repellent), and **Finances** (Cash, Credit Card).
+Items are grouped into categories. Each category has a colored dot that cycles through a 10-color palette. A new packing list starts empty — nothing is pre-populated, and the panel just reads *Packing list is empty* until you add something. Fill it by adding categories and items by hand, by applying a saved template (see [Templates](#templates)), or by pasting a whole list in at once (see [Importing a list](#importing-a-list)).
+
+The UI labels these groups **lists** rather than categories: the button that creates one reads **Add list** with the placeholder *List name (e.g. Clothing)*, moving an item between them reads **Move to List**, and the confirm dialog asks about deleting *the list "{name}"*. The REST API and this page still call them categories.
 
 Each category header has a collapse/expand toggle and an overflow menu with these actions:
 
-- **Check all** — mark every item in the category as packed.
-- **Uncheck all** — unmark every item in the category.
 - **Rename** — rename the category.
-- **Delete** — delete the category and all its items.
+- **Check All** — mark every item in the category as packed.
+- **Uncheck All** — unmark every item in the category.
+- **Delete List** — delete the category and all its items.
+
+**Rename** and **Delete List** need the `packing_edit` permission; **Check All** and **Uncheck All** are always shown.
 
 ### Assigning members to a category
 
@@ -46,10 +50,29 @@ Each item row contains:
 - A **quantity** field (always visible).
 - When bag tracking is enabled: a **weight** field (in grams) and a **bag picker**.
 
-Hovering over an item reveals a **category picker** (colored dot), a **rename** button (pencil icon), and a **delete** button. Add new items using the inline "add item" row at the bottom of each category.
+Hovering over an item reveals a **category picker** (colored dot), a **rename** button (pencil icon), and a **delete** button. Add new items using the inline "add item" row at the bottom of each category, or bring a whole list in at once with **Import** (below).
 
 On phones the row keeps the name and reduces everything else: sharing shows as an icon rather than a sentence, a weight nobody entered prints nothing, and edit/delete sit behind the **⋯** button at the end of the row while the list is in edit mode.
 
+## Importing a list
+
+**Import** in the Lists header opens a paste box, or use **Load CSV/TXT** to pick a file. One item per line:
+
+```
+Category, Name, Weight in g (optional), Bag (optional), checked/unchecked (optional)
+```
+
+```
+Toiletries, Toothbrush
+Clothing, T-Shirts, 200
+Documents, Passport, , Carry-on
+Electronics, Charger, 50, Suitcase, checked
+```
+
+Commas, semicolons and tabs all work as separators, and a quoted value keeps its commas (`"Shirt, blue"`). A line with a single value is treated as just a name. A line without a category lands in **Other**, and a bag name that does not exist yet is created for you. Imported items are appended; nothing already on the list is removed.
+
+Import is the only place in the UI that loads weights and bag assignments in bulk — applying a template brings across names and categories only. It requires the `packing_edit` permission.
+
 ## Sharing packing items
 
 Every packing item has a sharing tier that controls who sees it and who is bringing it. By default everything sits in the shared group pool, exactly as before — the tiers are opt-in per item.
@@ -97,7 +120,8 @@ Bag tracking is only available when an admin has enabled it.
 When enabled, a **Bags** panel appears as a right-hand sidebar on wide screens, or as a modal sheet on narrow screens (tap the **Bags** button in the header to open it). Each bag shows:
 
 - Name and color dot.
-- Total weight and a weight-limit progress bar (if a limit is set).
+- Total weight, and a weight limit if you set one. Click **Set limit** next to the weight (or the limit itself, to change it) and type the limit in kilograms — that is how airlines state them, and TREK stores it in grams. Clearing the field removes the limit again.
+- A fill bar. With a limit it reads against that limit; without one the bag is scaled against the heaviest bag, so bags stay comparable.
 - Member avatars assigned to that bag.
 - Item count.
 
@@ -105,7 +129,7 @@ The sidebar also shows an **unassigned** section for items that have no bag, and
 
 To use bags:
 
-1. Click **+ Add bag** to create a bag with a name and color.
+1. Click **+ Add bag** and type a name. The color dot is assigned automatically from a fixed palette; there is no color picker.
 2. Assign items to a bag using the bag picker on each item row (visible when bag tracking is enabled).
 3. Assign members to a bag using the member chip row on the bag card.
 
@@ -113,14 +137,14 @@ To use bags:
 
 You can save and reuse packing lists across trips:
 
-- **Save as Template** — click the **Save as Template** button in the header (visible when the list has items) to save the current list's items and categories as a named template.
+- **Save as template** (admins only) — click the **Save as template** button in the header to save the current list's items and categories as a named template. It only shows for instance admins, and only when the list has items.
 - **Apply Template** — if templates exist, an **Apply Template** dropdown appears in the header. Selecting a template appends its items to the current list without removing existing items.
 
 Templates are managed by admins in [Admin-Packing-Templates](Admin-Packing-Templates).
 
 ## Permissions
 
-All write operations require the `packing_edit` permission.
+All write operations require the `packing_edit` permission. Saving a list as a template on top of that requires an instance admin account; applying a template does not.
 
 ## See also