README accuracy: the listing, the component address, the dependency line

[pavel-te]

Rebased onto main and revised. Documentation only.

What was wrong

Claim	Reality
"a composite Marketplace action"	no listing exists — /marketplace/actions/ptc-translate, /ptc-action and /private-translation-cloud all return 404, and a Marketplace search returns nothing
a GitLab CI/CD Catalog component, with its address in a copy-paste block	a component address is resolved by the reader's own GitLab instance, so one published elsewhere can never be included from theirs; the include fails before any of our code runs
"Both pin ptc-cli v1.0.2"	this action vendors v1.0.3, and that release is required rather than merely newer — mktemp failed on busybox before it, i.e. on the very alpine image the GitLab recipe asks for

What this does

• GitLab section now carries the self-contained job the CLI prints, with the push-token fallback, the skip marker and a sha256sum for anyone who wants the integrity guarantee vendoring gives the GitHub side for free.
• templates/translate/template.yml stays. It is the component source for anyone mirroring this repository into their own instance, where the address is finally theirs and resolves. Its header used to hand out our address; it now explains what the file is for and shows a placeholder. A collapsed block in the README says the same, so a reader learns the file exists without being handed a recipe that cannot work.
• Marketplace claim dropped. uses: resolves against the repository, so nothing is lost by saying so.
• The skip marker is described as what it is: a human-readable label, not a CI skip token. GitHub honours only [skip ci], [ci skip], [no ci], [skip actions], [actions skip]. Loop safety comes from the paths: trigger and from ptc/translations not being a trigger branch.
• Quick start drops config-file: api-token is the only input you must pass, and a root .ptc-config.yml is picked up on its own.
• Dependency line: it installed jq, which the CLI never invokes, and did not name unzip, which unpacks every download. alpine:3.22 provides unzip as a busybox applet, so the job ran either way — naming it keeps it working if the image is ever swapped. git stays for the push step.

Self-test

The step that parsed templates/ still parses it, joined by a check that no file carries a component address pointing back at this repository. Prose about include: component: in general stays allowed — the check targets the copy-pasteable address.

Run before pushing:

• action.yml and the template parse; api-token stays the only required input
• the input-handling check still passes
• the new address check passes here and fails on the previous revision — it catches the README block and the template header, which is the point of adding it
• the sha256 printed in the README matches both the vendored script and the released file the recipe fetches
• every link in the README resolves

Also drops internal tracker identifiers from comments.