Repository navigation
feat(agent): activate evolved skill candidates - #149
Merged
Pepps233 merged 3 commits intoAug 31, 2026
Merged
Conversation
This was referenced Aug 29, 2026
Pepps233
force-pushed
the
feat/activate-evolved-skills
branch
2 times, most recently
from
August 30, 2026 15:10
cff9ed2 to
aa617a7
Compare
Pepps233
force-pushed
the
feat/activate-evolved-skills
branch
from
August 30, 2026 21:32
aa617a7 to
8aedc54
Compare
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
Activate accepted evolved-skill candidates through a dedicated, fenced writer that stages a complete immutable harness revision before compare-and-swap selection, without adding automatic activation or lifecycle controls.
Reasoning
Structural validation and retrieval/behavior evaluation establish that a draft is eligible for promotion, but activation still needs a separate mutation boundary. The writer must bind the accepted group, draft, validation, evaluation, workspace, harness base, and existing skill digests so stale or cross-scope inputs cannot modify the selected harness.
Activation therefore preserves memory and unrelated evolved skills, stages the full candidate bundle without changing the current pointer, verifies the staged revision, and only then selects it under the existing writer lease and harness compare-and-swap behavior. Immutable write and activation receipts make retries idempotent, while the harness parent revision preserves exact rollback lineage.
Changes
Stack
Position: 9 of 12
Base: #148
Next: #150
Testing
cd packages/evolution && node ../../node_modules/vitest/dist/cli.js --run test/skill-writer.test.ts test/filesystem-store.test.ts test/skill-candidate-registry.test.ts test/skill-evaluator.test.ts test/skill-draft-validator.test.tscd packages/harness-state && node ../../node_modules/vitest/dist/cli.js --run test/harness-state.test.tscd packages/coding-agent && node ../../node_modules/vitest/dist/cli.js --run test/skills.test.tsnpm run check(blocked by the pre-existing model-catalog TypeScript failures also reported on feat(agent): evaluate evolved skill candidates #148; nopackages/evolutionorpackages/harness-stateerrors)This pull request is AI-generated by Diffex.