Luigit
repositories / pi-ext

pi-ext

bugabingas pi extensions

owned by admin

extensions/lsp/registry/POLICY.md

Raw
Rendered preview

Reviewed LSP defaults

servers.json contains packaged runtime defaults only: schema version 1, ordered profiles gopls, typescript-language-server, clangd. Runtime never fetches sources or executes this importer.

Sources and licensing

Primary source: Helix languages.toml, revision ba40e547426b0f9896c8bdc699a4ab11f2b37dbc. fixtures/helix-languages.toml preserves exact pinned source bytes for deterministic offline tests. HELIX-LICENSE preserves upstream MPL-2.0 license text. Derived profile data remains attributed to Helix under MPL-2.0; importer implementation is repository MIT code. The pinned source URL provides corresponding original source; this directory records local modifications. No lsp-bridge supplement is selected: Helix already contains all three launch definitions and language associations.

Import policy

policy.json pins revision plus SHA-256 of source and license. Only explicitly selected languages/extensions are supported, not every catalog entry. Launch executable/arguments, language identifier, selected literal extensions, roots, initialization configuration are imported as data. Helix language-server.*.config means initialization options, not runtime settings. Runtime settings start empty unless explicitly supplied through reviewed local overrides. Editor preferences, formatter/debugger commands, actions, grammars and feature restrictions are never executed or interpreted. Selected server environment blocks are rejected, not silently carried over. Commands must be bare executable names; absolute paths, interpolation, unresolved placeholders, unsafe object keys and unbounded input fail validation. Configuration values never contain credentials.

Local overrides carry explicit reasons per field. Go preserves experimentally verified watcher initialization and settings separately, removing editor hints. TypeScript retains upstream --stdio, .ts, package.json/tsconfig.json roots; editor host information and hints are omitted. C++ retains upstream clangd launch, .cpp/.cc/.cxx/.hpp; Helix supplies no roots, so local .clangd, compile_commands.json, CMakeLists.txt markers select project scope. No server installation, executable discovery repair or protocol migration occurs.

Explicit refresh and conflict review

Run explicit Mise task //extensions/lsp:registry-refresh to fetch pinned source and license, validate hashes/notices, derive profiles and report field diffs. Refresh is not attached to startup, build, or tests. previousSource records prior imported values before local overrides, enabling three-way comparison with fresh import and current reviewed snapshot. Local snapshot changes survive unchanged upstream fields. Different simultaneous local/upstream changes fail with previous/local/fresh values and field names; equal simultaneous changes are accepted. Overrides remain intentional local decisions even when equal to an earlier imported value. Unknown override fields or missing reasons fail. To repin, deliberately edit revision/hashes and fixture/license after reviewing upstream changes; retain prior previousSource until conflict resolution. Resolve conflicts by explicitly reconciling snapshot and overrides, then rebase affected previousSource fields to reviewed new upstream values. After successful review, rebase all previousSource values against the new fixture to establish the next maintenance baseline. These policy changes are manual maintenance decisions, never automatic conflict winners. Review printed diffs plus repository diff before committing. No volatile timestamps or network-derived ordering enter generated output.

Publication uses one same-directory staging file and atomic rename after complete validation; staging is cleaned on handled failures and cancellation. A staging file must share the destination filesystem for atomic replacement; it is never a runtime input. Fetch, integrity, parsing, conflicts, publication failures or pre-publication interruption leave exact last-good bytes intact. A process killed without cleanup can leave an ignored .servers-*.tmp staging file, never a partial servers.json. Cancellation after atomic replacement cannot roll back an already completed publication. Concurrent snapshot changes observed before publication fail rather than overwrite maintenance work; run one maintainer at a time.

# Reviewed LSP defaults

`servers.json` contains packaged runtime defaults only: schema version 1, ordered profiles `gopls`, `typescript-language-server`, `clangd`.
Runtime never fetches sources or executes this importer.

## Sources and licensing

Primary source: [Helix languages.toml](https://github.com/helix-editor/helix/blob/ba40e547426b0f9896c8bdc699a4ab11f2b37dbc/languages.toml), revision `ba40e547426b0f9896c8bdc699a4ab11f2b37dbc`.
`fixtures/helix-languages.toml` preserves exact pinned source bytes for deterministic offline tests.
`HELIX-LICENSE` preserves upstream MPL-2.0 license text.
Derived profile data remains attributed to Helix under MPL-2.0; importer implementation is repository MIT code.
The pinned source URL provides corresponding original source; this directory records local modifications.
No lsp-bridge supplement is selected: Helix already contains all three launch definitions and language associations.

## Import policy

`policy.json` pins revision plus SHA-256 of source and license.
Only explicitly selected languages/extensions are supported, not every catalog entry.
Launch executable/arguments, language identifier, selected literal extensions, roots, initialization configuration are imported as data.
Helix `language-server.*.config` means initialization options, not runtime settings.
Runtime settings start empty unless explicitly supplied through reviewed local overrides.
Editor preferences, formatter/debugger commands, actions, grammars and feature restrictions are never executed or interpreted.
Selected server environment blocks are rejected, not silently carried over.
Commands must be bare executable names; absolute paths, interpolation, unresolved placeholders, unsafe object keys and unbounded input fail validation.
Configuration values never contain credentials.

Local overrides carry explicit reasons per field.
Go preserves experimentally verified watcher initialization and settings separately, removing editor hints.
TypeScript retains upstream `--stdio`, `.ts`, `package.json`/`tsconfig.json` roots; editor host information and hints are omitted.
C++ retains upstream clangd launch, `.cpp`/`.cc`/`.cxx`/`.hpp`; Helix supplies no roots, so local `.clangd`, `compile_commands.json`, `CMakeLists.txt` markers select project scope.
No server installation, executable discovery repair or protocol migration occurs.

## Explicit refresh and conflict review

Run explicit Mise task `//extensions/lsp:registry-refresh` to fetch pinned source and license, validate hashes/notices, derive profiles and report field diffs.
Refresh is not attached to startup, build, or tests.
`previousSource` records prior imported values before local overrides, enabling three-way comparison with fresh import and current reviewed snapshot.
Local snapshot changes survive unchanged upstream fields.
Different simultaneous local/upstream changes fail with previous/local/fresh values and field names; equal simultaneous changes are accepted.
Overrides remain intentional local decisions even when equal to an earlier imported value.
Unknown override fields or missing reasons fail.
To repin, deliberately edit revision/hashes and fixture/license after reviewing upstream changes; retain prior `previousSource` until conflict resolution.
Resolve conflicts by explicitly reconciling snapshot and overrides, then rebase affected `previousSource` fields to reviewed new upstream values.
After successful review, rebase all `previousSource` values against the new fixture to establish the next maintenance baseline.
These policy changes are manual maintenance decisions, never automatic conflict winners.
Review printed diffs plus repository diff before committing.
No volatile timestamps or network-derived ordering enter generated output.

Publication uses one same-directory staging file and atomic rename after complete validation; staging is cleaned on handled failures and cancellation.
A staging file must share the destination filesystem for atomic replacement; it is never a runtime input.
Fetch, integrity, parsing, conflicts, publication failures or pre-publication interruption leave exact last-good bytes intact.
A process killed without cleanup can leave an ignored `.servers-*.tmp` staging file, never a partial `servers.json`.
Cancellation after atomic replacement cannot roll back an already completed publication.
Concurrent snapshot changes observed before publication fail rather than overwrite maintenance work; run one maintainer at a time.