add plugin list change

Author: devyn

blog/2024-11-12-nushell_0_100_0.md

@@ -28,6 +28,7 @@ As part of this release, we also publish a set of optional plugins you can insta
 - [_Changes_](#changes-toc)
   - [_Additions_](#additions-toc)
   - [_Breaking changes_](#breaking-changes-toc)
+    - [_`plugin list`_](#plugin-list-toc)
   - [_Deprecations_](#deprecations-toc)
   - [_Removals_](#removals-toc)
   - [_Bug fixes and other changes_](#bug-fixes-and-other-changes-toc)
@@ -146,6 +147,35 @@ Thanks to [@sgvictorino](https://github.com/sgvictorino) in [#14095](https://git
 { |a $a }  # now errors
 ```
 
+### `plugin list` [[toc](#table-of-content)]
+
+The `plugin list` command has been changed in [#14085](https://github.com/nushell/nushell/pull/14085) to consider both the plugins currently present in the engine state as well as the plugins stored in the registry file. Changes made by `plugin add` and `plugin rm` should now be more obvious.
+
+As part of this change, the `is_running` column has been replaced by a `status` column, which now displays many possible states a plugin can be in:
+
+- `added`: The plugin is present in the plugin registry file, but not in the engine.
+- `loaded`: The plugin is present both in the plugin registry file and in the engine, but is not running.
+- `running`: The plugin is currently running, and the `pid` column should contain its process ID.
+- `modified`: The plugin state present in the plugin registry file is different from the state in the engine.
+- `removed`: The plugin is still loaded in the engine, but is not present in the plugin registry file.
+- `invalid`: The data in the plugin registry file couldn't be deserialized, and the plugin most likely needs to be added again.
+
+`running` always has high priority as a state, so other statuses won't be visible if a plugin is currently running. This means that
+
+```nushell
+# 0.99.0
+plugin list | where is_running
+```
+
+can now always be replaced by:
+
+```nushell
+# 0.100.0
+plugin list | where status == running
+```
+
+In case you want to avoid loading the plugin registry file (e.g. for performance reasons), you can now use the `--engine` flag to do so. Similarly, the `--registry` flag will only display the contents of the registry, without comparing them against the state of the engine (but all plugins will appear as `added`). The `--plugin-config` flag is now supported to allow use of a separate plugin registry file, identically to the other `plugin` commands.
+
 ## Deprecations [[toc](#table-of-content)]
 
 ## Removals [[toc](#table-of-content)]