[APPS][Superseded] Trace imported connection ID values

[sdkennedy2]

Status

This draft PR is superseded and is being closed intentionally.

Why This Is Not The Direction

This branch proved that imported connection ID value tracing is possible, but it bundled too many concerns into one review:

• enriching module graph records with import/export metadata
• traversing import/export relationships to resolve static definitions
• applying that resolver to action-catalog connectionId values
• reshaping connection ID extraction internals and documentation at the same time

That made the PR too large to review clearly and kept too much generic module graph logic inside connection ID-specific code.

Replacement Plan

Plan 014 now splits this work into smaller PRs:

1. build-plugins#371: enrich ParsedModuleRecord with domain-neutral module facts.
2. Follow-up PR: add generic static definition resolution over those records.
3. Follow-up PR: use that resolver to support imported connection ID values.

This PR is kept only as historical context for the prototype implementation. It should not be reviewed or merged.

QA Instructions

None. This draft is closed in favor of the split implementation above.

Blast Radius

No runtime or package impact. The PR is closed without merging.

[sdkennedy2]

• [APPS][Superseded] 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 👍 / 👎.

[sdkennedy2]

Closing this draft as superseded. The work is now split into smaller PRs starting with #371, followed by generic static definition resolution and then connection ID integration.