The popover/sheet split reverses — settings fold into the Git tab, the widget stacks name over branch

The titlebar widget becomes a two-line identity block: the board glyph at
22pt spanning both lines, the title over the branch (git-mode only, smaller
and secondary), the em-dash retired. New Branch… returns to the switch menu
behind a divider, revealing an inline name field — the pre-split shape. The
board settings sheet retires whole: add-git and commit identity render
inline in the Git tab's postures (BoardGitSetup.swift), the availability
rule collapses into BoardGitSetupSection.resolve, and Board ▸ Board
Settings… leaves the menu bar. Where 07's remote/credential setup surfaces
land is deliberately left open — filed on the Redesign board.

Claude-Session: https://claude.ai/code/session_01SR4XGjmBE16ZUYWpfFHXwY

Kanban/Git/BoardGitMode.swift

@@ -24,7 +24,7 @@ import Foundation
 /// answers `EACCES`/`EPERM` to is not "no repo there" — it is "cannot tell" — and folding that into
 /// `.none` would let add-git offer app-managed init on a board that might already sit inside a
 /// repository the app simply could not see. `unverifiable` therefore takes `repoNested`'s posture
-/// everywhere structural (no add-git, no app-managed git, `BoardSettingsSheet.resolve` empty), since
+/// everywhere structural (no add-git, no app-managed git, `BoardGitSetupSection.resolve` empty), since
 /// the two share the one property every surface but the popover's prose cares about: neither may be
 /// added to. Its prose is its own — "unverifiable" is not "nested", and telling a user their board
 /// sits inside a repository when the honest answer is "couldn't check" would be a lie dressed as
@@ -63,7 +63,7 @@ public enum BoardGitMode: String, Sendable, Equatable, CaseIterable {
     /// was **denied** (`EACCES`/`EPERM`) rather than answered — the sandbox refusing to say whether
     /// an ancestor above its grant carries a repository (06 ▸ Rules ▸ Detection, "Denial is not
     /// absence", ruled 2026-07-31). Structurally this takes `repoNested`'s posture: no add-git, no
-    /// app-managed git anywhere, `BoardSettingsSheet.resolve` empty — a denial can never be told
+    /// app-managed git anywhere, `BoardGitSetupSection.resolve` empty — a denial can never be told
     /// apart from a repository actually being there, so the conservative posture is the only honest
     /// one. Its prose is its own: the popover explains that Lanework could not verify whether the
     /// board sits inside a repository, never the `repoNested` sentence verbatim — denial is not