feat(platform): validate IBM Bob in real clients#656
Conversation
code-review-graph reviewOverall risk: 0.55 (MEDIUM) — 11 changed function(s)/class(es), 0 affected flow(s), 3 test gap(s) Risk-scored changes
Test gaps
Token savings: this graph-backed report used ~88,860 fewer tokens (~97%) than reading every changed file in full (estimated, chars/4 approximation). Powered by code-review-graph — local-first analysis; no code leaves the CI runner. |
Keep this draft unmerged until both Bob Shell and Bob IDE discover the generated MCP configuration, invoke code-review-graph successfully, and pass reinstall and uninstall checks in the real applications. Co-authored-by: mohan-kumar-m2 <243704502+mohan-kumar-m2@users.noreply.github.com>
479ea6f to
9f07ae4
Compare
rajpratham1
left a comment
There was a problem hiding this comment.
This pull request provides a well-structured addition of IBM Bob Shell and IBM Bob IDE platform support. The implementation introduces dedicated platform definitions, updates CLI platform selection, follows the documented mcpServers configuration format for both Bob clients, and adds appropriate auto-detection logic to avoid generating unnecessary configuration files. The documentation has been updated to reflect the new supported platforms, and the accompanying test suite thoroughly validates installation, detection, idempotency, configuration preservation, and CLI behavior. The implementation is consistent across the codebase, documentation, and tests, and no blocking issues were identified. LGTM and approved.
Latest refresh — 18 July 2026
Draft — do not merge until the real-client checks below pass.
This re-stages the safe IBM Bob portion of PR #540 after it was reverted from
mainbecause only automated configuration tests had been run. The original contributor remains credited.Change
Automated validation
git diff --check: cleanRequired real-client validation
Do not mark this ready or merge it until all items below are recorded with the released applications:
Carries the safe intent of PR #540 with
mohan-kumar-m2preserved as co-author.