Skip to content

chore: formalize reaching-defs ddg prov token#40

Open
rahlk wants to merge 1 commit into
fix/issue-31-level-gate-callgraphfrom
chore/issue-32-formalize-reaching-defs
Open

chore: formalize reaching-defs ddg prov token#40
rahlk wants to merge 1 commit into
fix/issue-31-level-gate-callgraphfrom
chore/issue-32-formalize-reaching-defs

Conversation

@rahlk

@rahlk rahlk commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

Closes #32. Part of epic #26 (contract-correctness cluster).

Stacked PR 6 of 7 — base: fix/issue-31-level-gate-callgraph; review this PR's diff in isolation. Merge the stack bottom-up into feat/issue-2-program-graphs.

Verified: full suite 99 pass / 0 fail, typecheck clean, schema.neo4j.json in lockstep. Reviewed (task-scoped + final whole-branch review: READY TO MERGE).

…ecisions + neo4j lockstep)

Strengthens the code comment at src/schema/v2/dataflow.ts to record that
"reaching-defs" is a deliberate, sanctioned additive DDG prov token — a
documented deviation from the canonical "ssa" tag — accepted across
JSON, Neo4j (open string[] property, no enum), and the SDK. Full
rationale recorded in .claude/SCHEMA_DECISIONS.md (gitignored, local-
only). No emitter behavior change: the token stays "reaching-defs" and
test/schema-v2.test.ts's assertion is untouched.
@rahlk rahlk force-pushed the chore/issue-32-formalize-reaching-defs branch from 2a32e42 to f0d78ce Compare July 7, 2026 10:38
@rahlk rahlk force-pushed the fix/issue-31-level-gate-callgraph branch from 730e73d to a109a77 Compare July 7, 2026 10:38
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.

1 participant