[bootstrap] Install and activate pinned Lem through Nix/Home Manager #14

New issue

Open

opened 2026-09-16 04:13:23 +00:00 by nsaspy · 0 comments

nsaspy commented

2026-09-16 04:13:23 +00:00

Owner

Parent: #1

RAGE contract

Consume only this issue on rage/<issue>-<slug>. Initialize the run log with the canonical RAGE helper and preserve the immutable full start SHA. Load the canonical rage and adadr skills from lost-rob0t/skills before architecture or implementation. Blocked by the control-plane decision in #2.

Queue blockers: #2

Analyze

Inspect the repository flake/Home Manager module and the consuming lost-rob0t/dotfiles Home Manager graph.
Use upstream Lem's flake outputs at the pinned commit; do not revive old Roswell or ad-hoc package recipes.

Gate

The pinned Lem package must evaluate for the user's NixOS architecture.
The existing Doom profile and default emacs wrapper must remain intact; this slice adds Lem and does not perform cutover.

Execute

Consume this repository's homeModules.default from dotfiles and enable programs.star-lem for the intended host profiles.
Generate and commit the real flake.lock from a Nix host.
Expose a stable lem command and deploy ~/.config/lem/init.lisp through Home Manager.

Evaluate

Run nix flake check, evaluate every affected Home Manager profile, build the Lem closure, and launch a no-init and configured smoke session.
Record exact package revision, closure/build result, host profile, and launch evidence.

Recurse

If the upstream package fails, record the contradiction and return through ADADR; do not add an imperative installer as a bypass.

Acceptance

Lem is present after Home Manager activation and lem resolves to the pinned build.
A configured Lem launch succeeds.
Doom/Emacs still launches exactly as before.
Rollback to the previous Home Manager generation is proven.

Durable evidence

Update the relevant facts in .prolog/kb/lem_migration.pl and .prolog/kb/issues.pl in the same change.
Record focused red/green evidence, the full local gate, packaging checks, and exact-head CI status.
Keep failed iterations and architecture contradictions visible.

Stop conditions

No Nix host is available for lock/build evidence.
Build requires unreviewed source changes.
Activation would replace Doom or the default editor.

Parent: #1 ## RAGE contract Consume only this issue on `rage/<issue>-<slug>`. Initialize the run log with the canonical RAGE helper and preserve the immutable full start SHA. Load the canonical `rage` and `adadr` skills from `lost-rob0t/skills` before architecture or implementation. Blocked by the control-plane decision in #2. Queue blockers: #2 ## Analyze - Inspect the repository flake/Home Manager module and the consuming `lost-rob0t/dotfiles` Home Manager graph. - Use upstream Lem's flake outputs at the pinned commit; do not revive old Roswell or ad-hoc package recipes. ## Gate - The pinned Lem package must evaluate for the user's NixOS architecture. - The existing Doom profile and default `emacs` wrapper must remain intact; this slice adds Lem and does not perform cutover. ## Execute - Consume this repository's `homeModules.default` from dotfiles and enable `programs.star-lem` for the intended host profiles. - Generate and commit the real `flake.lock` from a Nix host. - Expose a stable `lem` command and deploy `~/.config/lem/init.lisp` through Home Manager. ## Evaluate - Run `nix flake check`, evaluate every affected Home Manager profile, build the Lem closure, and launch a no-init and configured smoke session. - Record exact package revision, closure/build result, host profile, and launch evidence. ## Recurse - If the upstream package fails, record the contradiction and return through ADADR; do not add an imperative installer as a bypass. ## Acceptance - [ ] Lem is present after Home Manager activation and `lem` resolves to the pinned build. - [ ] A configured Lem launch succeeds. - [ ] Doom/Emacs still launches exactly as before. - [ ] Rollback to the previous Home Manager generation is proven. ## Durable evidence - Update the relevant facts in `.prolog/kb/lem_migration.pl` and `.prolog/kb/issues.pl` in the same change. - Record focused red/green evidence, the full local gate, packaging checks, and exact-head CI status. - Keep failed iterations and architecture contradictions visible. ## Stop conditions - No Nix host is available for lock/build evidence. - Build requires unreviewed source changes. - Activation would replace Doom or the default editor.

nsaspy referenced this issue

2026-09-16 04:13:23 +00:00

[epic] Port the complete active Emacs environment to Lem #16