… approvers (#3405, #3508)

Both issues shipped their platform fix but left their last acceptance item on a
real backend, and showcase had no specimen for either shape.

**#3405 — `p_assignee`, an inline `lookup` at `sys_user`.** The gallery already
covered an inline picker aimed at one of the app's own objects
(`p_account` → `showcase_account`). The reported bug (PLAT-DEF-005: "assign an
inspector" handed the supervisor a box wanting a pasted UUID) was a picker at a
SYSTEM object, and a person is the reference a human is least able to identify
by id — `sys_user` ids here are opaque 32-char tokens. That earns its own
specimen rather than riding on the account one.

**#3508 — `showcase_approver_bindings`, one approval node per record-backed
approver kind.** The existing flows cover `position` heavily and
`dynamic-approval` covers `org_membership_level` + `expression`; `user`, `team`,
`department`, `manager` and `field` had no specimen at all, which is why the
designer's Value control could regress unnoticed. `queue` is deliberately
absent — #3536 made it non-authorable.

The flow is `draft` on purpose, not by omission: the record-backed kinds point
at rows a fresh boot does not have (`sys_team` is empty, and unit membership /
position assignment are runtime admin actions by design — see the seed notes).
An `active` flow over them would resolve to nobody, which is the exact silent
dead slot #3508 exists to remove; shipping that as a demo would re-teach the bug.
`draft` keeps it out of the runtime while still loading in the designer, which
is the surface under test.

Verified on a real backend (showcase :5411 + objectui HEAD console :5412, own DB):
- the server publishes `reference` for both inline picker params;
- the param dialog renders Assignee as a searchable picker — typing "Dev" issues
  `GET /api/v1/data/sys_user?top=50&search=Dev` and offers "Dev Admin
  / admin@objectos.ai", with no degrade warning logged;
- the designer renders a record picker per kind off the published
  `xRef.sources`, listing the real seeded org tree for `department`
  (`sys_business_unit`), `manager` as a disabled "Resolved automatically" cell,
  `field` as the trigger-object field selector, and no `queue` in the Type
  dropdown. No `/api/v1/meta/:type` registry calls — the old broken path.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LkvDs4y4gveyB5NJZKxaZt

The "Check Changeset" gate requires one on every PR, not only on PRs that touch
a published package — and it sanctions an empty changeset for a change that
releases nothing, which this is: both specimens live in
`@objectstack/example-showcase`, which is `private: true`, so changesets would
skip it regardless. Matches the existing empty-changeset entries
(`adr-0104-design-doc-only.md` and friends).

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LkvDs4y4gveyB5NJZKxaZt

`check-i18n-coverage` ratchets each example at its current untranslated count,
so a newly declared label that skips a locale the example claims to support
pushes the count up and fails the gate — 456 → 460 here (`p_assignee`'s `label`
and `helpText`, each counted on two surfaces).

Translated rather than ratcheting the baseline up: ratcheting is what the gate
exists to prevent, and the script only sanctions `--update` for a count that
went DOWN. The gallery's older params sit inside the 456 baseline; this one is
not allowed to widen it.

`负责人` is what the bundle already renders for `showcase_task.assignee`, so the
same idea keeps one word. The flow specimen's own label/description are not
flagged — the `i18n/missing-action` rule covers action params, not flow nodes.

`check-i18n-coverage` now reports "none new"; validate, typecheck and the 58
example tests all pass.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LkvDs4y4gveyB5NJZKxaZt