You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Umbrella tracker for graph extraction quality — language/format coverage gaps, missing node/edge kinds, and extraction false positives. These are not crashes (see the stability/performance umbrellas) but cases where indexing succeeds yet the resulting graph is shallow, mistyped, or wrong.
Per item: the missing nodes/edges are emitted (or the false positive is suppressed), with a reproduce-first test on a public fixture, or the item is closed with rationale (out of scope / by design).
Why one task
These share the extraction pipeline (tree-sitter queries + hybrid-LSP resolvers + node/edge emission). Triaging them together keeps language/format coverage coherent instead of scattered one-off queries.
Scope
Umbrella tracker for graph extraction quality — language/format coverage gaps, missing node/edge kinds, and extraction false positives. These are not crashes (see the stability/performance umbrellas) but cases where indexing succeeds yet the resulting graph is shallow, mistyped, or wrong.
Sub-issues
Language coverage / LSP depth
@Annotation, signatures, and AST properties missing from graph nodesFormat / IaC / config extraction
.Valueslinkage, template→kind typing, image/env + hook/RBAC edgesCorrectness / false positives
get_code_snippetreturns inactive branchContent / docs indexing (BM25)
Tracked via open PR (not part of this task's open work)
.sql— PR feat(dbt): extract dbt Jinja lineage and macros from raw .sql models #584manifest.jsoningest + DEPENDS_ON — PR feat(dbt): add ingest_dbt_manifest tool for Model/Source nodes and DEPENDS_ON lineage #583Acceptance
Per item: the missing nodes/edges are emitted (or the false positive is suppressed), with a reproduce-first test on a public fixture, or the item is closed with rationale (out of scope / by design).
Why one task
These share the extraction pipeline (tree-sitter queries + hybrid-LSP resolvers + node/edge emission). Triaging them together keeps language/format coverage coherent instead of scattered one-off queries.