Iven Kooandgensokyo-dev
9df94a62cd
* feat(javascript): link assignment right-hand sides to their writes A declaration carries its value forward, but a later assignment to a variable, a property or through a compound operator stopped the forward trace at the right-hand-side read. The semantic IR now records one syntactic assignment flow per simple assignment target (ranges, operator, owning callable), and the graph projection connects each retained read of the right-hand side to the write occurrence through a defines relation. Compound assignments also consume the previous value of the target; the written value itself stays unknown, keeping the boundary of #4342 intact. Fixes #6193 * fix(javascript): preserve computed key assignment ownership * test(javascript): retain nested callback assignment ownership * docs(javascript): record assignment influence verification * test(mcp): isolate mocks and acknowledge cancellation boundaries * test(javascript): retain CLI diagnostics and current-main verification --------- Co-authored-by: gensokyo-dev <342580529+gensokyo-dev@users.noreply.github.com>
37 KiB
Cross-layer JavaScript application workflows
REA derives a complete reachable feature trace from one authenticated JavaScript
Application Graph and compares two authenticated graph versions. The MCP tools
are inspect_analysis_view, trace_application_feature,
trace_javascript_semantics, compare_application_versions,
compare_source_to_bundle, and compare_javascript_export_shapes; their CLI
equivalents use the same names with hyphens. inspect_analysis_view projects a
summary, module page, typed module references, or one module from already completed application
Evidence; it does not walk relationships.
inspect_analysis_view also projects retained inspect_binary_layout
Evidence. The remaining workflows consume Evidence produced by
analyze_javascript_application or reconcile_javascript_runtime. They do not
read an artifact, execute application code, attach to a process, or open a
native-analysis provider. Static artifact observations, passive runtime
observations, relationship inferences, and unknown or unavailable facts retain
their original graph authority.
analyze_javascript_application Evidence retains the structural JavaScript
Application Graph and a separate semantic relation graph bound to the same root
artifact digest and structural graph ID. Semantic tracing requires the semantic
relation graph and reports when it is unavailable rather than treating missing
data as an empty graph.
Worker progress reports the source path and last observed parse, static, semantic, projection or transfer stage. These notifications do not measure stage CPU/time or establish the root cause of a slow or incomplete analysis. Semantic projection limits bound retained output, not upstream analysis work.
Explicit TypeScript import type and export type declarations remain source
facts and do not create runtime import or export relationships. Type export names
are reported separately from value export names. Inline type specifiers