grafema-dual-path-type-classification-mismatch

AST node lookup fails in Grafema due to a dual-path classification mismatch where one code path assigns LITERAL while another assigns OBJECT_LITERAL at the same coordinates. This discrepancy causes coordinate-based lookups to miss the correct node type.

Debugging bufferArrayMutationEdges failures requires identifying dual-path AST classification mismatches where ObjectExpression or ArrayExpression nodes are incorrectly typed as LITERAL, breaking coordinate-based node retrieval during data flow tracing.

extractLiteralValue returns incorrect types when dual code paths classify the same AST node differently, creating a mismatch between LITERAL and OBJECT_LITERAL or ARRAY_LITERAL classifications at identical coordinates, disrupting type resolution.

Resolving coordinate-based node lookup failures involves diagnosing the dual-path AST classification mismatch, ensuring both code paths consistently assign OBJECT_LITERAL or ARRAY_LITERAL instead of LITERAL for ObjectExpression and ArrayExpression nodes.

Tracing data flow when array mutations are untracked requires fixing the underlying AST classification issue where dual code paths mismatch LITERAL and ARRAY_LITERAL types, restoring accurate coordinate-based node lookups for mutation edges.