feat(ensadmin): Apply namehash-ui package

[Y3drk]

Substantial PR → apply namehash-ui package in ensadmin

NOTE: This is very much a WIP. I'll update the PR's description once it reaches ready-for-review stage.

---

Reviewer Focus (Read This First)

What reviewers should focus on

Where should reviewers spend most of their time?

Call out:

• The risky or non-obvious parts
• Areas where you're least confident
• The kind of feedback you actually want

If your answer is "everything," explain why targeted review isn't possible.

Limit this to 1-3 areas.

---

Problem & Motivation

Why this exists

Explain:

• What problem this PR is solving
• What's broken, fragile, or getting worse without it
• Why this change is happening now
• Links to issues, incidents, or prior discussion

Keep this tight. Bullets are fine.

---

What Changed (Concrete)

What actually changed

List the concrete behavioral or structural changes in this PR.

This should be a factual inventory, not a narrative.
Prefer numbered bullets.

If this list starts getting long, that's a signal the PR may need splitting.

---

Design & Planning

How this approach was chosen

• Link any design docs or notes that existed before or during implementation
• If this didn't warrant upfront design, say why
• Mention the most realistic alternatives you considered and why you didn't take them
• If planning was lightweight, be explicit about that

• Planning artifacts:
• Reviewed / approved by (only if there was a real review):

---

Self-Review

What you caught yourself

Describe what changed after you reviewed your own diff end-to-end.

This is not optional.

• Bugs caught:
• Logic simplified:
• Naming / terminology improved:
• Dead or unnecessary code removed (or why none was):

---

Cross-Codebase Alignment

Related code you checked

Show that you looked beyond just the files in this PR.

• Terms you searched for to find related code or docs
• Files or packages you reviewed but intentionally didn't change
• Areas you left alone on purpose (and why)

Focus on directly related domains. Don't boil the ocean.

• Search terms used:
• Reviewed but unchanged:
• Deferred alignment (with rationale):

---

Downstream & Consumer Impact

Who this affects and how

Explain how this change impacts:

• Callers
• Readers
• Operators
• Future maintainers

Call out:

• Terminology or concepts that might confuse someone new
• What you changed to reduce that confusion

Point to actual diffs where possible.

• Public APIs affected:
• Docs updated:
• Naming decisions worth calling out:

---

Testing Evidence

How this was validated

Explain:

• How this was tested locally and/or in CI
• What important behavior is not covered by tests
• If this is wrong, what breaks first

• Testing performed:
• Known gaps:
• What reviewers have to reason about manually (and why):

---

Scope Reductions

What you intentionally didn't do

List follow-ups you identified but explicitly deferred to keep this PR reviewable.

Link issues where applicable and explain the tradeoffs.

• Follow-ups:
• Why they were deferred:

---

Risk Analysis

How this could go wrong

Call out:

• Assumptions this PR relies on
• Likely failure modes
• Blast radius if it breaks

• Risk areas:
• Mitigations or rollback options:
• Named owner if this causes problems:

---

Pre-Review Checklist (Blocking)

• I reviewed every line of this diff and understand it end-to-end
• I'm prepared to defend this PR line-by-line in review
• I'm comfortable being the on-call owner for this change
• Relevant changesets are included (or explicitly not required)

[changeset-bot]

⚠️ No Changeset found

Latest commit: b368475

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

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

Project	Deployment	Review	Updated (UTC)
admin.ensnode.io	Ready	Preview, Comment	Jan 13, 2026 3:10pm
ensnode.io	Ready	Preview, Comment	Jan 13, 2026 3:10pm
ensrainbow.io	Ready	Preview, Comment	Jan 13, 2026 3:10pm