Repository navigation
Sync fxtr plugin 0.1.3 - #19
Merged
Merged
Conversation
vrathi101
self-requested a review
October 26, 2026 22:28
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.
Syncs the fxtr plugin to 0.1.3:
Generated by
pnpm sync:pluginfrom TransluceAI/fxtr3mainat c3782b93.The sync leaves unchanged skills with their previous provenance. Their metadata was regenerated with
scripts/skills/prepare.mjsfrom the same clean revision so all three skills describe one source revision. Both marketplace skill trees match the complete prepared bundle exactly.Validation: all 22 skill/preparation tests passed; both marketplaces' checks and
git diff --checkpassed. Changes are limited to the fxtr plugin and its marketplace version; other plugins are unchanged.Hold merging until fxtr 0.1.0a0 and behaviors 0.0.1a4 are published from the package release PR. The source checkout still records the previous unpublished package versions, so refresh provenance from the final clean release revision before merge. The release requester explicitly waived the failing newest-dependency gate for this release; the normal locked-dependency release checks still apply.