[gate] Prove parity, cut over the default editor, and retain rollback #1

New issue

Open

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

nsaspy commented

2026-09-16 04:13:22 +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: #15

Analyze

Read the complete KB, all issue evidence, source probes, target probes, package/module/custom/snippet dispositions, and current dotfiles editor launch behavior.
Identify every remaining unknown, manual-only probe, stale SHA, and unsupported workflow.

Gate

The Prolog verifier, full local test suite, Nix builds, Home Manager evaluations, and exact-current-head CI must be green.
Cutover requires explicit user approval after the parity report; this issue cannot infer it.

Execute

Produce the final parity report and rollback plan.
After explicit approval only, update dotfiles so the chosen Lem frontend becomes the default editor while retaining an accessible Doom profile during the agreed rollback window.

Evaluate

Run cold/warm launch, crash recovery, file-open, project, Org, Lisp, language, Git, terminal, AI-offline, custom workflow, desktop association, and rollback drills on the live host.
Record the exact deployed generation and commit SHAs.

Recurse

Any failed capability reopens its owning issue and blocks cutover. Architecture contradictions restart ADADR.

Acceptance

No active capability is unknown or silently dropped.
The user explicitly approved cutover.
Default launch works and rollback is proven.
Doom retirement, if desired, is a separate explicit decision.

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

Any stale or wrong-head evidence.
Any unknown active capability.
No tested rollback.
No explicit cutover approval.

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: #15 ## Analyze - Read the complete KB, all issue evidence, source probes, target probes, package/module/custom/snippet dispositions, and current dotfiles editor launch behavior. - Identify every remaining unknown, manual-only probe, stale SHA, and unsupported workflow. ## Gate - The Prolog verifier, full local test suite, Nix builds, Home Manager evaluations, and exact-current-head CI must be green. - Cutover requires explicit user approval after the parity report; this issue cannot infer it. ## Execute - Produce the final parity report and rollback plan. - After explicit approval only, update dotfiles so the chosen Lem frontend becomes the default editor while retaining an accessible Doom profile during the agreed rollback window. ## Evaluate - Run cold/warm launch, crash recovery, file-open, project, Org, Lisp, language, Git, terminal, AI-offline, custom workflow, desktop association, and rollback drills on the live host. - Record the exact deployed generation and commit SHAs. ## Recurse - Any failed capability reopens its owning issue and blocks cutover. Architecture contradictions restart ADADR. ## Acceptance - [ ] No active capability is unknown or silently dropped. - [ ] The user explicitly approved cutover. - [ ] Default launch works and rollback is proven. - [ ] Doom retirement, if desired, is a separate explicit decision. ## 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 - Any stale or wrong-head evidence. - Any unknown active capability. - No tested rollback. - No explicit cutover approval.

nsaspy referenced this issue

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

[operations] Port Hackmode, libvirt, packet/container tools, auth-source, and system integrations #2

nsaspy referenced this issue

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

[web] Port RSS, browser editing, webpaste, PDF, media, and desktop-open workflows #3

nsaspy referenced this issue

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

[snippets] Port every Yasnippet family and Skeletor/project template #4

nsaspy referenced this issue

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

[custom] Port StarIntel research dashboards, approvals, TODO sync, capture, and activity tools #5