First punkbin publication of the G-103 family (suite_tcl90 kit-family
emission, byte-identical sha1s to the recorded goal evidence):
tclsh9.0.5-r1.exe (plain), tclsh9.0.5-punk-r1.exe (piperepl default-ON),
tclsh9.0.5-punk-bi-r1.exe (+Tk/tklib) - each with its .toml metadata
record (variant, working name, sha1, battery versions, source-checkout
provenance, toolchain, test evidence). These are the repo's first
metadata-carrying artifacts; r1 is now IMMUTABLE - any republish of
these (patchlevel, variant) pairs must use -Dfamilyrev=2.
defaults.txt: win32-x86_64 flips from tclsh902z.exe to
tclsh9.0.5-punk-r1.exe per the user's release decision (the recorded
publish-plus-flip-in-one-change-set process, validated by
build_sha1sums.tcl: 6 NEW, no CHANGED, defaults entries OK). README
recommended-runtime paragraph updated accordingly.
Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com
The default a no-name 'punk-runtime fetch' retrieves is a release
DECISION, so it lives on the artifact server as hand-curated data
(never generated) - updated in the same change-set that publishes the
artifact it points at, taking effect for every deployed punk-runtime
immediately with no punkshell release. src/build_sha1sums.tcl validates
entries (warns on unknown platforms / missing artifact files) so the
publish and the recommendation cannot drift silently.
Seeded from the values previously baked into punk-runtime's payloads,
with one correction those baked values got WRONG: linux-arm's actual
artifact is tclkit-9.0.2-Linux64-arm-dyn (dotted), not the baked
tclkit-902-Linux64-arm-dyn - a no-name fetch on linux-arm has been
broken until now, which is the config-in-code failure mode this file
removes. freebsd-x86_64 deliberately has no line (its only artifact is
a legacy 8.5-era kit, not a recommendation). Documented in AGENTS.md
Local Contracts with the release process.
Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com
Julian Noble