Validate native FreeBSD boot assets

docs/PROGRESS.md

@@ -3158,3 +3158,69 @@ Next recommended step:
 1. begin Phase 14 by replacing the remaining host-copy boot assets first
 2. keep shrinking the host-staged base boundary around the now-working native world/kernel path
 3. revisit cleaner runtime vs. development splits after the boot asset transition
+
+## 2026-04-03 — Phase 14.1: removed host-copied boot assets from the validated native boot path
+
+Completed work:
+
+- wrote the Phase 14.1 report:
+  - `docs/reports/phase14-native-boot-assets-freebsd.md`
+- added a dedicated Phase 14.1 native-boot PID1 template:
+  - `tests/system/phase14-native-boot-pid1-operating-system.scm.in`
+- added dedicated Phase 14.1 validation wrappers:
+  - `tests/system/run-phase14-native-boot-qemu.sh`
+  - `tests/system/run-phase14-native-boot-xcpng.sh`
+- validated a cleaner native boot path by sourcing boot assets from the existing native world output instead of the host-staged `freebsd-bootloader` package:
+  - `#:kernel freebsd-native-kernel`
+  - `#:bootloader freebsd-native-world`
+  - `#:base-packages (list freebsd-native-world)`
+- hardened the reusable local PID1 QEMU harness so it no longer boots the raw store image directly read/write from `/frx/store`:
+  - `tests/system/run-phase11-shepherd-pid1-qemu.sh` now copies the generated raw image to:
+    - `boot-disk.img`
+    in the workdir before launching QEMU
+  - this prevents repeated local boots from mutating the supposed store artifact and causing dirty-filesystem follow-up failures
+
+Validation:
+
+- local QEMU/UEFI/TCG native-boot wrapper passes:
+  - `tests/system/run-phase14-native-boot-qemu.sh`
+  - workdir: `/tmp/phase14-1-qemu2-1775188371`
+  - result: `PASS phase14-native-boot-qemu`
+  - confirmed:
+    - `native_base_store_count=2`
+    - `host_base_store_count=0`
+    - `shepherd_pid=1`
+    - `sshd_status=running`
+    - `native_boot_assets=freebsd-native-world`
+    - `native_base_boot=ok`
+- real XCP-ng native-boot wrapper passes:
+  - `tests/system/run-phase14-native-boot-xcpng.sh`
+  - workdir: `/tmp/phase14-1-xcpng-1775188701`
+  - result: `PASS phase14-native-boot-xcpng`
+  - confirmed:
+    - `vm_id=90490f2e-e8fc-4b7a-388e-5c26f0157289`
+    - `vdi_id=0f1f90d3-48ca-4fa2-91d8-fc6339b95743`
+    - `guest_ip=192.168.213.62`
+    - `native_base_store_count=2`
+    - `host_base_store_count=0`
+    - `shepherd_pid=1`
+    - `sshd_status=running`
+    - `compat_prefix_shims=absent`
+    - `guile_module_smoke=ok`
+    - `native_boot_assets=freebsd-native-world`
+    - `native_base_boot=ok`
+
+Current assessment:
+
+- Phase 14.1 is complete
+- the validated native boot path no longer depends on host-copied `/boot/...` material
+- the current Phase-14.1 native boundary is now fully host-base-free for the validated path:
+  - native kernel
+  - native world supplying boot assets
+  - native world supplying runtime
+
+Next recommended step:
+
+1. introduce a clearer native runtime slice so runtime is no longer modeled by reusing the broader native world output for both boot and runtime
+2. validate that explicit native runtime slice on QEMU and XCP-ng
+3. then revisit headers/toolchain/development package boundaries