server

El dominio server tiene 3 acciones. En la superficie meta se alcanzan todas a través de arcane_server; en la individual, cada una es una herramienta propia; en la dinámica se ejecutan con arcane_execute_action y el ID canónico.

Resumen

Acción	Título	Tipo
server.app_version	Get app version	lectura
server.health	Health check	lectura
server.version	Get version information	lectura

Acciones

server.app_version

Get app version

Get the current application version

• Tipo: lectura
• Parámetros obligatorios: ninguno
• Meta-herramienta: arcane_server con "action": "app_version"
• Herramienta individual: arcane_server_app_version
• Ruta de Arcane: GET /api/app-version
• ID de operación: getAppVersion
• Uso: Full version and build details of the manager, no credentials or parameters: currentVersion, displayVersion, revision, goVersion, buildTime, enabledFeatures, and the running image’s currentTag/currentDigest when Arcane runs in a container. Its update fields (updateAvailable, newestVersion, newestDigest, releaseUrl, releaseNotes, releasedAt) also cover digest-tracking builds (next channel or a non-release tag such as latest), where updateAvailable comes from the image digest and newestVersion may be absent. For a manager started from a digest-pinned image (name@sha256:…) they come from a live registry lookup of the image’s tag (latest when the reference names none), never from Arcane’s stored image-update record. server.version does not do this, and all update fields stay empty when update checks are disabled. For an agent or remote environment’s version use environment.version (environmentId from environment.list), which returns the same fields.
• Acciones relacionadas: server.version, environment.version, system.upgrade_check

server.health

Health check

Check if the API is healthy

• Tipo: lectura
• Parámetros obligatorios: ninguno
• Meta-herramienta: arcane_server con "action": "health"
• Herramienta individual: arcane_server_health
• Ruta de Arcane: GET /api/health
• ID de operación: health-check
• Uso: Liveness check of the Arcane manager itself. It needs no credentials and takes no parameters. Returns status UP, or DOWN with HTTP 503 once the server’s internal runtime has stopped, so it tells an unreachable or failing server from a credentials problem. It says nothing about remote environments: check those with environment.test or environment.version.
• Acciones relacionadas: server.version, server.app_version, environment.test

server.version

Get version information

Get application version information and check for updates

• Tipo: lectura
• Parámetros obligatorios: ninguno
• Meta-herramienta: arcane_server con "action": "version"
• Herramienta individual: arcane_server_version
• Ruta de Arcane: GET /api/version
• ID de operación: getVersion
• Uso: Lightweight check of the manager’s version against the latest GitHub release. It needs no credentials. Returns currentVersion (v-prefixed when it is numeric), updateAvailable, and newestVersion plus a matching releaseUrl when the release lookup succeeded and the latest release is not older than currentVersion. If update checks are disabled or GitHub is unreachable it still answers, with updateAvailable false and no newestVersion, so a missing newestVersion means unknown, not up to date. Optional current compares that version instead of the running one. For build details, release notes or digest-based updates of non-release tags use server.app_version.
• Acciones relacionadas: server.app_version, environment.version, system.upgrade_check, system.upgrade