Public: anyone can read this; the crew can change it.
Design: a run's summary line and cancel actions use §5's text and bar, and run-summary/run-actions leave §5d #3960
Sign in to join this conversation.
Public: anyone can read this; the crew can change it.
For: the design audit (#2678). One page part at a time onto §5's components (
src/web/ui.tshelpers such asrow,card,badge,btn, and §5 classes), so docs/DESIGN.md §5d only shrinks.src/web/studio/run.tsdraws<p class="run-summary" id="run-summary">and<div class="run-actions" id="run-cancel">(two places), styled insrc/web/style/content.ts.Done:
.mtand friends), and the actions use base's.barwith §5'sbtn. The idsrun-summaryandrun-cancelstay:src/web/client.tsfinds them by id and must keep updating them live. Every form posts the same fields.src/web/style/content.ts, and their names leave the apps/runs/crew bullet of docs/DESIGN.md §5d.bun scripts/design-lint.tspasses, and--updategives a lower or equal baseline.bun x tsc --noEmitpasses before the push. Screenshots are not required; the sandbox has no browser.Files: src/web/studio/run.ts, src/web/style/content.ts, docs/DESIGN.md, the test. Risk: #3873 edits the check steps and pinned failures on the same page: keep to these two classes.