Skip to content

feat(agent): activate evolved skill candidates - #149

Merged
Pepps233 merged 3 commits into
feat/evaluate-evolved-skillsfrom
feat/activate-evolved-skills
Aug 31, 2026
Merged

Pepps233 merged 3 commits into
feat/evaluate-evolved-skillsfrom
feat/activate-evolved-skills

Conversation

@Pepps233

@Pepps233 Pepps233 commented Aug 28, 2026 •

Copy link
Copy Markdown
Contributor

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

  • Add stable harness-owned evolved-skill identity derivation shared by catalog loading and writer target resolution.
  • Add dedicated skill mutation batch, exact inventory diff, and write-output contracts.
  • Require accepted draft, validation, and evaluation closure against the exact workspace, harness base, and existing evolved-skill digests.
  • Stage CREATE, UPDATE, MERGE, and RETIRE mutations as complete immutable harness bundles while preserving memory and unrelated skills.
  • Expose durable lease-fence validation and require it before staging and immediately before compare-and-swap activation.
  • Persist immutable write and activation receipts for retry safety, stale-writer rejection, and rollback lineage.
  • Keep installed skill directories, automatic activation, operator controls, and later lifecycle observation outside this change.

Stack

Position: 9 of 12
Base: #148
Next: #150

  1. feat(coding-agent): activate versioned evolved skills #134
  2. feat(agent): preserve target-neutral reflection evidence #136
  3. feat(agent): curate and checkpoint skill candidates #137
  4. feat(agent): persist and process skill candidate registry #138
  5. feat(agent): synthesize outcome-aware skill drafts #139
  6. feat(agent): validate evolved skill drafts #140
  7. feat(agent): measure procedural information loss #147
  8. feat(agent): evaluate evolved skill candidates #148
  9. feat(agent): activate evolved skill candidates #149 (this PR)
  10. feat(agent): observe evolved skill lifecycle outcomes #150
  11. feat(agent): define evolved skill memory handling #151
  12. feat(coding-agent): add evolved skill operator controls #152

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.ts
  • cd packages/harness-state && node ../../node_modules/vitest/dist/cli.js --run test/harness-state.test.ts
  • cd packages/coding-agent && node ../../node_modules/vitest/dist/cli.js --run test/skills.test.ts
  • npm run check (blocked by the pre-existing model-catalog TypeScript failures also reported on feat(agent): evaluate evolved skill candidates #148; no packages/evolution or packages/harness-state errors)

This pull request is AI-generated by Diffex.

@Pepps233
Pepps233 force-pushed the feat/activate-evolved-skills branch from aa617a7 to 8aedc54 Compare August 30, 2026 21:32
@Pepps233
Pepps233 merged commit 97df364 into main Aug 31, 2026
0 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant