Feat(abctl): also bind b/f for paging; label footer "[b/f] page"

Mac laptops have no dedicated Page Up/Down keys (they're fn+↑/fn+↓), so
route the less/vim-style b (page up) and f (page down) through the same
pager as PgUp/PgDn — uniform one-row overlap on every keyboard — and show
"[b/f] page" in the events footer instead of the ⇞⇟ glyphs, which aren't
obvious on a laptop. Extends the page-nav test to cover b/f.

Assisted-By: Claude (Anthropic AI) <noreply@anthropic.com>
Signed-off-by: Hai Huang <huang195@gmail.com>

Author: huang195

authbridge/cmd/abctl/tui/events_pane_test.go

@@ -41,6 +41,16 @@ func TestPageActivePane_EventsTable(t *testing.T) {
 	if got := m.eventsTbl.Cursor(); got != 0 {
 		t.Errorf("PgUp back to top: cursor=%d, want 0", got)
 	}
+
+	// b/f (the keys shown in the footer, work on any keyboard) page the same way.
+	m.pageActivePane(tea.KeyMsg{Type: tea.KeyRunes, Runes: []rune("f")})
+	if got := m.eventsTbl.Cursor(); got != h-1 {
+		t.Errorf("f (page down) from top: cursor=%d, want %d", got, h-1)
+	}
+	m.pageActivePane(tea.KeyMsg{Type: tea.KeyRunes, Runes: []rune("b")})
+	if got := m.eventsTbl.Cursor(); got != 0 {
+		t.Errorf("b (page up) back to top: cursor=%d, want 0", got)
+	}
 }
 
 // TestShortPhase covers the rendered string for every SessionPhase.

authbridge/cmd/abctl/tui/keys.go

@@ -273,12 +273,13 @@ func (m *model) handleKey(msg tea.KeyMsg) tea.Cmd {
 		m.goBottom()
 		return nil
 
-	case "pgup", "pgdown", "pgdn":
+	case "pgup", "pgdown", "pgdn", "b", "f":
 		// Page the active pane. Sessions can hold up to session.max_events
-		// (500) rows, so one-row-at-a-time nav isn't enough. Explicit here
-		// (rather than relying on the table component's own binding) so the
-		// page size carries a one-row overlap for context and the detail
-		// viewport pages too.
+		// (500) rows, so one-row-at-a-time nav isn't enough. b/f (less/vim
+		// style) work on any keyboard; PgUp/PgDn map to fn+↑/fn+↓ on Mac
+		// laptops. Explicit here (rather than the table component's own
+		// binding) so all of them share a one-row overlap for context and the
+		// detail viewport pages too.
 		return m.pageActivePane(msg)
 
 	case "P":
@@ -403,7 +404,7 @@ func (m *model) goBottom() {
 // panes (namespaces/pods) never reach here; they return early in handleKey
 // and page via their own component's binding.
 func (m *model) pageActivePane(msg tea.KeyMsg) tea.Cmd {
-	up := msg.String() == "pgup"
+	up := msg.String() == "pgup" || msg.String() == "b"
 	page := func(t *table.Model) {
 		n := t.Height() - 1
 		if n < 1 {
@@ -459,7 +460,7 @@ func (m *model) helpView() string {
 		if m.hideInactive {
 			skipHint = "[s] show all"
 		}
-		base := "[↑↓] nav  [⇞⇟] page  [↵] detail  [esc] back  [/] filter  " + skipHint + "  [p] pause  [q] quit"
+		base := "[↑↓] nav  [b/f] page  [↵] detail  [esc] back  [/] filter  " + skipHint + "  [p] pause  [q] quit"
 		// Surface the hidden-message count so a filtered timeline doesn't
 		// look like data loss. Only annotate when hiding is on AND at
 		// least one message was hidden.