Skip to content

fix: refresh built-in specialist registry safely on upgrade - #35

Merged
KayzenRoot merged 2 commits into
mainfrom
fix/builtin-specialist-registry-refresh
Sep 23, 2026
Merged

KayzenRoot merged 2 commits into
mainfrom
fix/builtin-specialist-registry-refresh

Conversation

@KayzenRoot

Copy link
Copy Markdown
Owner

Follow-up compatibility fix for the Forge systems-runtime coverage.

Problem:
an existing UADS installation may retain a valid persisted pre-update specialist registry, so updating the package alone can still leave the new systems-runtime profile and expanded built-in coverage unavailable.

Fix:

  • reconcile persisted built-in profiles against the current canonical built-in catalog on load;
  • preserve all non-builtin user-config/adapter profiles;
  • fail closed on any non-builtin collision with a reserved built-in ID;
  • atomically persist the reconciled registry/state only when the canonical built-ins changed;
  • add a regression test simulating an old 25-profile registry plus a custom user profile.

No ~/.uads wipe is required and user-defined profiles are preserved.

@KayzenRoot
KayzenRoot merged commit ad2e6c8 into main Sep 23, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant