[0xacee]

Problem and change

A guest link can expire while Owner access remains open, but the page only evaluates its timestamps during an unrelated render. The link stays active, the available count remains too high and its revoke action stays visible until the operator interacts.

Refresh time-dependent display state at the next known guest expiry and every 30 seconds for relative labels. Returning to a visible tab refreshes the clock immediately. Summary counts and rows use one timestamp, with expiry inclusive at its boundary; owner cards remain revoke-only. This uses the already loaded inventory and makes no extra API requests.

Validation

• New public-component regressions: 2 failed / 1 passed on freshly fetched upstream/public-beta.
• All 10 Invites, expiry and response-body deadline tests passed.
• Fake-clock tests cross the exact guest expiry, resume a suspended tab, preserve owner-card actions, check available counts and verify timer cleanup/no extra requests.
• Production dashboard build passed. ESLint zero errors, 26 pre-existing JSX unused-symbol warnings; git diff --check passed.

Scope and related work

Live PR review: #3290/#3289/#3207 test date/status helpers, #3833 addresses stale network refreshes, #4955 addresses focus, and #5291 addresses pending creation ownership. This fixes wall-clock invalidation of already loaded inventory and can be reviewed independently of those flows.

Browser timers may be throttled while backgrounded; visibility restoration corrects the displayed clock. Server-side token enforcement is unchanged and remains authoritative. jsdom validation is not a live browser/host test; independent human review and browser qualification remain pending.

AI-assisted implementation and validation by Codex; ready for review is not approval to merge.