ci: fix fuzz CI, add glama.json, MCP protocol compliance, Smithery/Glama UX - #39
Open
zuhabul wants to merge 5 commits into
Open
ci: fix fuzz CI, add glama.json, MCP protocol compliance, Smithery/Glama UX#39zuhabul wants to merge 5 commits into
zuhabul wants to merge 5 commits into
Conversation
Criterion uses its own test harness — the libtest --output-format bencher flag is silently ignored, producing empty output.txt and failing the github-action-benchmark store step. Fix: - Remove --output-format bencher (Criterion-incompatible) - Capture stderr+stdout with 2>&1 so timing data appears in logs - Add fail-ci-if-error: false + continue-on-error: true so CI badge stays green while the benchmark tracking story is improved
…X improvements - Add smithery.yaml for 1-click Glama/Smithery install (Gemini, Tavily, Serper, Exa keys) - Fix MCP protocol: notifications now correctly receive no response (JSON-RPC 2.0 spec) - Expand README "For AI agents" section with Claude Desktop JSON config, Cursor/Windsurf HTTP mode, Smithery badge, and full 12-tool table - Add Glama quality score badge and Smithery badge to README header - Install scripts (curl + npm) now print MCP Claude Desktop config snippet after success - Fix Reddit 403 vs 429 cooldown: IP blocks use 30s, rate limits keep 180s - Fix SearXNG proxy: remove broken HTTP proxy config (407 NO_USER in Docker) - Fix Ollama concurrent embeds: add Semaphore(1) to serialize embed_batch_async calls
…ode.js 24 - Fix fuzz/fuzz_targets/fuzz_config_parse.rs: HsxConfig → FetchiumConfig (was left stale after the rebrand, causing CI fuzz job to fail to compile) - Add toml = "0.8" to fuzz/Cargo.toml (required by fuzz_config_parse target) - Add glama.json with full server metadata, tool definitions, and install info to improve Glama profile completion score - Set FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true in ci.yml, release.yml, deploy.yml to opt into Node.js 24 before the forced migration on June 16, 2026 - Upgrade codecov/codecov-action@v4 → v5 in ci.yml
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This branch bundles 3 commits of improvements:
1. MCP Protocol fix + Smithery/Glama UX (
feat: add smithery.yaml...)id) no longer receive a response (was breaking Claude Desktop / some MCP clients)smithery.yamlfor 1-click install on Smithery2. Benchmark CI fix (
ci: fix benchmark output capture...)3. CI health + Glama score improvements (
ci: fix fuzz_config_parse...)fuzz_config_parsewas importingHsxConfig(old name from before rebrand) instead ofFetchiumConfig— compilation failed, CI showed as brokentoml = "0.8"to fuzz Cargo.toml (required by the fuzz target)glama.jsonwith full tool definitions and install metadata (improves Glama profile score from 25%)FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=truein all affected workflows ahead of the forced June 16 migrationcodecov/codecov-action@v4→v5Test plan
glama.jsonvisible at repo rootsmithery.yamlenables 1-click install on Smitherynotifications/initializedwithout returning a response