Skip to content

test(study): the orchestrator's card wears the Librarian portrait - #43

Merged
aaroncoville merged 1 commit into
theme/sixth-historyfrom
fix/sixth-mark-test
Oct 8, 2026
Merged

aaroncoville merged 1 commit into
theme/sixth-historyfrom
fix/sixth-mark-test

Conversation

@aaroncoville

Copy link
Copy Markdown
Owner

The study-scene test still expected the orchestrator card to carry the House logo. The portrait was deliberately switched to the Librarian's own portrait in #41, and that commit updated the other three portrait tests but missed this assertion.

Test-only change: the god card's portrait is now asserted as portraits/fascination.png, and houseMark is still asserted true (AgentCard still uses the flag to pick the portrait). Mutations that deal the god a worker's face, or drop houseMark, turn it red.

Suite: 1701/1703, 0 failing (base: 1 failing).

The scene test for the orchestrator's card failed on every run. It
still expected the Sixth History logo with the square House-mark
treatment, but the orchestrator's portrait had since moved to the
reserved Librarian portrait (fascination.png, cropped like any other
portrait). That change updated the portrait and face tests and missed
this one.

The code is right and the test was stale. It now asserts the card is
dealt the Librarian portrait and is still flagged as the
orchestrator's, the flag the card uses to choose that portrait itself.
Dealing the orchestrator a worker's face, or dropping the flag from the
scene, turns it red.
@github-actions

github-actions Bot commented Oct 8, 2026

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

@aaroncoville
aaroncoville merged commit d33ace4 into theme/sixth-history Oct 8, 2026
1 check failed
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