office: promise an attach line only when a session was actually built

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

@@ -1765,3 +1765,89 @@ Committed: `paperclip-harness` `fd71837`, pushed, and copied to `.27` and `.51`.
 - session: [[packs/paperclip-harness/80-sessions/rich-discovery-would-2026-11-12-23-34-09|Rich discovery: would 2026-11-12 23:34:09]]
 - context: [[packs/paperclip-harness/20-context/home|would]]
 - observation: [[packs/paperclip-harness/60-observations/tmp-repository-structure-and-configuration-patterns|would repository structure and configuration patterns]]
+
+
+---
+
+## Update (2026-11-13 00:00:47)
+
+## Rich discovery update (2026-11-13 00:00:47)
+
+It **did** work — the session exists. You did not get the output I expected, so let me show you both.
+
+## The session is there, on `.13`, right now
+
+```
+session: TEST-BETA-git
+  pane: git | cwd: /home/sam/TEST-BETA | running: lazygit
+```
+
+I checked it directly rather than trusting the output. Your staged files are there too:
+
+```
+A  .gitignore
+A  TEST0.md
+A  TEST1.md
+A  TEST2.md
+A  folder-0/TEST3.md
+branch main — no commits yet
+no .harness/  →  the project has not been created (correct)
+```
+
+So the next step is one command from `.27`:
+
+```sh
+tuios attach --host nixos-desktop TEST-BETA-git
+```
+
+That puts you in lazygit, in `/home/sam/TEST-BETA`, without ssh and without `cd`. Then `i` to ignore anything you do not want, `space` to stage or unstage, `c` to commit. Detach, and run the office command again — now that there is a commit it will create the project with worktrees, and no Y/N question.
+
+## Why the output confused you, and what I changed
+
+You were right that the text was wrong. The instruction to attach was printed **after** the lazygit key list, near the bottom — the keys looked like the next step, and the actual next step was buried. That is a fault in the wording order, not in the session creation.
+
+Now the first thing printed after your Y is the thing to do:
+
+```
+  EVERYTHING IS STAGED AND NOTHING IS COMMITTED. What you commit is what
+  the agent will be able to see, so check it before you commit.
+
+  A session called 'TEST-BETA-git' now holds lazygit in that folder.
+  Attach to it, stage and commit, then come back and repeat the command:
+
+      tuios attach --host nixos-desktop TEST-BETA-git
+
+  When you are done with it:  tuios kill-session TEST-BETA-git
+
+  In lazygit:
+      i      put the selected file or folder into .gitignore
+      space  stage or unstage        e  edit a file, .gitignore included
+      c      commit                  ?  every key
+```
+
+The `--host` part is added automatically when you are on a different machine from the folder.
+
+## Also cleaned up
+
+My testing had left four sessions on `.13` — `gitsess-git`, `gitsess4-git`, `gitsess5-git`, `gw2`, `remote-t-git`. All killed. `TEST-BETA-git` I left alone, because it is yours and it is the one you need.
+
+## If the session had not been there
+
+Then the answer would have been that `.27` was still running an older copy. I can rule that out now: the file on `.27`, `.51` and `.13` are byte-identical and all contain the code that opens the session, and I proved the remote path works end to end from `.27` against a folder on `.13` before answering.
+
+Committed: `paperclip-harness` `bd0114a`, pushed, and the copies refreshed on all three machines.
+
+## Source paths observed
+
+- `home/sam/TEST-BETA`
+
+## Evidence
+
+- Confidence: 84%
+- Reason: Update component/repository context with detailed discovered structure and configuration
+
+## Related learned memories <!-- same-turn-2026-11-13 00:00:47 -->
+
+- session: [[packs/paperclip-harness/80-sessions/rich-discovery-nixos-2026-11-13-00-00-47|Rich discovery: nixos 2026-11-13 00:00:47]]
+- context: [[packs/paperclip-harness/20-context/home|nixos]]
+- observation: [[packs/paperclip-harness/60-observations/tmp-repository-structure-and-configuration-patterns|nixos repository structure and configuration patterns]]

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

@@ -7295,3 +7295,89 @@ Committed: `paperclip-harness` `c53f37d`, pushed, and the copies on `.13`, `.27`
 - session: [[packs/paperclip-harness/80-sessions/paperclip-harness-lazygit-bootstrap-session-fix-and-cross-ma|paperclip-harness: lazygit bootstrap session fix and cross-machine wrapper bugs]]
 - session: [[packs/paperclip-harness/80-sessions/rich-discovery-with-2026-11-12-23-54-31|Rich discovery: with 2026-11-12 23:54:31]]
 - context: [[packs/paperclip-harness/20-context/with|with]]
+
+
+---
+
+## Update (2026-11-13 00:00:47)
+
+## Structural/configuration observations (2026-11-13 00:00:47)
+
+It **did** work — the session exists. You did not get the output I expected, so let me show you both.
+
+## The session is there, on `.13`, right now
+
+```
+session: TEST-BETA-git
+  pane: git | cwd: /home/sam/TEST-BETA | running: lazygit
+```
+
+I checked it directly rather than trusting the output. Your staged files are there too:
+
+```
+A  .gitignore
+A  TEST0.md
+A  TEST1.md
+A  TEST2.md
+A  folder-0/TEST3.md
+branch main — no commits yet
+no .harness/  →  the project has not been created (correct)
+```
+
+So the next step is one command from `.27`:
+
+```sh
+tuios attach --host nixos-desktop TEST-BETA-git
+```
+
+That puts you in lazygit, in `/home/sam/TEST-BETA`, without ssh and without `cd`. Then `i` to ignore anything you do not want, `space` to stage or unstage, `c` to commit. Detach, and run the office command again — now that there is a commit it will create the project with worktrees, and no Y/N question.
+
+## Why the output confused you, and what I changed
+
+You were right that the text was wrong. The instruction to attach was printed **after** the lazygit key list, near the bottom — the keys looked like the next step, and the actual next step was buried. That is a fault in the wording order, not in the session creation.
+
+Now the first thing printed after your Y is the thing to do:
+
+```
+  EVERYTHING IS STAGED AND NOTHING IS COMMITTED. What you commit is what
+  the agent will be able to see, so check it before you commit.
+
+  A session called 'TEST-BETA-git' now holds lazygit in that folder.
+  Attach to it, stage and commit, then come back and repeat the command:
+
+      tuios attach --host nixos-desktop TEST-BETA-git
+
+  When you are done with it:  tuios kill-session TEST-BETA-git
+
+  In lazygit:
+      i      put the selected file or folder into .gitignore
+      space  stage or unstage        e  edit a file, .gitignore included
+      c      commit                  ?  every key
+```
+
+The `--host` part is added automatically when you are on a different machine from the folder.
+
+## Also cleaned up
+
+My testing had left four sessions on `.13` — `gitsess-git`, `gitsess4-git`, `gitsess5-git`, `gw2`, `remote-t-git`. All killed. `TEST-BETA-git` I left alone, because it is yours and it is the one you need.
+
+## If the session had not been there
+
+Then the answer would have been that `.27` was still running an older copy. I can rule that out now: the file on `.27`, `.51` and `.13` are byte-identical and all contain the code that opens the session, and I proved the remote path works end to end from `.27` against a folder on `.13` before answering.
+
+Committed: `paperclip-harness` `bd0114a`, pushed, and the copies refreshed on all three machines.
+
+## Source paths observed
+
+- `home/sam/TEST-BETA`
+
+## Evidence
+
+- Confidence: 82%
+- Reason: Captured factual repo structure/configuration patterns from rich discovery
+
+## Related learned memories <!-- same-turn-2026-11-13 00:00:47 -->
+
+- session: [[packs/paperclip-harness/80-sessions/rich-discovery-nixos-2026-11-13-00-00-47|Rich discovery: nixos 2026-11-13 00:00:47]]
+- context: [[packs/paperclip-harness/20-context/home|nixos]]
+- observation: [[packs/paperclip-harness/60-observations/tmp-repository-structure-and-configuration-patterns|nixos repository structure and configuration patterns]]

.pi/memory-vault/packs/paperclip-harness/80-sessions/rich-discovery-nixos-2026-11-13-00-00-47.md

@@ -0,0 +1,105 @@
+---
+type: session
+id: session.paperclip-harness.rich-discovery-nixos-2026-11-13-00-00-47
+title: Rich discovery: nixos 2026-11-13 00:00:47
+status: active
+source_of_truth: false
+freshness: current
+last_reviewed: 2026-11-13
+tags:
+  - pack/paperclip-harness
+  - agent-memory/session
+  - autolearn
+  - rich-discovery
+  - repo/nixos
+---
+
+# Rich discovery: nixos 2026-11-13 00:00:47
+
+Sanitized rich discovery snapshot captured automatically from the completed turn.
+
+
+## Source paths observed
+
+- `home/sam/TEST-BETA`
+
+## Final answer snapshot
+
+It **did** work — the session exists. You did not get the output I expected, so let me show you both.
+
+## The session is there, on `.13`, right now
+
+```
+session: TEST-BETA-git
+  pane: git | cwd: /home/sam/TEST-BETA | running: lazygit
+```
+
+I checked it directly rather than trusting the output. Your staged files are there too:
+
+```
+A  .gitignore
+A  TEST0.md
+A  TEST1.md
+A  TEST2.md
+A  folder-0/TEST3.md
+branch main — no commits yet
+no .harness/  →  the project has not been created (correct)
+```
+
+So the next step is one command from `.27`:
+
+```sh
+tuios attach --host nixos-desktop TEST-BETA-git
+```
+
+That puts you in lazygit, in `/home/sam/TEST-BETA`, without ssh and without `cd`. Then `i` to ignore anything you do not want, `space` to stage or unstage, `c` to commit. Detach, and run the office command again — now that there is a commit it will create the project with worktrees, and no Y/N question.
+
+## Why the output confused you, and what I changed
+
+You were right that the text was wrong. The instruction to attach was printed **after** the lazygit key list, near the bottom — the keys looked like the next step, and the actual next step was buried. That is a fault in the wording order, not in the session creation.
+
+Now the first thing printed after your Y is the thing to do:
+
+```
+  EVERYTHING IS STAGED AND NOTHING IS COMMITTED. What you commit is what
+  the agent will be able to see, so check it before you commit.
+
+  A session called 'TEST-BETA-git' now holds lazygit in that folder.
+  Attach to it, stage and commit, then come back and repeat the command:
+
+      tuios attach --host nixos-desktop TEST-BETA-git
+
+  When you are done with it:  tuios kill-session TEST-BETA-git
+
+  In lazygit:
+      i      put the selected file or folder into .gitignore
+      space  stage or unstage        e  edit a file, .gitignore included
+      c      commit                  ?  every key
+```
+
+The `--host` part is added automatically when you are on a different machine from the folder.
+
+## Also cleaned up
+
+My testing had left four sessions on `.13` — `gitsess-git`, `gitsess4-git`, `gitsess5-git`, `gw2`, `remote-t-git`. All killed. `TEST-BETA-git` I left alone, because it is yours and it is the one you need.
+
+## If the session had not been there
+
+Then the answer would have been that `.27` was still running an older copy. I can rule that out now: the file on `.27`, `.51` and `.13` are byte-identical and all contain the code that opens the session, and I proved the remote path works end to end from `.27` against a folder on `.13` before answering.
+
+Committed: `paperclip-harness` `bd0114a`, pushed, and the copies refreshed 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 00:00:47 -->
+
+- session: [[packs/paperclip-harness/80-sessions/rich-discovery-nixos-2026-11-13-00-00-47|Rich discovery: nixos 2026-11-13 00:00:47]]
+- context: [[packs/paperclip-harness/20-context/home|nixos]]
+- observation: [[packs/paperclip-harness/60-observations/tmp-repository-structure-and-configuration-patterns|nixos repository structure and configuration patterns]]

bin/office

@@ -364,8 +364,6 @@ def run_on_remote(host, folder, opts):
         sys.stdout.write(out.stdout)
     if out.returncode != 0:
         raise h.Refused(3, "the other machine refused: %s" % (out.stderr or out.stdout).strip()[:300])
-    h.say("")
-    h.say("switch to it:  tuios attach --host %s %s" % (host, opts["session"] or os.path.basename(folder)))
     return 0
 
 
@@ -786,6 +784,14 @@ def main():
         sys.executable,
         [sys.executable, os.path.join(HERE, "board"), "--folder", folder],
     )
+    if code == 0:
+        # Only now is there a session worth attaching to. Promising one earlier
+        # is how a person ends up trying to attach to a session that was never
+        # created, because the project was still waiting for its first commit.
+        client = opts.get("client_host") or ""
+        h.say("")
+        h.say("switch to it:  tuios attach%s %s"
+              % (" --host " + client if client else "", session))
     return code