You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
star keeps its data outside devlore/: extensions belong at ~/.local/share/devlore/star/extensions #918
star keeps its data outside devlore/, alone among the products. Its config and cache are already devlore-scoped: ~/.config/devlore/config.d/star.yaml, ~/.cache/devlore/star. Its data is not.
star is part of devlore, so its data belongs at ~/.local/share/devlore/star/extensions, built through devlore.DataPath("star", "extensions") like writ's.
What moves with it
The loader's probe list (loader.go:237-240): the XDG path, and the system path /usr/local/share/star/extensions
beside it.
self install: its target <prefix>/share/star/extensions (cmd/star/star/root.go:322) and findExtensionsDir's <exeDir>/../share/star/extensions (:350).
The base layer in noblefactor-ops, which deploys com.noblefactor.ops.GitHub to the old path through writ.
Until both move, star gh issues report stops resolving -- that is the report agent rule 3 requires.
Existing installs. Anyone with extensions at the old path keeps them there until they reinstall; the loader can
probe the old location for a release or two, or the move can be clean with a note.
Order
After #917, which makes star's manifest honest. With that in place, an uninstall at the old path removes only star's
own files and leaves another installer's extensions alone, so the move cannot take writ's deployment with it.
Activity
fix(star): its data lives under devlore/, like writ's (#918)
docs(plans): #918 Phases 1 and 2 recorded
fix(star): its data lives under devlore/, like writ's (#921)
fix(cli): self install replaces the record, retiring what it no longe…
fix(cli): self install replaces the record, retiring what it no longe…