diff --git a/goals/G-127-crosstarget-vfs-bake.md b/goals/G-127-crosstarget-vfs-bake.md index edd2ab2c..e219b84a 100644 --- a/goals/G-127-crosstarget-vfs-bake.md +++ b/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// 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.