Code Analysis Captured Alias Calls

Captured configured-alias calls

Validated in Draft, not Labs: #1261, head cbc557b7b616dfc1dde2a6b2a7e04af32c9b5d54, runtime 9f8f3200c. It follows JS #1260 in actual native stack #1262, trunk preserved #1252/93378351d. Both are Draft, unmerged; original source-freeze/team/JS commits, authors and PR ownership retained. Go/Rust native stack #1257 and independent Java #1259 are unchanged. This ZIP is branch-specific, not an integrated all-language release. No approval, merge, release or live installation.

Developer investigation

Before, Redux test/utils/isPlainObject.spec.ts:9–14 had a correct captured import edge for @internal/utils/isPlainObject, but no callable definition target. After, the normal CLI follows each of the six calls into src/utils/isPlainObject.ts:5:1 with valid navigation. The external vm.runInNewContext remains unknown. A changed-definition authored paired fixture also recovers the foreign caller on both sides; this is synthetic, not an additional real upstream version pair.

The reserved real test/combineReducers.spec.ts:17 still stops at redux → src/index.ts. Reaching src/combineReducers.ts:123 requires another imported export hop. This is a known-source miss, not counted as a reasonable unknown or correct result. It is the next missing source step; the bounded implementation does not guess through that barrel.

Fixed evidence and replay

Redux c9e06506f88926e252daf5275495eba0c04bf8e3, repository-root source profile: 201 JS/TS files, zero parse errors. Source answers/configuration hashes were frozen before this question's first analyzer capture. Redux was reused in previous research, not blind. The barrel slice was source-reviewed and reserved before this implementation, then captured without rule tuning.

Eight selected observations	Correct	Wrong	Missed source-known targets	Reasonable unknowns
JS v3 baseline	0	0	7	1
Candidate source and ZIP	6	0	1	1

Post-design full-resolution TypeScript5.9.3 attribution agrees with all 11 new call targets, zero disagreements/unavailable. It uses real compiler options plus all captured files as explicit roots and reports 637 diagnostics. This is not successful configured compilation or runtime alias behavior. Earlier six-site attribution added only one test root and had15diagnostics; these are different programs. Supplemental sites were reviewed after implementation and are not added to the frozen six-positive score. All30,241call ranges,3,583previous targets, functions and imports are preserved.

Fixed manifests and report · complete11-site audit · source/ZIP parity.

python3 benchmarks/code-analysis-ts-captured-alias-calls/run.py \
  --cli archify/bin/archify.mjs --sample /path/to/pinned-redux --out /path/to/output

Install this source/extracted module's existing dependencies with npm --prefix archify/modules/code-analysis ci --ignore-scripts. To replay baseline use its CLI and --expect baseline; to replay ZIP point --cli at the extracted archify/bin/archify.mjs. Two checks and two saved questions across source/ZIP exit0, explicitly --fail-on never; the repository still has findings. Rawfacts byte-identical; saved question differs only in install/output paths.

Configuration and unknown scope

New js-ts-lexical-v4, adapter21, follows configured non-relative static imports only when the existing resolver selected an in-project captured implementation. JS and TS share this contract. Historicalv1/v2/v3 snapshots retain their own binding coverage. The noResolve/noLib extraction program does not load an aliased module or infer targets from matching names.

Redux tsconfig baseUrl./, paths@internal/* → src/* andredux → src/index.ts; include is only src. Archify's declared source profile additionally includes test files. Vitest's internal alias was inspected, never executed. No proof of emitted runtime alias behavior, successful build/test or complete impact. External/node_modules, outside-root, excluded/missing, declaration-only, malformed, type-only, factory and re-export targets remain unsupported. Symbol identity preserves shadows; v3 default-reference write/eval guards remain. Recapture after other configuration changes; valid target freshness is not whole-workspace current re-resolution.

No added dependency/toolchain/language server; project source/config/build never executed. Local Node26.12/macOSarm64. Existing npm dependency installation is required; no extra alias setup or server process. No local Windows execution claim.

Separate validation states

• Local: focused58/58; final imported suite rerun after JS control; packaged imported/question/paired45/45. Full module351pass/1inherited installed-config assertion/0skip, with later new historical-v3/JS controls separately passing. Earlier exact#1252 reproduces that same local assertion; cause unestablished.
• Package: two final canonical Node22.23.3/zlib1.3.1-e00f703 builds byte-identical;156trackedmodulefilesmatch; ZIPsha2560932eac8ffb815b31a3fa684bd0bca6d162f514e17b9b6cd6631de67cf21d526.
• Remote: final-head CI completed failure at cbc557b7b. Actual analysis log 353/353pass,0fail,0skip. Full-regression(1), browsers, ZIP, three-platform package and all other executed jobs pass. Only direct failure: full-regression(2) inherited README Classic source-artifact drift, expected ca273484a235600f96a74351ac3976cdb6bffb1cfb5d0b86f9ced8c21bd1aa80 vs actual7f68d7303c86988cfbe228202d25fc6da42fb174be47df5f637d57c39fbf5766; aggregate test(22) also fails, deployments skipped. A separate cumulative candidate is testing existing#1242repair; that repair is not applied to this TS head. No all-green claim.
• Integration: Draft only, not Labs/approved/merged/released/installed. Next prepare a history-preserving cumulative Go/Rust/Java/JS/TS/Python candidate and validate composition; maintainers retain formal merge/release decisions.