root/fusion
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat(FN-3704): separate plugin lifecycle from setup probe state

Browse Source 
Fixes a bug where plugin lifecycle operations were incorrectly gated by the setup probe state, separating the two concerns across the API, PluginManager component, routes, and tests, with updated documentation.

Fusion-Task-Id: FN-3704
This commit is contained in:
Fusion
2026-05-07 10:48:28 -07:00
committed by gsxdsm
parent 0efba0890f
commit a01aa31ab8
10 changed files with 121 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/plugin-management.md
View File

@@ -24,6 +24,14 @@ These are related but different systems; do not treat Pi Extensions as Fusion Pl
| `stopped` | Disabled/stopped |
| `error` | Failed to load or failed at runtime |
### Setup status vs lifecycle state (Settings behavior)
Setup-capable plugins (for example **Agent Browser**) expose an additional **setup** check that is separate from lifecycle state.
- A plugin may be `installed`/`stopped` without being broken.
- When a plugin is not `started`, Settings shows setup check as deferred ("Start plugin to check setup") instead of treating it as an error.
- Error styling is reserved for true plugin lifecycle failures (`state = error`) or true setup-check failures returned while the plugin is running.
### Common locations
| Location | Purpose |