From ec3e664edf493dac72d73481f92ea9c71fdfdc8b Mon Sep 17 00:00:00 2001 From: Julian Noble Date: Mon, 27 Jul 2026 20:07:03 +1000 Subject: [PATCH] G-130: archive markers on archived-goal mentions (goals_lint sweep) Clears the 5 informational goals_lint warnings, all on this file: G-096, G-098, G-099, G-100 and G-103 were referenced with no achieved/archive marker anywhere. The check reads a 3-line window around each G- mention for achieved|archive|landed and ORs across every mention in the file, so ONE marked mention clears an id. That matters here: G-103's only mentions are in Scope (index-canonical) and Acceptance (detail-canonical), both proposal-first. Neither is touched - the marker goes in Notes per the goals/AGENTS.md Archive rules, carrying the archive path and stating what G-103 contributes (the artifact- metadata contract those two lines name: a published runtime's record carries its target, which for this goal must name the 32-bit platform). G-096/G-098/G-099/G-100 are marked in place in Context. That mention is pure history - the phrasing was already factual rather than pending-tense - so a compact "all achieved and archived" is proportionate to the rules' guidance rather than four inline archive paths. Context paragraph reflowed to the file's ~90-char wrap (the marker insertion had pushed one line to ~118). Body lines now top out at 97, a pre-existing line; the 1180-char maximum is the Acceptance line, single-line by header grammar and unchanged. goals_lint clean (84 active-index goals, 50 archived). Claude-Session: https://claude.ai/code/session_01Y1diJnhjUxKgEG6EwYAzxj Assisted-by: harness=claude; primary-model=claude-opus-5[1m]; api-location=anthropic.com --- goals/G-130-32bit-windows-buildsuites.md | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/goals/G-130-32bit-windows-buildsuites.md b/goals/G-130-32bit-windows-buildsuites.md index 7bb9c583..f5dffdd7 100644 --- a/goals/G-130-32bit-windows-buildsuites.md +++ b/goals/G-130-32bit-windows-buildsuites.md @@ -16,10 +16,11 @@ windows Tcl available for BOTH majors, which means today the answer is assembled third-party builds of differing vintage and provenance. punkshell already builds Tcl from source with a pinned zig toolchain for both generations -(suite_tcl90, suite_tcl86 - G-096/G-098/G-099/G-100), and G-105 establishes the target as -an invocation dimension rather than a tree copy. 32-bit windows is the first target where -the change is one of BITNESS rather than OS, which is what makes it worth its own goal: it -exercises pointer-size and ABI assumptions that a linux-x86_64 cross does not. +(suite_tcl90, suite_tcl86 - G-096/G-098/G-099/G-100, all achieved and archived), and G-105 +establishes the target as an invocation dimension rather than a tree copy. 32-bit windows +is the first target where the change is one of BITNESS rather than OS, which is what makes +it worth its own goal: it exercises pointer-size and ABI assumptions that a linux-x86_64 +cross does not. Two third-party 32-bit runtimes now sit in `bin/runtime/win32-ix86/` and serve as the comparison baseline for what a suite-built pair would replace: @@ -64,6 +65,9 @@ the other's generation. decided there, not here. THIS GOAL PRODUCES RUNTIMES, NOT KITS: kit/container type is deliberately out of Scope, so a 32-bit runtime that is not yet wrappable still satisfies it. The two meet when G-101's decision lands. +- G-103 (achieved 2026-07-22 - see goals/archive/G-103-runtime-kit-family.md) defines the + artifact-metadata contract the Scope and Acceptance above name: a published runtime's + record carries its target, which for this goal must name the 32-bit platform. - Related: G-123 - the artifacts publish through the runtime-tier mechanism, and `punk-runtime.cmd list -platform win32-ix86` is where a user would see suite-built runtimes appear beside the third-party ones.