Summary

• track the initialized instance route key on the instance detail page
• skip the destructive reset/reload path when reactive updates fire for the same route

Why

The instance page effect that clears local state and re-runs refresh(true, true) was firing even when the route had not actually changed. That caused unnecessary churn on the detail page and regressed the local chat experience by repeatedly clearing instance/config/provider/module state while staying on the same instance.

Validation

• npm --prefix ui ci --no-audit --no-fund
• npm --prefix ui run build
• zig build -Dbuild-ui=false
• local smoke: chat on the instance page remained working after the rebuild instead of regressing under same-route refreshes