go-safe-move-refactor

Copy the file to the destination package, update its package declaration and imports, then add forwarding stubs (type aliases and variable forwarding) in the original package. Verify go build ./... passes after each step before updating consumers and removing stubs.

Drop the domain prefix since the package name provides the namespace, for example BranchCreateInput becomes CreateInput in the branches package. Keep type aliases in the source package temporarily so existing references like tools.BranchCreateInput still compile.

Extract the shared dependency into a separate utility package such as internal/toolutil so both the original and new packages import it instead of each other. This converts a circular tools-branches-tools chain into two clean one-way dependencies.

Copy the test file to the destination, change its package declaration, and update type and function references to the new names. Replace local helpers like newTestClient with shared testutil functions such as testutil.NewTestClient and testutil.RespondJSON instead of duplicating them.

Forwarding stubs are temporary bridges and should be deleted once all consumers import the new package directly and all tests pass. Keeping them long-term hides the real dependency graph and prevents the compiler from flagging stale references.