{"entries":[{"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":"App.tsx","size":1624},{"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":"app.css","size":798},{"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":"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-06T02:08:07.000000+02:00"},"committer":{"email":"claas@claas.dev","name":"Claas","when":"2026-08-06T17:29:41.000000+02:00"},"hash":"42ba5306561a8b3fc7fbbf0ef2793c075a0692fa","message":"Stream graph rows over an IPC channel\n\nRows are pushed to the frontend rather than returned page by page, and\nthe push is bounded by a budget the frontend tops up as it scrolls.\n\nCredit-based flow control rather than request/response, because a plain\nrequest/response costs a round trip before anything can be drawn and\nleaves the backend unable to speak on its own — which is what pushing\nnewly arrived commits into an open view will need later. The budget is\nwhat keeps a million-commit repository from flooding the boundary: the\nwalk computes nothing beyond what has been asked for.\n\nCancellation falls out of the design. A channel the webview has dropped\nmakes the send fail, which ends the stream and drops the walk; closing\nthe repository drops its actor, which drops the walk with it. There is\nnothing to clean up explicitly. One stream per repository — starting\nanother replaces it, and the previous walk is dropped there.\n\nTwelve tests cover the flow control against the real streaming code:\nChannel takes a plain closure, so what the test observes is exactly what\nwould have crossed the boundary. They pin the budget being respected,\nresuming without repeating or skipping a row, batches carrying their\nstart index, the end of history being announced, a replaced stream going\nquiet while the new one continues, and asking for more after the end\nbeing a harmless no-op rather than an error.\n\nThe TypeScript bindings are written by hand — the surface is small and a\ngenerator is another dependency to keep current. One of the Rust tests\nasserts the wire format matches the names in bindings.ts, so drift on\none side fails on the other.\n\nAlso suppresses unicorn/prefer-add-event-listener at the one place it\nmisfires: Tauri's Channel is not an EventTarget, so onmessage is the\nonly way to receive from it.\n\nCo-Authored-By: Claude Opus 5 \n","tree":"243f612508dab3381835b725249be597a89c593f"},"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-06T02:08:07.000000+02:00"},"committer":{"email":"claas@claas.dev","name":"Claas","when":"2026-08-06T17:29:41.000000+02:00"},"hash":"42ba5306561a8b3fc7fbbf0ef2793c075a0692fa","message":"Stream graph rows over an IPC channel\n\nRows are pushed to the frontend rather than returned page by page, and\nthe push is bounded by a budget the frontend tops up as it scrolls.\n\nCredit-based flow control rather than request/response, because a plain\nrequest/response costs a round trip before anything can be drawn and\nleaves the backend unable to speak on its own — which is what pushing\nnewly arrived commits into an open view will need later. The budget is\nwhat keeps a million-commit repository from flooding the boundary: the\nwalk computes nothing beyond what has been asked for.\n\nCancellation falls out of the design. A channel the webview has dropped\nmakes the send fail, which ends the stream and drops the walk; closing\nthe repository drops its actor, which drops the walk with it. There is\nnothing to clean up explicitly. One stream per repository — starting\nanother replaces it, and the previous walk is dropped there.\n\nTwelve tests cover the flow control against the real streaming code:\nChannel takes a plain closure, so what the test observes is exactly what\nwould have crossed the boundary. They pin the budget being respected,\nresuming without repeating or skipping a row, batches carrying their\nstart index, the end of history being announced, a replaced stream going\nquiet while the new one continues, and asking for more after the end\nbeing a harmless no-op rather than an error.\n\nThe TypeScript bindings are written by hand — the surface is small and a\ngenerator is another dependency to keep current. One of the Rust tests\nasserts the wire format matches the names in bindings.ts, so drift on\none side fails on the other.\n\nAlso suppresses unicorn/prefer-add-event-listener at the one place it\nmisfires: Tauri's Channel is not an EventTarget, so onmessage is the\nonly way to receive from it.\n\nCo-Authored-By: Claude Opus 5 \n","tree":"243f612508dab3381835b725249be597a89c593f"}}