diff --git a/goals/G-123-thirdparty-runtime-tiers.md b/goals/G-123-thirdparty-runtime-tiers.md
index 4008f4db..c709a090 100644
--- a/goals/G-123-thirdparty-runtime-tiers.md
+++ b/goals/G-123-thirdparty-runtime-tiers.md
@@ -164,11 +164,18 @@ see goals/archive/G-058-static-runtime-packages.md).
     embedded-vs-sidecar consistency gate now expects v2; family_check.tcl
     asserts embed_schema 2 AND pins the literal 'class = "suite-built"'
     line (its flat rfield scan would see [artifact] class first - the
-    documented caveat, pinned as designed). Verified so far: zig ast-check
-    clean, both tools parse (fail-fast option errors); the functional
-    family-build proof (kit-family + kit-family-artifacts steps under
-    suite.tcl) is the next verification step - v2 records appear in
-    artifacts only from the next published family revision.
+    documented caveat, pinned as designed). VERIFIED live same day:
+    suite.tcl build -steps {kit-family kit-family-artifacts} PASS - all
+    three variants re-wrapped with the v2 embedded record and family_check
+    reports "schema 2 (provenance class suite-built)" for plain/punk/
+    punk-bi; family_artifacts emitted all three sidecars through the
+    v2-expecting consistency gate into out/family staging. (The mid-log
+    critcl "failed command" block is the recorded zig-0.16
+    stderr-echo-on-success trap - warnings on stderr, step succeeded.)
+    PUBLICATION NOTE: the staging artifacts still carry -r2 names but now
+    differ from the PUBLISHED r2 bytes (v2 record + non-reproducible
+    dlls) - publishing v2 runtime records is a deliberate user step that
+    bumps to -r3; never overwrite the published r2.
   - punkbin side (git 1f10390, LOCAL ONLY - not pushed; publication stays
     the maintainer's call): 12 retroactive schema-v2 sidecars across all
     five runtime tiers - every pre-family artifact now carries