Overview

Adopt Brain's shared banner/navigation in scripts/board.py. Place logo/banner then navigation cards, then freshness/context and content; preserve owner-supplied counts, existing anchors/actions, semantics and identity. Count-free links are valid.

Plan

• Use the shared Brain component, retaining owner-specific navigation and evidence.
• Run repo tests and responsive/keyboard checks, then verify publication through existing workflows.
• Tier: judge — merge mode: human /prm (explicitly invoked for this execution turn).

Detailed implementation

Files: scripts/board.py. Add stable section destinations as needed; replace duplicate top stats/card styling with hero(..., navigation=items). Add focused renderer tests; all card targets must exist. Preserve data and action contracts. The shared Brain base is PR #464; merge it first. Proposed branch feature/board-navigation-memory; isolated worktree .worktrees/board-navigation-memory/PyAutoMemory. Canonical checkout on main; no active claim conflicts. Eyes' untracked files are excluded from task worktrees.

Original prompt

Adopt shared board navigation in PyAutoMemory

Type: feature
Target: PyAutoMemory
Repos:

• PyAutoMemory
  Difficulty: medium
  Autonomy: supervised
  Priority: normal
  Status: formalised
  Consequence: judge
  Filed: 2026-10-05

Approved scope

Adopt Brain's shared banner/navigation in scripts/board.py. Place logo/banner then navigation cards, then freshness/context and content; preserve owner-supplied counts, existing anchors/actions, semantics and identity. Count-free links are valid.

Approved as part of standard_board_banner_and_navigation.md by the user's “sounds good, go $prm”. Depends on PyAutoBrain PR #464; do not merge before that base. Validate the full applicable repo suite plus renderer link/header tests and five-width light/dark browser checks. Preserve copy/disclosure behavior and feed contracts. Existing regeneration/publication must be verified separately from source merge. Tier judge; user explicitly authorized /prm in the active execution turn. No scientific release or compute submission.

Original user request (verbatim)

I like the Ears format, we have the banner and logo at the top, but then remove "STALE — refresh required before judging the queue" which is unclear text. Then it has the big buttons under it with all the individual tabs you can go to and click. I want every board to now adopt this format, you prob cant always put numbers in a tbutton but thats fine, its a nice API and standarizes all boards which is a severely lacking aspect