/* ============================================================ Winnrs house style — one shared look for every app, every page. Home: backbone /static, served at team.winnrs.co/static Grown in pieces (see UI_KIT_PLAN.md). Phase A: header + boxes + page basics. How to use on a page: Then use the wui- classes below, or let winnrs-header.js draw the header. Everything is prefixed "wui-" so it never clashes with a page's own styles. Change a colour or size once here → every app updates. ============================================================ */ :root { --header-bg: #1a1a2e; /* the dark top bar */ --page-bg: #f4f5f8; /* the light page behind everything */ --surface: #ffffff; /* white boxes */ --border: #e4e6ef; /* thin box outline */ --radius: 14px; /* rounded corners */ --text: #1a1a2e; /* normal words */ --text-muted:#6b7280; /* quieter words */ --accent: #6d4aff; /* the one highlight colour (links, focus) */ --accent-dark:#5538e0; /* ── THE COLOUR A NEGATIVE NUMBER SHOWS IN. THE ONE HOME FOR IT. ────────── Randy, 2026-09-02: a negative shows as red (120), and becomes -120 again the moment you click into the box. Before this it was hand-written SEVEN times in six files across four apps — counted that day over every .html/.js/.css in Documents\Winnrs outside node_modules and worktrees, never a typed folder list — and had already drifted into TWO different reds (#c0392b and #dc2626). Picking one here ends that; #c0392b is the one winnrs-ui.css already uses for an error message (.wui-state-error below), so a negative amount and a refusal now speak in the same red instead of two. The BRACKETS are not here, and that is deliberate: CSS can paint a colour but it cannot read -120 out of a box. That half lives in the one file that can — winnrs-numbers.js, on this same shelf — and it names this class without ever naming a colour. Mottos a, b, c, n. */ --negative: #c0392b; /* --danger: SOMETHING WENT WRONG. Added 2026-09-07, §11 JOB 188's sitting. 🔴 IT IS NOT A SECOND NAME FOR --negative, AND KEEPING THEM APART IS THE WHOLE POINT. --negative means "this NUMBER is below zero". --danger means "this MESSAGE is an error". They happen to be the same red today. The day Randy wants a different red for a minus figure, every error message in the fleet would have followed it — which is matching by the VALUE instead of by what the thing MEANS (mottos a, d). ⚠️ THIS DOES NOT UNDO THE DECISION WRITTEN 20 LINES ABOVE, and it is worth saying so rather than letting a later reader think it was overruled. That note chose #c0392b so "a negative amount and a refusal speak in the same red instead of two". They still do — same value, on purpose. What it never said is that they must share a NAME, and two names holding one value is what keeps that choice REVERSIBLE instead of welded shut. 🔴 AND THE NAME IS NOT INVENTED HERE. It was already hand-typed in four places before this line existed, and it had ALREADY drifted into four different reds — counted over every .css and .html in Documents\Winnrs outside worktrees and node_modules, never a typed folder list: client database/static/db/relabel.html:13 #c0392b photo selection/styles.css:12 #a53b3b report drill through (old)/chatbot/static/admin.html:17 #ef4444 report drill through (old)/drill-through-wizard/styles.html:10 #dc2626 This gives that existing name ONE home (mottos b, c, n). The value is the one the live client database already uses. ✅ --good and --warn WERE in exactly the same state and now have their own home too — see the two lines below. §11 JOB 196, 2026-09-09. */ --danger: #c0392b; /* --warn: SOMETHING NEEDS A SECOND LOOK, and nothing has gone wrong yet. Added 2026-09-09, §11 JOB 196, the sitting that gave --danger its home having named these two as the next pair. 🔴 THE NAME WAS NOT INVENTED HERE EITHER. It was already hand-typed in FOUR files before this line existed, in THREE different shades — counted over every .css, .html and .js in Documents\Winnrs outside .git and node_modules, never a typed folder list: client database/static/db/relabel.html:13 #b45309 photo selection/styles.css:11 #9b6b16 report drill through (old)/drill-through-wizard/styles.html #d97706 report drill through (old)/report-webapp/styles.html #d97706 ⚠️ THE ROADMAP ROW SAID TWO FILES. A sweep of the whole fleet says four, in three shades. 🔴 THE VALUE IS CHOSEN BY THE SAME RULE --danger USED, not by taste: the one the live client database already uses. So relabel.html keeps exactly the amber it has today and simply stops typing it out. 🔴 AND NOTHING ELSE WAS TOUCHED, ON PURPOSE, NOT BY OVERSIGHT (motto o). `photo selection` is RETIRING — Randy, 2026-09-01: "no, i change my mind, the photo selection project will be retired" — and its page does not load this file at all, so pointing it here would leave it with no colour at all. `report drill through (old)` is covered by `..\master map\DEAD_FOLDERS_DO_NOT_TOUCH.md`. Both are left alone by the rules, not missed by a sweep. */ --warn: #b45309; /* --good: IT WORKED. Added 2026-09-09, §11 JOB 196. 🔴 THIS ONE HAD NOT DRIFTED YET, WHICH IS THE POINT OF DOING IT NOW. The sweep above found the name written in exactly ONE file, `client database/static/db/relabel.html:13` at #1f9d55, so giving it a home today changes nothing anybody can see and stops the second copy ever being typed. Every other success message in the fleet types its own green with no shared name to point at — that is the drift this line exists to prevent rather than to repair (mottos b, c, n; and motto f — cheaper now than after the fourth copy). */ --good: #1f9d55; --wui-font: -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, sans-serif; --btn-radius: 8px; /* rounded corners for buttons/fields (smaller than card radius) */ /* ── WHICH POP-UP SITS ON TOP OF WHICH. THE ONE HOME FOR THAT ORDER. ────── Every page that draws one of these also loads this file (checked over all 11 of them, 2026-09-02). Before this, the order lived as a COMMENT in error-report.js and six numbers typed into five other files — and a comment cannot stop the next number being typed. AUDIT_FINDINGS.md CD9_static_js_css/SLICE-08. Mottos a, b, h. Read the list downwards: each line is drawn on top of the one above it. To add a pop-up, add a line here. NEVER type a stacking number into a file. ⚠️ THE ONE ORDER THAT CHANGED, AND IT IS THE BUG THE FINDING NAMES. The Lock dialog used to be drawn ON TOP of the "are you sure?" box. So opening Lock on a journal page and then pressing the browser's Back button drew the "Are you sure you want to go back?" question UNDERNEATH the Lock dialog's grey backdrop — invisible, and clicking it shut the Lock dialog instead of answering the question. A box you MUST answer is now the top of the ladder, always. Every other order below is exactly what it already was. */ --wz-refusal-pill: 9989; /* the red "your save was refused" tab */ --wz-refusal: 9990; /* the panel that says WHY it was refused */ /* (deliberately below the table's own pop-ups */ /* at 9999 — that was decided in S4.8 and is */ /* NOT changed here) */ --wz-banner: 99997; /* the orange "you are previewing" strip on top */ --wz-card: 99998; /* the "unsaved work found" card, bottom right */ --wz-dialog: 99999; /* the Lock dialog and its grey backdrop */ --wz-ask: 100000; /* a box you MUST answer. ALWAYS THE TOP. */ } /* ── Page basics ──────────────────────────────────────────── */ /* Add class "wui" to to opt a page into the house look. */ body.wui { margin: 0; background: var(--page-bg); color: var(--text); font-family: var(--wui-font); -webkit-font-smoothing: antialiased; } /* Full-width content area under the header (UI_KIT_PLAN.md §4a — no side gutters, Randy 2026-07-24; the gap ITSELF zeroed 2026-07-29, General rule 5). Fills the screen edge to edge, no side padding at all. Changed here ONCE so every page is full-width by default — no page needs its own opt-out. The one written exception (a centred sign-in card, static/db/index.html) restores its own side padding locally — see that page's own