Motivation

This is the next PR in the backend connection ID analysis stack. The previous PR enriches parsed backend module records with domain-neutral import, export, star export, and top-level binding facts. The imported connection ID integration needs a reusable way to resolve those facts through the backend module graph without embedding import/export traversal inside connection ID-specific code.

Changes

Adds a domain-neutral static definition resolver for parsed backend module records. Given an ESTree identifier reference in a module, callers can resolve it to a concrete top-level const binding, or to a structured unsupported result with a stable reason code.

Example:

// actions.backend.ts
import { HTTP_CONNECTION_ID } from './connections';

request({
    connectionId: HTTP_CONNECTION_ID,
    inputs: {},
});

// connections.ts
const SOURCE_CONNECTION_ID = 'conn-http';
export const HTTP_CONNECTION_ID = SOURCE_CONNECTION_ID;

For the HTTP_CONNECTION_ID identifier in actions.backend.ts, the resolver follows the named import into connections.ts and returns the exported top-level const binding:

export const HTTP_CONNECTION_ID = SOURCE_CONNECTION_ID;

It does not evaluate the initializer into a string. That value-level evaluation is handled by the follow-up static string resolver PR.

The resolver is demand-driven: it follows named imports, local export aliases, named re-exports, local import/export relays, and unambiguous star exports for one requested symbol at a time.

Supported cases:

• Same-module identifier references to top-level const bindings
• Named imports through source module exports
• Local export aliases
• Named re-export aliases
• Local import/export relays
• Unambiguous star exports
• Explicit exports taking precedence over star exports

Unsupported cases return structured reason codes instead of throwing connection ID-specific errors.

Unsupported cases:

• Missing module records
• Missing exports
• Ambiguous star exports
• Import/export cycles
• Default imports
• Default exports and default re-exports
• Namespace imports
• Missing static bindings
• Mutable bindings
• Unsupported top-level declarations and binding patterns
• Unresolved identifiers and declaration identifiers

The result includes hop metadata so the follow-up connection ID PR can translate generic resolver failures into existing fail-closed diagnostics without recomputing graph traversal.

QA Instructions

No manual QA needed. This is an internal AST-analysis helper with focused unit coverage and no manifest behavior changes in this PR.

Blast Radius

This only affects the High Code Apps backend AST parsing internals in @dd/apps-plugin. The resolver is not wired into connection ID extraction or manifest output until the next stack PR, so customer-visible behavior should be unchanged.

Documentation

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