feat(FN-3077): enforce plugin AI security scan gate across install flows

- Add core plugin AI security scan module and schema support for scan toggle/state metadata
- Enforce scan checks during CLI and dashboard plugin install flows, with preserved API error status on scan failures
- Expose plugin scan toggle and rescan actions in dashboard/plugin manager with route and UI coverage
- Update plugin authoring and CLI/dashboard docs, plus add changeset for published CLI package

Fusion-Task-Id: FN-3077

docs/PLUGIN_AUTHORING.md

@@ -53,6 +53,33 @@ pnpm install
 pnpm test
 ```
 
+### Optional AI Security Scan (Opt-in)
+
+Plugin installs now support an opt-in `aiScanOnLoad` flag. When enabled, Fusion runs an AI security review before loading plugin code.
+
+- **Opt-in:** disabled by default (`aiScanOnLoad: false`)
+- **When it runs:** on plugin load/reload and explicit rescan
+- **Scan inputs (deterministic order):** `manifest.json`, optional `package.json`, optional `README.md`, entry module, then prioritized source files
+- **Boundaries:** excludes `node_modules`, `dist`, lockfiles, binary assets, files over 20 KB each, and enforces a 120 KB total raw-content cap
+
+### Scan Verdicts
+
+- `clean` — no concerning patterns found
+- `warning` — suspicious patterns found; plugin may still load
+- `blocked` — dangerous patterns found; plugin is blocked before import
+- `error` — scan failed to produce a valid decision
+- `unavailable` — AI scan service unavailable
+
+When a plugin is blocked (`blocked`/`error`/`unavailable`), Fusion does **not** execute plugin code for that load attempt and stores the scan result on plugin metadata (`lastSecurityScan`) for operator visibility.
+
+### Author Guidance for Blocked Plugins
+
+If your plugin is blocked:
+- remove dynamic execution patterns (`eval`, shell-outs, hidden network exfiltration behavior)
+- keep behavior explicit in source and manifest
+- document external calls and sensitive operations in README
+- ask operators to run `fn plugin rescan <id>` after publishing fixes
+
 ### Plugin Project Structure
 
 ```

docs/cli-reference.md

@@ -812,14 +812,17 @@ Plugin lifecycle management.
 
 ```bash
 fn plugin list
-fn plugin install <path>
+fn plugin install <path> [--ai-scan]
+fn plugin rescan <id>
 fn plugin uninstall <id> --force
 fn plugin enable <id>
 fn plugin disable <id>
 fn plugin create <name>
 ```
 
-Subcommands: `list|ls`, `install`, `uninstall`, `enable`, `disable`, `create`.
+Subcommands: `list|ls`, `install`, `rescan`, `uninstall`, `enable`, `disable`, `create`.
+
+`fn plugin install --ai-scan` enables AI security scanning on plugin load. `fn plugin rescan <id>` runs a fresh scan/reload cycle and prints plugin name, verdict, summary, and finding count. It exits non-zero for `blocked`, `error`, or `unavailable` verdicts.
 
 ---