release-readiness: go/no-go for the next dotfiles-Windows release

[github-actions]

release-readiness: go/no-go for the next dotfiles-Windows release — 2026-08-01

I have everything I need. Here's the readiness verdict.

---

Verdict: READY to cut v1.5.0 — the unreleased work carries three real feats, more than auto-tag's patch line can express on its own.

What would ship

The Core → Windows parity pass (2026-07) plus a desktop-bar redesign that landed after the [Unreleased] section was last written. The meaningful host work:

• jnv + web/lynx (feat(tools), chore(nvim): sync nvim/ from Core + fix checkhealth clipboard/regex, document psmux wart #150) — new interactive JSON explorer and a terminal-browser verb, closing fleet parity with Core's mid-2026 CLI tools. New commands = the clearest minor driver.
• psmux centered floating-island status bar (feat(psmux), feat(psmux): port Core's centered floating-island status bar #154) and a follow-up chip-less bar + Gerrrt session (psmux: chip-less bar + Gerrrt session + IP fix + fixes; Zebar battery placeholder #157) — a full status-bar redesign ported from Core.
• Zebar sketchybar floating-islands design (feat(zebar), feat(zebar): adopt sketchybar's floating-islands design + reconcile PARITY contract #155) — desktop-layer bar redesign, plus workspace-highlight/font/spacing polish (Desktop/psmux parity polish (monitor-bell, network color, weather °F, caffeine placeholder) #156, fix(zebar): match sketchybar's workspace highlight + tighten item spacing #159, fix(zebar): larger bar font + tighten left-island spacing #160).
• Command-block separators — exit-status-colored prompt rules (real UX feature, already in [Unreleased] → Added).
• A cluster of genuine fixes: nvim :checkhealth gerrrt clipboard false-warning, zebar network color, psmux monitor-bell config warning, GlazeWM bind_to_monitor revert, psmux IP-pill blank render (fix: revert GlazeWM bind_to_monitor (broke config) + psmux spacing #158, fix(psmux): IP/VPN pill renders blank — split text and colour into two options #161).

Mechanical churn (auto-tag already covered by patch tags): nvim/starship mirror-syncs, package refresh, ci(auto-tag) v4.5.0 adoption, docs-only commits.

Proposed version + why

v1.5.0 (minor). No breaking change exists — every feat is additive (web/jnv are new verbs, no module export removed, no profile contract changed), so it doesn't reach major; but three feats (jnv+web, psmux island bar, zebar floating-islands) put it firmly past a patch. The single strongest driver is feat(tools): add jnv + web/lynx (f3089fd) — a new user-facing command.

Tag drift: the tag line is at v1.4.7, seven mechanical patches ahead of the last deliberate CHANGELOG heading ## [v1.4.0] (2026-07-23). auto-tag has been PATCH-bumping the whole parity pass under the radar.

Next step

1. Reconcile the CHANGELOG first — [Unreleased] documents the parity pass through ~feat(psmux): port Core's centered floating-island status bar #154 but does not yet reflect the post-feat(psmux): port Core's centered floating-island status bar #154 desktop work: the zebar floating-islands adoption (feat(zebar): adopt sketchybar's floating-islands design + reconcile PARITY contract #155), psmux chip-less bar / Gerrrt session (psmux: chip-less bar + Gerrrt session + IP fix + fixes; Zebar battery placeholder #157), and the highlight/font/IP-pill fixes (fix(zebar): match sketchybar's workspace highlight + tighten item spacing #159–fix(psmux): IP/VPN pill renders blank — split text and colour into two options #161). Fold those into [Unreleased] before promoting.
2. Promote [Unreleased] under ## [v1.5.0] - 2026-08-01.
3. Cut the v1.5.0 tag deliberately — auto-tag will never produce a minor on its own.

Report only — I haven't touched CHANGELOG.md or tagged anything. You drive the release from here.

Filed by the claude-routines workflow. Report-first: review and act — nothing was changed.