Flip G-101 (kit container strategy for zig-built Tcl 8.6 runtimes) to
active in both tiers per the user's activation instruction. SEQUENCING
prose updated to record the activation; goals_xref score re-run at
activation per the freshness rule - one new relationship recorded: a
Related: G-130 back-pointer (its ix86 runtimes are the second platform
the container decision must fit; G-153 delivered mk4 dual-arch).
goals_lint clean (83 active / 71 archived).
Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com
### G-101 [proposed] kit container strategy for zig-built Tcl 8.6 runtimes (no zipfs)
### G-101 [active] kit container strategy for zig-built Tcl 8.6 runtimes (no zipfs)
Scope: investigation + decision record under src/buildsuites/suite_tcl86/ (or successor mechanism); src/buildsuites/suite_tcl86/patches/ (tracked sdx wrap.tcl provenance capture); TEMP_REFERENCE/{metakit_jnorthrup,KitCreator,kbs,sdx,tcl9} (read-only guidance - inventory in the detail file); src/runtime/mapvfs.toml ('kit' type consumers); src/make.tcl kit-wrap path (as consumer); bin/sdx.kit (the tracked wrapping tool - provenance is part of this goal)
# G-101 kit container strategy for zig-built Tcl 8.6 runtimes (no zipfs)
Status: proposed
Status: active
Scope: investigation + decision record under src/buildsuites/suite_tcl86/ (or successor mechanism); src/buildsuites/suite_tcl86/patches/ (tracked sdx wrap.tcl provenance capture); TEMP_REFERENCE/{metakit_jnorthrup,KitCreator,kbs,sdx,tcl9} (read-only guidance - inventory in the detail file); src/runtime/mapvfs.toml ('kit' type consumers); src/make.tcl kit-wrap path (as consumer); bin/sdx.kit (the tracked wrapping tool - provenance is part of this goal)
Goal: a decided, demonstrated strategy for wrapping zig-built 8.6 runtimes into self-contained punk86-class kit executables in the absence of zipfs - candidate containers: the metakit/mk4vfs tclkit lineage, cookfs, and zipvfs-over-tclvfs boot - so the prebuilt third-party kit runtimes (tclkit86bi.exe, tclkit-win64-dyn.exe) can eventually be replaced by suite-built, provenance-carrying ones.
Acceptance: the candidate containers are assessed and recorded here against punkshell's kit expectations (compatibility with make.tcl's 'kit' wrap path or a documented replacement path; boot-time vfs mount without an installed Tcl; loading binary dlls from or via the container; buildable from source under the zig-only policy); one strategy is demonstrated end-to-end - a kit wrapped from the suite-built 8.6 runtime boots on a path without any Tcl installation and runs a script from inside its vfs; the decision, rationale, and the follow-on work needed to reach punk86-kit parity are recorded in this file.
@ -36,12 +36,12 @@ Separated from G-099/G-100 deliberately: runtime + libs + test gating are
well-understood ports of the 9.0 work, while this is open investigation - keeping
it out of their acceptance keeps the 8.6 suite arc incrementally landable.
SEQUENCING: proposed; naturally last in the 8.6 arc (needs the G-099 runtime to
wrap). Both predecessors have landed - G-099 (achieved 2026-07-26 - see
goals/archive/G-099-suite-tcl86-buildsuite.md) built the runtime this goal wraps,
and G-100 (achieved 2026-07-26 - see goals/archive/G-100-suite-tcl86-tk-tcllib.md)
completed the dependency set that becomes this container's payload. The arc is
unblocked; activation is the user's call.
SEQUENCING: activated 2026-08-02 (user-directed), last in the 8.6 arc as planned
(needs the G-099 runtime to wrap). Both predecessors have landed - G-099 (achieved
2026-07-26 - see goals/archive/G-099-suite-tcl86-buildsuite.md) built the runtime
this goal wraps, and G-100 (achieved 2026-07-26 - see
goals/archive/G-100-suite-tcl86-tk-tcllib.md) completed the dependency set that
becomes this container's payload.
## Notes
@ -196,6 +196,13 @@ unblocked; activation is the user's call.
suite_tcl90) - a second fork-as-upstream package awaiting the same
suite-consumption era as the metakit records above; see
goals/archive/G-154-tclparser-punk-zig-build.md.
- Related: G-130 (recorded 2026-08-02 at activation, from the freshness survey):
its win32-ix86 runtimes are the second platform this goal's container decision
must fit. G-130 deliberately keeps kit/container type out of its own Scope
("THIS GOAL PRODUCES RUNTIMES, NOT KITS ... the two meet when G-101's decision
lands" - its Notes), and G-153 delivered the mk4 pieces dual-arch
(win32-x86_64 + win32-ix86), so the ix86 arm of whatever is decided here is
buildable from day one.
## Reference material (TEMP_REFERENCE, machine-local)
