[ScriptedAlchemy]

Why

Common TypeScript receiver patterns can break an otherwise useful call trace. Agents also need to connect two known symbols and understand where the recorded graph stops.

This adopts those capabilities from the comparison with @colbymchenry/codegraph, using TraceDecay's existing extraction, sealed graph, admitted query, source, and generated contract authorities.

Changes

Resolve supported TypeScript receivers

• Persist parser-derived receiver and declared-return evidence through extraction, sealed artifacts, resolution indexes, and resident-memory accounting.
• Resolve constructor-backed and explicitly typed instance receivers, including awaited imported factories with supported named return types. Resolve return names in their declaring module and preserve import aliases.
• Follow immutable const alias = receiver chains using the initializer's declaration scope. Generic constraints/defaults, parameter initializers, and computed property keys no longer create false receiver bindings.
• Keep mutable, reassigned, optional, ambiguous, cyclic, forward, and unsupported receivers unresolved. Every accepted edge stays bound to its call site and lexical scope.
• Re-resolve unchanged callers after factory-return edits, including after a sealed-generation restore. Scope changes re-extract the changed TypeScript file from its retained parse tree so distant binding edits cannot retain stale proof.

Return a connecting call path with context

• Add optional call_path to tracedecay_context, with exact endpoint IDs and a bounded depth. Reuse the admitted shortest-path query over indexed call edges.
• Return distinct found, no_path, truncated, and unavailable outcomes, ordered symbols, edge authority/evidence, and graph generation/freshness.
• When requested, include intermediate source within the existing code-block/token limits. Verify file identity and digest, sanitize content, and report explicit omission or unavailability.
• Bound source waiting by live cancellation, request deadline, and grant expiry, including completion races and dropped waiters. A blocked native file read cannot keep the requesting task waiting past its admitted lifetime.
• Preserve ordinary task context when graph authority is unavailable and existing behavior when no path is requested.

Explain recorded unresolved calls

• Add the required NodeDetailsV1.unresolved_calls report to the existing node operation, carrying its graph generation, caller/file identities, recorded reference name/span, optional argument count, and supported limitation reasons.
• Examine at most 16 retained evidence records for that exact caller and disclose complete, truncated, or unavailable. Non-call limitations consume the same read budget.
• Use the resident catalog and canonical admission/read-cost authority. Ordinary node metadata remains available while the catalog is rewarming; corrupt or unavailable evidence becomes a typed subreport.
• Preserve the same report in the ChatGPT extension's existing symbol inspection and chat-sharing journey. Show coverage state and snapshot mismatches, safely render unusual extracted names, and reject malformed required reports.
• Update the user guide, tool descriptions, canonical TypeScript SDK, and both embedded plugin bundles.

Scope and compatibility

The sealed format and affected extractor/chunker revisions are bumped. Older generations use the existing typed rebuild path; no compatibility shim is added.

Receiver inference remains bounded to parser-attested named types and supported declarations. The unresolved-call report describes retained extraction evidence: even a complete empty report does not prove that every possible runtime call resolves, and a recorded span may cover the enclosing declaration when extraction lacks an exact call token.

Framework-specific route discovery, event/job dispatch, and state-store/observer callback modeling remain outside this PR.

Validation

Passed locally on the updated source:

• Code-extraction main suite: 663 tests.
• TypeScript allocation/retained-extraction regressions: 2 tests, using the nonzero-test helper.
• TypeScript SDK typecheck, 111 Vitest tests across 6 files, and package build.
• ChatGPT plugin typecheck and 93 relevant tests across 6 files, including 15 new symbol-inspection tests.
• Canonical SDK generation, both embedded plugin builds, and the byte-exact embedded regeneration check.
• Rust formatting for 9 crates; all 61 generated BUILD.bazel files are current.
• Commit formatting/commitlint hooks and git diff --check.

The plugin's initial combined run passed 92 tests and failed the existing IPv6 loopback case because the local proxy exclusions lacked bracketed [::1]. With that entry added only to the test process's existing exclusions, all 13 adapter tests passed. No source, global proxy settings, test assertions, skips, or timeouts were changed for this environment issue.

Canonical SDK generation succeeded using command-local allocator settings and panic=abort only for the contracts crate and exporter binary. No tracked build policy or production/test configuration was changed, and no Rust tests were run under those exporter settings.

Backend verification remains incomplete locally. A final production metadata build with normal panic settings stopped in tracedecay-contracts with process_wrapper exit 1 and no Rust diagnostic. The host was under memory pressure, and its kernel OOM-kill counter increased from 95 to 98 over the verification period. This is not counted as a passing typecheck. Earlier full integration builds also stopped in the pinned runtime dependency/build environment.

The code-index/MCP integration suites and the new context-source lifetime unit tests have not run locally. Full Clippy and the combined dashboard contract freshness check also remain unverified. Source inspection found that the dashboard exporter uses separate schema roots, so there is no identified additional dashboard artifact change; the fresh canonical SDK export includes application.ts and the affected operations.ts.

Added backend regressions cover receiver resolution and sealed restores, exact caller/file evidence isolation, actual import/ambiguity limitations, bounded truncation/read cost, catalog rewarming, path source bounds, cancellation/deadline races, and disconnected/missing/zero-edge paths. Final-head repository CI is still required to verify these runtime behaviors.

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

[ScriptedAlchemy]

Current-head CI blocker (exact head f7f99115bbcd243da816ac1b2c2b01d2b3995279): Dashboard job 130214053904 executed its Bazel frontend/SDK targets, then the embedded-artifact verification failed with Error: embedded/server.mjs is stale; run pnpm run build and commit the result (job log near its final check). The PR changes the context operation schema and generated TypeScript SDK but its current diff contains no corresponding refreshed embedded/server.mjs. Please regenerate through the documented pnpm/build/codegen authority, commit generated outputs together with the canonical source changes, run the actual dashboard bundle/determinism + SDK contract checks, and get a new complete exact-head matrix. No hand-edits to generated output or bypassing the artifact check. This is a real current-head artifact drift failure, not a TypeScript unit-test failure or full Rust acceptance. I made no branch changes.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 9ec3e68

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR