zmuxuny opened a new pull request, #6753: URL: https://github.com/apache/rocketmq-dashboard/pull/6753
### Which Issue(s) This PR Fixes Fixes #6749 ### Brief Description Bind explicit relative --command paths when generating an MCP client snippet, so a client launched from another directory selects the same executable. Bare names retain client PATH lookup; absolute paths retain their exact spelling. POSIX prefixes the generation directory without cleaning symlink/.. components; native Windows resolution handles drive-relative/rooted paths. No credential/config content is read or executable launched. Distinct from #6460 (the separate --config file path) and #5916 (missing instance argument). ### How Did You Test This Change? - Three relative-path regressions fail on a92c2314 after changing client cwd: ./rmqctl, path with spaces, ../rmqctl. - Controls cover bare names, clean/non-clean absolute paths, and POSIX symlink-parent identity with os.Stat/SameFile, without process execution. - Go1.27.1 Linux: `GOMAXPROCS=2 go test -race -p 1 -count=1 ./...`: all packages pass. - `go vet -p 1 ./...`, gofmt, `git diff --check`: pass. - Independent source review caught absolute-path cleaning before publication. - Windows execution, external client launch and multi-platform build not run locally. No Java/web changes. ### Checklist - [x] One coherent path binding fix - [x] Conventional Commit subject - [x] Regression tests and ASF header - [x] No dependency or workflow changes AI-assisted implementation and tests, independently reviewed. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
