Make the documentation runnable, and fix the config examples

[pavel-te]

Documentation and shipped examples, plus one new test suite. No CLI behaviour changes.

detect_config note

The README and the CLI both said detect_config had to be reached at a different host. It answers on the default API host without a token:

$ curl -s -X POST https://app.ptc.wpml.org/api/v1/detect_config \
    -H 'Content-Type: application/json' -d '{"file_paths":["locales/en.json","locales/fr.json","package.json"]}'
{"kind":"node","source_locale":"en","files":[{"file":"locales/en.json","output":"locales/{{lang}}.json"}], ...}   # HTTP 200

ptc init is the first command the docs recommend, so that note stood between a new user and their first run. Removed from the README, from show_init_help and from the 404 hint, which now says what a 404 there means. The quick start also passed a token to init, which needs none.

A README example could not be copied

./ptc-cli.sh -c config.yml --file-tag-name=feature-branch exits 1. The = form is implemented for --api-url, --api-token, --monitor-interval, --monitor-max-attempts and --action only, while another example in the same file uses a working --api-url=…, so the rule was not inferable. The example now uses the separate-argument form, and the rule is written down under Main Options.

Accepting = everywhere is the other way to resolve this. That changes CLI behaviour and needs a release, so it is not part of a documentation change.

Both CI blocks were out of date

	was	now
GitHub	old pinned release, superseded third-party actions, a fresh PR per run	what ptc init prints
GitLab	never downloaded the CLI, triggered on merge requests	what ptc init prints

Checked by running ptc init for a GitHub project and a GitLab project and diffing its output against the page.

Dependencies in the generated job

It installed jq, which this script never invokes, and did not name unzip, which unpacks every download. alpine:3.22 provides unzip as a busybox applet and extraction works, so the job ran either way — naming it keeps it working if the image is ever swapped. git stays for the push step.

Three of five examples could not be used

java-app, react-app and wordpress-wpsite were KEY=VALUE files with a single-brace placeholder. Each stopped at Missing 'files:' section, and only {{lang}} is substituted. They are YAML now, renamed .config → .yml since the extension is what suggested the wrong format. config.local.yml.example no longer shows api_token:, ignored with a warning for several releases.

New suite

Nothing had ever fed an example to the parser. tests/test-config-examples.sh builds a scratch project from each config's declared paths, runs a real --dry-run, then checks the placeholder form and the absence of a token key.

Confirmed it reports the previous files as failures before relying on it:

[FAIL] zz-probe.yml is parsed as a config (got: Missing 'files:' section)
[FAIL] zz-probe.yml uses {lang}; only {{lang}} is substituted
exit code with a broken example: 1

Verification

• 230 assertions across seven suites, no failures (215 before this one)
• bash -n ptc-cli.sh clean
• All 20 fenced blocks in the README parse as the language they are tagged with — four showed CLI output while tagged bash and are text now
• Every link in the README resolves

Also drops internal tracker identifiers from source comments throughout.