Skip to content

Brand: the amber keycap mark, an org logo, and a demo that lets the reader keep up - #84

Merged
arpanghoshal merged 1 commit into
mainfrom
brand/amber-mark-and-paced-demo
Sep 6, 2026
Merged

Brand: the amber keycap mark, an org logo, and a demo that lets the reader keep up#84
arpanghoshal merged 1 commit into
mainfrom
brand/amber-mark-and-paced-demo

Conversation

@arpanghoshal

Copy link
Copy Markdown
Contributor

What changes

Colour. Grey → amber, #F5A623 with a #B8730A edge. It reads as a hold light on a control panel, and it sits beside the red BLOCKED lines without competing.

Mark. Same idea, a CTRL keycap with the run triangle, redrawn as a solid cap with a visible lower edge and the triangle cut out of it. Holds up at 16 px and as an avatar.

  • docs/assets/wordmark-light.svg / wordmark-dark.svg: the README uses a <picture> so GitHub swaps them with the viewer's theme. wordmark.svg self-adapts via a media query.
  • docs/assets/logo.svg, logo.png (1024, transparent), logo-on-dark.png: the organisation logo.
  • favicon.svg, social-preview.svg + PNG re-rendered, social-preview.md updated.

The README recording. The demo prints everything in one paint; the tape now pipes it through a while read loop that releases a line every 0.7 s, typed in the open beside the sed that ends it, and the tape's comment says exactly what is set up off screen (the loop, nothing else). The recording covers the first two scenarios and holds on the approval that was bound to one action and refused for another. 18.5 s.

The browser demo. docs/try-it.js reveals one line at a time, refusals in red. Verified in a headless browser against the real script with Pyodide stubbed to return a genuine transcript.

Mintlify. docs.json points at the per-theme wordmarks and the amber palette; docs/images/ carries the assets; the Try-it button is amber.

Tests

tests/test_readme_assets.py: the recording's last line is scenario 2's refusal, remote refund calls: 1 is still on screen, the only hidden setup is the pacing loop, the demo never runs off screen, both wordmarks exist and the README uses both, and docs/images/ has not drifted from docs/assets/. Full suite: 3784 passed, 45 skipped.

By hand after merge

  • Upload docs/assets/logo.png as the GitHub organisation avatar.
  • Re-upload docs/assets/social-preview.png under repository settings → Social preview.

…eader keep up

The wordmark, favicon and social preview move from grey to amber, #F5A623 with a
#B8730A edge: the colour of a hold light on a control panel. The mark keeps its
idea, a CTRL key with the run triangle, but is now a solid keycap with a visible
lower edge and the triangle cut out of it, so it survives at 16 px and as an
avatar. Light and dark wordmarks ship as separate files and the README picks one
per theme; docs/assets/logo.{svg,png} is the organisation logo, uploaded by hand.

The README recording no longer prints the demo in one paint. A while-read loop
releases a line every 0.7 s, typed in the open beside the sed that ends it, and
the recording now covers the first two scenarios, ending on the approval that was
bound to one action and refused for another. The browser demo on the Try-it page
does the same: one line at a time, refusals in red.

Mintlify follows: per-theme logos, the amber palette, and the Try-it button.
@mintlify

mintlify Bot commented Sep 6, 2026

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
ctrlrun 🟢 Ready View Preview Sep 6, 2026, 12:38 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

@arpanghoshal
arpanghoshal merged commit 7e725e2 into main Sep 6, 2026
8 checks passed
@arpanghoshal
arpanghoshal deleted the brand/amber-mark-and-paced-demo branch September 6, 2026 12:45
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