diff --git a/goals/archive/G-102-buildsuite-zig-bootstrap.md b/goals/archive/G-102-buildsuite-zig-bootstrap.md
index bc19a61e..f0435b82 100644
--- a/goals/archive/G-102-buildsuite-zig-bootstrap.md
+++ b/goals/archive/G-102-buildsuite-zig-bootstrap.md
@@ -85,14 +85,19 @@ PATH-scrubbed no-tclsh demonstration (clean checkout):
   per-checkin tarballs materialized into _build/suite_tcl90 (stagetree pin
   markers; packages verified against the manifest hashes by zig's fetch layer),
   recipe staged, and the nested staged build ran install + install-libraries +
-  make-zipfs + smoke + tklib + tcllib + tcllibc - ALL GREEN: suite_smoke
-  static+zip (9.0.5; zip proves attached tzdata+autoload), tklib tooltip:2.0.4
-  under withdrawn Tk, tcllib md5:2.0.9 sha1:2.0.5 cmdline:1.5.3, tcllibc:2.0
-  with md5-critcl-accel:1 (critcl driving zig cc). tcl::build-info of the demo
-  shell reports 9.0.5+1a9c3b9d... - IDENTICAL to the fossil-flow build: the zon
-  pins are the exact checkouts the promoted punk905 runtime was built from.
-  (The build pipeline was additionally green in an earlier pass with PATH = the
-  zig dir ALONE - not even cmd.exe.)
+  make-zipfs + smoke + tklib + tcllib + tcllibc. The clean SINGLE-INVOCATION
+  composite (true exit 0, clone updated to 4d9c8a26 after the echo-banner
+  finding below) produced all four shells in out/bin
+  (tclsh90s/tclsh90spr/tclsh90szip/tclsh90sprzip) with every smoke green:
+  suite_smoke static+zip (9.0.5; zip proves attached tzdata+autoload), tklib
+  tooltip:2.0.4 under withdrawn Tk, tcllib md5:2.0.9 sha1:2.0.5 cmdline:1.5.3,
+  tcllibc:2.0 with md5-critcl-accel:1 (critcl driving zig cc). Earlier scrubbed
+  passes at e5db0513 had proven the same steps green individually while the
+  composite was failing on the banner steps - the compile-only portion was also
+  green with PATH = the zig dir ALONE, not even cmd.exe. tcl::build-info of the
+  demo shell reports 9.0.5+1a9c3b9d... - IDENTICAL to the fossil-flow build:
+  the zon pins are the exact checkouts the promoted punk905 runtime was built
+  from.
 - Test gate ('zig build bootstrap -Dsteps=test-gate', scrubbed): totals 69552
   run, 56075 passed, 13468 skipped, 9 failed - 8 baselined plus fCmd-30.3,
   which is a scrub artifact (the test's expected result assumes
@@ -121,6 +126,12 @@ Environment findings (recorded for future suite work):
   without cmd.exe/COMSPEC/PATHEXT the winpipe/auto_execok/fCmd families fail
   spuriously (~52 extra), and fCmd-30.3 needs SystemDrive. These are properties
   of the tests, not the pipeline.
+- The recipe's five decorative 'echo --Installing package X--' banner steps
+  (2024-era) spawned 'echo' as a program - a cmd BUILTIN that only resolved
+  when a coreutils echo.exe happened to be on PATH. Scrubbed, the spawns failed
+  and took the tm installs, install-libraries and (transitively) make-zipfs
+  down - package steps green but no zip-wrapped shells. Removed 4d9c8a26; the
+  pipeline is now spawn-clean of incidental external commands.
 - First socket listen by a newly built shell at a new path raises the windows
   firewall consent dialog (user-observed and accepted mid-run during the first
   demo gate) - socket-family flakes in a first gate run on a fresh clone can be
@@ -135,9 +146,7 @@ Environment findings (recorded for future suite work):
   (the zip smoke deliberately excluded - its attached library is under test).
 
 Residual: out/bin/tclsh90sprzip.exe in the MAIN repo's fossil-flow stage is
-pending one install copy (the file was held open by a user application through
-the verification window; the product builds and installed cleanly in the demo
-clone, and the next make-zipfs run installs it once released). The G-104
+RESOLVED 2026-07-21: the user application released the file and the pending copy completed - all four shells current in both the fossil-flow stage and the demo clone. The G-104
 make.tcl surface will front these flows; -Dtestargs passthrough on bootstrap
 mode (currently a staged-invocation option only) is a G-104-adjacent nicety.