Skip to content

fix(javascript): prove namespace interop before attributing Electron APIs - #1857

Merged
morluto merged 17 commits into
mainfrom
fix/1842-electron-interop-provenance
Oct 11, 2026
Merged

morluto merged 17 commits into
mainfrom
fix/1842-electron-interop-provenance

Conversation

@N0zoM1z0

@N0zoM1z0 N0zoM1z0 commented Oct 11, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

A helper named __toESM that returns {BrowserWindow: FakeWindow} currently produces an Electron window observation. This follow-up to #1827 replaces emitted-name trust with structural proof while retaining the released T3 Rolldown namespace conversion. Fixes #1842; validates the original #1802 reproduction.

Problem and expected behavior

let electron = require("electron"); electron = __toESM(electron, 1) must retain origin only when the helper preserves that module. Stable names alone cannot prove this. Unproven results must remain unresolved.

Change and scope

  • One semantic owner matches the complete released Rolldown conversion/copy operations with lexical-role equivalence and captured intrinsic origins. Stable, pure parameter-return helpers also preserve identity, including fresh imports and direct call roots.
  • The existing write traversal records intrinsic effects against capture/conversion positions and callable scope. Known Object/Reflect mutators remain recognizable through static destructuring projections and bound aliases that preserve prebound targets and keys. Stable identifier chains to fresh object, array, function, undecorated class and RegExp syntax stay separate from intrinsic objects; opaque, decorated, reassigned, projected-member and not-yet-initialized targets remain conservative. Class-initialization writes are still retained. One shared pattern walker retains nested/default/rest identifier and member targets, including loop writes, while excluding keys and shadowed locals. Other callable bodies and later global-property replacements cannot invalidate an already captured function solely by source presence.
  • Remove superseded name-only normalization; reuse the shared AST owner for child fields. Keep general reassignment rules and source anchors.

Contract and boundary impact

  • Semantic owner/earliest stage: JavaScript Electron lexical identity classification.
  • CLI/MCP: same schemas and shared workflow; unproven helper results produce fewer inferred findings.
  • Provider/platform: static JavaScript only; no provider setup changes.
  • Evidence/provenance: original call-site ranges and dynamic preload expressions retained.
  • Process/authorization/cleanup: no target execution or additional processes.
  • Generated metadata/package/installation: ignored outputs regenerated; no authored package changes.

Evidence and regression coverage

  • 165 dedicated domain cases cover canonical/renamed helpers, identity helpers, fake/async/generator/fallback helpers, shadowing, reassignment, intrinsic writes, mutators, destructuring, fresh targets, class decorators, class-initialization effects and capture scope.

  • CLI and production stdio MCP fixture retains seven real construction anchors despite local-object/function/class/RegExp mutation and excludes the fake helper and eight reached modules with overwritten intrinsics, including a destructured mutator, replacement class decorator and bound mutator. All ten JavaScript files are parsed; literal preload resolves, dynamic expression stays unknown.

  • On main 0b4ce8361, public CLI reports one window for the fake helper; final tree reports zero.

  • Contributor verification on the exact public T3 nightly main producer source (SHA-256 e566055ab42d104b413575920bb62ea7f43677e014ad840fd7319d69fc83cf1f, 5.4 MB) reports four windows and zero parse failures. Dynamic preloads remain visible; resolved preload entrypoints remain zero in this subset.

  • Proof gaps: this is a boot/main source subset, not the complete ASAR. No Electron execution. Arbitrary cross-call side effects and other unverified esbuild/TypeScript/Babel helper bodies remain unresolved.

  • Observations and derived facts remain distinguishable.

  • Artifact/source identity and failed attempts remain preserved.

  • Unknown and partial outcomes remain visible.

Validation performed

  • Final review fixes — 73 interop cases, 277 adjacent source cases and four public CLI/production stdio MCP cases passed. Projected/fresh-alias regressions produced seven failures before their fix; function/class/RegExp cases produced six failures before expansion; the replacement decorator produced a false positive without the conservative class guard.
  • Main integration — 69 managed inspection and six Hopper handshake-recovery cases passed after incorporating the already merged provider timeout fix (fix(hopper): wait for late bridges during cleanup #1866); those workflows are unchanged by the subsequent JavaScript review fixes.
  • Official facade verification and MCP schema regression coverage are recorded in fix(managed): report ExportedType rows in managed member inspection #1828.
  • npm run check — passed, including architecture guards.
  • npm run docs:check — passed.
  • Public CLI T3/fake controls — four/zero windows, no parse failures.

Maintainer capture and normalization follow-up

  • Preserve the actual intrinsic function capture through initialized identifier and destructuring aliases. Reads before an alias initializer stay unresolved; the helper binding itself must initialize before conversion.
  • Share one unconditional declaration-initializer rule across RPC recognition, Electron origins, intrinsic aliases, and fresh-target checks, including class declarations. Retain the contributor follow-up for repeated variable declarations with exactly one unconditional initializer; assignments, multiple initializers and conditional initialization remain unresolved.
  • Normalize harmless single-statement if/for control blocks while retaining complete operations and lexical-role checks. Extra operations remain unresolved.
  • Recognize hoisted fresh function declarations and their stable aliases before their text; keep variable and class initialization ordering. This addresses review thread discussion_r4242170462.
  • Validation: 611 focused source tests and two public CLI/stdio MCP acceptance cases passed. The acceptance fixture preserves the latest function/class/RegExp and decorated-class controls, and now verifies an earlier captured function after global property replacement plus a hoisted function target.
  • Preserve literal member/destructuring projections at the interop owner. Omitted or literal node modes retain named exports; default projections require a truthy literal mode. Computed extra arguments remain unresolved for both namespace and identity helpers. Four projected-result regressions failed before the fix; public CLI and stdio MCP retain the two additional named-export anchors. This addresses review threads discussion_r4242217981 and discussion_r4242217985.
  • Resolve bound intrinsic mutators once at the semantic owner, including nested binding and call/apply invocation. Unknown bound arguments or replaced bind methods conservatively invalidate helper proof. Nested binding uses iterative traversal and one argument flattening pass. The public bound-mutator control produced eight windows before this fix and seven afterward in both CLI and production stdio MCP. This addresses review thread discussion_r4242268064.
  • Preserve the original bound receiver as well as arguments in the existing invocation contract. Generic Function.prototype.call/apply follow that receiver to the actual mutator; rebinding keeps the original receiver. Remove the redundant alias traversal from invocation normalization. Five valid generic-invocation controls failed before this correction; eight new cases cover generic invocation, receiver-preserving rebinding and fresh targets. The public CLI control reported eight windows before correction. Both final CLI/MCP controls retain seven windows across all ten parsed JavaScript files. This addresses review thread discussion_r4242338265.
  • Normalize generic binding creation through the same call/apply/Reflect.apply owner, including a bound generic binding helper. The invocation contract distinguishes known calls from unknown effects after visible intrinsic replacement, using actual alias-capture positions. Seven new negative controls failed before correction; five fresh/captured-alias controls preserve identity. Both public adapters include generic-bind and replaced-Reflect.apply modules. This addresses review threads discussion_r4242372178 and discussion_r4242372181.
  • Retain the explicit Reflect.set receiver as a possible write identity alongside the target. Unknown/spread receivers remain opaque; unrelated fresh receivers stay separate. Eight negative cases fail before correction and pass afterward, with two fresh-receiver positives. Public CLI/MCP include the receiver mutation module. This follows the ECMAScript Reflect.set contract and addresses discussion_r4242414414.
  • Both hoisting positives and five capture regressions failed before their respective fixes. The extra-operation and late-binding controls remain unresolved.
  • Combined revision: 613 focused tests across 17 files passed, including both public adapter regressions. Local build, full npm run check, and npm run docs:check passed. No Electron target execution or additional real-provider claim. Directly invoked local-function side effects remain explicitly unexamined.

Compatibility, safety, and release

  • No flags or schema migrations. Name-only helper inference is intentionally removed; structurally unverified variants remain unknown.
  • Linux x64 static CLI/stdio MCP coverage; no GUI, Windows/macOS runtime or deep-provider claims.
  • No package/release metadata changes, external requests from target code, or target execution.

Review checklist

  • Concrete bug, focused Conventional Commit outcome, related issue linked.
  • Observable behavior and meaningful failure paths tested.
  • Owning documentation updated; generated outputs remain ignored.
  • CLI/MCP output and limits stated.
  • Final diff checked for secrets, unrelated cleanup and unsupported claims.

N0zoM1z0 and others added 4 commits October 11, 2026 13:59
Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
Co-authored-by: Kaoru0822 <208281322+kaoru0822-kitauji@users.noreply.github.com>
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 11, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-11T17:08:33.951887Z c98d326 New commits
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@N0zoM1z0

Copy link
Copy Markdown
Collaborator Author

Review/verification: namespace provenance now depends on the complete helper operations and captured intrinsic identities, rather than helper spelling. The released T3 producer retains four window anchors; the fake-helper public CLI control reports zero. Known mutation, shadowing and reassignment failures are covered. Unverified helper variants and arbitrary cross-call effects remain explicit limits.

The integrated focused suite passed 91 tests; the final AST-owner extraction passed 45 source regressions and public CLI checks. Static/type/architecture, docs and test-discovery checks passed. Final 5.4 MB T3 profiling retained four windows; Flameox attributed 43/2,737 self samples to the interop module (single static-producer run, not a before/after benchmark). No target code was executed. Waiting for the remaining CI gates before merging.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ced8778094

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Share one pattern-target walker across lexical definitions, member mutation
tracking and Electron identity writes. Keep overwritten globals unresolved
without treating property keys or shadowed locals as global replacements.

Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
Co-authored-by: Kaoru0822 <208281322+kaoru0822-kitauji@users.noreply.github.com>
@N0zoM1z0

Copy link
Copy Markdown
Collaborator Author

@codex review

Follow-up 824728d fixes the reproduced destructuring write gap with one shared target walker. Source regressions, public CLI/stdio MCP, static/architecture and docs checks passed. Please verify the final head.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Can't wait for the next one!

Reviewed commit: 824728d7ee

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Include the main-branch Hopper startup timeout normalization already merged
in #1866 so combined CI retains launcher diagnostics when either timer fires.

Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
Co-authored-by: Kaoru0822 <208281322+kaoru0822-kitauji@users.noreply.github.com>
@N0zoM1z0

Copy link
Copy Markdown
Collaborator Author

The failed shard hit the Hopper startup/request timeout race already fixed upstream in #1866. Integrated current main (554cb45f7) into 47f8156e; the PR's Electron diff is unchanged. All 408 focused tests across 12 files now pass, including the failed handshake case and public CLI/stdio MCP interop/preload checks. CI is rerunning on the integrated head.

@codex review

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 47f8156efe

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

…tity

Resolve known mutators through static binding projections and prove stable
identifier chains to fresh literals before widening unknown mutation targets.
Keep reassigned, uninitialized and member-projected targets conservative.
Cover both review regressions through source tests and inert CLI/MCP fixtures.

Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
Co-authored-by: Kaoru0822 <208281322+kaoru0822-kitauji@users.noreply.github.com>
@N0zoM1z0

Copy link
Copy Markdown
Collaborator Author

@codex review

Please review head 5569e96, including both fixes for the previous review. Static intrinsic projections and stable fresh-literal target identity now have failing-before/passing-after regressions. All 63 interop cases, 277 adjacent source cases, four public CLI/stdio MCP cases, npm run check and npm run docs:check passed locally.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5569e96162

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Recognize stable local function, undecorated class and RegExp targets before
widening intrinsic mutations. Keep decorated classes opaque because their
binding value can be replaced, and preserve class-initialization writes.
Cover fresh targets and replacement decorators in inert CLI/MCP fixtures.

Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
Co-authored-by: Kaoru0822 <208281322+kaoru0822-kitauji@users.noreply.github.com>
@N0zoM1z0

Copy link
Copy Markdown
Collaborator Author

@codex review

Please review head b03df22. The fresh function/class/RegExp finding is fixed; decorated classes remain opaque and direct class-initialization intrinsic writes are retained. All 354 affected source and public CLI/stdio MCP tests, full static checks and docs checks passed. The previous head's unrelated first-connect Hopper fixture race is being fixed separately; final CI is running on this head.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: b03df22ce4

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Validate each alias read after initialization and retain the original function capture across copies. Share declaration initializer facts with RPC and Electron analysis, including class declarations used for fresh-target identity. Accept single-statement control blocks while keeping lexical roles and added operations checked. Cover the capture regressions through inert source and public CLI/MCP workflows.
Function declarations provide fresh targets before their textual position. Retain initialization-order checks for variable and class values, including aliases. Cover the reviewed regression with source controls and the public CLI/MCP fixture.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6b460683d7

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3d1d5b56b2

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@N0zoM1z0

N0zoM1z0 commented Oct 11, 2026 •

Copy link
Copy Markdown
Collaborator Author

Merged #1857 (9b3e598) and completed the remaining receiver correction in #1912 (9d8e42b; fixes #1909). All 488 focused tests pass, including four production CLI/stdio MCP cases; the public T3 boot/main source subset retains four windows, zero parse failures and both unresolved preload expressions.

The eventual sole #1912 CI test failure was a separate static Wasm/Harmony wording-audit omission. #1917 fixes it; all four test shards and CI required pass. Both requested coauthors are preserved and recognized on the actual main commits. Verification covers Linux static workflows; no target runtime or GUI provider claim.

N0zoM1z0 and others added 2 commits October 11, 2026 16:25
Keep repeated variable declarations with one unconditional initializer while
rejecting assignments, conditional initialization and multiple values.
Normalize known intrinsic calls, aliases and bound argument prefixes at the
semantic owner, retaining opaque targets without tainting unused bindings or
fresh local objects. Cover both regressions through source and CLI/MCP tests.

Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
Co-authored-by: Kaoru0822 <208281322+kaoru0822-kitauji@users.noreply.github.com>
Include the merged Hopper reconnect-listener readiness fix so local and CI
validation use the same current main recovery boundary.

Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
Co-authored-by: Kaoru0822 <208281322+kaoru0822-kitauji@users.noreply.github.com>

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: b60248c462

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3e9bce6249

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ad27b8b4ff

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@morluto
morluto merged commit 9b3e598 into main Oct 11, 2026
26 checks passed
@morluto
morluto deleted the fix/1842-electron-interop-provenance branch October 11, 2026 17:06
@github-actions github-actions Bot mentioned this pull request Oct 11, 2026
3 tasks done

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c98d326514

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

callee = unwrapJavaScriptExpression(callee).node;
if (visited.has(callee)) return undefined;
visited.add(callee);
let path = intrinsicPath(callee);

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Normalize sequence-wrapped intrinsic calls

When a known mutator is invoked through the common comma-call form (0, Object.defineProperty)(Object, "create", descriptor), intrinsicPath(callee) receives a SequenceExpression, so neither it nor boundIntrinsic recognizes the invocation. The write to Object.create is omitted, allowing the subsequent Rolldown helper proof to trust the replacement and falsely attribute Electron APIs. Normalize a sequence callee to its final expression while retaining traversal of preceding expressions.

AGENTS.md reference: AGENTS.md:L17-L19

Useful? React with 👍 / 👎.

node: t.Node,
path: readonly string[],
): boolean => {
const capture = capturedIntrinsic(node)?.capturedAt ?? node;

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Preserve alias capture time when invoking through call

When a function is captured before its global property is replaced and later invoked through a member, such as const define = Object.defineProperty; Object.defineProperty = replacement; define.call(null, metadata, "x", descriptor), capturedIntrinsic(define.call) timestamps the whole path at the later .call read. The earlier replacement therefore appears to invalidate define even though that alias still holds the original function, and the otherwise harmless local-object mutation becomes an opaque intrinsic write that suppresses valid Electron findings from helpers using the same capture. Preserve the base alias's capture time separately while checking the newly read call member at invocation time.

AGENTS.md reference: AGENTS.md:L17-L17

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: domain Domain logic, errors, and pure functions bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug] Electron interop helper names can attribute unrelated constructors to Electron

2 participants