Docs: record the 0.15.0 work missing from the changelog - #71
Merged
Merged
Conversation
Adds a fourth bundled background and makes it the one a brand-new install opens on, replacing Golden Gate as the first impression of the app. The gallery's NN- prefix does double duty: it orders the tiles and it picks the first-run default (ThemeManager.ApplyFirstRunBackground takes whatever sorts first). So making the new image the default means renumbering, and the three existing backgrounds move down one position each. That renaming is deliberate but not free. The file name is the durable identity persisted in ui-settings.json, so someone who had explicitly picked one of the three keeps their background working — the image is a copy in their own data folder — but its tile may stop showing as selected until they pick it again. Users on a custom background, or on none, are unaffected either way; the first-run path is guarded on a missing settings file and cannot fire for anyone who has launched the app before. No code change: BuiltInBackgrounds discovers the folder at startup and the csproj globs it by extension, so shipping an image is a file drop.
An audit of the 0.15.0 section against every pull request merged since v0.14.1 found three user-visible changes that shipped without an entry. Adds /compact and the persisted compacted context, with the clarified /clear wording that shipped alongside it; the deletion fix that keeps the snapshot, history, and note lists from resetting; and the high-contrast notice cards that keep status, plan, approval, and recovery messages readable over an image-heavy chat background. Documentation only; no code or behaviour changes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
An audit of the 0.15.0 changelog against every pull request merged since
v0.14.1found threeuser-visible changes that shipped without an entry. This adds them, so they are announced at
release rather than discovered by users.
Documentation only — no code, no behaviour change.
What was happening
The
[Unreleased]section is what the release notes get written from. Thirty-five pull requestshave merged into this generation, and three of them left no trace in it — including a command
users can type. At release they would simply have gone unmentioned.
What is new
/compactand the persisted compacted context. Desktop gained on-demand compaction, and thecompacted context is saved so it survives a restart.
/clearwas reworded at the same time tostate plainly that it wipes context completely, so the two commands are not confused. None of
this was recorded.
rebuild the whole list, so surviving cards slid back up and expanded groups collapsed — losing
your place mid-cleanup. The fix shipped; the entry did not.
rather than plain text so they stay readable over a chat background at high image opacity. This
belongs with the other readability entries in this release, which already cover the token metric,
secondary text, and the empty state.
Scope and risk
Low. One markdown file. Nothing compiles from it and no code path reads it.
The risk is editorial: whether each entry matches what actually shipped. All three were written
from the merged PRs rather than from memory, but the
/compactentry is the one most worth asecond read, since it is the only one describing a command whose exact wording users will compare
against what they see in the app.
Two things this deliberately does not add, called out so the omissions are a decision rather
than an oversight:
PR states no user-visible behaviour is lost, so there is nothing to announce.
active agent — is below the bar the rest of this changelog sets. Say the word and I will add it.
Verification
v0.14.1..main(Document the release process in RELEASING.md #35 through Feature: agents can address each other by name #69) was listed and matched against the[Unreleased]section one by one; these three are the entries with no corresponding text.###heading precededby a blank line — since the insert points sit on section seams.
Not covered: no build or test run, because nothing here is code. The suite was green at 489
passing on the parent branch. Whether each entry describes its feature accurately needs a human
read.
Dependency
Stacked on #70 (Midnight Ramen background), which also edits
CHANGELOG.md. Merge #70 first;this branch contains its commit and would otherwise conflict. Reviewing just the second commit
(
a2b0259) shows this change on its own.The paired engine audit is DevMando/MandoCode#96, which found seven gaps on that side —
including that per-step verification by a second model was removed without a changelog entry.