P4a: render the hero name in the reader's script

[mashkovd]

Goal

The home page hero renders Dmitrii Mashkov as a single unpaired string. It should render Dmitrii Mashkov in English and Дмитрий Машков in Russian.

This is not a defect in #24. That pull request implemented its proposal exactly, and the proposal required the unpaired string. AGENTS.md was amended afterwards (#25) and that amendment does not reach backwards onto an already-approved proposal — so the change needs its own cycle and its own contract. This issue is that contract.

Why

AGENTS.md, site constraints:

The name is a translated string, not a proper noun exempt from it. English renders Dmitrii Mashkov, Russian renders Дмитрий Машков. They are the same person and different scripts, so the hero is an .l.en / .l.ru pair like any other copy, and it is set in Onest — Instrument Serif ships no Cyrillic and would drop the Russian half onto a fallback family. The <title> element holds one string and stays Latin; a browser tab is a filing label, not prose.

Every other string on the home page is properly bilingual. If the name stays the single exception it becomes the one element that looks machine-made, on a site whose whole argument is that it was not. A Russian reader shown a transliteration of a Russian name reads a page that was translated rather than written.

Note the earlier typography note claimed the name is "identical in both languages" and therefore safe in the editorial face. That was wrong: Дмитрий Машков and Dmitrii Mashkov are different scripts, which is exactly why Instrument Serif cannot set the Russian half.

Files expected to change

• src/i18n/ui.ts — add heroName: { en: 'Dmitrii Mashkov', ru: 'Дмитрий Машков' }. Leave homeTitle exactly as it is: that is the <title> value and stays Latin on both sides.
• src/pages/index.astro — render the <h1> through Lang with the new pair instead of the literal string.
• src/styles/site.css — whatever rule sets the face for .hero-name must resolve to Onest, never Instrument Serif.
• test/ui.test.ts or test/home.test.ts — assert that heroName has both locales and that they differ, so a future "simplification" back to one string fails the suite.

Copy

heroName.en	Dmitrii Mashkov
heroName.ru	Дмитрий Машков
homeTitle	unchanged, Latin, both locales

Acceptance criteria

1. The built dist/index.html contains Dmitrii Mashkov inside an element carrying class="l en" and Дмитрий Машков inside one carrying class="l ru".
2. The .l.en and .l.ru counts on the page remain equal.
3. The computed font-family for .hero-name resolves to Onest first, and Instrument Serif appears nowhere in that rule.
4. <title> is Dmitrii Mashkov regardless of data-lang.
5. npm test and npm run build pass; dist/ still contains no JavaScript.
6. A test fails if heroName.en and heroName.ru are ever made identical.

Out of scope

• Any other string on the page.
• Finding new work for Instrument Serif. It may end up unused on this page; that is a design question for whoever needs the face, and the answer to "our editorial font has no Cyrillic" is not "then write the name in the wrong script".
• The calls to action still pointing at /work/ and /colophon/, which land in P5: Work page with project entries #7 and P7: Colophon page, journal and ADR routes, cycle table and backfill #9.

🤖 Generated with Claude Code

https://claude.ai/code/session_01MPpAwcFk2L1B94VT8LiKVx

[mctl-agents]

mctl-agents issue-investigator has analyzed this issue and created a proposal:

https://github.com/mctlhq/mctl-gitops/tree/main/platform-gitops/agents-state/portfolio/proposals/issue-27-p4a-render-the-hero-name-in-the-reader-s/

Status: proposed — pending human approval. Review requirements.md, design.md and tasks.md, then approve: signal this issue's DevLoopWorkflow (mctl-api POST /api/v1/agents/dev-loop/dev-loop-mctlhq-portfolio-27/approve, or python -m orchestrator.temporal.cli approve dev-loop-mctlhq-portfolio-27 --approver <your-identity>) — the workflow flips .status.yaml to accepted via the mctl-agents-approve operation and runs the Tier 2 implementer. If no DevLoopWorkflow is running for this issue (pre-Temporal proposal), run the mctl-agents-approve operation directly with service=portfolio slug=issue-27-p4a-render-the-hero-name-in-the-reader-s.

The approver is recorded in .status.yaml and in the gitops commit, and the implementer refuses a proposal whose control.requires_human_approval carries no named approver — so prefer the mctl-api endpoint, which takes the approver from the authenticated caller rather than from what the caller types.