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

[probelabs]

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

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

Changes

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

🤖 Auto-generated by release workflow

[probelabs]

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

Summary

This PR updates the @probelabs/probe dependency from version 0.6.0-rc226 to 0.6.0-rc227. This is a routine dependency update triggered by the Probe release workflow.

Files Changed

• package.json: Updated @probelabs/probe version constraint from ^0.6.0-rc226 to ^0.6.0-rc227
• package-lock.json: Updated the locked version, integrity hash, and tarball URL for the @probelabs/probe package

Stats: 2 files changed, 5 additions, 5 deletions

Architecture & Impact Assessment

What This PR Accomplishes

This is a dependency update that brings in the latest release candidate of the Probe SDK. The update is minimal in scope and follows the established pattern of Probe dependency updates.

Key Technical Changes

• Version bump: 0.6.0-rc226 → 0.6.0-rc227
• Integrity hash update: New SHA-512 hash for package verification
• No breaking changes: The update maintains the same major/minor version (0.6.0)

Affected System Components

The @probelabs/probe package is used throughout the Visor codebase:

1. Core AI Review Service (src/ai-review-service.ts): Imports ProbeAgent and ProbeAgentOptions types
2. Diff Processing (src/utils/diff-processor.ts): Uses the extract function from Probe
3. MCP Integration: Multiple test files use Probe's MCP server via npx -y @probelabs/probe mcp
4. Version Detection (src/index.ts, scripts/inject-version.js): Dynamically reads Probe version for logging

Component Relationships

graph TD
    A[Visor CLI/Action] --> B[AI Review Service]
    B --> C[ProbeAgent]
    A --> D[Diff Processor]
    D --> E[Probe extract]
    A --> F[MCP Provider]
    F --> G[Probe MCP Server]
    H[Test Suite] --> C
    H --> E
    H --> G
    
    style C fill:#f9f,stroke:#333,stroke-width:2px
    style E fill:#f9f,stroke:#333,stroke-width:2px
    style G fill:#f9f,stroke:#333,stroke-width:2px

Loading

Scope Discovery & Context Expansion

Immediate Impact

The update affects:

• Runtime behavior: Any changes in Probe's ProbeAgent class or extract function
• MCP server behavior: Changes to Probe's MCP server implementation
• Test mocks: Jest mocks in __mocks__/@probelabs/probe.ts may need verification

Related Files to Verify

Based on the search results, these files directly consume Probe:

1. Core imports:

   • src/ai-review-service.ts - Main AI review logic
   • src/utils/diff-processor.ts - Diff extraction utilities

2. Test files (may need mock updates if Probe API changed):

   • tests/unit/ai-review-service.test.ts
   • tests/unit/session-registry.test.ts
   • tests/unit/mermaid-production-scenario.test.ts
   • tests/integration/session-reuse-integration.test.ts
   • tests/integration/ai-custom-tools-integration.test.ts
   • tests/e2e/mcp-probe-e2e.test.ts

3. Configuration:

   • jest.config.js - Module mapper for Probe mocks
   • __mocks__/@probelabs/probe.ts - Mock implementation

Recommended Verification Steps

1. Run the full test suite to ensure compatibility with the new Probe version
2. Verify MCP integration tests pass (they invoke Probe via npx)
3. Check that version detection logic correctly reports the new version
4. Review Probe's changelog for v0.6.0-rc227 to identify any behavioral changes

Risk Assessment

Low Risk: This is a patch-level update within the same release candidate series. The change is limited to dependency version strings with no code modifications required in Visor itself.

Review Focus Areas:

• Test suite compatibility
• MCP server integration
• Version reporting in logs

Metadata

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

---

Powered by Visor from Probelabs

Last updated: 2026-02-06T17:37:28.766Z | Triggered by: pr_opened | Commit: cb345d8

💡 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 (4)

Severity	Location	Issue
🟢 Info	src/utils/tracer-init.ts:73	Code contains a workaround for missing recordEvent method in SimpleAppTracer (probe #321). This workaround may need validation with rc227 in case the method was added or the API changed. 💡 Suggestion Verify if rc227 added the recordEvent method to SimpleAppTracer. If so, the workaround can be removed. If not, consider adding a comment tracking when this workaround can be removed.
🟢 Info	package.json:100	Automated dependency update without changelog verification. The PR description doesn't indicate whether breaking changes, new features, or deprecations were reviewed. 💡 Suggestion Enhance the release workflow to include changelog extraction or breaking change detection for dependency updates. This would help identify if code changes are needed when updating dependencies.
🟡 Warning	package.json:100	Dependency update from @probelabs/probe@0.6.0-rc226 to 0.6.0-rc227 lacks verification of backward compatibility. The codebase uses ProbeAgent extensively with specific options (promptType, allowEdit, tracer, mcpConfig, etc.) and has workarounds for missing methods (recordEvent). Without reviewing rc227's changelog or release notes, there's risk of breaking changes. 💡 Suggestion Review the @probelabs/probe release notes for v0.6.0-rc227 to verify no breaking changes to the ProbeAgent API, options interface, or telemetry classes. Pay special attention to the workaround in tracer-init.ts that adds recordEvent to SimpleAppTracer.
🟡 Warning	package.json:100	Tests mock @probelabs/probe using jest.mock(), which means API changes in the actual dependency may not be caught by tests. The mock in ai-review-service.test.ts may not reflect rc227's actual API. 💡 Suggestion Consider adding integration tests that use the actual ProbeAgent dependency (not mocked) to verify compatibility. Alternatively, review and update the mock implementation to match rc227's API if there were changes.

---

Powered by Visor from Probelabs

Last updated: 2026-02-06T17:37:32.424Z | Triggered by: pr_opened | Commit: cb345d8

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