Prototype FreeBSD package definitions

docs/PROGRESS.md

@@ -1152,3 +1152,117 @@ Next recommended step:
 2. carry forward the concrete real-checkout runtime blocker for later integration work:
   - investigate the `leave-on-EPIPE` failure in `./pre-inst-env guix --version`
 3. continue using `/frx/store` rather than `/gnu/store` for future FreeBSD store experiments when the prototype work needs a persistent store root
+
+## 2026-04-01 — Phase 3.2 completed: FreeBSD system package-definition prototype and profile validation added
+
+Completed work:
+
+- added a Guix-style FreeBSD system package-definition prototype module:
+  - `modules/fruix/packages/freebsd.scm`
+- added a Scheme harness to materialize those package definitions into store-like outputs and a merged profile:
+  - `tests/packages/freebsd-package-profile-prototype.scm`
+- added a shell wrapper for that harness:
+  - `tests/packages/run-freebsd-package-profile-prototype.sh`
+- installed the missing host shell dependency needed to satisfy the requested package set:
+  - `bash`
+- wrote the Phase 3.2 report:
+  - `docs/reports/phase3-freebsd-package-definitions.md`
+- ran the profile prototype successfully and captured metadata under:
+  - `/tmp/freebsd-package-profile-prototype-metadata.txt`
+
+Important findings:
+
+- the prototype now defines a minimal FreeBSD core package set covering the categories requested by Phase 3.2:
+  - kernel
+  - kernel headers
+  - libc
+  - userland utilities
+  - development tools (`clang`, `make`, autotools)
+  - minimum system libraries (`openssl`, `zlib`)
+  - shells (`sh`, `bash`)
+- the current package-definition layer uses an explicit Guix-like record shape with fields for:
+  - name
+  - version
+  - build system
+  - inputs
+  - synopsis/description/home-page/license
+  - install plan
+- explicit dependency relationships are now encoded and resolved recursively during materialization, including examples such as:
+  - `freebsd-libc` -> `freebsd-kernel-headers`
+  - `freebsd-userland` -> `freebsd-libc`, `freebsd-sh`
+  - `freebsd-clang-toolchain` -> `freebsd-libc`, `freebsd-kernel-headers`, `freebsd-sh`
+  - `freebsd-autotools` -> `freebsd-gmake`, `freebsd-bash`, `freebsd-libc`
+- the harness successfully materialized:
+  - `11` core package outputs
+  into a store-like directory tree under the work directory
+- it then merged those outputs into a development profile and validated that the profile contains working:
+  - `bash`
+  - `make`
+  - `autoconf`
+  - `cc`
+  - kernel image path
+  - kernel-header path
+  - core shared-library paths
+- the generated profile compiled and ran a C test program successfully, with observed output:
+  - `hello-from-freebsd-profile`
+- for executables installed under `bin/`, the prototype uses wrappers that `exec` the host tool by absolute path; this preserved correct behavior for prefix-sensitive tools such as `autoconf`
+
+Current assessment:
+
+- Phase 3.2 is now satisfied on the current prototype track
+- Phase 3 as a whole is now completed on the current FreeBSD amd64 path because both:
+  - adapted GNU build-system execution, and
+  - minimal FreeBSD system package-definition/profile validation
+  have been demonstrated successfully
+- the next remaining project milestone is now Phase 4, centered on Shepherd rather than package-building foundations
+
+## 2026-04-01 — Phase 3 completed on the current FreeBSD prototype track
+
+Phase 3 is now considered complete for the active FreeBSD amd64 prototype path.
+
+Why this milestone is satisfied:
+
+- **Phase 3.1** success criteria were met on the prototype track:
+  - a reusable FreeBSD adaptation layer for GNU builder phases was added
+  - five representative GNU packages built successfully through that adapted runner
+  - the resulting binaries executed correctly on the host
+- **Phase 3.2** success criteria were met on the prototype track:
+  - a minimal FreeBSD system package-definition layer was added
+  - explicit dependency relationships were modeled and resolved
+  - the package outputs installed into a merged profile successfully
+  - the generated profile was validated by compiling and running a test program with the staged toolchain
+
+Important scope note:
+
+- this completes the **build-system adaptation milestone** in prototype form, not the full Guix package-lowering/daemon integration path
+- the earlier concrete upstream/runtime blocker still exists for later integration work:
+  - `./pre-inst-env guix --version` fails with `Wrong type to apply: #<syntax-transformer leave-on-EPIPE>`
+- however, that blocker no longer prevents Phase 4 work because the core build-system and package-definition assumptions have now been validated independently
+
+Recent commits:
+
+- `e380e88` — `Add FreeBSD Guile verification harness`
+- `cd721b1` — `Update progress after Guile verification`
+- `27916cb` — `Diagnose Guile subprocess crash on FreeBSD`
+- `02f7a7f` — `Validate local Guile fix on FreeBSD`
+- `4aebea4` — `Add native GNU Hello FreeBSD build harness`
+- `c944cdb` — `Validate Guix builder phases on FreeBSD`
+- `0a2e48e` — `Validate GNU which builder phases on FreeBSD`
+- `245a47d` — `Document gaps to real Guix FreeBSD builds`
+- `d62e9b0` — `Investigate Guix derivation generation on FreeBSD`
+- `c0a85ed` — `Build local Guile-GnuTLS on FreeBSD`
+- `15b9037` — `Build local Guile-Git on FreeBSD`
+- `47d31e8` — `Build local Guile-JSON on FreeBSD`
+- `d82195b` — `Advance Guix checkout on FreeBSD`
+- `9bf3d30` — `Document FreeBSD syscall mapping`
+- `7621798` — `Prototype FreeBSD jail build isolation`
+- `d65b2af` — `Prototype FreeBSD build user isolation`
+- `e404e2e` — `Prototype FreeBSD store management`
+- `eb0d77c` — `Adapt GNU build phases for FreeBSD`
+
+Next recommended step:
+
+1. begin Phase 4.1 by validating whether Shepherd itself now builds and runs as a regular service on FreeBSD with the fixed local Guile path
+2. carry forward the separate real-checkout runtime blocker for later integration work:
+  - investigate the `leave-on-EPIPE` failure in `./pre-inst-env guix --version`
+3. continue using `/frx/store` rather than `/gnu/store` for future FreeBSD integration experiments when a persistent store root is required