From 9651d73b6cd7268d76f4e8f6a92391ca99738b4a Mon Sep 17 00:00:00 2001 From: Julian Noble Date: Wed, 22 Jul 2026 09:27:54 +1000 Subject: [PATCH] G-101 notes: the promised G-103 family payload contract now exists - record the 8.6 target shape Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com --- goals/G-101-tcl86-kit-container-strategy.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/goals/G-101-tcl86-kit-container-strategy.md b/goals/G-101-tcl86-kit-container-strategy.md index 863de5b9..bb6216db 100644 --- a/goals/G-101-tcl86-kit-container-strategy.md +++ b/goals/G-101-tcl86-kit-container-strategy.md @@ -58,3 +58,12 @@ wrap), and only worth activating once G-099/G-100 land. those copies is a known wart (Tcl core TIP 741, windows-framed). This goal's "loading binary dlls from or via the container" acceptance should characterize that cleanup per platform - TIP 741 detail + requirement in G-103 Notes. +- 2026-07-22: the G-103 family attached-image contract this goal was promised as + its concrete payload target now EXISTS (G-103 Progress 2026-07-22): a family + runtime's image is tcl_library/ at the container root position the boot + searches, tm tree at tcl9/ (8.6: tcl8/), batteries at lib/ + with installed-shape pkgIndexes + dlls at bin/, and a one-line stock + auto_path hook at lib/pkgIndex.tcl. The 8.6 container investigation targets + delivering THAT payload shape (adjusted for 8.6 boot: no zipfs /app anchor - + the metakit/cookfs/zipvfs mount point plays the /app role and the hook + mechanism must be re-verified against 8.6's tclPkgUnknown).