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

[probelabs]

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

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

Changes

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

🤖 Auto-generated by release workflow

[probelabs]

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

Summary

This is a dependency update PR that upgrades the @probelabs/probe package from version 0.6.0-rc245 to 0.6.0-rc254. This is a release candidate update within the 0.6.0 series.

Files Changed

• package.json: Updated @probelabs/probe dependency version
• package-lock.json: Updated lockfile with new dependency versions and integrity hashes

Key Changes

Dependency Updates

1. @probelabs/probe: 0.6.0-rc245 → 0.6.0-rc254

   • New integrity hash: sha512-/tV65rA8hMVEk7OJzeHYOyqaPqkgwQPiOJkS35hDS98nThxwJy1aHYmVtA8zNOurjUcDZofEwcBT2PxqsgHagw==

2. @probelabs/maid: 0.0.24 → 0.0.25 (transitive dependency)

   • Updated as a dependency of @probelabs/probe
   • New integrity hash: sha512-uaXDxZHrtRJAuHCpWBBWD5zntPewGhcfFQSKVWBfbOoC4LsC94sE4H450eViAcS5Oxhf1I2pt49297gDH9SNJQ==

Architecture & Impact Assessment

What This PR Accomplishes

This PR updates the core AI agent SDK dependency to the latest release candidate version. The @probelabs/probe package is the primary AI orchestration engine used by Visor for:

• AI-powered code review
• Schema validation and structured output
• MCP (Model Context Protocol) tool integration
• Session management and conversation history
• Multi-provider AI support (Anthropic, OpenAI, Google, Bedrock)

Key Technical Changes

• No breaking changes expected - This is an update within the same 0.6.0 release candidate series
• Transitive dependency update - @probelabs/maid (used for diagram generation and AST processing) updated alongside probe
• Integrity hashes updated - New checksums for both packages in package-lock.json

Affected System Components

Based on code analysis, @probelabs/probe is used throughout the codebase:

1. AI Review Service (src/ai-review-service.ts)

   • Primary consumer of ProbeAgent
   • Handles session initialization, schema validation, and AI responses
   • Manages session registry for conversation reuse

2. State Machine Context (src/state-machine/context/build-engine-context.ts)

   • Integrates ProbeAgent into workflow engine

3. CLI Main (src/cli-main.ts)

   • CLI interface for AI operations

4. Testing Infrastructure

   • Unit tests mock ProbeAgent for testing
   • Concurrency limiter tests use DelegationManager from probe

5. Version Injection Script (scripts/inject-version.js)

   • Reads probe version from package-lock for build metadata

Component Relationships

graph TD
    A[Visor Application] --> B[AI Review Service]
    B --> C["@probelabs/probe SDK"]
    C --> D[AI Providers]
    C --> E[MCP Tools]
    C --> F["@probelabs/maid"]
    F --> G[Diagram Generation]
    C --> H[Session Management]
    H --> I[Conversation History]
    
    J[Tests] -.-> C
    K[CLI] -.-> C
    L[State Machine] -.-> C

Loading

Scope Discovery & Context Expansion

Immediate Impact

• Core AI functionality: All AI-powered checks and reviews use ProbeAgent
• Session management: Conversation history and session reuse features
• Schema validation: Structured output validation for AI responses
• MCP integration: Tool orchestration capabilities

Related Files to Verify

For comprehensive testing, reviewers should verify:

1. Test files:

   • tests/unit/ai-schema-resolution.test.ts - Schema handling
   • tests/unit/concurrency-limiter.test.ts - DelegationManager usage
   • tests/unit/mermaid-production-scenario.test.ts - ProbeAgent mocking
   • tests/unit/raw-output-extraction.test.ts - Output parsing

2. Configuration:

   • jest.config.js - Module mapping for mocks
   • __mocks__/open.ts - Mock configurations

3. Build scripts:

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

Testing Recommendations

1. Run full test suite: npm test
2. Verify AI review functionality with real providers
3. Test session reuse scenarios
4. Validate schema-based output formatting
5. Check MCP tool integration if applicable

Review Notes

• This is a dependency-only update with no code changes
• The update is within the same major/minor version (0.6.0-rc series)
• Low risk - Release candidate updates typically include bug fixes and minor improvements
• Auto-generated by release workflow from probelabs/probe repository

Labels

• Type: chore - Dependency maintenance update
• Review Effort: 1 (trivial) - No code changes, only dependency version updates

Metadata

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

---

Powered by Visor from Probelabs

Last updated: 2026-02-20T19:07:39.791Z | Triggered by: pr_opened | Commit: 51a2843

💡 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	package-lock.json:6380	Transitive dependency @probelabs/maid also updated from 0.0.24 to 0.0.25 without explicit review. This dependency is used by @probelabs/probe and may contain breaking changes that affect the codebase. 💡 Suggestion Review the @probelabs/maid v0.0.25 changelog to understand what changed. If there are breaking changes, ensure the codebase is compatible before merging.
🟡 Warning	package.json:105	Dependency update from @probelabs/probe v0.6.0-rc245 to v0.6.0-rc254 lacks integration tests to verify compatibility. The codebase uses mocks for all ProbeAgent tests, which means breaking changes in the actual dependency would not be caught by the test suite. 💡 Suggestion Add integration tests that use the real @probelabs/probe package to verify the upgrade works correctly. Consider adding a smoke test that instantiates ProbeAgent with the new version and calls basic methods to ensure API compatibility.
🟡 Warning	__mocks__/@probelabs/probe.ts:1	Mock implementation may not reflect API changes in @probelabs/probe v0.6.0-rc254. The mock only implements basic methods (constructor, initialize, answer, getTokenUsage) but the actual ProbeAgent has additional methods and options that may have changed between rc245 and rc254. 💡 Suggestion Review the @probelabs/probe v0.6.0-rc254 changelog and API documentation to ensure the mock implementation matches the new API. Update the mock to include any new methods or changed signatures.
🟡 Warning	tests/unit:1	All tests use jest.mock() for @probelabs/probe, providing no integration test coverage. This creates a risk that the dependency upgrade could introduce runtime errors that only manifest with the real package. 💡 Suggestion Add at least one integration test file that imports the real @probelabs/probe package and tests basic functionality. This would catch API incompatibilities early. Consider using a separate test suite with 'integration' in the filename that runs against the real dependency.

---

Powered by Visor from Probelabs

Last updated: 2026-02-20T19:07:42.688Z | Triggered by: pr_opened | Commit: 51a2843

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