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

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: #12

Analyze

Inventory all Emacs Lisp, Common Lisp/StarIntel, Nim, Nix, Org/OSINT, Prolog, Python, and web snippets plus Skeletor templates.
Record trigger, mode, fields, transforms, side effects, and collision behavior.

Gate

Generated security/recon commands require visible placeholders and must not auto-execute.
Duplicate or obsolete snippets need an explicit disposition rather than silent deletion.

Execute

Implement Lem snippet/template support and migrate data into a declarative format with a Common Lisp loader.
Preserve intent while removing compiled/generated Yasnippet artifacts.

Evaluate

Expand every snippet in a fixture buffer, exercise fields/transforms, and check syntax where a parser/compiler exists.
Test trigger collisions and wrong-mode isolation.

Recurse

Unrepresentable transforms become focused design iterations.

Acceptance

Every source snippet has a migrated, rejected, or superseded fact in the KB.
All migrated snippets expand deterministically.
No snippet executes commands on expansion.

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

A snippet contains a secret.
Expansion has hidden side effects.
Trigger ownership is ambiguous.

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: #12 ## Analyze - Inventory all Emacs Lisp, Common Lisp/StarIntel, Nim, Nix, Org/OSINT, Prolog, Python, and web snippets plus Skeletor templates. - Record trigger, mode, fields, transforms, side effects, and collision behavior. ## Gate - Generated security/recon commands require visible placeholders and must not auto-execute. - Duplicate or obsolete snippets need an explicit disposition rather than silent deletion. ## Execute - Implement Lem snippet/template support and migrate data into a declarative format with a Common Lisp loader. - Preserve intent while removing compiled/generated Yasnippet artifacts. ## Evaluate - Expand every snippet in a fixture buffer, exercise fields/transforms, and check syntax where a parser/compiler exists. - Test trigger collisions and wrong-mode isolation. ## Recurse - Unrepresentable transforms become focused design iterations. ## Acceptance - [ ] Every source snippet has a migrated, rejected, or superseded fact in the KB. - [ ] All migrated snippets expand deterministically. - [ ] No snippet executes commands on expansion. ## 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 - A snippet contains a secret. - Expansion has hidden side effects. - Trigger ownership is ambiguous.

nsaspy referenced this issue

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

[core] Port editing model, completion, navigation, UI, and workspaces #12

nsaspy referenced this issue

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

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