fix(js): extract methods assigned to factory object APIs

[rajanpanth]

Summary

• preserve callable members assigned to an object literal inside a JavaScript/TypeScript factory
• model the local API object beneath its factory and attach assigned functions as methods
• cover named async/function-expression assignments and their intra-factory call edge

Verification

• uv run pytest tests/test_extract.py -q
• uv run ruff check graphify/extractors/engine.py tests/test_extract.py
• uv run graphify update .

Fixes #2524

[graphify-labs]

Graphify reviewed this change.

Looks safe to merge — no coupling regressions and no blocking issues, checked against the code graph (not a self-assessment).

Formal verification. No changes could be formally verified in this run.

---

Graphify review — findings

This PR extends the JavaScript/TypeScript extractor in graphify/extractors/engine.py to capture callable members assigned to local object-literal variables inside a function body (e.g. factory patterns like const api = {}; api.foo = fn), in addition to the existing this.X = fn handling. The _js_member_assignment_target helper now returns an ("object", name, member) tuple for arbitrary identifier receivers instead of returning None, and the caller in _extract_generic collects object-literal bindings and materializes owner nodes/edges only for those tracked identifiers. A new test, test_extract_js_factory_object_assigned_methods, is added to exercise this factory-object scenario and assert the expected node labels and contains/method/calls edges. The large set of other changed test symbols appears to reflect incidental renumbering/shifts in the test module. The surface area is the JS/TS member-assignment extraction path and the associated test file.

No blocking issues surfaced. 3 lower-confidence candidates did not survive cross-model review.

Analysis details — impact, health, verification

Impact & health

Graphify review

Impact — 897 functions depend on the 534 functions this change touches.

Health — this change adds coupling hotspots:

• worse: extract_js() — 77 callers, 3 callees

Verification — 897 functions in the blast radius were not formally verified this run (proofs are advisory here).

Gate & verification

graphify gate

PASS — objectively clean (no health regressions, tests not run — proofs not run this pass (advisory)). Grounded, not self-assessed.

Advisory (not blocking):

• verification_scope: 838 function(s) in the blast radius were not formally verified this run

Formal verification

Could not verify: Could not verify \_extract\_generic.

The verifier did not have enough to check \_extract\_generic, so it is saying so rather than guessing. No false assurance is the whole point.

Guarantee: No guarantee either way, this is an honest abstention, not a pass.

Note: Reason: parameter `path` is annotated `Path` — outside the synthesizable primitive/collection set

Could not verify: Could not verify \_js\_member\_assignment\_target.

The verifier did not have enough to check \_js\_member\_assignment\_target, so it is saying so rather than guessing. No false assurance is the whole point.

Guarantee: No guarantee either way, this is an honest abstention, not a pass.

Note: Reason: not verifiable: all 182 sampled inputs raised on both versions — the function never executed, so 'no divergence' would be vacuous (mostly AttributeError — names the real obstacle, not a sampling gap)

· 1 more finding(s) on lines outside this diff (see the check run).