PR #30562 runtime verification main: 3368dd70f2, separate /home/user/main worktree PR: c42609dedad8a5d1f6ac714e225e14793c8cc27e, /home/user/t3code Both installed with vp i. One dev server at a time, separate .t3 data. main server 16733, web 8693; PR server 13773, web 5733. Browser: repository Playwright 1.60.0, /usr/bin/google-chrome. Created real git repository /home/user/cli-verification/old-app. Added it through the web client's Add project > Local folder. Selected Codex gpt-6.1-sol, sent a real prompt through the web composer. main and PR both returned CLI_VERIFY_OK through the real local proxy. Moved the repository to old-app-retained, leaving the stored workspace absent. CLI commands used node /apps/server/src/bin.ts and explicit --base-dir /.t3. Ran from /home/user/cli-verification against the running server. MAIN $ t3 project rename old-app renamed-relative ProjectNotFoundError: No active project found for 'old-app'. exit=1 $ t3 project rename /home/user/cli-verification/old-app/ renamed-trailing ProjectNotFoundError: No active project found for '/home/user/cli-verification/old-app/'. exit=1 $ t3 project remove old-app ProjectNotFoundError: No active project found for 'old-app'. exit=1 $ t3 project remove /home/user/cli-verification/old-app/ ProjectNotFoundError: No active project found for '/home/user/cli-verification/old-app/'. exit=1 $ t3 project rename /home/user/cli-verification/old-app renamed-absolute Renamed project 8209acf5-3550-461f-819a-b42c2e461caa to renamed-absolute. exit=0 PR HEAD $ t3 project rename old-app renamed-relative Renamed project 441c0774-2723-484b-aa7f-99be084920e1 to renamed-relative. exit=0 $ t3 project rename /home/user/cli-verification/old-app/ renamed-trailing Renamed project 441c0774-2723-484b-aa7f-99be084920e1 to renamed-trailing. exit=0 Both changes appeared in the already-open browser without reload. $ t3 project remove old-app Server rejected invalid_command. exit=1. Project and real thread remained visible. $ t3 project remove /home/user/cli-verification/old-app/ Server rejected invalid_command. exit=1. Project and real thread remained visible. After restoring the repository, the same thread accepted a second real Codex turn: CLI_FOLLOWUP_OK. No conversation loss from renaming or refused removal. Moved the repository away again before the recorded renames and forced removal. $ t3 project remove old-app --force Removed project 441c0774-2723-484b-aa7f-99be084920e1 (renamed-trailing). exit=0 The project and thread disappeared from the web client, leaving the unrelated server thread. EMPTY PROJECTS, REAL GIT REPOSITORIES ADDED WITH THE APP CLI $ t3 project add empty-relative Added project cff434af-e39d-4318-a336-57b3fa35bd47 (empty-relative). $ t3 project rename empty-relative empty-relative-existing Renamed project cff434af-e39d-4318-a336-57b3fa35bd47 to empty-relative-existing. Moved its folder away. $ t3 project remove empty-relative Removed project cff434af-e39d-4318-a336-57b3fa35bd47 (empty-relative-existing). exit=0 $ t3 project remove /home/user/cli-verification/empty-trailing/ Removed project d7375c1a-c39d-45e2-bf6c-dc3592063c93 (empty-trailing-existing). exit=0 $ t3 project remove 77cab71d-ec30-48e9-8770-a0292b7becdd Removed project 77cab71d-ec30-48e9-8770-a0292b7becdd (empty-id-existing). exit=0 Each removed project's ID then failed rename with ProjectNotFoundError. Missing-folder rename by exact ID and literal ~/cli-verification/old-app/ both succeeded. An unregistered identifier still failed with ProjectNotFoundError. Focused existing checks through blacksmith-check: vp i && vp test run apps/server/src/cli/project.test.ts 1 test file passed; 13 tests passed. GitHub checks on the exact head: all completed checks green (some unrelated checks skipped). No source changes required.