Skip to content

Study: the Librarian card keeps its own portrait - #31

Merged
aaroncoville merged 1 commit into
theme/sixth-historyfrom
fix/sixth-history-librarian-portrait
Sep 28, 2026
Merged

aaroncoville merged 1 commit into
theme/sixth-historyfrom
fix/sixth-history-librarian-portrait

Conversation

@aaroncoville

Copy link
Copy Markdown
Owner

The Librarian's Study card goes back to its own portrait.

The square house mark on the rectangular card read wrong in the live run. The card now uses the reserved pre-#27 portrait asset (assets/portraits/fascination.png), narrowed at the card's final seam only: portraitFor({ isGod: true }) still returns the house mark for the small shared avatars, and packaged icons, Focus and other branding are untouched.

Scope: AgentCard.tsx and its test. The regression was written red against the square mark first; focused suite 65 pass, typecheck, production build and diff-check clean.

@aaroncoville
aaroncoville merged commit 59893db into theme/sixth-history Sep 28, 2026
@github-actions

Copy link
Copy Markdown

🚫 This PR is missing its before/after evidence

Every pull request here has to show its work. Screenshots or a short screen recording, before the change and after it.

  • Before — no image or video under that heading
  • After — no image or video under that heading

How to fix it: edit the description, keep the ### Before and ### After headings from the template, and drag an image or video under each. GitHub uploads it inline. This check re-runs the moment you save.

A bug fix with no visible surface still needs it: show the failing behaviour, then the same steps passing. A terminal recording is fine.

Genuinely nothing to show — a CI tweak, a typo, a dependency bump? A maintainer can apply the no-visual-change label. Please don't ask unless it truly has no observable effect.

📖 CONTRIBUTING.md → Evidence is mandatory

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant