Datasets:

NullVoider
/

Memory-Archive-Paradigm

	# Memory: explorer-search-copy

	## Overview

	Find files whose names match a term and copy a match into another folder, using the file
	manager's search. Use this when the file's location is not known and it has to be found
	before it can be copied. The route types the term into the search box, copies the result
	from its context menu, navigates back and into the destination folder, and pastes there.
	The recorded trace copies the `invoice` match into `found\`.

	## Prerequisites

	- A desktop environment with a file manager that can search, or a shell.
	- A folder to search under, existing and readable, and a destination folder that already
	exists and is writable. The copy step does not create the destination.
	- A search term, and clarity about what it is expected to match — a fragment of a name, a
	whole name, or an extension. The term decides the result set, and nothing reviews that
	set before the copy runs.
	- Enough free space at the destination for every match, which is not known in advance.
	- Acceptance that same-named matches from different folders collide at the destination.
	A recursive search can return several files sharing a name, and copying them into one
	flat folder means the later ones overwrite the earlier ones.
	- Clarity that the originals stay in place — this is a copy, not a move.

	## Steps

	### Step 1 — Left-click at (1797, 66)

	The task is to find a file by name and copy it somewhere, and the file's location is not given, so it has to be searched for rather than navigated to. Move the cursor and Left-click the search box at the top right of the Explorer window to put the caret in it.

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

	### Step 2 — Type: invoice

	Type `invoice`. Explorer searches the current folder and its subfolders, matching both file names and indexed file contents.

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

	### Step 3 — Press: Enter

	After typing `invoice` Press Enter to run the search. The address bar changes to `Search Results in corpus-seed` — the visible confirmation that the view is now a result set rather than a folder.

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

	### Step 4 — Right-click at (270, 115)

	The search returned a single hit, `invoice_2026.txt`, with `invoice` highlighted in its name. Move the cursor and Right-click it. The click sits at `y=115` because search results are laid out in taller two-line rows carrying the file's path and a content preview, not on the compact Details grid the rest of these takes use.

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

	### Step 5 — Left-click at (330, 416)

	Move the cursor and Left-click `Copy`. The task says copy, not move, so the original must stay where it is. This menu belongs to a search result and carries `Print` and `Edit` items that the plain file menu does not, which pushes `Copy` lower than its usual position — the menu has to be measured for this view, not carried over.

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

	### Step 6 — Left-click at (19, 67)

	The destination folder cannot be reached from a search-results view. Move the cursor and Left-click the Back arrow to return to `corpus-seed`.

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

	### Step 7 — Double-click at (212, 176)

	Move the cursor and Double-click `found`, the third folder in `corpus-seed`, to open the destination.

	![Step 7](vision/frames/step_0007_20260730_062214_at.webp)

	### Step 8 — Right-click at (700, 300)

	`found\` is empty, so there is no item to move the cursor and right-click. Right-click blank space in the file pane to open the folder's own context menu, which is where `Paste` lives.

	![Step 8](vision/frames/step_0008_20260730_062219_at.webp)

	### Step 9 — Left-click at (780, 439)

	Move the cursor and Left-click `Paste`. It is black rather than dimmed, confirming the clipboard still holds the copied file. `invoice_2026.txt` now exists in both `corpus-seed` and `corpus-seed\found\`, which is what a copy — as opposed to a move — should leave behind.

	![Step 9](vision/frames/step_0009_20260730_062223_at.webp)

	## Notes & Edge Cases

	1. The file's location is not given, which is what makes this a search rather than a navigation. Searching also means the result set is what gets acted on, so read what came back before acting — a search that matched more than expected copies more than expected.
	2. The search covers the current folder and everything under it, and matches indexed contents as well as names. A file whose name does not contain the term can still appear, and one that merely happens to contain it appears regardless of relevance.
	3. The address bar changing to a results heading is the confirmation that the view is a result set rather than a folder. That distinction matters because the destination cannot be reached from a results view — going back is a required step, not housekeeping.
	4. A search result's context menu is not the same menu as a file's. It carries extra entries, which pushes the wanted one to a different position, so the menu has to be read in this view rather than measured once and reused.
	5. Results are drawn in taller rows than an ordinary listing because each carries a path and a preview line. Coordinates taken from a normal folder view do not transfer.
	6. A recursive search flattens the hierarchy: matches from different folders sit side by side, so two files of the same name from different places can overwrite each other at the destination with nothing reporting it.
	7. The destination has to exist before the paste, and the originals stay where they are. Copy and move produce identical-looking destinations, so confirm the source still holds the file if a copy was what was asked for.
	8. A dimmed paste entry means the clipboard is empty and the copy did not land. It is a report rather than a rendering quirk.