Conversation
# Conflicts: # CHANGELOG.md
|
🎉 This PR is included in version 1.1.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
This pull request addresses two open bugs related to
agenticscope.tomlmanifest validation:Support for Memory Fragments (Closes init scaffolds .scope/memory/ but the manifest schema rejects type = "memory" #3)**
memoryto theFragmentTypeenum soagenticscope init's default scaffolded.scope/memory/directory correctly passes schema validation.memoryfragment type in generated context files.Clean Validation Error Formatting (Closes
builddumps a rawZodErrorstacktrace on an invalid manifest (lintfails cleanly) #4)**loadManifestin a helper function (loadManifestOrExit) across thebuild,pack, andlintCLI commands.ZodErrorand elegantly prints the exact validation failures (along with their property paths), rather than instantly crashing and dumping a raw Node stacktrace to the user.