data/sessions/explorer-duplicate-file/memory.md

# Memory: explorer-duplicate-file

## Overview

Duplicate a file in place through the file manager's context menu, by copying it and
pasting into the same folder. Use this when a second copy is wanted beside the original and
the file manager offers no single duplicate command. The route right-clicks the file and
chooses Copy, then right-clicks empty space in the same folder and chooses Paste. The
recorded trace leaves `report - Copy.pdf` beside `report.pdf`.

## Prerequisites

- A desktop environment with a file manager, or a shell — either route reaches the same
  end state.
- A file that already exists and can be identified at run time, together with the folder
  holding it. The file is found by name, so the name has to be known; its path does not.
- Write access to that folder. The copy is created beside the original, so the folder
  itself must be writable even though the original is only read.
- Enough free space for a second copy of the file.
- A decision about the copy's name. The file manager names it automatically, following its
  own convention; a shell names it explicitly. The two produce the same file only if the
  shell is told to use the same name.
- No file already occupying the copy's name. The shell route overwrites it silently; the
  file manager route sidesteps it by choosing a different name, which is a different end
  state from the one intended.

## Steps

### Step 1 — Right-click at (250, 386)

The task is to end up with a second copy of `report.pdf` in the folder it already lives in. Move the cursor and Right-click **`report.pdf`** in `corpus-seed` — this selects it and opens its context menu in one action.

![Step 1](vision/frames/step_0001_20260731_122707_at.webp)

### Step 2 — Move-cursor at (298, 642)

Move the cursor onto the **`Copy`** row without clicking yet. A bare click at a menu row does not reliably land in this environment, so moving first and clicking second is the route that works; it also leaves the hover highlight visible in the next frame, which is what makes the target verifiable afterwards.

![Step 2](vision/frames/step_0002_20260731_122712_at.webp)

### Step 3 — Left-click at (298, 642)

Move the cursor and Left-click **`Copy`** — now confirmed by the hover band on that row. `Cut` sits 21 px above it and would move the file rather than duplicate it, which is the opposite of what this task wants.

![Step 3](vision/frames/step_0003_20260731_122714_at.webp)

### Step 4 — Right-click at (900, 600)

The copy has to be pasted back into the same folder, so the destination is where the view already is. Move the cursor and Right-click blank space below the file list to open the folder's context menu, which is the one that carries `Paste`.

![Step 4](vision/frames/step_0004_20260731_122718_at.webp)

### Step 5 — Move-cursor at (948, 739)

Move the cursor onto the **`Paste`** row first, for the same reason as step 2.

![Step 5](vision/frames/step_0005_20260731_122723_at.webp)

### Step 6 — Left-click at (948, 739)

Move the cursor and Left-click **`Paste`**. It is black rather than dimmed, confirming the clipboard holds the file. Because the destination already contains a `report.pdf`, Windows resolves the collision by naming the new file `report - Copy.pdf` — the duplicate the task asked for, with the original untouched.

![Step 6](vision/frames/step_0006_20260731_122726_at.webp)

## Notes & Edge Cases

1. There is no single duplicate command on this system, so the task is two menu operations: copy from the file's own menu, then paste into the folder. Treating it as one action is what makes it look like a step is missing.
2. The first right-click has to be on the file and the second on empty space. They open different menus and each holds only half of what the task needs, so the same gesture in the wrong place produces a menu without the wanted entry.
3. Pasting into the folder that already holds the original creates a name collision, which the file manager resolves itself by appending its own word to the name. That name is its choice and has to be read back rather than predicted.
4. The clipboard is the state carried between the two halves, and it is shared with everything else running. Anything that copies in between replaces it, and the paste then produces the wrong file with no error.
5. A dimmed paste entry is a report, not a rendering quirk: it means the clipboard is empty and the first half did not land. Read it before clicking anything else.
6. Move to the target and click as separate actions; a combined move-and-click sometimes reaches the position without the click registering.
7. The same two operations exist as keyboard shortcuts and reach the same end state in two keystrokes. Prefer them when the selection is already correct, and use the menus as the fallback.