Document Kuzu MAP-as-STRING pattern in plan + prompts#6
Merged
Conversation
PR-A1 discovered that Kuzu's Python binder (0.11.x) rejects native `dict` for `MAP(STRING, INT64)` parameters and shipped `routes_by_framework` as a `STRING` JSON blob. Add this as a top-level plan principle so PR-A3's `routes_by_layer` (the next map-shaped graph_meta field) doesn't re-discover it. Reminder injected into both the prompts file and the relevant plan sections.
This was referenced May 6, 2026
This was referenced May 13, 2026
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
1 participant
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
Documents the Kuzu MAP-as-STRING pattern that PR-A1 (#5) discovered, so PR-A3's
routes_by_layerdoesn't re-discover it.PR-A1 shipped
routes_by_frameworkas aSTRINGJSON blob because Kuzu's Python binder (0.11.x) rejects a nativedictbound to aMAP(STRING, INT64)parameter (STRUCT()vsMAPmismatch). The fix worked cleanly — schema comment,json.dumpson write, decode inkuzu_queries.meta(), plus a_META_LEGACYCypher path so v4 graphs still read.This PR makes the pattern part of the plan so:
STRINGand a paragraph explaining why.routes_by_layermust follow the same pattern.Files
plans/PLAN-TIER1-COMPLETION.md— three insertions (Principles, PR-A1 §3.6, PR-A3 §3).plans/CURSOR-PROMPTS-TIER1.md— two insertions (PR-A2 prompt scope, PR-A3 prompt scope).Planning artifacts only
No production code; no schema or behaviour change.