# Progress

This file is now intentionally compact.

Detailed chronological history through Phase 18.2 has been archived at:

- `docs/reports/progress-log-through-phase18-2-freebsd.md`

For a broader narrative summary, see:

- `docs/PROG_SUMMARY.md`

## Current status

Fruix currently has:

- declarative system modeling on FreeBSD
- content-addressed system closures under `/frx/store`
- native FreeBSD base artifacts in `/frx/store`
- declarative FreeBSD source objects and source materialization
- source-driven native base builds from materialized source snapshots
- side-by-side source revisions and boot validation
- a host-driven non-interactive install path:
  - `fruix system install`
- a bootable Fruix-managed installer environment:
  - `fruix system installer`
- a bootable Fruix-managed installer ISO:
  - `fruix system installer-iso`
- an explicit installed-system generation layout under:
  - `/var/lib/fruix/system`
- explicit installed-system retention roots under:
  - `/frx/var/fruix/gcroots`
- a validated installed-system generation switch/rollback workflow via:
  - `fruix system status`
  - `fruix system switch`
  - `fruix system rollback`
- a validated separate in-system development environment overlay via:
  - `/run/current-system/development-profile`
  - `/run/current-development`
  - `/usr/local/bin/fruix-development-environment`
- a validated host-initiated native base-build path inside a Fruix-managed guest via:
  - real XCP-ng boot of a development-enabled Fruix system
  - in-guest `buildworld` / `buildkernel`
  - staged `installworld` / `distribution` / `installkernel`

Validated boot modes still are:

- `freebsd-init+rc.d-shepherd`
- `shepherd-pid1`

The validated Phase 18 installation work currently uses:

- `freebsd-init+rc.d-shepherd`

## Latest completed achievement

### 2026-04-05 — Phase 20.2 completed

Fruix now has a validated intermediate path where the host still orchestrates the workflow, but real FreeBSD native base-build work runs inside a booted Fruix-managed FreeBSD guest.

Highlights:

- development-enabled systems now expose canonical native-build compatibility links at:
  - `/usr/include -> /run/current-system/development-profile/usr/include`
  - `/usr/share/mk -> /run/current-system/development-profile/usr/share/mk`
- media builder versions were bumped so booted images and future installed targets pick up that rootfs layout change
- the validated guest build path now runs real FreeBSD native build steps inside the Fruix-managed guest:
  - `buildworld`
  - `buildkernel`
  - `installworld`
  - `distribution`
  - `installkernel`
- staged install steps use:
  - `DB_FROM_SRC=yes`
  - so the staged install is driven by the declared source tree's account database rather than by the guest's minimal local `/etc` state
- the validated result now includes staged native artifact outputs for:
  - kernel
  - bootloader slice
  - headers / `usr/share/mk`

Validation:

- `PASS phase20-host-initiated-native-build-xcpng`

Reports:

- `docs/system-deployment-workflow.md`
- `docs/GUIX_DIFFERENCES.md`
- `docs/reports/phase20-development-environment-freebsd.md`
- `docs/reports/phase20-host-initiated-native-builds-freebsd.md`

## Recent major milestones

- `1d00907` — `Add Fruix bootable installer environment`
- `2517710` — `Add non-interactive Fruix installation flow`
- `02a02e3` — `Document Fruix FreeBSD source policy`
- `865012e` — `Boot Fruix from distinct FreeBSD source revisions`
- `8150508` — `Validate side-by-side FreeBSD source revisions`
- `5cbf5b9` — `Build native bases from materialized FreeBSD sources`

## Active constraints

- local `bhyve` remains blocked under Xen due to lack of nested VT-x exposure
- XO self-service creation is still not usable with the current token
- real XCP-ng validation must continue to use:
  - VM `90490f2e-e8fc-4b7a-388e-5c26f0157289`
  - approved A/B VDIs:
    - `0f1f90d3-48ca-4fa2-91d8-fc6339b95743`
    - `7061d761-3639-4bec-87f7-2ba1af924eaa`
- local QEMU/TCG validation keeps conservative default SMP settings; `QEMU_SMP` remains overrideable

## Next step

Per `docs/PLAN_4.md`, the next planned step is:

- **Phase 20.3** — reassess and potentially prototype guest self-hosted base builds

Phase 20.2 is now complete: Fruix validates host-initiated native FreeBSD base builds running inside the approved real XCP-ng Fruix guest path.