G-121: archive markers on archived-goal mentions (goals_lint informational sweep)

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

goals/G-121-bakelist-selective-bake.md

@@ -15,11 +15,13 @@ delivered the buildsuite list/info/build surface without this item - the kit
 wrap subsystem is a separate surface reading src/runtime/mapvfs.config.
 
 Today a bake is all-or-nothing: iterating on one kit (e.g punk91 during the
-G-120 work) rebuilds/deploys every configured kit, and discovering what WOULD
+work on G-120, achieved 2026-07-25) rebuilds/deploys every configured kit, and
-be baked means reading mapvfs.config's custom line format by eye. The
+discovering what WOULD be baked means reading mapvfs.config's custom line
-deploy-state question ("is bin/punk91.exe current with what a bake would
+format by eye. The deploy-state question ("is bin/punk91.exe current with what
-produce?") has no surface at all - the stale-r1-runtime incident of 2026-07-25
+a bake would produce?") has no surface at all - the stale-r1-runtime incident
-(see the G-112 flip evidence) was exactly an invisible kit-state divergence.
+of 2026-07-25 (see archived G-112's flip evidence,
+goals/archive/G-112-maketcl-subcommand-rename.md) was exactly an invisible
+kit-state divergence.
 
 ## Approach
 
@@ -41,8 +43,8 @@ produce?") has no surface at all - the stale-r1-runtime incident of 2026-07-25
 - Discoverability nicety (decided in the work): the bake/bakelist argdocs may
   enumerate configured kit names as punk::args choices when the mapping parses
   at definition time, degrading to plain string args otherwise.
-- Piped output is ESC-free automatically (G-113 policy); keep bakelist's
+- Piped output is ESC-free automatically (the G-113 colour policy, achieved
-  columns stable enough to grep.
+  2026-07-25); keep bakelist's columns stable enough to grep.
 
 ## Alternatives considered