CB-624: add scripts/rename-checkout.sh (rename checkout claude-bridge -> fleetd) #143
Reference in New Issue
Block a user
Delete Branch "worker/cb-624-script-ff7bc2-3"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Implements unit A of CB-624 / issue #128.
What: one new script,
scripts/rename-checkout.sh, modeled onredeploy-bridged.sh.--check(read-only) reports all five surfaces: files in the checkout holding the old absolute path (with hit counts), the installed launchd plist and its ProgramArguments, the Claude Code project-state dirs at old and new slug, git worktrees whose.gitpointer names the old path, and the running daemon with its jar path.launchctl unloadwhen supervised, plain kill otherwise), waits for real process exit; moves the checkout; moves the Claude Code project-state dir using slugs derived from both paths viatr '/.' '-'; rewrites each worktree's.gitpointer found through.git/worktrees/*/gitdir; rewrites gitignoredbridged/bridged.yamland the installed plist if they exist (backups kept,plutil -lintafter the plist); restarts (launchctl load when supervised) and verifies /healthz plus a FRESHbridged listeningline anchored to a line-count marker taken before the stop. Ends by listing references it deliberately left alone.Checks run:
bash -npasses; shellcheck is not installed on this machine so it could not run;--checkexecuted for real against the live machine (output in the worker report). Apply mode was NOT executed — it would move the running system out from under the fleet, per the ticket's hard limits.Untested branch, stated plainly: the bridged.yaml rewrite path could not be exercised from a worktree (the file is gitignored and exists only in the live checkout). The code path is written but unverified.