fix: regenerate standalone core lockfile for @earendil-works deps

[mandarnilange]

Summary

Regenerates the standalone packages/core/package-lock.json to match the @earendil-works/pi-* dependencies introduced in 0.3.1.

Why

The Docker core image stage runs npm ci against this standalone lockfile (not the root one). During the 0.3.1 migration the root lockfile was regenerated, but this one was missed — it still encoded the old @mariozechner/pi-* tree. That mismatch (strnum/xml-naming/anynum) made npm ci fail and broke the core Docker image in the v0.3.1 release (npm publish + platform image succeeded).

Fix

• Regenerated packages/core/package-lock.json against @earendil-works/pi-* 0.79.9.
• Verified with an isolated npm ci --omit=dev --ignore-scripts (exactly the Docker core stage): 347 packages, exit 0.

No source or version change — lockfile only. Unblocks the core image for the next release.

[coderabbitai]

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (1)

• packages/core/package-lock.json is excluded by !**/package-lock.json

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 18f04fa0-f9c2-42d0-871d-2980019ded14

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}