fix(ruflo-adr): parse bullet-prefixed metadata from adr-create template (#2659) - #2755
Open
michaelaperez-byte wants to merge 1 commit into
Open
Conversation
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.
Summary
Fixes #2659 — ruflo-adr adr-index parser drops Status/Date/Tags for bullet-prefixed metadata from adr-create's own template.
Root cause
adr-create's template (SKILL.md step 3) writes ADR metadata as a bullet list:adr-index's parser (plugins/ruflo-adr/scripts/lib/parse-adrs.mjs) reads these fields with^-anchored regexes that require the field marker at the start of the line. The leading-fromadr-create's own template breaks the^anchor, so Status/Date/Tags silently come back empty/unknown for every ADR created viaadr-create's documented template.Fix
Add
(?:[-*]\s*)?after each^anchor in 5 regex locations to tolerate an optional leading list marker:No new dependencies. No changes to adr-create's template (parser-side loosening is safer since adr-create is the authoring tool and adr-index is the consumer).
Regression test
New standalone Node test:
v3/@claude-flow/cli/__tests__/issue-2659-adr-bullet-metadata.test.mjs(23 assertions):parseAdron bullet-prefixed ADR text → correct Status/Date/Tags/Links**Status**: accepted) still worksVerification
Independent detached-HEAD worktree (
/tmp/ruflo-verify-T22at e03c33f):node --checkexit 0 ✓Closes #2659