scanner: parse YAML block-list tags/keywords in frontmatter - #5
Merged
mockingbird777 merged 1 commit intoJul 22, 2026
Merged
Conversation
The lightweight frontmatter scanner only understood inline [a, b] tag lists. Recognize the common YAML block-list form (tags: then indented - items) with no YAML runtime dependency: when a tags/keywords key has an empty inline value, consume following ' - scalar' lines. Only simple scalars are accepted — a nested/mapping item (- foo: bar) ends the list rather than recursing, so malformed input can't crash the scan. Values merge with the kind tag, dedupe, sort deterministically, and stay within the 256-item bound. Inline lists are unchanged. Fixes mockingbird777#4
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
3 participants
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
Markdown resources may declare
tags/keywordsas a YAML block list, but the lightweight frontmatter scanner only understood the inline[a, b]form. This adds block-list support with no YAML runtime dependency:When a
tags/keywordskey has an empty inline value, the parser consumes the following- scalarlines.Acceptance criteria
tagsandkeywordsuniqueSorted)[a, b]syntax preserved- foo: bar) ends the list rather than recursing, so malformed/nested structures neither execute code nor crash the scanMAX_LIST_ITEMS, and the merged result is re-sliced)[Unreleased]entryTests
Three deterministic scanner tests (synthetic fixtures via the existing
workspace/scanWorkspacehelpers): a block list oftags+keywords→[audit, prompt, review, security]; the inline form still →[prompt, review, security]; and a block list with a nested- key: valueitem stops cleanly, keeping the scalar before it. My three tests pass; the only two failing tests in the suite are the pre-existing Windows-only symlinkEPERMcases (unrelated).Fixes #4