Reframe the project around Skill evolution - #2
Merged
Conversation
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.
What changed
agent-runtimeSkill with the action-shapedevolve-skillsSkill;Why
Runtime is an implementation layer, not the standard unit of reusable agent capability. Native Skills are the correct public abstraction, while ADK, task state, memory, and authorization remain separate concerns.
Impact
Existing v2.0.0 users install
evolve-skills, then remove the retiredagent-runtimeSkill. Internal package names and launchd labels remain stable during v2 for compatibility.Validation
quick_validate.py;skillsdiscovery finds exactly three Skills;Rollback
Revert commit
403ae43; existing v2.0.0 runtime release and service labels remain unchanged.