Format

Author: vdavid

.claude/rules/docs-maintenance.md

@@ -4,11 +4,11 @@ paths:
 ---
 
 When modifying code in a directory that contains a `CLAUDE.md` file, check whether your changes affect the documented
-architecture, key decisions, or gotchas. If they do, update the `CLAUDE.md` to stay in sync.
-If you notice a `CLAUDE.md` missing in a directory where there should be one, add it.
-Skip this for trivial changes (bug fixes, formatting, small refactors that don't change the architecture).
+architecture, key decisions, or gotchas. If they do, update the `CLAUDE.md` to stay in sync. If you notice a `CLAUDE.md`
+missing in a directory where there should be one, add it. Skip this for trivial changes (bug fixes, formatting, small
+refactors that don't change the architecture).
 
 If something failed due to a wrong assumption, add a `Gotcha/Why` entry to the nearest `CLAUDE.md`.
 
-Add `Decision/Why` entries to the nearest colocated `CLAUDE.md` for key decisions. If the decision has rich
-evidence (benchmarks, detailed analysis), put the evidence in `docs/notes/` and link from the CLAUDE.md.
+Add `Decision/Why` entries to the nearest colocated `CLAUDE.md` for key decisions. If the decision has rich evidence
+(benchmarks, detailed analysis), put the evidence in `docs/notes/` and link from the CLAUDE.md.

docs/architecture.md

@@ -1,57 +1,54 @@
 # Architecture
 
-High-level map of loc-counter's subsystems. Each row links to the colocated
-CLAUDE.md that contains the full details.
+High-level map of loc-counter's subsystems. Each row links to the colocated CLAUDE.md that contains the full details.
 
 ## Frontend (`src/lib/`)
 
 Details: [`src/lib/CLAUDE.md`](../src/lib/CLAUDE.md)
 
-| Module | Purpose |
-|---|---|
-| `components/` | Svelte UI — `ResultsChart`, `ResultsTable`, `ResultsSummary`, `PipelineProgress`, `RepoInput`, era-markers plugin |
-| `git/clone.ts` | Clone/fetch via isomorphic-git + lightning-fs, abort support, staleness monitor |
-| `git/history.ts` | Commit log grouped by date, batch fetching, `CompactOidSet` dedup |
-| `git/count.ts` | Line counting per tree, prod/test classification, blob dedup, incremental tree diffing |
-| `git/mailmap.ts` | `.mailmap` parsing and author normalization |
-| `worker/` | Web Worker entry point (Comlink) — orchestrates full and incremental analysis pipelines |
-| `types.ts` | Shared interfaces (`LanguageCount`, `DayStats`, `AnalysisResult`, `ProgressEvent`, etc.) |
-| `languages.ts` | Language registry (~35 languages), extension mapping, inline test detection |
-| `cache.ts` | IndexedDB results cache — LRU eviction, 500 MB limit, separate meta store |
-| `server-cache.ts` | Shared server cache client (opt-in via `PUBLIC_SHARED_CACHE_URL`) |
-| `url.ts` | Repo URL parsing and normalization (GitHub/GitLab/Bitbucket, owner/repo shorthand) |
-
-The SvelteKit app itself lives in `src/routes/` (single page) with global styles
-in `src/app.css` (Tailwind v4 + CSS custom properties).
+| Module            | Purpose                                                                                                           |
+| ----------------- | ----------------------------------------------------------------------------------------------------------------- |
+| `components/`     | Svelte UI — `ResultsChart`, `ResultsTable`, `ResultsSummary`, `PipelineProgress`, `RepoInput`, era-markers plugin |
+| `git/clone.ts`    | Clone/fetch via isomorphic-git + lightning-fs, abort support, staleness monitor                                   |
+| `git/history.ts`  | Commit log grouped by date, batch fetching, `CompactOidSet` dedup                                                 |
+| `git/count.ts`    | Line counting per tree, prod/test classification, blob dedup, incremental tree diffing                            |
+| `git/mailmap.ts`  | `.mailmap` parsing and author normalization                                                                       |
+| `worker/`         | Web Worker entry point (Comlink) — orchestrates full and incremental analysis pipelines                           |
+| `types.ts`        | Shared interfaces (`LanguageCount`, `DayStats`, `AnalysisResult`, `ProgressEvent`, etc.)                          |
+| `languages.ts`    | Language registry (~35 languages), extension mapping, inline test detection                                       |
+| `cache.ts`        | IndexedDB results cache — LRU eviction, 500 MB limit, separate meta store                                         |
+| `server-cache.ts` | Shared server cache client (opt-in via `PUBLIC_SHARED_CACHE_URL`)                                                 |
+| `url.ts`          | Repo URL parsing and normalization (GitHub/GitLab/Bitbucket, owner/repo shorthand)                                |
+
+The SvelteKit app itself lives in `src/routes/` (single page) with global styles in `src/app.css` (Tailwind v4 + CSS
+custom properties).
 
 ## CORS proxy (`cors-proxy/`)
 
 Details: [`cors-proxy/CLAUDE.md`](../cors-proxy/CLAUDE.md)
 
-| Component | Purpose |
-|---|---|
-| Cloudflare Worker (Hono) | Adds CORS headers, forwards bytes to git hosts (GitHub, GitLab, Bitbucket) |
-| Rate limiting | Cloudflare edge rules + in-memory per-isolate counters |
-| Ref caching | Caches v1 `/info/refs` responses at the edge (12 h TTL) |
-| Shared results cache | Optional R2-backed cache for analysis results (`GET`/`PUT /cache/v1/:repoHash`) |
+| Component                | Purpose                                                                         |
+| ------------------------ | ------------------------------------------------------------------------------- |
+| Cloudflare Worker (Hono) | Adds CORS headers, forwards bytes to git hosts (GitHub, GitLab, Bitbucket)      |
+| Rate limiting            | Cloudflare edge rules + in-memory per-isolate counters                          |
+| Ref caching              | Caches v1 `/info/refs` responses at the edge (12 h TTL)                         |
+| Shared results cache     | Optional R2-backed cache for analysis results (`GET`/`PUT /cache/v1/:repoHash`) |
 
 ## Tooling
 
-| Directory | Purpose |
-|---|---|
-| `scripts/` | Go-based check runner |
-| `tests/` | Vitest (unit) + Playwright (e2e) |
-| `shared/` | `language-ids.ts` — single source of truth for valid language IDs, imported by both frontend and CORS proxy |
+| Directory  | Purpose                                                                                                     |
+| ---------- | ----------------------------------------------------------------------------------------------------------- |
+| `scripts/` | Go-based check runner                                                                                       |
+| `tests/`   | Vitest (unit) + Playwright (e2e)                                                                            |
+| `shared/`  | `language-ids.ts` — single source of truth for valid language IDs, imported by both frontend and CORS proxy |
 
 ## Cross-cutting patterns
 
-- **Web Worker isolation** — All git operations and line counting run in a
-  dedicated Web Worker (via Comlink). The main thread only drives the UI.
-- **Diff-based incremental processing** — After the first commit's full tree
-  walk, every subsequent commit uses recursive tree diffing (`diffTreesDetailed`)
-  so only changed files are re-counted.
-- **IndexedDB caching with LRU eviction** — Analysis results are cached
-  client-side in IndexedDB with a 500 MB cap. A separate lightweight meta store
-  enables eviction and size checks without deserializing full results.
-- **Incremental refresh** — `analyzeIncremental` fetches only new commits since
-  the last cached result and merges the new days in.
+- **Web Worker isolation** — All git operations and line counting run in a dedicated Web Worker (via Comlink). The main
+  thread only drives the UI.
+- **Diff-based incremental processing** — After the first commit's full tree walk, every subsequent commit uses
+  recursive tree diffing (`diffTreesDetailed`) so only changed files are re-counted.
+- **IndexedDB caching with LRU eviction** — Analysis results are cached client-side in IndexedDB with a 500 MB cap. A
+  separate lightweight meta store enables eviction and size checks without deserializing full results.
+- **Incremental refresh** — `analyzeIncremental` fetches only new commits since the last cached result and merges the
+  new days in.

docs/style-guide.md

@@ -6,8 +6,8 @@ Writing and code styles.
 
 - Wording
     - **Use a friendly style**: Make all texts informal, friendly, encouraging, and concise.
-    - **Always prefer active voice**: Active voice is direct and clear. Passive voice feels bureaucratic.
-      "We released a new feature" not "A new feature was released." "Add a repo" not "A repo can be added."
+    - **Always prefer active voice**: Active voice is direct and clear. Passive voice feels bureaucratic. "We released a
+      new feature" not "A new feature was released." "Add a repo" not "A repo can be added."
     - **Use verbs, not verb-noun phrases**: "Search" not "Make a search." "Analyze" not "Perform an analysis."
     - **Don't use permissive language**: Give users confidence. "Add repos and start searching" not "Add repos and you
       can start searching."
@@ -37,19 +37,19 @@ Writing and code styles.
     - **Use ISO dates**: Use YYYY-MM-DD wherever it makes sense.
 - UI
     - Make **error messages** positive, actionable, and specific.
-    - **Success messages**: Talk about the user, not the action. Make success implicit and warm.
-      "You're in!" not "Login successful." "Repo added" not "The repository has been successfully added."
+    - **Success messages**: Talk about the user, not the action. Make success implicit and warm. "You're in!" not "Login
+      successful." "Repo added" not "The repository has been successfully added."
     - **Confirmation dialogs**: Title should be a verb+noun question ("Delete this repo?"). Body should be a plain
       irreversibility warning ("This can't be undone."). Buttons should be outcome verbs ("Delete" / "Keep"), never
       "Yes" / "No".
-    - **Empty states**: Say what belongs here and offer a next step.
-      "No repos yet. Add one to start tracking lines of code."
+    - **Empty states**: Say what belongs here and offer a next step. "No repos yet. Add one to start tracking lines of
+      code."
     - **Start UI actions with a verb**: This makes buttons and links more actionable. Use "Create user" instead of "New
       user".
-    - **Link the destination, not the sentence**: Only link text that describes where you'll go.
-      "Read the [style guide](...)." not "[Read the style guide](...)."
-    - **Helper text**: Only add helper text if users actually need it. Keep it short and specific.
-      "Must be a valid GitHub URL" not "Please enter the URL of the GitHub repository you would like to add."
+    - **Link the destination, not the sentence**: Only link text that describes where you'll go. "Read the
+      [style guide](...)." not "[Read the style guide](...)."
+    - **Helper text**: Only add helper text if users actually need it. Keep it short and specific. "Must be a valid
+      GitHub URL" not "Please enter the URL of the GitHub repository you would like to add."
     - **Give examples in placeholder text**: Use "Example: 2025-01-01" or "name@example.com" rather than an instruction
       like "Enter your email".
     - **Never write "something(s)"**: Always pluralize dynamically: "1 user" instead of "1 user(s)".