Skip to content

fix: restore Blackboard startup on MeshLLM protocol 3 - #4

Merged
ndizazzo merged 1 commit into
mainfrom
codex/protocol-3-compatibility
Nov 1, 2026
Merged

ndizazzo merged 1 commit into
mainfrom
codex/protocol-3-compatibility

Conversation

@ndizazzo

@ndizazzo ndizazzo commented Nov 1, 2026 •

Copy link
Copy Markdown
Contributor

Blackboard 0.1.4 starts on MeshLLM hosts that require plugin protocol 3. The published 0.1.3 archive uses protocol 2 and is rejected during startup. This pins the plugin SDK to Mesh commit efd30516fd2cd92ac132dfd7b8341d24d412ee9c, regenerates the dependency lockfile, and sets both package and archive metadata to 0.1.4. The README now documents the host's current Streamable HTTP MCP endpoint.

Part of Mesh-LLM/mesh-llm#2777.

Compatibility

This version requires a protocol-3 host. Protocol-2 hosts cannot load it. Blackboard retains its private-mesh startup policy and existing CLI and namespaced MCP tools.

Connect an MCP client to http://127.0.0.1:3131/mcp, using the configured console port when different. The host exposes blackboard.feed, blackboard.search, and blackboard.post.

Validation

  • Targeted Cargo lock update; formatting, locked check, warning-denying Clippy, full tests and release build passed on macOS. Twenty-seven tests passed, with no failures or ignored tests.
  • The built executable passed mandatory plugin startup against the local Mesh development host. Feed and search reads succeeded through HTTP and the actual mesh-llm blackboard CLI. The host MCP endpoint initialized, listed the three namespaced tools, and returned an empty feed with isError=false. Owned processes and listeners were gone after a clean SIGINT shutdown.
  • This is pre-RC compatibility evidence, not qualification of a published Mesh release candidate. Checks were read-only; message publication and cross-node propagation were not tested.

Summary by CodeRabbit

  • Documentation
    • Updated the release information to version 0.1.4 and clarified that it requires a host supporting plugin protocol 3; protocol 2 hosts cannot load it.
    • Updated build instructions to use locked dependency versions.
    • Revised MCP connection guidance to use the host’s Streamable HTTP endpoint, defaulting to port 3131 unless configured otherwise, and listed the available Blackboard tools.

@coderabbitai

coderabbitai Bot commented Nov 1, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

No actionable comments were generated in the recent review.

Recent review info
Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 0e17eab9-1b5e-408b-95ad-e938a62f0db1
Commits

Reviewing files that changed from the base of the PR and between beb31d9 and 728116d.

Files ignored due to path filters: 1
  • Cargo.lock is excluded by !**/*.lock
Files selected for processing: 3
  • Cargo.toml
  • README.md
  • plugin.toml

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

Walkthrough

The package and plugin versions change to 0.1.4, and the SDK dependency is pinned to a Git revision. The README adds host compatibility requirements, updates the build command, and documents the host’s Streamable HTTP endpoint and Blackboard tools.

Changes: Version 0.1.4 release updates

Layer / File(s) Summary
Version and host compatibility
Cargo.toml, plugin.toml, README.md
The package and plugin versions change to 0.1.4. The SDK dependency uses a pinned Git revision. The README states the protocol 3 host requirement, excludes protocol 2 hosts, and uses cargo build --locked.
Blackboard endpoint instructions
README.md
The README directs clients to the host’s Streamable HTTP endpoint, using port 3131 unless configured otherwise, and lists the blackboard.feed, blackboard.search, and blackboard.post tools.

Estimated code review effort: 2 (Simple) | ~8 minutes

Change: Bug fix

Suggested reviewers: i386

Merge Risk: Minimal · up to 72811

No actionable merge-blocking risk is identified.

Pre-merge checks: Passed 5
Check name Status Explanation
Description Check Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check Passed The title clearly and concisely describes the main change: restoring Blackboard startup for MeshLLM protocol 3.
Docstring Coverage Passed No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage

Explanation

No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (3 skipped: 3 unsupported.)

Finishing Touches
Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@ndizazzo
ndizazzo marked this pull request as ready for review November 1, 2026 20:16
@ndizazzo
ndizazzo merged commit 906078b into main Nov 1, 2026
2 checks passed
@ndizazzo
ndizazzo deleted the codex/protocol-3-compatibility branch November 1, 2026 20:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant