fix: remove retired Plugins frontend packaging and false Web inventory #378
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/remove-retired-web-frontend"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Plugins removed its old Web frontend in3199a70 and retained API-only dashboard-api. Core still pinned/builds an old frontend at a03e5d via its asset lock, while component inventory incorrectly treated API channel webui as frontend activation evidence. Remove the stale lock/downloader/browser build and obsolete activation docs; remove only generated old asset directories at build, refusing symlink-parent traversal; never touch installed operator plugins/config/home. Do not report retired provenance even if stale files remain. Report separate dashboard package as installed, not proven running.
Validation: npm run build; full 2073 passed / 1 skip / 0 failures; independent supplied-diff review APPROVE. New tests cover generated artifact cleanup, installed-plugin preservation, no old fetch/build/package, stale-provenance ignore and API-channel not frontend. Existing native updater still builds separate WebUI package; no target-host test gate. Overlays export handles missing optional lock by design.
This corrects stale Core packaging rather than updating/reintroducing a frontend already removed from Plugins. Current agent recovery/stop and independent dashboard services remain intact.