[rabbitson87]

Change

The two non-blocking notes from the last review of #229, in docs/guide.md:

• Settings label: the Portal section now says Settings → Phone & devices → Pair a device, matching the app (SettingsDialog.tsx) and the rest of the guide. The devices.json paragraph had the same old "Settings → Devices", so it is updated too.
• Portal keeps its name: half a sentence after the command says the first run saves the name in the identity file and later runs reuse it. The random --name in the command therefore does not give a new address on each start (LoadOrCreate, portal/identity/client_identity.go in Portal v2.6.1).

The sign-in screen's own text (AccessGate.tsx) still says "Settings → Devices". That is a UI string with ko/ja/zh translations, so I left it for a separate change.

Docs only; no CHANGELOG entry, since app users do not notice it.

Validation

• No "Settings → Devices" is left in docs/guide.md; "Phone & devices" is the label in src/components/SettingsDialog.tsx.
• Checked the identity behavior against Portal v2.6.1's LoadOrCreate: an existing identity file is parsed as it is, and its stored name is used. I did not restart a tunnel to see it live.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Repository: devswha/herdr-web-ui/.coderabbit.yaml
• Review profile: CHILL
• Plan: Advanced
• Run ID: 0a872526-46b4-4e63-a906-7cb5748c7bda

---

📥 Commits

Reviewing files that changed from the base of the PR and between a01d7f4 and f06108c.

---

📒 Files selected for processing (1)

• docs/guide.md

---

Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 3 remain after this review.

---

---

📝 Summary

Summary by CodeRabbit

• Documentation
  • Clarified that the Portal reuses the generated name saved during the first run on subsequent runs.
  • Updated pairing guidance to refer to Phone & devices instead of Devices.
  • Updated device-registry error guidance to use the current Phone & devices settings label.

Walkthrough

The guide now says the first run saves the generated Portal name in the identity file and later runs reuse it. It updates the settings path for device pairing and device-registry errors to Phone & devices.

Changes

Portal guide updates

Layer / File(s)	Summary
Portal identity and device instructions docs/guide.md	The guide describes first-run name storage and reuse. It updates the pairing and device-registry error paths to Phone & devices.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Other

Suggested reviewers: devswha

---

Merge Risk: ⚪ Minimal · up to f0610

No actionable merge risk is identified in the supplied guide updates.

Architecture Summary

Architecture risk: 🔵 Low · up to a01d7

The change affects 1 system.

Changed systems: docs

Architecture concerns
No architecture-level concerns identified.

Review details

Systems and components

• observed — docs (service) was modified; 1 changed file maps to changed impact.

Before / after behavior

• observed — Modified behavior in docs/guide.md: The Portal instructions now say that the first run saves its generated name in the identity file and subsequent runs reuse it.
• observed — Modified behavior in docs/guide.md: The pairing path in Settings is updated from Devices → Pair a device to Phone & devices → Pair a device.
• observed — Modified behavior in docs/guide.md: The instructions for viewing devices.json errors now direct readers to Settings → Phone & devices instead of Settings → Devices.

---

---

---

---

Pre-merge checks | 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check		The title clearly identifies both documentation changes: the updated Settings label and Portal name reuse behavior.
Description check		The description includes the Change and Validation sections, explains the resulting behavior, records validation results, and identifies the unchanged sign-in text as separate scope. No screenshot or …
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

---

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create a new PR

---

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

---

_{Comment @coderabbitai help to get the list of available commands.}

[devswha]

Thanks! I checked each claim against the code, and they are all correct:

• Settings → Phone & devices → Pair a device: Phone & devices is the page's label (src/components/SettingsDialog.tsx, PAGES title), and the Pair a device button lives on that page (DevicesPanel.tsx).
• devices.json paragraph: with a damaged registry, /api/devices answers 503 device_store_unavailable with the full message for the owner (server/devices.ts), and the Devices panel on that page shows it as an alert. So "Settings → Phone & devices and the server log explain the error" holds.
• Portal keeps its name: in v2.6.1, identity.LoadOrCreate (portal/identity/client_identity.go) parses an existing identity file as-is, without looking at --name, and cmd/portal-tunnel/tunnel/runtime.go uses that identity. A new random --name on a later start therefore changes nothing, as the added sentence says.

Non-blocking, for a follow-up rather than this PR: besides AccessGate.tsx, which you already noted, the server's own 503 text for non-owner callers in server/devices.ts still says "Settings → Devices".