{"entries":[{"lastCommit":{"author":{"email":"claas@claas.dev","name":"Claas","when":"2026-08-06T09:21:27.000000+02:00"},"committer":{"email":"claas@claas.dev","name":"Claas","when":"2026-08-06T17:29:41.000000+02:00"},"hash":"04ee93bf05a24f9feb8509925b2e646896e95780","message":"Make the skip control reachable in WebKit\n\nWebKit leaves links out of the tab order unless the system's keyboard\nnavigation setting is on, and that setting is off by default. On macOS\nthe app runs in WKWebView, so a skip link written as an anchor is a skip\nlink nobody can reach with the keyboard — which is the one thing a skip\nlink exists to be.\n\nTab order, measured in both engines against the running app:\n\n chromium A \"Skip to history\" -> input -> button\n webkit input -> button (the link is never focused)\n\nA button is tabbable everywhere and moves focus explicitly, so it does\nthe job in both. The end-to-end tests that found this run next.\n\nCo-Authored-By: Claude Opus 5 \n","tree":"439b4c80d805c9f8b3f340db5475c4217c9c1222"},"mode":"0100644","name":"App.tsx","size":3831},{"lastCommit":{"author":{"email":"claas@claas.dev","name":"Claas","when":"2026-08-06T09:09:35.000000+02:00"},"committer":{"email":"claas@claas.dev","name":"Claas","when":"2026-08-06T17:29:41.000000+02:00"},"hash":"316a0f76438414e6321d2debd9f60d4410436dbc","message":"Draw the commit graph\n\nThe history is an ordinary list of buttons. Each row owns a small SVG\nfor its lane segment, marked aria-hidden, over content that already\nreads correctly without it — a summary, an author, a , and a\nshort id. Row is a button because selecting a commit is an action and a\nbutton brings its own role, focus ring and Enter handling; that limits\nit to phrasing content, which is why ref badges are spans with a\nvisually hidden word for what each one is.\n\nTen lane colours come from one CSS rule rather than ten values: the\nlane index rotates an oklch hue, starting near the seed colour so the\ngraph belongs to the same palette as everything else. Nothing about\ncolour reaches the Rust side, and switching light to dark re-themes the\nwhole graph without a re-render.\n\nNothing here needs a virtual list. Rows arrive in batches as the end of\nthe list nears the viewport, so the DOM only holds what has been\nscrolled to, and rows past the first forty get content-visibility so\nthe browser skips laying out and painting the rest. `none` for the\nintrinsic width keeps an off-screen row from collapsing horizontally,\nwhich would make the scroll width jump on a wide graph. Which rows are\ndeferred is decided by nth-child, so no JavaScript is involved.\n\nWide graphs scroll rather than compress. A graph's width comes from the\nhistory — aspnetcore lays out 115 columns — so no window size makes it\nfit and capping would only hide branches.\n\nTwo things caught while driving the real components in a browser:\n\n- Five arrow presses moved the selection one row. Solid 2 batches\n signal writes, so reading selected() to compute the next value goes\n stale when presses land in one batch. Now the update goes through the\n functional setter, which sees the pending value.\n- jsx-a11y assumes React's htmlFor, so Solid's plain `for` read as an\n unassociated label. Configured rather than worked around.\n\nSafari drops list semantics from a list styled with list-style: none,\nwhich Tailwind's preflight applies — and Tauri is WKWebView on macOS,\nso that is the default here. An empty-string marker renders nothing and\nleaves the list a list, which beats patching the role back with ARIA.\n\nOpening is a path field for now. A native folder picker needs the Tauri\ndialog plugin, which is a dependency this change does not need; the\npicker arrives with the repository-picker work.\n\nInfinite scrolling is not verified yet — IntersectionObserver does not\nrun in a hidden document, and the browser pane available here cannot\nmake one visible. The Playwright harness covers it next.\n\nCo-Authored-By: Claude Opus 5 \n","tree":"2b0493859691be843589c8b062e5e045085099f5"},"mode":"0100644","name":"app.css","size":2934},{"lastCommit":{"author":{"email":"claas@claas.dev","name":"Claas","when":"2026-08-06T09:09:35.000000+02:00"},"committer":{"email":"claas@claas.dev","name":"Claas","when":"2026-08-06T17:29:41.000000+02:00"},"hash":"316a0f76438414e6321d2debd9f60d4410436dbc","message":"Draw the commit graph\n\nThe history is an ordinary list of buttons. Each row owns a small SVG\nfor its lane segment, marked aria-hidden, over content that already\nreads correctly without it — a summary, an author, a , and a\nshort id. Row is a button because selecting a commit is an action and a\nbutton brings its own role, focus ring and Enter handling; that limits\nit to phrasing content, which is why ref badges are spans with a\nvisually hidden word for what each one is.\n\nTen lane colours come from one CSS rule rather than ten values: the\nlane index rotates an oklch hue, starting near the seed colour so the\ngraph belongs to the same palette as everything else. Nothing about\ncolour reaches the Rust side, and switching light to dark re-themes the\nwhole graph without a re-render.\n\nNothing here needs a virtual list. Rows arrive in batches as the end of\nthe list nears the viewport, so the DOM only holds what has been\nscrolled to, and rows past the first forty get content-visibility so\nthe browser skips laying out and painting the rest. `none` for the\nintrinsic width keeps an off-screen row from collapsing horizontally,\nwhich would make the scroll width jump on a wide graph. Which rows are\ndeferred is decided by nth-child, so no JavaScript is involved.\n\nWide graphs scroll rather than compress. A graph's width comes from the\nhistory — aspnetcore lays out 115 columns — so no window size makes it\nfit and capping would only hide branches.\n\nTwo things caught while driving the real components in a browser:\n\n- Five arrow presses moved the selection one row. Solid 2 batches\n signal writes, so reading selected() to compute the next value goes\n stale when presses land in one batch. Now the update goes through the\n functional setter, which sees the pending value.\n- jsx-a11y assumes React's htmlFor, so Solid's plain `for` read as an\n unassociated label. Configured rather than worked around.\n\nSafari drops list semantics from a list styled with list-style: none,\nwhich Tailwind's preflight applies — and Tauri is WKWebView on macOS,\nso that is the default here. An empty-string marker renders nothing and\nleaves the list a list, which beats patching the role back with ARIA.\n\nOpening is a path field for now. A native folder picker needs the Tauri\ndialog plugin, which is a dependency this change does not need; the\npicker arrives with the repository-picker work.\n\nInfinite scrolling is not verified yet — IntersectionObserver does not\nrun in a hidden document, and the browser pane available here cannot\nmake one visible. The Playwright harness covers it next.\n\nCo-Authored-By: Claude Opus 5 \n","tree":"2b0493859691be843589c8b062e5e045085099f5"},"mode":"0040000","name":"components","size":0},{"lastCommit":{"author":{"email":"claas@claas.dev","name":"Claas","when":"2026-08-06T01:05:49.000000+02:00"},"committer":{"email":"claas@claas.dev","name":"Claas","when":"2026-08-06T17:29:37.000000+02:00"},"hash":"39172c3e042f42852a348f49638697401ac6001f","message":"Set up the frontend toolchain and app shell\n\nReplaces the create-tauri-app demo with the toolchain the project will\nactually use, and a shell to hang the real UI off.\n\n- Solid 2.0 beta. The JSX runtime moved to @solidjs/web, so jsxImportSource\n and the render import point there now. @solidjs/signals is a direct\n dependency so resolve.dedupe can actually resolve it under pnpm —\n more than one copy of the Solid packages causes reactivity bugs that\n are painful to trace.\n- TypeScript 7, the native compiler. Type-checking only; Vite transpiles.\n- Tailwind v4 with CSS-first config, plus @claas.dev/material-tailwind to\n generate the Material 3 colour system from a single seed. The plugin\n emits every colour as light-dark(), so light and dark themes work with\n no dark: variants at all — only a color-scheme declaration.\n- oxlint and oxfmt instead of ESLint and Prettier, with Tailwind class\n sorting pointed at src/app.css. Verified it resolves plugin-generated\n utilities, not just core Tailwind ones. jsx-a11y is enabled and works\n on Solid's JSX; react is deliberately off. Vendored skill files and\n Tauri's generated JSON are excluded from formatting.\n\nThe shell is landmarks and headings only: banner, a labelled navigation\nsidebar, main, and a contentinfo status bar with an live region.\nA skip link targets main, which takes tabindex=\"-1\" so focus actually\nmoves rather than only scrolling.\n\nThe scaffold's greet command in src-tauri is left alone; the repository\nactor change replaces it.\n\nCo-Authored-By: Claude Opus 5 \n","tree":"2a0be45da83e293c31775c2ec079aaac96764aed"},"mode":"0100644","name":"index.tsx","size":262},{"lastCommit":{"author":{"email":"claas@claas.dev","name":"Claas","when":"2026-08-06T09:09:35.000000+02:00"},"committer":{"email":"claas@claas.dev","name":"Claas","when":"2026-08-06T17:29:41.000000+02:00"},"hash":"316a0f76438414e6321d2debd9f60d4410436dbc","message":"Draw the commit graph\n\nThe history is an ordinary list of buttons. Each row owns a small SVG\nfor its lane segment, marked aria-hidden, over content that already\nreads correctly without it — a summary, an author, a , and a\nshort id. Row is a button because selecting a commit is an action and a\nbutton brings its own role, focus ring and Enter handling; that limits\nit to phrasing content, which is why ref badges are spans with a\nvisually hidden word for what each one is.\n\nTen lane colours come from one CSS rule rather than ten values: the\nlane index rotates an oklch hue, starting near the seed colour so the\ngraph belongs to the same palette as everything else. Nothing about\ncolour reaches the Rust side, and switching light to dark re-themes the\nwhole graph without a re-render.\n\nNothing here needs a virtual list. Rows arrive in batches as the end of\nthe list nears the viewport, so the DOM only holds what has been\nscrolled to, and rows past the first forty get content-visibility so\nthe browser skips laying out and painting the rest. `none` for the\nintrinsic width keeps an off-screen row from collapsing horizontally,\nwhich would make the scroll width jump on a wide graph. Which rows are\ndeferred is decided by nth-child, so no JavaScript is involved.\n\nWide graphs scroll rather than compress. A graph's width comes from the\nhistory — aspnetcore lays out 115 columns — so no window size makes it\nfit and capping would only hide branches.\n\nTwo things caught while driving the real components in a browser:\n\n- Five arrow presses moved the selection one row. Solid 2 batches\n signal writes, so reading selected() to compute the next value goes\n stale when presses land in one batch. Now the update goes through the\n functional setter, which sees the pending value.\n- jsx-a11y assumes React's htmlFor, so Solid's plain `for` read as an\n unassociated label. Configured rather than worked around.\n\nSafari drops list semantics from a list styled with list-style: none,\nwhich Tailwind's preflight applies — and Tauri is WKWebView on macOS,\nso that is the default here. An empty-string marker renders nothing and\nleaves the list a list, which beats patching the role back with ARIA.\n\nOpening is a path field for now. A native folder picker needs the Tauri\ndialog plugin, which is a dependency this change does not need; the\npicker arrives with the repository-picker work.\n\nInfinite scrolling is not verified yet — IntersectionObserver does not\nrun in a hidden document, and the browser pane available here cannot\nmake one visible. The Playwright harness covers it next.\n\nCo-Authored-By: Claude Opus 5 \n","tree":"2b0493859691be843589c8b062e5e045085099f5"},"mode":"0040000","name":"lib","size":0},{"lastCommit":{"author":{"email":"claas@claas.dev","name":"Claas","when":"2026-08-05T23:11:46.000000+02:00"},"committer":{"email":"claas@claas.dev","name":"Claas","when":"2026-08-05T23:11:46.000000+02:00"},"hash":"30d6fc6273d153ec656cd3d6673037d1e74ee756","message":"Scaffold tauri project\n","tree":"57f5c1afe32dc29a10085f8742a5a8205e0b9d37"},"mode":"0100644","name":"vite-env.d.ts","size":38}],"lastCommit":{"author":{"email":"claas@claas.dev","name":"Claas","when":"2026-08-06T09:21:27.000000+02:00"},"committer":{"email":"claas@claas.dev","name":"Claas","when":"2026-08-06T17:29:41.000000+02:00"},"hash":"04ee93bf05a24f9feb8509925b2e646896e95780","message":"Make the skip control reachable in WebKit\n\nWebKit leaves links out of the tab order unless the system's keyboard\nnavigation setting is on, and that setting is off by default. On macOS\nthe app runs in WKWebView, so a skip link written as an anchor is a skip\nlink nobody can reach with the keyboard — which is the one thing a skip\nlink exists to be.\n\nTab order, measured in both engines against the running app:\n\n chromium A \"Skip to history\" -> input -> button\n webkit input -> button (the link is never focused)\n\nA button is tabbable everywhere and moves focus explicitly, so it does\nthe job in both. The end-to-end tests that found this run next.\n\nCo-Authored-By: Claude Opus 5 \n","tree":"439b4c80d805c9f8b3f340db5475c4217c9c1222"}}