Move remaining runtime plugins to canonical namespaces

Author: marcofortina

README.md

@@ -192,17 +192,17 @@ automax plugins audit
 Current categories:
 
 ```text
-commands:      local.command, remote.command
+commands:      command.local.run, command.remote.run
 filesystem:    fs.*
-archive:       archive.*
+data/archive:  data.archive.*, data.compression.*
 packages:      os.package.*
 systemd:       systemctl.*
 users/groups:  user.*, group.*
 processes:     process.*
-transfer:      data.transfer.*
-http/api:      http.*
+data:          data.download.*, data.transfer.*, data.backup.*, data.restore.*
+http/api:      network.http.*
 wait/assert:   wait.*, assert.*
-database:      db.sqlite.query, db.postgres.query, db.mysql.query, db.oracle.query
+database:      database.sqlite.query, database.postgres.query, database.mysql.query, database.oracle.query
 ```
 
 See `docs/plugins/` for detailed examples of every builtin macro.

docs/TECHNICAL_DESIGN.md

@@ -25,7 +25,7 @@ A step opens one fresh SSH connection per target and reuses it for all its
 substeps. The runtime context is kept by Automax, not by a long-lived remote
 shell. Plugins that need step-local state can use the `ExecutionContext.step_state`
 mapping. For example, `fs.cd` sets the current remote working directory and
-`remote.command` applies it to subsequent commands in the same step.
+`command.remote.run` applies it to subsequent commands in the same step.
 
 Targets can be scoped at job, task, step or substep level. When substeps in the
 same step resolve to different target sets, Automax keeps one execution group per
@@ -108,17 +108,17 @@ continue
 Current builtins are grouped into these categories:
 
 ```text
-commands:      local.command, remote.command
+commands:      command.local.run, command.remote.run
 filesystem:    fs.*
-archive:       archive.*
+data/archive:  data.archive.*, data.compression.*
 packages:      os.package.*
 system:       system.service.*, system.systemd.*, system.kernel.*, system.process.*, system.cron.*, system.journal.*, system.log.*
 identity:      identity.user.*, identity.group.*
-transfer:      data.transfer.*
-http/api:      http.*
+data:          data.download.*, data.transfer.*, data.backup.*, data.restore.*
+http/api:      network.http.*
 connectivity:   network.connectivity.*
 storage:        storage.*
-database:      db.*.query
+database:      database.<engine>.*
 ```
 
 Builtin plugin names are canonical only: no short or ambiguous compatibility aliases

docs/concepts/execution-model.md

@@ -49,7 +49,7 @@ Substeps can register outputs for later use:
 
 ```yaml
 - id: read_version
-  use: remote.command
+  use: command.remote.run
   with:
     command: cat /opt/app/VERSION
   register:

docs/concepts/plugin-system.md

@@ -12,7 +12,7 @@ Only canonical names are public DSL names. For example:
 ```text
 fs.file.template
 system.service.restart
-db.sqlite.query
+database.sqlite.query
 ```
 
 Aliases are intentionally not exposed by `automax plugins list`.

docs/guides/facts.md

@@ -9,7 +9,7 @@ Automax gathers remote Linux facts for conditional workflows, reports and run di
 
 ```yaml
 - id: gather_core_facts
-  use: facts.gather
+  use: os.facts
   with:
     subset:
       - os
@@ -22,8 +22,8 @@ Automax gathers remote Linux facts for conditional workflows, reports and run di
 Individual plugins are also available:
 
 - `os.facts`
-- `facts.network`
+- `network.link.facts`
 - `os.package.facts`
-- `facts.services`
+- `system.service.facts`
 
 Package facts support Debian/Ubuntu through `dpkg-query` and Red Hat-like systems through `rpm`.

docs/guides/first-local-job.md

@@ -29,7 +29,7 @@ tasks:
       - id: local
         substeps:
           - id: hello
-            use: local.command
+            use: command.local.run
             with:
               command: "printf hello"
 ```

docs/guides/first-ssh-job.md

@@ -64,7 +64,7 @@ tasks:
       - id: shell
         substeps:
           - id: hostname
-            use: remote.command
+            use: command.remote.run
             with:
               command: hostname
             register:

docs/guides/ssh-smoke.md

@@ -42,7 +42,7 @@ AUTOMAX_SSH_COMMAND_TIMEOUT=60
 The default smoke is non-destructive and should be safe for an unprivileged
 remote user. It covers:
 
-- `remote.command`
+- `command.remote.run`
 - `fs.dir.create`, `fs.dir.remove`, `fs.dir.exists`, `fs.dir.wait`
 - `fs.file.exists`, `fs.file.wait`, `fs.cd`, `fs.file.write`, `fs.file.read`, `fs.object.stat`
 - `fs.file.line`, `fs.file.replace`, `fs.object.copy`, `fs.object.move`, `fs.symlink.create`, `fs.symlink.remove`

docs/guides/templating.md

@@ -44,7 +44,7 @@ Registered outputs can be reused later in the same run:
 
 ```yaml
 - id: get_user
-  use: remote.command
+  use: command.remote.run
   with:
     command: whoami
   register:

docs/guides/writing-jobs.md

@@ -67,7 +67,7 @@ use: fs.dir.create
 over:
 
 ```yaml
-use: remote.command
+use: command.remote.run
 with:
   command: mkdir -p /opt/myapp
 ```
@@ -79,7 +79,7 @@ document and test.
 
 ```yaml
 - id: app_version
-  use: remote.command
+  use: command.remote.run
   with:
     command: cat /opt/app/VERSION
   register: