Repository navigation
fix(evolution): evolution curation semantics and curation failures - #133
Merged
Merged
Conversation
- Keeps replacements at the original item and section location - Rejects blank-memory sections instead of silently discarding them
- Corrects semantic errors inside the active model transcript - Aligns schema variants and exhausted-response classification
- Runs hosted server tests against current workspace sources - Prevents stale build artifacts from hiding integration failures
- Keeps PR 132 changelog content out of the rebased branch - Restores the pre-PR 132 Unreleased section exactly
Pepps233
force-pushed
the
fix/evolution-curation-semantics
branch
from
August 27, 2026 14:49
018eb61 to
b81c07f
Compare
Contributor
Author
|
Issue 1: PR 133 was based on main before PR 132 merged. Its history needed to be synchronized with the current base. Issue 2: PR 132 added a Breaking Changes subsection and a unified skill catalog entry to the coding-agent CHANGELOG. Those entries needed to be excluded from PR 133. |
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
Fixes evolution-memory curation failures caused by inconsistent placement semantics.
Aligns the curator, writer, proposal schema, and runtime correction behavior.
Reasoning
The public contract and writer already treated a null/null ADD destination as global append, but the curator rejected it.
REPLACE also reused ADD placement after removal, which relocated replacement content.
Semantic validation ran outside the active model transcript, while the schema and exhausted-response classification disagreed with parser and request-stage behavior.
Changes
Testing
node ../../node_modules/vitest/dist/cli.js --run test/evolution-memory-writer.test.ts test/curator.test.tsinpackages/evolutionnode ../../node_modules/vitest/dist/cli.js --run test/proposal-ranking.test.tsinpackages/evolutionnode ../../node_modules/vitest/dist/cli.js --run test/evolution-runtime.test.ts test/evolution-menu.test.tsinpackages/coding-agentnode ../../node_modules/vitest/dist/cli.js --run test/websocket-flow.test.tsinpackages/coding-agent-servernpm run check./test.sh