Cut v3.17.0 release (dogfood: version-bump handler)

[Jason-Vaughan]

What

Cuts the v3.17.0 release using the new version-bump handler shipped in PR #202 — programmatic dogfood (handler invoked via node -e, staged writes flushed via commit._flushStagedWrites).

Why

The [Unreleased] section had accumulated thirteen ### Added + one ### Changed + one ### Fixed entries across the #139 series + #191 hotfix + #200 ai-content prompts + #202 version-bump handler — substantial release surface, ready to cut. And the new handler we just shipped is the obvious tool to do it.

How

Single Node invocation:

const versionBump = require('./lib/wrap-steps/version-bump');
const commit = require('./lib/wrap-steps/commit');
const ctx = {
  project: { name: 'TangleClaw-v3', path: process.cwd() },
  step: { id: 'version-bump', kind: 'version-bump' },
  staged: {},
  options: {}
};
const result = await versionBump.run(ctx);  // → ok:true, status:'done'
commit._flushStagedWrites(ctx.staged);       // → writes version.json + CHANGELOG.md

Handler output:

oldVersion: 3.16.2
newVersion: 3.17.0
bumpLevel:  minor (subsections detected: Changed, Fixed, Added)
detail:     3.16.2 → 3.17.0 (minor)

One manual edit on top of the handler output: the dated heading came out as 2026-05-23 (UTC) but every prior CHANGELOG entry uses local-PT dates; patched to 2026-05-22 to match the convention. Filed as #205 (handler should use local-zoned dates, not UTC) — future releases pick up the fix when that lands.

v3.17.0 release-notes summary (full text in CHANGELOG)

• [feature] Methodology-aware single-button session wrap #139 Methodology-aware single-button session wrap (series closed). 12 chunks; wrapV2: true is now the default; full server-side pipeline replaces the legacy NL-prompt flow. ADR 0002 is the durable home.
• Populate prawduct ai-content prompts (open-queue #2 post-#139) #200 (open-queue Add Linux support (systemd) #2): prawduct ai-content prompts populated.
• Real version-bump wrap-step handler (open-queue #3 post-#139) #202 (open-queue Add dark/light theme toggle to session wrapper #3): real version-bump handler — the one that cut this release.
• Fix tmux.createSession env vars not reaching launch command process #191: tmux env-ordering hotfix.
• [chore] CHANGELOG structural-invariants test to prevent silent heading regressions #168: CHANGELOG structural-invariants test.

Test plan

• test/changelog-structure.test.js (9 tests) passes against the bumped CHANGELOG. Release-heading sequence, no duplicates, descending semver, parseable date format all intact.
• Handler output: real run produced status: 'done', both staged entries with correct bumpLevel: 'minor' and oldVersion: '3.16.2' / newVersion: '3.17.0' metadata.
• Bytes-on-disk: post-flush, version.json is {"version": "3.17.0"} + trailing newline; CHANGELOG.md [Unreleased] retained empty at top, full prior content moved under ## [3.17.0] - 2026-05-22, ## [3.16.2] - 2026-05-13 and prior preserved byte-for-byte.

Post-merge follow-ups

• Tag v3.17.0 + gh release create v3.17.0 (done by the session immediately after merge).
• Add > 🚀 feature-release banner to the ## [3.17.0] section. Handler intentionally does NOT auto-inject; curated decision per banner convention.
• [bug] version-bump handler uses UTC date instead of local-timezone date for new release heading #205 fix (UTC → local date in the handler) when scope allows.

Out of scope

• Banner emoji injection (curated decision).
• The _topReleasedVersion runtime guard from [enhancement] version-bump should refuse to bump when version.json trails CHANGELOG's top released heading #203 (separate issue).
• The output.skipped:true convention lockstep from [enhancement] Backfill output.skipped:true on all wrap-step handlers' skip returns for drawer-side lockstep #204 (separate issue).