Repository navigation
fix(presets): repair frontmatter that no YAML parser accepts - #6880
Open
RemyLoveLogicAI wants to merge 1 commit into
Open
RemyLoveLogicAI wants to merge 1 commit into
RemyLoveLogicAI wants to merge 1 commit into
Conversation
13 frame presets write `key:{ ... }` without the space YAML requires after a flow-map
colon. The block then fails to parse as a whole, so a harness reads nothing from the
preset - it is listed in the package and silently dead at runtime.
Each of the 84 changed lines adds one space; no prose is touched. Verified before and
after with Ruby YAML.safe_load: all 13 blocks were rejected before and parse to a
mapping after, and everything outside the frontmatter is byte-identical to upstream.
🤖 Generated with Codebuff
Co-Authored-By: Codebuff <noreply@codebuff.com>
This branch has not been deployed
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
13 of the frame presets under
skills/hyperframes/assets/frame-presets/ship YAMLfrontmatter that no parser accepts. When the block fails to parse, the document is
rejected whole - a harness loading these presets reads nothing, silently. The preset
is present in the package and dead at runtime.
The defect is one character, 84 times: a flow mapping written
key:{ ... }with no spaceafter the colon. YAML requires that space.
Verification
Every file checked before and after with Ruby
YAML.safe_load(psych), not with ahand-rolled parser:
84 lines changed, each adding exactly one space. No wording is touched, so the diff can be
read as a whitespace-only change.
files
biennale-yellowblockframeblue-professionalbold-posterbroadsidecapsulecartesiancobalt-gridcode-editorialcoralcreative-modedaisy-dayseditorial-forestHow this was found
A library-wide audit cross-checked every skill's frontmatter against an independent YAML
parser. The audit's own parser had rated these files healthy, because it only looked at
which keys were declared and never at whether the block parsed.