diff --git a/goals/G-101-tcl86-kit-container-strategy.md b/goals/G-101-tcl86-kit-container-strategy.md
index 67e560d6..863de5b9 100644
--- a/goals/G-101-tcl86-kit-container-strategy.md
+++ b/goals/G-101-tcl86-kit-container-strategy.md
@@ -49,7 +49,9 @@ wrap), and only worth activating once G-099/G-100 land.
   Consequence for the container choice: "loadable binary batteries" implies a
   DYNAMIC-libc runtime - a fully-static-libc 8.6 kit would hit the same 'load'
   limitation G-105 records for linux (the compiled-in static-packages
-  alternative is G-058). The container question (metakit/cookfs/zipvfs) is
+  alternative is G-058, achieved 2026-07-10 - see
+  goals/archive/G-058-static-runtime-packages.md). The container question
+  (metakit/cookfs/zipvfs) is
   orthogonal to the libc-linking question; keep them separate at activation.
 - 2026-07-21: temp-copy cleanup applies here too - Metakit/starkit 'load' copies
   the extension out of the VFS to a temp dir (same as zipfs), and cleanup of
diff --git a/goals/G-105-buildsuite-cross-target.md b/goals/G-105-buildsuite-cross-target.md
index 647809c9..204cdf0b 100644
--- a/goals/G-105-buildsuite-cross-target.md
+++ b/goals/G-105-buildsuite-cross-target.md
@@ -47,7 +47,9 @@ dimension), G-102 (achieved 2026-07-21 - driver shape settled; target becomes a
   embedded VFS, not by static-linking libc), so the fully-static-musl 'load'
   limitation stands and dynamic (glibc-stub-dynamic with a version floor, or
   musl-dynamic) is the tclkit model. Compiled-in batteries ('load {} <pkg>', no
-  dlopen) are G-058's alternative. Don't re-litigate at activation.
+  dlopen) are G-058's alternative (achieved 2026-07-10 - see
+  goals/archive/G-058-static-runtime-packages.md). Don't re-litigate at
+  activation.
 - 2026-07-21: per-platform temp-file cleanup is part of verifying dynamic-loaded
   batteries here - a shared lib loaded from a kit's VFS is copied to a temp dir
   first (dlopen/LoadLibrary need a real file) and cleanup of those copies is a