Remove --srcFormat/--targetFormat options

docs/AGENTIC_MIGRATION.md

@@ -5,8 +5,7 @@ This document summarizes the important changes when migrating from the pre-agent
 ## What changed (high-level)
 
 - New translation service: `--service=agent`.
-- New preferred flag for same-format workflows: `--format=<one-format>`.
-- Legacy format flags still work for conversions: `--srcFormat` / `--targetFormat` (intentionally not promoted in READMEs).
+- `--format=<one-format>` is the only format flag; the legacy `--srcFormat` / `--targetFormat` flags have been removed.
 - `json` is a supported format and is treated the same as `nested-json` (implementation-wise).
 
 ## New agent workflow (`--service=agent`)
@@ -21,17 +20,15 @@ The first run exits with a non-zero code by design, so CI/CD can detect that tra
 Notes:
 - Empty translations are supported by piping an empty line (line count still must match).
 
-## Format flags: `--format` vs legacy `--srcFormat/--targetFormat`
+## Format flag: `--format`
 
-- Use `--format=<format>` when source + target use the **same** file format.
-- Use legacy `--srcFormat=<format> --targetFormat=<format>` when doing **format conversion** (e.g. XML → iOS strings).
-- `--format` accepts **exactly one** format (no separators, no conversions).
+- `--format=<format>` is required and is used for both source and target files.
+- `--format` accepts **exactly one** format (no separators, no conversions between different formats).
 
 ## Practical migration checklist
 
-- Replace same-format calls:
+- Replace legacy calls:
   - From: `--srcFormat=<x> --targetFormat=<x>`
-  - To: `--format=<x>`
-- For format conversions, keep using legacy flags.
+  - To: `--format=<x>` (only supported when source and target use the same format)
 - If you relied on `--prompt`, remove it from scripts and automation (flag removed).
 - Consider switching scripts to `--service=agent` if you want the agentic two-step workflow.

sample-scripts/po_generic.sh

@@ -7,6 +7,3 @@ BASE_DIR=po-generic
 # Run "npm install --global attranslate" before you try this example.
 attranslate --srcFile=$BASE_DIR/en.po --srcLng=English --format=po --targetFile=$BASE_DIR/es.po --targetLng=Spanish --service=agent
 attranslate --srcFile=$BASE_DIR/en.po --srcLng=English --format=po --targetFile=$BASE_DIR/de.po --targetLng=German --service=agent
-
-# Convert a YAML to PO (just for the sake of test-coverage)
-attranslate --srcFile="$BASE_DIR/nested-fruits.yml" --srcFormat=yaml --srcLng=x --targetFile=$BASE_DIR/nested-fruits.po --targetFormat=po --targetLng=x --service=sync-without-translate

sample-scripts/xml_generic.sh

@@ -7,6 +7,3 @@ BASE_DIR=xml-generic
 # Run "npm install --global attranslate" before you try this example.
 attranslate --srcFile=$BASE_DIR/en.xml --srcLng=English --format=xml --targetFile=$BASE_DIR/ar.xml --targetLng=Arabic --service=agent
 attranslate --srcFile=$BASE_DIR/en.xml --srcLng=English --format=xml --targetFile=$BASE_DIR/de.xml --targetLng=German --service=agent
-
-# Convert an iOS string file into an XML (just for the sake of test-coverage)
-attranslate --srcFormat=ios-strings --srcFile=$BASE_DIR/nested-fruits.strings --srcLng=en --targetFormat=xml --targetFile=$BASE_DIR/nested-fruits.xml --targetLng=en --service=sync-without-translate

sample-scripts/yaml_ecommerce.sh

@@ -12,6 +12,3 @@ node search_replace.js "yaml/es_ecommerce.yml" "en:" "es:" # postprocessing
 node search_replace.js "yaml/de_ecommerce.yml" "de:" "en:" # preprocessing
 attranslate --srcFile=yaml/en_ecommerce.yml --srcLng=English --format=yaml --targetFile=yaml/de_ecommerce.yml --targetLng=German --service=agent
 node search_replace.js "yaml/de_ecommerce.yml" "en:" "de:" # postprocessing
-
-# Convert a JSON to YML (just for the sake of test-coverage)
-attranslate --srcFile="yaml/nested-fruits.json" --srcFormat=json --srcLng=x --targetFile=yaml/nested-fruits.yml --targetFormat=yaml --targetLng=x --service=sync-without-translate