fix(devx): derive wire producers past the REST door's translating arms (#15762)

`check:error-status-conformance` read `DuplicateRecordError`'s `readonly
status = 409` as "the runtime can emit HTTP 409 for DUPLICATE_RECORD", so
direction A required a scanned page to publish 409 for a code that never
crosses HTTP. Per the #14723 ruling that code is the engine's in-process
identity; the REST door answers `UNIQUE_VIOLATION` on every route.

`deriveDoorTranslations` reads those arms out of the door's own source — a
guard on `error?.code` / `error?.name` whose `{ status, body: { code } }`
terminal answers a different code — never a hand-written list. R1 skips a
class the door translates away and REPORTS it in a new `translated` census;
a translated code is kept out of the unpinned census too, since the door
pins the answer under its wire spelling.

Pinned in `--self-test` battery 26 (8 cases): the arm-less negative control
still produces, the guard's class name is load-bearing, a `code: error.code`
arm translates nothing, and an untranslated code is untouched.


Claude-Session: https://claude.ai/code/session_012zGPuVVX3deAx9LdjK8jCk

Co-authored-by: Claude <noreply@anthropic.com>

Author: claude[bot]