fix: require finite zara-memory MCP deadlines #333

Open
nsaspy wants to merge 0 commits from rage/296-memory-mcp-finite-deadline into main
Owner

Implements #296 and advances #7.

Deterministic RED first: SymbolicMemoryMCP currently accepts boolean, NaN, and positive-infinity timeout values. The transport must require a finite positive numeric deadline so the subprocess boundary cannot be silently disabled or mis-typed.

No backend feature expansion and no Zara Core changes.

Implements #296 and advances #7. Deterministic RED first: `SymbolicMemoryMCP` currently accepts boolean, NaN, and positive-infinity timeout values. The transport must require a finite positive numeric deadline so the subprocess boundary cannot be silently disabled or mis-typed. No backend feature expansion and no Zara Core changes.
Some checks failed
CI / test (pull_request) Failing after 17s
This branch is already included in the target branch. There is nothing to merge.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin rage/296-memory-mcp-finite-deadline:rage/296-memory-mcp-finite-deadline
git switch rage/296-memory-mcp-finite-deadline

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff rage/296-memory-mcp-finite-deadline
git switch rage/296-memory-mcp-finite-deadline
git rebase main
git switch main
git merge --ff-only rage/296-memory-mcp-finite-deadline
git switch rage/296-memory-mcp-finite-deadline
git rebase main
git switch main
git merge --no-ff rage/296-memory-mcp-finite-deadline
git switch main
git merge --squash rage/296-memory-mcp-finite-deadline
git switch main
git merge --ff-only rage/296-memory-mcp-finite-deadline
git switch main
git merge rage/296-memory-mcp-finite-deadline
git push origin main
Sign in to join this conversation.
No description provided.