mirror of
https://github.com/snapotter-hq/SnapOtter.git
synced 2026-08-03 07:46:42 +02:00
SnapOtterandGitHub
d10d0f544f
A release-readiness QA pass over the whole product. The commits split into defects a user would hit and gates that were reporting green while measuring nothing. ## Fixes that change behaviour Rate limiting was bypassable on every install: TRUST_PROXY defaulted to true, so request.ip came from a client-set header and a forged X-Forwarded-For got past the login limiter. The default is now a private-network trust list. A transient Postgres outage stranded in-flight jobs, leaving finished output on disk with no row pointing at it. A reconciler now resolves those rows and adopts the bytes rather than dropping the work. A Redis connection that moved to a new address wedged every read-blocked consumer, so completions stopped signalling while health still answered 200. Socket timeouts plus subscriber pings recover it. Installing more than one AI bundle left the shared venv multi-versioned and silently broke three tools. The installer now reconciles distributions to one version each. Converting an image to JXL at quality 1 through 4 returned a 500, because libjxl 0.7 rejects the distance those values compute. The quality is floored at what the encoder honours. A missing ffmpeg was also reported to the user as a corrupt upload; it now says the engine is unavailable. RAW uploads reached an unpatched LibRaw on arm64, so it is built from source at 0.22.2, and the release scan was split so it can fail on an unfixed critical instead of hiding it behind ignore-unfixed. ## Gates that could not fail Two mutation lanes ran zero mutants because Stryker crawled the gitignored docs build; coverage discarded its whole report on any failing test; the lint gate skipped root tests, scripts, and two workspaces; and several generated matrices counted a host missing ffmpeg as a passing tool. Each now measures what it claims. Full evidence and the outstanding release items are tracked locally and are not part of this branch.
77 lines
2.9 KiB
CSS
77 lines
2.9 KiB
CSS
/* Otter-orange brand override. AA note: #A85518 on white = ~5.2:1 (passes AA for text + buttons).
|
|
Vibrant #E07832 / #F09550 are decorative only (see DocsHome.vue), never under white text. */
|
|
:root {
|
|
--vp-c-brand-1: #A85518;
|
|
--vp-c-brand-2: #8F4712;
|
|
--vp-c-brand-3: #A85518;
|
|
--vp-c-brand-soft: rgba(224, 120, 50, 0.14);
|
|
--vp-button-brand-border: transparent;
|
|
--vp-button-brand-text: #fff;
|
|
--vp-button-brand-bg: #A85518;
|
|
--vp-button-brand-hover-border: transparent;
|
|
--vp-button-brand-hover-text: #fff;
|
|
--vp-button-brand-hover-bg: #8F4712;
|
|
--vp-button-brand-active-border: transparent;
|
|
--vp-button-brand-active-text: #fff;
|
|
--vp-button-brand-active-bg: #7A3D10;
|
|
|
|
/* Inline `code` never sits on white. VitePress tints it with --vp-c-default-soft
|
|
(#e7e9ec in tables and prose) and custom blocks tint it further (#f7dcca), which
|
|
drops brand-1 to 4.34:1 and 4.03:1. The darker ink clears AA on both: 5.62:1 and
|
|
5.22:1. This was 482 failures on the REST page alone. */
|
|
--vp-code-color: #8F4712;
|
|
/* The language label above a code block was #929295 on #f6f6f7, 2.87:1. */
|
|
--vp-code-lang-color: #5C5C60;
|
|
}
|
|
/* Inside a tip/info block VitePress paints inline code with brand-1 over the brand
|
|
tint directly, so --vp-code-color never reaches it: 4.03:1. Dark mode was fine. */
|
|
.vp-doc .custom-block :not(pre) > code {
|
|
color: #8F4712;
|
|
}
|
|
|
|
.dark .vp-doc .custom-block :not(pre) > code {
|
|
color: var(--vp-c-brand-1);
|
|
}
|
|
|
|
.dark {
|
|
--vp-c-brand-1: #F0A766;
|
|
--vp-c-brand-2: #F09550;
|
|
--vp-c-brand-3: #A85518;
|
|
--vp-c-brand-soft: rgba(240, 149, 80, 0.16);
|
|
}
|
|
|
|
/* Tablet navbar overflow (SITE-20260726-011).
|
|
|
|
VitePress swaps to the desktop nav at 768px. Several locales carry top-level
|
|
labels far longer than English (es 55 characters, pt-BR 54, th 53, ru 52,
|
|
de 48 against en 33), so between 768px and the 960px sidebar breakpoint the
|
|
navbar's right edge landed outside the viewport and every docs page in those
|
|
languages scrolled sideways.
|
|
|
|
Moving that one switch to 960px puts the top-level nav back in the hamburger
|
|
overlay for the 768-959 band. Nothing becomes unreachable: the sidebar is
|
|
already opened from VPLocalNav's menu button below 960px, and this is exactly
|
|
the arrangement VitePress uses below 768px. VPNavScreen is v-if-mounted, so
|
|
the display override only ever applies to an open overlay.
|
|
|
|
One upstream wart is inherited: useNav closes an open overlay on resize past
|
|
768px, so dragging the window across that width inside the band shuts the
|
|
menu. Reopening it works.
|
|
|
|
The declarations carry !important because VitePress ships these rules from
|
|
Vue `<style scoped>` blocks, which compile to `.VPNavBarMenu[data-v-hash]`
|
|
and outrank a plain class selector however late it loads. */
|
|
@media (min-width: 768px) and (max-width: 959.9px) {
|
|
.VPNavBarMenu {
|
|
display: none !important;
|
|
}
|
|
|
|
.VPNavBarHamburger {
|
|
display: block !important;
|
|
}
|
|
|
|
.VPNavScreen {
|
|
display: block !important;
|
|
}
|
|
}
|