Include executed imported files in glTF exports

[Joe-Spencer]

Retain original foreign-import bytes and resolved paths with the successful execution snapshot, including external glTF buffers. glTF export forwards those executed inputs alongside KCL source, so cache hits and later file edits cannot pair exported geometry with newer file contents. Only executed imports are included; repeated identical paths deduplicate, while conflicting bytes and unrepresentable project paths produce an actionable glTF export error. Other export formats retain the existing KCL-source behavior.

Stacked on #14003. Depends on modeling-api #1442, format #925, and engine #5303. The API revision, Cargo lock entries, and Nix source hash are updated, and modeling-command bindings are regenerated.

Request-recording regressions cover exact non-UTF-8 bytes, nested buffer dependencies, unused assets, repeated imports, cached file changes, mock execution, failure/recovery, cross-drive paths, and unresolved traversal. A Studio import/export smoke test with the updated engine remains necessary before landing.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
modeling-app	Ready	Preview	Oct 8, 2026 6:37pm UTC

[codspeed]

Merging this PR will not alter performance

✅ 157 untouched benchmarks
⏩ 131 skipped benchmarks¹

---

_{Comparing codex/gltf-imported-files (571e94d) with codex/export-kcl-source (63a4731)}

Footnotes

1. 131 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩