data/sessions/explorer-nested-folders-3/memory.md

# Memory: explorer-nested-folders-3

## Overview

Build a multi-level folder tree and move a file into its deepest level from a shell, in a
single line. Use this as the terminal route to the same end state as the file-manager task:
one command creates every level of the path at once and a second moves the file in, with no
navigation and no row counting. The recorded trace opens a shell, runs a
`New-Item -ItemType Directory … -Force` and a `Move-Item` separated by a semicolon, and
closes the shell with `exit`.

## Prerequisites

- A desktop environment with a file manager, or a shell.
- A starting folder that exists and is writable, and that is the active target when
  creation begins. The keyboard route creates each folder inside whatever container
  currently has focus, so the focused container — not the one on screen — is what
  governs.
- The full folder path decided in advance, level by level, including capitalisation.
- A file to relocate, existing and identifiable by name, and write access to both its
  current folder and the final destination.
- No existing folder at any level using the intended name, and no file of the same name at
  the destination.
- Clarity that the file is moved, not copied — nothing must remain at the source.
- Enough space, and both locations on the same volume where that can be arranged; a move
  across volumes copies and deletes rather than renaming.

## Steps

### Step 1 — Left-click at (268, 1060)

The task is to build a three-level folder path and move a file into its innermost folder, all of which is expressible as commands, so the first move is to open somewhere to type them. Move the cursor and Left-click the PowerShell icon in the taskbar. This is the Windows equivalent of the Dock click in the macOS twins.

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

### Step 2 — Type: New-Item -ItemType Directory $env:USERPROFILE\corpus-seed\Projects\2026\Q3 -Force; Move-Item $env:USERPROFILE\corpus-seed\report.pdf $env:USERPROFILE\corpus-seed\Projects\2026\Q3\

Type both operations as one line separated by a semicolon. `New-Item -ItemType Directory` with `-Force` creates the whole `Projects\2026\Q3` chain in one call, including the intermediate folders — that is what replaces the three separate folder creations the GUI and keyboard takes need, and `-Force` also stops it failing if a level already exists. `Move-Item` then relocates the file into the innermost folder. `$env:USERPROFILE` is used instead of a literal home path so the command does not depend on the account name.

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

### Step 3 — Press: Enter

After typing the command Press Enter to run both commands.

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

### Step 4 — Type: exit

Type `exit` to close the shell. The Windows takes end this way rather than with a quit shortcut, because the shell is a console window that closes when its session ends.

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

### Step 5 — Press: Enter

After typing the `exit` Press Enter to run it and close the window.

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

## Notes & Edge Cases

- **Creating the whole path in one call is the point of this route.** The directory command
  makes every missing level, so the tree does not have to be built level by level and there
  is no descent between levels to get wrong.
- **`-Force` here means "do not complain if it already exists" — and that is exactly why it
  needs care.** It suppresses the collision report that would otherwise be the warning
  that the destination is not the fresh folder it was assumed to be. Use it when
  idempotence is genuinely wanted, not to make an error message go away.
- **A semicolon runs the second command whether or not the first succeeded.** If the
  directory creation fails, the move still runs and lands the file somewhere unintended.
  Where the second command depends on the first, chain them so failure stops the line.
- **The trailing backslash on the destination marks it as a folder**, which is what keeps
  the move from being interpreted as a rename when the folder is missing.
- **A move overwrites a same-named file at the destination and the source is gone by
  then.** Check before running.
- **Paths are built from an environment variable rather than written literally**, so the
  command does not depend on the account name. Anything that hardcodes a user's folder
  works on one machine only.
- **The prompt returning is not confirmation.** Read the tree back.