fix: resolve remaining #445, #448 gaps + persistent MCP client#462
Merged
Conversation
- #445: Stop _load_tasks from persisting normalized frontmatter on the read path (atomic write+fcntl+fsync was a hidden write on every @agora render/list) - #448: Replace curl health probe with urllib in memory_mesh; implement persistent MCP stdio client (_PersistentMCPClient) reused across satellite connectors (memory_mesh, memtrace) so they don't spawn a fresh subprocess+handshake per query - All prior #445-#449 perf fixes were already committed to main; this closes the three remaining sub-items - Build artifact regenerated: 1073 tests pass, 0 failures
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
1 participant
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 #445, #446, #447, #448, #449, #451.
#445: Hidden writes in read paths
_load_tasksno longer persists normalized frontmatter on the read path. The atomic write + fcntl lock + fsync was a hidden write on every@agorarender/list. Other items (@memory shows "No Mnēmē narrative found" warning on cold render even when narrative exists #1, perseus memory show resolves workspace from CWD, not home, causing confusing output #2, Add workspace= modifier to @memory directive #4) were already fixed in prior commits.#448: Satellite connector subprocess per query
curlhealth probe with in-processurllib_PersistentMCPClient— a lightweight persistent MCP stdio client thatmemory_meshandmemtracenow reuse instead of spawning a fresh subprocess + handshake per queryVerified
python3 scripts/build.py— cleanpython3 scripts/build.py --check— in syncpython3 -m pytest tests/ -x -q— 1073 passed, 25 skipped, 0 failuresIssues #446, #447, #449 were already fully addressed in commits on
mainprior to this branch. This branch closes the three remaining sub-items to complete the full set.