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

[probelabs]

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

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

Changes

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

🤖 Auto-generated by release workflow

[probelabs]

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

Description

This PR updates the @probelabs/probe dependency from version 0.6.0-rc311 to 0.6.0-rc317, a minor version bump within the release candidate series for v0.6.0.

Files Changed

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

Architecture & Impact Assessment

What This PR Accomplishes

This is a dependency update PR that pulls in the latest probe release candidate (rc317). The update:

• Brings in bug fixes and improvements from probe versions rc312 through rc317
• Maintains API compatibility within the v0.6.0-rc series
• Updates the npm integrity checksum for the new package tarball

Key Technical Changes

• Version bump: 0.6.0-rc311 → 0.6.0-rc317 (6 release candidate increments)
• Integrity hash: Updated from sha512-7dT9T3CUm6aIBxq/ac85ljTQUluPUBopq/C8E1fbVHPije8pR5L3uJuREUbjeKpaBB2fY6+FqrBsSW4KAzewzw== to sha512-NKQKYhqSbnBNDhaoSRtYDv1scxty+KdzajE16TwZv5gPNazbyNpPdNPtK3NidSgb4C68GJ9f+F3GPvGzoy6VoQ==
• Tarball URL: Updated to point to the new rc317 package on npmjs.org

Affected System Components

The @probelabs/probe package is a core dependency used extensively throughout Visor:

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

   • ProbeAgent class for AI-powered code review
   • Tracing integration via SimpleTelemetry and SimpleAppTracer
   • Timeout management and graceful wind-down
   • MCP server configuration

2. Session Management (src/session-registry.ts)

   • Session reuse and cloning for multi-check workflows
   • Agent lifecycle management

3. Task Evaluation (src/agent-protocol/task-evaluator.ts)

   • LLM judge for evaluating task response quality
   • Execution trace analysis

4. Diff Processing (src/utils/diff-processor.ts)

   • extract utility for code analysis

5. Telemetry (src/utils/tracer-init.ts)

   • OpenTelemetry integration
   • Trace file generation for debugging

6. Test Infrastructure

   • Mock implementations in __mocks__/@probelabs/probe.ts
   • Unit and E2E tests for AI features

Component Relationships

graph TD
    A[Visor Application] --> B[AI Review Service]
    A --> C[Session Registry]
    A --> D[Task Evaluator]
    A --> E[Diff Processor]
    A --> F[Telemetry]
    
    B --> G["@probelabs/probe"]
    C --> G
    D --> G
    E --> G
    F --> G
    
    G --> H[ProbeAgent]
    G --> I[SimpleTelemetry]
    G --> J[extract utility]
    G --> K[DelegationManager]
    
    L[Test Suite] --> G
    M[MCP Integration] --> G

Loading

Scope Discovery & Context Expansion

Immediate Impact

• No breaking changes expected - This is an update within the same minor version (v0.6.0-rc series)
• Bug fixes: Likely includes fixes from probe rc312-rc317 (specific changes not visible in this repo)
• Performance improvements: Potential optimizations in probe's core agent logic

Related Files to Verify

Based on the codebase analysis, these areas should be tested after the upgrade:

1. AI Review Flows

   • PR review checks using code-review schema
   • Session reuse between checks
   • Timeout and graceful wind-down behavior

2. Telemetry Output

   • Trace file generation in debug-artifacts/
   • OpenTelemetry span emission
   • NDJSON fallback logging

3. MCP Integration

   • MCP server configuration passing
   • Tool execution through MCP

4. Test Mocks

   • Verify __mocks__/@probelabs/probe.ts still aligns with new probe API
   • Run unit tests: ai-review-service.test.ts, session-registry.test.ts, llm-judge.test.ts
   • Run E2E test: mcp-probe-e2e.test.ts

Potential Risks

• API drift: If probe rc317 introduced subtle API changes, mocks may need updating
• Behavioral changes: Agent iteration logic, timeout negotiation, or tool selection may have changed
• Telemetry format: Trace output structure or event names may have shifted

Recommendations

1. Run full test suite to ensure no regressions in AI review functionality
2. Check CI logs for any new warnings from probe's internal logging
3. Verify trace output format if you have tooling that parses debug-artifacts/*.jsonl
4. Monitor first production runs for any unexpected agent behavior

References

• package.json:123 - Dependency declaration
• package-lock.json:5659 - Locked package metadata
• src/ai-review-service.ts - Primary consumer of ProbeAgent
• src/session-registry.ts - Session management
• src/agent-protocol/task-evaluator.ts - LLM judge implementation
• src/utils/tracer-init.ts - Telemetry initialization
• __mocks__/@probelabs/probe.ts - Test mocks

Metadata

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

---

Powered by Visor from Probelabs

Last updated: 2026-05-20T07:16:50.232Z | Triggered by: pr_opened | Commit: e5652ef

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

[probelabs]

✅ Security Check Passed

No security issues found – changes LGTM.

✅ Security Check Passed

No security issues found – changes LGTM.

\n\n \n\n

✅ Performance Check Passed

No performance issues found – changes LGTM.

Quality Issues (1)

Severity	Location	Issue
🟠 Error	system:0	ProbeAgent execution failed: Error: Failed to get response from AI model. No output generated. Check the stream for errors.

---

Powered by Visor from Probelabs

Last updated: 2026-05-20T07:09:44.135Z | Triggered by: pr_opened | Commit: e5652ef

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