From d0d2cf60401707f05a9370a190edabc05d1a5aed Mon Sep 17 00:00:00 2001
From: speak-agent <248744407+speak-agent@users.noreply.github.com>
Date: Wed, 2 Sep 2026 23:31:49 +0800
Subject: [PATCH] design: the ecosystem consumer resolves for three targets on
 the released engine

Section 13.3 recorded one target. The release changes what `[xlings]` accepts
and when a runner is consulted, and neither is target-scoped, so the criterion
that it narrowed nothing has to name more than the target it was written for.
---
 .../docs/2026-09-02-runner-beyond-baremetal-design.md  | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/.agents/docs/2026-09-02-runner-beyond-baremetal-design.md b/.agents/docs/2026-09-02-runner-beyond-baremetal-design.md
index d6b38981..d49627d4 100644
--- a/.agents/docs/2026-09-02-runner-beyond-baremetal-design.md
+++ b/.agents/docs/2026-09-02-runner-beyond-baremetal-design.md
@@ -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
 
 | | |