fix(ci): drop uv cache + clarify entry skill action/conversation split - #13
Merged
Conversation
The Entry Publish workflow enabled astral-sh/setup-uv caching, which required a uv.lock that doesn't exist (scripts use PEP 723 inline metadata, not a project lockfile). The cache step errored with "No matches found for glob **/uv.lock" before any publish work ran. Removed enable-cache so the action installs uv without a cache key. Entry skill: clarified that artifacts are only written when the user picks a listed action — free-form follow-ups are conversation, not revise instructions. Added a research.yaml rule that later sections should build on earlier ones. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Contributor
|
✅ All review checks passed. When you're ready, apply the |
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
Test plan