shared-workflows now depends on the CLI surface, and neither side records it

[mairas]

halos-org/shared-workflows/.github/workflows/translation-status.yml
(#39) hard-codes four
invocations of this package: translation-status --format markdown --diff,
translation-status --comment, translation-status --check, and
check-anchors site.

Two version axes with no stated compatibility range. Consumers pin this package
to a tag in their own pyproject.toml; they pin the workflow at @main. So a
workflow change that uses a flag added in a later release breaks every consumer
still on an older pin, at once, and the failure surfaces as argparse printing
unrecognized arguments inside somebody else's CI.

AGENTS.md names the consumers of the entry points as hatlabs/halpi2,
halos-org/docs.halos.fi and the translate-page skill. shared-workflows is
not on that list, so a rename gets reviewed against a consumer set that omits
the one consumer that hard-codes flags rather than calling the commands
interactively.

Two things to do:

1. Add halos-org/shared-workflows to the consumer list in AGENTS.md.
2. Decide how the workflow states a minimum version. Related to
   #5, which notes that no
   command has --version and nothing ties the git tag to project.version —
   a floor is not enforceable until that is settled.