Public application form renders the object name `ats_inquiry` as its heading and leaves the form title / section label untranslated

[os-sam]

Found while taking the release screenshots for #9 (card 14); not fixed there — a release card ships no behaviour change, and the fix lands in the Console, not in this repository.

What was measured

cli 17.3.0, memory driver, branch claude/issue-9-release, 2026-09-07. Headless Chromium, no session (the public form is anonymous).

GET /api/v1/forms/apply returns the authored copy:

{"slug":"apply","object":"ats_inquiry","form":{"type":"simple","columns":1,"title":"Apply","description":"Tell the employer who you are. They will be in touch through the platform.", ... "sections":[{"name":"apply","label":"Your application", ...

/_console/f/apply renders, as its whole visible text:

Browser locale	Rendered
en-US	ats_inquiry · Your application · Job* · Full Name* · Email* · Phone · Cover Letter · Résumé · Submit
zh-CN	ats_inquiry · Your application · 岗位* · 姓名* · 邮箱* · 手机 · 求职信 · 简历 · Submit

So on the page a visitor actually sees:

1. the heading is the object name ats_inquiry, not the form's title ("Apply") — in both locales;
2. the form description is not rendered at all;
3. the section label "Your application" is not translated although the bundle carries objects.ats_inquiry._sections.apply.label = 你的投递 and objects.ats_inquiry._views.apply_public.label / .description (both accepted by os validate — it warns only for view names the object does not declare), while the field labels on the same page are translated.

The field-label half proves the bundle reaches the page; the heading and section half show the public-form page reads object.name for its title and skips the _views / _sections resolvers the app pages use.

Where it lands

The public-form page in the Console (objectui), i.e. upstream — the app authors the right keys already. Filed here so the release README's "public application form" paragraph has a tracked caveat; the maintainer may want to mirror it upstream.

Not in scope of #9

Release card; no metadata or behaviour change. The zh-CN screenshot set in docs/screenshots/ therefore does not include the public form.

[os-sam]

Traced to the Console source and filed upstream: objectui#8408. Every symptom in this card is confirmed, all three land in one file — apps/console/src/components/FormPage.tsx — and I read each line rather than inferring it.

The heading. FormPage.tsx:1118 computes it as payload.label ?? payload.form?.label ?? payload.object. The public-form endpoint sends no top-level label, and form.label does not exist because a form config carries title, not label — a fact this repository's own dependency already documents at FormPage.tsx:176-200 and form-spec.ts:286-296 ("FormViewSchema REJECTS it — unrecognized_keys"). So form.title = "Apply" is a real, typed, populated key that the chain never reads, and the heading falls through to the object API name. The subtitle slot below it (:1860) is unreachable for the same reason.

The description is fetched and dropped: grep -n description over all 1948 lines of that file returns exactly one hit, inside a comment.

One correction to this card, which I got wrong when I filed it. The body argues that the field labels rendering translated "proves the bundle reaches the page", so the page must be skipping the _views/_sections resolvers the app pages use. That inference does not hold. FormPage imports nothing from @object-ui/i18n — zero hits for useObjectLabel, useSafeFieldLabel, useTranslation — so it applies no client-side translation to anything, field labels included. Those arrive already localized in the server payload. The observable table above is unchanged; the mechanism is not "one resolver used, another skipped", it is "no resolver at all, and only one of the three strings happens to arrive localized". The upstream issue carries the correction so the next person is not misled by it.

There is also a structural detail worth knowing before anyone estimates the fix: buildSections (:553) copies only sec.label onto its render row and drops sec.name, so the objects.<object>._sections.<name>.label key cannot be built at the render site at all — the i18n half is not a one-line change, unlike the heading half.

Nothing to do in this repository. The app already authors the right keys; docs/screenshots/ still has no public-form shot for the reason this card gives. Keeping this open as the tracked caveat behind the README's "public application form" paragraph until objectui#8408 lands.

---

Generated by Claude Code