diff --git a/goals/G-153-metakit-punk-zig-port.md b/goals/G-153-metakit-punk-zig-port.md index 48f27b36..264c98ef 100644 --- a/goals/G-153-metakit-punk-zig-port.md +++ b/goals/G-153-metakit-punk-zig-port.md @@ -106,15 +106,19 @@ section) and as the proof that a zig-built Mk4tcl works at all. Audit COMPLETE - see Progress increment 3 and the disposition table in metakit_punk src/reference/AGENTS.md: zero to port, every live lineage already absorbed by the 2.4.9.8 baseline, three autoconf-era rejects. -- Draft sources.config record for suite_tcl86 (name/dir chosen to match the - gitea repo name; dir names are recipe-coupled per that file's header): - `source metakit git https://www.gitea1.intx.com.au/jn/metakit metakit` +- READY-TO-LAND sources.config record for suite_tcl86 (concrete as of the + increment-5 pin capture; name/dir chosen to match the gitea repo name; dir + names are recipe-coupled per that file's header): + `source metakit git https://www.gitea1.intx.com.au/jn/metakit 6a92b47955c986e8d04db0a3f9555710482bc56d metakit` (commit pin like punkzip - the fork carries no tags yet; the ssh origin ssh://git@pcm-gitea1.corp.intx.com.au:2222/jn/metakit is the push remote, the https web URL is the fetch/pin form). -- Draft build.zig.zon record for suite_tcl86 (hash computed with the pinned zig - at landing time - 'zig fetch' from the suite dir per that file's TRAP note): - `.metakit = .{ .url = "https://www.gitea1.intx.com.au/jn/metakit/archive/.tar.gz", .hash = "", .lazy = true },` +- READY-TO-LAND build.zig.zon record for suite_tcl86 (hash computed with the + pinned zig 0.16.0 on 2026-08-02, 'zig fetch' run from a build.zig dir per + that file's TRAP note): + `.metakit = .{ .url = "https://www.gitea1.intx.com.au/jn/metakit/archive/6a92b47955c986e8d04db0a3f9555710482bc56d.tar.gz", .hash = "metakit_punk-0.1.0-fjiV29tTbQAB6kfuzK76YFyu7-HYnwGJKwNlMFyBTECZ", .lazy = true },` + Landing these two records in suite_tcl86 remains G-101-era consumption per + Scope - the capture here completes this goal's pin clause. - UCRT/deployment: adding the C++ engine to shells changes exe size, not the redistribution story - zig links libc++ statically on windows-gnu and the CRT import surface stays the UCRT set measured in G-130 Notes (2026-08-02). @@ -263,9 +267,19 @@ the stubs contract exercised across patchlevel AND CRT lineage; transcript identical to the above but tclsh/tcl lines reading tclsh8.6.10-luck-zip.exe / 8.6.10). +Increment 5 landed 2026-08-02: the PIN-CAPTURE acceptance clause is MET. +User pushed metakit_punk to the gitea origin; verified origin/master == +local master == 6a92b47955c986e8d04db0a3f9555710482bc56d (the increment-4 +tip - all seven fork commits up). zig package hash for the pinned archive +computed with the pinned zig 0.16.0: +metakit_punk-0.1.0-fjiV29tTbQAB6kfuzK76YFyu7-HYnwGJKwNlMFyBTECZ. The +ready-to-land sources.config and build.zig.zon record text is now CONCRETE +in the Notes above (the two READY-TO-LAND bullets). Every 'zig build' / +'zig build test' / demos / interchange / mk4tcl / smoke verification in +increments 1-4 was run at exactly this tree state, so the pinned commit is +the verified commit. + Remaining for acceptance: - Static-embed shape (Tcl_StaticPackage) into a kit-class shell copy, or its - blocker recorded here. -- Fork commit pinned + ready-to-land sources.config and build.zig.zon record - text captured here (drafts above become concrete once the port is pushed; - 7 commits pending push as of increment 4). + blocker recorded here. (Suite-side experiment: a tclsh86ts variant per the + suite recipe - next work unit.)