feat: make Home Link a reusable remote dashboard

[frahlg]

What changed

• turns the Home Link page into a read-only dashboard that matches the local FTW layout
• adds Overview, Energy, Plan and System views with the existing FTW theme and energy-flow component
• asks for one passkey per encrypted browser session, then reuses that authorization for fixed reads
• remembers the non-secret home invite in the browser and adds an explicit “Forget this home” action
• extends the encrypted session ceiling to 30 minutes and keeps every authorization bound to the exact route, generation, session and stream

Why

The beta page exposed raw JSON and asked for a passkey on every read. It did not feel like remote access to the user’s FTW.

Safety

• read-only and limited to the five existing typed Home Link scopes
• the reusable grant token stays inside Core and never reaches the browser or relay
• every read still checks the request hash, session binding, expiry and credential revocation
• no generic proxy, remote write, Buzz, or shared production dependency

Validation

• make verify-all
• focused Home Link race tests, 10 runs
• npm test (238 tests)
• desktop and mobile visual checks in dark and light themes
• normal pre-commit and pre-push hooks

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ca5ccf184e

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Clamp read authorization to the session expiry

When passkey verification crosses a millisecond boundary, this calculates the remaining TTL before verification, but IssueReadSession later sets ExpiresAt from its post-verification wall clock plus that full TTL. The returned expires_at_ms therefore exceeds the signed session expiry, and HomeLinkSession.authorize() rejects it via result.expires_at_ms > this.expiresAtMS, making Unlock fail with “session authorization failed” under ordinary verification latency. Pass the absolute session deadline through or subtract the elapsed verification time before returning the grant.

AGENTS.md reference: AGENTS.md:L72-L75

Useful? React with 👍 / 👎.