docs: document custom destination plate names in micronix move.

Explain how to create a new plate with any name from the destination
picker, including when the filename already matched an existing plate.

Co-authored-by: Cursor <cursoragent@cursor.com>

Author: m-murphy

packages/docs/src/content/docs/guides/bulk-operations/container-movement.md

@@ -53,10 +53,16 @@ Choose a scanner configuration that matches your CSV format. Upload your file(s)
 
 For each file, confirm the **destination plate**:
 
-- If the inferred name matches exactly one existing plate, it is auto-selected.
-- If the name matches no plate, it is treated as a **new plate** (shown as “New plate — assign a storage location in the next step”). You can also click **Create new plate: …** when the filename suggests a name that is not in the database.
+- If the inferred name matches exactly one existing plate, it is auto-selected. You can still choose a **different** destination — open the destination plate picker and select another existing plate, or create a new plate with **any name** (see below).
+- If the name matches no plate, it is treated as a **new plate** (shown as “New plate — assign a storage location in the next step”).
 - If several plates partially match, pick the correct one from the destination plate picker (search by name, barcode, or location).
 
+**Creating a new destination plate (any name)**
+
+Open the **destination plate picker** for a file. At the bottom of the picker, use **Create new plate**: enter the plate name you want and click **Use name**. The name does not have to match the CSV file name — for example, you can upload `PLATE-001.csv` (which auto-selects an existing `PLATE-001`) and still target a brand-new plate named `PLATE-001-RUN2`. If your search text does not match any existing plate, a **Create new plate: …** shortcut appears above the list. Names must be unique; if a plate with that name already exists, select it from the list instead.
+
+When a new name is selected, the picker shows **New plate** and the upload step reminds you that a storage location is assigned on the next step.
+
 Click **Next: Create Destination Plates** when any destination is new, or **Next: Resolve Containers** when all destinations already exist.
 
 **Create Plates**

packages/docs/src/content/docs/guides/features/plate-scan-validation.md

@@ -72,5 +72,5 @@ A **unique exact** match on the stem is auto-selected even if longer plate names
 
 ## Related workflows
 
-- **Container move (micronix)** uses the same CSV format and scanner configurations to move tubes to a destination plate. If the destination plate does not exist, the move wizard creates it before resolving tubes. Container move does not perform read-only validation like this page.
+- **Container move (micronix)** uses the same CSV format and scanner configurations to move tubes to a destination plate. If the destination plate does not exist, the move wizard creates it before resolving tubes — you can choose any new plate name in the destination picker, not only the name inferred from the file. Container move does not perform read-only validation like this page.
 - **qPCR experiments** use a similar plate CSV upload for plate layout; validate plate scan is independent and does not create or change experiments.

packages/docs/src/content/docs/guides/workflows/containers.md

@@ -41,7 +41,7 @@ Before you can add containers, you need collections to put them in. Creating col
 
 Micronix plates can be created in several places:
 
-- **Move Micronix Tubes** — When your scan CSV targets a plate that does not exist, the wizard includes a **Create Plates** step: enter the plate name (from the filename or CSV), pick a storage location, and optionally add a plate barcode. See [Container Movement](/docs/guides/bulk-operations/container-movement/).
+- **Move Micronix Tubes** — When your scan CSV targets a plate that does not exist, the wizard includes a **Create Plates** step: pick a storage location and optionally add a plate barcode. On the upload step you can name a new destination plate yourself (any unique name) from the destination plate picker, even when the file name already matched an existing plate. See [Container Movement](/docs/guides/bulk-operations/container-movement/).
 - **Bulk import** — Step 2 (**Create Missing Collections**) when a CSV references a plate that is not in the database.
 - **Specimen registration or Add container** — Use **Create new collection** on the plate field when registering a specimen or adding a container (Micronix tube type).