fix(ui): key reverse answers by address and chain

[mariano-aguero]

What

Reverse resolution answers are filed by address and chain, instead of by address alone.

Why

The request already scopes each address to its chain with an @eip155:<chainId> suffix, and the dedupe key already carried the chain, but the answers were stored under the lowercased address on its own. A batch spanning two chains collapsed both answers onto one entry, and whichever came back last was rendered on both rows. An address with a name set on Base showed that name on a mainnet transaction.

The chain is read back from the coinType each slot echoes rather than from the slot's position in the response array. Both are documented and the order is stable, but the failure modes differ: by position a mismatch puts a name on a row it was not read for, while by coinType it leaves the address as hex. On a signing screen the failure has to fall toward the hex. A slot whose coinType is null failed before the lookup and has no chain to be filed under, so it is dropped.

Closes

N/A

How to test

bun install
bunx nx run-many -t typecheck lint test --projects=@jaw.id/ui
bunx nx build @jaw.id/ui

packages/ui/src/utils/reverseResolve.test.ts covers one address asked on mainnet and on Base, that both still go out in a single request, and that an unplaceable slot is dropped. Reverting the keying line on its own makes the first fail, with the Base name sitting on the mainnet entry.

Checklist

• The title is a conventional commit and reads as the subject it becomes on squash. nx release takes the version bump from its type
• bunx prettier --check . and bunx nx affected -t lint test typecheck build api-check pass, which is what CI runs
• @jaw.id/core's public API is unchanged, or bunx nx api-update @jaw.id/core ran and the report diff is part of this PR
• Docs updated, if this changes behaviour somebody integrates against

prettier --check . passes and every affected task passes except @jaw-mono/keys-jaw-id:test, which fails on Node 25 and later for a reason unrelated to this change. #347 fixes it. The keys of the returned record are internal to @jaw.id/ui, so there is nothing to document.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
demo	Ready	Preview	Sep 22, 2026 8:58am UTC
jaw-docs	Ready	Preview	Sep 22, 2026 8:58am UTC
keys-jaw-id	Ready	Preview	Sep 22, 2026 8:58am UTC
playground	Ready	Preview	Sep 22, 2026 8:58am UTC

[justalab-agents]

Findings outside the diff

These sit on lines this PR did not change, but this PR is what makes them wrong. They cannot be posted as inline comments.

• [WARNING] .github:2 — Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: amannn/action-semantic-pull-request@v5. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Reviewer callouts (1)

Non-blocking observations. Nothing here needs to change before merge.

• .github:1 — "The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see actions/runner-images#14748"