Ensure CLI is available for external connections and exposes controls for watchdog, agent, and dataframe manipulation

[guillaume-byte]

Problem: The CLI must remain available for external connections and expose control for watchdogs, agents, and dataframes. We need to verify availability and access patterns.

Goals:

• Ensure the CLI is always available for external connections (e.g., remote admin) while respecting security constraints.
• Ensure users can manipulate watchdogs, agents, and dataframes via CLI commands.
• Validate network binding, authentication/authorization, and robustness (daemon/agent availability under load).

Acceptance criteria:

• CLI binds to an interface/configuration that allows external connections when enabled (document default: localhost-only; opt-in to 0.0.0.0 with clear security warnings).
• Provide and document commands to manipulate watchdog (watchdog list/status/kill/restart), agent controls, and dataframe operations (export/import/list).
• Include authentication/authorization options (token, TLS, or local-only mode) to prevent unauthorized access.
• Add automated tests that assert CLI responsiveness under typical load and during watchdog manipulations.

Implementation notes / suggestions:

• Prefer adding an authenticated control socket (unix domain socket for local, TLS-protected TCP for remote) rather than opening an unrestricted TCP port.
• Ensure CLI operations are idempotent and safe to run concurrently.
• Document examples for remote usage and how to secure the endpoint.

References: user request — "CLI, check that a) CLI is always available for external connexion, and user able to manipulate watchdog with it, agent, dataframe ?"