You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem — Found during the #856 sweep (2026-09-07): the staged server bundle's .opencode directory carries a package-lock pinning msgpackr-extract-darwin-arm64 — a macOS-arch npm artifact synced from the mac — on the Linux hub. If msgpackr's native-extract path resolves through it, plugin loading on the hub may silently degrade or fail on the affected module. Approach — Verify whether the hub's plugin runtime actually resolves that artifact (it may be inert lock noise — prove which, with evidence, before touching anything); if load-bearing: regenerate the lock on Linux (or make the staged bundle platform-agnostic), and add the platform-artifact check to the #856 guard test's sweep so a mac-synced lock can't land again. Found by: the #856 chore cast's honesty sweep (PR #865 description).
Important
Problem — Found during the #856 sweep (2026-09-07): the staged server bundle's
.opencodedirectory carries a package-lock pinning msgpackr-extract-darwin-arm64 — a macOS-arch npm artifact synced from the mac — on the Linux hub. If msgpackr's native-extract path resolves through it, plugin loading on the hub may silently degrade or fail on the affected module.Approach — Verify whether the hub's plugin runtime actually resolves that artifact (it may be inert lock noise — prove which, with evidence, before touching anything); if load-bearing: regenerate the lock on Linux (or make the staged bundle platform-agnostic), and add the platform-artifact check to the #856 guard test's sweep so a mac-synced lock can't land again.
Found by: the #856 chore cast's honesty sweep (PR #865 description).