Skip to content

Sixth History skin: dark treatment for the Librarian tab and CLI, house mark on the Librarian card - #29

Merged
aaroncoville merged 2 commits into
theme/sixth-historyfrom
fix/sixth-history-dark-surfaces
Sep 28, 2026
Merged

aaroncoville merged 2 commits into
theme/sixth-historyfrom
fix/sixth-history-dark-surfaces

Conversation

@aaroncoville

Copy link
Copy Markdown
Owner

Second pass on the Sixth History skin after the first live run.

The Librarian card keeps the house mark. The Study AgentCard now pins the licensed Sixth History mark whenever houseMark is true, overriding any stale caller portrait, so the card matches every other surface.

The Librarian tab and the CLI take the scene's dark treatment. The paper-toned aubergine surfaces are gone. The command-center subtree and the live CLI host are scoped to the Study's deepest night ramp; xterm and Monaco move from raised #352531 to scene ground #120F1B (recessed #0F0C17). Contrast on #120F1B: primary 14.41:1, secondary 10.26:1, tertiary 5.98:1, gilt 7.82:1, structural boundary 3.99:1; primary on recessed 14.74:1.

Files: AgentCard.tsx, CommandCenterPanel.tsx, PtyTerminalView.tsx, occult-tokens.css, occultTerminal.ts, three focused tests. Verification: focused occult/polish/card/scene/face suite 58/58, typecheck, build and diff-check pass. Visual verification in the running app is still needed after a pull and restart; no scene-room files are touched, so this sits cleanly on top of #28.

@aaroncoville
aaroncoville merged commit 94cada9 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