G-127 notes: record that its payload/target mismatch clause is already delivered by G-133

Non-contract Notes addition (user-directed). G-133 (achieved 2026-07-27) landed the
structural arch scan this goal's Acceptance still asks for: a recapped BUILD-WARNING
naming file, found architecture and kit target; no warning for multi-arch
platform-subdir packages or recognised vendor spellings; and the scan running for
cross-target kits. That covers the clause in full.

The clause is deliberately left in place rather than trimmed - trimming an Acceptance is
a contract edit - so the note says how to read it: a regression pin on behaviour that
already exists, not work to do. It also states the goal's genuine remainder so whoever
activates it is not misled about the size: the bin/kits/<platform>/ output split, the
per-target payload declaration, and keeping G-133's smoke probe pointed at wherever the
relocated artifact lands.

Goal, Acceptance and Scope are unchanged.

Assisted-by: harness=claude; primary-model=claude-opus-5[1m]; api-location=anthropic.com

goals/G-127-crosstarget-vfs-bake.md

@@ -133,6 +133,17 @@ exists locally (empty but for sha1sums.txt) and punkbin upstream carries
   second, adopts that target-addressing; its output-location move must also keep the
   smoke probe pointed at wherever the freshly built artifact lands - see
   goals/archive/G-133-bake-payload-consistency-checks.md.
+- Acceptance redundancy (recorded 2026-07-28, user-directed): the payload/target mismatch
+  clause in this goal's Acceptance - a payload binary built for another platform reported
+  naming the file and both platforms, with platform-discriminated subdirs explicitly not
+  flagged - is ALREADY DELIVERED by G-133 (achieved 2026-07-27). Its acceptance requires a
+  recapped BUILD-WARNING naming file, found architecture and kit target; no warning for
+  multi-arch platform-subdir packages or recognised vendor spellings; and the scan running
+  for cross-target kits. The clause is deliberately left in place rather than trimmed (that
+  would be a contract edit): read it as a regression pin on behaviour that already exists,
+  not as work to do. The genuine remainder of this goal is the other two gaps in Context -
+  the bin/kits/<platform>/ output split and per-target payload declaration - and, per the
+  note above, keeping G-133's smoke probe pointed at wherever the artifact now lands.
 - Related: G-131 - sibling surface in the same kit loop (its kit_type_mismatch rework and
   container autodetection read the same mapvfs/runtime_caps machinery whose outputs this
   goal relocates); their previously recorded bridge was G-133, now archived.