Repository navigation
mcp-server 3.2.0: update_project tool; handoff 422 names the membership story - #1037
Merged
Merged
Conversation
…ip story (#1036) No MCP tool reached PATCH /api/v1/projects/:id, so no session could set a work project's repo_url (Second Brain has none, so SessionStart resolves no channel for second_brain). update_project sends name/repo_url/description/tech_stack/ mission/metadata with the orchestrator-pinned key, never slug or status, and refuses an empty update locally. The handoff tool's 422 remediation on a work project now names the membership-story fix instead of stopping at the cause.
# Conflicts: # mcp-server/CHANGELOG.md # mcp-server/package-lock.json # mcp-server/package.json
Owner
Author
|
Review attested at |
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.
Closes #1036.
What changed
mcp-server/index.js: newupdate_projecttool forPATCH /api/v1/projects/:id. It sendsname,repo_url,description,tech_stack,missionandmetadata. It never sendsslugorstatus, and it refuses locally a call that names no field or has a malformed id. It usesorchestratorPinnedApiCall, ascreate_epicandupdate_epicdo (orchestrator key verbatim, else user key). The description warns that arepo_urlmust be on only one active project.mcp-server/lib/handoff.js: a 422 on a work-project post now names the fix, a membership story in that project, never a second channel. This matches the handoff skill (mkreyman/claude-config#1075).mcp-server/), CHANGELOG, and a version bump to 3.2.0.Testing
node --test test/*.test.jsinmcp-server: all pass. This includes the newtest/update_project_tool.test.jsand the existinghandoff_tool.test.jsanddelete_project_tool.test.js.Review findings
orchestratorPinnedApiCall("PATCH", ...). The request now lives inlib/project-update.jsas a literalapiCall("PATCH", ...).PATCH /api/v1/projects/:paramis removed from the gap table, and itsPUTtwin is nowduplicate.index.js, against the repo'slib/rule. It moved tolib/project-update.jswith an injectedapiCall, like the epic tools.apiCall(named fields only, never slug or status, an empty mission sent, an empty update and a malformed id refused with nothing sent), and it readsindex.jsthroughstripComments.Risk
The new tool is additive. The server already enforces orchestrator role and the human anchor on PATCH. The one sharp edge is a
repo_urlthat duplicates another active project, which makesresolve_project409. The tool description says so; the server does not stop it.How to revert
Revert the squash commit. Nothing reads
update_projectyet.