Skip to content

fix(ruflo-adr): use a key separator the memory validator accepts for edges - #3636

Merged
ruvnet merged 2 commits into
ruvnet:mainfrom
drakeo338:claude/3633-fix
Oct 7, 2026
Merged

ruvnet merged 2 commits into
ruvnet:mainfrom
drakeo338:claude/3633-fix

Conversation

@drakeo338

Copy link
Copy Markdown
Contributor

Fixes #3633.

edgeKey() in ruflo-adr joined the two ADR ids with ->, and > is in the CLI's DANGEROUS_KEY_PATTERN, so every adr-edges store failed with "Key contains disallowed characters" and no edges were written.

Edge keys now use __ between the ids. parseEdgeKey() accepts both __ and ->, in case any old-format row exists. The regression test fails on the old code (2 failing) and passes with the change; the other ruflo-adr script tests still pass (30/30).

…edges (ruvnet#3633)

edgeKey() joined the endpoints with '->', and '>' is in the CLI's
DANGEROUS_KEY_PATTERN, so every adr-edges store failed with "Key contains
disallowed characters". Join with '__' instead; parseEdgeKey() still reads
the earlier '->' keys so existing rows stay verifiable.
@drakeo338
drakeo338 requested a review from ruvnet as a code owner October 2, 2026 22:07
@ruvnet
ruvnet merged commit 940bb62 into ruvnet:main Oct 7, 2026
122 of 123 checks passed
@ruvnet

ruvnet commented Oct 7, 2026

Copy link
Copy Markdown
Owner

Shipped in v3.55.0. Thank you @drakeo338 for the contribution.

🤖 Generated with RuFlo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ruflo-adr: edge keys use '->', which the memory key validator rejects, so no edges are stored

2 participants