Repair lock file

[amackillop]

Was seeing this upon running npm ci or npm install:

Installing dependencies
npm warn reify invalid or damaged lockfile detected
npm warn reify please re-try this operation once it completes
npm warn reify so that the damage can be corrected, or perform
npm warn reify a fresh install with no lockfile if the problem persists.
npm warn reify invalid or damaged lockfile detected
npm warn reify please re-try this operation once it completes
npm warn reify so that the damage can be corrected, or perform
npm warn reify a fresh install with no lockfile if the problem persists.
npm warn reify invalid or damaged lockfile detected
npm warn reify please re-try this operation once it completes
npm warn reify so that the damage can be corrected, or perform
npm warn reify a fresh install with no lockfile if the problem persists.

Not sure what went wrong by looking at the diff. Just a lot of platform specific packages being deleted mostly.

[chatgpt-codex-connector]

💡 Codex Review

mdk-checkout/package-lock.json

Lines 576 to 580 in cc5bf7f

	"optionalDependencies": {
	"@moneydevkit/lightning-js-android-arm-eabi": "0.1.54",
	"@moneydevkit/lightning-js-android-arm64": "0.1.54",
	"@moneydevkit/lightning-js-darwin-arm64": "0.1.54",
	"@moneydevkit/lightning-js-darwin-x64": "0.1.54",

Restore non-Linux optional deps in lockfile

This optionalDependencies list still declares non-Linux binaries (e.g., @moneydevkit/lightning-js-darwin-*/win32-*), but this commit removes their node_modules/@moneydevkit/lightning-js-… entries elsewhere in the lockfile. That leaves dangling references with no resolved/integrity metadata, so the lockfile no longer fully specifies installs on macOS/Windows (or other non-Linux targets) and will need regeneration there. If the intent wasn’t to make the lockfile Linux-only, the removed platform entries should be restored.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".