zes-bugfix-sweep

Automated bug triage for ZES Orchestration System services evaluates issue reports against live service states and logs to verify root causes before applying targeted code patches. It systematically checks components like claude-oc, MCP servers, and sub-agent pipelines to ensure high-confidence remediation.

Fixing service-level bugs in sub-agent pipelines and MCP servers requires live state verification against local repository logs to confirm the root cause. This approach applies narrow code patches that follow established system patterns, ensuring fixes are verified and preventing regressions across core services.

Automated triage verifies claude-oc proxy connectivity issues by checking the live service status and evaluating the specific port against issue reports. It cross-references local repository logs to confirm the root cause before guiding the agent to apply a targeted, verifiable fix.

Yes, patching ZES components like 9Router and Hermes requires access to system service managers and local repository logs. This access enables the workflow to perform live state verification, ensuring high-certainty bug resolution and preventing regressions during the remediation process.

To start a bugfix sweep for ZES core services, you initiate the process by providing a list of issue references or pull request links. The system then automates the investigation, verifying live states and applying focused patches to resolve the identified bugs.

Targeted code patching for orchestration system services ensures that fixes remain narrow and follow established system patterns, preventing regressions. By verifying live service states and repository logs before modifying code, this approach guarantees high-confidence, verifiable bug resolution across core components.