From 6a69cbf85c2422a33b5612e255b8b38b30452291 Mon Sep 17 00:00:00 2001 From: Julian Noble Date: Fri, 24 Jul 2026 03:51:30 +1000 Subject: [PATCH] goals: xref reconciliation - kit/launcher/modpod cluster (G-019 G-023 G-028 G-029 G-031 G-057 G-077 G-089 G-109 G-111, recorded 2026-07-24) Assisted-by: harness=opencode; primary-model=openrouter/moonshotai/kimi-k3; api-location=openrouter.ai --- goals/G-019-dependency-scan-module-trimming.md | 4 ++++ goals/G-023-version-named-binaries.md | 4 ++++ goals/G-028-file-locker-identification.md | 4 ++++ goals/G-029-testmodules-from-srctests.md | 8 ++++++++ goals/G-031-componentized-kit-boot.md | 7 +++++++ goals/G-057-kit-icon-embedding.md | 13 +++++++++++++ goals/G-077-punkexe-dash-e-oneliner.md | 9 +++++++++ goals/G-089-scriptlib-kits-and-modes.md | 5 +++++ goals/G-109-libunknown-manifest-multiname-tm.md | 11 +++++++++++ goals/G-111-modpod-tidy-tests.md | 3 +++ 10 files changed, 68 insertions(+) diff --git a/goals/G-019-dependency-scan-module-trimming.md b/goals/G-019-dependency-scan-module-trimming.md index d10a0830..5a63fd7d 100644 --- a/goals/G-019-dependency-scan-module-trimming.md +++ b/goals/G-019-dependency-scan-module-trimming.md @@ -64,5 +64,9 @@ here. - Interacts with G-005/G-006 (how the c-only tclparser binary is provisioned if chosen) and G-018 (the spectrum of executable flavours). +- G-115 relationship (recorded 2026-07-24 after overlap review; neither file + previously referenced the other): the scan closure plus declared dynamic + extras is a payload-determination input G-115's toml materialization can + consume - a trimmed kit is then a declared kit with a generated declaration. - punk::lib sites already noting tclparser use/fallback: tclword_to_scriptlist and related parsing helpers (~lib 3322-3580). diff --git a/goals/G-023-version-named-binaries.md b/goals/G-023-version-named-binaries.md index 52ff75f5..e450ac5d 100644 --- a/goals/G-023-version-named-binaries.md +++ b/goals/G-023-version-named-binaries.md @@ -86,3 +86,7 @@ binary-artifacts repository). Revisit when the accumulation actually bites. DECISION section (achieved 2026-07-22 - goals/archive/G-103-runtime-kit-family.md; the decision text is stable there flipped). +- G-057 relationship (recorded 2026-07-24 after overlap review): the + icon-embedding step hooks the same kit wrap steps; its ordering constraint + (icon the stub before payload append) interacts with this goal's every-build + rewrite cadence. diff --git a/goals/G-028-file-locker-identification.md b/goals/G-028-file-locker-identification.md index 4c908d1b..89224930 100644 --- a/goals/G-028-file-locker-identification.md +++ b/goals/G-028-file-locker-identification.md @@ -79,3 +79,7 @@ the kind of file this fails on. or the same Restart-Manager-adjacent infrastructure this goal introduces) is the fix, and a locker-report helper that returns paths would serve both. (G-030 achieved 2026-07-14 - goals/archive/G-030-maketcl-punkargs.md) +- G-057 relationship (recorded 2026-07-24 after overlap review): its PE + resource update hits the same locked-target failure class when an inspected + or running kit is being re-wrapped - the locker-report helper covers the icon + step's failures as well as deploy's. diff --git a/goals/G-029-testmodules-from-srctests.md b/goals/G-029-testmodules-from-srctests.md index 747941d8..420184a5 100644 --- a/goals/G-029-testmodules-from-srctests.md +++ b/goals/G-029-testmodules-from-srctests.md @@ -76,3 +76,11 @@ are now fossil-tracked and must be kept in sync by hand until this goal lands. - The packaging step's output is a build artifact by policy even though it lives under src/ - the punkcheck records make regeneration cheap and hand-edits detectable. +- G-109 relationship (recorded 2026-07-24 after overlap review; neither file + previously referenced the other): generated test:: modpods are + manifest-emission consumers - when G-109's manifest lands in the wrap + tooling, the packaging step emits it (multi-name for test::punk::foo-style + sub-packages). +- G-111 relationship: G-111's modpod tidy plus first test baseline is the + machinery-health floor this goal's generation step builds on - sequence + after it. diff --git a/goals/G-031-componentized-kit-boot.md b/goals/G-031-componentized-kit-boot.md index 4e17fe36..bcfde195 100644 --- a/goals/G-031-componentized-kit-boot.md +++ b/goals/G-031-componentized-kit-boot.md @@ -80,6 +80,13 @@ permanently own - a thousand lines of boot code. (boot-core vintage reporting), G-032 (punk::args-defined dispatch built on the registration model), G-012 (layout payload hygiene), G-018 (plain tclsh kits deliberately carry NO punk boot layer - out of scope here). +- G-089 relationship (recorded 2026-07-24 after overlap review): its + boot-provided packagemode hint (for scriptlib resolution) is a boot-core + interface this goal's registration model should carry - one boot "running + state" surface, not per-feature side channels. +- G-118 relationship: its item-9 project_main.tcl parity duplication is + deliberately interim (recorded in G-118's decision line); this goal's boot + core is the consolidation path. - The tomlish silent-exe incident (2026-07-07, tomlish 1.1.10 fix) is a reminder that launch-path contracts are easy to break invisibly - behaviour parity in the acceptance means exercising each dispatch case, not just diff --git a/goals/G-057-kit-icon-embedding.md b/goals/G-057-kit-icon-embedding.md index 78ae0c46..d04c6e51 100644 --- a/goals/G-057-kit-icon-embedding.md +++ b/goals/G-057-kit-icon-embedding.md @@ -71,3 +71,16 @@ delete-then-write). Requirements sketch agreed 2026-07-10: (compare icon group/images against the source .ico), not visual inspection. - Linux/other-platform kit outputs have no PE resources - explicitly out of scope; the skip path covers them. +- G-023 relationship (recorded 2026-07-24 after overlap review; this file + previously referenced nothing): its versioned/dev outputs are rewritten every + build - the icon step hooks the same kit wrap steps, and the + icon-before-payload-append ordering is settled against that rebuild cadence. +- G-024 relationship: the per-kit icon override convention may become a mapvfs + element; if so it lands in G-024's toml grammar, not the legacy line format. +- G-028 relationship: a locked kit exe blocks the resource update exactly as it + blocks deploy - G-028's locker-report helper should name the holder on + icon-step failure too. +- G-025/G-117 note: the parked RT_VERSION follow-on above stamps + version/copyright resources from punkproject.toml - when it is drafted as a + goal, reconcile with G-025's kit stamp and G-117's embedded artifact record + so the three provenance surfaces tell one story. diff --git a/goals/G-077-punkexe-dash-e-oneliner.md b/goals/G-077-punkexe-dash-e-oneliner.md index bdfb79d5..df58280b 100644 --- a/goals/G-077-punkexe-dash-e-oneliner.md +++ b/goals/G-077-punkexe-dash-e-oneliner.md @@ -19,3 +19,12 @@ The punk kits currently fail fast instead (`punk script: script file not found: no one-liner form. This goal makes the instinct work on punk executables, removing the failure class for the kits entirely. app-punkscript's existing stdin form already provides the execution scaffolding (argv0/argv setup, errorInfo-to-stderr, exit-code discipline). + +## Notes + +- G-118 relationship (recorded 2026-07-24 after overlap review; neither file + previously referenced the other): G-118 (active) settled the stock leading-dash + fallthrough this goal must not disturb - ` tclsh -e ...` deliberately + keeps stock's -e misparse (stock parity is the tclsh subcommand's contract, per + its cross-note); the one-liner instinct is served only at the top level and via + `script -e`. Its item-10 definitions (G-032-compatible) will state this boundary. diff --git a/goals/G-089-scriptlib-kits-and-modes.md b/goals/G-089-scriptlib-kits-and-modes.md index 51b55674..98e7e694 100644 --- a/goals/G-089-scriptlib-kits-and-modes.md +++ b/goals/G-089-scriptlib-kits-and-modes.md @@ -62,3 +62,8 @@ Findings from the 2026-07-18 lib: extensionless work (punk::path 0.3.0): (a resolvable scriptlib/utils/pwsh file still wins when present, so shipping scriptlib remains dev-friendly, just not required for raw mode). See goals/archive/G-106-powershell-consolemode-fallback.md. +- G-031 relationship (recorded 2026-07-24 after overlap review; neither file + previously referenced the other): the packagemode "running" hint this goal + needs from the boot layer (Context above) lands in G-031's shared boot core - + implement the hint against the componentized shape if G-031 has landed, or + record the seam in its registration model otherwise. diff --git a/goals/G-109-libunknown-manifest-multiname-tm.md b/goals/G-109-libunknown-manifest-multiname-tm.md index 73d305e1..b9cf07d5 100644 --- a/goals/G-109-libunknown-manifest-multiname-tm.md +++ b/goals/G-109-libunknown-manifest-multiname-tm.md @@ -72,3 +72,14 @@ mount path - the 8.6 leg of acceptance), TIP 590 (lowercase naming), G-110 or a byplatform// parent). Candidate defensive extra for THIS goal's manifest format: a declared target-platform field, letting libunknown skip/refuse wrong-platform binary .tm even when someone shares a path. +- G-114 relationship (recorded 2026-07-24 after overlap review): G-114 + formalizes the roots/boot-wiring half of the 2026-07-22 platform discussion + recorded above; this goal keeps the manifest format and the declared + target-platform field stays this goal's item (per the division of labour + recorded there). +- G-029 relationship: its generated test:: modpods become manifest + consumers once this goal's emission lands in the wrap tooling (multi-name for + test::punk::foo-style sub-packages). +- G-111 relationship: G-111's modpod tidy plus first test baseline is the + precursor - its cleanup and round-trip pins land before this goal's manifest + edits to the same module. diff --git a/goals/G-111-modpod-tidy-tests.md b/goals/G-111-modpod-tidy-tests.md index 3cfb2a94..189afa3a 100644 --- a/goals/G-111-modpod-tidy-tests.md +++ b/goals/G-111-modpod-tidy-tests.md @@ -72,3 +72,6 @@ leg of the testsuite). - 2026-07-21: drafted from the session findings and approved (user: "approved - apply G-111"). +- G-029 relationship (recorded 2026-07-24 after overlap review): its + testmodpod generation exercises the same wrap+load round-trips this goal's + baseline pins - the two suites share fixtures where sensible.