Upgrade to v2.0.0

Upgrade to v2.0.0
Replace the resource with the complete v2.0.0 build while keeping the resource folder named 
nord_inventory.
Keep your existing database. Auto-SQL remains backwards-compatible and creates any missing Operations tables without deleting existing inventory data.
Review 
config/operations.lua before restart. Existing defaults remain backwards-compatible.
If you customized 
Config.UI.specialSlots, merge your slot definitions into the v2.0.0 
config/ui.lua. Category matching and explicit 
items allowlists remain supported.
Restart 
nord_inventory (or the server) and open Admin Studio → Operations and Admin Studio → Integrations.
Run one Anti-Dupe scan and verify the result before resolving historic alerts.
Create a manual snapshot of a test player, perform a small Inventory Manager edit and restore the snapshot to validate database permissions.
Place a disposable test item persistently, restart the resource and confirm the item returns at the same coordinates.
Confirm long weapons disappear from the back immediately when equipped/used and that ground drops stream in/out cleanly.
Confirm connected integration providers appear in the Integrations registry and that Recommended scripts / Refresh actions remain responsive.
No destructive database migration is required for v2.0.0.
Optional physical clothing
Config.Operations.ClothingBridge.Enabled remains 
false after upgrade. Enable it only when the configured appearance resource exposes the matching client export. This keeps v2.0.0 backwards-compatible with existing clothing/appearance setups.
Config merge checklist
Do not copy an old 
config/ folder over v2.0.0. Explicitly review at least 
config/operations.lua, 
config/ui.lua, 
config/admin.lua, 
config/player_interactions.lua and any owner-customized bridge/vehicle/item settings.
Post-upgrade verification
After the resource starts, check for missing tables, provider failures and locale errors before allowing players in. Then perform the v2.0.0 Operations smoke tests from the Production Checklist.