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

[probelabs]

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

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

Changes

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

🤖 Auto-generated by release workflow

[probelabs]

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

Summary

This PR updates the @probelabs/probe dependency from version v0.6.0-rc245 to v0.6.0-rc247. This is a routine dependency update within the 0.6.0 release candidate series.

Files Changed

• package.json: Updated @probelabs/probe version constraint from ^0.6.0-rc245 to ^0.6.0-rc247
• package-lock.json: Updated lockfile with new package versions and integrity hashes

Dependency Updates

Direct Dependencies

• @probelabs/probe: 0.6.0-rc245 → 0.6.0-rc247

Transitive Dependencies

• @probelabs/maid: 0.0.24 → 0.0.25 (dependency of @probelabs/probe)

Architecture & Impact Assessment

What This PR Accomplishes

This is a dependency maintenance update that brings in the latest release candidate of the Probe library. The update is within the same minor version (0.6.0-rc series), indicating it contains bug fixes and minor improvements rather than breaking changes.

Key Technical Changes

The @probelabs/probe library is a core dependency used throughout the codebase:

1. AI Review Service (src/ai-review-service.ts): Uses ProbeAgent and ProbeAgentOptions for AI-powered code review
2. Diff Processing (src/utils/diff-processor.ts): Uses the extract utility for parsing diffs
3. Tracer Initialization (src/utils/tracer-init.ts): Uses SimpleTelemetry and SimpleAppTracer for debugging/tracing
4. Session Management (src/session-registry.ts): Extends ProbeAgent with tracing capabilities
5. Engine Context (src/state-machine/context/build-engine-context.ts): Uses DelegationManager for managing concurrent AI operations

Affected System Components

graph TD
    A[Probe Library Update] --> B[AI Review Service]
    A --> C[Diff Processor]
    A --> D[Tracer/Telemetry]
    A --> E[Session Registry]
    A --> F[Delegation Manager]
    
    B --> G[Code Review Workflows]
    C --> H[PR Analysis]
    D --> I[Debug Artifacts]
    E --> J[Session Management]
    F --> K[Concurrency Control]

Loading

Risk Assessment

Low Risk - This is a minor version bump within the same release candidate series (rc245 → rc247). Based on the codebase usage:

• The code uses stable, public APIs from Probe (ProbeAgent, extract, SimpleTelemetry, DelegationManager)
• No custom or experimental APIs are referenced
• The update includes a transitive dependency update (@probelabs/maid 0.0.24 → 0.0.25), which is also a minor patch update

Scope Discovery & Context Expansion

Related Files to Monitor

Based on the dependency analysis, these files directly import from @probelabs/probe:

1. Core Integration Points:

   • src/ai-review-service.ts - Main AI review orchestration
   • src/utils/diff-processor.ts - Diff parsing utilities
   • src/utils/tracer-init.ts - Tracing/telemetry setup
   • src/session-registry.ts - Session lifecycle management
   • src/state-machine/context/build-engine-context.ts - Delegation management

2. Test Infrastructure:

   • __mocks__/@probelabs/probe.ts - Mock implementations for testing

3. Build Scripts:

   • scripts/inject-version.js - Version injection logic

Recommended Verification

Since this affects AI operations, consider verifying:

• CI/CD pipeline tests pass (especially AI review tests)
• No regressions in diff processing
• Tracing/telemetry still functions correctly in debug mode
• Delegation limits and concurrency controls work as expected

Labels

• Type: chore - Dependency maintenance update
• Review Effort: 1/5 - Automated dependency update with low risk

Metadata

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

---

Powered by Visor from Probelabs

Last updated: 2026-02-18T15:59:09.827Z | Triggered by: pr_opened | Commit: 264c734

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

[probelabs]

✅ Security Check Passed

No security issues found – changes LGTM.

Architecture Issues (2)

Severity	Location	Issue
🟡 Warning	package.json:105	Using caret (^) versioning with pre-release software allows automatic updates to newer release candidates, which may introduce breaking changes. Consider pinning to exact version for pre-release dependencies. 💡 Suggestion Consider using exact version pinning for pre-release dependencies: "@probelabs/probe": "0.6.0-rc247" instead of "@probelabs/probe": "^0.6.0-rc247" to prevent automatic updates to potentially incompatible rc versions.
🟡 Warning	package.json:105	Dependency update from rc245 to rc247 lacks changelog review documentation. The codebase has a WORKAROUND comment in tracer-init.ts indicating the probe API is evolving, making changelog review important. 💡 Suggestion Review the @probelabs/probe changelog between v0.6.0-rc245 and v0.6.0-rc247 to identify any breaking changes, especially related to SimpleAppTracer, SimpleTelemetry, or the recordEvent method mentioned in the WORKAROUND at visor/src/utils/tracer-init.ts:75-78.

✅ Performance Check Passed

No performance issues found – changes LGTM.

Quality Issues (3)

Severity	Location	Issue
🟢 Info	package.json:105	The dependency uses a release candidate version (^0.6.0-rc247). While this is intentional for testing pre-release features, it carries higher risk than stable releases. The automated update from rc245 to rc247 suggests frequent changes in the RC series. 💡 Suggestion Consider pinning to a specific RC version (remove the ^) if you need strict control over which RC is used, or document why this RC series is acceptable for production use. Monitor the @probelabs/probe repository for the stable 0.6.0 release and plan to upgrade once available.
🟡 Warning	package.json:105	Dependency update from @probelabs/probe v0.6.0-rc245 to v0.6.0-rc247 lacks integration test coverage with the actual dependency. The existing tests in tests/unit/mermaid-escaping-test.test.ts and tests/unit/mermaid-production-scenario.test.ts use jest.mock() to mock the ProbeAgent class, which means they won't catch breaking API changes in the updated dependency. While tests/e2e/mcp-probe-e2e.test.ts does execute the actual binary via npx, it only tests the MCP transport interface, not the direct ProbeAgent SDK usage in src/ai-review-service.ts. 💡 Suggestion Add an integration test that imports and instantiates the actual @probelabs/probe ProbeAgent class (not mocked) to verify basic API compatibility after dependency updates. This test should call initialize() and a simple answer() method to ensure the SDK interface hasn't changed in a breaking way. Consider adding this to a new tests/integration/probe-sdk-integration.test.ts file.
🟡 Warning	package.json:105	Transitive dependency @probelabs/maid updated from 0.0.24 to 0.0.25 as part of the @probelabs/probe update. While this is typically safe, there is no test coverage that verifies this transitive dependency's functionality. The codebase imports from @probelabs/probe but @probelabs/maid is a dependency of that package, so changes could affect behavior. 💡 Suggestion Review the changelog for @probelabs/maid v0.0.25 to identify any breaking changes or behavioral modifications. If @probelabs/maid's API affects your code's behavior (e.g., through DelegationManager or other exported types), consider adding tests that verify the expected behavior after the update.

---

Powered by Visor from Probelabs

Last updated: 2026-02-18T15:59:14.152Z | Triggered by: pr_opened | Commit: 264c734

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