Verify clean SWI pack installation path #140

Merged
lost-rob0t merged 9 commits from validation/clean-pack-install into main 2026-08-21 03:49:40 +00:00
lost-rob0t commented 2026-08-21 02:08:03 +00:00 (Migrated from github.com)

Part of #3 manual full-system validation.

Gap

The existing CI starts from a clean Ubuntu checkout and validates the source tree thoroughly, but it does not exercise the supported SWI pack packaging surface from pack.pl. A source checkout can therefore be green while a copied pack install/load path is broken.

Slice

  • install the current checkout through SWI's pack manager into an isolated pack root with linking disabled;
  • assert the installed prolog_rlm pack is a copied directory rather than a development symlink;
  • start a fresh SWI process from outside the checkout;
  • attach only the isolated pack root, load library(rlm), and require rlm_ready/0 plus rlm_version/1;
  • run this as its own required-to-be-green review signal without weakening the existing CI or REAL provider gates.

This is validation infrastructure for the v0.1 completion gate, not a claim that the repository is production-ready by itself.

Part of #3 manual full-system validation. ## Gap The existing CI starts from a clean Ubuntu checkout and validates the source tree thoroughly, but it does not exercise the supported SWI pack packaging surface from `pack.pl`. A source checkout can therefore be green while a copied pack install/load path is broken. ## Slice - install the current checkout through SWI's pack manager into an isolated pack root with linking disabled; - assert the installed `prolog_rlm` pack is a copied directory rather than a development symlink; - start a fresh SWI process from outside the checkout; - attach only the isolated pack root, load `library(rlm)`, and require `rlm_ready/0` plus `rlm_version/1`; - run this as its own required-to-be-green review signal without weakening the existing CI or REAL provider gates. This is validation infrastructure for the v0.1 completion gate, not a claim that the repository is production-ready by itself.
Sign in to join this conversation.
No description provided.