chore: update @probelabs/probe to v0.6.0-rc206

[probelabs]

This PR updates @probelabs/probe to version v0.6.0-rc206.

Triggered by release: probelabs/probe@v0.6.0-rc206

Changes

• Updates @probelabs/probe dependency to v0.6.0-rc206

🤖 Auto-generated by release workflow

[probelabs]

PR Overview: Update @probelabs/probe to v0.6.0-rc206

Summary

This PR updates the @probelabs/probe dependency from version 0.6.0-rc204 to 0.6.0-rc206. This is a routine dependency update triggered by the release workflow, bringing in the latest release candidate of the Probe SDK.

Files Changed

• package.json: Updated @probelabs/probe version constraint from ^0.6.0-rc204 to ^0.6.0-rc206
• package-lock.json: Updated locked version and associated dependency metadata

Changes Analysis

Direct Changes

• @probelabs/probe: 0.6.0-rc204 → 0.6.0-rc206
• @probelabs/maid: 0.0.22 → 0.0.23 (transitive dependency update)

Impact Assessment

This is a low-risk, routine dependency update:

1. Version Type: Release candidate (rc) update within the same minor version (0.6.0)
2. Change Scope: Only dependency version declarations modified
3. Code Impact: No application code changes required
4. Breaking Changes: None expected within rc releases of the same minor version

Architecture & System Components

The @probelabs/probe package is a core dependency that provides:

• AI agent capabilities (ProbeAgent class)
• Tool execution framework (search, query, extract, delegate)
• MCP (Model Context Protocol) server integration
• Multi-provider AI support (Anthropic, OpenAI, Google, AWS Bedrock)

Component Relationship:

graph LR
    A[Visor Application] --> B[AIReviewService]
    B --> C["@probelabs/probe"]
    C --> D[ProbeAgent]
    D --> E[AI Providers]
    D --> F[Tool Execution]
    D --> G[MCP Servers]
    
    style C fill:#f9f,stroke:#333,stroke-width:2px
    style D fill:#bbf,stroke:#333,stroke-width:2px

Loading

Scope Discovery & Context

Affected Modules:

• src/ai-review-service.ts - Primary consumer of ProbeAgent
• src/providers/ai-check-provider.ts - AI provider configuration
• src/providers/mcp-check-provider.ts - MCP integration
• Test files in tests/unit/ and tests/integration/

Integration Points:

• Session management (src/session-registry.ts)
• Debug tracing (src/utils/tracer-init.ts)
• Configuration system (src/config.ts)

Testing Considerations:

• Unit tests mock @probelabs/probe via __mocks__/@probelabs/probe.ts
• Integration tests may exercise real ProbeAgent functionality
• E2E tests for MCP integration should be verified

Review Guidance

Key Areas to Verify:

1. Compatibility: Ensure rc206 maintains API compatibility with rc204
2. Test Suite: Run full test suite to catch any behavioral changes
3. MCP Integration: Verify MCP server connections still function correctly
4. Session Management: Test session reuse and cloning functionality

Potential Risks:

• RC releases may contain bug fixes or behavioral changes
• Transitive dependency updates (@probelabs/maid) could affect tool execution
• MCP protocol handling may have been updated

Recommendations

1. Merge Confidence: High - This is a standard dependency update within the same minor version
2. Testing Priority: Medium - Run integration tests, especially for AI and MCP functionality
3. Deployment: Safe to deploy after test validation
4. Monitoring: Watch for any AI-related issues in production post-deployment

---

Generated by: PR overview automation
Trigger: Release workflow for probelabs/probe@v0.6.0-rc206

Metadata

• Review Effort: 1 / 5
• Primary Label: chore

---

Powered by Visor from Probelabs

Last updated: 2026-01-31T16:39:10.242Z | Triggered by: pr_opened | Commit: d472ef5

💡 TIP: You can chat with Visor using /visor ask <your question>

[probelabs]

✅ Security Check Passed

No security issues found – changes LGTM.

✅ Architecture Check Passed

No architecture issues found – changes LGTM.

✅ Performance Check Passed

No performance issues found – changes LGTM.

Quality Issues (5)

Severity	Location	Issue
🟠 Error	package.json:100	Dependency update lacks integration test verification. The E2E tests (tests/e2e/mcp-probe-e2e.test.ts) that use the real @probelabs/probe package are not being run to validate compatibility with version 0.6.0-rc206. This risks introducing breaking changes that only surface in production. 💡 Suggestion Run E2E tests against the new version before merging. Add a CI check that runs tests/integration/* and tests/e2e/* on dependency updates. Consider adding a smoke test that verifies basic ProbeAgent functionality works with the new version.
🟡 Warning	package.json:100	No changelog or release notes provided for @probelabs/probe version 0.6.0-rc204 → 0.6.0-rc206. Without understanding what changed, it's impossible to assess risk or prepare for breaking changes. The transitive dependency @probelabs/maid also updated from 0.0.22 → 0.0.23 without explanation. 💡 Suggestion Include release notes or changelog links in the PR description. Document what changed between rc204 and rc206, especially any breaking changes or new features. For transitive dependencies, explain why they were updated.
🟡 Warning	package.json:100	Automated dependency update without corresponding test updates or validation. The codebase has known issues where it passes unsupported options (allowedTools, disableTools) to ProbeAgent via type casting (src/ai-review-service.ts:1830-1837), but this update doesn't verify if those issues are resolved in the new version. 💡 Suggestion Add a test that verifies ProbeAgent actually supports the options being passed to it. Check if rc206 adds support for allowedTools/disableTools and update code accordingly. Document which ProbeAgent features are actually supported vs. silently ignored.
🟡 Warning	package.json:100	Dependency update uses caret ranges (^0.6.0-rc206) which allows automatic patch updates. If rc206 introduces breaking changes, there's no easy rollback mechanism and future patch versions could auto-update and break the application. 💡 Suggestion Consider pinning to exact version (0.6.0-rc206) for better stability, or implement automated testing that runs on all dependency updates. Add a CI check that prevents merging if tests fail after dependency updates. 🔧 Suggested Fix "@probelabs/probe": "0.6.0-rc206"
🟡 Warning	package-lock.json:5974	No negative tests for dependency update failures. The update doesn't include tests for scenarios like: ProbeAgent API incompatibilities, missing methods, changed behavior in tool execution, or MCP server integration failures. 💡 Suggestion Add tests that verify graceful degradation when ProbeAgent has issues. Test scenarios: missing ProbeAgent methods, incompatible API changes, timeout handling, and MCP server connection failures. Ensure the application provides helpful error messages when dependency updates break functionality.

---

Powered by Visor from Probelabs

Last updated: 2026-01-31T16:39:12.771Z | Triggered by: pr_opened | Commit: d472ef5

💡 TIP: You can chat with Visor using /visor ask <your question>