5.3.3 is a packaging truthfulness patch. It does not add a new cognitive subsystem. It removes a contradiction between two product surfaces that should have agreed all along: the packaged installer and runtime doctor.
The mismatch
NEXO already shipped an hourly backup helper as part of the packaged runtime. The installer treated com.nexo.backup as a built-in auxiliary LaunchAgent. But runtime doctor did not inventory that same helper as core, which meant a clean npm install could still show a false “Unknown com.nexo LaunchAgents” warning.
What 5.3.3 changes
Runtime doctor now recognizes the built-in backup LaunchAgent as part of the core auxiliary inventory. That means the packaged installer, the runtime filesystem, and nexo doctor now describe the same system instead of pulling in different directions.
Why this matters
Small inventory mismatches create trust erosion. If a user installs from npm, keeps their own data in ~/.nexo, and runs doctor on a healthy runtime, the tool should not imply there is a ghost legacy process when the process was actually shipped by the product. Packaging cleanup is only credible when diagnostics tell the same story.
Relationship to 5.3.2
The boundary fix from 5.3.2 remains the bigger change: packaged core scripts and hooks are tracked as product artifacts, the personal bucket stops absorbing them by accident, and legacy heartbeat wrappers move into managed core hooks. Version 5.3.3 is the follow-through that makes doctor reflect that cleaned-up packaged surface honestly.
Upgrade
Open the 5.3.3 changelog section for the exact release note. If you are already installed, the intended path stays simple:
npm install -g nexo-brain@5.3.3nexo update
Your data stays in ~/.nexo. The runtime stays replaceable. Now the packaged installer and runtime doctor agree about the built-in backup surface too.