help: say that the other commands are their own commands, not office subcommands

.pi/memory-vault/packs/paperclip-harness/20-context/paperclip-harness.md

@@ -1569,3 +1569,103 @@ Nothing was changed by me in this answer; the commands above are for you to run
 - session: [[packs/paperclip-harness/80-sessions/lazygit-gitignore-editing-discovery-sanitized|lazygit .gitignore editing discovery (sanitized)]]
 - session: [[packs/paperclip-harness/80-sessions/rich-discovery-home-2026-11-13-01-55-32|Rich discovery: home 2026-11-13 01:55:32]]
 - context: [[packs/paperclip-harness/20-context/home|home]]
+
+
+---
+
+## Update (2026-11-13 06:21:57)
+
+## Rich discovery update (2026-11-13 06:21:57)
+
+Built, and I have already used it on `TEST-BETA` — which is now completely clean.
+
+## Why you could not delete it in Paperclip
+
+The API can delete a project (`DELETE /api/projects/{id}`), but **you had two of them**, from two creation attempts:
+
+```
+cf776606-f20c-43c8-90c5-56452486911b   TEST-BETA     git_repo  isolated_workspace
+dc24897b-cbf3-4068-86fd-a84caa1a3ee5   TEST-BETA 2   git_repo  isolated_workspace
+```
+
+Deleting one leaves the other pointing at the same folder, so the folder never looks free.
+
+## The new command
+
+```sh
+project-delete <folder>            # says exactly what would go, changes nothing
+project-delete <folder> --yes      # does it
+```
+
+It removes, in this order:
+
+1. the TUIOS session for the project **and** any `<session>-git` helper session
+2. **every** Paperclip project that claims that folder — not just the one the project file remembers
+3. the registry lines in `~/.config/paperclip-harness/projects.toml`
+4. the folder's machinery: `.git`, `.gitignore`, `.harness`, `.paperclip`, `.pi`
+
+It keeps every ordinary file, so your notes survive and the folder can be adopted again. `--delete-folder` removes the folder too, and asks you to type its name first.
+
+`project-reset` remains the gentle one: panes and worktrees only, keeping the Paperclip history.
+
+## What it did to `TEST-BETA`
+
+```
+folder   /home/sam/TEST-BETA
+project  TEST-BETA    cf776606-f20c-43c8-90c5-56452486911b
+project  TEST-BETA 2  dc24897b-cbf3-4068-86fd-a84caa1a3ee5
+sessions (none)
+files    .git, .gitignore
+
+  deleted the Paperclip project TEST-BETA
+  deleted the Paperclip project TEST-BETA 2
+  removed cf776606-… from projects.toml
+  removed dc24897b-… from projects.toml
+  removed /home/sam/TEST-BETA/.git
+  removed /home/sam/TEST-BETA/.gitignore
+```
+
+Verified afterwards:
+
+```
+/home/sam/TEST-BETA:  folder-0  TEST0.md  TEST1.md  TEST2.md
+projects for that folder: 0
+registry lines for TEST-BETA: 0
+```
+
+Your four files are untouched. `~/TEST-BETA` is now a plain folder with no git, no dot files, and nothing in Paperclip or TUIOS — exactly the state for a clean run.
+
+## Two things to know before you run it again
+
+- **One Paperclip project per folder.** If a creation attempt dies half-way, a second attempt makes "TEST-BETA 2" rather than reusing the first. `office` now adopts a project whose workspace points at the folder before creating a new one, but if you ever see a numbered name, that is what happened — and `project-delete` clears them all.
+- **The Y/N gate is now the right order**: nothing is staged, you ignore first, then `a` stages what is left, then `c` commits. Then run the office command again and it will create the project with worktrees, the session, and eight panes.
+
+Committed: `paperclip-harness` `7144878`, pushed, and `project-delete` is on `PATH` on all three machines.
+
+## Source paths observed
+
+- `nix/store/bya4ansy58az5133kryqp2cvrxbnz8qy-python3-3.14.10/lib/python3.14/tomllib/_parser.py`
+- `home/sam/paseo/projects/paperclip-harness/bin/project-delete`
+- `home/sam/paseo/projects/paperclip-harness/bin/lib/harness.py`
+- `home/sam/paseo/projects/test-alpha`
+- `tmp/del-test/.git`
+- `tmp/del-test/.gitignore`
+- `tmp/del-test/.harness`
+- `tmp/del-test/.paperclip`
+- `tmp/del-test/.pi`
+- `home/sam/TEST-BETA`
+- `home/sam/.config/paperclip-harness/projects.toml`
+- `home/sam/TEST-BETA/.git`
+- `home/sam/TEST-BETA/.gitignore`
+- `.config/paperclip-harness/projects.toml`
+
+## Evidence
+
+- Confidence: 84%
+- Reason: Update component/repository context with detailed discovered structure and configuration
+
+## Related learned memories <!-- same-turn-2026-11-13 06:21:57 -->
+
+- session: [[packs/paperclip-harness/80-sessions/rich-discovery-isolated-workspace-2026-11-13-06-21-57|Rich discovery: isolated_workspace 2026-11-13 06:21:57]]
+- context: [[packs/paperclip-harness/20-context/paperclip-harness|isolated_workspace]]
+- observation: [[packs/paperclip-harness/60-observations/tmp-repository-structure-and-configuration-patterns|isolated_workspace repository structure and configuration patterns]]

.pi/memory-vault/packs/paperclip-harness/60-observations/tmp-repository-structure-and-configuration-patterns.md

@@ -7784,3 +7784,103 @@ Nothing was changed by me in this answer; the commands above are for you to run
 - session: [[packs/paperclip-harness/80-sessions/lazygit-gitignore-editing-discovery-sanitized|lazygit .gitignore editing discovery (sanitized)]]
 - session: [[packs/paperclip-harness/80-sessions/rich-discovery-home-2026-11-13-01-55-32|Rich discovery: home 2026-11-13 01:55:32]]
 - context: [[packs/paperclip-harness/20-context/home|home]]
+
+
+---
+
+## Update (2026-11-13 06:21:57)
+
+## Structural/configuration observations (2026-11-13 06:21:57)
+
+Built, and I have already used it on `TEST-BETA` — which is now completely clean.
+
+## Why you could not delete it in Paperclip
+
+The API can delete a project (`DELETE /api/projects/{id}`), but **you had two of them**, from two creation attempts:
+
+```
+cf776606-f20c-43c8-90c5-56452486911b   TEST-BETA     git_repo  isolated_workspace
+dc24897b-cbf3-4068-86fd-a84caa1a3ee5   TEST-BETA 2   git_repo  isolated_workspace
+```
+
+Deleting one leaves the other pointing at the same folder, so the folder never looks free.
+
+## The new command
+
+```sh
+project-delete <folder>            # says exactly what would go, changes nothing
+project-delete <folder> --yes      # does it
+```
+
+It removes, in this order:
+
+1. the TUIOS session for the project **and** any `<session>-git` helper session
+2. **every** Paperclip project that claims that folder — not just the one the project file remembers
+3. the registry lines in `~/.config/paperclip-harness/projects.toml`
+4. the folder's machinery: `.git`, `.gitignore`, `.harness`, `.paperclip`, `.pi`
+
+It keeps every ordinary file, so your notes survive and the folder can be adopted again. `--delete-folder` removes the folder too, and asks you to type its name first.
+
+`project-reset` remains the gentle one: panes and worktrees only, keeping the Paperclip history.
+
+## What it did to `TEST-BETA`
+
+```
+folder   /home/sam/TEST-BETA
+project  TEST-BETA    cf776606-f20c-43c8-90c5-56452486911b
+project  TEST-BETA 2  dc24897b-cbf3-4068-86fd-a84caa1a3ee5
+sessions (none)
+files    .git, .gitignore
+
+  deleted the Paperclip project TEST-BETA
+  deleted the Paperclip project TEST-BETA 2
+  removed cf776606-… from projects.toml
+  removed dc24897b-… from projects.toml
+  removed /home/sam/TEST-BETA/.git
+  removed /home/sam/TEST-BETA/.gitignore
+```
+
+Verified afterwards:
+
+```
+/home/sam/TEST-BETA:  folder-0  TEST0.md  TEST1.md  TEST2.md
+projects for that folder: 0
+registry lines for TEST-BETA: 0
+```
+
+Your four files are untouched. `~/TEST-BETA` is now a plain folder with no git, no dot files, and nothing in Paperclip or TUIOS — exactly the state for a clean run.
+
+## Two things to know before you run it again
+
+- **One Paperclip project per folder.** If a creation attempt dies half-way, a second attempt makes "TEST-BETA 2" rather than reusing the first. `office` now adopts a project whose workspace points at the folder before creating a new one, but if you ever see a numbered name, that is what happened — and `project-delete` clears them all.
+- **The Y/N gate is now the right order**: nothing is staged, you ignore first, then `a` stages what is left, then `c` commits. Then run the office command again and it will create the project with worktrees, the session, and eight panes.
+
+Committed: `paperclip-harness` `7144878`, pushed, and `project-delete` is on `PATH` on all three machines.
+
+## Source paths observed
+
+- `nix/store/bya4ansy58az5133kryqp2cvrxbnz8qy-python3-3.14.10/lib/python3.14/tomllib/_parser.py`
+- `home/sam/paseo/projects/paperclip-harness/bin/project-delete`
+- `home/sam/paseo/projects/paperclip-harness/bin/lib/harness.py`
+- `home/sam/paseo/projects/test-alpha`
+- `tmp/del-test/.git`
+- `tmp/del-test/.gitignore`
+- `tmp/del-test/.harness`
+- `tmp/del-test/.paperclip`
+- `tmp/del-test/.pi`
+- `home/sam/TEST-BETA`
+- `home/sam/.config/paperclip-harness/projects.toml`
+- `home/sam/TEST-BETA/.git`
+- `home/sam/TEST-BETA/.gitignore`
+- `.config/paperclip-harness/projects.toml`
+
+## Evidence
+
+- Confidence: 82%
+- Reason: Captured factual repo structure/configuration patterns from rich discovery
+
+## Related learned memories <!-- same-turn-2026-11-13 06:21:57 -->
+
+- session: [[packs/paperclip-harness/80-sessions/rich-discovery-isolated-workspace-2026-11-13-06-21-57|Rich discovery: isolated_workspace 2026-11-13 06:21:57]]
+- context: [[packs/paperclip-harness/20-context/paperclip-harness|isolated_workspace]]
+- observation: [[packs/paperclip-harness/60-observations/tmp-repository-structure-and-configuration-patterns|isolated_workspace repository structure and configuration patterns]]

.pi/memory-vault/packs/paperclip-harness/80-sessions/rich-discovery-isolated-workspace-2026-11-13-06-21-57.md

@@ -0,0 +1,119 @@
+---
+type: session
+id: session.paperclip-harness.rich-discovery-isolated-workspace-2026-11-13-06-21-57
+title: Rich discovery: isolated_workspace 2026-11-13 06:21:57
+status: active
+source_of_truth: false
+freshness: current
+last_reviewed: 2026-11-13
+tags:
+  - pack/paperclip-harness
+  - agent-memory/session
+  - autolearn
+  - rich-discovery
+  - repo/isolated-workspace
+---
+
+# Rich discovery: isolated_workspace 2026-11-13 06:21:57
+
+Sanitized rich discovery snapshot captured automatically from the completed turn.
+
+
+## Source paths observed
+
+- `nix/store/bya4ansy58az5133kryqp2cvrxbnz8qy-python3-3.14.10/lib/python3.14/tomllib/_parser.py`
+- `home/sam/paseo/projects/paperclip-harness/bin/project-delete`
+- `home/sam/paseo/projects/paperclip-harness/bin/lib/harness.py`
+- `home/sam/paseo/projects/test-alpha`
+- `tmp/del-test/.git`
+- `tmp/del-test/.gitignore`
+- `tmp/del-test/.harness`
+- `tmp/del-test/.paperclip`
+- `tmp/del-test/.pi`
+- `home/sam/TEST-BETA`
+- `home/sam/.config/paperclip-harness/projects.toml`
+- `home/sam/TEST-BETA/.git`
+- `home/sam/TEST-BETA/.gitignore`
+- `.config/paperclip-harness/projects.toml`
+
+## Final answer snapshot
+
+Built, and I have already used it on `TEST-BETA` — which is now completely clean.
+
+## Why you could not delete it in Paperclip
+
+The API can delete a project (`DELETE /api/projects/{id}`), but **you had two of them**, from two creation attempts:
+
+```
+cf776606-f20c-43c8-90c5-56452486911b   TEST-BETA     git_repo  isolated_workspace
+dc24897b-cbf3-4068-86fd-a84caa1a3ee5   TEST-BETA 2   git_repo  isolated_workspace
+```
+
+Deleting one leaves the other pointing at the same folder, so the folder never looks free.
+
+## The new command
+
+```sh
+project-delete <folder>            # says exactly what would go, changes nothing
+project-delete <folder> --yes      # does it
+```
+
+It removes, in this order:
+
+1. the TUIOS session for the project **and** any `<session>-git` helper session
+2. **every** Paperclip project that claims that folder — not just the one the project file remembers
+3. the registry lines in `~/.config/paperclip-harness/projects.toml`
+4. the folder's machinery: `.git`, `.gitignore`, `.harness`, `.paperclip`, `.pi`
+
+It keeps every ordinary file, so your notes survive and the folder can be adopted again. `--delete-folder` removes the folder too, and asks you to type its name first.
+
+`project-reset` remains the gentle one: panes and worktrees only, keeping the Paperclip history.
+
+## What it did to `TEST-BETA`
+
+```
+folder   /home/sam/TEST-BETA
+project  TEST-BETA    cf776606-f20c-43c8-90c5-56452486911b
+project  TEST-BETA 2  dc24897b-cbf3-4068-86fd-a84caa1a3ee5
+sessions (none)
+files    .git, .gitignore
+
+  deleted the Paperclip project TEST-BETA
+  deleted the Paperclip project TEST-BETA 2
+  removed cf776606-… from projects.toml
+  removed dc24897b-… from projects.toml
+  removed /home/sam/TEST-BETA/.git
+  removed /home/sam/TEST-BETA/.gitignore
+```
+
+Verified afterwards:
+
+```
+/home/sam/TEST-BETA:  folder-0  TEST0.md  TEST1.md  TEST2.md
+projects for that folder: 0
+registry lines for TEST-BETA: 0
+```
+
+Your four files are untouched. `~/TEST-BETA` is now a plain folder with no git, no dot files, and nothing in Paperclip or TUIOS — exactly the state for a clean run.
+
+## Two things to know before you run it again
+
+- **One Paperclip project per folder.** If a creation attempt dies half-way, a second attempt makes "TEST-BETA 2" rather than reusing the first. `office` now adopts a project whose workspace points at the folder before creating a new one, but if you ever see a numbered name, that is what happened — and `project-delete` clears them all.
+- **The Y/N gate is now the right order**: nothing is staged, you ignore first, then `a` stages what is left, then `c` commits. Then run the office command again and it will create the project with worktrees, the session, and eight panes.
+
+Committed: `paperclip-harness` `7144878`, pushed, and `project-delete` is on `PATH` on all three machines.
+
+## Evidence
+
+- Confidence: 86%
+- Reason: Preserve full sanitized discovery detail from a rich investigation turn
+
+## Related
+
+- [[packs/paperclip-harness/00-system/pi-agent/memory-manifest|Memory Manifest]]
+
+## Related learned memories <!-- same-turn-2026-11-13 06:21:57 -->
+
+- session: [[packs/paperclip-harness/80-sessions/rich-discovery-isolated-workspace-2026-11-13-06-21-57|Rich discovery: isolated_workspace 2026-11-13 06:21:57]]
+- context: [[packs/paperclip-harness/20-context/paperclip-harness|isolated_workspace]]
+- observation: [[packs/paperclip-harness/60-observations/tmp-repository-structure-and-configuration-patterns|isolated_workspace repository structure and configuration patterns]]

bin/office

@@ -389,6 +389,9 @@ WHAT IT DOES
 
 COMMANDS
 
+  Each of these is its own command on your PATH, not a subcommand of office:
+  type `board`, not `office board`.
+
   office <folder> --project "<Name>"                     adopt a project Paperclip already has
   office <folder> --new "<Name>"                         create the Paperclip project as well
   office .                                               adopt the folder you are standing in