update/refact

.gitignore

@@ -1 +1,7 @@
 /target
+
+# Local development overrides (see .cargo/config.toml inside)
+/.cargo
+
+# Scaffolded plugins (dev-time tooling)
+/plugins-dev

CHANGELOG.md

@@ -1,5 +1,73 @@
 # Changelog
 
+## [0.3.0] - 2026-09-04
+
+### Ecosystem externalization (monocrate cycle complete)
+- The kernel is now a thin host over the externalized ecosystem. It
+  consumes the contract crates from `xtop-cli/api` (`xtop-plugin-api`,
+  `xtop-widget-api`, `xtop-extension-api`), the widget packs from
+  `xtop-cli/widgets`, layouts from `xtop-cli/layouts`, the samurai plugin
+  from `xtop-cli/plugins` and the MCP extension from `xtop-cli/extensions`
+  as floating git dependencies with optional feature flags.
+- Deleted the dead uncompiled `src/commands/plugins_dir_tmp/` leftover
+  from the pre-monocrate layout. (Path spelled in scripts/audit.sh as the
+  absence guard.)
+- `crate version 0.2.0 -> 0.3.0`; `rust-version = "1.87"` declared.
+
+### Local-only CI
+- The GitHub Actions CI workflow (`.github/workflows/ci.yml`) has been
+  removed: gating is local only (`scripts/ci.sh`, `scripts/audit.sh`) and
+  will not be re-enabled until the release pipeline is 100% ready.
+
+### Contract consolidation
+- `config::AlertThresholds` removed: the persisted config now uses
+  `xtop_plugin_api::AlertThresholds` directly (identical JSON keys
+  `cpu_high`/`mem_high`/`disk_high`; defaults 90/90/90 constructed at the
+  config layer). Hand-marshalling bridge code deleted from
+  `plugins/host.rs` and `state/widget_state.rs`.
+- Plugin widget registrations use `xtop_plugin_api::PluginWidget`; the
+  duplicated `PluginWidgetFn` alias in `ui/layout/engine.rs` is gone.
+- Docker leftovers removed (`dockers: vec![]` assignment, `docker_info`
+  composite forwarding) — the api model no longer carries Docker data.
+- Plugin context reads are capability-gated and `Result`-typed upstream;
+  consumers adapted.
+
+### Themes
+- `miami` is now embedded and seeded like the other 11 themes (12 JSONC
+  theme files ship, all in `DEFAULT_THEMES`); seed version bumped to "2"
+  so existing installs receive the new template.
+- Theme docs/counts corrected everywhere (12 themes; `x` compiled in as
+  the startup fallback).
+- `theme::themes_dir()` routes through the platform-aware
+  `config::config_dir()`, so themes live next to `config.json` and layouts
+  on macOS/Windows too.
+
+### Dependency refresh
+- ratatui `0.29 -> 0.30.2` (`Layout::vertical`/`Layout::horizontal`
+  builder API); crossterm aligned with ratatui's backend (single
+  `crossterm 0.29` in the graph via `ratatui-crossterm`).
+
+### New features
+- Unknown widget names in the active layout produce a one-time stderr
+  warning per name (`xtop: layout '<layout>' references unknown widget
+  '<name>'`).
+- Optional `effects` feature (off by default) wires the built-in
+  `xtop-effect-fade` through the `effect` config key ("fade" activates the
+  500 ms fade-in; absent/unknown disables). Builds without the feature
+  carry zero extra dependencies.
+
+### Docs and release plumbing
+- `docs/` refreshed: configuration keys, plugin architecture (plugins as
+  separate crates, `plugin list|install|scaffold` real behavior, MCP
+  extension), multi-repo RFC status, feature/theme counts; `colors.md`
+  moved under `docs/`.
+- `install.sh` VERSION synced to the crate version; OpenSSL build-dep
+  claims removed (the crate has no openssl dependency); `install.ps1`
+  placeholder comment removed.
+- Kernel `ROADMAP.md` synced with the implemented state (phases 4-6 and
+  the R2/R3 refactor items); `scripts/audit.sh` extended with dead-dir and
+  theme-seed gates.
+
 ## [0.2.1] - 2026-06-18
 
 ### Config: Persistencia de Layouts Personalizados

CONTRIBUTING.md

@@ -5,7 +5,7 @@ First off, thank you for considering contributing to `xtop`! It's people like yo
 ## How Can I Contribute?
 
 ### Reporting Bugs
-- Ensure the bug was not already reported by searching on GitHub under [Issues](https://github.com/xscriptor/xtop/issues).
+- Ensure the bug was not already reported by searching on GitHub under [Issues](https://github.com/xtop-cli/xtop/issues).
 - If you're unable to find an open issue addressing the problem, open a new one. Be sure to include a title and clear description, as much relevant information as possible, and a code sample or an executable test case demonstrating the expected behavior that is not occurring.
 
 ### Suggesting Enhancements
@@ -23,7 +23,7 @@ First off, thank you for considering contributing to `xtop`! It's people like yo
 
 ```bash
 # Clone the repository
-git clone https://github.com/xscriptor/xtop.git
+git clone https://github.com/xtop-cli/xtop.git
 cd xtop
 
 # Build the project