v1.2.1

One fix, in the Health view. Flagged hideFromModal in the index: it counts toward the version number and shows in Config → Overview → Latest update, but does not reopen the What's new modal, which still leads with v1.2.0. DASHBOARD_RELEASE and NEXTDASH_WHATS_NEW_DATA_VERSION are deliberately unchanged — those two tokens are what re-show the modal, and a one-fix release should not push a feature release off the front of it for everyone who has already read it.

What's new

• fix — usage no longer decides where a row sits. never_opened and not_opened_30_days cost 10 points each, so opening a bookmark — the action the Broken filter's own note asks for — raised its score, and under the default worst-first sort carried the row away: measured on a 200-bookmark install, position 10 of 200 became position 188 while the reader was still working through the list. Both penalties are 0 now; the flags, the Unused and Stale tiles and filters, and the reason text on the row are unchanged.
• fix — the score sort's tiebreak reads the flags with the two usage ones removed (stableStatusRank) rather than the status. Status alone was not enough: opening a never-opened row that also has no preview turns unused into missing-preview, a different rank, and the row travels on that instead.
• fix — a row you have acted on keeps its position. Opening one under Unused, or re-checking one under Broken, takes it out of what the filter selects, and the list used to close the gap under the cursor. It stays at the position it held, dimmed and marked handled, until the list is asked a different question (filter, sort, search) or reloaded on purpose with R or Retest all — and when the view is left.
• new — the score breakdown separates deductions from context: reasons that cost nothing are listed under worth knowing, at no cost to the score, because a full score with a deduction printed beneath it reads as broken arithmetic.

Docs

• static/data/whats-new/v1.2.1.json, and the index entry ahead of v1.2.0 carrying hideFromModal: true.
• tests/health-list-stability.spec.js pins both halves against the real UI path — the row's own Open — and compares positions against the rows whose own score did not move, so a startup check landing mid-test cannot pass for a re-ranking. Both halves were falsified: restoring the penalties fails the score assertion, removing the anchoring fails the position one.
• tests/whats-new-hidden-release.spec.js: the real-index case flips to asserting v1.2.1 is hidden and that v1.2.0 still leads the modal; the constants case now asserts the two tokens are unchanged, and says why that is right here where bumping was right for v1.2.0. The four fixture-driven cases are untouched.
• MANUAL.md and README.md: the score breakdown no longer lists the two usage penalties, and both describe the handled row and the sort key nothing can move.

v1.2.0 — 16 August 2026

The keyboard release, and the one where three views stop lying about what they know. Typing on the dashboard used to open bookmarks mid-word; the inbox counted links it was not showing; a failed health check worked out its cause and threw it away. All three are now what they appear to be.

What's new

Typing and keys

• fix — typing on the grid no longer opens anything by itself. A bookmark shortcut fired the instant the typed query matched it exactly, so which of your words survived depended on which other bookmarks you owned: on a 200-shortcut install, eight of thirteen ordinary words were swallowed mid-word. Typing now narrows the list and Enter opens the top result, with the exact shortcut match leading it — one keystroke more, and stable against every bookmark you add later.
• fix — g, j and k no longer eat the first letter of a word. Letters reach the grid only while a row is selected (_letterMayActOnGrid); the arrows always pass, j/k stop propagation once they act, and the g/G chord paints data-grid-keys on the body instead of swallowing the keystroke. c is the documented exception: it still creates a category unconditionally, because four specs pin that behaviour deliberately.
• new — the mode prefix is drawn in front of the query line (> search, : commands, ? finders) with an × to clear it, and closeSearch() now clears #search-query instead of leaving the old text behind.
• new — an optional key legend under the bookmark grid, shown after the first keystroke and hidden again on Enter. Behavior → General → Show grid key legend, on for fresh installs (Settings.ShowGridKeyLegend).
• new — Show shortcut hints on toolbar icons is off for everyone, via a one-time migration (migrateShortcutTooltipsDefaultOff, marker ShortcutTooltipsOffMigrated). A default change alone would not have reached existing installs, which all carry the field in their stored settings.
• new — the shortcut field warns about the letter you are assigning: ShortcutKeys.gridKeyNote() says what the grid does with it and when, and usedShortcutsNote() lists the shortcuts the page has already spoken for.

Inbox

• fix — every count follows the active filter. filterBaseItems()/narrowItems() feed the tiles, the pills and the badge, Mark all read becomes Mark shown read while isNarrowed(), and the first tile is Active — asleep is deliberately excluded.
• fix — snoozed links have a footer saying how many are asleep and when the first wakes, and domainOptions() no longer offers a host whose only link is asleep.
• new — Import beside the CSV and JSON exports (openImportPicker, parseImportPayload, importFromFile), skipping links already present and reporting added / already there / rejected.
• new — markUnread(id) and a row-menu entry for it, and the fetched summary (previewDesc) is rendered on the row, searched, and carried into both exports.

Health

• fix — a failure records its class (failureClass, HealthSample.Fail) so DNS, timeout, refused, TLS, redirect and content failures reach the incident list, the timeline and the CSV with a reason. Anything that was not an HTTP error stored Up:false, Code:0 and showed nothing.
• fix — a failed check is re-probed after monitorConfirmDelay and only recorded if it fails again, so one dropped check no longer dents a month of uptime.
• fix — buildMonitorStats reports CoveredMs, and renderUptimeTiles prints how much history is behind a window rather than labelling a week "30 days".
• new — certificate expiry comes from every check: liveHosts now includes CheckStatus bookmarks, not only monitored ones.
• new — a recovery names its duration, TREND_SERIES gives the trend chart six series with a per-mode axis, /api/health/expectations-bulk mutes or unmutes a whole selection, and Settings.HealthCheckTimeoutSeconds replaces the fixed three-second dial timeout.

Search

• new — negation. parseSearchFilters produces filters.not, and matchesAdvancedFilters runs the positive keys then the negative ones, so tag:dev -status:pinned is expressible in the bar the way it always was in a collection rule.
• new — status:untagged, status:tagged, status:noted and status:unnoted; :trash as a command onto #config/data-backups/trash; and Ctrl/Cmd+Enter on a result opens in a new tab regardless of the standing preference.

Dashboard and config

• new — undo for moves: single (undoBookmarkCategoryMove) and cross-page bulk (undoBulkMoveToPage), each restoring from a snapshot so every bookmark returns to its own category. showGroupedNotification translated undoCallback into nothing — the bulk-delete undo it also gates has been dead since it shipped.
• new — category icons (openIconEditor, live preview into .category-title-icon) and Alt+←/→ to move a category, announced to screen readers.
• new — setting-art.js draws the settings whose subject is a shape (grid, spacing, margins, density, dots, type size, layout version, bar position, flow), in config and in help.
• fix — a settings change made elsewhere now reaches an open dashboard: fetchDataRevision tracks the settings revision (GetSettingsRevision) and routes a change through refreshAfterConfigSettingsUpdate.
• fix — a failed automatic backup is visible: autoBackupRunState records LastRunAt/LastRunError and the tile reports it.
• new — a bookmark row in config carries a page › category breadcrumb pill, each half filtering the list.
• new — fresh installs start on Retro CRT (defaultThemeID), with fold-all and shortcut hints off. Existing installs are untouched.
• new — the extension can send a link straight to the inbox: two context-menu entries, a quick-save-inbox command on Ctrl/Cmd+Shift+U, and tags carried through postInboxLink.

Docs

• static/data/whats-new/v1.2.0.json and the index entry ahead of v1.1.2. DASHBOARD_RELEASE (2026.08-dashboard-release-v1.2.0) and NEXTDASH_WHATS_NEW_DATA_VERSION (whats-new-v245) are both bumped: a feature release that left them alone would be announced to nobody who had already dismissed v1.1.2.
• tests/whats-new-hidden-release.spec.js: the real-index and constants cases move to v1.2.0. The four fixture-driven hideFromModal cases are untouched.
• Config → Overview gains three feature spotlights — typing filters/Enter opens, the health failure reason, and the inbox counts — with their five locale keys each in en/nl/de/fr.
• MANUAL.md and README.md carry the keyboard model, the inbox round, the health engine and the new settings; Config → Help and the printable cheat sheet were updated alongside them.

v1.1.2 — 15 August 2026

A release that exists to announce the one before it. v1.1.1 shipped hideFromModal so it would not displace v1.1.0 on the day both landed; that call is reversed here.

...

v1.2.0

The keyboard release, and the one where three views stop lying about what they know. Typing on the dashboard used to open bookmarks mid-word; the inbox counted links it was not showing; a failed health check worked out its cause and threw it away. All three are now what they appear to be.

What's new

Typing and keys

• fix — typing on the grid no longer opens anything by itself. A bookmark shortcut fired the instant the typed query matched it exactly, so which of your words survived depended on which other bookmarks you owned: on a 200-shortcut install, eight of thirteen ordinary words were swallowed mid-word. Typing now narrows the list and Enter opens the top result, with the exact shortcut match leading it — one keystroke more, and stable against every bookmark you add later.
• fix — g, j and k no longer eat the first letter of a word. Letters reach the grid only while a row is selected (_letterMayActOnGrid); the arrows always pass, j/k stop propagation once they act, and the g/G chord paints data-grid-keys on the body instead of swallowing the keystroke. c is the documented exception: it still creates a category unconditionally, because four specs pin that behaviour deliberately.
• new — the mode prefix is drawn in front of the query line (> search, : commands, ? finders) with an × to clear it, and closeSearch() now clears #search-query instead of leaving the old text behind.
• new — an optional key legend under the bookmark grid, shown after the first keystroke and hidden again on Enter. Behavior → General → Show grid key legend, on for fresh installs (Settings.ShowGridKeyLegend).
• new — Show shortcut hints on toolbar icons is off for everyone, via a one-time migration (migrateShortcutTooltipsDefaultOff, marker ShortcutTooltipsOffMigrated). A default change alone would not have reached existing installs, which all carry the field in their stored settings.
• new — the shortcut field warns about the letter you are assigning: ShortcutKeys.gridKeyNote() says what the grid does with it and when, and usedShortcutsNote() lists the shortcuts the page has already spoken for.

Inbox

• fix — every count follows the active filter. filterBaseItems()/narrowItems() feed the tiles, the pills and the badge, Mark all read becomes Mark shown read while isNarrowed(), and the first tile is Active — asleep is deliberately excluded.
• fix — snoozed links have a footer saying how many are asleep and when the first wakes, and domainOptions() no longer offers a host whose only link is asleep.
• new — Import beside the CSV and JSON exports (openImportPicker, parseImportPayload, importFromFile), skipping links already present and reporting added / already there / rejected.
• new — markUnread(id) and a row-menu entry for it, and the fetched summary (previewDesc) is rendered on the row, searched, and carried into both exports.

Health

• fix — a failure records its class (failureClass, HealthSample.Fail) so DNS, timeout, refused, TLS, redirect and content failures reach the incident list, the timeline and the CSV with a reason. Anything that was not an HTTP error stored Up:false, Code:0 and showed nothing.
• fix — a failed check is re-probed after monitorConfirmDelay and only recorded if it fails again, so one dropped check no longer dents a month of uptime.
• fix — buildMonitorStats reports CoveredMs, and renderUptimeTiles prints how much history is behind a window rather than labelling a week "30 days".
• new — certificate expiry comes from every check: liveHosts now includes CheckStatus bookmarks, not only monitored ones.
• new — a recovery names its duration, TREND_SERIES gives the trend chart six series with a per-mode axis, /api/health/expectations-bulk mutes or unmutes a whole selection, and Settings.HealthCheckTimeoutSeconds replaces the fixed three-second dial timeout.

Search

• new — negation. parseSearchFilters produces filters.not, and matchesAdvancedFilters runs the positive keys then the negative ones, so tag:dev -status:pinned is expressible in the bar the way it always was in a collection rule.
• new — status:untagged, status:tagged, status:noted and status:unnoted; :trash as a command onto #config/data-backups/trash; and Ctrl/Cmd+Enter on a result opens in a new tab regardless of the standing preference.

Dashboard and config

• new — undo for moves: single (undoBookmarkCategoryMove) and cross-page bulk (undoBulkMoveToPage), each restoring from a snapshot so every bookmark returns to its own category. showGroupedNotification translated undoCallback into nothing — the bulk-delete undo it also gates has been dead since it shipped.
• new — category icons (openIconEditor, live preview into .category-title-icon) and Alt+←/→ to move a category, announced to screen readers.
• new — setting-art.js draws the settings whose subject is a shape (grid, spacing, margins, density, dots, type size, layout version, bar position, flow), in config and in help.
• fix — a settings change made elsewhere now reaches an open dashboard: fetchDataRevision tracks the settings revision (GetSettingsRevision) and routes a change through refreshAfterConfigSettingsUpdate.
• fix — a failed automatic backup is visible: autoBackupRunState records LastRunAt/LastRunError and the tile reports it.
• new — a bookmark row in config carries a page › category breadcrumb pill, each half filtering the list.
• new — fresh installs start on Retro CRT (defaultThemeID), with fold-all and shortcut hints off. Existing installs are untouched.
• new — the extension can send a link straight to the inbox: two context-menu entries, a quick-save-inbox command on Ctrl/Cmd+Shift+U, and tags carried through postInboxLink.

Docs

• static/data/whats-new/v1.2.0.json and the index entry ahead of v1.1.2. DASHBOARD_RELEASE (2026.08-dashboard-release-v1.2.0) and NEXTDASH_WHATS_NEW_DATA_VERSION (whats-new-v245) are both bumped: a feature release that left them alone would be announced to nobody who had already dismissed v1.1.2.
• tests/whats-new-hidden-release.spec.js: the real-index and constants cases move to v1.2.0. The four fixture-driven hideFromModal cases are untouched.
• Config → Overview gains three feature spotlights — typing filters/Enter opens, the health failure reason, and the inbox counts — with their five locale keys each in en/nl/de/fr.
• MANUAL.md and README.md carry the keyboard model, the inbox round, the health engine and the new settings; Config → Help and the printable cheat sheet were updated alongside them.

v1.1.2 — 15 August 2026

A release that exists to announce the one before it. v1.1.1 shipped hideFromModal so it would not displace v1.1.0 on the day both landed; that call is reversed here.

What's new

• fix — the hideFromModal flag is dropped from the v1.1.1 index entry, so the modal lists it again. The flag only ever gated the modal: the release tag and Config → Overview → Latest update read index[0] and have shown v1.1.1 since it shipped.
• new — DASHBOARD_RELEASE (2026.08-dashboard-release-v1.1.2) and NEXTDASH_WHATS_NEW_DATA_VERSION (whats-new-v244) are bumped, so the modal reopens once for every user. Unbumped they would have left the un-hiding invisible to anyone who had already dismissed it — the two tokens are the whole re-show mechanism, which is why v1.1.1 deliberately left them alone.

Docs

• static/data/whats-new/v1.1.2.json, and the index entry ahead of v1.1.1.
• tests/whats-new-hidden-release.spec.js: the real-index case flips from asserting v1.1.1 is hidden to asserting nothing in the top three is, and that the modal lists both v1.1.2 and v1.1.1; the constants case moves to the v1.1.2 literals and says why bumping is right here where it was wrong there. The four fixture-driven cases are untouched — the flag still works, it is simply no longer in use.
• MANUAL.md: the What's new section now says a release can be recorded without being announced, and names v1.1.1 as the one that was.

v1.1.1 — 15 August 2026

Keyboard consistency, and the parts of the app that teach it. Flagged hideFromModal in the index: it counts toward the version number and shows in Config → Overview → Latest update, but does not reopen the What's new modal, which still leads with v1.1.0. DASHBOARD_RELEASE and NEXTDASH_WHATS_NEW_DATA_VERSION are deliberately unchanged — those tokens are what re-show the modal.

Keyboard

• new — the Shift+letter family is closed: Shift+E inline edit and Shift+V preview join move, tag, delete, checking, pin, share and reveal. ; and [ still work, undocumented, the way 0 still opens the inbox. Brackets mean previous / next sub-tab in config, and one pair of keys meaning two things was the reason to move preview off [.
• new — share moves to Shift+L, so Shift+S always opens config. It was the only key whose meaning depended on whether a row was selected, which took two cheat-sheet rows and a parenthesis to explain. The capture-phase handler still declines rather than swallows a key it has no row for — that is what keeps Shift+S reaching setupPageShortcuts over a selected row, and tests/shift-key-row-actions.spec.js (renamed from shift-s-two-meanings.spec.js) pins it.
• new — bare letters act on keydown. C_HOLD_MS and the g-chord hold are gone, and with them the whole keyup handler in keyboard-navigation.js and SearchComponent.addShortcutLetter, which had no other caller. _activateGChordMode now runs on the first g; G_CHORD_MS (3s) is the only timer left.
• new — j/k alias ArrowDown/ArrowUp in the grid, matching config's section rail and bookmark list.
• new — Shift+Home focus...

v1.1.2

A release that exists to announce the one before it. v1.1.1 shipped hideFromModal so it would not displace v1.1.0 on the day both landed; that call is reversed here.

What's new

• fix — the hideFromModal flag is dropped from the v1.1.1 index entry, so the modal lists it again. The flag only ever gated the modal: the release tag and Config → Overview → Latest update read index[0] and have shown v1.1.1 since it shipped.
• new — DASHBOARD_RELEASE (2026.08-dashboard-release-v1.1.2) and NEXTDASH_WHATS_NEW_DATA_VERSION (whats-new-v244) are bumped, so the modal reopens once for every user. Unbumped they would have left the un-hiding invisible to anyone who had already dismissed it — the two tokens are the whole re-show mechanism, which is why v1.1.1 deliberately left them alone.

Docs

• static/data/whats-new/v1.1.2.json, and the index entry ahead of v1.1.1.
• tests/whats-new-hidden-release.spec.js: the real-index case flips from asserting v1.1.1 is hidden to asserting nothing in the top three is, and that the modal lists both v1.1.2 and v1.1.1; the constants case moves to the v1.1.2 literals and says why bumping is right here where it was wrong there. The four fixture-driven cases are untouched — the flag still works, it is simply no longer in use.
• MANUAL.md: the What's new section now says a release can be recorded without being announced, and names v1.1.1 as the one that was.

v1.1.1 — 15 August 2026

Keyboard consistency, and the parts of the app that teach it. Flagged hideFromModal in the index: it counts toward the version number and shows in Config → Overview → Latest update, but does not reopen the What's new modal, which still leads with v1.1.0. DASHBOARD_RELEASE and NEXTDASH_WHATS_NEW_DATA_VERSION are deliberately unchanged — those tokens are what re-show the modal.

Keyboard

• new — the Shift+letter family is closed: Shift+E inline edit and Shift+V preview join move, tag, delete, checking, pin, share and reveal. ; and [ still work, undocumented, the way 0 still opens the inbox. Brackets mean previous / next sub-tab in config, and one pair of keys meaning two things was the reason to move preview off [.
• new — share moves to Shift+L, so Shift+S always opens config. It was the only key whose meaning depended on whether a row was selected, which took two cheat-sheet rows and a parenthesis to explain. The capture-phase handler still declines rather than swallows a key it has no row for — that is what keeps Shift+S reaching setupPageShortcuts over a selected row, and tests/shift-key-row-actions.spec.js (renamed from shift-s-two-meanings.spec.js) pins it.
• new — bare letters act on keydown. C_HOLD_MS and the g-chord hold are gone, and with them the whole keyup handler in keyboard-navigation.js and SearchComponent.addShortcutLetter, which had no other caller. _activateGChordMode now runs on the first g; G_CHORD_MS (3s) is the only timer left.
• new — j/k alias ArrowDown/ArrowUp in the grid, matching config's section rail and bookmark list.
• new — Shift+Home focuses the category header via focusCategoryHeader(), which reuses resolveFocusedCategoryEl. Delete on a focused header calls categoryMenu.runAction('delete', …) instead of opening the menu; Shift+F10 opens it.
• fix — handleContextMenu took clientX/clientY at face value, which a keyboard-raised contextmenu reports as 0/0. menuPointFor() falls back to the row's rectangle; the category menu's own handler does the same.
• fix — resolveFocusedCategoryEl took an options argument: :width keeps the first-category fallback because the palette names what it acts on, Shift+W passes fallbackToFirst: false and falls through.
• fix — search.js kept a code-name list (KeyM/KeyD/KeyT/KeyB) that had fallen behind the keys added since; it tests /^Key[A-Z]$/ now.
• fix — setupPageShortcuts was the only typing guard in the app without an isContentEditable check.

Discoverability

• new — DashboardContextMenu renders a kbd.move-popover-item-key per entry with a matching aria-keyshortcuts, for all eleven actions that have a key. ShortcutFormat.ariaKeys() and .modifierLabel() are shared with the category menu, which had the chips but no aria.
• new — syncShortcutAriaHints() stamps aria-keyshortcuts on the toolbar, the header buttons and the first nine page tabs. It runs independently of showShortcutTooltips: the tooltips are a desktop hover affordance that can be switched off, this is the only route the keys have to assistive technology. shortcutButtonDefs() replaces the three parallel lists that let the header row end up with tooltips and no aria.
• fix — the side-rail legend printed the what's-new button's ★ glyph in the same chip as real keys.

Cheat sheet

• fix — buildPrintSections passed each row's printFallback to the caller's label resolver as a fallback, and generate-cheatsheet.cjs resolves from locales/en.json, where the i18n check guarantees every cheatKey exists. The short wording therefore never reached paper for any of the 23 rows that carry one. printLabel() uses it directly. validate-cheatsheet-registry.cjs gains a check built with the generator's resolver — with the identity resolver the other checks use, a printFallback wins either way and the check would pass against the bug.
• new — printed rows for k/j, Shift+E and Shift+Home; nextDash-cheatsheet.html, nextDash-cheatsheet.pdf and the static/ copy regenerated.

Config

• new — logFilterActivity is a fourth value for the log viewer's Show control, matched on Source == "activity" by logEntryMatchesFilter() rather than on severity. Activity lines already flowed into serverLogSink through log.Printf("activity: …") and parseServerLogLine already split the subsystem out; nothing about capture or NEXTDASH_ACTIVITY_LOG changes.
• new — Help → About carries the wordmark and three addresses: nextdash.cc, GitHub, and jordibrw.nl. The help-signature sign-off is dropped, so each address appears once.

Dashboard

• fix — .category-title centres its flex items instead of aligning them on the baseline. The + button hangs padding and a border below its own baseline, which made every header carrying it 1.44px taller; centring costs nothing, where a line-height tall enough to swallow the button added 3px to every header. .category-title--multiline keeps flex-start.
• fix — * carries the same guards as ! and ., with an exception for its own modal so it still closes the recent list.

Analytics

• new — settings-snapshot widens from 21 to 45 fields and a new content-snapshot reports install size (bookmarks, pages, categories, tags, finders, collections, monitored, inbox totals). Every value is bucketed client-side; MAX_EVENT_PROPS = 50 is Umami's per-event limit, which is why it is two events. analytics_content.go counts server-side and returns "" when telemetry is off — analytics_content_test.go proves it with a nil store, where any counting would panic.
• fix — a custom theme reported its own id, which is theme-<base36>-<4 chars> and random per install: not a name leak, but distinctive enough to follow one install across releases. It reports custom.

Docs

• MANUAL.md and README.md follow the moved keys, the G chord, the category-header keys, the right-click menu chips, the log viewer's Activity only and the About tab.
• locales/{en,nl,de,fr}.json: the cheat-sheet rows for the moved keys, two new rows (navCategoryHeader, bmCategoryDeleteKey), a rewritten config.helpKeyboardBody, keyboardFixedNoteGridNav without the hold, logLevelActivity, logActivityHint, helpAboutBody, helpSiteProject, helpSiteAuthor.
• static/nextdash-wordmark.png is keyed out of logo-ascii-on-black-large.png by greenness rather than brightness; the existing logo-ascii-transparent.png clears only pixels darker than 40, which leaves the glow behind the middle of the word as a dark ellipse.
• New: tests/dashboard-keyboard-uniformity.spec.js, tests/config-help-about.spec.js, TestServerLogSinkActivityFilter. Updated: the c-hold and G-chord cases in tests/create-page-category-from-dashboard.spec.js and tests/dashboard-grid-shortcuts.spec.js, the category-menu chip case in tests/dashboard-nice-to-haves.spec.js.
• go generate ./... for the changed CSS/JS.

v1.1.0 — 15 August 2026

The first minor since 1.0: a category can be wider than one column. DASHBOARD_RELEASE and NEXTDASH_WHATS_NEW_DATA_VERSION are bumped, so the modal reopens once.

Categories across columns

• new — Category.Spread (spread in bookmarks-{page}.json) marks a category as allowed to run across grid columns; uncategorized and the smart collections keep theirs in settings.categorySpreads[pageId][categoryId], the shape categorySortModes already uses. dashboard-category-span.js owns both, so no caller has to know which applies.
• new — the width itself is derived, never stored: spanForCount is min(ceil(count / categoryItemLimit), effectiveColumns, 12). It was a number the user picked in the first draft; it became a switch because the number is implied by two settings that already exist, and a stored number goes stale the moment a bookmark is added.
• new — applyCategoryItemLimit multiplies the limit by the span, so a spread category shows its limit once per column and stays the height of its neighbours. refreshAllCategorySpans runs from finishIncrementalRefresh, which is what makes an added bookmark bring the next column with it rather than waiting for a reload; settleSpanChange follows that through to the "+ N more" cut and, in packed mode, to a full re-render.
• new — the two settings rule out each other's extreme: `spreadUnavailable...

v1.1.1

Keyboard consistency, and the parts of the app that teach it. Flagged hideFromModal in the index: it counts toward the version number and shows in Config → Overview → Latest update, but does not reopen the What's new modal, which still leads with v1.1.0. DASHBOARD_RELEASE and NEXTDASH_WHATS_NEW_DATA_VERSION are deliberately unchanged — those tokens are what re-show the modal.

Keyboard

• new — the Shift+letter family is closed: Shift+E inline edit and Shift+V preview join move, tag, delete, checking, pin, share and reveal. ; and [ still work, undocumented, the way 0 still opens the inbox. Brackets mean previous / next sub-tab in config, and one pair of keys meaning two things was the reason to move preview off [.
• new — share moves to Shift+L, so Shift+S always opens config. It was the only key whose meaning depended on whether a row was selected, which took two cheat-sheet rows and a parenthesis to explain. The capture-phase handler still declines rather than swallows a key it has no row for — that is what keeps Shift+S reaching setupPageShortcuts over a selected row, and tests/shift-key-row-actions.spec.js (renamed from shift-s-two-meanings.spec.js) pins it.
• new — bare letters act on keydown. C_HOLD_MS and the g-chord hold are gone, and with them the whole keyup handler in keyboard-navigation.js and SearchComponent.addShortcutLetter, which had no other caller. _activateGChordMode now runs on the first g; G_CHORD_MS (3s) is the only timer left.
• new — j/k alias ArrowDown/ArrowUp in the grid, matching config's section rail and bookmark list.
• new — Shift+Home focuses the category header via focusCategoryHeader(), which reuses resolveFocusedCategoryEl. Delete on a focused header calls categoryMenu.runAction('delete', …) instead of opening the menu; Shift+F10 opens it.
• fix — handleContextMenu took clientX/clientY at face value, which a keyboard-raised contextmenu reports as 0/0. menuPointFor() falls back to the row's rectangle; the category menu's own handler does the same.
• fix — resolveFocusedCategoryEl took an options argument: :width keeps the first-category fallback because the palette names what it acts on, Shift+W passes fallbackToFirst: false and falls through.
• fix — search.js kept a code-name list (KeyM/KeyD/KeyT/KeyB) that had fallen behind the keys added since; it tests /^Key[A-Z]$/ now.
• fix — setupPageShortcuts was the only typing guard in the app without an isContentEditable check.

Discoverability

• new — DashboardContextMenu renders a kbd.move-popover-item-key per entry with a matching aria-keyshortcuts, for all eleven actions that have a key. ShortcutFormat.ariaKeys() and .modifierLabel() are shared with the category menu, which had the chips but no aria.
• new — syncShortcutAriaHints() stamps aria-keyshortcuts on the toolbar, the header buttons and the first nine page tabs. It runs independently of showShortcutTooltips: the tooltips are a desktop hover affordance that can be switched off, this is the only route the keys have to assistive technology. shortcutButtonDefs() replaces the three parallel lists that let the header row end up with tooltips and no aria.
• fix — the side-rail legend printed the what's-new button's ★ glyph in the same chip as real keys.

Cheat sheet

• fix — buildPrintSections passed each row's printFallback to the caller's label resolver as a fallback, and generate-cheatsheet.cjs resolves from locales/en.json, where the i18n check guarantees every cheatKey exists. The short wording therefore never reached paper for any of the 23 rows that carry one. printLabel() uses it directly. validate-cheatsheet-registry.cjs gains a check built with the generator's resolver — with the identity resolver the other checks use, a printFallback wins either way and the check would pass against the bug.
• new — printed rows for k/j, Shift+E and Shift+Home; nextDash-cheatsheet.html, nextDash-cheatsheet.pdf and the static/ copy regenerated.

Config

• new — logFilterActivity is a fourth value for the log viewer's Show control, matched on Source == "activity" by logEntryMatchesFilter() rather than on severity. Activity lines already flowed into serverLogSink through log.Printf("activity: …") and parseServerLogLine already split the subsystem out; nothing about capture or NEXTDASH_ACTIVITY_LOG changes.
• new — Help → About carries the wordmark and three addresses: nextdash.cc, GitHub, and jordibrw.nl. The help-signature sign-off is dropped, so each address appears once.

Dashboard

• fix — .category-title centres its flex items instead of aligning them on the baseline. The + button hangs padding and a border below its own baseline, which made every header carrying it 1.44px taller; centring costs nothing, where a line-height tall enough to swallow the button added 3px to every header. .category-title--multiline keeps flex-start.
• fix — * carries the same guards as ! and ., with an exception for its own modal so it still closes the recent list.

Analytics

• new — settings-snapshot widens from 21 to 45 fields and a new content-snapshot reports install size (bookmarks, pages, categories, tags, finders, collections, monitored, inbox totals). Every value is bucketed client-side; MAX_EVENT_PROPS = 50 is Umami's per-event limit, which is why it is two events. analytics_content.go counts server-side and returns "" when telemetry is off — analytics_content_test.go proves it with a nil store, where any counting would panic.
• fix — a custom theme reported its own id, which is theme-<base36>-<4 chars> and random per install: not a name leak, but distinctive enough to follow one install across releases. It reports custom.

Docs

• MANUAL.md and README.md follow the moved keys, the G chord, the category-header keys, the right-click menu chips, the log viewer's Activity only and the About tab.
• locales/{en,nl,de,fr}.json: the cheat-sheet rows for the moved keys, two new rows (navCategoryHeader, bmCategoryDeleteKey), a rewritten config.helpKeyboardBody, keyboardFixedNoteGridNav without the hold, logLevelActivity, logActivityHint, helpAboutBody, helpSiteProject, helpSiteAuthor.
• static/nextdash-wordmark.png is keyed out of logo-ascii-on-black-large.png by greenness rather than brightness; the existing logo-ascii-transparent.png clears only pixels darker than 40, which leaves the glow behind the middle of the word as a dark ellipse.
• New: tests/dashboard-keyboard-uniformity.spec.js, tests/config-help-about.spec.js, TestServerLogSinkActivityFilter. Updated: the c-hold and G-chord cases in tests/create-page-category-from-dashboard.spec.js and tests/dashboard-grid-shortcuts.spec.js, the category-menu chip case in tests/dashboard-nice-to-haves.spec.js.
• go generate ./... for the changed CSS/JS.

v1.1.0 — 15 August 2026

The first minor since 1.0: a category can be wider than one column. DASHBOARD_RELEASE and NEXTDASH_WHATS_NEW_DATA_VERSION are bumped, so the modal reopens once.

Categories across columns

• new — Category.Spread (spread in bookmarks-{page}.json) marks a category as allowed to run across grid columns; uncategorized and the smart collections keep theirs in settings.categorySpreads[pageId][categoryId], the shape categorySortModes already uses. dashboard-category-span.js owns both, so no caller has to know which applies.
• new — the width itself is derived, never stored: spanForCount is min(ceil(count / categoryItemLimit), effectiveColumns, 12). It was a number the user picked in the first draft; it became a switch because the number is implied by two settings that already exist, and a stored number goes stale the moment a bookmark is added.
• new — applyCategoryItemLimit multiplies the limit by the span, so a spread category shows its limit once per column and stays the height of its neighbours. refreshAllCategorySpans runs from finishIncrementalRefresh, which is what makes an added bookmark bring the next column with it rather than waiting for a reload; settleSpanChange follows that through to the "+ N more" cut and, in packed mode, to a full re-render.
• new — the two settings rule out each other's extreme: spreadUnavailableReason returns unlimited-items when categoryItemLimit is 0, and the config select disables Unlimited while anySpreadCategory holds. Both say why where they are asked for.
• new — routes: DashboardCategoryMenu (entry flips to Back to one column, no aria-checked beside a label that already flips), Shift+W in keyboard-navigation.js, :width on|off|all, a data-cat-spread button per row in the categories editor, and Appearance → Layout → Categories across columns for the defaults and the reset.
• new — .category--wide spans with grid-column: span var(--category-span) and repeats the row's track pattern once per column, so subgrid alignment survives. The inner column gap is the grid gap plus 2 × --category-inline-pad: a run of categories pads every column on both sides, a single wide box only its outer edges, and without that the inner columns sat 16px left of the grid. syncWideColumnTracks pins the shortcut and lead tracks, which are intrinsic and were sized per repeat by whichever rows happened to land in them.
• new — a rule under the header spanning the block, and a ↔N badge in the header, both dropped while the category is collapsed or one column wide.

Packed columns

• new — packed keeps its round-robin flex columns while nothing spreads, and switches to a grid (packed-masonry) the moment something does: --masonry-span rows per category from dashboard-packed-masonry.js, `grid-auto-...

v1.1.0

The first minor since 1.0: a category can be wider than one column. DASHBOARD_RELEASE and NEXTDASH_WHATS_NEW_DATA_VERSION are bumped, so the modal reopens once.

Categories across columns

• new — Category.Spread (spread in bookmarks-{page}.json) marks a category as allowed to run across grid columns; uncategorized and the smart collections keep theirs in settings.categorySpreads[pageId][categoryId], the shape categorySortModes already uses. dashboard-category-span.js owns both, so no caller has to know which applies.
• new — the width itself is derived, never stored: spanForCount is min(ceil(count / categoryItemLimit), effectiveColumns, 12). It was a number the user picked in the first draft; it became a switch because the number is implied by two settings that already exist, and a stored number goes stale the moment a bookmark is added.
• new — applyCategoryItemLimit multiplies the limit by the span, so a spread category shows its limit once per column and stays the height of its neighbours. refreshAllCategorySpans runs from finishIncrementalRefresh, which is what makes an added bookmark bring the next column with it rather than waiting for a reload; settleSpanChange follows that through to the "+ N more" cut and, in packed mode, to a full re-render.
• new — the two settings rule out each other's extreme: spreadUnavailableReason returns unlimited-items when categoryItemLimit is 0, and the config select disables Unlimited while anySpreadCategory holds. Both say why where they are asked for.
• new — routes: DashboardCategoryMenu (entry flips to Back to one column, no aria-checked beside a label that already flips), Shift+W in keyboard-navigation.js, :width on|off|all, a data-cat-spread button per row in the categories editor, and Appearance → Layout → Categories across columns for the defaults and the reset.
• new — .category--wide spans with grid-column: span var(--category-span) and repeats the row's track pattern once per column, so subgrid alignment survives. The inner column gap is the grid gap plus 2 × --category-inline-pad: a run of categories pads every column on both sides, a single wide box only its outer edges, and without that the inner columns sat 16px left of the grid. syncWideColumnTracks pins the shortcut and lead tracks, which are intrinsic and were sized per repeat by whichever rows happened to land in them.
• new — a rule under the header spanning the block, and a ↔N badge in the header, both dropped while the category is collapsed or one column wide.

Packed columns

• new — packed keeps its round-robin flex columns while nothing spreads, and switches to a grid (packed-masonry) the moment something does: --masonry-span rows per category from dashboard-packed-masonry.js, grid-auto-flow: row dense, a ResizeObserver per category. Bands were tried first and left a hole the height of the tallest column beside the wide block.
• fix — syncCategoriesFromDom read the columns in document order while the render filled them round-robin. Those are not each other's inverse, so every category drag rewrote the order into one that redistributed differently and scrambled the page. readCategoryElementsInOrder is the single inverse now, keyed on what is in the DOM, and getExistingCategories delegates to it.
• fix — syncDashboardGridLayout rebuilds className wholesale and dropped packed-masonry, so any settings refresh — including the one behind a window resize — left the categories as bare flex children of a row with no columns in it.

Config

• fix — the location memory was written only on the exits config knows about; the header's health, inbox and page buttons switch view around it. restoreConfigHash now saves on every move inside config and setActiveView stamps it on the way out. The TTL is 5 minutes (DashboardConfig and DashboardConfigLoader both), counted from leaving rather than from the last click inside.
• new — type: 'action' panel controls with bindPanelActions, used for Turn spreading off everywhere; NEW_THIS_RELEASE is the one place naming where the twinkle points, drawn on the section, the sub-tab and the panel.
• new — #category-context-menu sizes to its content (width: max-content, capped at 24rem). The shared .move-popover cap is for the move/tag/delete pickers; at 16rem the widest row here needed 274px and got 237, so the Shift+W chip was trimmed away — and the French label is half again as long.

Config → Bookmarks

• new — the section gets the sub-tab strip five others already have: List and Settings. The nine settings sat after the list — fifty rows down by default and up to five hundred as the infinite scroll loads more, which also rules out jumping to the bottom of a list whose bottom moves as you approach it. Registered in SUB_TABS, SUB_TAB_STATE, SUB_TAB_ATTR and SUB_TAB_SECTION, so the deep link, the remembered location and the arrow-key walk come for free; handleOverviewGo accepts bmTab.

Views

• new — Health, Inbox and Config → Bookmarks draw one card from feed-row.css instead of three copies. The rule was written out in health-view.css, dashboard-inbox.css and config-view.css and the copies had drifted into being byte-identical — one design, three places to change it, and no way to tell whether a difference was meant. What genuinely differs is a modifier: feed-row--with-select for Health's checkbox column, and the coloured left edge each view uses for its own state, including modern layout's inset redraw of it. Classic layout also gains the row focus ring only modern had.
• new — the shape the three views disagreed on is settled: Inbox rounded its filter pills and buttons where Health squared them off; rounded won. Config → Bookmarks reads as a view rather than a settings panel — a header with a count, the search box sized like Health's, and tiles matching Health's without the stripe.

Discoverability

• new — spread-notice.js (a NoticeCard) and spread-tutorial.js, a four-step AppModal walkthrough in the shape of the inbox and health tours, reachable afterwards from Help → Pages & categories.
• fix — NoticeCard bound an action with querySelector, and a card naming its × through dismissName puts that attribute on the × as well. The × comes first, so it took the handler and the button sharing its name got none: the side rail's No thanks had been dead since the cards were unified.

Docs

• MANUAL.md — the spreading section with the columns-per-bookmark-count table, and the config-memory paragraphs at five minutes. Config → Bookmarks is described with its two sub-tabs.
• README.md — the feature bullet, Shift+W, :width on|off, and the five-minute memory.
• CHANGELOG.md, static/data/whats-new/v1.1.0.json, index.json, whats-new-stub.js, tests/whats-new-hidden-release.spec.js, the four locale files, and go generate ./... for asset_hashes_gen.go.

v1.0.4

A review pass over the bookmark grid and the menus around it, in five rounds: correctness first, then consistency between routes that do the same thing, then accessibility, then performance, then cleanup. DASHBOARD_RELEASE and NEXTDASH_WHATS_NEW_DATA_VERSION are bumped, so the modal reopens once.

The grid

• fix — repaintBookmarkMutationSurfaces passed incremental: false, the one flag canAttemptDataPatch refuses outright, so every add, edit, delete, move and tag change tore down the whole grid — every DragReorder instance, the scroll offset and the focused row — for what is usually one changed row. The incremental path's own guards decide now: canAttemptDataPatch still bails on a layout-settings change and categoryStructureMatches on a category added, removed or reordered.
• new — the scroll offset is stored per page in _pageScrollPositions and consumed on return. Consumed, not kept: takeRememberedScroll deletes the entry, so a later deliberate visit still starts at the top.
• fix — the incremental renderer built a category's empty state without the + bookmark button createCategoryElement includes.
• fix — rows are built at tabIndex = -1 for the roving tab stop and KeyboardNavigation hands one of them a 0 only after walking the grid, which a render does not do — so Tab skipped the grid entirely from first paint. syncBookmarkGridA11y guarantees exactly one stop now, on the row currentIndex points at rather than on row 0, which would walk the tab position away from the user on every repaint.

Selecting several bookmarks

• new — deleteSelected offers an undo toast for 8s, restoring in ascending index order (each splice shifts what follows) and dropping the redundant trash entries afterwards via dropRestoredTrashEntries.
• fix — a failed save left the rows spliced out of the model and the selection cleared, then returned silently. Both are restored and showErrorNotification is called.
• fix — the toolbar was prepended into #dashboard-layout, which carries role="grid"; a role="toolbar" among rows and rowgroups is invalid. It also rendered as a 90×278 vertical strip, because the grid is a flex row and width: 100% had nothing to fill. Inserted before the grid instead: full width, 44px tall, still sticky.
• fix — the tags popover bound no scroll or resize handler and drifted away from its anchor. It reuses the shared reposition and outside-close helpers now.

Search

• new — SearchComponent.FILTER_KEYS replaces three hardcoded four-item lists. opened: and added: parsed and filtered correctly but were absent from getFilterHintItems, unoffered as a prefix, and unrecognised by _isCompleteFilterQuery, so the completion list kept firing over real results. Their values are offered the way status values are, with never only under opened:.

Tag filters

• fix — updateTagFilterIndicator had been reduced to a teardown that emptied #tag-filter-indicator on every call, leaving the header element and its CSS doing nothing. It carries the active tags and the match count now, and hides itself while the in-grid banner is on screen so the chips are not shown twice. renderTagFilterBanner gained withToolbar for that.

Menus and popovers

• fix — resolveRowBookmark fell back to the URL for rows with no page-local index and searched the current page first. The same URL legitimately sits on more than one page, so a row belonging to another page resolved to the wrong bookmark before delete ever saw it. It matches on the row's visible label now; list order only decides when nothing distinguishes the candidates. Fixed in both copies — dashboard-bookmark-interactions-loader.js keeps its own, and that is the one that runs on the first right-click of a session.
• fix — _persistBookmarkField swallowed every error and returned nothing while all three pin routes flipped pinned themselves. It applies the change (synchronously, before its first await, so the palette label still updates), reverts on failure, surfaces an error and returns a boolean; the callers no longer flip anything.
• fix — the Delete key went through AppModal while Shift+D and the context menu used the anchored popover. All three use the popover now. The modal stays for the inline editor, whose row is a form at that moment, and for a multi-row selection.
• fix — one shared _bindActionPopoverOutsideClose for Move, Delete, Tag and the multi-select tags popover: it also closes on an outside contextmenu, and matches the anchor by containment rather than identity.
• fix — _focusActionPopoverItem picks its pattern from the container's role: aria-activedescendant with focus on the box for role="listbox", roving tabindex for menus. The tag popover's second capture-phase keydown listener is removed — document capture runs first and every branch calls stopImmediatePropagation, so it never ran.
• new — the check-mode submenu entry sets aria-expanded, opens with ArrowRight and closes with ArrowLeft, matching the Escape path that already existed.
• new — the category menu shows F2 and Delete as aria-hidden chips. "Add category" gets none: it is a held c, and a chip would promise a tap that goes to the shortcut search.
• new — the category sort button opens on ArrowDown, which aria-haspopup="menu" already promised.
• fix — _restoreActionPopoverFocus fell back to focusing a detached anchor, a no-op that left focus on <body>. It falls through to the first row still on the grid.

Reduced motion

• fix — dashboard.css overrode four selectors with animation: none !important, contradicting reduced-motion.css, which uses 0.01ms precisely so animationend still fires. bookmark-copy-flash and bookmark-pulse stayed on the row for the rest of the session. The 320ms wait before a cross-page move is skipped under reduced motion (ANIM.BOOKMARK_MOVE_OUT, prefersReducedMotion()).

Performance

• aria-colindex/aria-colcount are constant and are stamped in populateBookmarkRowView; syncBookmarkGridA11y no longer does a querySelector per row on every render to rewrite them.
• Click and auxclick are delegated to #dashboard-layout — two listeners for the grid instead of two per row. contextmenu stays per row: bindRow serves inbox cards too.
• restartRowAnimation replaces five hand-written copies of remove/reflow/add plus animationend.
• The action popovers reposition once per frame instead of once per scroll event, and the toolbar tooltip's pointermove sweep is frame-throttled with its header buttons cached.

Docs

• MANUAL.md — the Delete row in the shortcut table, and the Shift+S entries in the cheat sheet registry and all four locales.
• nextDash-cheatsheet.html and both PDFs — unchanged this release; the affected rows are not in the printed sheet.
• static/data/whats-new/v1.0.4.json, index.json, whats-new-stub.js, tests/whats-new-hidden-release.spec.js, README.md.
• 64 unused const d = this.dash; bindings across 12 files; two JSDoc blocks moved to the functions they describe; CLICK_OUTSIDE_DELAY_MS, syncAllBookmarksMetadata and the public delegate for updateBookmarkRowsCategoryInDom removed.
• go generate ./... for the changed CSS, JS and locales.

v1.0.3 — 14 August 2026

One theme across most of it: openCount, lastOpened, createdAt, updatedAt and tags were written on every path, fed the built-in features, and reached almost none of the ones the user drives. Plus settings for Config → Bookmarks, which had none.

Unlike v1.0.1 and v1.0.2 this is not flagged hideFromModal, and both of those had the flag removed in this release — every version is visible in the What's new modal again. DASHBOARD_RELEASE and NEXTDASH_WHATS_NEW_DATA_VERSION are bumped, so the modal reopens once for everyone.

Config

• new — the remembered config location applies on every exit and every way back in, expiring after 15 minutes (CONFIG_LAST_TTL_MS, stamped on the way out). It was saved only when leaving via Shift+H or Shift+I and cleared on every other exit, and resolveConfigOpenTarget additionally required activeView to be health or inbox — so the common route, Escape out and Shift+S back in, always landed on Overview. clearLastConfigLocation has no callers left and is removed. The expiry is duplicated in dashboard-config-loader.js, which reads the same entry on a cold load before the module exists; an entry with no savedAt predates the expiry and is treated as stale.

Config → Bookmarks settings

• new — ten settings, all previously constants: stored sort (configBookmarksSort), rows per load step, and the availability, pin and category a quick-added bookmark starts with; the interval a bookmark gets when switched to Monitor, including in bulk; thresholds for confirming a delete and a bulk icon refresh; the "not opened in N days" figure, which also drives the cleanup score; and the archive service template.
• new — clampBookmarkSettings enforces every range server-side rather than leaving it to the controls, since the API is reachable without the browser. The archive template must contain {url} and start with http, so it can never become a javascript: URL handed to window.open.
• fix — opening a bookmark from Config now respects openInNewTab. The setting existed and the grid honoured it; this path forced a new tab regardless.

Reaching the data

• new — opened: and added: in the search parser, matched by matchesAgeFilter against today/week/month/year, plus never for opened:. An unrecognised word filters nothing rather than everything, which is the safer way round for a typo.
• new — custom collection rules gain pinned, untagged, notOpenedDays and changedDays. valuelessRuleFields keeps pinned and untagged without a...

v1.0.3

One theme across most of it: openCount, lastOpened, createdAt, updatedAt and tags were written on every path, fed the built-in features, and reached almost none of the ones the user drives. Plus settings for Config → Bookmarks, which had none.

Unlike v1.0.1 and v1.0.2 this is not flagged hideFromModal, and both of those had the flag removed in this release — every version is visible in the What's new modal again. DASHBOARD_RELEASE and NEXTDASH_WHATS_NEW_DATA_VERSION are bumped, so the modal reopens once for everyone.

Config

• new — the remembered config location applies on every exit and every way back in, expiring after 15 minutes (CONFIG_LAST_TTL_MS, stamped on the way out). It was saved only when leaving via Shift+H or Shift+I and cleared on every other exit, and resolveConfigOpenTarget additionally required activeView to be health or inbox — so the common route, Escape out and Shift+S back in, always landed on Overview. clearLastConfigLocation has no callers left and is removed. The expiry is duplicated in dashboard-config-loader.js, which reads the same entry on a cold load before the module exists; an entry with no savedAt predates the expiry and is treated as stale.

Config → Bookmarks settings

• new — ten settings, all previously constants: stored sort (configBookmarksSort), rows per load step, and the availability, pin and category a quick-added bookmark starts with; the interval a bookmark gets when switched to Monitor, including in bulk; thresholds for confirming a delete and a bulk icon refresh; the "not opened in N days" figure, which also drives the cleanup score; and the archive service template.
• new — clampBookmarkSettings enforces every range server-side rather than leaving it to the controls, since the API is reachable without the browser. The archive template must contain {url} and start with http, so it can never become a javascript: URL handed to window.open.
• fix — opening a bookmark from Config now respects openInNewTab. The setting existed and the grid honoured it; this path forced a new tab regardless.

Reaching the data

• new — opened: and added: in the search parser, matched by matchesAgeFilter against today/week/month/year, plus never for opened:. An unrecognised word filters nothing rather than everything, which is the safer way round for a typo.
• new — custom collection rules gain pinned, untagged, notOpenedDays and changedDays. valuelessRuleFields keeps pinned and untagged without a value, so the server no longer drops them as half-filled. changedDays is the first reader updatedAt has ever had on the dashboard.
• new — a Recently added smart collection on createdAt, off by default, with its own limit and page scope. The other four all key on lastOpened or openCount, so "what did I just add" was unanswerable.
• new — previewDesc joins the search haystack, scored below the note: the site's words rather than the user's.
• new — drift reaches the dashboard header badge in the warning tier. A drifted link still returns 200, which is exactly why it needed a human.

Grid

• new — tag chips on rows, off by default, capped at a configurable two with the rest collapsing into +N. Rendered inside .bookmark-link rather than as a column: it is a subgrid whose columns align across every category, so an extra column would shift every row. Verified by measuring the shortcut column before and after — identical to the pixel, and pinned as a test.
• new — createSortControls rebuilt as one active button plus a ⋯ menu. Four buttons per header, repeated per category, took more width than the bookmark names; the strip goes from ~90px to 19px, or 58px once something is sorted.
• new — two sort modes, added and opens.
• fix — the grid's recent mode sorted by lastOpened while Config used the same words for createdAt. Renamed to opened; normalizeSortMode still accepts the old value so stored categories keep working.

Keyboard and pointer

• new — Shift+P pin, Shift+S share, Shift+R reveal in Health, t filter to the row's tag. Each delegates to the existing implementation — _persistBookmarkField, shareBookmark, revealInHealth, toggleTagFilter — rather than adding a second path that could drift.
• new — pin gains a right-click entry. It had Shift+P and :pin but no pointer route at all from the grid, while every other one-bit row action had one.
• fix — Ctrl/Cmd+Enter opens in a new tab for that press alone. selectCurrentElement fired a bare .click(), which constructs no MouseEvent and carries no modifier, so the keyboard had only the standing openInNewTab preference.

Inbox

• fix — triage swallowed every key but Escape. Its guard asked dash.isModalOpen(), which counts the triage overlay itself, so the overlay blocked its own keyboard. Now asks isLayeredModalOpen() — whether something sits over triage. advance() was correct all along; nothing called it. Reported earlier and not reproducible then; the repro is a seeded queue of three and two presses of j.
• new — a seven-step one-time tour (inbox-tutorial.js, inboxTutorialV1), fetched on demand rather than with the module: the inbox loads during bootstrap for the unread badge, so riding along would cost every session that never opens the view. Guards and structure mirror health-tutorial.js.
• fix — resetOnboarding now calls clearSeenTips(). It only cleared onboardingCompleted while its own dialog promised to replay "the welcome tour and tips" — those ids live in discoverabilityState.seenTips, which it never touched, so no tour or tip had ever come back. tipsNotBefore is cleared with them; seenSettingPromos is deliberately left alone.

Config → Help

• new — a fifth panel under Help → Inbox describing the one-time tour, and a matching entry in the help search index.

Docs

• README.md and MANUAL.md (§4.5, the config chapter and the shortcut table) corrected for the config location memory: three of the four places describing it stated the old rule.
• Four tests in config-dashboard-view.spec.js asserted the restored section without resetting config.section first, which closeConfigView leaves in memory — so they could not have failed. They reset it now.
• MANUAL.md §4.4 and §7.9 cover the tour; the Health tour's replay line was corrected — it claimed a button that did not do what it said, which is what turned up the resetOnboarding defect.
• README.md, CHANGELOG.md, the What's new modal and Config → Overview updated for this release.
• 45 locale keys per language for the tour, 2 for the help panel, in en, nl, de and fr; the German and French reset hints were corrected against the real control labels.
• resetDashboardData() added to the e2e helpers, and used by four spec files that depend on what they find. /api/reset re-seeds the defaults in ~39ms, so this is far cheaper than the per-spec fixtures estimated earlier. The suite as a whole is still not hermetic: ~166 files share one data directory.
• Known and not addressed: monitor-visibility-reveal shows two flaky tests in group runs that pass on retry.

v1.0.2 — 14 August 2026

A repair release for the config view, from a full audit of it. Flagged hideFromModal in index.json like v1.0.1, so it does not reopen the What's new modal.

The recurring fault: a read that failed degraded to an empty list, and the next write posted that emptiness back as the complete state. Failure and emptiness were the same value, so a server blip during an edit destroyed real data behind a "Saved" badge.

Data integrity

• fix — ensureCategoryOnPage (dashboard-config.js) turned a failed GET into a one-item POST that replaced every category on the page. Proven end to end: five categories in, one out, no error shown. SaveCategoriesByPage's guard cannot catch it, since it only rejects a zero-length list. Now throws rather than degrading.
• fix — loadFinders and loadCategoriesEditor set a _xLoadFailed flag instead of []; saveFinders and saveCategories refuse to write while it is set.
• fix — saveCategories returns whether it saved and takes the page id as an argument, captured by each caller at edit time. It swallowed the error and returned undefined either way, so the delete flow acted on a 409 as if it had worked — trash entry, undo toast and all. The page picker reassigns _catPageId synchronously, so a save in flight could also land on the wrong page.
• fix — SaveSettings (handlers.go) reports dropped collections in the response instead of discarding them behind {"status":"success"}. Surfaced when leaving the Collections tab, not per save: a half-filled row is the normal state while typing.
• fix — publishConfigSync added to dashboard-config-sync.js. The listener, the pending-marker drain and four specs all existed; nothing ever published, so a second tab stayed stale until reloaded by hand. The specs write the markers themselves, so they passed either way.

Config

• fix — refreshAllFavicons posted a body-less request to /api/bookmarks/prefetch-icons, which is per-page and decodes the body first, so it answered 400 every time. Routed through ConfigFaviconPrefetch, as search-commands.js and dashboard-quickstart.js already did.
• fix — the prefetch overlay drops pointer-events on completion. It covers the viewport at z-index: 12000 and stayed up through the 900ms completion pause and the reloads after it, so the page read "Icons updated" while every click landed on the overlay. Found via a spec that timed out clicking Save; elementFromPoint over the button returned the overlay.
• fix — guardUniqueName rejects empty and over-long names. It only ever checked duplicates and delegated emptiness to callers that n...

v1.0.2

A repair release for the config view, from a full audit of it. Flagged hideFromModal in index.json like v1.0.1, so it does not reopen the What's new modal.

The recurring fault: a read that failed degraded to an empty list, and the next write posted that emptiness back as the complete state. Failure and emptiness were the same value, so a server blip during an edit destroyed real data behind a "Saved" badge.

Data integrity

• fix — ensureCategoryOnPage (dashboard-config.js) turned a failed GET into a one-item POST that replaced every category on the page. Proven end to end: five categories in, one out, no error shown. SaveCategoriesByPage's guard cannot catch it, since it only rejects a zero-length list. Now throws rather than degrading.
• fix — loadFinders and loadCategoriesEditor set a _xLoadFailed flag instead of []; saveFinders and saveCategories refuse to write while it is set.
• fix — saveCategories returns whether it saved and takes the page id as an argument, captured by each caller at edit time. It swallowed the error and returned undefined either way, so the delete flow acted on a 409 as if it had worked — trash entry, undo toast and all. The page picker reassigns _catPageId synchronously, so a save in flight could also land on the wrong page.
• fix — SaveSettings (handlers.go) reports dropped collections in the response instead of discarding them behind {"status":"success"}. Surfaced when leaving the Collections tab, not per save: a half-filled row is the normal state while typing.
• fix — publishConfigSync added to dashboard-config-sync.js. The listener, the pending-marker drain and four specs all existed; nothing ever published, so a second tab stayed stale until reloaded by hand. The specs write the markers themselves, so they passed either way.

Config

• fix — refreshAllFavicons posted a body-less request to /api/bookmarks/prefetch-icons, which is per-page and decodes the body first, so it answered 400 every time. Routed through ConfigFaviconPrefetch, as search-commands.js and dashboard-quickstart.js already did.
• fix — the prefetch overlay drops pointer-events on completion. It covers the viewport at z-index: 12000 and stayed up through the 900ms completion pause and the reloads after it, so the page read "Icons updated" while every click landed on the overlay. Found via a spec that timed out clicking Save; elementFromPoint over the button returned the overlay.
• fix — guardUniqueName rejects empty and over-long names. It only ever checked duplicates and delegated emptiness to callers that never picked it up, so a cleared name saved as "" and two emptied names stopped colliding, since "" is never taken. Server clamps to the same 60 characters via clampEntityName (rune-wise, through truncateRunes), because the API is reachable without the browser.
• new — checkedAt, nextBackupAt and totalKept are rendered. All three were shipped by the server and read by nothing; totalKept was silently excluded from the inbox conversion sum while the panel above showed it as its own tile.
• fix — four config.* keys were missing from every locale (addBookmarkBtn, bookmarkNotFound, clearBookmarkFilters, saved).

Accessibility

• fix — labelSettingsControls() names every schema-rendered control after the panel is drawn. Labels render as <span class="config-field-label">, not <label for>, so selects and number inputs across Behavior and much of Appearance had no accessible name. Done in one pass rather than at ~30 render sites that would drift. Ranges also get aria-valuetext, since 0.85 is not what the UI shows.
• fix — captureControlPanelFocus() restores focus and caret across repaintActiveControlPanels. Controls bind on change, which fires while the control still has focus, and the repaint replaces the whole body — so the next Tab started from the top of the page. repaintTagsBody already did this, with a comment explaining the hazard.
• fix — bindSubTabStrip re-focuses on the next frame rather than testing target.isConnected immediately. Appearance activates through render(), which had not run yet, so the branch was skipped and focus landed on <body> — one ArrowRight killed every press after it.
• fix — both hand-rolled confirm dialogs handle Tab through FocusTrapUtils.trapTabKey. They declared aria-modal="true" and only handled Escape, so focus wandered into the page behind, including on Reset all data.

Import and export

• new — theme import (importThemeFromFile, normalizeImportedTheme), reusing Duplicate's id and naming logic so it lands as a new theme and cannot overwrite the palette on screen. A JSON file with no colour values is refused.
• new — CSV import (importBookmarksCSV, parseBookmarksCSV). Hand-written parser rather than split(','): the export quotes every field so a note can hold a comma, a doubled quote or a newline. Columns are matched by header, so reordering them in a spreadsheet still imports. Rows go through /api/bookmarks/import-browser, keeping URL de-duplication server-side.
• new — trash search across name, URL, tag, category and origin page, plus tick boxes and a bulk restore that runs per item so one failure cannot take the batch with it. Select-all covers what the search shows.
• new — SavedSearch added to Settings, normalized by normalizeSavedSearches (trimmed, incomplete entries dropped, capped at ten). Saved searches lived only in localStorage, so they were in no ZIP backup; anything left there is migrated on first read.

Removed

• Page archiving. Settings.ArchivedPageIds had defaults and a migration, and MANUAL and README described it as working and said where to find it, but no line of JS ever read it.

Docs

• Release dates now name the day in both the changelog and the modal, per the new convention; v1.0.0 and v1.0.1 backfilled.
• Twelve spec files fixed. None were product regressions: seeded inbox items read before the view had loaded them; showRecentButton asserted on the Display tab after it moved to Toolbar (eight failures from one line); appearanceTab set before openConfigView, which resets it; .first() matching a bookmark's smart-collection copy, whose row carries no page-local index; role="feed" asserted on #dashboard-layout for health, which renders it on .health-view-feed; cheat-sheet rows asserted visible inside collapsed <details>; last-opened-format.js still counted as lazy after 8115b0e7 made it eager; a hardcoded help-tab list now read from HELP_TABS; analytics regexes demanding the retired vYYYY. scheme; and config-info-reset demanding an ℹ for five fields whose own comment in FIELD_META explains they carry none.
• Known and not addressed: the suite is not hermetic. All 170 spec files share one data directory with no reset between tests, so parallel and sequential runs drop different handfuls. Every file that failed the last full run passes on its own.

v1.0.1 — 13 August 2026

A patch release on top of v1.0.0. Recorded here and versioned normally, but flagged hideFromModal in index.json so it does not reopen the What's new modal in front of users who have just read the 1.0 entry — see v2026.09.09.1 for the same treatment.

Health

• new — the collection trend chart moved out of .health-view-toolbar-actions, where it was a flex: 1 1 6rem track competing with the button row for space, into a new .health-view-note-row shared with the filter note. Reserving a column beside the buttons via padding-right was tried first and reverted: it stranded whichever button ran out of room on a line of its own.
• new — the chart gained a midpoint gridline, an endpoint dot, and a 100% axis label rendered outside the SVG. The label sits outside because preserveAspectRatio="none" stretches the viewBox to the layout box and would distort any type inside it. Only the ceiling is labelled; a 50% label was added and removed as one number too many.
• new — per-day hover readout. Hit zones are absolutely positioned <button> elements sized in CSS percentages rather than SVG geometry, for the same preserveAspectRatio reason: coordinates inside the viewBox drift away from where the pointer actually is. trendPointLabel() reads HealthTrendPoint.t (Unix ms), not a d/day field — an earlier draft assumed the latter and produced empty labels. A null reading renders "no reading" rather than 0%.
• new — showTrendExplainer() behind an ℹ beside the chart, kept separate from showHealthExplainer() so the fixed-axis and gap rationale is not buried in the view-wide text.

Update check

• fix — fetchGitHubLatestRelease read GitHub's /releases/latest, which resolves "latest" by published_at rather than by version. A patch published on the calendar line after v1.0.0 would be named there and then correctly rejected by compareReleaseTags, so a genuinely newer release was never announced in the modal or in Config → Overview. Now reads the release listing and orders it with compareReleaseTags, falling back to /releases/latest when the listing cannot be read.
• fix — the listing URL is derived from githubLatestReleaseURL via releaseListURL() rather than declared as a second package var. As two independent vars, TestFetchGitHubLatestRelease stubbed one and reached the real api.github.com with the other, passing against live data.

Docs

• Three inbox shortcuts shipped in v1.0.0 without reaching KeyboardViewLegends: Shift+↑/↓ (extend selection), Ctrl/Cmd+A (select all) and R (refresh). Added to INBOX_VIEW, which feeds both the inline legend and the cheat sheet. Printable sheet: 55 → 58 rows; nextDash-cheatsheet.html and both PDFs regenerated.
• TestWhatsNewStubReleaseConstants asserted a literal 2026.07 prefix on DASHBOARD_RELEASE; the regex now a...

v1.0.1

A patch release on top of v1.0.0. Recorded here and versioned normally, but flagged hideFromModal in index.json so it does not reopen the What's new modal in front of users who have just read the 1.0 entry — see v2026.09.09.1 for the same treatment.

Health

• new — the collection trend chart moved out of .health-view-toolbar-actions, where it was a flex: 1 1 6rem track competing with the button row for space, into a new .health-view-note-row shared with the filter note. Reserving a column beside the buttons via padding-right was tried first and reverted: it stranded whichever button ran out of room on a line of its own.
• new — the chart gained a midpoint gridline, an endpoint dot, and a 100% axis label rendered outside the SVG. The label sits outside because preserveAspectRatio="none" stretches the viewBox to the layout box and would distort any type inside it. Only the ceiling is labelled; a 50% label was added and removed as one number too many.
• new — per-day hover readout. Hit zones are absolutely positioned <button> elements sized in CSS percentages rather than SVG geometry, for the same preserveAspectRatio reason: coordinates inside the viewBox drift away from where the pointer actually is. trendPointLabel() reads HealthTrendPoint.t (Unix ms), not a d/day field — an earlier draft assumed the latter and produced empty labels. A null reading renders "no reading" rather than 0%.
• new — showTrendExplainer() behind an ℹ beside the chart, kept separate from showHealthExplainer() so the fixed-axis and gap rationale is not buried in the view-wide text.

Update check

• fix — fetchGitHubLatestRelease read GitHub's /releases/latest, which resolves "latest" by published_at rather than by version. A patch published on the calendar line after v1.0.0 would be named there and then correctly rejected by compareReleaseTags, so a genuinely newer release was never announced in the modal or in Config → Overview. Now reads the release listing and orders it with compareReleaseTags, falling back to /releases/latest when the listing cannot be read.
• fix — the listing URL is derived from githubLatestReleaseURL via releaseListURL() rather than declared as a second package var. As two independent vars, TestFetchGitHubLatestRelease stubbed one and reached the real api.github.com with the other, passing against live data.

Docs

• Three inbox shortcuts shipped in v1.0.0 without reaching KeyboardViewLegends: Shift+↑/↓ (extend selection), Ctrl/Cmd+A (select all) and R (refresh). Added to INBOX_VIEW, which feeds both the inline legend and the cheat sheet. Printable sheet: 55 → 58 rows; nextDash-cheatsheet.html and both PDFs regenerated.
• TestWhatsNewStubReleaseConstants asserted a literal 2026.07 prefix on DASHBOARD_RELEASE; the regex now accepts both the calendar and semver suffix shapes.
• TestBuildUpdateStatusDetectsNewerRelease used v9999.99.99.9 as its newer upstream. That first segment is above calendarVersionFloor (1000), so it is read as a calendar tag and correctly loses to semver — the fixture was wrong, not the comparison. Now v99.0.0.
• New tests/health-trend-placement.spec.js (6 specs). Locale keys for the trend title, axis, hover and explainer added to en/nl/de/fr.
• go generate ./... regenerated asset_hashes_gen.go for the changed JS and CSS.

v1.0.0 — August 2026

The first release under semantic versioning, and deliberate milestone: after a long run of bug fixing and consolidation has left the app feeling finished and stable rather than in flux. From here 1.x.0 carries features and 1.0.x carries fixes; see v2026.09.09.3 for the scheme change itself, which shipped the comparison logic ahead of this tag.

The bulk of this release is correctness work. A recurring class of bug ran through it: an operation that reported success for something it had not done — a move that could lose the bookmark, a category save that silently no-opped, an add that discarded the item it had just accepted. Several were found by tracing a pattern already solved correctly elsewhere in the same file.

Data integrity

• fix — _moveBookmarkToPage (dashboard-inline-edit.js) did a double whole-list read-modify-write: GET both pages, splice/push in memory, POST both back. A concurrent write to either page was clobbered, and a source save landing while the target save failed lost the bookmark from both. Now uses the single-item POST /api/bookmarks/add + DELETE /api/bookmarks endpoints, each atomic under the store lock.
• fix — bulkMoveTagFilterToPage (dashboard-tag-filter.js) had the same shape for a whole batch. Converted to per-item add+delete via Promise.allSettled, with a partial-failure toast.
• fix — deleteRemoteBookmarkInline read the whole source page, spliced, and POSTed it back, racing any concurrent write. Now uses the single-item DELETE endpoint. saveRemoteBookmarkEdit deliberately left as-is: no single-item update endpoint exists, and emulating one as delete+add would move the bookmark to the end of its page.
• fix — SaveCategoriesByPage returned nil for an empty-list save while bookmarks still referenced a category, changing nothing. Now returns ErrCategoriesStillReferenced, mapped to 409 by respondCategoriesSaveError.
• fix — category rename without originalId fell back to matching by array position, so dropping a middle category reassigned later categories' bookmarks. Positional fallback removed.
• fix — AddInboxLink trimmed at capacity after appending, discarding an item with an older AddedAt while returning success. Now uses trimInboxItemsKeeping plus a survival check, mirroring RestoreInboxLink.
• fix — DeleteBookmarkFromPage skipped read-cache invalidation.
• fix — concurrent page/category creation could clobber each other.
• fix — fetchBookmarkPreview cached error pages as valid previews.

API and validation

• fix — PUT /api/inbox skipped every validation POST performs: no validateBookmarkURL, no sanitizeBookmarkIcon. It was the one route that would store a javascript: URL or a private address under allowLocalBookmarks:false, and the only path where a client could write Icon.
• fix — an empty inbox URL returned 500 for a client error. validateBookmarkURL intentionally permits empty strings (bookmarks may have none), so the check belongs in the handler.
• fix — GetCategories/SaveCategories accepted a nonexistent page, materialising bookmarks-N.json as a side effect. Both now 404 via pageExists.
• fix — GetBookmarks silently returned 200 [] for a missing page/all param.
• fix — bookmark Name/Category/Note were never trimmed server-side, unlike Tags/Icon.
• new — POST /api/categories?dryRun=1 reports what a category save would do — which bookmarks move, which are orphaned, which submitted categories carry no originalId — and writes nothing. Shares buildCategoryRemap with the real save so the preview cannot drift from it.
• new — inbox text fields are bounded (clampInboxLinkFields), applied on add, patch and restore. inbox.json is rewritten whole on every mutation, so an unbounded field is paid for by every later request.
• fix — PATCH /api/inbox stored readAt verbatim, including negative and far-future values, while snoozedUntil directly above it was carefully clamped.
• new — PATCH /api/inbox accepts tags (a pointer, so clearing is expressible).

Inbox

• new — tags are rendered as filter chips, editable from the row menu, matched by search, and included in both exports. InboxLink.Tags had existed and been normalised since the field was added, with no UI at all.
• new — a Stats panel reads /api/inbox-stats, previously consumed only by the config view. Promote rate is measured against triaged (promoted + deleted) rather than added.
• new — bulk promote, bulk open, bulk copy links, Shift+click and Shift+arrow range selection, Ctrl/Cmd+A select-all.
• new — the right-click menu carries the inbox's own actions rather than the bookmark menu's.
• new — R re-fetches the feed, wiring up loadAndRender({refresh}), which had no caller.
• fix — a failed load rendered the empty state; now a distinct panel with a Retry button, matching the health view.
• fix — the keyboard cursor is no longer dropped after a delete.
• fix — Escape and view-level keys ran below the empty-list guard, so clearing ticks was impossible exactly when a filter hid them.
• fix — a consumed ?ib_id= deep link kept clearing searchQuery/domainFilter on every later render.
• fix — triage's delete ignored deleteItemWithUndo's return value; bulkSnooze discarded its results entirely; bulkDelete reported partial success as success and snapshotted survivors for undo.
• fix — capacity eviction is reported to the client, and evicted items' icons are cleaned up (previously only the explicit DELETE path called removeUnusedIconFile).
• new — a polite live region announces the row count after each render.

Health

• new — an orphaned-category issue type: bookmarks whose Category id matches no category on their page. Detect-only, following the shortcut-conflict precedent. Category save and browser import now invalidate the health report cache, which they did not need to before.
• fix — header badge polling moved from a fixed 60s interval to the server's cache TTL with exponential backoff, and no longer double-fetches on tab return (dashboard.js already refreshed there).
• new — header restructured to two rows matching .inbox-header; the trend chart moved into the toolbar.

Dashboard

• fix — _smartCollectionFilterNeedsCrossPageData had been collapsed into !_isSmartCollectionPageAllowed in an earlier commit; the two answer different questions and diverge on t...

v1.0.0

The first release under semantic versioning, and deliberate milestone: after a long run of bug fixing and consolidation has left the app feeling finished and stable rather than in flux. From here 1.x.0 carries features and 1.0.x carries fixes; see v2026.09.09.3 for the scheme change itself, which shipped the comparison logic ahead of this tag.

The bulk of this release is correctness work. A recurring class of bug ran through it: an operation that reported success for something it had not done — a move that could lose the bookmark, a category save that silently no-opped, an add that discarded the item it had just accepted. Several were found by tracing a pattern already solved correctly elsewhere in the same file.

Data integrity

• fix — _moveBookmarkToPage (dashboard-inline-edit.js) did a double whole-list read-modify-write: GET both pages, splice/push in memory, POST both back. A concurrent write to either page was clobbered, and a source save landing while the target save failed lost the bookmark from both. Now uses the single-item POST /api/bookmarks/add + DELETE /api/bookmarks endpoints, each atomic under the store lock.
• fix — bulkMoveTagFilterToPage (dashboard-tag-filter.js) had the same shape for a whole batch. Converted to per-item add+delete via Promise.allSettled, with a partial-failure toast.
• fix — deleteRemoteBookmarkInline read the whole source page, spliced, and POSTed it back, racing any concurrent write. Now uses the single-item DELETE endpoint. saveRemoteBookmarkEdit deliberately left as-is: no single-item update endpoint exists, and emulating one as delete+add would move the bookmark to the end of its page.
• fix — SaveCategoriesByPage returned nil for an empty-list save while bookmarks still referenced a category, changing nothing. Now returns ErrCategoriesStillReferenced, mapped to 409 by respondCategoriesSaveError.
• fix — category rename without originalId fell back to matching by array position, so dropping a middle category reassigned later categories' bookmarks. Positional fallback removed.
• fix — AddInboxLink trimmed at capacity after appending, discarding an item with an older AddedAt while returning success. Now uses trimInboxItemsKeeping plus a survival check, mirroring RestoreInboxLink.
• fix — DeleteBookmarkFromPage skipped read-cache invalidation.
• fix — concurrent page/category creation could clobber each other.
• fix — fetchBookmarkPreview cached error pages as valid previews.

API and validation

• fix — PUT /api/inbox skipped every validation POST performs: no validateBookmarkURL, no sanitizeBookmarkIcon. It was the one route that would store a javascript: URL or a private address under allowLocalBookmarks:false, and the only path where a client could write Icon.
• fix — an empty inbox URL returned 500 for a client error. validateBookmarkURL intentionally permits empty strings (bookmarks may have none), so the check belongs in the handler.
• fix — GetCategories/SaveCategories accepted a nonexistent page, materialising bookmarks-N.json as a side effect. Both now 404 via pageExists.
• fix — GetBookmarks silently returned 200 [] for a missing page/all param.
• fix — bookmark Name/Category/Note were never trimmed server-side, unlike Tags/Icon.
• new — POST /api/categories?dryRun=1 reports what a category save would do — which bookmarks move, which are orphaned, which submitted categories carry no originalId — and writes nothing. Shares buildCategoryRemap with the real save so the preview cannot drift from it.
• new — inbox text fields are bounded (clampInboxLinkFields), applied on add, patch and restore. inbox.json is rewritten whole on every mutation, so an unbounded field is paid for by every later request.
• fix — PATCH /api/inbox stored readAt verbatim, including negative and far-future values, while snoozedUntil directly above it was carefully clamped.
• new — PATCH /api/inbox accepts tags (a pointer, so clearing is expressible).

Inbox

• new — tags are rendered as filter chips, editable from the row menu, matched by search, and included in both exports. InboxLink.Tags had existed and been normalised since the field was added, with no UI at all.
• new — a Stats panel reads /api/inbox-stats, previously consumed only by the config view. Promote rate is measured against triaged (promoted + deleted) rather than added.
• new — bulk promote, bulk open, bulk copy links, Shift+click and Shift+arrow range selection, Ctrl/Cmd+A select-all.
• new — the right-click menu carries the inbox's own actions rather than the bookmark menu's.
• new — R re-fetches the feed, wiring up loadAndRender({refresh}), which had no caller.
• fix — a failed load rendered the empty state; now a distinct panel with a Retry button, matching the health view.
• fix — the keyboard cursor is no longer dropped after a delete.
• fix — Escape and view-level keys ran below the empty-list guard, so clearing ticks was impossible exactly when a filter hid them.
• fix — a consumed ?ib_id= deep link kept clearing searchQuery/domainFilter on every later render.
• fix — triage's delete ignored deleteItemWithUndo's return value; bulkSnooze discarded its results entirely; bulkDelete reported partial success as success and snapshotted survivors for undo.
• fix — capacity eviction is reported to the client, and evicted items' icons are cleaned up (previously only the explicit DELETE path called removeUnusedIconFile).
• new — a polite live region announces the row count after each render.

Health

• new — an orphaned-category issue type: bookmarks whose Category id matches no category on their page. Detect-only, following the shortcut-conflict precedent. Category save and browser import now invalidate the health report cache, which they did not need to before.
• fix — header badge polling moved from a fixed 60s interval to the server's cache TTL with exponential backoff, and no longer double-fetches on tab return (dashboard.js already refreshed there).
• new — header restructured to two rows matching .inbox-header; the trend chart moved into the toolbar.

Dashboard

• fix — _smartCollectionFilterNeedsCrossPageData had been collapsed into !_isSmartCollectionPageAllowed in an earlier commit; the two answer different questions and diverge on the default empty scope, silently disabling cross-page loading. Both restored, sharing only the id normalisation.
• fix — the staleness fingerprint omitted pinned, checkStatus, icon and note.
• fix — saveSettings swallowed its error without logging.
• fix — the translation-fallback pattern never fell back on a missing key.
• fix — multi-select Clear referenced a nonexistent keyboardNav property.
• fix — smart collection headers could be renamed via long-press/double-click.
• fix — copySelectedLinks had no execCommand fallback for plain-HTTP installs.
• fix — the inline-edit save hint always showed Ctrl, never Cmd on macOS.
• fix — multi-select Move/Tags buttons lacked aria-haspopup/aria-expanded; the recent-bookmarks skeleton lacked aria-busy.
• fix — the double /api/data-revision round-trip on tab refocus is debounced.
• new — bulk tag-filter delete offers an undo toast.
• new — _applyLoadedPageData's full-container view identity moved into one FULL_CONTAINER_VIEWS table instead of three hand-copied checks.
• new — NoticeCard (static/js/notice-card.js) is the shared bottom-left card; the analytics and side-rail notices were rewritten onto it. The push/outage notice was removed entirely.
• perf — noteDataMutation(pageID) scopes read-cache invalidation to the page a write touched.

Docs

• static/data/whats-new/v1.0.0.json added; index.json gains the entry first.
• static/js/whats-new-stub.js — both tokens bumped to 2026.08-dashboard-release-v1.0.0 / whats-new-v240.
• tests/whats-new-hidden-release.spec.js — constants test renamed and both literals updated.
• CHANGELOG.md, README.md, MANUAL.md updated; Config → Help gains a v1.0.0 note.
• go generate ./... regenerated asset_hashes_gen.go.