Mooring 0.11.0

Your sidebar can now tell you what state a branch is in — ready for merge, needs rebase, or whatever states you define — without opening anything. Release versions became usable at last, the Tips window and the Claude Usage chart both stopped wasting the space they were given, and the backlog stopped re-counting itself every time you typed.

Say what state a worktree's branch is in

• Right-click a worktree and choose Mark As to set it Ready for merge or Needs rebase. The state renders on the worktree row in its own themed colour, so the sidebar tells you what is waiting for review at a glance.
• A state describes the branch, not one card. Setting one from any surface writes it to every card linked to that branch, and reading takes the union — so a branch with several cards cannot disagree with itself about its own state. There are four places to see or set one: the worktree row, the Mark As submenu, a section in the card window, and Claude.
• The vocabulary is yours. Settings ▸ Worktrees ▸ Custom states lets you add, rename, recolour or delete states. Renaming updates every use at once, and deleting one that is in use asks first and never erases it from your cards.
• States clear themselves on merge, so a merged branch stops advertising that it is ready for review.
• Claude can read and set them by name or id, and they survive backup and restore — including across machines, where states are matched by name when their ids differ.
• ⌘Z undoes setting or clearing a state, reverting every card on the branch in one step.

Name a release version straight from a card

• Versions were impossible to use. A card's Release and Fix pickers listed the versions a project already had, and nothing anywhere in Mooring could create the first one — so in every project both menus offered only None, and the backlog's version filter never had anything to show. Type a name in the picker now and the version is created and assigned in one step.
• Retyping a name you already have picks the existing version rather than making a duplicate, and versions stay per-project, so "0.11.0" in one project is separate from "0.11.0" in another.

The Tips window fills a large display

• Help ▸ Tips used to put a narrow column of text in the top-left corner and leave the rest of the window blank — on a large display, often more than half the window doing nothing. Tips now opens on All Tips: every tip as a card, grouped by category, in a grid that reflows to whatever width the window has.
• A tip's own page ends with the rest of its category as cards rather than a short list of links, so the space below the prose carries something worth reading.
• Searching shows its results in the main pane, instead of filtering the sidebar while the pane kept showing an unrelated tip — and it says so plainly when nothing matches.
• The sidebar can be dragged wider, so long titles stop truncating.

Claude Usage opens on today, at a readable scale

• The chart used to open parked at the oldest transcript you had, not today. With usage going back months, the window opened on the oldest month and today sat off-screen. It now shows a trailing window that always ends at the current hour or day, so the most recent work is at the right-hand edge whenever you open it.
• Amounts no longer look microscopic. The vertical axis was scaled to your all-time peak, so a busy hour anywhere in history flattened every other view. The axis now fits the range you are actually looking at.
• A new Range control sets how far back to look — 12h / 24h / 3d / 7d when hourly, 7d / 30d / 90d when daily, and All on both to reach your full history.
• Axis labels and day boundaries follow your local calendar and time zone, including on the two days a year that are 23 or 25 hours long.
• With "Estimated cost" ticked, the colour key no longer lists token categories that cost mode doesn't draw. Empty ranges now say so and point at the Range control. The window also opens larger, so its controls row no longer wraps a label to "Ra/ng/e".

The card window's rail reads as one thing

• The rail had grown nine sections speaking two different visual languages — small uppercase headings for some, large bold title-case for others. Every section now uses the same heading treatment, with the accent colour and a ✦ reserved for the on-device AI sections so generated content stays distinguishable from what you typed.
• One control per section, always a glyph with a tooltip, replacing four different trailing treatments. Mark As loses its "Edit" wording for a gear, which also removes a real ambiguity — the card body's "Edit" links edit a field in place, whereas this one opens Settings.
• Sections badge how many items the card has, and only when there are some. Sections you can add to keep their heading and say "No … yet"; purely derived sections hide themselves entirely.
• Fixed: rail values ignored your theme. Status and Priority took their colour from the macOS control tint rather than the active theme's accent — invisible on blue-accented themes, but on Kelp or Dusk the rail's two most prominent values rendered system blue against a differently coloured app. All rail values now use the theme's accent.

Performance

• The backlog pane stopped re-counting everything on every keystroke. Typing in the backlog, dragging the Favourites divider, and editing any card anywhere in the app all made the backlog re-tally itself — it appeared in four of seven high-CPU samples on 0.10.0. Three separate causes, all fixed, with no change to the numbers, filters, chips or search results.
• The file tree no longer stutters during heavy git churn. Switching branches, or any burst changing many files at once, could briefly pin a CPU core: every visible row re-derived its own path on every published change, and every visible row rebuilt its entire right-click menu continuously. Measured on a branch-switch burst, work in the row-render path fell 45%.

Also fixed

• An expanded card showed its tags twice — two strips, one of which appeared to gain the tag when you accepted a suggestion. Now there is one strip, below the attachment icons, with the suggestions.
• The worktree right-click menu no longer offers Show Card in Backlog when no card is linked to that worktree, where choosing it did nothing.
• Naming a version on a card that belongs to no project — a global template or draft — no longer strands an unusable version that no project could see or reuse, whether it came from Claude or from importing a backup.
• The pre-existing attention toggles are now Flag for Attention / Clear Attention, so "Mark as…" means exactly one thing in that menu.