G-101 Scope: sync both tiers on the survey-extended wording

The pre-activation survey (f4031b20) extended G-101's Scope in the detail file
but not the index, leaving goals_lint at exit 1 on the Status/Scope mirror
check. Scope is a contract element canonical in the INDEX, so the detail-file
edit was both the wrong tier and not proposal-first - that commit's "Notes-only
on the goal" opening misclassified it. A clean lint run would not have caught
the underlying problem either: had both tiers been edited together lint would
have passed green with the contract change still unapproved. goals_lint checks
consistency, not authorization.

User-approved this session: the index moves to the extended wording rather than
the detail file reverting - the survey genuinely brought bin/sdx.kit and three
further reference trees into the goal's territory.

Both tiers now carry an identical, tier-neutral line. The survey's "see ...
below" cross-references resolve only inside the detail file while the index
entry must stay safe standalone (GOALS.md Format), so they become "inventory in
the detail file". src/buildsuites/suite_tcl86/patches/ is added: the sdx
wrap.tcl provenance capture is tracked material this goal now owns and was named
in neither tier.

goals_lint clean (79 active-index goals, 44 archived).

Claude-Session: https://claude.ai/code/session_01Y1diJnhjUxKgEG6EwYAzxj
Assisted-by: harness=claude; primary-model=claude-opus-5[1m]; api-location=anthropic.com

GOALS.md

@@ -350,7 +350,7 @@ Scope: src/modules/shellfilter-999999.0a1.0.tm (stack placement, insert_transfor
 Detail: goals/G-090-shellfilter-shellthread-audit.md
 
 ### G-101 [proposed] kit container strategy for zig-built Tcl 8.6 runtimes (no zipfs)
-Scope: investigation + decision record under src/buildsuites/suite_tcl86/ (or successor mechanism); TEMP_REFERENCE/metakit + TEMP_REFERENCE/KitCreator (read-only guidance); src/runtime/mapvfs.config ('kit' type consumers); src/make.tcl kit-wrap path (as consumer)
+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,KitCreator,kbs,sdx,tcl9} (read-only guidance - inventory in the detail file); src/runtime/mapvfs.config ('kit' type consumers); src/make.tcl kit-wrap path (as consumer); bin/sdx.kit (the tracked wrapping tool - provenance is part of this goal)
 Detail: goals/G-101-tcl86-kit-container-strategy.md
 
 ### G-105 [proposed] buildsuite cross-target builds (zig -target): linux first, WSL-verified

goals/G-101-tcl86-kit-container-strategy.md

@@ -1,7 +1,7 @@
 # G-101 kit container strategy for zig-built Tcl 8.6 runtimes (no zipfs)
 
 Status: proposed
-Scope: investigation + decision record under src/buildsuites/suite_tcl86/ (or successor mechanism); TEMP_REFERENCE/{metakit,KitCreator,kbs,sdx,tcl9} (read-only guidance - inventory in 'Reference material' below); src/runtime/mapvfs.config ('kit' type consumers); src/make.tcl kit-wrap path (as consumer); bin/sdx.kit (the tracked wrapping tool - provenance is part of this goal, see 'sdx: provenance' below)
+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,KitCreator,kbs,sdx,tcl9} (read-only guidance - inventory in the detail file); src/runtime/mapvfs.config ('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.