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

[probelabs]

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

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

Changes

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

🤖 Auto-generated by release workflow

[probelabs]

{"text":"# PR Overview: Update @probelabs/probe to v0.6.0-rc175

Summary

This PR updates the @probelabs/probe dependency from version 0.6.0-rc173 to 0.6.0-rc175, bringing in the latest release candidate improvements and bug fixes from the Probe ecosystem.

Files Changed Analysis

• package.json: Updated main dependency version reference
• package-lock.json: Updated dependency lock file with version changes and updated transitive dependency @probelabs/maid from 0.0.21 to 0.0.22

Architecture & Impact Assessment

What this PR accomplishes

• Updates the core ProbeAgent SDK dependency to the latest release candidate
• Includes transitive dependency updates for improved stability
• Maintains compatibility with existing Visor functionality

Key technical changes introduced

• Version bump: @probelabs/probe 0.6.0-rc173 → 0.6.0-rc175
• Transitive update: @probelabs/maid 0.0.21 → 0.0.22
• Updated package integrity hashes for security verification

Affected system components

• AI Review Service: Uses ProbeAgent for code analysis and review
• MCP Provider: Integrates with Probe for Model Context Protocol operations
• Session Registry: Manages ProbeAgent instances for session reuse
• Diff Processor: Utilizes Probe binary for enhanced diff processing```mermaid
  graph TD
  A[Visor Core] --> B[AI Review Service]
  A --> C[MCP Provider]
  B --> D[ProbeAgent SDK]
  C --> D
  D --> E["@probelabs/maid"]
  A --> F[Diff Processor]
  F --> G[Probe Binary]
  D --> H[Session Registry]

    D --> H[Session Registry]

Scope Discovery & Context Expansion

Based on the search results, this dependency update impacts:

Primary Integration Points

• src/ai-review-service.ts: Core AI functionality using ProbeAgent
• src/session-registry.ts: Session management for ProbeAgent instances
• src/utils/diff-processor.ts: Enhanced diff processing with Probe binary
• src/utils/tracer-init.ts: Telemetry and tracing initialization

Configuration and Documentation

• MCP provider configurations throughout docs/ reference @probelabs/probe@latest
• Workshop materials and examples reference Probe CLI usage
• Mock files in __mocks__/@probelabs/probe.ts for testing

Testing Considerations

• Jest configuration includes module mapping for Probe mocks
• Integration tests may need verification with new SDK version
• CLI version detection scripts reference Probe package version

The update appears to be a routine dependency bump within the same release candidate series, suggesting minimal breaking changes while incorporating bug fixes and improvements from the Probe ecosystem.","tags":{"review-effort":1,"label":"chore"}}

---

Powered by Visor from Probelabs

Last updated: 2025-11-28T18:55:51.471Z | Triggered by: pr_opened | Commit: b486af8

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

[probelabs]

✅ Security Check Passed

No security issues found – changes LGTM.

Architecture Issues (4)

Severity	Location	Issue
🟢 Info	package-lock.json:5945	Transitive dependency @probelabs/maid updated from 0.0.21 to 0.0.22. This dependency is used by probe and may introduce changes that affect probe's functionality. 💡 Suggestion Monitor for any behavioral changes in probe's diff processing or MCP functionality that may be related to the maid dependency update.
🟡 Warning	package.json:99	Dependency update within RC series may introduce breaking changes to ProbeAgent API workarounds. The codebase has multiple workarounds for missing features (disableTools, allowedTools) that could be affected by API changes. 💡 Suggestion Verify that existing workarounds in ai-review-service.ts still function correctly with the new probe version. Consider adding integration tests to validate ProbeAgent behavior after dependency updates.
🟡 Warning	src/utils/diff-processor.ts:23	Hardcoded paths to probe-binary are fragile and may break with dependency updates. The multiple fallback path strategy indicates structural dependency on probe's internal binary layout. 💡 Suggestion Consider using a more robust binary discovery mechanism or add runtime validation that the probe binary is functional before use. The current approach may fail if probe's internal structure changes.
🟡 Warning	src/ai-review-service.ts:23	Comments indicate probe 'removed' AppTracer and TelemetryConfig, suggesting API volatility. The tracing integration relies on specific probe exports that may change. 💡 Suggestion Add runtime checks for the availability of SimpleTelemetry and SimpleAppTracer classes. Consider implementing a more abstract tracing interface that can handle probe API changes.

✅ Performance Check Passed

No performance issues found – changes LGTM.

Quality Issues (6)

Severity	Location	Issue
🟢 Info	PROBE_API_INVESTIGATION.md:9	Documentation shows that disableTools and allowedTools options are passed to ProbeAgent but silently ignored. This version update might change this behavior, potentially breaking existing configurations that depend on the current (non-working) behavior. 💡 Suggestion Verify if the new probe version addresses the known API issues. Update documentation and configuration validation accordingly. Add tests to verify tool filtering behavior works as expected.
🟡 Warning	package.json:99	Dependency update from @probelabs/probe@0.6.0-rc173 to v0.6.0-rc175 without corresponding test updates or validation. The codebase has extensive integration with ProbeAgent but lacks comprehensive unit tests to detect API breaking changes. 💡 Suggestion Add integration tests to validate ProbeAgent API compatibility after dependency updates. Test core functionality including session management, diff processing, and tracing initialization.
🟡 Warning	src/ai-review-service.ts:1	AIReviewService heavily depends on ProbeAgent API but lacks tests to verify compatibility. The version update could break core functionality like session reuse, tool filtering, and schema validation. 💡 Suggestion Add unit tests for AIReviewService that mock ProbeAgent and verify critical integration points: constructor options, answer() method calls, session cloning, and cleanup functionality.
🟡 Warning	__mocks__/@probelabs/probe.ts:1	ProbeAgent mock is too basic to catch API breaking changes. It only mocks constructor and answer() method, but the codebase uses additional features like session cloning, tracing, and cleanup methods. 💡 Suggestion Enhance the mock to include ProbeAgent methods used in the codebase: clone(), cleanup(), getTokenUsage(), and tracing properties. Add tests that verify these integrations work correctly.
🟡 Warning	src/utils/diff-processor.ts:1	Diff processor directly imports and uses the 'extract' function from @probelabs/probe. Version update could break diff processing functionality if the extract API changed. 💡 Suggestion Add unit tests for processDiffWithOutline function that mock the extract function and verify it handles different diff formats and error conditions correctly.
🟡 Warning	src/utils/tracer-init.ts:28	Tracer initialization uses dynamic imports of @probelabs/probe with fallback patterns. Version update could break telemetry functionality if module structure changed. 💡 Suggestion Add tests for initializeTracer function that verify both ESM and CJS import patterns work correctly and handle missing telemetry classes gracefully.

---

Powered by Visor from Probelabs

Last updated: 2025-11-28T18:55:54.109Z | Triggered by: pr_opened | Commit: b486af8

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