release-notes: draft for the next release

[github-actions]

release-notes: draft for the next release — 2026-07-16

Here's the drafted release notes for the next tag.

---

Release-notes draft — since v3.5.2 → HEAD

Range resolved: v3.5.2 (commit 8089460, 2026-07-14) → HEAD (cf612a3) — 4 commits, all in nvim/.
Generator: git-cliff is absent in this environment, so used the first-party twin ./scripts/gen-release-notes.sh . v3.5.2 HEAD.

Generated bullets (raw, as-is)

### Features
- Feat(nvim): adopt five QoL tweaks from the voidarc config (d91975b)

### Bug Fixes
- Fix(nvim): address PR review on the git-toast + cursorline autocmds (7a49d37)

### Documentation
- Docs(nvim): clarify vimade fadelevel comment (direction was correct) (0ff5f1f)

---

Editorial pass

User-facing vs. internal

• User-facing (1 bullet, really): the feat(nvim) five-tweak set. This is the only change an operator will notice — auto-indent on blank-line insert, the git-ahead toast, vimade dimming + active-only cursorline, the lualine macro indicator, and exrc.
• Internal / plumbing (fold into the above): the fix(nvim) and docs(nvim) commits are both refinements of that same PR (feat(nvim): adopt five QoL tweaks from the voidarc config #228) — the fix addresses review feedback on the toast/cursorline autocmds, and the docs commit only clarifies a comment. Neither is a standalone change. In a curated changelog they should collapse into the single "Added" bullet, not appear as separate Fixed/Documentation entries. Your existing [Unreleased] section already does exactly this — the curated bullet is in good shape and needs no restructuring.

Breaking changes: None. But two items carry behavioral surface worth a sentence in the notes so nobody is surprised:

• exrc — Neovim now sources project-local config. It's gated on DOTFILES_OFFLINE and leans on vim.secure's trust prompt for untrusted repos, so it's not a silent code-execution vector — but it is new "runs code from the cwd" behavior. Worth calling out explicitly.
• git-ahead toast — does a network git fetch on VimEnter. Gated on DOTFILES_OFFLINE so it stays inert on engagement boxes, but reviewers of the release should know a startup network call now exists.

SemVer: additive editor features, no removals or contract changes → minor bump, v3.6.0.

Suggested headline:

v3.6.0 — Neovim quality-of-life: blank-line auto-indent, upstream-ahead toast, split-focus dimming, and project-local exrc.

---

Scope note: this cycle is nvim-only — no zsh/tmux/git/starship/CI changes. Report only; I haven't touched CHANGELOG.md or cut a tag. The [Unreleased] section already reflects this work, so curation here is minimal: optionally add the one-line exrc / network-fetch caveat to the existing bullet, then it's ready for make release.

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

[github-actions]

release-notes: draft for the next release — 2026-07-17

Here's the drafted release notes report.

---

/release-notes — draft for the next tag

Range: v3.6.1..HEAD (9 commits: 6 non-merge, 3 merges)
Generator: ./scripts/gen-release-notes.sh . v3.6.1 HEAD — git-cliff is not installed in this environment, so the first-party twin was used (same grouped, commit-parser output).

Raw generated draft (as-is)

Features

• feat(nvim,starship): cross-fleet fixes — Windows DAP/clipboard, venv/package prompt, robustness (15f1155)

Bug Fixes

• fix(nvim,zsh): un-deprecate cheatsheet highlight API and harden history hygiene (31cad5e)
• fix(security): verify hook tool downloads and least-privilege the routine tools (fix(security): verify hook tool downloads and least-privilege the routine tools #235) (202d9d0)
• fix(ci): stop routines from running nvim plugin build hooks with the token present (64d05de)
• fix(ci): grant release-readiness pull-requests: read for gh pr list (9345e05)

Refactoring

• refactor(zsh,tmux): drop hot-path forks, redundant logic, and brittle help (refactor(zsh,tmux): drop hot-path forks, redundant logic, and brittle help #237) (d0b790d)

---

Editorial pass

Note: the [Unreleased] section of CHANGELOG.md is already hand-curated and covers all six of these commits (grouped Changed / Security / Fixed). The generated bullets above map 1:1 onto prose that already exists — so for this release the curation work is essentially done; the task is mostly to verify nothing is missing and set the heading.

User-facing vs. internal plumbing

User-facing (a machine that syncs Core will feel these):

• feat(nvim,starship) — the biggest surface. New Neovim clipboard behavior (gated OSC52 fallback, Windows Get-Clipboard -Raw multi-line paste, Windows Python DAP paths, emmet_ls on .html, pcall-guarded LSP capabilities), plus Starship prompt gains ($virtualenv, $package, git_metrics, WSL badge). Broadest reach of the release.
• fix(nvim,zsh) — Cheatsheet keeps working on current/nightly Neovim (deprecation fix); HISTORY_IGNORE now keeps more secret shapes (--flag=value, TOKEN=/PASSWORD=/*ACCESS_KEY=/APIKEY) out of the plaintext history file.
• refactor(zsh,tmux) — behavior-preserving but user-perceptible: hot-path fork reduction on gcom/gswm/grbm (git_main_branch one-call resolve) and _core_suggest (no per-candidate fork). Startup/interactive latency wins.

Internal plumbing (repo-meta / CI — do not sync into core/, no operator impact):

• fix(ci) × 2 (64d05de, 9345e05) — routine-workflow token/permission scoping.
• fix(security) 202d9d0 — the routine --allowedTools least-privilege half is CI-only. However, the other half of the same commit — the session-start.sh hook verifying tool-download SHA-256 — is a real hardening change and is already in the ### Security block of [Unreleased].

Breaking changes

None detected. No !-bang or BREAKING CHANGE: footer in any commit; every behavioral change is explicitly framed as backward-compatible (Windows bits gated on has("win32"), native clipboard providers never overridden, refactors flagged behavior-preserving with fallbacks retained). One thing worth a curator's eye, though not breaking:

• git_current_branch now assumes git ≥ 2.22 (git branch --show-current). The detached-HEAD and outside-repo cases are preserved, but this is a new minimum-version assumption worth a one-line note if any target host ships older git.
• The dropped nvim-spectre sed→oxi swap is called out in the commit body as intentionally not shipped — nothing to note.

Suggested SemVer bump

MINOR → v3.7.0. One feat, no breaking changes, plus fixes/refactors. (Matches the [Unreleased] content.)

Suggested release headline

v3.7.0 — Cross-fleet Neovim & Starship fixes, plus hot-path and history-hygiene hardening

Alternate, if you want to lead with the security angle:

v3.7.0 — Windows/OSC52 clipboard + Starship prompt upgrades; verified hook downloads and least-privilege routines

---

Report only — I have not edited CHANGELOG.md or cut a tag. Given the [Unreleased] section already mirrors these bullets, the remaining curator step before make release is just moving that block under a ## [v3.7.0] - <date> heading.

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