Sundry
A holding pen for small, miscellaneous items to work on that don't (yet) warrant their own Atlas note.
Most work earns a dedicated Atlas note — a bug with a root cause, a feature with a design, an analysis with measurements. Sundry is the holding pen for everything too small for that: a one-line idea, a chore, a “we should look at this” that would be overkill as its own note. Jot it down here so it isn’t lost, and when an item grows a real shape, graduate it to its own note.
What belongs here
An item belongs in Sundry when it’s real work but not yet note-sized — there is no design to argue, no root cause to diagnose, no measurement to report. The bar is deliberately low: a single row with a what and a goal is enough. The moment an item needs more than that — a diagram, a repro, a plan, a debate — it has outgrown Sundry (see Graduating an item).
Backlog
No open items.
The item Unify the two Dock activity dots graduated to the roadmap as
R-activity-merge — it grew a real
shape (a shared nested indicator across the Dock and pulam-web, plus retiring the
drifted #7ee787 from #1551). The item Distinguish the active terminal in a
split graduated to its own note — Distinguish the Active Terminal in a
Split.
Overnight loops
Items here are self-contained enough to hand to an autonomous overnight run — a clear target, a public reference to follow, and a definition of done an agent can check itself against without a human in the loop.
No open items. The Upgrade to Vite 8.1, repo-wide loop shipped in
#1543: every Vite-built surface is on
8.1 (Rolldown/Oxc bundler), all surfaces build, and just dev runs — confirmed
via chrome-devtools (kolu loads, connects, creates a working terminal). The
experimental bundled dev mode was evaluated and not adopted: on 8.1.0 it
crashes kolu’s client with __reExport is not defined so the app never mounts —
a known cluster of bundledDev runtime-ReferenceError bugs upstream
(vite#22419,
vite#22012); revisit when fixed.
The build-output experiments (chunk import map, Wasm-as-build) were left off for
nix build reproducibility; the stable features (import.meta.glob
caseSensitive, Wasm ESM, html.additionalAssetSources) had no call sites.
Graduating an item
When a Sundry item earns a design, a repro, or a plan, it has stopped being
sundry. Create a real note under its true index (parents: [bug], [feature],
[analysis], or [reference]), move the substance there, and delete the row
here — keeping a one-line prose pointer only if the link is worth following.
Sundry should stay short: a long list is a signal that items are being hoarded
instead of either done or promoted.