| name | mx-space-remote-translation-audit |
| description | Audit remote mx-space translation data through ssh to the swarm host, then docker exec into the Postgres container and run psql inside the container. Use for checking translation_entries coverage, ai_translations gaps, strict computeContentHash mismatches, and runtime freshness semantics in deployments where direct Postgres access is unreliable. |
mx-space Remote Translation Audit
Use this skill when validating remote mx-space translation state in translation_entries or ai_translations — coverage, freshness, hash drift, or route-level behavior.
This deployment migrated MongoDB → PostgreSQL. Older notes referencing mongosh, refType/sourceModified, or other camelCase fields are stale.
For connection mechanics see the sibling skill mx-space-remote-db-access: mx_core database, mx role, mx-space-pg-* container, container env auto-sets credentials.
Critical semantics (must not collapse)
strict hash mismatch != runtime stale
| Status | Meaning |
|---|
missing | no translation row exists for the requested language |
strict hash mismatch | translation.hash !== computeContentHash(current source) |
runtime valid | source_modified_at >= article.modified_at, or created_at >= article.modified_at when source_modified_at is absent, or hash matches |
