Five cards break their directory's schema, two carry non-ASCII (found by the #6063 test lane) #7911

Part of #6063 (t27b coverage). Found while writing real tests for the pass_vacuous cards of specs/crons and specs/functions (the lane of #7903). The tests hold each card to the schema its directory's README states. Five cards break that schema, and two more carry non-ASCII text. The lane does not change any existing line of a spec, so the tests leave these rules out on the cards below; nothing here is fixed by the lane.

What is wrong

1. specs/crons/railway-jobsearch-cron.t27: ID does not carry REPO.
   • specs/crons/README.md says ID is <host>/<repo>/<slug> and REPO is the short repo name.
   • The card has ID = "railway-cron/999/jobsearch-cron" and REPO = "railway".
   • Either REPO should be the repository the middle segment names (999), or the README should say what <repo> means for a Railway cron service.
2. Four function cards break the ID grammar of specs/functions/README.md (<domain>-<object>-<verb>, with DOMAIN its first part):
   • client-telemetry-daily.t27 and club-invoice-abandoned-watch.t27: DOMAIN = "analytics".
   • robokassa-unclaimed-watch.t27 and ton-pending-watch.t27: DOMAIN = "money".
   • The other 29 function cards follow the grammar.
3. DOMAIN = "money" is outside the README's vocabulary. The vocabulary is neuro | reels | training | morph | render | payment | broadcast | instagram | content | monitoring | analytics | webhook | welcome | crm. The two cards of item 2 use money.
   • The README's own generator rules do not list DOMAIN among the fields that fail the build.
   • Either add money to the vocabulary or use payment.
4. Non-ASCII text in two cards (L3 PURITY; both READMEs say the cards are ASCII-only):
   • specs/crons/trinity-brain-ci.t27: NAME holds a superscript three and an em dash.
   • specs/skills/t27-wave-audit.t27: NAME holds an em dash.

The four function cards of item 2 came home from trinity's mirror in #7304. The railway card and the two cards of item 4 date from the first commit of the catalogs (#3543).

What the lane's tests do about it

• Item 1: the railway card's test checks only the shape of ID (<host>/<a>/<b>), not its middle segment.
• Items 2 and 3: those cards get no <domain>-... test. The two analytics ones still check that DOMAIN is in the vocabulary; the two money ones do not.
• Item 4: no test reads NAME.

Done when

Each card agrees with its README (or the README states the exception), and the lane's tests can check the rule on these cards too.

User Scenarios

• Given a specs/crons/railway-jobsearch-cron.t27 card with ID = "railway-cron/999/jobsearch-cron" and REPO = "railway", when the card is validated against specs/crons/README.md which states ID is <host>/<repo>/<slug> and REPO is the short repo name, then the card either has REPO = "999" or the README clarifies what <repo> means for Railway cron services.
• Given four function cards (client-telemetry-daily.t27, club-invoice-abandoned-watch.t27, robokassa-unclaimed-watch.t27, ton-pending-watch.t27) with DOMAIN values analytics or money that don't match their ID prefix, when validated against specs/functions/README.md which requires ID grammar <domain>-<object>-<verb> with DOMAIN as its first part, then each card's DOMAIN matches its ID prefix and is in the README's vocabulary.
• Given specs/crons/trinity-brain-ci.t27 and specs/skills/t27-wave-audit.t27 with non-ASCII characters in NAME, when validated against their directory READMEs which state cards are ASCII-only, then both cards contain only ASCII text.

Requirements

• FR-001: specs/crons/railway-jobsearch-cron.t27 MUST have REPO equal to the middle segment of ID (999) or specs/crons/README.md MUST document the exception for Railway cron services.
• FR-002: specs/functions/client-telemetry-daily.t27 and specs/functions/club-invoice-abandoned-watch.t27 MUST have DOMAIN matching their ID prefix (client and club respectively) and the value MUST be in the vocabulary of specs/functions/README.md.
• FR-003: specs/functions/robokassa-unclaimed-watch.t27 and specs/functions/ton-pending-watch.t27 MUST have DOMAIN matching their ID prefix (robokassa and ton respectively) and the value MUST be in the vocabulary of specs/functions/README.md, or money MUST be added to the vocabulary.
• FR-004: specs/crons/trinity-brain-ci.t27 MUST contain only ASCII characters in all fields.
• FR-005: specs/skills/t27-wave-audit.t27 MUST contain only ASCII characters in all fields.
• FR-006: The lane's tests MUST validate the REPO field against ID middle segment for the railway card.
• FR-007: The lane's tests MUST validate <domain>-<object>-<verb> grammar and vocabulary membership for all four function cards.
• FR-008: The lane's tests MUST validate ASCII-only NAME fields for the two non-ASCII cards.

Boundary

• specs/crons/railway-jobsearch-cron.t27
• specs/crons/trinity-brain-ci.t27
• specs/skills/t27-wave-audit.t27
• specs/crons/README.md
• specs/functions/README.md
• specs/functions/client-telemetry-daily.t27
• specs/functions/club-invoice-abandoned-watch.t27
• specs/functions/robokassa-unclaimed-watch.t27
• specs/functions/ton-pending-watch.t27