Repository navigation
Scope the first tools/list to this server's backend and report unreadable connections (0.7.12) - #15
Merged
Merged
Conversation
…able connections (0.7.12) devtools 0.3.14 fixes the two registry defects found while accepting 0.7.9. The server now awaits the catalog's ready(), which resolves its backend without a network request the way auth-status does, before answering the first tools/list, so another backend's cached tools never appear in a chat (0.7.9 listed every cached scope until its first refresh). A connection whose catalog cannot be read, or is not read within the 300 s refresh budget, keeps its earlier tools and is marked unavailable in the catalog file; mainsequence_open → registeredTools reports it from any process. The packaged-server test now seeds the shared catalog with two backends and asserts that only this server's backend is listed. The lockfile pins devtools 0.3.14 by the local pack's integrity for this test run; it must be re-pinned from the registry once 0.3.14 is published. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The registry archive of 0.3.14 differs in bytes from the local pack the branch pinned for its test run (identical contents, different compression), as with 0.3.12. The lockfile now carries the integrity of the archive on the registry. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
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
Consumes devtools 0.3.14 (mainsequence-sdk/mainsequence-devtools#26), which fixes the two registry defects found while accepting 0.7.9:
tools/listscoped to this server's backend. The server awaits the catalog'sready()(backend resolved from the environment, the shared preferences or the default, no network) before answering, so another backend's cached tools never appear in a chat. 0.7.9 listed every cached scope — 144 tools from two backends on the workstation — until its first refresh.unavailablein the catalog file;mainsequence_open→registeredToolsreports it from any process. 0.7.9 once wrote a scope empty after a 773 s refresh and reported nothing.Docs:
docs/agents-tools-panel.mddescribes both behaviours (version-free, percheck-docs).Testing
npm run build(vendors devtools 0.3.14 from a local pack),node --test tests/*.test.cjs: 57 pass. The packaged-server test seeds the shared catalog with two backends and asserts that only this server's backend is listed.node scripts/check-release.cjs,node scripts/check-docs.cjspass. The marketplace stays at 0.7.11 until 0.7.12 is published.tools/listreturned 103 tools = 16 + the 87 of its own backend; the other backend'sms_crm_contacts_list_183f8138was absent.Review notes
v0.3.14); the lockfile now pins the published archive (sha512-H7Vv…Qu4dg==, re-pinned from the registry in 64ffd97) and CI is green on ubuntu and macOS.🤖 Generated with Claude Code