G-171 note: staleness-message emitter seam for Approach 10

Records that the stale_bootsupport gate cited as the layout-store report's
shape template now emits via the shared punkboot::lib::bootsupport_stale_warning
helper (b729ce07): Approach 10's implementer should generalize that helper
rather than hand-roll a second block, keeping the semantic split deliberate -
bootsupport staleness aborts/prompts (stale copies execute make.tcl itself),
the layout-store report is report-and-proceed. goals_lint clean.

Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com

goals/G-171-bake-writes-land-untracked.md

@@ -169,3 +169,15 @@ mint to pack the tracked modpod tree as it stands.
   and judged not related in substance: G-089, G-114, G-131 (boot/_config surface),
   G-019 (payload content trimming), G-020 (Scope names a lib_tcl9 path only),
   G-116 (tcltls payload constituent - its removal stays G-004-era work).
+- Approach 10 message-shape template updated 2026-08-08 (git b729ce07 / fossil
+  55a54d8b, project 0.65.1): the stale_bootsupport gate it cites now emits via a
+  shared helper, punkboot::lib::bootsupport_stale_warning - mechanism-first
+  wording that names the launch directory, contrasts src/-vs-elsewhere module
+  precedence, special-cases the repair commands, and prints the resolved src
+  path as a copy-pasteable fix line. The layout-store staleness report should
+  generalize that helper (parameterize the subject tree, stale list and steer-to
+  command) rather than hand-roll a second block. Semantics stay distinct by
+  design: bootsupport staleness is a version-aware abort/prompt (the stale
+  copies are the code executing make.tcl itself), while the layout-store report
+  is report-and-proceed (the mint packs the tracked modpod tree as it stands -
+  the lag is the deliberate, reported state).