diff --git "a/web/src/index.css" "b/web/src/index.css" --- "a/web/src/index.css" +++ "b/web/src/index.css" @@ -7077,11 +7077,25 @@ a.cg-map-ctl-b { text-decoration: none; } padding-right: 6px; } .auto-rail.is-collapsed > :not(.auto-rail-top) { display: none; } +/* ⭐ WAVE 23 C13 (owner item 2) — THE SAME TOP BAND AS THE VIEWS RAIL, anatomy for anatomy. + It had the height and nothing else: the fold control sat LEFT while the Views rail's sits + right, and there was no hairline at all — so the automation page's top band simply stopped + halfway across the screen while every database page's ran edge to edge. The three things + `.cg-views-top` does and this did not: `justify-content: flex-end`, the closing hairline, + and the negative margin that bleeds that line past the rail's own gutter to its true edges + (`overflow: hidden` on the rail clips the collapsed overshoot, exactly as it does there). + ⚠ THE BLEED IS THIS RAIL'S OWN GUTTER, not a copied number: `.cg-views` pads 8px and bleeds + -8px; this rail pads 10px, so it bleeds -10px. Copying the -8 would leave a 2px gap at each + end — the same defect in a more convincing disguise. */ .auto-rail-top { + flex: 0 0 var(--lp-rail-head-h); + height: var(--lp-rail-head-h); display: flex; align-items: center; - height: var(--lp-rail-head-h); - flex: 0 0 auto; + justify-content: flex-end; + margin: 0 -10px; + padding: 0 10px; + border-bottom: 1px solid var(--lp-line); } .auto-create { margin-top: 8px; } .auto-create-btn { @@ -7130,6 +7144,20 @@ a.cg-map-ctl-b { text-decoration: none; } background: transparent; color: inherit; font: inherit; + /* ⭐ WAVE 24 (owner item 2) — THE SAME SIZE AS THE VIEWS RAIL, which is what the two rails + are: one idea rendered twice. `font: inherit` alone resets font-size to the INHERITED + value, and this rail's ancestor carries `--lp-fs-sm` (14px) while `.cg-view-main` (:570) + declares `--lp-fs-xs` (13px) right after its own shorthand. So the automation rail rendered + one step larger than the views rail for no reason anybody chose. + ⛔ THE ORDER OF THESE TWO LINES IS LOAD-BEARING. `font:` is a SHORTHAND and re-expands over + every longhand before it, so this declaration above `font: inherit` would be silently + undone — no error, no gate, nothing to see but a 1px difference. That is the trap + `index.css:3013`'s comment documents for `.shell-nav-item` and the one wave 21 paid for + twice on the Alerts button. `verify_automation_ui.py` now resolves both selectors the way + the cascade does and fails if they disagree, so this cannot silently come back. + ⚠ The rail's SECOND line needed nothing: `.auto-row-desc` and `.cg-view-desc` already both + resolve `--lp-fs-3xs`. Measured before touching either. */ + font-size: var(--lp-fs-xs); text-align: left; cursor: pointer; border-radius: var(--lp-r-md); @@ -7237,6 +7265,14 @@ a.cg-map-ctl-b { text-decoration: none; } background: var(--lp-surface); } .auto-head-title { display: flex; align-items: center; gap: 10px; min-width: 0; } +/* ⭐ WAVE 23 C13 — BYTE-MATCHED TO `.shell-db-name`, which is the title system this page now + wears (the shell's `DbHead`, wiring W23-W1). It was 16px/**700** beside the frame's 16px/650 + and a 20px/600 empty-state h1: three treatments on one page. The spec here is the SIBLING'S + COMPUTED VALUES, not "a legal token" (DESIGN.md 2 — the wave-21 scar where a legal token + still put a 17px title beside a 14.875px one), so this copies the token AND the weight from + `.shell-db-name` rather than picking either independently. + ⚠ `font: inherit` FIRST, longhands after — a bare shorthand below them re-expands and undoes + them (R5b's gate, the Alerts-button scar). */ .auto-name { min-width: 0; flex: 0 1 auto; @@ -7248,7 +7284,7 @@ a.cg-map-ctl-b { text-decoration: none; } color: var(--lp-ink); font: inherit; font-size: var(--lp-fs-md); - font-weight: 700; + font-weight: 650; } .auto-name:hover { border-color: var(--lp-line); } .auto-name:focus { @@ -7340,7 +7376,7 @@ a.cg-map-ctl-b { text-decoration: none; } color: var(--lp-green-deep); } -/* ── the canvas (R5) ───────────────────────────────────────────────────────────────────── */ +/* ── the work area: the flow on the left, its config panel on the right ─────────────────── */ .auto-work { flex: 1 1 auto; min-height: 0; @@ -7349,9 +7385,12 @@ a.cg-map-ctl-b { text-decoration: none; } } /* ── the numbered steps (owner ruling R9) ────────────────────────────────────────────────── ⛔ THIS BLOCK REPLACED THE CANVAS'S (`.auto-canvas*`, `.auto-scene`, `.auto-wires`, - `.auto-node*`, `.auto-zoom*`). `AutomationCanvas.tsx` + `canvasLayout.ts` are still on disk - and are UNMOUNTED — remounting one would paint an unstyled flow, so its CSS comes back with - its mount, not before. Booked as debt in the wave-21 mailbox. + `.auto-node*`, `.auto-zoom*`). ⚠ PROSE CORRECTED, WAVE 23 (D-42): it said those components + were "still on disk and UNMOUNTED", which stopped being true when wave 22 DELETED + `AutomationCanvas.tsx` and `canvasLayout.ts` outright — the board supersedes the rebuild + question they were being kept for. A comment describing files that no longer exist is the + hazard [[gate-can-report-green-on-nothing]] is about wearing a footnote's clothes: the next + reader goes looking for a mount that cannot be found. The column reads top to bottom: a number, a card, a line to the next one. An ALTERNATIVE (the paid rung vs the anonymous ladder) repeats the number it is an alternative to and says @@ -7403,7 +7442,9 @@ a.cg-map-ctl-b { text-decoration: none; } background: var(--lp-surface); color: var(--lp-muted); font-size: var(--lp-fs-4xs); - font-weight: 700; + /* 600, not 700 — DESIGN.md 2 caps display weights, and a step numeral in a bordered pill is + legible at semibold. Part of the D-42 sweep: the region carried eight 700s. */ + font-weight: 600; font-variant-numeric: tabular-nums; } /* An alternative carries the SAME number, so it is drawn hollow — the reader needs to see at a @@ -7486,7 +7527,7 @@ a.cg-map-ctl-b { text-decoration: none; } text-overflow: ellipsis; white-space: nowrap; font-size: var(--lp-fs-xs); - font-weight: 700; + font-weight: 600; } .auto-step-tag { flex: 0 0 auto; @@ -7597,7 +7638,7 @@ a.cg-map-ctl-b { text-decoration: none; } .auto-panel-head h2 { margin: 0; font-size: var(--lp-fs-md); - font-weight: 700; + font-weight: 600; } .auto-panel-close { flex: 0 0 auto; @@ -7617,7 +7658,7 @@ a.cg-map-ctl-b { text-decoration: none; } .auto-panel h3 { margin: 8px 0 0; font-size: var(--lp-fs-xs); - font-weight: 700; + font-weight: 600; } .auto-panel-scroll { max-height: 340px; overflow: auto; } .auto-panel code { @@ -7770,19 +7811,14 @@ a.cg-map-ctl-b { text-decoration: none; } .auto-drill { margin-top: 8px; border-top: 1px solid var(--lp-line); padding-top: 8px; } .auto-drill-scroll { max-height: 320px; overflow: auto; } -/* ── the empty state and the create form ───────────────────────────────────────────────── */ -.auto-empty { padding: 40px 32px; max-width: 720px; } -.auto-empty h1 { margin: 0 0 8px; font-size: var(--lp-fs-lg); font-weight: 700; } -.auto-empty p { margin: 0 0 14px; color: var(--lp-muted); line-height: var(--lp-lh); } -.auto-empty-kinds { - margin: 0; - padding-left: 18px; - display: flex; - flex-direction: column; - gap: 10px; -} -.auto-empty-kinds li { line-height: var(--lp-lh); font-size: var(--lp-fs-xs); color: var(--lp-muted); } -.auto-empty-kinds strong { color: var(--lp-ink); } +/* ── the create form ─────────────────────────────────────────────────────────────────────── + ⛔ `.auto-empty`, `.auto-empty h1/p`, `.auto-empty-kinds` and `.auto-empty-kinds strong` + ARE DELETED (D-42). They styled the 130-word landing pane R13 removed in wave 22; the + replacement is `.autob-empty` in the W22 region below, and these six rules had ZERO call + sites in `src/` for a whole release. Dead CSS is not inert — `.auto-empty h1` carried one of + the region's `font-weight: 700`s, so a sweep for the weight cap kept finding a rule that + could never paint, and the next person to grep `.auto-empty` finds two families where there + is one. */ .auto-create-pane { flex: 1 1 auto; min-height: 0; overflow-y: auto; padding: 24px 20px 40px; } .auto-create-card { max-width: 780px; @@ -7794,8 +7830,8 @@ a.cg-map-ctl-b { text-decoration: none; } border-radius: var(--lp-r-lg); background: var(--lp-surface); } -.auto-create-card h1 { margin: 0; font-size: var(--lp-fs-lg); font-weight: 700; } -.auto-create-card h3 { margin: 6px 0 0; font-size: var(--lp-fs-xs); font-weight: 700; } +.auto-create-card h1 { margin: 0; font-size: var(--lp-fs-lg); font-weight: 600; } +.auto-create-card h3 { margin: 6px 0 0; font-size: var(--lp-fs-xs); font-weight: 600; } .auto-create-card .auto-banner { margin: 0; } /* Narrow viewports: the panel stops being a side rail and becomes a bottom sheet, so the @@ -7885,14 +7921,11 @@ a.cg-map-ctl-b { text-decoration: none; } align-items: flex-start; gap: 10px; } -/* Weight 600, not 700: DESIGN.md 2 caps display weights at 600 and the pane this replaced - was one of the sites carrying a heavier one. */ -.autob-empty-title { - margin: 0; - font-size: var(--lp-fs-lg); - font-weight: 600; - color: var(--lp-ink); -} +/* ⛔ `.autob-empty-title` IS DELETED (wave 23 C13, owner item 2). It styled this pane's own + 20px `h1` — the THIRD title treatment on a page that already had the header's editable name + and now wears the shell's `DbHead` (16px/650) like every database page. The h1 went with the + duplicate; its rule goes with the h1, in the same change, so the next reader cannot find a + title style with nothing to style. */ .autob-empty-line { margin: 0; font-size: var(--lp-fs-xs); @@ -7908,26 +7941,14 @@ a.cg-map-ctl-b { text-decoration: none; } display: flex; flex-direction: column; } -.autob-triggerbar { - flex: 0 0 auto; - display: flex; - flex-direction: column; - gap: 8px; - padding: 14px 16px; - border-bottom: 1px solid var(--lp-line); - background: var(--lp-surface); -} -/* The picker is one short phrase, not a paragraph: `.auto-field-row`'s `flex: 1 1 220px` - stretched it across the full bar, so "Manual only" sat in a 600px control. 320px is - MEASURED, not chosen: at 260 the longest option ("When an email arrives - needs setting - up") truncated in the collapsed control, which reads as a broken value rather than a long - one. The open list is as wide as it needs to be either way. */ -.autob-triggerbar .auto-field { flex: 0 1 320px; } -.autob-triggerbar-tag { - font-size: var(--lp-fs-4xs); - font-weight: 600; - color: var(--lp-muted); -} +/* ⛔ `.autob-triggerbar`, `.autob-triggerbar .auto-field` and `.autob-triggerbar-tag` WERE HERE + and are DELETED (wave 24, owner item 10). The bar sat above the Board's lanes carrying a + second trigger picker and the "Instagram profile column" kind tag; the Board is for reading + where records ARE, so the trigger went back to the Builder and the tag went with the header. + Session B took `AutomationDetail.tsx` to zero call sites and said so in its mailbox before + this was removed — a class deleted while one call site survives is a blank control, which is + worse than the residue. Deleted rather than left behind because W23/D-42 closed exactly this + residue class one wave ago and re-earning it in the next wave is how a rule stops being one. */ /* A trigger waiting on a connector: attention, not failure — so yellow, and the next step sits inside the same box as the sentence that explains it. */ .autob-needs { @@ -7972,56 +7993,14 @@ a.cg-map-ctl-b { text-decoration: none; } /* ── the process strip: the stages that are STEPS rather than places ───────────────────── `record: false` stages (find / collect / write) can never hold a card, so they are not lanes — a lane that can never receive anything is a drop target that lies. They keep - everything else a stage has: a click into their settings, their run dot, their switch. */ -.autob-strip { - flex: 0 0 auto; - display: flex; - align-items: center; - gap: 0; - flex-wrap: wrap; - padding: 10px 14px 0; -} -.autob-strip-step { - display: inline-flex; - align-items: center; - gap: 8px; - padding: 3px 10px; - border: 1px solid var(--lp-line); - border-radius: var(--lp-r-pill); - background: var(--lp-surface); - color: var(--lp-ink); -} -.autob-strip-hit { - display: inline-flex; - align-items: center; - gap: 6px; - padding: 0; - border: 0; - background: transparent; - color: inherit; - font: inherit; - font-size: var(--lp-fs-3xs); - font-weight: 600; - cursor: pointer; -} -.autob-strip-hit:focus-visible { outline: 2px solid var(--lp-blue-deep); outline-offset: 3px; } -.autob-strip-switch { position: relative; top: auto; right: auto; flex: 0 0 auto; } -/* The connector, drawn as a rule rather than a glyph: it is the shape of the flow, not a - character somebody has to have a font for. */ -.autob-strip-step + .autob-strip-step { position: relative; margin-left: 22px; } -.autob-strip-step + .autob-strip-step::before { - content: ""; - position: absolute; - left: -17px; - top: 50%; - width: 12px; - border-top: 1px solid var(--lp-line); -} -.autob-strip-step:hover { background: var(--lp-surface-2); } -/* The connector must not paint over a chip that has grown a switch. */ -.autob-strip { row-gap: 8px; } -.autob-strip-step.is-selected { border-color: var(--lp-blue-deep); } -.autob-strip-step.is-off { opacity: 0.55; } +/* ⛔ THE `.autob-strip*` FAMILY WAS HERE and is DELETED (wave 24, owner item 9): `.autob-strip`, + `-step`, `-hit`, `-label`, `-switch`, the `+ .autob-strip-step` connector rule and the three + state modifiers. It styled the Board's process strip — Capture / Bright Data / Anonymous / + Post engagement / Write as chips above the lanes. Those stages' bodies and all four of their + switches now live in Properties > Configuration > "How this fetches" (C-CFG), so the strip has + no markup left; `AutomationBoard.tsx` is at zero call sites for every one of these classes. + ⚠ The STAGES did not go away — the server still emits them and the engine still runs them, and + `BoardStage.record` still keeps them out of the lanes. Only the drawing stopped. */ /* The review gate's audit: who moved which record, and when. */ .autob-reviews { @@ -8317,6 +8296,24 @@ a.cg-map-ctl-b { text-decoration: none; } background: var(--lp-yellow-tint); color: var(--lp-yellow-deep); } +/* The "what IS this field" line, for the handful nobody can guess (Instagram ID, Facebook ID). + Shown only when a field is switched ON — a hint under all 21 rows is a hint under none. */ +.autob-tgl-hint { + margin: 0 0 6px; + color: var(--lp-muted); + font-size: var(--lp-fs-4xs); +} +/* "any of 3" — the confirmation that a comma-separated value was read as several. Without it, + the difference between one keyword and three is a comma the eye skips. */ +.autob-cond-any { + flex: 0 0 auto; + padding: 0 6px; + border-radius: var(--lp-r-pill); + background: var(--lp-blue-tint); + color: var(--lp-blue-deep); + font-size: var(--lp-fs-4xs); + white-space: nowrap; +} /* Indented past the switch, so the conditions read as belonging to the field above them. */ .autob-tgl-body { display: flex; @@ -8377,640 +8374,720 @@ a.cg-map-ctl-b { text-decoration: none; } } /* === WAVE22 AUTOMATION BOARD — B REGION END === */ -/* ═══ W18-A TENANT/SETTINGS region (SESSION A — integrator) ═══ - Shell-side surfaces for wave 18: the user-table Add-record bar and the New-database - dialog. Tokens with fallbacks; text/strokes take the -deep weight rule. - - ⛔ `.shell-nav-newdb` WAS HERE AND IS DELETED WITH ITS ONLY CALL SITE (wave 19, R11): - "+ New database" folded into the database list's "+ Create new…" chooser. Two reasons to - delete rather than leave it: this rail's own note three thousand lines up says "a rule kept - alive for zero call sites is how dead CSS accumulates" — and the rule was a live example of - the very thing R11 was raised about, since `color: #6b7280` is a hardcoded grey sitting - beside the `--lp-muted` token that means it. */ -.shell-ut-frame { - display: flex; - flex-direction: column; - width: 100%; - height: 100%; - min-height: 0; - overflow: hidden; -} -.shell-ut-frame > .shell-grid-host { flex: 1 1 auto; min-height: 0; height: auto; } -.shell-ut-bar { - display: flex; - align-items: center; - justify-content: space-between; - gap: 12px; - padding: 8px 16px; - border-bottom: 1px solid var(--lp-line, #e6e9ef); - background: var(--lp-surface, #fafbfc); +/* === WAVE23 BUILDER — B REGION START === ══════════════════════════════════════════════════ + The BUILDER (owner item 3b, ruling R1: "exact layout, Loopable skin"). Airtable's anatomy — + a centre column of trigger → actions with a spine down the left carrying each step's status + chip, dashed add-boxes, and a Properties panel on the right — rendered in OUR tokens. + + THE SKIN IS THE PART THAT IS NOT AIRTABLE'S, and the differences are deliberate: + · NO CAPS. Airtable's "TRIGGER / ACTIONS / CONFIGURATION / TEST STEP" are sentence case + here (R6, DESIGN.md 2), and de-capping takes the caps-era letter-spacing WITH it — + positive tracking existed only to open capitals up. Weight and colour are unchanged. + · No Airtable blue. Selected = `--lp-primary`, the one hue this product spends on "you are + here"; attention = yellow; a refusal = red. DESIGN.md 3's fixed semantics, unaltered. + · Hairlines, not shadows (DESIGN.md 4) — the two shadows in this block are on OVERLAYS + (the action menu, the confirm), which is the exception the constitution names. + ⚠ Every button here resets UA chrome and declares `font: inherit` BEFORE its own longhands + — the wave-19 leaked-chrome bug and the R5b cascade gate, in that order. + No literal font-size anywhere: tokens or nothing (R5). ═══════════════════════════════════ */ + +/* ── the view switch (C1): what it DOES / where its records ARE ─────────────────────────── */ +.autox-views { + display: inline-flex; flex: 0 0 auto; + padding: 2px; + gap: 2px; + border: 1px solid var(--lp-line); + border-radius: var(--lp-r-md); + background: var(--lp-surface-2); } -.shell-ut-name { - font-size: var(--lp-fs-sm); - font-weight: 600; - color: var(--lp-ink, #1b2a41); -} -.shell-ut-add { - border: 1px solid var(--lp-line, #e6e9ef); - background: #fff; - border-radius: var(--lp-r-sm, 7px); - padding: 5px 12px; +.autox-view { + border: 0; + background: transparent; + color: var(--lp-muted); font: inherit; font-size: var(--lp-fs-xs); font-weight: 600; - color: var(--lp-ink, #1b2a41); + padding: 3px 12px; + border-radius: var(--lp-r-sm); cursor: pointer; } -.shell-ut-add:hover { background: var(--lp-wash, #f6f8fa); } -.shell-ut-add:disabled { opacity: 0.55; cursor: default; } -.shell-newdb-scrim { - position: fixed; - inset: 0; - background: rgba(15, 23, 42, 0.32); +.autox-view:hover { color: var(--lp-ink); } +.autox-view.is-on { background: var(--lp-surface); color: var(--lp-ink); } +.autox-view:focus-visible { outline: 2px solid var(--lp-blue-deep); outline-offset: 1px; } + +/* ── the centre column ──────────────────────────────────────────────────────────────────── */ +.autox-flow { + flex: 1 1 auto; + min-width: 0; + min-height: 0; + overflow-y: auto; + padding: 20px 24px 48px; +} +/* THE SPINE is the side column's right border, so it is continuous down the page without a + single absolutely-positioned line: each step contributes its own segment and they meet. */ +.autox-step { + display: grid; + grid-template-columns: 132px minmax(0, 1fr); + align-items: stretch; +} +.autox-side { display: flex; - align-items: flex-start; - justify-content: center; - padding-top: 18vh; - z-index: 80; + flex-direction: column; + align-items: flex-end; + gap: 10px; + padding: 3px 14px 18px 0; + border-right: 1px solid var(--lp-line); + text-align: right; } -.shell-newdb { - width: 400px; - max-width: calc(100vw - 48px); - background: #fff; - border: 1px solid var(--lp-line, #e6e9ef); - border-radius: 10px; - box-shadow: 0 18px 50px rgba(15, 23, 42, 0.18); - padding: 20px 22px; +.autox-tag { + font-size: var(--lp-fs-2xs); + font-weight: 600; + color: var(--lp-muted); } -.shell-newdb h2 { - font-size: var(--lp-fs-sm); - font-weight: 650; - margin: 0 0 6px; - color: var(--lp-ink, #1b2a41); +.autox-main { + display: flex; + flex-direction: column; + align-items: flex-start; + gap: 10px; + min-width: 0; + padding: 0 0 18px 20px; } -.shell-newdb-sub { - font-size: var(--lp-fs-xs); - color: #6b7280; - margin: 0 0 14px; - line-height: 1.45; +/* The chip sits ON the connector line, right-aligned to it (images 3/4/7): it is the step's + one-line state, and it is a STATEMENT, never a control. */ +.autox-chip { + display: inline-flex; + align-items: center; + gap: 6px; + padding: 3px 10px; + border: 1px solid var(--lp-line); + border-radius: var(--lp-r-pill); + background: var(--lp-surface); + color: var(--lp-muted); + font-size: var(--lp-fs-3xs); + font-weight: 600; + white-space: nowrap; } -.shell-newdb-input { - width: 100%; - border: 1px solid var(--lp-line, #e6e9ef); - border-radius: 8px; - padding: 8px 10px; - font: inherit; - font-size: var(--lp-fs-sm); - box-sizing: border-box; +.autox-chip.is-warn { + background: var(--lp-yellow-tint); + border-color: var(--lp-yellow); + color: var(--lp-yellow-deep); } -.shell-newdb-err { - font-size: var(--lp-fs-xs); - color: #b4231f; - margin: 8px 0 0; +.autox-chip.is-ok { + background: var(--lp-green-tint); + border-color: var(--lp-green); + color: var(--lp-green-deep); } -.shell-newdb-actions { + +/* ── a card ─────────────────────────────────────────────────────────────────────────────── */ +.autox-card { display: flex; - justify-content: flex-end; - gap: 8px; - margin-top: 16px; + align-items: center; + gap: 4px; + width: 100%; + max-width: 460px; + padding-right: 6px; + border: 1px solid var(--lp-line); + border-radius: var(--lp-r-md); + background: var(--lp-surface); + transition: border-color 0.14s ease, background 0.14s ease; } -.shell-newdb-actions button { - border-radius: 8px; - padding: 7px 14px; +.autox-card.is-selected { border-color: var(--lp-primary); background: var(--lp-primary-tint); } +/* ⚠ OFF IS DRAWN, NOT FADED — the same rule the steps card carries. `opacity` on a whole + surface is how wave 19 shipped a permanently half-erased rail. */ +.autox-card.is-off { border-style: dashed; background: var(--lp-surface-2); } +.autox-card.is-machine { background: var(--lp-wash); } +.autox-card.is-group { border-color: var(--lp-purple); } +/* ── the reorder drop target (owner item 11) ──────────────────────────────────────────────── + A LINE, not a fill: the card being dragged over is where the dragged one will LAND, so the + mark belongs on the edge it will arrive at rather than over the card's own contents — and a + tinted card would collide with `.is-selected`, which already spends the primary hue on + "you are here". `[draggable]` gets the grab cursor only on the cards that actually reorder, + so the affordance and the capability cannot disagree. */ +.autox-card[draggable="true"] { cursor: grab; } +.autox-card[draggable="true"]:active { cursor: grabbing; } +.autox-card.is-dropinto { box-shadow: inset 0 2px 0 0 var(--lp-primary); } +.autox-card-hit { + flex: 1 1 auto; + min-width: 0; + display: flex; + align-items: center; + gap: 10px; + padding: 9px 10px; + border: 0; + background: transparent; + color: inherit; font: inherit; font-size: var(--lp-fs-xs); - font-weight: 600; + font-weight: 400; + text-align: left; cursor: pointer; - border: 1px solid var(--lp-line, #e6e9ef); - background: #fff; - color: var(--lp-ink, #1b2a41); + border-radius: var(--lp-r-md); } -.shell-newdb-actions button:disabled { opacity: 0.55; cursor: default; } -/* ═══ end W18-A TENANT/SETTINGS region ═══ */ - -/* W18-A addition: the assistant's boarded door (same panel family as .shell-newdb). */ -.shell-assist-note h2 { - display: flex; +.autox-card-hit:focus-visible { outline: 2px solid var(--lp-blue-deep); outline-offset: -2px; } +.autox-card-mark { + flex: 0 0 auto; + display: inline-flex; align-items: center; - gap: 8px; -} -.shell-assist-note h2 svg { flex: 0 0 auto; } - -/* W18-A addition: keychain + connectors panes (set-* family extensions). */ -.kc-row { display: flex; align-items: flex-start; justify-content: space-between; gap: 12px; } -.kc-main { display: flex; flex-direction: column; gap: 2px; min-width: 0; } -.kc-meta { font-size: var(--lp-fs-xs); color: #6b7280; } -.kc-test { font-size: var(--lp-fs-xs); color: #374151; } -.kc-actions { display: flex; gap: 6px; flex: 0 0 auto; } -.kc-danger { color: #b4231f; } -.kc-form { display: flex; flex-direction: column; gap: 10px; margin-top: 12px; } -.kc-note { margin-top: 10px; } -.kc-unsynced { margin-top: 14px; } -.kc-orphans { - margin: 8px 0 0; - padding-left: 18px; - font-size: var(--lp-fs-xs); - color: #374151; - max-height: 200px; - overflow-y: auto; -} - -/* W18-A addition: the tenant welcome hero. `.login-submit` is `display:block; width:100%` by - design (a login form's button fills its field column) — inside a full-width pane that made - the CTA span the whole viewport. Caught in the close-out visual pass; no gate sees width. */ -.shell-tenant-hero { max-width: 560px; } -.shell-tenant-hero h1 { margin-bottom: 8px; } -.shell-tenant-hero p { margin: 0 0 20px; line-height: 1.55; color: #4b5563; } -.shell-hero-create { - width: auto; - display: inline-block; - padding: 0 20px; - margin-top: 0; -} - -/* == W19-D PLATFORM ADMIN == */ -/* The Loopable admin plane (`settings/AdminPane.tsx`, owner item 13 / R3+R4). - - Region-owned by session D this wave; nothing outside these markers is touched. - Table-first and deliberately quiet: this surface is read, not operated — the - only interactions are "open the rows behind this number" and "close it". - - Constitution compliance, stated because it is checkable (DESIGN.md): - §2 no `text-transform`; micro-labels are small + muted + tracked, sentence - case. Every `font-size` is a `--lp-fs-*` token, never a literal. - §3 tokens as variables only — no hex anywhere below. Pastels appear as - FILLS (the status dots); all text rides ink/muted or `--lp-primary`. - §4 4/8px rhythm, hairlines instead of shadows, ONE containment layer (the - pane's own card chrome is `.set-*`; nothing here nests a second card), - and every `