Move system operations under system namespace

Author: marcofortina

docs/TECHNICAL_DESIGN.md

@@ -112,9 +112,8 @@ commands:      local.command, remote.command
 filesystem:    fs.*
 archive:       archive.*
 packages:      pkg.*
-systemd:       systemctl.*
+system:       system.service.*, system.systemd.*, system.kernel.*, system.process.*, system.cron.*, system.journal.*, system.log.*
 identity:      identity.user.*, identity.group.*
-processes:     process.*
 transfer:      transfer.*
 http/api:      http.*
 connectivity:   network.connectivity.*

docs/concepts/plugin-system.md

@@ -11,7 +11,7 @@ Only canonical names are public DSL names. For example:
 
 ```text
 fs.file.template
-systemctl.restart
+system.service.restart
 db.sqlite.query
 ```
 

docs/guides/creating-plugins.md

@@ -8,7 +8,7 @@ SPDX-License-Identifier: AGPL-3.0-or-later
 Automax plugins are small execution units loaded by the plugin registry.
 
 A plugin should keep business logic outside the engine and expose one canonical
-DSL name, for example `fs.dir.create` or `systemctl.restart`.
+DSL name, for example `fs.dir.create` or `system.service.restart`.
 
 ## Contract
 
@@ -43,7 +43,7 @@ Good examples:
 ```text
 fs.file.template
 pkg.install
-systemctl.enable
+system.service.enable
 transfer.upload
 ```
 

docs/guides/cron.md

@@ -9,7 +9,7 @@ Automax manages `/etc/cron.d` entries with explicit files, which keeps changes a
 
 ```yaml
 - id: install_healthcheck_cron
-  use: cron.entry
+  use: system.cron.entry.add
   with:
     name: myapp-health
     schedule: "*/5 * * * *"
@@ -18,4 +18,4 @@ Automax manages `/etc/cron.d` entries with explicit files, which keeps changes a
     sudo: true
 ```
 
-Use `cron.file` when a full cron.d file must be installed verbatim.
+Use `system.cron.file` when a full cron.d file must be installed verbatim.

docs/guides/kernel-tuning.md

@@ -5,11 +5,11 @@ SPDX-License-Identifier: AGPL-3.0-or-later
 
 # Kernel tuning
 
-Automax manages Linux runtime kernel parameters through `sysctl.*` and kernel modules through `kernel.module.*`.
+Automax manages Linux runtime kernel parameters through `system.kernel.sysctl.*` and kernel modules through `system.kernel.module.*`.
 
 ```yaml
 - id: enable_forwarding
-  use: sysctl.set
+  use: system.kernel.sysctl.set
   with:
     name: net.ipv4.ip_forward
     value: "1"
@@ -21,11 +21,11 @@ Automax manages Linux runtime kernel parameters through `sysctl.*` and kernel mo
 
 ```yaml
 - id: load_bridge_filter
-  use: kernel.module.load
+  use: system.kernel.module.load
   with:
     name: br_netfilter
     persist: true
     sudo: true
 ```
 
-Use `sysctl.get` for checks, `sysctl.reload` to reload persisted files, and `kernel.module.unload` / `kernel.module.persist` for module lifecycle management.
+Use `system.kernel.sysctl.get` for checks, `system.kernel.sysctl.reload` to reload persisted files, and `system.kernel.module.unload` / `system.kernel.module.persist` for module lifecycle management.

docs/guides/ssh-smoke.md

@@ -49,7 +49,7 @@ remote user. It covers:
 - `fs.object.find`, `fs.permission.mode`
 - `archive.tar`, `archive.untar`, `archive.zip`, `archive.unzip`
 - `transfer.upload`, `transfer.download`, `transfer.sync`
-- `process.wait`
+- `system.process.wait`
 - `storage.usage.disk_check`, `network.connectivity.port_check`
 - artifact capture for stdout/stderr/data
 - resume helpers through the normal run state store

docs/plugins/facts-cron.md

@@ -14,12 +14,12 @@ target.
 
 ## Cron
 
-Use `cron.entry` for one managed cron.d entry and `cron.file` for a complete
+Use `system.cron.entry.add` for one managed cron.d entry and `system.cron.file` for a complete
 cron.d file. Prefer systemd timers when the service model is systemd-native, and
 use cron only when the target platform or operational requirement needs it.
 
 ## Cron readback and validation
 
-Use `cron.list` to inspect existing cron state, `cron.absent` for explicit
-removal of `/etc/cron.d` entries, and `cron.validate` to check cron file syntax
+Use `system.cron.entry.list` to inspect existing cron state, `system.cron.entry.remove` for explicit
+removal of `/etc/cron.d` entries, and `system.cron.validate` to check cron file syntax
 before installing or replacing a schedule file.