@poodle64/ui 2026.10.3 → 2026.10.4

package/README.md

@@ -911,9 +911,11 @@ Settled here, the same in every module, and not props:
   above its card; figures in the body face with tabular numerals, money out
   bracketed and money in green (`formatCurrency(v, { negative: 'brackets' })`).
 - **Sorting and the groups' one control.** Click a column head to sort by it,
-  largest or newest first; click again to reverse. A sorted list is one flat
-  run with no group heads and shows the Date column even by day. Until the
-  viewer sorts, rows sit newest first in their groups. A chevron in the head's
+  largest or newest first; click again to reverse; a third click returns to the
+  default order. A sort orders rows inside the grouping the viewer chose (the
+  groups stay newest first); grouped by none, the list is one flat run. The
+  head shows its state: a down chevron descending, an up chevron ascending,
+  none at rest. Until the viewer sorts, rows sit newest first. A chevron in the head's
   gutter opens or closes every group at once; where rows tick, the gutter
   widens to hold it beside the select-all checkbox.
 - **The Columns menu** holds every column as a tick, the three fixed ones

package/dist/components/ui/ledger/ledger.svelte

@@ -220,9 +220,9 @@
 	/** What a column sorts by; the running balance depends on the order, so never it. */
 	const sorter = (c: { key: string; sort?: LedgerColumn<R>['sort']; text?: LedgerColumn<R>['text'] }) =>
 		c.key === 'balance' ? undefined : (c.sort ?? c.text);
-	/** Click a head to sort by it, largest or newest first; again to reverse. */
+	/** Click a head to sort by it, largest or newest first; again to reverse; a third time back to the default order. */
 	function sortBy(key: string) {
-		sort = sort?.key === key ? { key, dir: sort.dir === 1 ? -1 : 1 } : { key, dir: -1 };
+		sort = sort?.key !== key ? { key, dir: -1 } : sort.dir === -1 ? { key, dir: 1 } : null;
 	}
 	/** The sort in force: a column the viewer has since unticked no longer sorts. */
 	const activeSort = $derived.by(() => {
@@ -231,8 +231,8 @@
 			? sort
 			: null;
 	});
-	/** Until the viewer sorts, rows sit newest first in their period's groups. */
-	const grouped = $derived(prefs.period !== 'none' && !activeSort);
+	/** A sort orders rows inside their period's groups; only `none` is the flat list. */
+	const grouped = $derived(prefs.period !== 'none');
 	const BY_DAY = $derived(grouped && prefs.period === 'day');
 
 	const shown = $derived(
@@ -262,8 +262,9 @@
 	});
 	const groups = $derived.by(() => {
 		const by = activeSort && sorter(resolved.find((c) => c.key === activeSort.key)!);
-		if (activeSort && by) return [{ key: '', rows: sortRows(rows, by, activeSort.dir) }];
-		return groupRows(rows, prefs.period, fy);
+		const base = groupRows(rows, prefs.period, fy);
+		if (!activeSort || !by) return base;
+		return base.map((g) => ({ key: g.key, rows: sortRows(g.rows, by, activeSort.dir) }));
 	});
 	/** Closed groups, keyed with their period so a new period starts open. */
 	const closed = new SvelteSet<string>();
@@ -923,7 +924,7 @@
 									mine && 'text-foreground'
 								)}
 								aria-label={mine
-									? `Sorted by ${c.label}, ${mine.dir === -1 ? 'descending' : 'ascending'}. Click to reverse`
+									? `Sorted by ${c.label}, ${mine.dir === -1 ? 'descending' : 'ascending'}. Click ${mine.dir === -1 ? 'to reverse' : 'for the default order'}`
 									: `Sort by ${c.label}`}
 								onclick={() => sortBy(c.key)}
 								data-slot="ledger-sort"

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@poodle64/ui",
-	"version": "2026.10.3",
+	"version": "2026.10.4",
 	"description": "Household shared component layer: shadcn-svelte primitives (bits-ui) plus the composed page chrome every app builds its routes from, restyled by each app's @poodle64/design-tokens alias layer. One fix reaches every app.",
 	"type": "module",
 	"license": "MIT",

package/registry/component-map.json

@@ -1,7 +1,7 @@
 {
 	"meta": {
 		"package": "@poodle64/ui",
-		"version": "2026.10.3",
+		"version": "2026.10.4",
 		"generatedBy": "scripts/generate-registry.mjs",
 		"source": "scripts/situations.json + package source (DO NOT EDIT the outputs by hand)",
 		"componentCount": 62,

package/registry/component-map.md

@@ -1,7 +1,7 @@
 # @poodle64/ui — situation → component map
 
 <!-- GENERATED by scripts/generate-registry.mjs from scripts/situations.json + package source. DO NOT EDIT. -->
-Generated from `@poodle64/ui@2026.10.3`. 62 components, 18 situations.
+Generated from `@poodle64/ui@2026.10.4`. 62 components, 18 situations.
 
 **Read this before writing a `<div>`.** Find the SITUATION you are in below, then compose the component named for it — do not hand-build it from raw `Card` or utility classes. Import is `import { Name } from '<import path>'`. Props marked `?` are optional. This map is the retrieval step the [`frontend-design` skill] makes mandatory; the [CHI 2026 study] measured composing-from-a-registry at 95% design-system compliance against 71% for writing the CSS from a prose style guide.