Skip to main content

​
run output (text)

Key summary fields:
  • planned_total
  • skipped_by_lock
  • executable_total
  • succeeded
  • failed
  • persisted_to_lock
Failure line format: 
failure target=<path> key=<key> reason=<reason>

​
status output (csv)

Header columns: 
key,namespace,locale,status,origin,state
Interactive mode:
  • hyperlocalise status --output csv -i renders a TTY dashboard for manual triage.
  • CSV remains the canonical machine-readable format for CI and automation.

​
sync output (text or json)

Text summary fields:
  • action
  • creates
  • updates
  • unchanged
  • conflicts
  • applied
  • skipped
  • warnings
Use JSON output when integrating with CI checks. Common sync warning or conflict cases include:
  • invariant validation blocked an unsafe change
  • adapter only supports best-effort remote concurrency
  • unresolved remote identity for a local key during push
  • post-push verification detected a remote mismatch

​
CSV translation files

When run writes .csv translation targets, output row order is deterministic for newly appended keys (sorted by key), and existing rows keep their original order.

​
Fluent translation files

When run writes .ftl translation targets, existing comments, blank lines, and message order come from the selected template. Parsed message and attribute value spans are replaced in place. Missing top-level message keys are appended in sorted order, and unsupported Fluent terms fail before output is written.