[APPS][Connections Part 9] Trace imported connection ID values

[sdkennedy2]

Motivation

The backend connection ID stack can already find action-catalog calls in reachable backend helper modules, but it still fails closed when the connectionId value is imported from another local module. Real apps commonly keep connection IDs in shared connections or ids modules, so the manifest analysis needs to trace those imported static values without changing graph collection or reachability traversal.

Changes

This PR adds graph-aware import/export value tracing on top of the existing reachable module graph extraction. Module graph records now preserve enough resolved static import information for value tracing to map AST import/export source literals back to collected module records.

The connection ID resolver keeps the same same-module behavior by default, but graph extraction now passes an optional imported-value resolver. That resolver follows named imports, local export aliases, aliased re-exports, import/export relays, and unambiguous export * chains back to static exported constants or object roots. Imported object roots reuse the existing static object member resolver, so patterns like this are handled demand-first from an action-catalog call site:

import { CONNECTIONS } from './connections';

request({ connectionId: CONNECTIONS.HTTP.PROD, inputs: {} });

The implementation keeps the analysis conservative. Missing exports, mutable or reassigned exports, default and namespace imports, ambiguous star exports, import/export cycles, and unsupported object shapes still fail closed instead of silently producing an incomplete allowlist.

QA Instructions

Validated the apps plugin with typecheck, focused lint, focused AST/module graph tests, and the full apps plugin unit slice:

yarn workspace @dd/apps-plugin typecheck
yarn eslint packages/plugins/apps/src/backend/ast-parsing/connection-id-imports.ts packages/plugins/apps/src/backend/ast-parsing/connection-id-values.ts packages/plugins/apps/src/backend/ast-parsing/extract-connection-ids.ts packages/plugins/apps/src/backend/ast-parsing/extract-connection-ids-from-module-graph.ts packages/plugins/apps/src/backend/ast-parsing/module-graph.ts packages/plugins/apps/src/backend/ast-parsing/extract-connection-ids-from-module-graph.test.ts packages/plugins/apps/src/backend/ast-parsing/walk-module-graph.test.ts packages/plugins/apps/src/vite/backend-module-graph-collector.ts packages/plugins/apps/src/vite/backend-module-graph-collector.test.ts --quiet
yarn workspace @dd/tests test:unit packages/plugins/apps/src

Blast Radius

This affects High Code Apps backend connection ID manifest analysis for backend builds and dev backend execution. It only changes static analysis for app-local backend modules collected through the backend module graph; unsupported shapes continue to fail closed.

Documentation

• How to reliably make frontend production changes
• PR Description Guidelines
• Deploy steps

[sdkennedy2]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• [APPS][Connections Part 9] Trace imported connection ID values #365 👈 (View in Graphite)
• [APPS][Connections Part 8] Traverse backend module graph for connection IDs #362 : 1 other dependent PR (#363 )
• [APPS][Connections Part 7] Add reusable module graph walker #364
• [APPS][Connections Part 6] Build backend module graph during backend builds #353
• [APPS][Connections Part 5] Move apps Vite behavior into getVitePlugin #357
• [APPS][Connections Part 4] Resolve same-module connection ID object values #354
• [APPS][Connections Part 3] Resolve same-module connection ID constants #351
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

[sdkennedy2]

@codex review
@cursor review

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 98a8c40d8f

ℹ️ 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]

Preserve dependency alignment when sources repeat

When a module imports/re-exports the same source more than once before another source, this index-based pairing shifts every later resolution because Rollup exposes importedIds/importedIdResolutions once per unique source. For example import './a'; import './a'; import { HTTP_ID } from './ids'; produces dependencies [a, ids], but this maps the second ./a to ids and leaves ./ids unresolved as the literal string, so imported connection IDs from ./ids fail as outside the collected graph. Reuse the cached resolution for a source before consuming the next dependency index, or build the mapping directly from Rollup's source order.

Useful? React with 👍 / 👎.