docs(changelog): reconcile the desktop work and promote v1.5.0

[Gerrrt]

Closes #162 — steps 1 and 2 of the readiness verdict. Step 3, cutting the tag, is deliberately left to you (see below).

What this does

[Unreleased] documented the Core → Windows parity pass through ~#154 and stopped, while #155–#161 landed a full status-bar redesign across both surfaces the host draws. This folds that work in, then promotes the section under ## [v1.5.0] - 2026-08-01.

I added a second lead paragraph rather than stretching the parity-pass one: the bar redesign is a distinct arc that grew out of the parity work, and several entries are live-testing fixes from actually running it.

Added — Zebar caffeine/keep-awake indicator (flagged as visual-only, since it renders state but doesn't yet drive a keep-awake mechanism) and the battery AC-power placeholder for machines with no battery.

Changed — the Zebar floating-islands adoption and PARITY.md rewrite (#155), the chip-less psmux bar (#157), the main → Gerrrt default-session rename (#157), weather in °F (#156), the sketchybar-matching workspace highlight (#159), and the spacing/font tuning (#159, #160).

Fixed — the IP pill rendering blank (#157 + #161), the prefix indicator shifting the centered tabs and leaking style into them (#158), and the cwd↔clock gap (#158).

Two entries got more detail than their commits gave them, because the mechanism is the useful part:

• The IP pill had two causes fixed in sequence — set -gq @vpn_pill "" clobbering the refresher's poked value on every reload, and then the real one: a pre-styled #[…] run inside an option value isn't re-interpreted when the format expands it. The changelog records both, and why psmux-pill-status looked healthy while the bar was empty (separate code path, plain file write). That asymmetry is exactly what would burn the next person debugging it.
• monitor-bell was already correctly documented — Desktop/psmux parity polish (monitor-bell, network color, weather °F, caffeine placeholder) #156 first claimed a setw fix, fix: revert GlazeWM bind_to_monitor (broke config) + psmux spacing #158 established psmux 3.3.7 doesn't implement it at all and reconciled the entry. Left as-is; noting it so the Desktop/psmux parity polish (monitor-bell, network color, weather °F, caffeine placeholder) #156-vs-fix: revert GlazeWM bind_to_monitor (broke config) + psmux spacing #158 discrepancy doesn't look unreviewed.

Version

v1.5.0 (minor). Three additive feats — jnv + web/lynx, the psmux island bar, the Zebar islands — no module export removed and no profile contract changed, so it doesn't reach major, but well past a patch.

Deliberately not done

I did not cut the tag. The tag line is at v1.4.7 because auto-tag has been PATCH-bumping the whole parity pass; as the readiness report notes, it will never produce a minor on its own, so v1.5.0 has to be cut by hand. That's an outward-facing, hard-to-undo action on a release you own, so it's yours to make:

git tag -a v1.5.0 -m v1.5.0 && git push origin v1.5.0

I did not document the GlazeWM bind_to_monitor change from #156. #158 reverted it as an invalid key for this GlazeWM version (it failed config validation on restart — zero monitors, wrong window sizes). Added and removed inside the same unreleased window, so it nets to zero and a changelog entry would describe a state no released version was ever in. Confirmed absent from desktop/glazewm/config.yaml. Flagging in case you'd rather have it recorded as a known dead end.

Checks

markdownlint-cli2 is back to the file's pre-existing baseline — the 2 MD024 duplicate-heading warnings in the v1.2.0-era sections were there before this change and are untouched; my edits introduced 3 MD049 emphasis-style errors, which are fixed.

Not render-verified on a Windows host — #155's own commit message carries that caveat and it's reproduced in the entry.

---

Generated by Claude Code

[Copilot]

Pull request overview

Reconciles CHANGELOG.md by folding the post-parity desktop/status-bar work into the previously-stale [Unreleased] section and promoting it as the v1.5.0 release entry dated 2026-08-01.

Changes:

• Promotes the prior [Unreleased] content under ## [v1.5.0] - 2026-08-01.
• Adds a second lead paragraph describing the distinct status-bar redesign arc (psmux + Zebar) and documents the related Added/Changed/Fixed entries in more detail.
• Expands release notes for Zebar/psmux fixes and redesign details (e.g., caffeine placeholder, AC-power battery placeholder, IP pill rendering root cause).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Gerrrt]

Done in d0b2239 — _Nothing yet._, matching the file's existing italic-aside style.

Agreed on the reasoning: a blank section doesn't distinguish "nothing has landed since v1.5.0" from "the promotion ate something," and that ambiguity is worst right after a promotion, which is exactly when someone reads it.

---

Generated by Claude Code

[Gerrrt]

Merged main in — #163 landed after this branch was cut and conflicted, since it added an [Unreleased] entry while this branch had promoted that section to v1.5.0.

Resolved by folding #163's entry into v1.5.0, not into the new empty [Unreleased]. v1.5.0 isn't tagged yet, so cutting the tag at main's tip will include #163's commit — filing it under [Unreleased] would claim it ships in the next release when it actually ships in this one.

Three things I reconciled rather than stacking, because they're one symptom iterated:

• absolute-centre is the real fix for the tab drift that fix: revert GlazeWM bind_to_monitor (broke config) + psmux spacing #158's equal-width prefix cell was working around. Both entries now say so, instead of reading as two unrelated fixes. The prefix entry is retitled to lead with the style-leak, which is the part still doing work.
• fix(psmux): widen the cwd→clock gap in status-right #163 also widened the cwd→clock gap 6 → 12 spaces — that's in its commit title but not its changelog entry. Folded into the existing gap entry, which now reads as the two passes it was: move it out of the #{?} branch so it renders at all, then widen it because it was still too tight.
• The Changed entry described the port as status-justify centre, which v1.5.0 no longer ships. It now points at the Fixed entry, so the release section describes one coherent end state.

The third is the one worth a second look — I edited a description of #163's own change beyond mechanical conflict resolution. Say the word if you'd rather the entry stayed verbatim as merged.

markdownlint-cli2 still at the file's pre-existing baseline (the 2 v1.2.0-era MD024 warnings, untouched).

---

Generated by Claude Code