{{- /* SPDX-License-Identifier: AGPL-3.0-only OR LicenseRef-Commercial */ -}} {{- /* SPDX-FileCopyrightText: 2025-2026 Christian Galo */ -}} {{/* Application shell: the account menu's second home. Pipeline: server.Shell. Contract: chrome-conventions "Session controls live in the account menu on both surfaces". Below the lg breakpoint the rail is the shell's one menu, so the account items render inside it as their own labelled group at the drawer's foot; at lg and up the whole group is hidden (d-lg-none) and the static rail carries task destinations and the surface switch only. It is a second list, not more entries in the rail's list, because these are not destinations: a screen reader should hear two groups, and the group's name is the person (design D8, the research note). The identity block is that name, through aria-labelledby, so the group is labelled without inventing copy; it is a paragraph, not a heading element, because the anatomy lint reserves those for the section-header part. The items, their order and their rules are the top bar dropdown's, from one template so the two surfaces cannot drift (D4): the person, Identity and Access, Get help when a support URL is configured, Sign out. Sign out posts here too, for the same reason it posts in the bar: a link would be a GET any origin could send the browser to (logout-ends-session D6). Included by shell_rail_member.html and by operator.html's rail, after the entry list. */}}

{{- if .Email }}{{ end }}