[languages] Port Prolog, Nim, Nix, Python, JS/TS, C/C++, web, PHP, data, and LSP #9

Open
opened 2026-09-16 04:13:22 +00:00 by nsaspy · 0 comments
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: #7

Analyze

  • Cover Doom language modules and flags for C/C++, Emacs Lisp editing, JSON/tree-sitter, JavaScript/TypeScript/tree-sitter, Nim/LSP, Nix, PHP, Python, shell, web, Markdown, and data formats.
  • Cover ob-nim, ob-prolog, lsp-pyright, syntax checking, lookup, editorconfig, make, formatting, and required servers/tools from Home Manager.

Gate

  • Record one server/formatter/linter owner and launch contract per language.
  • LSP processes must be scoped, restartable, and unable to block the editor loop.

Execute

  • Configure Lem modes, tree-sitter grammars, LSP clients, formatters, diagnostics, and project roots.
  • Add missing Lem extensions in Common Lisp only where native support is insufficient.

Evaluate

  • Use fixture projects for every language and exercise open, diagnostics, completion, definition, references, formatting, restart, and missing-server failure.
  • Test multiple simultaneous language servers.

Recurse

  • Unsupported upstream behavior becomes an evidence-backed extension issue, never a silent omission.

Acceptance

  • Every active language module has a tested disposition.
  • Required external tools are declaratively installed.
  • LSP failure is visible and recoverable.

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 server requires secrets committed to Git.
  • Formatting changes files without explicit invocation/approved save hook.
  • Process lifecycle leaks or hangs.
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: #7 ## Analyze - Cover Doom language modules and flags for C/C++, Emacs Lisp editing, JSON/tree-sitter, JavaScript/TypeScript/tree-sitter, Nim/LSP, Nix, PHP, Python, shell, web, Markdown, and data formats. - Cover ob-nim, ob-prolog, lsp-pyright, syntax checking, lookup, editorconfig, make, formatting, and required servers/tools from Home Manager. ## Gate - Record one server/formatter/linter owner and launch contract per language. - LSP processes must be scoped, restartable, and unable to block the editor loop. ## Execute - Configure Lem modes, tree-sitter grammars, LSP clients, formatters, diagnostics, and project roots. - Add missing Lem extensions in Common Lisp only where native support is insufficient. ## Evaluate - Use fixture projects for every language and exercise open, diagnostics, completion, definition, references, formatting, restart, and missing-server failure. - Test multiple simultaneous language servers. ## Recurse - Unsupported upstream behavior becomes an evidence-backed extension issue, never a silent omission. ## Acceptance - [ ] Every active language module has a tested disposition. - [ ] Required external tools are declaratively installed. - [ ] LSP failure is visible and recoverable. ## 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 server requires secrets committed to Git. - Formatting changes files without explicit invocation/approved save hook. - Process lifecycle leaks or hangs.
Sign in to join this conversation.
No description provided.