bug: recognize binaries from previous sessions

[kbuffardi]

Description

when opening a previous project that has already been compiled, and trying to run the binary without re-compiling I get an error message such as:

Clang WASM compiler loaded. Ready to compile C++20.
browser.cpp:~$ ./a.out
No binary found. Compile first with:  g++ main.cpp

It shows a.out in the explorer and I confirmed it is in the directory but won't recognize it until I compile again.

Expected behavior

if a command is given to run a binary (such as ./a.out but not limited to that file name) the binary should be run if it exists in the workspace. The error message shown should only display if no file of that name is found.

Steps to reproduce

n/a

Environment

No response

Logs or screenshots

Additional context

No response

Before submitting

• I searched existing issues and did not find a duplicate.
• I have provided enough information to reproduce the issue.

[kbuffardi]

Codex plan (pending human review): make terminal run-target resolution accept an exact workspace file path (including nested/custom output paths) when no current-session artifact exists; carry that resolved path through the run callback; have the app load its bytes from the workspace snapshot for the worker; preserve the cached current-session artifact and existing missing-path errors. Add focused unit/E2E coverage for restored a.out, custom/nested targets, absent targets, and regression of the current-session flow. No code has been changed.

[kbuffardi]

Implementation is now available in PR #99. Per user decision, “it should try to recognize a matching workspace file”: explicit ./path commands resolve any exact workspace file and pass its bytes to the worker; invalid contents are reported by the runtime. The implementation also prevents stale cached binaries from executing for an explicit restored target.