Skip to content

design: the ecosystem consumer resolves for three targets on the released engine #547

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Sunrisepeak merged 1 commit into from
Sep 2, 2026
Merged

design: the ecosystem consumer resolves for three targets on the released engine #547

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions .agents/docs/2026-09-02-runner-beyond-baremetal-design.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -908,6 +908,16 @@ fails when something is thrown, so a destructor run during the unwind is what
separates the two. It answers `yes` under the emulator, which means the runner
carried a working C++ runtime rather than merely starting the process.

The same consumer was then built for three targets from the same SubOS, to
establish that the release did not narrow what the ecosystem resolves:

```
x86_64-linux: BUILD-OK
aarch64-linux-musl: BUILD-OK
x86_64-windows-gnu: BUILD-OK
host run: RUN-OK
```

### 13.4 Release state

| | |
Expand Down
Loading