Published · npm latest
Field upgrade truth.
Patch over 4.5.5. Registry-aware package install, skill drift honesty, multi-project MCP process clarity—for one developer with many checkouts. Not a score. Gate unchanged. No required config migration.
Upgrade
Get 4.5.6
Preview shows skillDrift, hostSelection, and
whatsNew. After apply, read advisory
postUpgradeChecks. Customized skills stay preserved unless you pass
--refresh-skills.
What changed
In plain English.
Registry-aware upgrade
When CLI version equals node_modules but npm is ahead,
upgrade --apply no longer false-skips. Skip paths emit
reasonCode + a copy-paste suggestedInstallCmd.
Skill drift + opt-in refresh
Preview counts stale / customized / missing skills. Customized bodies stay
preserved by default. --refresh-skills rewrites managed skills
only with consent—never silent overwrite of true edits.
Multi-project MCP honesty
Every MCP tool context includes processPackage: process version
vs project install, mismatch/stale, next action. Restart MCP after package
bump. One checkout = one expectedRoot.
Post-upgrade checks
After apply, advisory pin↔CLI, verification, doctor/status/MCP notes.
Always notAScore—never flips the gate.
Host selection honesty
When your active host is not in managed --tools, upgrade notes
it and suggests the exact expansion.
Inventory UX quieting
Rules inventory downranks pure error/message string constants so business limits stay visible for adopt pilots. No new sensors.
Honesty notes
What did not change
- Write gate and CI fail-closed semantics for value layer edges
- Binary gate—no numeric architecture score, no LLM pass/fail
- No new skill names; no new ArkRules sensors
- No silent multi-project MCP retarget (identity handshake still required)
-
Soft hosts stay advisory at local write; required CI
--strict-mergeis the hard merge boundary
Maintainer source: docs/releases/4.5.6.md ↗