/* styles/tabs/update.css */ /* ══════════════════════════════════════════════════════════════════════ PROJECT UPDATE & CONTROL — STYLES Every colour here comes from styles/core/00-00-tokens-reset.css. Nothing in this file introduces a palette: --bg #FBF7F1 parchment ground --tx #2A2F36 body ink --bg2 #F3E9DA warm secondary --st #0F1B2E navy structure --mu #4D6E91 steel blue --am #24B47E green, positive --pk #188D68 deep green --rd #8B3A1F terracotta, negative --vi #B8693E ochre, attention --sk/--sk2 hairlines --r 16px --r2 12px --r3 8px 'DM Sans' WBS colours are NEVER written here. They arrive as inline custom properties resolved from window.AppearancePalette.getLevelPalette() — the same call tabs/gantt/plugins/142-gantt-premium-layout-v13.js makes — so the Update module, the Gantt table and the generated Excel sheet cannot drift apart. Changing the palette in Settings repaints all three. Two additions the rest of the app does not have, both earned: · a navy STATUS RAIL, because every number on these screens is measured at the Data Date and it must never scroll off · a monospace face for activity IDs, dates and durations, because a 1,200-row project-controls grid is read column-wise and proportional digits do not line up ══════════════════════════════════════════════════════════════════════ */ .upd { /* ── SEMANTIC COLOURS ARE LITERAL ON PURPOSE ────────────────────────── --am, --rd, --vi and --pk are the app's accent tokens, and several theme stylesheets REMAP them: styles/core/nexora-theme05.css sets --am to var(--nx-gold), 999-ai-planner-landing-theme.css sets it to var(--ap-honey), nexora-premium-redesign.css sets it to var(--nx-warning). So `var(--am)` is not reliably green. On a project-controls screen that is not a cosmetic problem. "Ahead of plan" rendering in the same hue as "attention", because someone chose a different theme preset, misreads the programme. So the four status colours are pinned to the values in styles/core/00-00-tokens-reset.css and used through these names everywhere in the module. WBS colours are the opposite case and are NOT pinned: they come from window.AppearancePalette so the planner's chosen palette reaches the grid, the Gantt and the Excel sheet alike. */ --u-ok: #24B47E; /* ahead of / on plan (00-00 --am) */ --u-good: #188D68; /* complete, earned (00-00 --pk) */ --u-warn: #B8693E; /* attention, suggested (00-00 --vi) */ --u-bad: #8B3A1F; /* behind, negative (00-00 --rd) */ --u-crit: #C6462B; /* critical / negative float */ --u-ai: #6D5BA8; /* machine-proposed */ --u-dd: #2F6BD8; /* the Data Date, as tabs/gantt/print/tokens.js draws it */ /* the two the inline timeline adds. A baseline bar has to sit BEHIND the current one without competing with it, and remaining work has to be legible against both green and terracotta, which --u-warn at bar height is not — it reads as the same ink as the baseline. */ /* ── THE BAR PALETTE ───────────────────────────────────────────────── Four values, and the rule between them is the whole legend: --u-bl the baseline. ONE fixed colour, never tinted by status, criticality or the WBS palette. A reference that changes colour is not a reference. --u-todo an activity that still has float --u-crit an activity on the critical path — which after an update is the NEW critical path, not the baseline's --u-cmpl an activity that has finished --u-sum a WBS summary One colour per bar. Splitting a bar into "done" and "remaining" shades put two hues inside what reads as a single object, and with the overrun segment beside it a single in-progress row carried four coloured pieces. Progress is a figure, in the Plan % / Actual % / Var columns. */ /* AMBER, and only ever amber. The baseline is the one thing on the timeline that does not move, so it is the one thing whose colour must not depend on anything: not status, not criticality, not the WBS palette, not whether the activity slipped. Slate was too close to the grid lines and to the app's own steel to read as a distinct object at 5px tall across 257 rows. */ --u-bl: #D9A419; /* amber — the baseline, and nothing else */ --u-todo: #2E9E72; /* in progress or still to come, with float */ /* COMPLETE IS BLUE. A finished activity is out of the argument: critical and float are questions about work still to come, and leaving a closed activity green keeps it in a conversation it has left. */ --u-cmpl: #1F5FA9; /* A WBS SUMMARY IS BLACK. A phase has no status of its own to be coloured by — it is not late, not critical, not complete, it is a container. Tinting it from the WBS palette made every band a different colour and put it in competition with the bars it summarises. */ --u-sum: #0B0F14; /* near-black: a summary bar, and nothing else */ --u-rem: #C79157; /* kept: the Review screen's "after" bar */ --u-mono: 'JetBrains Mono', ui-monospace, 'SFMono-Regular', Menlo, monospace; --u-row: 26px; /* was 30: the grid is the screen's job, so it fits more of it */ font-size: 13px; color: var(--tx); padding-bottom: 40px; } /* ── A