Sync allium plugin references to upstream 3.4.0#8
Open
chromalchemy wants to merge 1 commit into
Open
Conversation
Port forward the upstream juxt/allium changes since the original port base (82da292 → 8af2da4, plugin v3.4.0). Only two reference files gained content; all other skill/agent/rule files were unchanged upstream. - language-reference.md: zero-argument contract signatures, List<T> list literals (`[ ... ]`, duplicate-retaining vs set literals), qualified default type names, and corresponding validation rules - patterns.md: Pattern 9 external-API `demands` side example plus demands/fulfils/provides direction-marker guidance - README.md: update upstream sync note to 8af2da4 (2026-06-19) Verified the synced references are byte-identical to upstream HEAD and the installed allium CLI 3.5.0 (language versions 1/2/3) validates the documented language version 3 via the `allium check` hook contract. 🤖 Generated with [ECA](https://eca.dev) Co-Authored-By: eca-agent <git@eca.dev>
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
1 participant
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.
Port forward the upstream juxt/allium changes since the original port base (82da292 → 8af2da4, plugin v3.4.0). Only two reference files gained content; all other skill/agent/rule files were unchanged upstream.
[ ... ], duplicate-retaining vs set literals), qualified default type names, and corresponding validation rulesdemandsside example plus demands/fulfils/provides direction-marker guidanceVerified the synced references are byte-identical to upstream HEAD and the installed allium CLI 3.5.0 (language versions 1/2/3) validates the documented language version 3 via the
allium checkhook contract.🤖 Generated with ECA