that had been lightened, which is a mismatch you can only see on the raw view. Whenever a rule up there names one of a pair, check it did not drop the other. */ pre.raw, code.raw { background: #33373f !important; color: #d4d4d4 !important; border-radius: 6px; /* A
 renders a tab at the browser default of 8 characters. film.php is tab-indented
     and deeply nested, which is why it read as enormous indentation rather than as code. */
  -moz-tab-size: 2;
  tab-size: 2;
}

/* ---- the gutter ------------------------------------------------------------------------
   A shade under the slab so it reads as a gutter without a rule between them. The numerals
   are #868e9c, not Dark Modern's own #6e7681: that measures 2.92:1 on this background, which
   is faint by design in an editor but is the same too-light-to-read problem already fixed
   once on Commits/Branches/Releases. #868e9c is 4.07:1 and still recedes from the code. */
/* Fill and rule go on the CELL only. The markup is a single  holding
   one stacked  per line — so setting border-right/border-radius on the spans
   too draws a rule segment and a rounded corner on every individual line. */
.repository.file.list #file-content .code-view .lines-num,
.repository .diff-file-box .file-body.file-code .lines-num {
  background: #2c3038 !important;
  border-right: 1px solid #434855 !important;
  border-radius: 6px 0 0 6px;
}
.repository.file.list #file-content .code-view .lines-num,
.repository.file.list #file-content .code-view .lines-num pre,
.repository.file.list #file-content .code-view .lines-num span,
.repository .diff-file-box .file-body.file-code .lines-num {
  color: #868e9c !important;
}

/* ---- tokens: Dark Modern / Dark+ -------------------------------------------------------
   Contrast on #2b2f37, lowest first: comment 4.03:1, keyword 4.55:1, string 5.08:1,
   body text 9.06:1. Nothing here lands under 4:1. */
.hljs                                                 { background: transparent !important; color:#d4d4d4 !important; }
.hljs-comment, .hljs-quote                            { color:#6a9955 !important; font-style: italic; }
.hljs-keyword, .hljs-selector-tag, .hljs-literal      { color:#569cd6 !important; }
/*  markers, 100 of them on film.php — grey so they punctuate rather than
   compete with the code they wrap. */
.hljs-meta                                            { color:#9b9b9b !important; }
.hljs-string, .hljs-doctag                            { color:#ce9178 !important; }
.hljs-number, .hljs-subst                             { color:#b5cea8 !important; }
/* Function names. In v11 these arrive as class=\"hljs-title function_ invoke__\"; the
   attribute is a LIST, so .hljs-title still matches. */
.hljs-title, .hljs-section                            { color:#dcdcaa !important; }
/* hljs-name is the TAG name in xml/php-template, not a function — blue, per Dark Modern.
   It was folded in with hljs-title above, which was harmless only while the php grammar
   never emitted it. Now that php-template tokenises the HTML it is 73 tokens on film.php
   alone, and yellow would paint every  as if it were a function call. */
.hljs-name                                            { color:#569cd6 !important; }
.hljs-type, .hljs-class .hljs-title, .hljs-built_in,
.hljs-builtin-name                                    { color:#4ec9b0 !important; }
.hljs-variable, .hljs-template-variable, .hljs-attr,
.hljs-attribute, .hljs-params                         { color:#9cdcfe !important; }
.hljs-symbol, .hljs-bullet, .hljs-link                { color:#4fc1ff !important; }
.hljs-regexp                                          { color:#d16969 !important; }
.hljs-selector-class                                  { color:#d7ba7d !important; }
.hljs-selector-id                                     { color:#d7ba7d !important; }
.hljs-tag                                             { color:#9b9b9b !important; }  /* angle brackets, 4.83:1 */
.hljs-formula                                         { color:#d4d4d4 !important; }
.hljs-emphasis                                        { font-style: italic; }
.hljs-strong                                          { font-weight: 700; }

/* ---- diffs -----------------------------------------------------------------------------
   Row fills as tints OF the slab, not replacements for it, so the token colours above stay
   on a predictable ground inside changed lines. */
.repository .diff-file-box .code-diff tbody tr.del-code td,
.repository .diff-file-box .code-diff tbody tr .removed-code {
  background: #3f2b2e !important; color:#d4d4d4 !important;
}
.repository .diff-file-box .code-diff tbody tr.add-code td,
.repository .diff-file-box .code-diff tbody tr .added-code {
  background: #2c3a2c !important; color:#d4d4d4 !important;
}
.hljs-addition { background:#2c3a2c !important; color:#b5cea8 !important; }
.hljs-deletion { background:#3f2b2e !important; color:#f48771 !important; }

/* Borders inside the slab have to darken with it — the light-panel #c0c0c0 would draw a grid. */
.repository.file.list #file-content .code-view table td,
.repository.file.list #file-content .code-view table tr {
  border-color: #434855 !important;
}

/* ==========================================================================================
 * SECTION MARK — 2026-08-17
 *
 * "Code" beside the Gogs navbar logo rather than as a standalone  over the panel. The
 * main site does the latter (/desk/ renders 
Desk above its
 * .entry-content), but reproducing that here added a row of height and pushed the content
 * area down. In the brand link it costs no vertical space.
 *
 * It sits INSIDE , so it has to out-specify
 * `.following.bar .top.menu a.item.brand`, which is itself !important.
 *
 * FONT PATH — the reason this is under css/fonts/ and not fonts/:
 *   Gogs does not serve the whole of custom/public. It mounts a fixed set of top-level
 *   prefixes, and a new directory at the top level is simply not routed — custom/public/
 *   fonts/cmunsx.woff returns 404 while the identical file under css/fonts/ returns 200,
 *   verified against :3000 directly with nginx out of the path. Nesting it under an already
 *   -served prefix is the whole fix. Anything else added later (icons, images) needs the
 *   same treatment.
 * ======================================================================================== */

@font-face {
  font-family: 'CM Sans';
  font-style: normal;
  font-weight: 400;
  /* Relative to this stylesheet at /code/css/themes/, so it survives a change of subpath.
     local("☺") is the main site's own idiom: a family name no installed font can match,
     which forces the download instead of silently resolving to something local. */
  src: local("☺"), url(../fonts/cmunsx.woff) format("woff");
}

.daw-code-mark {
  margin-left: .55rem;
  font-family: 'CM Sans', 'DAW Playfair', Georgia, serif;
  font-size: 1.35rem;
  font-weight: 400;
  line-height: 1;
  vertical-align: middle;
  /* #dadada is the content panel's own colour — 6.14:1 on the bar's #484c57, and it ties the
     mark to the thing it labels rather than introducing a third value. */
  color: #dadada !important;
}

.following.bar .top.menu a.item.brand:hover .daw-code-mark {
  color: rgba(196, 45, 45, .95) !important;   /* follow the bar's existing hover */
}

/* ==========================================================================================
 * COMMIT PAGE SURFACES — 2026-08-17
 *
 * The commit box is , and the rule that
 * paints it is:
 *
 *     .ui .info.segment.top { background: #0b0b0b !important }        <- four classes
 *
 * The panel's own neutraliser is `.repository .ui.segment` — three classes. Both carry
 * !important, so SPECIFICITY decides and the near-black wins no matter how much later in the
 * file the panel rule sits. That is why this one survived the Semantic-surfaces sweep: that
 * sweep assumed source order was enough, which holds only while the rules it fights are of
 * equal or lower specificity. Selectors below are deliberately five classes.
 *
 * The SECOND box on the page, , has no `top` class, so
 * it never matched the near-black rule and was already transparent — which is why only the
 * upper half of the commit header looked wrong.
 *
 * The earlier version of this block made .commit-message a deliberate #33373f slab to match
 * the code view. Reverted: commit text is prose, not code, and belongs on the panel with the
 * rest of the page furniture.
 * ======================================================================================== */

.repository .ui.info.segment.top,
.repository .ui.top.attached.info.segment,
.repository .ui.attached.info.segment {
  background: transparent !important;
  color: #33373f !important;
}

.repository.diff .commit-message,
.repository.diff .commit-message pre,
.repository.diff .commit-message h3 {
  background: transparent !important;
  color: #33373f !important;
  -moz-tab-size: 2;
  tab-size: 2;
}
.repository.diff .commit-message a { color: #67000a !important; }
.repository.diff .commit-message a:hover { color: #0f7a63 !important; }

/* ==========================================================================================
 * NESTED CELL FILLS — 2026-08-17
 *
 * The theme paints the  INSIDE each code cell as well as the cell itself:
 *
 *     .code-view .lines-code pre  ->  #1c2025      (never re-listed by any later block)
 *     .code-view .lines-num  pre  ->  #1c2025      (later overridden to a LIGHT tint)
 *
 * So setting a colour on .lines-code / .lines-num alone changes nothing you can see — the
 * child covers the parent. That is why the code view still read as near-black after the slab
 * was set to #33373f, and why the gutter had a pale strip over a dark cell: the two nested
 * rules were caught by different blocks and ended up disagreeing.
 *
 * Fixed by making the nested elements transparent rather than by colouring them, so the cell
 * rules above are the single place the code view's colour is decided.
 * ======================================================================================== */

/* The selector list below MIRRORS the theme rule exactly, including the .hljs variants.
   That is deliberate. A near-miss does not work here: both rules are !important, so
   specificity decides, and `.lines-code .hljs` is six classes against five-classes-plus-an-
   element for `.lines-code code` — the theme rule wins on class count. highlight.js puts
   `hljs` on the  element, so that is the one that actually paints the code. Matching
   the list makes them tie, and source order settles it. */
.repository.file.list #file-content .code-view .lines-num pre,
.repository.file.list #file-content .code-view .lines-code pre,
.repository.file.list #file-content .code-view .lines-num ol,
.repository.file.list #file-content .code-view .lines-code ol,
.repository.file.list #file-content .code-view .lines-num .hljs,
.repository.file.list #file-content .code-view .lines-code .hljs,
.repository.file.list #file-content .code-view .lines-code code,
.repository .diff-file-box .file-body.file-code .lines-code pre,
.repository .diff-file-box .file-body.file-code .lines-num pre {
  background: transparent !important;
}

/* ==========================================================================================
 * CONTRIBUTIONS CARD — 2026-08-17
 *
 * A surface behind the whole component — heading included — in the page ground #484c57. On the
 * #dadada panel that reads as a deliberate inset rather than a tint, and it needs no border to
 * separate it, which is why there is none.
 *
 * THE RAMP HAD TO INVERT WITH IT. The panel block above runs the levels PALE -> DARK
 * (#c3cdc0 to #486b43) because they sat on a light ground. On #484c57 that ordering puts the
 * busiest days closest to the card colour and the quietest days furthest from it — the scale
 * reads backwards. These restore the muted #97b094 ramp built for the dark ground, by opacity
 * so the four steps stay one hue.
 *
 * Empty days are darker than the card, not lighter: a quiet day should recede into the surface
 * rather than register as a faint mark of its own.
 * ======================================================================================== */

.daw-activity {
  background: #484c57;
  border-radius: 6px;
  padding: 1rem 1.1rem;
}

/* Levels re-stated at the SAME specificity as the panel block (two classes + an element) and
   later in the file, so source order decides. Matching it is deliberate — going higher would
   work too, but then anything editing the panel block later would silently stop having an
   effect here with no clue why. */
.daw-activity-grid i.lvl0 { background: rgba(0,0,0,.16)          !important; }
.daw-activity-grid i.lvl1 { background: rgba(151,176,148,.30)    !important; }
.daw-activity-grid i.lvl2 { background: rgba(151,176,148,.55)    !important; }
.daw-activity-grid i.lvl3 { background: rgba(151,176,148,.80)    !important; }
.daw-activity-grid i.lvl4 { background: #97b094                  !important; }
.daw-activity-grid i.lvl5 { background: #bcd4b8                  !important; }

/* The heading was #6b7268 for the light panel — 1.6:1 here. #c2c7d0 is 5.06:1 on #484c57. */
.daw-activity .daw-activity-head { color: #c2c7d0 !important; }

/* ==========================================================================================
 * REPO LIST — NAME SIZE — 2026-08-17
 *
 * gogs.min.css sets `.ui.repository.list .item .ui.header { font-size: 1.5rem }`. Being in
 * rem it is measured against the ROOT, so it grew as a side effect of the
 * `html { font-size: 16px }` rule added earlier to make  match the main site:
 * 1.5 × 14px = 21px before, 1.5 × 16px = 24px after. Nothing about the repo list changed —
 * the reference it was sized against did.
 *
 * 1.15rem = 18.4px, which sits below where it started rather than merely undoing the growth.
 * The `.metas` (14px) and `.time` (12px) beneath it are absolute and were never affected, so
 * bringing the name down also restores the size relationship between the three.
 * ======================================================================================== */

.ui.repository.list .item .ui.header {
  font-size: 1.15rem !important;
}

/* ==========================================================================================
 * DIFF ROW TINTS — 2026-08-17
 *
 * Added/removed rows were showing no colour at all, and the cause is specificity again — the
 * third time tonight, in a different disguise.
 *
 *     slab   .repository .diff-file-box .file-body.file-code .lines-code        5 classes
 *     tints  .repository .diff-file-box .code-diff tbody tr.add-code td         4 classes
 *
 * Both !important, so the slab repainted every cell #33373f and erased the tints regardless
 * of order. Class count is compared before element count, so adding `tbody tr td` to the
 * tint selector could never win — more elements do not beat one more class.
 *
 * These name .lines-code/.lines-num explicitly, giving six classes, which clears the slab.
 *
 * The rows carry the state on the  (`add-code`, `del-code`, `same-code`, `tag-code`), so
 * the cells are tinted via the row rather than being classed themselves.
 *
 * Values are tints OF the slab, not replacements: #33373f -> #2f4030 shifts green and drops
 * blue, #452f33 lifts red. Subtle enough to read as a highlight behind code rather than as a
 * coloured band, which is what the old #6f3a3a / #b40000 pair did on the near-black theme.
 * ======================================================================================== */

.repository .diff-file-box .file-body.file-code tr.add-code td.lines-code,
.repository .diff-file-box .file-body.file-code tr.add-code td.lines-num {
  background: #2f4030 !important;
}
.repository .diff-file-box .file-body.file-code tr.del-code td.lines-code,
.repository .diff-file-box .file-body.file-code tr.del-code td.lines-num {
  background: #452f33 !important;
}

/* Intra-line (word-level) highlights sit ON the row tint, so they have to be a step stronger
   than it or they vanish into their own row. */
.repository .diff-file-box .file-body.file-code .added-code {
  background: #3d5a3d !important; color: #d4d4d4 !important;
}
.repository .diff-file-box .file-body.file-code .removed-code {
  background: #66393f !important; color: #d4d4d4 !important;
}

/* Hunk headers (@@ -15,6 +15,7 @@) — recede from both the code and the tinted rows. */
.repository .diff-file-box .file-body.file-code tr.tag-code td.lines-code,
.repository .diff-file-box .file-body.file-code tr.tag-code td.lines-num {
  background: #2a2d34 !important;
}
.repository .diff-file-box .file-body.file-code tr.tag-code td.lines-code code {
  color: #9b9b9b !important;
}

/* ==========================================================================================
 * BUTTONS AND MENUS INSIDE THE PANEL — 2026-08-17
 *
 * Logged-out pages never render these, which is why they survived every pass tonight: the
 * New File / Upload File pair, the Open/Closed filter on issues and pulls, and the dashboard's
 * tabable menu are all behind authentication.
 *
 * Specificity of what they have to beat, measured rather than assumed:
 *
 *     .ui.button                        (0,2,0)  #2F435C
 *     .ui.basic.button                  (0,3,0)  #272c34
 *     .ui.blue.button                   (0,3,0)  #33363D
 *     .ui.blue.buttons .button          (0,4,0)  #33363D
 *     .ui.basic.buttons .button         (0,4,0)  #272c34
 *     .ui.menu.three.item .item         (0,5,0)  #272c34
 *     .ui.menu .ui.dropdown .menu>.item (0,6,0)  #272c34
 *
 * Every selector below is scoped by a page-type class, which buys exactly one class of
 * specificity — enough for the buttons, and the menus are given a second where they need it.
 *
 * NOTE: these could not be checked in a browser from here, since reaching them needs a login.
 * They are verified by resolving the cascade instead, which is what caught the three earlier
 * misses tonight anyway.
 * ======================================================================================== */

/* Neutral buttons — the default and `basic` variants. */
.repository .ui.button, .dashboard .ui.button, .explore .ui.button,
.user.profile .ui.button, .organization .ui.button, .admin .ui.button,
.repository .ui.basic.button, .dashboard .ui.basic.button, .explore .ui.basic.button,
.user.profile .ui.basic.button, .organization .ui.basic.button, .admin .ui.basic.button,
.repository .ui.basic.buttons .button, .dashboard .ui.basic.buttons .button,
.explore .ui.basic.buttons .button, .admin .ui.basic.buttons .button {
  background: #e6e6e6 !important;
  border: 1px solid #c0c0c0 !important;
  box-shadow: none !important;
  color: #33373f !important;          /* 9.57:1 */
}
.repository .ui.button:hover, .dashboard .ui.button:hover, .explore .ui.button:hover,
.user.profile .ui.button:hover, .organization .ui.button:hover, .admin .ui.button:hover,
.repository .ui.basic.button:hover, .dashboard .ui.basic.button:hover,
.explore .ui.basic.button:hover, .admin .ui.basic.button:hover,
.repository .ui.basic.buttons .button:hover, .dashboard .ui.basic.buttons .button:hover {
  background: #dcdcdc !important;
  color: #67000a !important;          /* 10.64:1 */
}

/* Primary actions. Semantic paints these `blue`; New File / Upload File are
   `.ui.tiny.blue.buttons`. Filled in the site red rather than neutralised, because they are
   the primary action on the page and a flat grey would lose that. */
.repository .ui.blue.button, .repository .ui.blue.buttons .button,
.dashboard .ui.blue.button, .dashboard .ui.blue.buttons .button,
.admin .ui.blue.button, .admin .ui.blue.buttons .button,
#file-buttons.ui.blue.buttons .button {
  background: #67000a !important;
  border: 1px solid #67000a !important;
  color: #f2f2f2 !important;          /* 13.28:1 */
}
.repository .ui.blue.button:hover, .repository .ui.blue.buttons .button:hover,
.dashboard .ui.blue.buttons .button:hover, #file-buttons.ui.blue.buttons .button:hover {
  background: #4f0008 !important;
  border-color: #4f0008 !important;
  color: #ffffff !important;
}

/* The selected filter on issues / pulls is `.ui.red.active.basic.button` — it has to stay
   visibly distinct from the unselected one, so it takes the fill rather than the outline. */
.repository .ui.red.active.basic.button, .repository .ui.active.basic.button,
.repository .ui.red.button {
  background: #67000a !important;
  border: 1px solid #67000a !important;
  color: #f2f2f2 !important;
}

/* Menus: the dashboard's `.ui.three.item.tabable.menu` and the vertical menus beside it.
   Two page-type classes are NOT needed here — one is enough against (0,5,0), but the item
   rules go to (0,6,0) to clear `.ui.menu .ui.dropdown .menu > .item`. */
.dashboard .ui.menu, .dashboard .ui.tabable.menu, .dashboard .ui.vertical.menu,
.user.profile .ui.menu, .organization .ui.menu, .repository .ui.menu, .admin .ui.menu {
  background: transparent !important;
  border-color: #c0c0c0 !important;
  color: #33373f !important;
}
.dashboard .ui.menu.three.item .item, .dashboard .ui.menu.two.item .item,
.dashboard .ui.tabable.menu .item, .dashboard .ui.vertical.menu .item,
.organization .ui.menu.two.item .item, .repository .ui.menu .item {
  background: transparent !important;
  color: #33373f !important;
}
.dashboard .ui.menu.three.item .item.active, .dashboard .ui.tabable.menu .item.active,
.dashboard .ui.vertical.menu .active.item, .repository .ui.menu .item.active {
  background: #dadada !important;
  color: #67000a !important;
}

/* ==========================================================================================
 * SETTINGS / FORM INK — 2026-08-17
 *
 * The settings pages are behind a login, so none of the earlier passes saw them. Measured
 * against the #dadada panel, the dark theme's type colours land here:
 *
 *     h1..h5, .ui.header, .ui.input input, .ui.button:not(.label)   #e9c062   1.23:1
 *     .ui.checkbox label, .ui.card, .secondary .item                silver    1.30:1
 *     .ui .text.black                                               #d3d3d3   1.07:1
 *
 * #e9c062 is a sand yellow — it was the heading colour on the near-black ground and is close
 * to invisible on a light panel. Everything here is a leftover of that ground, not a choice.
 *
 * The competitors are weak (bare elements at (0,0,1), two- and three-class selectors), so a
 * page-type scope is enough to clear them without !important escalation in most cases. It is
 * applied anyway for consistency with the rest of this file.
 * ======================================================================================== */

/* Headings. The panel block already covers h1-h3 for three wrappers; h4/h5/h6 and .ui.header
   were never in it, which is most of a settings page's structure. */
.repository h1, .repository h2, .repository h3, .repository h4, .repository h5, .repository h6,
.repository .ui.header, .repository .ui.header .content,
.admin h1, .admin h2, .admin h3, .admin h4, .admin h5, .admin .ui.header,
.organization .ui.header, .user.profile .ui.header, .dashboard .ui.header {
  color: #2f333c !important;          /* 8.24:1 */
}

/* Form furniture: labels, checkbox text, plain body copy in the settings panes. */
.repository label, .repository .ui.form label, .repository .ui.checkbox label,
.repository .ui.checkbox + label, .repository .ui.card, .repository .text,
.repository .ui.list .item, .repository .secondary .item,
.admin label, .admin .ui.form label, .admin .ui.checkbox label, .admin .ui.list .item,
.organization label, .organization .ui.form label {
  color: #33373f !important;          /* 9.06:1 */
}

/* Help text under a field should recede but stay readable — #565c69 is 4.81:1, where the
   #5c6270 that looks right on screen measures 4.37:1 and fails. */
.repository .help, .repository .ui.form .help, .repository .note,
.admin .help, .organization .help {
  color: #565c69 !important;
}

/* Inputs and textareas. The dark theme fills these #555966 with light text; on the panel they
   have to invert or the field looks like a hole. */
.repository .ui.form input:not([type]), .repository .ui.form input[type=text],
.repository .ui.form input[type=email], .repository .ui.form input[type=password],
.repository .ui.form input[type=url], .repository .ui.form input[type=number],
.repository .ui.form textarea, .repository .ui.input input, .repository textarea,
.admin .ui.form input[type=text], .admin .ui.input input, .admin .ui.form textarea {
  background: #f0f0f0 !important;
  border: 1px solid #c0c0c0 !important;
  color: #33373f !important;
}

/* `.ui .text.black` is the theme's own "make this dark" helper, set to #d3d3d3 for the dark
   ground — the exact inverse of what the name promises on a light one. */
.repository .ui .text.black, .admin .ui .text.black, .dashboard .ui .text.black {
  color: #33373f !important;
}
.repository .ui .text.black:hover, .admin .ui .text.black:hover {
  color: #67000a !important;
}

/* Settings sidebar — . */
.repository .ui.tab.active.list, .repository .ui.tab.active.list .item,
.repository .ui.tab.active.list a, .admin .ui.tab.active.list .item {
  background: transparent !important;
  color: #33373f !important;
}
.repository .ui.tab.active.list a:hover, .admin .ui.tab.active.list a:hover {
  color: #67000a !important;
}
.repository .ui.tab.active.list .item.active, .repository .ui.tab.active.list a.active {
  color: #67000a !important;
  font-weight: 600;
}

/* ==========================================================================================
 * ATTACHED HEADERS OUTSIDE .repository — 2026-08-17
 *
 * The dashboard's right column is
 *
 *     .six.wide.column > .ui.tab.active.list > .ui.top.attached.header
 *                                            > .ui.attached.table.segment
 *
 * The Semantic-surfaces sweep listed `.ui.attached.header` under `.repository` ONLY, while
 * `.ui.segment` and `.ui.table` were listed for every wrapper. So on the dashboard the panel
 * below the header went transparent and the header itself stayed #272c34 — which is exactly
 * how it looked: one dark bar sitting on top of a light list.
 *
 * The theme declares `.ui.attached.header` twice (#272c34 and #080705), both at three
 * classes, so a wrapper scope at four clears both.
 * ======================================================================================== */

.dashboard .ui.attached.header, .dashboard .ui.top.attached.header,
.dashboard .ui.attached.table, .dashboard .ui.attached.segment,
.organization .ui.attached.header, .organization .ui.top.attached.header,
.organization .ui.attached.table, .organization .ui.attached.segment,
.user.profile .ui.attached.header, .user.profile .ui.attached.table,
.explore .ui.attached.header, .explore .ui.attached.table,
.admin .ui.attached.header, .admin .ui.attached.table {
  background: transparent !important;
  border-color: #c0c0c0 !important;
  color: #2f333c !important;
}

/* The list rows beneath it, and the count chip in the header. */
.dashboard .repo-owner-name-list li, .dashboard .repo-owner-name-list a,
.dashboard .ui.tab.active.list .item, .organization .repo-owner-name-list a {
  background: transparent !important;
  color: #33373f !important;
}
.dashboard .repo-owner-name-list a:hover, .organization .repo-owner-name-list a:hover {
  color: #67000a !important;
}
.dashboard .ui.grey.label, .organization .ui.grey.label, .repository .ui.grey.label {
  background: #c6c6c6 !important;
  color: #33373f !important;
  border: none !important;
}
/* `.text.light.grey` is the star count at the right of each row — it has to recede from the
   repo name without dropping out of readability on the panel. */
.dashboard .text.light.grey, .dashboard .ui.right.text.light.grey,
.organization .text.light.grey {
  color: #565c69 !important;
}

/* ==========================================================================================
 * DASHBOARD REPO LIST — 2026-08-17
 *
 * The last dark surface, and the one that hid the longest:
 *
 *     .feeds .list ul            { background: #272c34 }     (0,2,1), NOT !important
 *     .feeds .list ul li.private { background: #272c34 }
 *
 * It only renders on the logged-in dashboard, and it matches through a coincidence of class
 * names: the page wrapper is , and Semantic's `.ui.tab.list`
 * carries a `list` class, so `.feeds .list ul` lands on the repository  in the right-hand
 * column without ever naming it.
 *
 * Worth noting for the remaining sweep: this pair carries no !important, so it never appeared
 * in the "dark !important surfaces" hunts — it won purely on specificity against rules that
 * did. Searching for `!important` alone will keep missing this class of leftover.
 *
 * `li.private` used the same value as the list, so private repos were marked by a border
 * alone. Given a light ground they can carry the tint the original intended.
 * ======================================================================================== */

.dashboard.feeds .list ul,
.dashboard .ui.tab.list ul,
.dashboard .ui.tab.active.list ul,
.organization.feeds .list ul {
  background: transparent !important;
}

.dashboard.feeds .list ul li.private,
.dashboard .ui.tab.list ul li.private,
.dashboard .ui.tab.active.list ul li.private {
  background: rgba(72,76,87,.07) !important;
}

/* ==========================================================================================
 * MARKDOWN TABLES — 2026-08-17
 *
 * The cells were black. The theme sets
 *
 *     .markdown:not(code) table th, .markdown:not(code) table td { background: #080705 }
 *
 * as ONE rule, and the light-panel block re-listed only `table th` — so `td` kept the
 * near-black. Fourth time tonight for that exact shape: a rule styling a pair, an override
 * naming one half. (pre.raw/code.raw, .lines-code/.hljs, th/td.)
 *
 * gogs.min.css already provides #fff rows with #f8f8f8 zebra striping, but the theme's `td`
 * painted straight over them, so the striping has never been visible. Restated here a touch
 * off pure white so the table reads as a surface on the #dadada panel rather than a hole.
 *
 * Hover is the page ground at .08 — a wash of the same blue-grey the site is built on, rather
 * than the light fill that was showing. Applied to the ROW with the cells transparent, so a
 * hovered row tints as one band instead of striping through the cells.
 * ======================================================================================== */

.markdown:not(code) table tr              { background: #fcfcfc !important; }
.markdown:not(code) table tr:nth-child(2n){ background: #f5f5f5 !important; }

.markdown:not(code) table th {
  background: #ebebeb !important;
  color: #2f333c !important;
  border-color: #d6d6d6 !important;
}
.markdown:not(code) table td {
  background: transparent !important;   /* let the row colour through */
  color: #33373f !important;
  border-color: #d6d6d6 !important;
}

.markdown:not(code) table tr:hover,
.markdown:not(code) table tr:nth-child(2n):hover {
  background: rgba(72,76,87,.08) !important;
}
.markdown:not(code) table tr:hover td,
.markdown:not(code) table tr:hover th {
  background: transparent !important;
}

/* ==========================================================================================
 * DROPDOWN POPUPS — 2026-08-17
 *
 * Two menus that no earlier pass reached, both only visible when signed in.
 *
 * 1. The avatar menu (Your Profile ... Sign Out). A light rule for it already existed —
 *    `.ui.dropdown .menu { background:#e6e6e6 !important }` at THREE classes — but it loses to
 *
 *        .ui.menu .right.menu .dropdown:last-child .menu   -> #272c34 !important
 *
 *    which is six classes plus :last-child, so seven. Same lesson as the rest of tonight: an
 *    !important light rule is not a fix if a darker rule is more specific. The selector is
 *    RESTATED verbatim below so the two tie and source order decides.
 *
 * 2. The dashboard context switcher (Switch Dashboard Context), which is
 *    `.context.user.overflow.menu`. Its background resolved light already, but this file sets
 *    `.overflow.menu .items .item { color: silver }` — overriding Gogs' own rgba(0,0,0,.8) —
 *    so the entries were near-invisible on it. Restated at the same specificity, later.
 *
 * These sit OUTSIDE every panel wrapper (the top bar is .following.bar, a sibling of the page
 * content), which is why the page-type scoping used everywhere else does not reach them.
 * ======================================================================================== */

/* --- 1. top-bar dropdowns ---------------------------------------------------------------- */
.ui.menu .right.menu .dropdown:last-child .menu,
.ui.menu .right.dropdown.item .menu,
.ui.buttons > .ui.dropdown:last-child .menu,
.following.bar .ui.menu .dropdown .menu,
.following.bar .ui.dropdown .menu {
  background: #f2f2f2 !important;
  border: 1px solid #c0c0c0 !important;
  box-shadow: 0 2px 6px rgba(0,0,0,.18) !important;
}

.ui.menu .ui.dropdown .menu > .item,
.following.bar .ui.menu .dropdown .menu > .item,
.following.bar .ui.dropdown .menu > .header {
  background: transparent !important;
  color: #33373f !important;
}
.ui.menu .ui.dropdown .menu > .item:hover,
.following.bar .ui.menu .dropdown .menu > .item:hover {
  background: #e2e2e2 !important;
  color: #67000a !important;
}
/* The sign-out control is a div.submit-button, not an .item, so it misses the rules above. */
.following.bar .ui.dropdown .menu .submit-button,
.ui.menu .ui.dropdown .menu .submit-button {
  background: transparent !important;
  color: #33373f !important;
}
.following.bar .ui.dropdown .menu .submit-button:hover {
  background: #e2e2e2 !important;
  color: #67000a !important;
}

/* --- 2. dashboard context switcher -------------------------------------------------------- */
.context.user.overflow.menu,
.ui.floating.dropdown .context.user.overflow.menu {
  background: #f2f2f2 !important;
  border: 1px solid #c0c0c0 !important;
  box-shadow: 0 2px 6px rgba(0,0,0,.18) !important;
}
.context.user.overflow.menu .ui.header,
.context.user.overflow.menu .items .item,
.overflow.menu .items .item {
  background: transparent !important;
  color: #33373f !important;
}
.overflow.menu .items .item:hover,
.context.user.overflow.menu .items .item:hover {
  background: #e2e2e2 !important;
  color: #67000a !important;
}
over the panel. The * main site does the latter (/desk/ renders

Desk
