[swapnilpaliwal-sd]

Symptom

A name destructured out of a value whose declared type is an object type literal stays untyped, so every call on it is ambiguous_unknown, while the member access beside it resolves:

function f(opts: { port: Port }) {
  opts.port.execute(1);          // known_edge
  const { port } = opts;
  port.execute(1);               // ambiguous_unknown (before)
}
type Opts = { port: Port };
function g({ port }: Opts) { port.execute(2); }   // ambiguous_unknown (before)

Cause

The destructuring rules (binding_pattern_type, var_binding_target) read the source's type (param_type / expr_type). A type literal has no declaration to be a type. It is a shape (param_shape_target / expr_shape), and nothing on the destructuring side read shapes.

Fix

reference-types.dl gets a shape twin of each rule, for parameters (binding_pattern_shape) and variables (var_binding_shape), covering field types, nested shapes and methods. A shape is its own scope (scope_sibling(s, s)), so the existing declared_field / declared_method lookups are reused. No negation is added. param_type gets one more positive clause, built only from rows that sit below the expression fixpoint.

Tests

• New case 100-destructure-from-type-literal (oracle-checked). It covers inline and aliased literals, parameters and variables, a nested shape, and a shape method. Controls: an any source stays unresolved; a look-alike literal { execute(x) } resolves to its own method, not to Port.execute.
• Case 75-jsx-wrapper-guards: five destructured-prop calls now resolve to exactly the targets the compiler oracle had listed as known-missing, and the shadowing guard still holds. Its debt list drops from 6 entries to 1.
• Second commit, test tool: normalize_edges.py labelled a destructured parameter once per bound name (aliasParam(Opts,Opts,Opts); the compiler prints aliasParam(Opts)), so a right edge showed up as one missing plus one extra. It now keeps one row per position. Case 100 needs no known-missing file.
• Full TypeScript suite: 110/110.

Note for #2010: its case 99 lists three edges as known-missing only because of that label. Once both are in, those lines start passing and must be removed (re-bless 99 with --oracle).

Real project (1.9k-file Deno TypeScript repo)

	base 0.2.3	this PR
known_edge	7,410	7,441
ambiguous_unknown	35,820	35,789
resolved edges lost		0
index, warm	40.2 s	36.1 s

Spot-checked new edges: an interface method reached through const { transport } = opts with opts: { transport: Transport; ... }, and methods of an inline utils: { json: { omit(..) } } parameter type.

Stacks cleanly with #2010 (contextual destructured parameters); the two touch different rules.