Skip to content

feat: adopt shared board section navigation #4

Closed

Description

@Jammy2211

Overview

Adopt Brain's shared banner/navigation in insight/board.py, insight/theme.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. Adapt independent renderer to shared header/card sizing; preserve gallery/table behavior and fix container overflow needed for responsive adoption. Preserve existing local untracked files.

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: insight/board.py, insight/theme.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-insight; isolated worktree .worktrees/board-navigation-insight/PyAutoInsight. Canonical checkout on main; no active claim conflicts. Eyes' untracked files are excluded from task worktrees.

Original prompt

Adopt shared board navigation in PyAutoInsight

Type: feature
Target: PyAutoInsight
Repos:

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

Approved scope

Adopt Brain's shared banner/navigation in insight/board.py, insight/theme.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. Adapt independent renderer to shared header/card sizing; preserve gallery/table behavior and fix container overflow needed for responsive adoption. Preserve existing local untracked files.

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

Activity

  1. Jammy2211 commented on Oct 5, 2026

    @Jammy2211
    ContributorAuthor

    Implementation and local validation complete: #5

    77 passed in 1.99s. Browser checks passed across five widths and both themes. Heart GREEN. Awaiting every CI leg before the user-authorized merge.

  2. Jammy2211 commented on Oct 5, 2026

    @Jammy2211
    ContributorAuthor

    Shared banner and navigation: PyAutoInsight

    Merged #5 (20772fc), closing #4.

    The board now uses the shared logo banner followed immediately by prominent section links. Counts remain optional and owned by this board. Existing evidence, freshness safeguards and action payloads are preserved.

    Validation: 77 passed in 1.99s; ten viewport/theme browser cases; all workflow runs and every CI job on d4ebffa succeeded. Heart GREEN, 100, at 2026-10-05T17:25:39Z.

    Local evidence: tmp/board-navigation/ (test logs, CI verdict and renders/PyAutoInsight/ browser screenshots).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions