Manifest-driven editor tooling for m-stdlib. Reads the canonical dist/stdlib-manifest.json produced by m-stdlib's generator and surfaces it as hover docs, goto-definition, and completion in any open .m file.

This is not a full M (MUMPS) language server. The scope is exactly the m-stdlib public surface — STD* modules and their public labels. For non-stdlib symbols the extension stays out of the way.

Hovering on a ^STD* or label^STDxxx reference shows the same content m doc <symbol> prints in a terminal: signature, params, returns, raises, since/stable, see-also, examples, and the source location.

Cmd/Ctrl-click on parse^STDJSON jumps to src/STDJSON.m:39 (or wherever the manifest's source.line field points). Works on bare module references too.

Typing ^STD triggers a module completion list. Typing <partial>^STDJSON triggers a label completion list scoped to that module. The ^ is registered as a completion-trigger character so suggestions appear without ctrl-space.

The extension auto-discovers dist/stdlib-manifest.json in this order:

1. The m-stdlib.manifestPath user/workspace setting (absolute path; tilde-expanded).
2. The $M_CLI_MANIFEST environment variable.
3. Walking up from each workspace folder looking for dist/stdlib-manifest.json — catches the natural case of having m-stdlib checked out as one of the workspace roots.
4. The manifest bundled with the extension at <extension>/assets/stdlib-manifest.json — this is the final fallback and ships with the .vsix, so the extension works on a stock install with no other repo on disk. It's a snapshot pinned to the extension version; for live tracking against an in-progress m-stdlib checkout, set m-stdlib.manifestPath or $M_CLI_MANIFEST.

The bundled manifest is refreshed by the maintainer at release time by copying m-stdlib/dist/stdlib-manifest.json into assets/ and bumping the extension version.

The manifest is generated by make manifest in m-stdlib. The extension watches the resolved file for changes and picks up regenerations without an editor reload (only relevant when manifestPath / env var / walk-up resolves — the bundled manifest doesn't change at runtime).

cd m-stdlib-vscode
npm install
npm run compile     # tsc -> out/

To run the extension in a development host:

code .
# F5 in VS Code → opens an Extension Development Host

v0.1 — hover + goto-def + completion. Snippets and a richer diagnostic surface are tracked as follow-on work in m-stdlib's docs/tracking/discoverability-tracker.md (WC2).

MIT