[Bala (0xba1a)]

Summary

Tool YAML command fields (install_commands, verify_commands, setup_commands, uninstall_commands) can now be distro-specific. Microbots picks the right commands from the sandbox's /etc/os-release, so the same tool definition can support several sandbox images. The sandbox's distribution is never configured separately.

This is the second PR in the stack, following #202 (stock MCR images prepared on the fly).

Format

Each *_commands field accepts either form:

• A list: generic commands that run on every distro. This is the existing format, so existing YAMLs keep working unchanged.
• A map: keys are distro IDs from /etc/os-release (for example debian or azurelinux) and/or generic.

install_commands:
  debian:
    - apt-get update
    - apt-get install -y tesseract-ocr
  azurelinux:
    - tdnf install -y tesseract
verify_commands:          # a list applies to every distro
  - tesseract --version

Resolution

For a map, Microbots reads the sandbox's /etc/os-release:

• Known distro: its ID wins, then its ID_LIKE entries (so debian also covers Ubuntu), then generic.
• Known distro, no match: the tool fails with UnsupportedDistroError before any command runs, and the error says which entry to add.
• Distro can't be detected: Microbots logs a warning and runs generic, or the first entry if there's no generic. A failing command is the last resort.

Changes

• Environment.get_distro_ids() reads and caches the sandbox's /etc/os-release (ID, then ID_LIKE).
• ToolAbstract.resolve_commands() selects the commands. Map keys are validated (no empty or duplicate keys) and lower-cased.
• Internal tools resolve against the sandbox; external tools resolve against the host's /etc/os-release (new microbots.utils.os_release).
• cscope, browser-use and the tesseract docs example use apt-get, so their commands are now keyed to debian. Their behaviour on the default Debian image is unchanged.
• Docs: the custom tool walkthrough describes the format and resolution rules.

Testing

• New test/tools/test_distro_commands.py covers resolution order, the unknown-distro fallback, the UnsupportedDistroError message, key validation, os-release parsing and caching, and internal/external tool wiring. Unit tests: 705 passed. The 6 failures in test_microbot.py::TestMicrobotUnit and 4 errors in test_memory_tool_integration.py also occur on main and come from my local environment.
• Live checks on the stock images:
  • mcr.microsoft.com/devcontainers/python:3.11: detected ['debian'], and cscope.yaml installed and verified.
  • With /etc/os-release removed: the tool fell back to its first entry with a warning.
  • mcr.microsoft.com/azurelinux/base/core:3.0: detected ['azurelinux'], and cscope.yaml was rejected with UnsupportedDistroError before running anything.

Upcoming PRs in this stack

1. refactor(env): run stock MCR images, prepare the sandbox on the fly #202 (merged): stock MCR images prepared on the fly.
2. This PR: distro-aware tool commands.
3. Azure Linux 3 sandbox (AZURELINUX_IMAGE), with an image option on the bots.
4. Optional root_access for the sandbox shell.
5. rpm / mock / azldev tool definitions.
6. CopilotBot session_options and skill tracking, so it can use a repository's agent skills.

[Codecov Comments Bot (codecov-commenter)]

Codecov Report

❌ Patch coverage is 98.91304% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 77.03%. Comparing base (0dc77c8) to head (049f40a).

Files with missing lines	Patch %	Lines
src/microbots/tools/tool.py	97.43%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #205      +/-   ##
==========================================
+ Coverage   76.48%   77.03%   +0.55%     
==========================================
  Files          46       47       +1     
  Lines        3113     3192      +79     
==========================================
+ Hits         2381     2459      +78     
- Misses        732      733       +1     

Flag	Coverage Δ
ghcp	31.76% <34.78%> (+0.06%)	⬆️
integration	42.16% <71.73%> (+0.79%)	⬆️
ollama_local	34.27% <71.73%> (+0.99%)	⬆️
slow-browser	18.42% <34.78%> (+0.39%)	⬆️
slow-other	39.12% <53.26%> (+0.48%)	⬆️
unit	74.06% <98.91%> (+0.62%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
src/microbots/environment/Environment.py	100.00% <100.00%> (ø)
src/microbots/tools/external_tool.py	100.00% <100.00%> (ø)
src/microbots/tools/internal_tool.py	97.75% <100.00%> (+0.10%)	⬆️
src/microbots/utils/os_release.py	100.00% <100.00%> (ø)
src/microbots/tools/tool.py	98.71% <97.43%> (-1.29%)	⬇️

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Kavya Sree Kaitepalli (KavyaSree2610)]

LGTM