fix: Improve plugin ui entry points, Fix chat scroll, fix notifications, fix user rights

docs-site/docs/plugin-development/api/context-and-logging.md

@@ -37,21 +37,23 @@ Example context shape:
 
 ## Action Context
 
-Composer, toolbar, and profile actions receive context directly.
+Composer, toolbar, and profile actions receive context directly. Toolbar actions are launched from the server side panel's View plugins menu and report `source: 'toolbarAction'`.
 
 ```js
 export function activate(context) {
-  context.subscriptions.push(context.api.ui.registerToolbarAction('where-am-i', {
-    label: 'Where am I?',
-    run: (actionContext) => {
-      context.api.logger.info('Toolbar action context', {
-        source: actionContext.source,
-        serverId: actionContext.server?.id,
-        textChannelId: actionContext.textChannel?.id,
-        voiceChannelId: actionContext.voiceChannel?.id
-      });
-    }
-  }));
+  context.subscriptions.push(
+    context.api.ui.registerToolbarAction('where-am-i', {
+      label: 'Where am I?',
+      run: (actionContext) => {
+        context.api.logger.info('Toolbar action context', {
+          source: actionContext.source,
+          serverId: actionContext.server?.id,
+          textChannelId: actionContext.textChannel?.id,
+          voiceChannelId: actionContext.voiceChannel?.id
+        });
+      }
+    })
+  );
 }
 ```
 
@@ -70,4 +72,4 @@ export function activate(context) {
 }
 ```
 
-Logs are visible in the Plugin Manager. Avoid logging passwords, bearer tokens, or private message contents.
+Logs are visible in the Plugin Manager. Avoid logging passwords, bearer tokens, or private message contents.