feat: record installed parser SHA in lock.js

[taku25]

Part of #41. This is PR1 of 3 planned PRs for parser revision tracking.

Changes

• Added lock file utilities to util.lua:
• lock_set(lang, entry) — saves { url, sha } after installation
• lock_remove(lang) — removes the entry on parser removal
• lock_get(lang) — retrieves the entry (for future use in PR2/PR3)
• After a successful build, git rev-parse HEAD is called to capture the installed commit SHA, which is written to lock.json
• remove() now cleans up the corresponding lock entry
• lock.json is stored in the parent of parser_dir (e.g. ~/.local/share/nvim/site/lock.json) to keep the parser directory clean

lock.json example

{
"lua": {
"sha": "abc1234...",
"url": "https://github.com/..."
}
}

[moqodow]

Hello,
I do like the idea of a lock file for the installed parser in general. I just think the lock file should be in the neovim config directory. Then the user can add it to the tracked files. This would allow to have the same parser installed on each system that uses the same neovim config.
Other tools with lock files also use the user config dir by default e.g. lazy.nvim, vim.pack.
Thanks,
Wilfried

[taku25]

That makes a lot of sense. Storing the lock file in the config directory is much better for users who manage their dotfiles, as it ensures consistent parser versions across different environments. I’ll update the PR accordingly. Please wait a bit!

[ssfdust]

Any update on this?